The goal of this exercise is to learn to use the assignment submittal
tool at esubmit.msoe.edu. You will use
this for most assignments this term as well as in some other courses. To
access esubmit from on campus, you simply go to the site. If you are
off campus you will need to log in to the campus VPN; see
here for
directions.
If you have not done so yet, complete exercise 1. That is, write
a program that prompts for and reads an integer and prints its cube.
If you have used a function like pow in your answer, change it to
simply multiply the value a few times. Using transcendental functions to
cube numbers is very inefficient and less precise.
Next, log in to esubmit.
If you are off campus, you will have to log in to the campus VPN as described above. If you are on campus (and logged in to the MSOE WiFi, you can connect directly.
Enter your campus username (without the @msoe.edu) and your
standard password.
On your home page, click on the name of the assignment, ex2esubmit.
On the assignment page, click on the Submit button.
Use the Choose File button to select your solution and click on Submit.
After a few seconds there will be two boxes. The first shows the output of compiling your code. It should have just the compilation command; if there is other text then your code had a compilation error. The second box shows any differences between your output and the expected output. Ideally this should be empty, but if you are seeing the right output just formatted differently, you can still get partial credit. Common formatting errors include printing an extra newline after the prompt for an integer or not printing a newline after printing the result.
You can resubmit as many times as you like. We will grade just your final submission. This means esubmit is also ideal when you simply have a question for your instructor: submit and then send a message saying you have submitted and asking your question.
Your solution to this exercise (unlike SPAs) will be graded for correctness only. Documentation and style will not be graded. Submit your own solution, but feel free to talk to other students for this exercise if you are having problems.
Pay close attention to how your instructor asks you to submit your solutions. Generally you will submit code here and not submit any code to Canvas; your instructor will be able to grade your solution on the esubmit site. But there are cases in which students are asked to submit Zip files, documents, and/or paper printouts, and these are needed because different instructors have different grading workflows. Read submission requirements twice, and ask if there are parts that are not clear. Incorrect submissions slow down grading significantly.
If at all possible, the expectation is that you will match the expected
output exactly. This includes writing complete text lines to the output.
In Java terms, that means using System.out.println instead of
System.out.print. Be sure to remove any debugging output. If you have
any differences shown - even if both outputs look the same - then
contact your instructor on removing those differences if you cannot find
things to fix on your own.
A challenge you will face is that output sometimes appears slightly differently in esubmit than on your computer. Output that appears on multiple lines on your computer often appears on a single line in esubmit. This is because of the differences between typing text using your keyboard and reading the input from a file. You can ignore these differences. A writeup will give a sample session, and if you match the appearance of that session when you run the program on your machine, it should be fine in esubmit.
There are several advantages to using esubmit. A key one is the immediate feedback. Assuming you follow the coding standard (when appropriate) and meet the design requirements in the writeup, you should get full credit by simply matching the output.