Computer Science at Indiana State University - Recent changes [en]

FAQ

Jkinne — Fri, 05 Jun 2026 02:03:39 GMT

Recommended Computer

← Older revision		Revision as of 02:03, 5 June 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
			==Recommended Computer==
			Much of what we do in CS courses can work in Windows, Mac OS, Linux, or Chrome. There will be an odd thing or two still that may not work in Chrome.

			All other things being equal, getting a computer that is not "bottom of the barrel" would be good. Chromebooks in the $400+ range should generally work reasonably well. For Windows/Linux/Mac OS laptops, you should be looking for 8GB RAM bare minimum, preferred 16GB if possible, and avoid getting a laptop with an i3 or Celeron processor; this roughly corresponds to the $500+ price range. You can potentially get anything to work, but will have an easier time with a medium-range computer than a low-end system.

			For laptops, we recommend getting at least a 3 year warranty (since they tend to break if you actually do transport them around). Also, we recommend getting an option that has a long battery life (rule of thumb - battery life will be half of its original rating after 1-2 years of regular daily use).

			You should also have the ability to install programs on the system and have a normally reliable internet connection at home if possible.

			If you have a particular system in mind for purchase that you would like an opinion on, please feel free to contact one of the CS faculty members.

			University recommendations are listed [https://indstate.teamdynamix.com/TDClient/1851/Portal/KB/Article/71665/Student-Laptop-Minimum-Specifications here] and are similar to that described above.

	== CS 151 ==		== CS 151 ==
	New students majoring in computer science should take ECT 130 and CS 151 their first term. ECT 130 is an overview of CS, IT, and CEET majors. It is required for all of those majors. There is a ''small'' amount of programming. CS 151 is the first programming course in the CS major, is a full semester of programming (in Python, as of 2026), and helps to decide whether you prefer CS or IT.		New students majoring in computer science should take ECT 130 and CS 151 their first term. ECT 130 is an overview of CS, IT, and CEET majors. It is required for all of those majors. There is a ''small'' amount of programming. CS 151 is the first programming course in the CS major, is a full semester of programming (in Python, as of 2026), and helps to decide whether you prefer CS or IT.

Programming and CS - Getting Started

Jkinne — Fri, 05 Jun 2026 02:02:38 GMT

← Older revision		Revision as of 02:02, 5 June 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	We are developing Getting Started pages on the most important topics and skills that are used throughout our courses. These can be used by incoming undergraduate students to get a head start, incoming graduate students to review, or current students to refresh/remediate.

	~~=Recommended Computer=~~
	~~Much of what we do in CS courses can work in Windows, Mac OS, Linux, or Chrome. There will be an odd thing or two still that may not work in Chrome.~~

	All other things being equal, getting a computer that is not "bottom of the barrel" would be good. Chromebooks in the $400+ range should generally work reasonably well. For Windows/Linux/Mac OS laptops, you should be looking for 8GB RAM bare minimum, preferred 16GB if possible, and avoid getting a laptop with an i3 or Celeron processor; this roughly corresponds to the $500+ price range. You can potentially get anything to work, but will have an easier time with a medium-range computer than a low-end system.

	For laptops, we recommend getting at least a 3 year warranty (since they tend to break if you actually do transport them around). Also, we recommend getting an option that has a long battery life (rule of thumb - battery life will be half of its original rating after 1-2 years of regular daily use).

	~~You should also have the ability to install programs on the system and have a normally reliable internet connection at home if possible.~~

	~~If you have a particular system in mind for purchase that you would like an opinion on, please feel free to contact one of the CS faculty members.~~

	~~University recommendations are listed [https://indstate.teamdynamix.com/TDClient/1851/Portal/KB/Article/71665/Student-Laptop-Minimum-Specifications here] and are similar to that described above.~~

	=Getting Started Pages=		=Getting Started Pages=

CS accounts

Jkinne — Thu, 04 Jun 2026 22:29:11 GMT

← Older revision		Revision as of 22:29, 4 June 2026
Line 1:		Line 1:
	This page gives information about logging into and using the CS server (cs.indstate.edu). For help about getting started with using the terminal once you can login, see [[Linux and CS Systems - Getting Started]].		This page gives information about logging into and using the CS server (cs.indstate.edu). For help about getting started with using the terminal once you can login, see [[Linux and CS Systems - Getting Started]]. For more about getting started with programming in general for CS courses, see [[Programming and CS - Getting Started]].

	=Logging In=		=Logging In=

Gitlab - Getting Started

Jkinne — Thu, 04 Jun 2026 22:28:39 GMT

← Older revision		Revision as of 22:28, 4 June 2026
Line 1:		Line 1:
			''This page is part of [[Programming and CS - Getting Started]]''

	=Git=		=Git=
	[https://en.wikipedia.org/wiki/Git Git] is a version control system that can be used to keep track of your files (programming code, but also other files as well).		[https://en.wikipedia.org/wiki/Git Git] is a version control system that can be used to keep track of your files (programming code, but also other files as well).

Linux and CS Systems - Getting Started

Jkinne — Thu, 04 Jun 2026 22:27:42 GMT

← Older revision		Revision as of 22:27, 4 June 2026
Line 1:		Line 1:
			''This page is part of [[Programming and CS - Getting Started]]''

	This page is meant to help a new student in a CS course at ISU to get familiar with using Linux (in particular using the text-based terminal to interact with the system).		This page is meant to help a new student in a CS course at ISU to get familiar with using Linux (in particular using the text-based terminal to interact with the system).

Python Programming - Getting Started

Jkinne — Thu, 04 Jun 2026 22:26:30 GMT

Installing Python on Your Personal Computer

← Older revision		Revision as of 22:26, 4 June 2026
Line 65:		Line 65:
	'''Linux''' On Linux python is probably already installed. If not do an internet search for your Linux distribution and "install python3" (i.e., search for - ubuntu install python).		'''Linux''' On Linux python is probably already installed. If not do an internet search for your Linux distribution and "install python3" (i.e., search for - ubuntu install python).

	'''Chromebook''' You should first get Linux ~~(beta) installed (see [[https://cs.indstate.edu/web/index.php/Linux_-_System_Setup#Chromebook]])~~ and then you can follow instructions for installing python3 for ubuntu. If python3 is not already installed, then running <code>sudo apt install python3</code> should install it.		'''Chromebook''' You should first get the Linux development environment enabled and then you can follow instructions for installing python3 for ubuntu. If python3 is not already installed, then running <code>sudo apt-get install python3</code> should install it.

	==Lists of Problems==		==Lists of Problems==

Programming and CS - Getting Started

Jkinne — Thu, 04 Jun 2026 22:25:07 GMT

Getting Started Pages

← Older revision		Revision as of 22:25, 4 June 2026
Line 15:		Line 15:

	=Getting Started Pages=		=Getting Started Pages=
			* [[CS accounts]]
	* [[Linux and CS Systems - Getting Started]]		* [[Linux and CS Systems - Getting Started]]
	* [[Python Programming - Getting Started]]		* [[Python Programming - Getting Started]]

Linux - System Setup

Jkinne — Thu, 04 Jun 2026 22:24:38 GMT

Show changes

Beginning Programming

Jkinne — Thu, 04 Jun 2026 19:45:17 GMT

Getting Ready

← Older revision		Revision as of 19:45, 4 June 2026
(4 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	== Computing majors ==		== Computing majors ==
	If you are interested in computing, at ISU your options are Computer Science, Information Technology~~, Management Information Systems~~, Cyber & Security Studies. There is a fair amount of overlap, but roughly - (a) CS is mostly about making software and making it efficient, (b) IT is about managing computer systems and networks, (c~~) MIS is about managing both computer systems and personnel, (d~~) CSS at ISU is in the School of Criminology and has a large focus in criminology / social science. The most common job titles for those graduating from CS are - programmer/developer/software engineer of various kinds (web, database, network, systems, ...). If you do not want to be a programmer, consider whether CS, IT, ~~MIS~~, or ~~CSS~~ would best suit you.		If you are interested in computing, at ISU your options are Computer Science, Information Technology, Cyber & Security Studies, Computer and Electrical Engineering Technology. There is a fair amount of overlap, but roughly - (a) CS is mostly about making software and making it efficient, (b) IT is about managing computer systems and networks, (c) CSS at ISU is in the School of Criminology and has a large focus in criminology / social science, (d) CEET more involves the hardware / circuits. The most common job titles for those graduating from CS are - programmer/developer/software engineer of various kinds (web, database, network, systems, ...). If you do not want to be a programmer, consider whether CS, IT, CSS, or CEET would best suit you.

	== CS at ISU ==		== CS at ISU ==
Line 10:		Line 10:
	If you have done some work in computing before and want to do something extra to get ready for CS at ISU, here are a few things you can do.		If you have done some work in computing before and want to do something extra to get ready for CS at ISU, here are a few things you can do.

			* [[Programming Practice]]
	* http://code.org - go do some of their tutorials. These are mostly aimed at middle-school aged students, but is great experience and fun.		* http://code.org - go do some of their tutorials. These are mostly aimed at middle-school aged students, but is great experience and fun.
	* http://hackerrank.com - create an account and start doing basic programming problems. This site is great because your answer won't be accepted until it is 100% correct.
	* [https://www.youtube.com/playlist?list=PLCFNfZsc2MIByWxTX2Zjg0wJpk1YXbcQ8 CS 151] - check out Jeff Kinne's video lectures from CS 151, the first course in our major.
	* [https://www.youtube.com/playlist?list=PLXFP6J47Bp0fxKk5q6V_K2_3DkPIdGmMf AI] - video playlist from high school summer honors course at ISU from 2017.
	* Get a copy of Introduction to Algorithms (any edition) and start perusing it.		* Get a copy of Introduction to Algorithms (any edition) and start perusing it.
	* http://appinventor.mit.edu/explore/ - make apps for Android.		* http://appinventor.mit.edu/explore/ - make apps for Android.
	* See our [[Help and Getting Started]] page ~~and [http://cs.indstate.edu/info/learn.html Learn]~~.		* See our [[Help and Getting Started]] page.
	* Install linux on one of your home computers (Ubuntu and Mint are pretty easy to use). Note - do it on a computer that doesn't have any important data on it... You can also do this by first installing VirtualBox in your current operating system and then install linux inside of that.		* Install linux on one of your home computers (Ubuntu and Mint are pretty easy to use). Note - do it on a computer that doesn't have any important data on it... You can also do this by first installing VirtualBox or VMWare in your current operating system and then install linux inside of that.
	* Some key ideas in CS and examples -		* Some key ideas in CS and examples -
	** Algorithm - linear search vs. binary search, selection sort vs. merge sort, ~~euclid~~'s algorithm vs. trial division		** Algorithm - linear search vs. binary search, selection sort vs. merge sort, Euclid's algorithm vs. trial division
	** Proof - there are infinitely many primes, the halting problem is uncomputable, the square root of 2 is irrational, the sum of an arithmetic series [1 + 2 + ... + n = n*(n+1)/2]		** Proof - there are infinitely many primes, the halting problem is uncomputable, the square root of 2 is irrational, formula for the sum of an arithmetic series [1 + 2 + ... + n = n*(n+1)/2]
	** Data speeds - tape vs. hard disk drive vs. RAM vs. CPU cache vs. CPU registers		** Data speeds - tape vs. hard disk drive vs. RAM vs. CPU cache vs. CPU registers
	** Abstraction - operating system virtual memory, RAID, object-oriented programming, file system, any API, any programming language		** Abstraction - operating system virtual memory, RAID, object-oriented programming, file system, any API, any programming language
Line 34:		Line 32:
	** Drawing shapes - regular polygons, stars, fractals		** Drawing shapes - regular polygons, stars, fractals
	** Board game - tic tac toe, connect 4, chess, you name it		** Board game - tic tac toe, connect 4, chess, you name it
	** Calculator - with usual operations but also with your own ~~cutsom~~ ones		** Calculator - with usual operations but also with your own custom ones

	== Other Helpful Resources ==		== Other Helpful Resources ==

ISU Computer Science

Jkinne — Thu, 04 Jun 2026 19:39:07 GMT

More information

← Older revision		Revision as of 19:39, 4 June 2026
Line 17:		Line 17:
	* [[Procedures]]		* [[Procedures]]
	* [[FAQ]]		* [[FAQ]]
	* [[Labs and Office Hours]]
	* [[CS Help and Getting Started]]		* [[CS Help and Getting Started]]
	* [[Programming Practice]]		* [[Programming Practice]]

Programming and CS - Getting Started

Jkinne — Wed, 03 Jun 2026 02:07:24 GMT

Practice Programming Contest Problems

← Older revision		Revision as of 02:07, 3 June 2026
(2 intermediate revisions by the same user not shown)
Line 12:		Line 12:
	If you have a particular system in mind for purchase that you would like an opinion on, please feel free to contact one of the CS faculty members.		If you have a particular system in mind for purchase that you would like an opinion on, please feel free to contact one of the CS faculty members.

	University ~~requirements~~ are listed [https://~~www~~.~~indstate~~.~~edu~~/~~online~~/~~resources~~/~~students~~/~~technology~~-~~requirements~~ here] and are similar to that described above.		University recommendations are listed [https://indstate.teamdynamix.com/TDClient/1851/Portal/KB/Article/71665/Student-Laptop-Minimum-Specifications here] and are similar to that described above.

	=Getting Started Pages=		=Getting Started Pages=
	* [[Linux and CS Systems - Getting Started]]		* [[Linux and CS Systems - Getting Started]]
	* [[Handin\|Handin - The CS Assignment Handin System]]
	* [[Python Programming - Getting Started]]		* [[Python Programming - Getting Started]]
	* [[C Programming - Getting Started]]		* [[C Programming - Getting Started]]
Line 24:		Line 23:

	=Practice Programming Contest Problems=		=Practice Programming Contest Problems=
	~~These are problems with precisely defined correct output, so that you can submit your program to make sure it is 100% correct.~~		See [[Programming Practice]].

	* [~~http://www.hackerrank.com/ Hacker Rank] - very user-friendly, different programming languages available, different categories of questions~~
	* [~~https://open.kattis.com/problems~~ Practice ~~problems] at open.kattis.com (sort by difficulty or solved % to try the easiest ones first)~~
	* [http://cs.indstate.edu/acm/contests.html ISU ACM Club's Contest Problem page]
	* [http://cs.indstate.edu/~jkinne/Cpractice/ A few simple practice problems]~~, with solutions to some on the CS server. See the .txt files~~.

	= Source Control =		= Source Control =

CS accounts

Jkinne — Wed, 03 Jun 2026 02:02:42 GMT

Spring 2026

← Older revision		Revision as of 02:02, 3 June 2026
(10 intermediate revisions by the same user not shown)
Line 2:		Line 2:

	=Logging In=		=Logging In=
	The CS server is a Linux server. The primary ways you will login to the server is either (a) with a terminal (aka shell) that allows you to type text commands, or (b) with sftp to transfer files between your computer and the server. In either case, you need a username (aka login) and password. There are two types of accounts on the system - ISU portal accounts, and local accounts.		The CS server is a Linux server. The primary ways you will login to the server is either (a) with a terminal (aka shell) that allows you to type text commands, or (b) with an sftp program to transfer files between your computer and the server. In either case, you need a username (aka login) and password. There are two types of accounts on the system - ISU portal accounts, and local accounts.

	==ISU Portal Accounts==		==ISU Portal Accounts==
	Any student/faculty/staff who is involved in CS courses or programs (enrolled in a course, teaching a course, etc.) can login to cs.indstate.edu using their full ISU email address and portal password. The first time you login to the system, an account is created on the system that you can use. It will set your home directory on the system to <code>/home/SID@isuad.indstate.edu/</code> where <code>SID</code> is your portal id (aka sycamore id - for students it is the part before the @sycamores in your email address). After logging in, you can run the <code>pwd</code> command to see this.		Any student/faculty/staff who is involved in CS courses or programs (enrolled in a course, teaching a course, etc.) can login to cs.indstate.edu using their full ISU email address and portal password. The first time you login to the system, an account is created on the system that you can use. It will set your home directory on the system to <code>/home/SID@isuad.indstate.edu/</code> where <code>SID</code> is your portal id (aka sycamore id - for students it is the part before the @sycamores in your email address). After logging in, you can run the <code>pwd</code> command to see this.

	Note that there is not currently "finger information" about ISU portal account users. In fact, trying to run something like "finger jkinne@isuad.indstate.edu" will fail. Note that instructors of current courses can get a class list (aka roster) of accounts for their course; see below.		For those familiar with Linux already... Note that there is not currently "finger information" about ISU portal account users. In fact, trying to run something like "finger jkinne@isuad.indstate.edu" will fail. Note that instructors of current courses can get a class list (aka roster) of accounts for their course; see below.

	==Local Accounts==		==Local Accounts==
Line 19:		Line 19:
	ssh-keygen # create keys for logging in		ssh-keygen # create keys for logging in
	</pre>		</pre>
	You will then transfer the private key file (the one that does not end in .pub) to your local computer in the location for ssh keys.		You will then transfer the private key file (the one that does not end in .pub) to your local computer in the location for ssh keys. This varies depending on your operating system. On Linux and Mac OS, it will be in <code>~/.ssh</code>.

	= CS Server Policies =		= CS Server Policies =
Line 33:		Line 33:
	== Inactivity ==		== Inactivity ==
	Accounts that are not used for a period of 6 months will likely be locked as a security precaution. You can write to root@cs.indstate.edu to ask to have your account unlocked again.		Accounts that are not used for a period of 6 months will likely be locked as a security precaution. You can write to root@cs.indstate.edu to ask to have your account unlocked again.


	=Student Use and Course Account=		=Student Use and Course Account=
	For courses that are currently being offered, if the course uses the server, a class account is created that the instructor of the course can use if they like. This is explained with two examples: CS 151 Intro to Computer Science, and CS 473/573 Computer Networks.		For courses that are currently being offered, if the course uses the server, a class account is created that the instructor of the course can use if they like. This is explained in this section with two examples: CS 151 Intro to Computer Science, and CS 473/573 Computer Networks.

	==Course Account==		==Course Account==
Line 53:		Line 52:
	Inside the <code>~/private/</code> directory of the course account, there is also a <code>students</code> directory that has symbolic links to each of the student's course directories in the course. For example, if the course is cs151, and if the user jdoe12345@isuad.indstate.edu is a student in the course, then there will be a link <code>/home/cs151/private/students/jdoe12345@isuad.indstate.edu</code> that is a link to the cs151 directory for this student (<code>/home/jdoe12345@isuad.indstate.edu/cs151/</code>). The instructor for the course can quickly get into the students' directories for the course (but not their home directory) by going to the private/students/ directory and going from there.		Inside the <code>~/private/</code> directory of the course account, there is also a <code>students</code> directory that has symbolic links to each of the student's course directories in the course. For example, if the course is cs151, and if the user jdoe12345@isuad.indstate.edu is a student in the course, then there will be a link <code>/home/cs151/private/students/jdoe12345@isuad.indstate.edu</code> that is a link to the cs151 directory for this student (<code>/home/jdoe12345@isuad.indstate.edu/cs151/</code>). The instructor for the course can quickly get into the students' directories for the course (but not their home directory) by going to the private/students/ directory and going from there.

	The accounts for the instructors of the course are set so they can sudo as the course account. If the instructor of CS 151 uses the local account <code>jkinne</code> then this user can run the following command to get a shell running as the CS 151 course account: <code>sudo -u cs151 -i</code>		The accounts for the instructors of the course are set so they can sudo as the course account. If the instructor of CS 151 uses the local account <code>jkinne</code> then this user can run the following command to get a shell running as the CS 151 course account: <code>sudo -u cs151 -i</code>.
	Note that this only works for local accounts, and does not work for ISU Portal accounts (it might work for the jkinne local account but not for the jkinne@isuad.indstate.edu account).		Note that this only works for local accounts, and does not work for ISU Portal accounts (it might work for the jkinne local account but not for the jkinne@isuad.indstate.edu account).

Line 62:		Line 61:

	When the new semester starts (if the course is running in the new semester), the following in the <code>~/private</code> directory will be updated to be for the new term: classlist_brief.csv, classlist_full.csv, students directory (symbolic links to new semester's students).		When the new semester starts (if the course is running in the new semester), the following in the <code>~/private</code> directory will be updated to be for the new term: classlist_brief.csv, classlist_full.csv, students directory (symbolic links to new semester's students).

			==Assignments==
			Any directory within the course account can be used as an assignment. For example, suppose the account <code>cs151</code> contains a directory <code>h7</code>. This directory might have files for the students to use on the assignment; they can view these files by going to the directory <code>/home/cs151/h7/</code>.

			A student can "checkout" or "get" an assignment by running
			<pre>hw_get.py cs151 h7</pre>
			This will copy the <code>h7</code> directory that is in the <code>cs151</code> account into the <code>cs151</code> directory of the user that executes the command.

			An instructor can collect an assignment by running the script <code>hw_collect.py</code>. For the above example, the instructor would run: <code>hw_collect.py cs151 h7</code>. This will go into each student in the course's <code>cs151</code> directory and copy their h7 directory into <code>/home/cs151/private/submissions/h7/</code>. There will be a new directory in that submissions directory for the date and time the submissions were collected. For example, if the user jdoe12345@isuad.indstate.edu is in the cs151 course, then the contents of <code>/home/jdoe12345@isuad.indstate.edu/h7/</code> will be copied into the submission directory (inside of <code>/home/cs151/private/submissions/h7/</code>). The directory <code>/home/cs151/private/submissions/h7/</code> will have a symbolic link <code>latest</code> that is a pointer to the latest submission.

			There is a system in place that can be used for auto-checking the output of student programs. The instructor creates a file <code>.tests.json</code> inside of the assignment directory that has the test cases. The instructor will also need to create a correct working version of each program that can be run to get the "correct" results. The students will use the <code>hw_check.py</code> command to check their output. The instructor can also use the same command to check student submissions. You can get more details about how this works by logging into the system and running: <code>hw_check.py --help</code>.

	=Websites / Webservers=		=Websites / Webservers=
Line 79:		Line 89:
	==Node, Django, etc.==		==Node, Django, etc.==
	Node, Django, and many other web server frameworks can also be run off of the CS server. These generally will pick a port that they will run off of, and you run the main file for your server. Note that the Apache web server uses the "standard" ports (80 for http and 443 for https), so you cannot use those. If you want to run a Node, Django, or similar web server off of the CS server, you need to pick a port that isn't used for anything else. You should never pick a port number that is below 1024 and really should avoid port numbers below 10000. If you want to make sure to pick a port that will not interfere with anything, write to root@cs.indstate.edu. If you were to run your node web server with port 60000, then you would browse to it on the web at https://cs.indstate.edu:60000. Note that there is indeed normally a node server running on that particular port.		Node, Django, and many other web server frameworks can also be run off of the CS server. These generally will pick a port that they will run off of, and you run the main file for your server. Note that the Apache web server uses the "standard" ports (80 for http and 443 for https), so you cannot use those. If you want to run a Node, Django, or similar web server off of the CS server, you need to pick a port that isn't used for anything else. You should never pick a port number that is below 1024 and really should avoid port numbers below 10000. If you want to make sure to pick a port that will not interfere with anything, write to root@cs.indstate.edu. If you were to run your node web server with port 60000, then you would browse to it on the web at https://cs.indstate.edu:60000. Note that there is indeed normally a node server running on that particular port.

	~~=Assignments=~~
	Any directory within the course account can be used as an assignment. For example, suppose the account <code>cs151</code> contains a directory <code>h7</code>. This directory might have files for the students to use on the assignment; they can view these files by going to the directory <code>/home/cs151/h7/</code>.

	~~A student can "checkout" or "get" an assignment by running~~
	~~<pre>hw_get.py cs151 h7</pre>~~
	~~This will copy the <code>h7</code> directory that is in the <code>cs151</code> account into the <code>cs151</code> directory of the user that executes the command.~~

	An instructor can collect an assignment by running the script <code>hw_collect.py</code>. For the above example, the instructor would run: <code>hw_collect.py cs151 h7</code>. This will go into each student in the course's <code>cs151</code> directory and copy their h7 directory into <code>/home/cs151/private/submissions/h7/</code>. There will be a new directory in that submissions directory for the date and time the submissions were collected. For example, if the user jdoe12345@isuad.indstate.edu is in the cs151 course, then the contents of <code>/home/jdoe12345@isuad.indstate.edu/h7/</code> will be copied into the submission directory (inside of <code>/home/cs151/private/submissions/h7/</code>). The directory <code>/home/cs151/private/submissions/h7/</code> will have a symbolic link <code>latest</code> that is a pointer to the latest submission.

	There is a system in place that can be used for auto-checking the output of student programs. The instructor creates a file <code>.tests.json</code> inside of the assignment directory that has the test cases. The instructor will also need to create a correct working version of each program that can be run to get the "correct" results. The students will use the <code>hw_check.py</code> command to check their output. The instructor can also use the same comment to check student submissions. You can get more details about how this works by logging into the system and running: <code>hw_check.py --help</code>.

	=Spring 2026=		=Spring 2026=
	The following is the list of courses that are supported on the server for the ~~fall 2025~~, along with the instructor accounts (aka admin accounts) for each course.		The following is the list of courses that are supported on the server for the 2026 spring, along with the instructor accounts (aka admin accounts) for each course.
	<pre>		<pre>
	course,admin_accounts		course,admin_accounts

Email Lists

Jkinne — Wed, 03 Jun 2026 00:11:45 GMT

Maintenance

← Older revision		Revision as of 00:11, 3 June 2026
(4 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	The CS faculty maintain a variety of email lists used to send announcements and keep in touch with the CS students and faculty. Each is described briefly below~~. Click on the link to a list if you wish to subscribe to the list or modify your subscription, or send email to Jeff Kinne at jkinne@cs.indstate.edu~~.		The CS faculty maintain a variety of email lists used to send announcements and keep in touch with the CS students and faculty. Each is described briefly below.

	For those authorized to send email to the lists, you send email to the name of the list followed by @cs.indstate.edu. So to send email to the CS undergraduate students, you would compose a message to cs-ugrads@cs.indstate.edu. If you are not authorized to send a message to the list, it will be automatically ignored by the email system.		For those authorized to send email to the lists, you send email to the name of the list followed by @cs.indstate.edu. So to send email to the CS undergraduate students, you would compose a message to cs-ugrads@cs.indstate.edu. If you are not authorized to send a message to the list, it will be automatically ignored by the email system.
Line 14:		Line 14:

	== Jobs (cs-jobs) ==		== Jobs (cs-jobs) ==
	This email list is used to pass on potential job opportunities - internships, full time positions, etc. Current CS students and alumni are welcome to join the list to receive these notices. ~~Previously~~ job ~~notices were~~ sent to ~~the other email lists~~, ~~but going forward they will only be sent to~~ cs-jobs. '''~~This~~ is an opt-in list - you need to sign up for it.''' The list page is at http://cs.indstate.edu/mailman/listinfo/cs-jobs/		This email list is used to pass on potential job opportunities - internships, full time positions, etc. Current CS students and alumni are welcome to join the list to receive these notices. Oftentimes, job postings are sent to all of cs-grads, cs-ugrads, and cs-jobs. '''cs-jobs is an opt-in list - you need to sign up for it.''' The list page is at http://cs.indstate.edu/mailman/listinfo/cs-jobs/

	== Alumni (cs-alumni) ==		== Alumni (cs-alumni) ==
Line 20:		Line 20:

	== Faculty ==		== Faculty ==
	This email list is used to contact Computer Science faculty~~. The list is managed (not open to subscription requests)~~. The mailing list is cs-faculty.		This email list is used to contact Computer Science faculty. The mailing list is cs-faculty.

			== Graduate and Undergraduate Assistants ==
			This email list contains all CS students working for the department.

	== Maintenance ==		== Maintenance ==
Line 29:		Line 32:
	* cs-courses - mass removal of all from the previous term, mass subscription for all registered for the coming term. Update these starting a few weeks before the term, and about once per week until after the last day to add classes.		* cs-courses - mass removal of all from the previous term, mass subscription for all registered for the coming term. Update these starting a few weeks before the term, and about once per week until after the last day to add classes.
	* cs-faculty, cs-assistants - updated once per term or year as staffing and GA positions change.		* cs-faculty, cs-assistants - updated once per term or year as staffing and GA positions change.
	* ~~cs-chat,~~ cs-jobs - these are opt-in, so all that needs to be done is approving or denying subscription requests (approve any request from an @sycamores.indstate.edu or @indstate.edu email address).		* cs-jobs - these are opt-in, so all that needs to be done is approving or denying subscription requests (approve any request from an @sycamores.indstate.edu or @indstate.edu email address).
	You can get to the administrative interface from the links above. For removing all from a list, you can use scripts to do this, or you can copy/paste the entire membership list into excel, then copy/paste the email column into the "mass removal" form in the web interface.		You can get to the administrative interface from the links above. For removing all from a list, you can use scripts to do this, or you can copy/paste the entire membership list into excel, then copy/paste the email column into the "mass removal" form in the web interface.

Help and Getting Started

Jkinne — Mon, 01 Jun 2026 22:37:26 GMT

← Older revision		Revision as of 22:37, 1 June 2026
Line 1:		Line 1:
	* [[CS ~~Accounts and CS Lab Computers~~]]		* [[CS accounts]]
	* [[Email Lists]]		* [[Email Lists]]
	* [[Beginning Programming]]		* [[Beginning Programming]]