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.
This exercise is based on the code you wrote for exercise 1 to esubmit. That is, exercise 2 assumes you have a program which prompts for an integer and prints its cube:
Enter an integer: 4 The cube of 4 is 64If 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 a number is poor practice.
If necessary, log in to the campus VPN. You will not need to if you are logged in to the MSOE WiFi. Once you are connected,
You can resubmit as many times as you like. We will grade just your final submission. If you have troubles submitting your code by the due date, do email the code to your instructor and explain what your problem is. But the expectation is that you will submit via esubmit, and your instructor is likely to respond by asking you to show them what happens when you try to use esubmit.
Your solution to this exercise (unlike labs) 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 appears differently in esubmit. 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 - you don't need for this exercise!) and meet the design requirements in the writeup, you should get full credit on each assignment if you match the output.