- To understand the bitwise operators
- To use bitwise operators to complete tasks
- To understand ASCII
- Make sure all 4 les are in the same folder:
- Open a terminal / command prompt and navigate to the folder that all the les are in.
- Run the following command to see your grade for BitVector.java:
java -jar hw2checker.jar -g BitVector.java
- It should show all the test cases you are failing and give a 0/45 score.
- Implement one of the functions in BitVector.java and re-run step 3 until you get full credit for that part of BitVector.java.
Now complete all the other methods in each of the 3 les based on their comments. Run the veri er and autograder frequently to avoid errors and to make sure you are using only the allowed operations.
Note: We have included an Examples.java le which shows and explains examples of two methods similar to those used in your assignment, which may be useful if you get stuck or confused at any point.
- How to run the auto-grader & veri er
- Make sure that the hw2checker.jar le is in the same folder as your Bases.java, BitVector.java, and Operations.java les.
- Navigate to this folder in your command line.
- Run the desired command (see below).
Test all methods and verify that no banned operations are being used (all 3 les):
java -jar hw2checker.jar
Note: Your grade will be dependent on the output of the above command, as it will both test the output of your methods, and verify that you are not using banned operations. If you get stuck though, you can use some of the below commands to help you debug.
On Windows and Mac, you can also double click the hw2checker.jar in your le explorer to test and verify all 3 les. The results will be placed in a new le called gradeLog.txt. Any errors with compilation, in nite loops, or other runtime errors will be placed in a new le called errorLog.txt.
Test & verify all methods in a single le (using Bases.java). Useful for when you just want to look at one le at a time. For example:
java -jar hw2checker.jar -g Bases.java
Test all methods in a single le without running veri er (using Bases.java). This means that this will only run the unit tests, and will not check for the use of banned operations. Useful for when you just want to try and get something that works. For example:
java -jar hw2checker.jar -t Bases.java
Verify all methods in a single le without running tests (using Bases.java for example):
java -jar hw2checker.jar -v Bases.java
Any combination of les can also be graded, tested, or veri ed at the same time. For instance, Bases and
Operations can be graded simultaneously as follows:
java -jar hw2checker.jar -g Bases.java Operations.java
The grade the autograder gives you should be the same as the grade you get (unless you intentionally hardcode just the solutions or try to hack the autograder).
Please upload the following 3 les the \Homework 02″ assignment on Gradescope:
Download and test your submission to make sure you submitted the right les.
- Rules and Regulations
6.1 General Rules
- Starting with the assembly homeworks, any code you write must be meaningfully commented. You should comment your code in terms of the algorithm you are implementing; we all know what each line of code does.
- Although you may ask TAs for clari cation, you are ultimately responsible for what you submit. This means that (in the case of demos) you should come prepared to explain to the TA how any piece of code you submitted works, even if you copied it from the book or read about it on the internet.
- Please read the assignment in its entirety before asking questions.
- Please start assignments early, and ask for help early. Do not email us the night the assignment is due with questions.
- If you nd any problems with the assignment it would be greatly appreciated if you reported them to the author (which can be found at the top of the assignment). Announcements will be posted if the assignment changes.
6.2 Submission Conventions
- All les you submit for assignments in this course should have your name at the top of the le as a comment for any source code le, and somewhere in the le, near the top, for other les unless otherwise noted.
- When preparing your submission you may either submit the les individually to Canvas/Gradescope or you may submit an archive (zip or tar.gz only please) of the les (preferred). You can create an archive by right clicking on les and selecting the appropriate compress option on your system.
- If you choose to submit an archive please don’t zip up a folder with the les, only submit an archive of the les we want (see Deliverables).
- Do not submit compiled les, that is .class les for Java code and .o les for C code. Only submit the les we ask for in the assignment.
- Do not submit links to les. We will not grade assignments submitted this way as it is easy to change the les after the submission period ends.
6.3 Submission Guidelines
- You are responsible for turning in assignments on time. This includes allowing for unforeseen circum-stances. If you have an emergency let us know IN ADVANCE of the due time supplying documenta-tion (i.e. note from the dean, doctor’s note, etc). Extensions will only be granted to those who contact us in advance of the deadline and no extensions will be made after the due date.
- You are also responsible for ensuring that what you turned in is what you meant to turn in. After submitting you should be sure to download your submission into a brand new folder and test if it works. No excuses if you submit the wrong les, what you turn in is what we grade. In addition, your assignment must be turned in via Canvas/Gradescope. Under no circumstances whatsoever we will accept any email submission of an assignment. Note: if you were granted an extension you will still turn in the assignment over Canvas/Gradescope.
- There is a 6-hour grace period added to all assignments. You may submit your assignment without penalty up until 11:55PM, or with 25% penalty up until 5:55AM. So what you should take from this is not to start assignments on the last day and plan to submit right at 11:54AM. You alone are responsible for submitting your homework before the grace period begins or ends; neither Canvas/Gradescope, nor your aky internet are to blame if you are unable to submit because you banked on your computer working up until 11:54PM. The penalty for submitting during the grace period (25%) or after (no credit) is non-negotiable.
6.4 Syllabus Excerpt on Academic Misconduct
Academic misconduct is taken very seriously in this class. Quizzes, timed labs and the nal examination are individual work.
Homework assignments are collaborative, In addition many if not all homework assignments will be evaluated via demo or code review. During this evaluation, you will be expected to be able to explain every aspect of your submission. Homework assignments will also be examined using computer programs to nd evidence of unauthorized collaboration.
What is unauthorized collaboration? Each individual programming assignment should be coded by you. You may work with others, but each student should be turning in their own version of the assignment. Submissions that are essentially identical will receive a zero and will be sent to the Dean of Students’ O ce of Academic Integrity. Submissions that are copies that have been super cially modi ed to conceal that they are copies are also considered unauthorized collaboration.
You are expressly forbidden to supply a copy of your homework to another student via elec-tronic means. This includes simply e-mailing it to them so they can look at it. If you supply an electronic copy of your homework to another student and they are charged with copying, you will also be charged. This includes storing your code on any site which would allow other parties to obtain your code such as but not limited to public repositories (Github), pastebin, etc. If you would like to use version control, use github.gatech.edu
6.5 Is collaboration allowed?
Collaboration is allowed on a high level, meaning that you may discuss design points and concepts relevant to the homework with your peers, share algorithms and pseudo-code, as well as help each other debug code. What you shouldn’t be doing, however, is pair programming where you collaborate with each other on a single instance of the code. Furthermore, sending an electronic copy of your homework to another student for them to look at and gure out what is wrong with their code is not an acceptable way to help them, because it is frequently the case that the recipient will simply modify the code and submit it as their own. Consider instead using a screen-sharing collaboration app, such as http://webex.gatech.edu/, to help someone with debugging if you’re not in the same room.
Figure 1: Collaboration rules, explained colorfully