Lab46 Wiki

User Tools

Site Tools

You are here: start » haas » fall2020 » common » projects » lob0
haas:fall2020:common:projects:lob0

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
haas:fall2020:common:projects:lob0 [2020/08/21 12:52] – wedgehaas:fall2020:common:projects:lob0 [2020/09/01 12:23] (current) – [Raspberry Pi command-line via SSH/MOSH] wedge
Line 1: Line 1:
 ======PROJECT====== ======PROJECT======
-PROJECT: Letters of Blocks+PROJECT: Letters of Blocks (lob0)
  
 =====Objective===== =====Objective=====
-To create a program that generates an image containing a set of letters, made from coordinated blocks.+To adapt and experiment with a program that generates an image containing a set of letters, made from coordinated blocks.
  
 +Also to start some time-sensitive activities to ensure ground is broken on the project before the day it is due (see submission rubric below)
 =====Abstraction===== =====Abstraction=====
-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). +{{page>haas:fall2020:common:projects:abstraction&noheader}}
- +
-Some examples: +
- +
-  * //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. +
-  * //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. +
- +
-Do not be a literalist computer! Start to exercise your abstraction abilities.+
  
 =====Locational Awareness===== =====Locational Awareness=====
-This document is written with TWO locations in mind: +{{page>haas:fall2020:common:projects:location&noheader}}
- +
-  * lab46 (the system you may retrieve resources and SUBMIT projects) +
-  * 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). +
- +
-For example: +
- +
-  * YOU cannot install software on lab46. You don't have access. +
-  * projects CANNOT be SUBMITTED on your pi.+
  
 =====Reading===== =====Reading=====
Line 53: Line 30:
     * each symbol is a unique render (if you had 2 letter M's, both M's should look different)     * each symbol is a unique render (if you had 2 letter M's, both M's should look different)
     * the symbols are arranged to comfortably fill and fit within a canvas of 1280x1024 pixels     * the symbols are arranged to comfortably fill and fit within a canvas of 1280x1024 pixels
-   * I don't want swaths of unused space+      * I don't want swaths of unused space
     * the image will utilize no fewer than 8 different colours     * the image will utilize no fewer than 8 different colours
     * letters are to be entirely constructed out of blocks (filled but square rectangles), no smaller than 32x32 pixels a piece and no larger than 64x64 pixels (all blocks must be the same size)     * letters are to be entirely constructed out of blocks (filled but square rectangles), no smaller than 32x32 pixels a piece and no larger than 64x64 pixels (all blocks must be the same size)
Line 95: Line 72:
 At which point you can change into the newly created and populated **lob0** directory. At which point you can change into the newly created and populated **lob0** directory.
  
 +Be sure to **add**, **commit**, and **push** this to your lab46 clone of your repository.
 +
 +Then, on your pi, **pull** and **update** to get the files available there.
 =====Compiling===== =====Compiling=====
 Since the grabit brought in a Makefile, you can compile your code simply by typing: **make** Since the grabit brought in a Makefile, you can compile your code simply by typing: **make**
Line 115: Line 95:
 As with any process you are looking to describe or automate (in this case, both), if YOU do not personally understand or appreciate the steps involved, you are going to have a hard time communicating a proficient list of instructions to the computer to carry out. As with any process you are looking to describe or automate (in this case, both), if YOU do not personally understand or appreciate the steps involved, you are going to have a hard time communicating a proficient list of instructions to the computer to carry out.
  
-So, the FIRST order of business would be to, BY HAND, ON A SHEET OF GRAPH PAPER:+So, the FIRST order of business would be to, BY HAND, ON A SHEET OF GRAPH PAPER (consider this your PROTOTYPE):
  
   * START EARLY: perhaps even while you are working on week 2's "pct2" project. Don't WASTE the abundance of time made available to you. Waiting until the last minute will only preserve frustration and confusion.   * START EARLY: perhaps even while you are working on week 2's "pct2" project. Don't WASTE the abundance of time made available to you. Waiting until the last minute will only preserve frustration and confusion.
Line 144: Line 124:
 You don't have a monitor, so you are logging into your pi remotely (doable, and good intra-system practice) You don't have a monitor, so you are logging into your pi remotely (doable, and good intra-system practice)
  
-Once your **Makefile** and **lob0.c** file are added to your repository, **commit** and **push**. +We start by running a successfully-compiled **lob0**:
- +
-On lab46, **pull** and **update**. +
- +
-Compile:+
  
 <cli> <cli>
-lab46:~/src/desig/lob0$ make+yourpi:~/src/desig/lob0$ ./lob0
 </cli> </cli>
  
-and run your program:+... which will produce an image (**lob0.png**); You want to put this in your web space (with the proper permissions set), so you can view it in a web browser:
  
 <cli> <cli>
-lab46:~/src/desig/lob0$ ./lob0+yourpi:~/src/desig/lob0$ scp lob0.png yourusername@lab46.g7n.org:public_html/
 </cli> </cli>
  
-... which will produce an image (**lob0.png**); You want to put this in your web space (with the proper permissions set), so you can view it in a web browser:+Note that you will be prompted for your lab46 password. 
 + 
 +Then over on lab46, run this:
  
 <cli> <cli>
-lab46:~/src/desig/lob0$ mv lob0.png ~/public_html/ +lab46:~$ chmod 0644 ~/public_html/lob0.png
-lab46:~/src/desig/lob0$ chmod 0644 ~/public_html/lob0.png+
 </cli> </cli>
  
haas/fall2020/common/projects/lob0.1598014376.txt.gz · Last modified: 2020/08/21 12:52 by wedge

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki