cs101-F2019-practical7-starter

Table of Contents

• Table of Contents
• Introduction
• Continuous Learning
• System Commands
  • Using Docker
  • Using Gradle
• Expected Program Output
• Automated Checks with GatorGrader
• Downloading Project Updates
• Using Travis CI
• System Requirements
• Reporting Problems
• Receiving Assistance
• Project Assessment

Introduction

This assignment requires a programmer to implement and test a benchmarking framework that supports the empirical evaluation of BubbleSort, InsertionSort, and QuickSort. More details about the sorting algorithms are provided in the discussion of array sorting in Section 3.1.2 of the textbook. You can learn about experimental studies by reading the content in Sections 4.1 through 4.3. Please note that this assignment will also require you to read and use Java classes that contain a test suite, as explained in Section 1.9. As verified by Checkstyle, the source code for all of the Java source code files must adhere to all of the requirements in the Google Java Style Guide.

The source code in the submitted Java source code files must also pass additional tests set by the GatorGrader tool. For instance, GatorGrader will check to ensure that Experiment and RunCampaign have println statements that can produce the output from running a campaign of experiments. Gradle will also run a JUnit test suite that will perform many checks on your implementation of the Java classes. More details about the GatorGrader checks are included later in this document and in the assignment sheet.

Continuous Learning

If you have not done so already, please read all of the relevant GitHub Guides that explain how to use many of the features that GitHub provides. In particular, please make sure that you have read the following GitHub guides: Mastering Markdown, Hello World, and Documenting Your Projects on GitHub. Each of these guides will help you to understand how to use both GitHub and GitHub Classroom.

Students who want to learn more about how to use Docker should review the Docker Documentation. Students are also encouraged to review the documentation for their text editor, which is available for text editors like Atom and VS Code. You should also review the Git documentation to learn more about how to use the Git command-line client. In addition to talking with the instructor and technical leader for your course, students are encouraged to search StackOverflow for answers to their technical questions.

To do well on this assignment, you should also review Chapter 3 of the course textbook, paying close attention to Sections 3.1 and 3.6 and the source code on page 111. Also, you should read the content in Sections 4.1 through 4.3, focusing on the order of growth for a logarithmic function, as shown in Figure 4.4. Please see the course instructor or one of the student technical leaders if you have questions about any of these reading assignments.

System Commands

This project invites students to enter system commands into a terminal window. This assignment uses Docker to deliver programs, such as gradle and the source code and packages needed to run GatorGrader, to a students' computer, thereby eliminating the need for a programmer to install them on their development workstation. Individuals who do not want to install Docker can optionally install of the programs mentioned in the Project Requirements section of this document.

Using Docker

Once you have installed Docker Desktop, you can use the following docker run command to start gradle grade as a containerized application, using the DockaGator Docker image available on DockerHub.

docker run --rm --name dockagator \
  -v "$(pwd)":/project \
  -v "$HOME/.dockagator":/root/.local/share \
  gatoreducator/dockagator

The aforementioned command will use "$(pwd)" (i.e., the current directory) as the project directory and "$HOME/.dockagator" as the cached GatorGrader directory. Please note that both of these directories must exist, although only the project directory must contain something. Generally, the project directory should contain the source code and technical writing of this assignment, as provided to a student through GitHub. Additionally, the cache directory should not contain anything other than directories and programs created by DockaGator, thus ensuring that they are not otherwise overwritten during the completion of the assignment. To ensure that the previous command will work correctly, you should create the cache directory by running the command mkdir $HOME/.dockagator. If the above docker run command does not work correctly on the Windows operating system, you may need to instead run the following command to work around limitations in the terminal window:

docker run --rm --name dockagator \
  -v "$(pwd):/project" \
  -v "$HOME/.dockagator:/root/.local/share" \
  gatoreducator/dockagator

If that Docker command does not work correctly, then you should first consider writing the command on a single line in your terminal window and then replacing $(pwd) and $HOME with the fully qualified name of the directory that those variables represent. Students who are stuck on this step should explain to the course instructor what they have already tried and what challenges they currently face.

Here are some additional commands that you may need to run when using Docker:

• docker info: display information about how Docker runs on your workstation
• docker images: show the Docker images installed on your workstation
• docker container list: list the active images running on your workstation
• docker system prune: remove many types of "dangling" components from your workstation
• docker image prune: remove all "dangling" docker images from your workstation
• docker container prune: remove all stopped docker containers from your workstation
• docker rmi $(docker images -q) --force: remove all docker images from your workstation

Using Gradle

Since the above docker run command uses a Docker image that, by default, runs gradle grade and then exits the Docker container, you may want to instead run the following command so that you enter an "interactive terminal" that will allow you to repeatedly run commands within the Docker container.

docker run -it --rm --name dockagator \
  -v "$(pwd)":/project \
  -v "$HOME/.dockagator":/root/.local/share \
  gatoreducator/dockagator /bin/bash

Once you have typed this command, you can use the GatorGrader tool in the Docker container by typing the command gradle grade in your terminal. Running this command will produce a lot of output that you should carefully inspect. If GatorGrader's output shows that there are no mistakes in the assignment, then your source code and writing are passing all of the automated baseline checks. However, if the output indicates that there are mistakes, then you will need to understand what they are and then try to fix them.

You can also complete several important Java programming tasks by using the gradle tool. For instance, you can compile (i.e., create bytecode from the program's source code if it is correct) the program using the command gradle build. Here are some other commands that you can type:

• gradle grade: run the GatorGrader tool to check your work
• gradle clean: clean the project of all the derived files
• gradle check: check the quality of the code using Checkstyle
• gradle build: create the bytecode from the Java source code
• gradle run: run the Java program in the command-line
• gradle cleanTest: clean the JUnit test suite of derived files
• gradle test: run the JUnit test suite and display the results
• gradle tasks: display details about the Gradle system

To run one of these commands, you must be in the main (i.e., "home base") directory for this assignment where the build.gradle file is located.

Expected Program Output

Typing the command gradle run in the terminal window produces the following output for the instructor's version of practicalsix.experiment.Experiment. Critically, the timing values and order of growth ratios may be different when you run the experiment on your own computer. If you are finding that it is difficult to determine the likely worst-case time complexity based on the computed growth ratios, then please consider running the experiment for more campaigns and with larger inputs. With that said, be careful to consider that certain algorithm(s) may require a long time to properly execute. Also, please note that this laboratory assignment invites you to run a comprehensive JUnit test suite of multiple Java classes in multiple packages. While this test suite does not produce any output, you should carefully inspect its tests so that you understand their strategy.

> Configure project :
Configured GatorGradle 0.4.4

> Task :run
Starting a campaign of experiments with BubbleSort ...
  Running round 0 with input size 250
  Running round 1 with input size 500
  Running round 2 with input size 1000
  Running round 3 with input size 2000
  Running round 4 with input size 4000
  Running round 5 with input size 8000
  Running round 6 with input size 16000
  Running round 7 with input size 32000
... Finishing a campaign of experiments with BubbleSort

Results of an experiment campaign with BubbleSort:

Size (#)        Timing (ms)     Ratio (#)
250             2               0
500             2               1
1000            2               1
2000            12              6
4000            27              2
8000            120             4
16000           530             4
32000           2277            4

Starting a campaign of experiments with InsertionSort ...
  Running round 0 with input size 250
  Running round 1 with input size 500
  Running round 2 with input size 1000
  Running round 3 with input size 2000
  Running round 4 with input size 4000
  Running round 5 with input size 8000
  Running round 6 with input size 16000
  Running round 7 with input size 32000
... Finishing a campaign of experiments with InsertionSort

Results of an experiment campaign with InsertionSort:

Size (#)        Timing (ms)     Ratio (#)
250             1               0
500             2               2
1000            1               1
2000            4               4
4000            4               1
8000            7               2
16000           28              4
32000           121             4

Starting a campaign of experiments with QuickSort ...
  Running round 0 with input size 250
  Running round 1 with input size 500
  Running round 2 with input size 1000
  Running round 3 with input size 2000
  Running round 4 with input size 4000
  Running round 5 with input size 8000
  Running round 6 with input size 16000
  Running round 7 with input size 32000
... Finishing a campaign of experiments with QuickSort

Results of an experiment campaign with QuickSort:

Size (#)        Timing (ms)     Ratio (#)
250             0               0
500             1               0
1000            0               0
2000            2               0
4000            2               1
8000            1               1
16000           2               2
32000           4               2

Automated Checks with GatorGrader

In addition to meeting all of the requirements outlined in the assignment sheet, your submission must pass the following checks that GatorGrader automatically assesses:

• The BubbleSort.java in src/main/java/practicalseven/sort has exactly 0 of the Add Your Name Here fragment
• The BubbleSort.java in src/main/java/practicalseven/sort has exactly 0 of the TODO fragment
• The BubbleSort.java in src/main/java/practicalseven/sort has exactly 1 of the extends Sorter fragment
• The BubbleSort.java in src/main/java/practicalseven/sort has exactly 1 of the package practicalseven fragment
• The Campaign.java in src/main/java/practicalseven/experiment has exactly 0 of the Add Your Name Here fragment
• The Campaign.java in src/main/java/practicalseven/experiment has exactly 0 of the TODO fragment
• The Campaign.java in src/main/java/practicalseven/experiment has exactly 0 of the println fragment
• The Campaign.java in src/main/java/practicalseven/experiment has exactly 1 of the package practicalseven fragment
• The Experiment.java in src/main/java/practicalseven/experiment has at least 2 multiple-line Java comment(s)
• The Experiment.java in src/main/java/practicalseven/experiment has at least 2 single-line Java comment(s)
• The Experiment.java in src/main/java/practicalseven/experiment has at least 7 of the println( fragment
• The Experiment.java in src/main/java/practicalseven/experiment has exactly 0 of the Add Your Name Here fragment
• The Experiment.java in src/main/java/practicalseven/experiment has exactly 0 of the TODO fragment
• The Experiment.java in src/main/java/practicalseven/experiment has exactly 1 of the package practicalseven fragment
• The InsertionSort.java in src/main/java/practicalseven/sort has exactly 0 of the Add Your Name Here fragment
• The InsertionSort.java in src/main/java/practicalseven/sort has exactly 0 of the TODO fragment
• The InsertionSort.java in src/main/java/practicalseven/sort has exactly 1 of the extends Sorter fragment
• The InsertionSort.java in src/main/java/practicalseven/sort has exactly 1 of the package practicalseven fragment
• The QuickSort.java in src/main/java/practicalseven/sort has exactly 0 of the Add Your Name Here fragment
• The QuickSort.java in src/main/java/practicalseven/sort has exactly 0 of the TODO fragment
• The QuickSort.java in src/main/java/practicalseven/sort has exactly 1 of the extends Sorter fragment
• The QuickSort.java in src/main/java/practicalseven/sort has exactly 1 of the package practicalseven fragment
• The ResultsTable.java in src/main/java/practicalseven/data has at least 12 multiple-line Java comment(s)
• The ResultsTable.java in src/main/java/practicalseven/data has at least 2 single-line Java comment(s)
• The ResultsTable.java in src/main/java/practicalseven/data has exactly 0 of the Add Your Name Here fragment
• The ResultsTable.java in src/main/java/practicalseven/data has exactly 0 of the TODO fragment
• The ResultsTable.java in src/main/java/practicalseven/data has exactly 0 of the println fragment
• The ResultsTable.java in src/main/java/practicalseven/data has exactly 1 of the double ratio = fragment
• The ResultsTable.java in src/main/java/practicalseven/data has exactly 1 of the package practicalseven fragment
• The RunCampaign.java in src/main/java/practicalseven/experiment has at least 1 single-line Java comment(s)
• The RunCampaign.java in src/main/java/practicalseven/experiment has at least 3 of the println( fragment
• The RunCampaign.java in src/main/java/practicalseven/experiment has at least 5 multiple-line Java comment(s)
• The RunCampaign.java in src/main/java/practicalseven/experiment has exactly 0 of the Add Your Name Here fragment
• The RunCampaign.java in src/main/java/practicalseven/experiment has exactly 0 of the TODO fragment
• The RunCampaign.java in src/main/java/practicalseven/experiment has exactly 1 of the package practicalseven fragment
• The Sorter.java in src/main/java/practicalseven/sort has exactly 0 of the Add Your Name Here fragment
• The Sorter.java in src/main/java/practicalseven/sort has exactly 0 of the TODO fragment
• The Sorter.java in src/main/java/practicalseven/sort has exactly 1 of the package practicalseven fragment
• The Sorter.java in src/main/java/practicalseven/sort has exactly 1 of the public abstract class fragment
• The TestResultsTable.java in src/test/java/practicalseven has exactly 0 of the Add Your Name Here fragment
• The TestResultsTable.java in src/test/java/practicalseven has exactly 0 of the TODO fragment
• The TestResultsTable.java in src/test/java/practicalseven has exactly 1 of the package practicalseven fragment
• The command gradle -q --console plain run executes correctly
• The command gradle build executes correctly
• The command gradle test executes correctly
• The file BubbleSort.java exists in the src/main/java/practicalseven/sort directory
• The file Campaign.java exists in the src/main/java/practicalseven/experiment directory
• The file Experiment.java exists in the src/main/java/practicalseven/experiment directory
• The file InsertionSort.java exists in the src/main/java/practicalseven/sort directory
• The file QuickSort.java exists in the src/main/java/practicalseven/sort directory
• The file ResultsTable.java exists in the src/main/java/practicalseven/data directory
• The file RunCampaign.java exists in the src/main/java/practicalseven/experiment directory
• The file Sorter.java exists in the src/main/java/practicalseven/sort directory
• The file TestResultsTable.java exists in the src/test/java/practicalseven directory
• The repository has at least 5 commit(s)

If GatorGrader's automated checks pass correctly, the tool will produce the output like the following in addition to returning a zero exit code (which you can access by typing the command echo $?).

        ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
        ┃ Passed 55/55 (100%) of checks for cs101-F2019-practical7! ┃
        ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

Downloading Project Updates

If GatorGrader's maintainers push updates to this sample assignment and you received it through GitHub Classroom and you would like to also receive these updates, then you can type this command in the main directory for this assignment:

git remote add download [email protected]:Allegheny-Computer-Science-101-F2019/cs101-F2019-practical7-starter.git

You should only need to type this command once; running the command additional times may yield an error message but will not negatively influence the state of your Git repository. Now, you are ready to download the updates provided by the GatorGrader maintainers by typing this command:

git pull download master

This second command can be run whenever the maintainers needs to provide you with new source code for this assignment. However, please note that, if you have edited the files that we updated, running the previous command may lead to Git merge conflicts. If this happens, you may need to manually resolve them with the help of the instructor or a student technical leader. Finally, please note that the Gradle plugin for GatorGrader will automatically download the newest version of GatorGrader.

Using Travis CI

This assignment uses Travis CI to automatically run GatorGrader and additional checking programs every time you commit to your GitHub repository. The checking will start as soon as you have accepted the assignment — thus creating your own private repository — and the course instructor and/or GitHub enables Travis for it. If you are using Travis for the first time, you will need to authorize Travis CI to access the private repositories that you created on GitHub. If you do not see either a yellow ● or a green ✔ or a red ✗ in your listing of commits, then please ask the instructor to see whether or not Travis CI was correctly enabled.

System Requirements

We developed this assignment to work with the following software and versions:

• Docker Desktop
• Operating Systems
  • Linux
  • MacOS
  • Windows 10 Pro
  • Windows 10 Enterprise
• Programming Language Tools
  • Gradle 5.4
  • MDL 0.5.0
  • OpenJDK 11.0.4
  • JUnit 4.9.0
  • Proselint 0.10.2
  • Python 3.6 or 3.7

Reporting Problems

If you have found a problem with this assignment's provided source code or documentation, then you can go to the Computer Science 101 Fall 2019 Practical 4 repository and raise an issue. If you have found a problem with the GatorGrader tool and the way that it checks your assignment, then you can also raise an issue in that repository. To ensure that your issue is properly resolved, please provide as many details as is possible about the problem that you experienced. If you discover a problem with the assignment sheet for this project, then please raise an issue in the GitHub repository that provides the assignment sheets for your course.

Whenever possible, individuals who find, and use the appropriate GitHub issue tracker to correctly document, a mistake in any aspect of this assignment will receive free GitHub stickers and extra credit towards their grade for the project.

Receiving Assistance

If you are having trouble completing any part of this project, then please talk with either the course instructor or a student technical leader during the course session. Alternatively, you may ask questions in the Slack workspace for this course. Finally, you can schedule a meeting during the course instructor's office hours.

Project Assessment

Taking inspiration from the principles of specification-based grading, the grade that a student receives on this practical assignment is based on the following:

• Travis CI Build Status: Since additional checks on the source code and/or technical writing may be encoded in Travis CI's actions and, moreover, all of the GatorGrader checks are also run in Travis CI, students will receive a checkmark grade if their last before-the-deadline build passes and a green ✔ appears in their GitHub commit log instead of a red ✗. Students are encouraged to repeatedly revise their source code in an attempt to get their Travis CI build to pass.

All grades for this project will be reported through a student's GitHub repository using either messages in the GitHub commit log or issues raised in the issue tracker. Students should ask questions about their grade for this project in GitHub so as to facilitate an effective conversation about the submitted deliverables.