ac

Author: brownsarahm

_practice/2023-04-04.md

@@ -0,0 +1,15 @@
+*note: this is integrative3*
+1. Update more rows on your KWL Chart based on what we did today.
+1. Contribute to your group repo and review a team mate's PR
+2. Install [ gcc](https://gcc.gnu.org/install/) locally and practice using it.  Repeat steps we did in class on your computer and then change the order of parameters; try skipping steps to produce errors, etc. Export the list of variations you tried and summarize what you learned as a list of tips and reminders on what the parameters do/why/when you would need them (or not) in {index} `gcctips.md`.  (to reinforce what we learned)
+3. Write two short programs that do the same thing in different ways and compile them both to assembly (eg using a for vs while loop to sum numbers up to a number). Check the assembly to see if they produce the same thing or if it's different. Save your code (in code blocks) and notes about your findings in `assemblycompare.md`
+4. On Seawulf, modfiy `main.c` from class to accept the integer as a command line argument instead of via input while running the program. [See this tutorial for an example](http://crasseux.com/books/ctutorial/argc-and-argv.html). 
+5. Write a bash script that runs your compiled program for each integer from 10 to 30 (syntax for a range is `{start..end}` so this would be `{10..30}`)
+6. Create an sbatch script to run your script  on a compute node and save the output to a file. The sbatch script should compile and link the program and then call the script. [see the options](https://web.uri.edu/hpc-research-computing/using-seawulf/#sbatch)
+7. use [scp](https://www2.stat.duke.edu/comp/security/scp_man.html) to download your modified main, script files, and output to your local computer and include them in your kwl repo. 
+8. Answer the following in {index}`hpc.md` of your KWL repo:  (to think about how the design of the system we used in class impacts programming and connect it to other ideas taught in CS)
+    ```
+    1. What kinds of things would your code need to do if you were going to run it on an HPC system?
+    2. What Sbatch options seem the most helpful?
+    3. How might you go about setting the time limits for a script? How could you estimate how long it will take?
+    ```

_prepare/2023-04-04.md

@@ -0,0 +1,2 @@
+1. [install this hardware simulator](https://www.nand2tetris.org/software)
+1. Create {index}`operators.md` and make some notes about what you know about operators.  What kinds of operators are you familiar with? Which have you seen in programming? math?

_review/2023-04-04.md

@@ -0,0 +1,13 @@
+*note: this is integrative3*
+1. Update  your KWL Chart based on what you have learned.
+1. Contribute to your group repo and review a team mate's PR.
+2. Install [ gcc](https://gcc.gnu.org/install/) locally and practice using it.  Repeat steps we did in class on your computer and then change the order of parameters; try skipping steps to produce errors, etc. Export the list of variations you tried and summarize what you learned as a list of tips and reminders on what the parameters do/why/when you would need them (or not) in {index}`gcctips.md`.  (to reinforce what we learned)
+3. Create some variations of the `hello.c` we made in class. Make `hello2.c` print twice with 2 print commands. Make `hello5.c` print 5 times with a for loop and `hello7.c` print 7 times with a for loop. Build them all on the command line and make sure they run correctly. 
+4. Write a bash script, {index}`assembly.sh` to compile each program to assembly and print the number of lines in each file.  
+5. Put the output of your script in {index}`hello_assembly_compare.md`. Add to the file some notes on how they are similar or different based on your own reading of them.  
+1. Read about [sbatch](https://web.uri.edu/hpc-research-computing/using-seawulf/#sbatch). Answer the following in {index}`hpc.md` of your KWL repo:  (to think about how the design of the system we used in class impacts programming and connect it to other ideas taught in CS)
+    ```
+    1. What kinds of things would your code need to do if you were going to run it on an HPC system?
+    2. What Sbatch options seem the most helpful?
+    3. How might you go about setting the time limits for a script? How could you estimate how long it will take?
+    ```