Just the FAQs

Here are a bunch of questions that you might find useful. We will update them over the course of the semester, and if you have any suggestion hit the Contact button above and send them along

First Login

If you do not have an EGRaccount, then you should be able to login to the EGR laboratory computers using your MSU id and the PID as a password. Remember to use a capital A when typing in your PID

Change/reset password

Change Password : You have to take your ID and go to the DECS office, 1325 EB. It is important to change your password to something other than your PID .

How should I set up to do work at home?

Note: A lot of this is discussed in videos now on the first week page

There are many choices, going from easy to hard.
  1. Work in the labs. OK, that' isn't at home but it is a good choice anyway.
  2. Use the x2go application. x2go is a way to log into an EGR server from anywhere with a good network connection and get, local to your home screen, a window with the lab machine environment. The whole environment: compiler, editor, mounting home directory, everything. DECS provides a great link on how to get your x2go setup running on your local machine: https://www.egr.msu.edu/decs/help-support/how-to/x2go
  3. Go command line. You can skip all the fancy environment stuff and just run everything out of a terminal window. Even in this scenario you can do it one of two ways:
    • Run on the server. If you follow these directions you can ssh into a terminal server at EGR. All you get is a raw terminal this way, but from the terminal you can run the compiler and a non-graphical (terminal oriented) editor. Basically:
      • Get ssh (everybody has it but windows, follow directions above)
      • open a terminal
      • type ssh yourname@byron.cse.msu.edu (hey, yourname is what your CSE login is, not the string "yourname").
      • You're in. See command line below for using the terminal.

Lab Rules & Info

  1. You can miss two. Labs do not count toward your grade, but they can hurt you. You can miss two labs for any reason you like (from true emergency to oversleeping). However, after two absences you lose 0.5 a point of your final gradepoint . So show up to your scheduled lab. For the 730 students, you can also miss two but the TAs will look each week at what you turn in for the labs. If they deem it insufficient for "good faith effort", you will not get credit.
  2. Go to your own lab. . If you signed up for a section, that that is the lab you must attend.
    • If you want to change sections, go to piazza and work it there. No other way as the class is almost always full.
  3. Show up on time. . If you are late, then you will be counted absent. I have informed the TAs to do this, so if you have a problem with that you need to see me.
  4. Labs are done in pairs during your lab time. . You cannot come to lab with the lab "done". You must do the lab during your schedule lab time. One of the goals of the lab is to foster collaboration, and you can't collaborate if you do the lab by yourself.
  5. I was marked absent but did attend a lab . Lab attendance is marked at the end of each lab session (for 730, after you labs are due) on D2L. Check it that week . Mistakes from months ago cannot be checked; no one will remember. Check it each week on D2L and get it fixed then.

Project Rules & Info

  1. On time. You turn projects in via Mimir . This is a web page based turn-in program testing site. Each project has a due date. If you turn it on time, you can get full credit. If you are late by 1 day or less, Mimir will accept your code but with a 50% penalty (you lose 1/2 your points you earned via the tests). After that, there is no option to turn in the project.
  2. Compile. The project you turn in must compile. If it doesn't compile then it cannot be graded and you will receive a very small number of points. The TAs job is not to "fix" your program so it compiles. One semicolon, one poorly placed comment, and all your work is for nothing. Check that your project compiles.
    • Your project may compile somewhere else (say, on visual studio which is a particularly troublesome compiler) but that doesn't matter. It needs to compile on Mimir or it doesn't compile.
  3. On your own. Projects are homework, they are to be done on your own. Labs are a collaboration opportunity, but for projects you should write your own code. You can talk "generally" about code, but don't copy or share code.
    • We compare every project against every other project using a sophisticated checker. The checker (called MOSS out of Stanford, look it up) can "see" through variable name changes, moving of lines etc. It is very good.
    • If you copy code, you cheated. However, people are also surprised to hear that if you gave code, you also cheated. Don't share your code!


Here is some info about Mimir that might help you as you move forward:

What's my grade

How to Study for the Exams

I get asked a lot of questions about the exams. Here are some answers:

C++ info

Unfortunately there are lots of ways to get C++ depending on your operating system. Furthermore, there are lots of versions of C++ and we have some rather specific requirements as we are doing C++11. Finally, as we grade your projects there are limits to our ability to deal with all these possibilities. Read more below

Linux Stuff

Honors Credit

We have some rules about how the honors credit works for CSE232. Take a look at this document for the rules on Honors Projects

DECS help guide

DECS, the Division of Engineering and Computing Services, is responsible for the upkeep of the lab, the lab machines and its software. They provide a lovely FAQ of their own. Please see https://www.egr.msu.edu/decs/help-support/how-to