Corning Community College
CSCS1730 UNIX/Linux Fundamentals
To create an increasingly detailed program logic that implements and displays a playing field of a defined number/logic game.
Due to similar descriptions among the range of projects, I have condensed everything into one common project page. Where you see “ngfX” please substitute the particular project you are working on (ie “ngf0”, “ngf1”, etc.)
As an exercise in toning your abstraction abilities (literally seeing one thing, but understanding and using it as something else), there will be a number of 'generic' terms used throughout this (and other) documents throughout the course, requiring you to substitute in the pertinent information (else face confusion or error).
Some examples:
This sort of abstraction is very similar to that we will find in our utilization of variables in programming, where we can have a “name”, but the data associated with it can change based on various conditions.
Do not be a literalist computer! Start to exercise your abstraction abilities.
This document is written with TWO locations in mind:
There are commands you can ONLY run on one system or the other. Pay attention to any prompt cues in the given examples (or section headings, context of language leading up to any examples).
For example:
Please pay attention to your prompt, so you can perform the needed activity on the correct system.
Please be sure to familiarize yourself with the pertinent content in:
Please familiarize yourself with the table of contents and or index of the various resources, and sample various content to connect yourself with deeper understanding into the concepts being called upon in the current activity.
Develop and test this program on your pi. Only when done, verify that it compiles on lab46.
To utilize the needed functionality for this project, you will need to ensure you have the following packages installed:
NOTE: make sure you, for the purposes of your activities pertaining to this class, that you are using your SEMESTER repository.
Your program should:
To obtain project data, you will need to satisfy the following prerequisites:
If all those conditions are met, you can use the grabit tool to obtain the project, as follows:
lab46:~/src/SEMESTER/DESIG$ grabit DESIG ngfX make: Entering directory '/var/public/SEMESTER/DESIG/ngfX' '/var/public/SEMESTER/DESIG/ngfX/Makefile' -> '/home/USER/src/SEMESTER/DESIG/ngfX/Makefile' '/var/public/SEMESTER/DESIG/ngfX/README' -> '/home/USER/src/SEMESTER/DESIG/ngfX/README' '/var/public/SEMESTER/DESIG/ngfX/ngfX.sh' -> '/home/USER/src/SEMESTER/DESIG/ngfX/ngfX.sh' '/var/public/SEMESTER/DESIG/ngfX/ref_ngfX.aarch64' -> '/home/USER/src/SEMESTER/DESIG/ngfX/ref_ngfX.aarch64' '/var/public/SEMESTER/DESIG/ngfX/ref_ngfX.armv7l' -> '/home/USER/src/SEMESTER/DESIG/ngfX/ref_ngfX.armv7l' '/var/public/SEMESTER/DESIG/ngfX/ref_ngfX.x86_64' -> '/home/USER/src/SEMESTER/DESIG/ngfX/ref_ngfX.x86_64' '/var/public/SEMESTER/DESIG/ngfX/tttX.sh' -> '/home/USER/src/SEMESTER/DESIG/ngfX/tttX.sh' make: Leaving directory '/var/public/SEMESTER/DESIG/ngfX' lab46:~/src/SEMESTER/DESIG$
At which point you can change into the newly created and populated ngfX directory.
If you don't have a monitor, you likely are logging into your pi remotely (doable, and good intra-system practice)
Once your ngfX project files are 'hg' added to your repository on lab46, commit and push.
On your pi, to obtain those files there, be sure to be in your repository, and 'hg' pull and update.
NOTE: To avoid repository conflicts, ALWAYS check for any incoming pull/update transactions before doing a commit/push. Problems occur when you forget (this is an issue on both lab46 and your pi).
Run your script:
lab46:~/src/SEMESTER/DESIG/ngfX$ ./ngfX.sh
To successfully complete this project, the following criteria must be met:
To submit this program to me using the submit tool, run the following command at your lab46 prompt:
lab46:~/src/SEMESTER/DESIG/ngfX$ make submit Project backup process commencing Taking snapshot of current project (ngfX) ... OK Compressing snapshot of ngfX project archive ... OK Setting secure permissions on ngfX archive ... OK Project backup process complete Submitting DESIG project "ngfX": -> ../ngfX-DATESTAMP-HOUR.tar.gz(OK) SUCCESSFULLY SUBMITTED lab46:~/src/SEMESTER/DESIG/ngfX$
You should get some sort of confirmation indicating successful submission if all went according to plan. If not, check for typos and or locational mismatches.
What I'll be looking for:
SCORE:ngfX:final tally of results (SCORE/TOTAL) *:ngfX:obtained via grabit by Sunday before deadline [#/#] *:ngfX:script contains no syntax errors [#/#] *:ngfX:script contains no logical errors [#/#] *:ngfX:script contains no runtime errors [#/#] *:ngfX:script performs stated task/algorithm [#/#] *:ngfX:script output conforms to formatting expectations [#/#] *:ngfX:proper error checking and status reporting performed [#/#] *:ngfX:code implements solution using relevant concepts [#/#] *:ngfX:code updates committed/pushed to lab46 semester repo [#/#] *:ngfX:code uses correct variable types and name lengths [#/#] *:ngfX:project is submitted with relevant and complete source [#/#] *:ngfX:project is submitted on lab46 using 'make submit' [#/#] *:ngfX:runtime tests of submitted program succeed [#/#]
Additionally:
project (ngfX) | point item (#) | total points (TOTAL) |
---|---|---|
ngf0 | 1 | 13 |
ngf1 | 2 | 26 |
ngf2 | 3 | 39 |
ngf3 | 4 | 52 |
ngf4 | 5 | 65 |
ngf5 | 6 | 78 |