User Tools

Site Tools


Sidebar

projects

pct0 (bonus; due 20230823)
wcp1 (due 20230823)
abc0 (due 20230830)
btt0 (due 20230830)
pct1 (bonus; due 20230830)
pct2 (due 20230830)
wcp2 (due 20230830)
mpg0 (due 20230906)
pct3 (bonus; due 20230906)
wcp3 (due 20230906)
pct4 (due 20230913)
ttb0 (due 20230913)
wcp4 (due 20230913)
pct5 (bonus; due 20230920)
ttb1 (due 20230920)
wcp5 (due 20230920)
dap0 (due 20230927)
gfo0 (due 20230927)
pct6 (due 20230927)
wcp6 (due 20230927)
cgf0 (due 20231004)
pct7 (bonus; due 20231004)
wcp7 (due 20231004)
bwp1 (bonus; due 20231018)
cgf1 (due 20231018)
pct8 (due 20231018)
wcp8 (due 20231018)
cgf2 (due 20231025)
pct9 (bonus; due 20231025)
wcp9 (due 20231025)
cgf3 (due 20231101)
gfo1 (due 20231101)
pctA (due 20231101)
wcpA (due 20231101)
pctB (bonus; due 20231108)
waq0 (due 20231108)
wcpB (due 20231108)
pctC (due 20231115)
waq1 (due 20231115)
wcpC (due 20231115)
bwp2 (bonus; due 20231129)
pctD (bonus; due 20231129)
wcpD (bonus; due 20231129)
gfo2 (due 20231206)
pctE (bonus; due 20231206)
wcpE (bonus; due 20231206)
EoCE (due 20231214)
haas:fall2023:data:projects:abc0

Corning Community College

CSCS2320 Data Structures

PROJECT: Already Beginning Concepts (ABC0)

OBJECTIVE

To get started on the course and semester. Bootstrap your access and configuration of various resources, following instructions, contributing to documentation, and asking questions in the discord.

EDIT

You will want to go here to edit and fill in the various sections of the document:

ABC0 documentation

Tasks

Get on discord and into class channels

To log into the lab46 Discord server, use the link provided on the class's main page: (https://lab46.g7n.org/haas/[semester]/[course])

Once logged into Discord and entered the server, state your name as well as every course instructed by Matt Haas you will be taking during the semester. You will be given roles that will allow you to speak and interact in specific channels corresponding to each of your courses. Interaction here is key, as messages sent within course channels contribute towards your participation grade for the course.

Log into Lab46 (shell)

To log into Lab46 shell, start by opening a terminal. Once in the terminal input 'ssh' followed by your CCC user name and the domain <@lab46.g7n.org>.

*Your username is your CCC email excluding the domain.

EX: [username]@lab46.g7n.org

Clone lab46 semester repo on lab46

Once you have successfully logged into the Lab46 server you will want to enter the command fixrepo into the command line and press enter

Note You ONLY run fixrepo command once per semester

After you have done that, proceed to type cd src/ into the command line then perform an ls to make sure you see your appropriate SEMESTER

cd into your SEMESTER directory and perform hg status and if you do not get an error, proceed.

From here you can enter the following commands for every change to your repo:

hg add
hg commit -m "commit message text"
hg push
Log into Lab46 wiki

Your journal, the syllabus and other resources are made available to you via the lab46 wiki. In order to access these web resources for the class you have to log in.

  • At the top right of this page, click the “login” button
    • input your username (your college email without the @corning-cc.edu part)
    • input your password (your CCC ID# (capital C))

Once logged in note that the left sidebar has been updated with some new links, now on the wiki you have access to links to the course homepages of the classes you are taking and a link to your journal. It would be a good idea to familiarize yourself with these resources. 8-)

* Also if you have done a journal in previous semesters and would like to recall on them you can use the “Sitemap” link in the top right of the wiki page. This will take to a page with plenty of links, to access your previous journals

  • First click journal
  • Second the class year of your journal
  • Third your username
  • Finally select your week you wish to access
Set up personal development system
Clone lab46 semester repo on your system
Create info.text file with information

Your preferred name or nickname (after the heading “name: ”)

Your preferred (and frequently checked) e-mail (after the heading “email: ”)

Your discord screen name (they aren't always easy to intuit, after the heading “discord: ”)

Your matriculated program of study aka your major (after the heading “program: ”)

Any other information you feel pertinent to tell me (after the heading “other: ”)

Create and execute hello.c

Create and name a text file “hello.c”. You can do this simultaneously by typing vim or nano followed by the desired name of the new file

Once the file is created open it with a text editor. Ex: nano or vim.

Write the following program to the file.

  #include <stdio.h>
  
  // This code outputs"Hello World!" on a new line and then returns 0 after successful running.
  int main() {
  printf("Hello World!/n");
  return (0);
  }

Now compile the program with the following command

gcc -Wall -std=gnu18 hello.c -o some_file_name

Locate journal and customize title and intro

Your journal is always available while on the lab46 website under content on the left side of the screen.

You're able to customize many aspects of this page to your liking, simply use the [Edit] button on the bottom right of each module to change what appears. Feel free to experiment with different options and formats within this page to see what best matches you and your workflow.

 

SUBMISSION

To be successful in this project, the following criteria (or their equivalent) must be met:

  • Project must be submit on time, by the deadline.
    • Late submissions will lose 33% credit per day, with the submission window closing on the 3rd day following the deadline.
  • All code must compile cleanly (no warnings or errors)
    • Compile with the -Wall and –std=gnu18 compiler flags
    • all requested functionality must conform to stated requirements (either on this document or in a comment banner in source code files themselves).
  • Executed programs must display in a manner similar to provided output
    • output formatted, where applicable, must match that of project requirements
  • Processing must be correct based on input given and output requested
  • Output, if applicable, must be correct based on values input
  • Code must be nicely and consistently indented
  • Code must be consistently written, to strive for readability from having a consistent style throughout
  • Code must be commented
    • Any “to be implemented” comments MUST be removed
      • these “to be implemented” comments, if still present at evaluation time, will result in points being deducted.
      • Sufficient comments explaining the point of provided logic MUST be present
  • No global variables (without instructor approval), no goto statements, no calling of main()!
  • Track/version the source code in your lab46 semester repository
  • Submit a copy of your source code to me using the submit tool (make submit on lab46 will do this) by the deadline.

Submit Tool Usage

Let's say you have completed work on the project, and are ready to submit, you would do the following:

lab46:~/src/SEMESTER/DESIG/PROJECT$ submit DESIG PROJECT file1 file2 file3 ... fileN

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.

RUBRIC

I'll be evaluating the project based on the following criteria:

13:abc0:final tally of results (13/13)
*:abc0:submitted information for project by duedate [3/3]
*:abc0:got situated in and used class discord [3/3]
*:abc0:contributed to project documentation [3/3]
*:abc0:committed project related changes to semester repo [4/4]

Pertaining to the collaborative authoring of project documentation

  • each class member is to participate in the contribution of relevant information and formatting of the documentation
    • minimal member contributions consist of:
      • near the class average edits (a value of at least four productive edits)
      • near the average class content change average (a value of at least 128 bytes (absolute value of data content change))
      • near the class content contribution average (a value of at least 1kiB)
      • no zero-sum commits (adding in one commit then later removing in its entirety for the sake of satisfying edit requirements)
    • adding and formatting data in an organized fashion, aiming to create an informative and readable document that anyone in the class can reference
    • content contributions will be factored into a documentation coefficient, a value multiplied against your actual project submission to influence the end result:
      • no contributions, co-efficient is 0.50
      • less than minimum contributions is 0.75
      • met minimum contribution threshold is 1.00

Additionally

  • Solutions not abiding by spirit of project will be subject to a 50% overall deduction
  • Solutions not utilizing descriptive why and how comments will be subject to a 25% overall deduction
  • Solutions not utilizing indentation to promote scope and clarity or otherwise maintaining consistency in code style and presentation will be subject to a 25% overall deduction
  • Solutions not organized and easy to read (assume a terminal at least 90 characters wide, 40 characters tall) are subject to a 25% overall deduction
haas/fall2023/data/projects/abc0.txt · Last modified: 2023/08/16 21:30 by 127.0.0.1