| |
VAB requirements |
|
| |
Formal Lab Write-up: |
|
| |
- Heading with a VAB # and Title, date, and lab partners (if any).
- Overview or brief purpose of the lab.
- Columns or tables of any data collected or requested in lab instructions (use a straightedge if drawing please). Time and frequency domain data may be captured off the screen and printed out. Items placed into the lab book need to be neatly cut out and taped in place with clear tape.
- Paragraph on Results & Discussion of the findings (if one is called for) with a description of problems encountered and solved (hopefully!) and any errors that occurred.
> The results answer the questions asked in the objective. This section will present the primary findings of your observations and/or data. The results may have been numerical, sketched, or printed out. Numerical results may be graded against an “accepted” value.
> Screenshots of the actual VAB block diagram setup are required for Design and Build labs when essential features or design strategies are discussed.
> Design and Build labs require a version number that you generate (v. 2.2, etc) based on the amount of changes you've made. Every day you work on a VAB project you should be an additional 0.1 to the version number.
> An initial functional VAB worksheet could be version 1.0 (everything before a working VAB would be below 1.0). For example, v. 1.3 could be the third day of refining a functional worksheet. When a major functional breakthrough has been made, call it a 2.0 version (jump to the next whole-number level) and then add a 0.1 to the version number after every day's work.
- Design & Build labs need to have an additional section at the end of the lab report that describes ACTION ITEMS to be fixed or improved in the next "version" number if you were to continue working on it.
- The VAB worksheet (if you designed and built one OR modified one) with your last name at the end of the file name.
|
|
| |
Email Requirements: |
|
| |
- Attach and email to Mr. Rummel with the
VAB number and
your last name in the subject line.
|
|
| |
a. Filename example = "4-2 VAB Marksman" for VAB 4.2 by Joe Marksman
OR "Optical Tracker 3-2 Marksman" for an original project
version 3.2 by Joe Marksman
b. Email Subject line example = "Marksman VAB 4.2" OR
"Marksman Optical Tracker 3-2" |
|
| |
c. VAB # and Title (font size 14 pt, placed in a clearly legible spot).
d. The author's name(s)
e. Date of last change
f. Descriptions of the major objective(s) of the worksheet
(can be the same as #2 in the formal lab report). |
|
| |
g. Any other brief descriptive notes explaining functionality
and logic of the worksheet's design that are required.
h. All sliders/ controls need to be logically and explicitly labeled
as to their function.
i. Lines connecting blocks (like outputs for R,G,B on video block) should be colored
appropriately so that the connection paths are easy to follow. |
|
| |
Remember:A happy grader is a generous grader :-) ... |
|
| |
...so make sure everything is clearly formatted and laid out. |
|
| |
|
|
