Differences

This shows you the differences between two versions of the page.

--- haas:fall2020:common:projects:ntr0 [2020/08/22 13:47] – [Program to Implement] wedge
+++ haas:fall2020:common:projects:ntr0 [2021/01/28 12:41] (current) – wedge
@@ Line 1: / Line 1: @@
 ======PROJECT======
-PROJECT: Introductory Activities and Getting Started
+PROJECT: Introductory Activities and Getting Started (ntr0)
 =====Objective=====
 In this project, we get started with some course initialization activities.
-=====Abstraction=====
+The aim is to:
-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:
+  * get you settled and configured with pertinent class resources
+  * test your ability to parse and proceed through linear, top-down documentation
+  * generate contextual awareness of your place within the computing environment
+  * start to acclimate to variables and conditions of abstraction
-  * //yourusername// - where you see this (likely in a config file or command-line argument), you are NOT to literally type in y-o-u-r-u-s-e-r-n-a-m-e, but instead, substitute in YOUR lab46 username.
+All of which will be important, ongoing skills to possess and continue to strengthen as we proceed through the course.
-  * //desig// - different classes have different class designations. To make one universal document pertinent to ALL classes, specific examples will instead use 'desig', where you must substitute in the class desig of the class YOU are taking and acting upon in that moment. Example class desigs:
-    * c4eng - ENGR1050 "C for Engineers"
-    * cprog - CSCS1320 "C/C++ Programming"
-    * unix - CSCS1730 "UNIX/Linux Fundamentals"
-    * data - CSCS2320 "Data Structures"
-    * discrete - CSCS2330 "Discrete Structures"
-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.
+=====How to proceed through this project=====
+There has been some unexpected confusion by some on how to glean information and make progress through this project (ie the information contained within this document and the necessary actions and awareness of what is going on).
-Do not be a literalist computer! Start to exercise your abstraction abilities.
+The following advice, when genuinely followed, seems to remedy any initial confusion:
-=====Locational Awareness=====
+  * read through this document, starting at its very top, and working your way down, line by line to the bottom (it is generally linear, with contextual clues sprinkled in)
-This document is written with TWO locations in mind:
+  * as you read through, comprehend and strive to understand what is happening. The supporting text, often surrounding any example or model commands to run, will tend to fill in the crucial backstory and connections. If further clarification is needed, please ask questions! Just running the commands in this document and have ZERO clue of what you are doing isn't going to help you in the long run.
+  * have a contextual/locational awareness of where you are (there are 2 different computing systems you are to perform work on, and there are two different means of accessing one of the systems- via command line, and via the web)
+  * we will be making heavy use of abstraction in this course. We start off with some simple exercises, providing you with model commands you need to adjust to fit your reality (ie commands that won't work as literally shown, but when pertinent meanings are substituted in and followed, will result in success: this is a common theme throughout the course).
+  * remember (for the duration of the course) the important concepts presented: for this project will NOT be the last time you see them. Starting from a clean slate each project, retaining NOTHING from your prior experiences will make things unnecessarily difficult for you.
+  * be sure to spend some time experimenting and playing, so as to gain an even deeper understanding and familiarity with these concepts. We will encounter and use many tools that facilitate our means of accomplishing various tasks. Their application isn't necessarily limited to the current activity of the project or the subject matter of the course. There are a wealth of productivity treasures to be encountered (both tangible and intangible) that can supercharge your educational journey.
-  * lab46 (the system you may retrieve resources and SUBMIT projects)
+As many of my graduated and subsequently employed alumni have relayed to me, many of these activities and behaviours I have highlighted have been quite influential in their success at their various jobs.
-  * your pi (the system you will transfer resources to/from, and WORK ON/COMPLETE projects)
-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).
+Say some of my former students now employed as engineers: "Reading is 90%+ of the job"
+=====Abstraction=====
+{{page>haas:fall2020:common:projects:abstraction&noheader}}
-For example:
+=====Locational Awareness=====
+{{page>haas:fall2020:common:projects:location&noheader}}
-  * YOU cannot install software on lab46. You don't have access.
+=====Part 1: Getting started with course resources=====
-  * projects CANNOT be SUBMITTED on your pi.
+Be sure to have a handle on these things before proceeding on:
-=====Reading=====
+====Reading====
-Please be sure to read through the PDF "UNIX for the Beginning Mage":
+Please be sure to read through, play with, and comprehend the material in the PDF "UNIX for the Beginning Mage":
   * https://lab46.g7n.org/_media/haas/ufbm.pdf
-=====Course Homepage/Syllabus=====
+This will introduce you to some important computing tools which we will be using to facilitate our class activities this semester. Especially if you haven't had much exposure to "files" on the computer and their organization and manipulation. You really need to have this material down.
+====Course Homepage/Syllabus====
 You're reading this, so you've likely already found your way to the course homepage. It consists of the syllabus plus additional course resources.
 Please familiarize yourself with it, bookmarking important resources as appropriate, so that you can refer back when needed.
-I'd recommend knowing how to get to the projects page (where you found the link for this project), as new content will be posted there.
+I'd recommend knowing how to get to the projects page (where you found the link for this project), as new content will be posted there. Note the due dates and identify the current and upcoming projects.
 Be sure to read through and over the syllabus, ensuring there are no questions on the material and organization of the course.
-=====Lab46 Shell====
+=====Part 2: logging onto Lab46 command-line=====
+====Lab46 Shell====
 For many of you, this will be your first experience logging onto Lab46 and working within a command-line environment.
@@ Line 61: / Line 67: @@
 lab46:~$
 </cli>
-=====Wiki=====
-The course homepage/syllabus, your journal, and other resources are made available to you via the lab46 wiki. In order to better access your web resources for the course, you must log in:
-  * top right of this page, notice the "login" button
-    * sign in with your wiki username (should be same as lab46 login) and password
-    * your wiki password should be in an e-mail to you on lab46
-      * use the 'alpine' command when logged into lab46 to retrieve your wiki password
-  * once logged in, note the left sidebar has been updated with some custom (to you) content
-    * links to the course homepages of the classes you are taking with me
-    * a link to your journal
-Go ahead and familiarize yourself with these resources.
-=====Journal Intro=====
-When Clicking on your journal link:
-Familiarize yourself with your Journal, and once there:
-  * customize it (title/subtitle, as you feel fitting. Change "YOUR NAME" to your actual name, etc.)
-  * add an introduction (tell us a little something about yourself)
-  * create your first week content
 ====Clone your Lab46 Mercurial Repository on lab46====
@@ Line 122: / Line 106: @@
 And that's it! Repeat this process (NOT the 'fixrepo'; only do that once) for any changes you make to your repository.
-=====Raspberry Pi section=====
+=====Part 3: Getting started on the Raspberry Pi=====
 The pi-related activities on this project require you to have a Raspberry Pi single board computer, assembled and operational, running the 32-bit Raspberry Pi OS (aka raspbian).
@@ Line 131: / Line 115: @@
   * username: **pi**
   * password: **raspberry**
 ====The Shell (command-line) on the pi====
 For many of you, this will be your first experience logging onto a Raspberry Pi and working within a command-line environment. You're taking your first steps into a much larger world.
-Your clearest indication you are on your Raspberry Pi will likely be in the display of the prompt, resembling the following:
+Your clearest indication you are on your Raspberry Pi will likely be in the display of the prompt, resembling the following (in whole or in part):
 <cli>
@@ Line 156: / Line 139: @@
 NOTE: you will NOT see ANYTHING when you type in your password.
 ====Manage Packages====
 Through various course activities, you may need to install additional software on your Raspberry Pi. Here are some instructions on how to do that.
@@ Line 210: / Line 194: @@
 NOTE: With the installation of **aptitude**, you can use it in place of apt-get/apt-cache:
-  * update: sudo aptitude update
+  * update: **sudo aptitude update**
-  * upgrade: sudo aptitude upgrade
+  * upgrade: **sudo aptitude upgrade**
-  * search: aptitude search TOKEN
+  * search: **aptitude search __TOKEN__**
-  * install: sudo aptitude install PACKAGE
+  * install: **sudo aptitude install __PACKAGE__**
-Some other packages you might want to install (some might already be installed):
+Where **__TOKEN__** is some substring of the thing you are looking for, and **__PACKAGE__** is the name of the installable package.
+Some other packages (substitute in place of **__PACKAGE__** above) you might want to install (some might already be installed):
   * bc
@@ Line 224: / Line 210: @@
   * file
-Be on the lookout for other packages to install in this project.
+Be on the lookout for other packages to install in this project (often embedded in the reading or unhighlighted on various lists of actions to take).
 ====Clone your Lab46 Mercurial Repository on your raspberry pi====
@@ Line 401: / Line 387: @@
 </cli>
-=====Getting data from your pi to lab46=====
+=====Part 4: Accessing your website-based class resources=====
+====Wiki====
+The course homepage/syllabus, your journal, and other resources are made available to you via the lab46 wiki. In order to better access your web resources for the course, you must log in:
+  * top right of this page, notice the "login" button
+    * sign in with your wiki username (should be same as lab46 login) and password
+    * your wiki password should be in an e-mail to you on lab46
+      * use the 'alpine' command when logged into lab46 to retrieve your wiki password (you can ask for help about this in the class discord)
+  * once logged in, note the left sidebar has been updated with some custom (to you) content
+    * links to the course homepages of the classes you are taking with me
+    * a link to your journal
+Go ahead and familiarize yourself with these resources.
+====Journal Intro====
+When Clicking on your journal link:
+Familiarize yourself with your Journal, and once there:
+  * customize it (title/subtitle, as you feel fitting. Change "YOUR NAME" to your actual name, etc.)
+  * add an introduction (tell us a little something about yourself)
+  * create your first week content
+=====Part 5: Getting data from your pi to lab46=====
 So, you've written a C program and a text file. Both of which need to be submitted on lab46. How do we get data from your pi to lab46? If you've added it to your repository, we use that!
@@ Line 412: / Line 421: @@
 Make sure you've pushed any and all commits before you do this, though!
-=====Submission Criteria=====
+=====Part 6: Submission of the project=====
 To be successful in this project, the following criteria must be met:

Lab46 Wiki

User Tools

Site Tools

Differences

Page Tools