Difference between revisions of "Unix Lab and Help"

From Computer Science
Jump to: navigation, search
(Unix Lab Hours and Help)
 
(52 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
'''Note - CS has moved from Root Hall to Myers Technology Center. We do NOT have our labs up and running yet, and we do not know if they'll be running this term or not. We'll send an announcement when there is more to say.'''
 +
 
Note - if you are looking for help in Math courses, see the [http://www.indstate.edu/cas/mathcs/mathematics-tutoring Math tutoring] information on the department webpage.
 
Note - if you are looking for help in Math courses, see the [http://www.indstate.edu/cas/mathcs/mathematics-tutoring Math tutoring] information on the department webpage.
  
Room A-017 in Root Hall is used primarily for courses, with 36 Linux PCs available for student use during lecture and lab time. Room A-015, the "Unix Lab", has 12 Linux PCs and additional seating for those with laptops, and also has a couch, microwave, and coffee maker. Students are encouraged to work on assignments and projects in the Unix lab, and are free to socialize as long as other students are not distracted.
+
Rooms A-017 and A-019 in Root Hall are used primarily for courses, with 36 Linux PCs available in each for student use during lecture and lab time. Room A-015, the "Unix Lab", has 12 Linux PCs and additional seating for those with laptops, and also has a couch, microwave, and coffee maker. Students are encouraged to work on assignments and projects in the Unix lab, and are free to socialize as long as other students are not distracted.
  
See the [http://cs.indstate.edu/info/people.php CS People Page] for graduate and undergraduate assistants who might be in the lab. See also the [http://cs.indstate.edu/acm/ ACM Page] for the ACM officers who might be in the lab.
+
See [[ISU CS People]] for graduate and undergraduate assistants who might be in the lab, and see [http://cs.indstate.edu/index.php#lab_hours the CS homepage] for who is currently on duty. See also the [http://cs.indstate.edu/acm/ ACM Page] for the ACM officers who might be in the lab.
 +
 
 +
'''Covid''' The 2021 fall term will start with the lab being open for use - both in person and online.  We may change this depending on how the covid situation changes.  To help with contact tracing, please login to one of the unix lab machines any time you come to the lab.  If any of the lab staff contract covid, we will use the login history to identify who needs to be contacted.  Please do the same - if you contract covid please reach out to those who you were in extended contact with (including instructors and lab assistants).
  
 
== Unix Lab Hours and Help ==
 
== Unix Lab Hours and Help ==
The Unix lab is staffed by lab assistants so that it can remain open during most business hours. Each lab assistant makes sure to stay up to date on a few of the CS courses, so that students from the course can come to ask questions when that lab assistant is on duty.
+
The Unix lab is staffed by lab assistants so that it can remain open at least a few morning, afternoon, and evening hours most days. Each lab assistant makes sure to stay up to date on a few of the CS courses, so that students from the course can come to ask questions when that lab assistant is on duty.
  
'''Open Hours'''  The calendar below shows (will be updated soon to show) who is on duty. The lab is typically open during the fall and spring semesters during most business hours.  To see who is on duty, see [https://calendar.google.com/calendar/embed?src=0n4d71upnps2v0kpdt5a2qlsb0%40group.calendar.google.com&ctz=America%2FNew_York&mode=WEEK the lab google calendar].
+
'''Open Hours'''  The [http://cs.indstate.edu/index.php#lab_hours CS homepage] shows who is currently on duty and the hours the lab is normally open.
 +
 
 +
'''Study week / exams''' The lab is normally open during study week (the last week of classes for the term) but is ''not'' open during exam week.
  
 
'''Who Covers My Course'''  See [[ISU_CS_People#CS_Departmental_Graduate_Assistants|People]] for which lab assistants can help with which courses. All lab assistants can help with CS 101, 151, 201, 256, 202, 500. For other courses you can ask but the lab assistant might not be able to help you.
 
'''Who Covers My Course'''  See [[ISU_CS_People#CS_Departmental_Graduate_Assistants|People]] for which lab assistants can help with which courses. All lab assistants can help with CS 101, 151, 201, 256, 202, 500. For other courses you can ask but the lab assistant might not be able to help you.
Line 16: Line 22:
 
== Unix Lab Policies ==
 
== Unix Lab Policies ==
 
Here are a few do's and don't's for those using the CS lab and those working in the lab...
 
Here are a few do's and don't's for those using the CS lab and those working in the lab...
 
 
* '''Lab attendance''' - if your instructor asks you to go to the unix lab for credit, they will let you know what they want you to do. One possibility is that they would ask you to say hello to the lab assistant on duty and ask the lab assistant to log your attendence. In this case you need to login to one of the computers with your cs class account (cs15100, or whatever your cs class account is) to show the lab assistant who you are. Your instructor may ask you to have a brief conversation with the lab assistant, or speak about a particular topic.
 
* '''Lab attendance''' - if your instructor asks you to go to the unix lab for credit, they will let you know what they want you to do. One possibility is that they would ask you to say hello to the lab assistant on duty and ask the lab assistant to log your attendence. In this case you need to login to one of the computers with your cs class account (cs15100, or whatever your cs class account is) to show the lab assistant who you are. Your instructor may ask you to have a brief conversation with the lab assistant, or speak about a particular topic.
* '''CS 101 versus CS 151''' - CS 151 is the first course in the CS major and is required for IT majors. Most students are prepared to take CS 151 - the main requirements are "maturity" (will do assigned work) and basic computer skills. For those who find they are under-prepared or not ready, talk to your instructor or the director of CS about switching to CS 101. Students who "have no clue" or "are completely lost" by the second or third week might consider switching to CS 101.
+
* '''Food''' - <s>be reasonable. Don't leave crumbs, don't spill drinks (you break it, you buy it). If you make a mess clean it up. Leave the lab in a state that is better than or equal to when you arrived.</s> Those visiting the lab should refrain from eating or drinking in the lab until further notice.  Lab assistants can eat/drink when there are only lab assistants in the lab.
* '''Food''' - be reasonable. Don't leave crumbs, don't spill drinks (you break it, you buy it). If you make a mess clean it up. Leave the lab in a state that is better than or equal to when you arrived.
 
 
* '''Working together''' - each instructor has a different policy on whether students are allowed to work together on assignments. It is your responsibility to know your instructor's policy.
 
* '''Working together''' - each instructor has a different policy on whether students are allowed to work together on assignments. It is your responsibility to know your instructor's policy.
 
* '''Lab Assistants''' should ''never'' take the keyboard and type for someone they are helping. Lab assistants shoud always be respectful of people asking questions, no matter how basic and simple. Try to remember when you didn't know much, or think of some relative who is computer illiterate and think how you'd explain things to them.
 
* '''Lab Assistants''' should ''never'' take the keyboard and type for someone they are helping. Lab assistants shoud always be respectful of people asking questions, no matter how basic and simple. Try to remember when you didn't know much, or think of some relative who is computer illiterate and think how you'd explain things to them.
* If a student clearly is not prepared to even begin an assignment, lab assistants should suggest some starting point. For example, suppose a the student clearly doesn't know how to copy files, compile programs, or get rid of syntax errors, and they are asking for help on an assignment to make a prime tester program. The lab assistant would suggest that they first start with a "hello world" program that doesn't do anything.
+
* If a student clearly is not prepared to even begin an assignment, lab assistants should suggest some starting point. For example, suppose the student clearly doesn't know how to copy files, compile programs, or get rid of syntax errors, and they are asking for help on an assignment to make a prime tester program. The lab assistant would suggest that they first start with a "hello world" program that doesn't do anything.
 
* Lab assistants ''are not'' responsible for teaching material to students. If you are a student who skips classes and misses material, you will have to read and catch up mostly on your own, and only ask the lab assistants to clarify your understanding.
 
* Lab assistants ''are not'' responsible for teaching material to students. If you are a student who skips classes and misses material, you will have to read and catch up mostly on your own, and only ask the lab assistants to clarify your understanding.
* '''Working together policies''' For CS 151, don't sit at a computer together and work together; it is okay to talk about. For other courses, talk to your instructor and see the next note.
+
* '''Rule of thumb''' for students... You should be able to delete what you worked on in the lab, start over from scratch, and do it on your own without help from friends or lab assistants. If you cannot do that, then it isn't your work and you shouldn't turn it in. Students, don't ask questions like "can you explain loops to me". Do ask questions like "here's a program with a loop to add up the first 10 odd numbers, is it right that I would change ______ to make it do the evens between 100 and 200". Or, "here is the directory where my instructor keeps class files, could you explain ____ file that has loops in it".
* '''Rule of thumb''' for students... You should be able to delete what you worked on in the lab, start over from scratch, and do it on your own without help from friends or lab assistants. If you cannot do that, then it isn't your work and you shouldn't turn it in.
+
* '''Coding style''' Your code should follow good programming style. Each instructor may have slightly different expectations (in particular depending on the programming language). By default you should follow  [[Programming Style - Generic]].
Students, don't ask questions like "can you explain loops to me". Do ask questions like "here's a program with a loop to add up the first 10 odd numbers, is it right that I would change ______ to make it do the evens between 100 and 200". Or, "here is the directory where my instructor keeps class files, could you explain ____ file that has loops in it".
+
* '''Card swipe''' By default, CS students working for the department and CS faculty have their Id numbers added to the card swipe lock for the unix lab. Others who think they would need access to the lab when it is not normally open should contact the CS systems administrator.
* '''Coding style''' The CS group by default requires/endorses XYZ style. ''To be coordinated with Steve Baker and Geoff Exoo, check back later. Probably: 2 spaces for tabbing, blank lines ..., camelcase or _, ... Note - Aaron suggests rc files for emacs and vim that can shared with people ...''
 
* '''Card swipe''' By default, CS students working for the department and CS faculty have their Id numbers added to the card swipe lock for the unix lab. Others who think they would need access to the lab when it is not normally open should contact the director of CS.
 
  
 
== Lab Assistant Duties ==
 
== Lab Assistant Duties ==
 
=== All ===
 
=== All ===
 
All lab assistants (whether grad or undergrad) have the following duties.
 
All lab assistants (whether grad or undergrad) have the following duties.
 
 
* Mondays 3pm - lab meeting.
 
* Mondays 3pm - lab meeting.
 
* Show up when you are on duty (at least 5 minutes early).
 
* Show up when you are on duty (at least 5 minutes early).
* Reply to emails from department faculty and staff (mostly director of CS and department administrative assistant) promptly (within 1/2 a day, say).
+
* Reply to emails from department faculty and staff promptly (within 1/2 a day, say).
 
* Spend 30 minutes per week cleaning the unix lab. A schedule is created at the beginning of the term of what you are responsible for cleaning each week.
 
* Spend 30 minutes per week cleaning the unix lab. A schedule is created at the beginning of the term of what you are responsible for cleaning each week.
 
* Be on campus from the first day of classes through the last day of classes.
 
* Be on campus from the first day of classes through the last day of classes.
* All lab assistants should be able to help students with CS 101, 151, 170, 201, 202. If you need to refresh any of the content, use some of your lab time when there are no students needing help, to refresh the content from those classes (C and C++ programming, html/css and javascript, basic data structures and algorithms).
+
* All lab assistants should be able to help students with CS 101, 151, 201, 256, 202, 500, 501. If you need to refresh any of the content, use some of your lab time when there are no students needing help, to refresh the content from those classes (Python and C programming, data structures and algorithms).
* Complete any task asked of you by the CS faculty, department chairperson, or department administrative assistant.
+
* Complete any task asked of you by the CS faculty or department staff.
* Help with programming review sessions when your schedule allows.
+
* Help with programming review sessions when asked.
* Available to help with the CS website.
+
* Available to help with the CS website or other administrative tasks.
  
 
=== GAs ===
 
=== GAs ===
Line 48: Line 49:
  
 
* Be on campus through the end of exams.
 
* Be on campus through the end of exams.
* Finish grading within 3 days of receiving it (and to it how the faculty ask you to).
+
* Finish grading within 3 days of receiving it (and do it how the faculty ask you to).
 
* Look for cheating in the assignments you grade - either copied from the internet or from other students. It is suspicious if someone with low quiz/exam grades has code that is too good, or if a student is using something that wasn't taught in class.
 
* Look for cheating in the assignments you grade - either copied from the internet or from other students. It is suspicious if someone with low quiz/exam grades has code that is too good, or if a student is using something that wasn't taught in class.
* You are scheduled to be in the lab 7 hours per week. Each of your class assignments (as listed on the [http://cs.indstate.edu/info/people.php people page]) is for 6.5 hours of grading or other work for that faculty member per week. If the faculty member has not given you grading work to do, then use your 6.5 hours to stay up to date on assignments and content in the course. If you finish that, then spend some extra time in the unix lab.
+
* You are scheduled to be in the lab 10 hours per week. Each of your class assignments (as listed on [[ISU CS People]]) is for 10 hours of grading or other work for that faculty member per week. If the faculty member has not given you grading work to do, then use your 10 hours to stay up to date on assignments and content in the courses. If you finish that, then spend some extra time in the unix lab.
 
* Attend any events and complete any training required of GAs by the College of Graduate and Professional Studies.
 
* Attend any events and complete any training required of GAs by the College of Graduate and Professional Studies.
 
* Help with the annual programming contest(s).
 
* Help with the annual programming contest(s).
* Be available to help with the department's homecoming table on the Saturday of homecoming (typically mid-October).
+
* Other duties as assigned.

Latest revision as of 01:31, 10 August 2024

Note - CS has moved from Root Hall to Myers Technology Center. We do NOT have our labs up and running yet, and we do not know if they'll be running this term or not. We'll send an announcement when there is more to say.

Note - if you are looking for help in Math courses, see the Math tutoring information on the department webpage.

Rooms A-017 and A-019 in Root Hall are used primarily for courses, with 36 Linux PCs available in each for student use during lecture and lab time. Room A-015, the "Unix Lab", has 12 Linux PCs and additional seating for those with laptops, and also has a couch, microwave, and coffee maker. Students are encouraged to work on assignments and projects in the Unix lab, and are free to socialize as long as other students are not distracted.

See ISU CS People for graduate and undergraduate assistants who might be in the lab, and see the CS homepage for who is currently on duty. See also the ACM Page for the ACM officers who might be in the lab.

Covid The 2021 fall term will start with the lab being open for use - both in person and online. We may change this depending on how the covid situation changes. To help with contact tracing, please login to one of the unix lab machines any time you come to the lab. If any of the lab staff contract covid, we will use the login history to identify who needs to be contacted. Please do the same - if you contract covid please reach out to those who you were in extended contact with (including instructors and lab assistants).

Unix Lab Hours and Help

The Unix lab is staffed by lab assistants so that it can remain open at least a few morning, afternoon, and evening hours most days. Each lab assistant makes sure to stay up to date on a few of the CS courses, so that students from the course can come to ask questions when that lab assistant is on duty.

Open Hours The CS homepage shows who is currently on duty and the hours the lab is normally open.

Study week / exams The lab is normally open during study week (the last week of classes for the term) but is not open during exam week.

Who Covers My Course See People for which lab assistants can help with which courses. All lab assistants can help with CS 101, 151, 201, 256, 202, 500. For other courses you can ask but the lab assistant might not be able to help you.

GA duties Most GAs are instructors or graders for half of their 20 hours per week, and schedule 10 hours per week in the lab for the rest of their hours. The 10 hours in the lab is divided into 8 "general purpose" hours and 2 hours of problem/recitation.

Unix Lab Policies

Here are a few do's and don't's for those using the CS lab and those working in the lab...

  • Lab attendance - if your instructor asks you to go to the unix lab for credit, they will let you know what they want you to do. One possibility is that they would ask you to say hello to the lab assistant on duty and ask the lab assistant to log your attendence. In this case you need to login to one of the computers with your cs class account (cs15100, or whatever your cs class account is) to show the lab assistant who you are. Your instructor may ask you to have a brief conversation with the lab assistant, or speak about a particular topic.
  • Food - be reasonable. Don't leave crumbs, don't spill drinks (you break it, you buy it). If you make a mess clean it up. Leave the lab in a state that is better than or equal to when you arrived. Those visiting the lab should refrain from eating or drinking in the lab until further notice. Lab assistants can eat/drink when there are only lab assistants in the lab.
  • Working together - each instructor has a different policy on whether students are allowed to work together on assignments. It is your responsibility to know your instructor's policy.
  • Lab Assistants should never take the keyboard and type for someone they are helping. Lab assistants shoud always be respectful of people asking questions, no matter how basic and simple. Try to remember when you didn't know much, or think of some relative who is computer illiterate and think how you'd explain things to them.
  • If a student clearly is not prepared to even begin an assignment, lab assistants should suggest some starting point. For example, suppose the student clearly doesn't know how to copy files, compile programs, or get rid of syntax errors, and they are asking for help on an assignment to make a prime tester program. The lab assistant would suggest that they first start with a "hello world" program that doesn't do anything.
  • Lab assistants are not responsible for teaching material to students. If you are a student who skips classes and misses material, you will have to read and catch up mostly on your own, and only ask the lab assistants to clarify your understanding.
  • Rule of thumb for students... You should be able to delete what you worked on in the lab, start over from scratch, and do it on your own without help from friends or lab assistants. If you cannot do that, then it isn't your work and you shouldn't turn it in. Students, don't ask questions like "can you explain loops to me". Do ask questions like "here's a program with a loop to add up the first 10 odd numbers, is it right that I would change ______ to make it do the evens between 100 and 200". Or, "here is the directory where my instructor keeps class files, could you explain ____ file that has loops in it".
  • Coding style Your code should follow good programming style. Each instructor may have slightly different expectations (in particular depending on the programming language). By default you should follow Programming Style - Generic.
  • Card swipe By default, CS students working for the department and CS faculty have their Id numbers added to the card swipe lock for the unix lab. Others who think they would need access to the lab when it is not normally open should contact the CS systems administrator.

Lab Assistant Duties

All

All lab assistants (whether grad or undergrad) have the following duties.

  • Mondays 3pm - lab meeting.
  • Show up when you are on duty (at least 5 minutes early).
  • Reply to emails from department faculty and staff promptly (within 1/2 a day, say).
  • Spend 30 minutes per week cleaning the unix lab. A schedule is created at the beginning of the term of what you are responsible for cleaning each week.
  • Be on campus from the first day of classes through the last day of classes.
  • All lab assistants should be able to help students with CS 101, 151, 201, 256, 202, 500, 501. If you need to refresh any of the content, use some of your lab time when there are no students needing help, to refresh the content from those classes (Python and C programming, data structures and algorithms).
  • Complete any task asked of you by the CS faculty or department staff.
  • Help with programming review sessions when asked.
  • Available to help with the CS website or other administrative tasks.

GAs

Graduate assistants have the following additional duties.

  • Be on campus through the end of exams.
  • Finish grading within 3 days of receiving it (and do it how the faculty ask you to).
  • Look for cheating in the assignments you grade - either copied from the internet or from other students. It is suspicious if someone with low quiz/exam grades has code that is too good, or if a student is using something that wasn't taught in class.
  • You are scheduled to be in the lab 10 hours per week. Each of your class assignments (as listed on ISU CS People) is for 10 hours of grading or other work for that faculty member per week. If the faculty member has not given you grading work to do, then use your 10 hours to stay up to date on assignments and content in the courses. If you finish that, then spend some extra time in the unix lab.
  • Attend any events and complete any training required of GAs by the College of Graduate and Professional Studies.
  • Help with the annual programming contest(s).
  • Other duties as assigned.