From 2c4157b62fb921ee77e0079fae372d1e94643a08 Mon Sep 17 00:00:00 2001 From: Trevor Moy <51927676+trevmoy@users.noreply.github.com> Date: Tue, 24 Oct 2023 14:30:25 -0400 Subject: [PATCH 1/6] Update faq/syllabus.md --- faq/syllabus.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/faq/syllabus.md b/faq/syllabus.md index 4398208..b1c4de9 100644 --- a/faq/syllabus.md +++ b/faq/syllabus.md @@ -66,3 +66,17 @@ excerpts or screenshots embedded in it. They should be markdown files in your KWL repo. I recommend myst markdown. ``` +## Why won't my experience badge workflow contain the new changes after I edit the workflow? +```{toggle} +If you find that a workflow you may have made changes to are not properly reflecting your workflow changes is because you may not be running the workflow correctly. + +To correctly execute an action in GitHub you should: + +1. Make sure you are in the actions tab in your repository +2. On the left side of the screen the specific workflows should be available to select. +3. Select the desired workflow. +4. At the top of the workflow runs there should be an option to run the workflow. +5. Select Run Workflow to run the most recent and up to date workflow. + +This should help correct the workflow if it was causing issues. +``` \ No newline at end of file From 36c4eb5fa5351cd7dd127cee55dc1e131c85c73b Mon Sep 17 00:00:00 2001 From: Trevor Moy <51927676+trevmoy@users.noreply.github.com> Date: Tue, 24 Oct 2023 14:34:28 -0400 Subject: [PATCH 2/6] Update faq/syllabus.md --- faq/syllabus.md | 14 -------------- 1 file changed, 14 deletions(-) diff --git a/faq/syllabus.md b/faq/syllabus.md index b1c4de9..4398208 100644 --- a/faq/syllabus.md +++ b/faq/syllabus.md @@ -66,17 +66,3 @@ excerpts or screenshots embedded in it. They should be markdown files in your KWL repo. I recommend myst markdown. ``` -## Why won't my experience badge workflow contain the new changes after I edit the workflow? -```{toggle} -If you find that a workflow you may have made changes to are not properly reflecting your workflow changes is because you may not be running the workflow correctly. - -To correctly execute an action in GitHub you should: - -1. Make sure you are in the actions tab in your repository -2. On the left side of the screen the specific workflows should be available to select. -3. Select the desired workflow. -4. At the top of the workflow runs there should be an option to run the workflow. -5. Select Run Workflow to run the most recent and up to date workflow. - -This should help correct the workflow if it was causing issues. -``` \ No newline at end of file From be4e509286363fea90b8d032e03fe614abb4e6cf Mon Sep 17 00:00:00 2001 From: Trevor Moy <51927676+trevmoy@users.noreply.github.com> Date: Tue, 28 Nov 2023 14:18:15 -0500 Subject: [PATCH 3/6] Update 2023-10-19.md typo --- notes/2023-10-19.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/notes/2023-10-19.md b/notes/2023-10-19.md index ba314df..df64776 100644 --- a/notes/2023-10-19.md +++ b/notes/2023-10-19.md @@ -5,7 +5,7 @@ kernelspec: --- -# Why did we learn the plubming commands? +# Why did we learn the plumbing commands? You will not typically use them on a day to day basis, but they are a good way to see what happens at the interim steps and make sure that you have the right understanding of what git does. @@ -1061,4 +1061,4 @@ save your command history to `2023-10-19-log.txt` and put that file in your KWL ```{note} due to scheduling issues this will be late today -``` \ No newline at end of file +``` From c781dbdbd5d6a2906aa3628329663139c724da49 Mon Sep 17 00:00:00 2001 From: Trevor Moy <51927676+trevmoy@users.noreply.github.com> Date: Thu, 14 Dec 2023 10:25:36 -0500 Subject: [PATCH 4/6] Updated resources/testimonials.md --- resources/testimonials.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/resources/testimonials.md b/resources/testimonials.md index 4429356..6bcb2f0 100644 --- a/resources/testimonials.md +++ b/resources/testimonials.md @@ -1,3 +1,5 @@ # Testimonials from Fall 2023 students The best way to succeed in this course is to start badges as early as possible. Waiting till the end of the semester to finish up a lot of it creates unnecessary stress and it is something that I regret doing myself. I would also recommend going over the notes after they are posted to reinforce what you learned during the class. All the topics build on each other so this is something I’m glad I did. Do your best to stay on top of the work early to make the end of the semester easier. If you do these you’ll have no trouble passing the class and you’ll definitely finish it being glad you took it. + +The best way that you can succeed in CSC 392 is to practice with the course content and get ahead on the badges. Taking the time to complete badges is the best way to do this and the more consistently you can get your badges done, the more practice and skills you're going to improve with this course. Definitely work to get your explore and build badges out of the way early on because they will sneak up out of nowhere and make your life unnecessarily tough. The class is a great preview of what collaboration in an actual workplace might look like so make sure to actively participate to get the full lerning experience. \ No newline at end of file From 533ca74d1800006598a7d30412dc7de5ffe5c550 Mon Sep 17 00:00:00 2001 From: Trevor Moy <51927676+trevmoy@users.noreply.github.com> Date: Thu, 14 Dec 2023 13:39:05 -0500 Subject: [PATCH 5/6] Added resources/coursetimeline.md --- resources/coursetimeline.md | 62 +++++++++++++++++++++++++++++++++++++ 1 file changed, 62 insertions(+) create mode 100644 resources/coursetimeline.md diff --git a/resources/coursetimeline.md b/resources/coursetimeline.md new file mode 100644 index 0000000..46984c7 --- /dev/null +++ b/resources/coursetimeline.md @@ -0,0 +1,62 @@ +# Course Timeline + +For an easy visual of how the course is going to go over the next few months and what it will cover you can use this timeline to keep track of what part of the semester we're at. + +```{mermaid} +timeline + title CSC 392 Course Timeline + section Week 1 + 2023-09-07 : Lecture - start of semester + create kwl repo in github, navigate github.com basics + 2023-09-08 : Lab - GitHub Basics + syllabus quiz, setup + section Week 2 + 2023-09-12 : Lecture - set up to work offline together, create a folder + 2023-09-14 : Lecture - navigate files and clone a repo locally + 2023-09-15 : Lab - working at the terminal + organization, setup kwl locally, manage issues + section Week 3 + 2023-09-19 : Lecture - clone a repo and make a branch locally + 2023-09-21 : Lecture - work with bash and recover from a mistake with git + 2023-09-22 : Lab - offline branches + plan for success, clean a messy repo + section Week 4 + 2023-09-26 : Lecture - examine commit objects, introduce plumbing commands + 2023-09-28 : Lecture - make a jupyterbook + 2023-09-29 : Lab - tool familiarity + work on badges, self progress report + section Week 5 + 2023-10-03 : Lecture - examine git from multiple definitions and inspect objects + 2023-10-05 : Lecture - discussion with minor code examples + 2023-10-06 : Lab - unix philosophy + design a command line tool that would enable a bash script + section Week 6 + 2023-10-12 : Lecture - create a commit using plumbing commands + 2023-10-13 : Lab - git plumbing + git plumbing experiment + section Week 7 + 2023-10-17 : Lecture - discussion and use hashing algorithm + 2023-10-19 : Lecture - make a tag and release + 2023-10-20 : Lab - git plumbing + grade calculation script, self reflection + section Week 8 + 2023-10-24 : Lecture - build a bash script that calculates a grade + 2023-10-26 : Lecture - log into a remote server and work with large files + 2023-10-27 : Lab - scripting + releases and packaging + section Week 9 + 2023-10-31 : Lecture - discussions and sharing IDE tips + 2023-11-02 : Lecture - discussion or independent research + 2023-11-03 : Lab - remote, hpc + server work, batch scripts + section Week 10 + 2023-11-07 : Lecture - configure and use ssh keys on a hpc + 2023-11-09 : Lecture - build code in C and examine intermediate outputs + 2023-11-10 : Lab - Compiling + C compiling experiments + section Week 11 + 2023-11-14 : Lecture - use a hardware simulator to see step by step of a simple program + 2023-11-16 : Lecture - work with float representation through fractions in Python + 2023-11-17 : Lab - Machine Representation + bits and floats and number libraries + section Week 12 + 2023-11-21 : Lecture - derive addition from basic logic operations + section Week 13 + 2023-11-28 : Lecture - discussion + 2023-11-30 : Lecture - write a threaded program and fix a race condition + 2023-12-01 : Lab - hardware + self-reflection, work, project consultations + section Week 14 + 2023-12-05 : Lecture - large data that has to be read in batches + 2023-12-07 : Lecture - review quiz, integration/reflection questions + 2023-12-08 : Lab - os + hardware simulation + section Week 15 + 2023-12-12 : Lecture - end of semester discussion +``` From cd7b327bf1caa32bd9fca5dce2c2727d42f7ba93 Mon Sep 17 00:00:00 2001 From: Trevor Moy <51927676+trevmoy@users.noreply.github.com> Date: Thu, 14 Dec 2023 13:46:16 -0500 Subject: [PATCH 6/6] Update coursetimeline.md --- resources/coursetimeline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/resources/coursetimeline.md b/resources/coursetimeline.md index 46984c7..4891d17 100644 --- a/resources/coursetimeline.md +++ b/resources/coursetimeline.md @@ -2,7 +2,7 @@ For an easy visual of how the course is going to go over the next few months and what it will cover you can use this timeline to keep track of what part of the semester we're at. -```{mermaid} +```mermaid timeline title CSC 392 Course Timeline section Week 1