Lab46 Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
======ABC0======
NOTE: this is a collaborative document among ALL my classes this semester. That means more people editing. Be mindful that only one person can edit the document at a time.

Only task headings have been provided. You are not expected to know how to do the task given just that description (although in some cases it can be adequately figured out). Instead, if no further information is yet present, ASK FOR DETAILS on the discord.

If something is missing: add it.

If something is present but needs polish: spruce it up.

If something is present but is incorrect: please fix it.

This is intended to be an informative, useful document that all can benefit from.

Those with prior experience, please be mindful not to gobble up all the low-hanging fruit from the newcomers.

=====Get on discord and into class channels=====

If for somehow you made it this far into the CS program yet are not in the lab46 discord, there is a link on the respective class syllabus. Click the link, and you will be transported to the channel. Also, you may have to identify yourself to the admin / class.

=====Getting an editor=====
You will need a text editor for class, vim is recommended

On WSL you can install it with:
<code>
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install vim
</code>
On Arch you can install it with:
<code>
sudo pacman -Syu
sudo pacman -S vim
</code>
=====Log into Lab46 (shell)=====
====Change lab46 password====
====Clone lab46 semester repo on lab46 (fixrepo)====
=====Log into Lab46 wiki=====
  * If you are reading this, YOU FOUND THE LAB46 WIKI!
  * Click login in the upper right and enter your user name and password
  * Your username is the beginning of your CCC email (i.e jsmith@corning-cc.edu user = jsmith)
  * Your password is your CCC i.d. (i.e. C00######)
====Change lab46 wiki password (can be same as lab46)====
  * Once logged in click update profile in the upper right and there is a menu to update your password

=====Set up personal development system=====

====Clone lab46 semester repo on your system====
  * On your system of choice, Virtual Machine or Pi, open a terminal
  * Option 1:
    * If on a Pi or Debian based distro the following command should work
<code>
wget -q https://lab46.g7n.org/~wedge/piph/download -O piph
bash ./piph
</code>
  * Option 2:
    * Not taking the shortcut route, use these two commands
<code>
hg clone ssh://USER@lab46.g7n.org//var/repos/hg/user/USER ~/src
hg clone ssh://USER@lab46.g7n.org//var/repos/hg/user/USER/spring2024 ~/src/spring2024
</code> 
  * Of course replacing USER with your username
====Create info.text file with information====
Create using ''touch'', ''vi'', ''echo'', ''nano'', etc.

If requirements for this semester's 'info.text' file are the same as past semesters, the file should include the following information: name, email, discord username, and program.

Example format:

  * name: John
  * email: jdoe@corning-cc.edu
  * disord: JohnDoe
  * program: Computer Science
====Create, compile, and execute hello.c====
Similarly to info.txt, you can need to create a file using a text editor like nano or vim.

Using one of the text editors, create a new file and name it "hello.c"

Within your file write out your C code for hello world

To compile you can use the gcc command with certain flags like this 
<code>
USER@lab46:~/src/fall2024/DESIG$ gcc -Wall -std=gnu18 -o "OUTPUTFILE" INPUTFILE 
</code>
where INPUTFILE is your uncompiled code, and OUTPUTFILE is your compiled code

Once you have compiled your code you can execute it with ./OUTPUTFILE
====Add, Commit, Push changes to repo====
In order to move files between Lab46 and your personal computer you can do this by doing hg add, hg commit and hg push and pull.
Using hg add will start tracking files. Using hg commit will commit those files and save them (hg commit -m "put commit message here") and doing hg push will push them out to the other destination where you want to access them. After using hg push make sure to go the destination and use hg pull to get access to the updated files.
=====Pull and Update project changes on Lab46=====
=====Submit project files on lab46=====
submitting files on lab46 uses the submit command
<code>
USER@lab46:~/src/fall2024/DESIG$ submit DESIG PROJECT FILE1 FILE2 FILE3 ...
</code>
sub in the class you are taking in place of DESIG, the project you are submitting in place of PROJECT, in this case abc0, and the files you are submitting in place of FILE, in this case your C code and info.txt file.
For example, if you were in data submitting abc0:
<code>
USER@lab46:~/src/fall/2024/data/abc0$ submit data abc0 helloworld.c info.txt
</code>
=====Customize journal title and intro, edit week1 entry=====

Each classmate has their own journal that you can see and read, Giving an intro helps introduce yourself. shocking, I know. This is also a great place to be creative and experiment with the text editor. Have fun!

Completing the weekly journal earns you points towards your grade, as well as getting you in the mindset of documenting progress.  

=====Class notes=====
Class Notes 8/27
Data/Discrete

Preamble:
--------

-Your soul is now on fire!

-Brief history lesson on tables

-Discussed AI policies, don't do it

-Opening projects: abc0 and btt0, do it

-Next due project, making space invaders (msi0 and after that msi1)

-First four pct's are available as of writing. 0 and 1 are due end of tomorrow.

-Journals / Class documents available

Class Discussion:
----------------

msi0 - using malloc'ed ARRAYS of structs, make space invaders. On the screen, the player at the bottom will shoot enemies at the top of the screen. They in the form of a grid, all aligned evenly, and if the player's bolt hits the enemy, they should go away with the bolt. The enemies march to one side of the screen and move down a row. The enemies should also shoot back. The player should die and cause a game over when the enemies either hit the player head-on or if their bolt hits the enemy. Consider have a score count on screen. Other bonus features are optional, like shields or powerups. 

In your struct for sprites (sprites being the things on screen), consider an X and Y for each on screen.

*Key instruction, how to form arrays with pointers:
Sprite *array 	= NULL;
array 		= (Sprite *)malloc(sizeof(sprite) * 15);




msi1 - the same project, but converting msi0 to use a linked list instead of an array, possibly the conversation for Thursday 8/29


Matt's class will make you think so hard, it'll make you physically ill!
Lab46 Wiki

User Tools

Site Tools

Page Tools
