Lab46 Wiki

User Tools

Site Tools

You are here: start » notes » discrete » fall2022 » projects » bdb0
notes:discrete:fall2022:projects:bdb0

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
notes:discrete:fall2022:projects:bdb0 [2022/09/13 18:59] – [VERIFICATION] hcordellnotes:discrete:fall2022:projects:bdb0 [2022/09/14 23:30] (current) – [PROGRAM] zswartwo
Line 22: Line 22:
 *For anybody interested in editing the wiki page, here is the dokuwiki user guide: https://www.dokuwiki.org/wiki:syntax#basic_text_formatting -Ash *For anybody interested in editing the wiki page, here is the dokuwiki user guide: https://www.dokuwiki.org/wiki:syntax#basic_text_formatting -Ash
 =====PROGRAM===== =====PROGRAM=====
 +When checking to verify that one's project functions as intended, it should be borne in mind that the verify program included in the grabit does not work, so it will ultimately be up to you to check the program. Ways this may be done include using the diff and xxd commands, and testing your project with with the files included in the in sub-directory. I myself found it useful to custom-create a few files in order to ensure certain edge cases occurred, such that they may be tested for (bear in mind this project is a debugger to assist us in future projects, so leaving flaws is likely sub-optimal). 
 =====OUTPUT SPECIFICATIONS===== =====OUTPUT SPECIFICATIONS=====
  
Line 63: Line 63:
 When running the program with two SAME files, the program should display nothing. When running the program with two SAME files, the program should display nothing.
 The normal process of using **make check** to check your file against the desired result won't work in this case. The verify file is that of a different year when different specifications were desired. Running it this time around will lead you to many mismatches and headaches. You can check your output against the pictures provided above as a general guideline but other than that it is essential that if you have any questions to just ask in discord instead of guessing and hoping it is what is desired. Most of the desired output is already located on the project page. The normal process of using **make check** to check your file against the desired result won't work in this case. The verify file is that of a different year when different specifications were desired. Running it this time around will lead you to many mismatches and headaches. You can check your output against the pictures provided above as a general guideline but other than that it is essential that if you have any questions to just ask in discord instead of guessing and hoping it is what is desired. Most of the desired output is already located on the project page.
 +
 +=====Approaches=====
 +I think there are two approaches people have taken with the display of information with this project:
 +\\
 +{{:notes:discrete:fall2022:projects:screen_shot_2022-09-13_at_6.45.45_pm.png?800|}}
 +\\
 +===or===
 +\\
 +{{:notes:discrete:fall2022:projects:screenshot_2022-09-13_185444.png?800|}}
 +\\
 +The main thing of note here is the position of the first mismatched bit in its line. In the first implementation, bytes are displayed chronologically, with the leftmost bit always being a multiple of 16. The second implementation has the mismatched bit always in the leftmost position and never in the middle of a line. The approach you take comes down to personal preference as is with a lot of this project, since we don't have a strict verify script to check output with.
notes/discrete/fall2022/projects/bdb0.1663095563.txt.gz · Last modified: 2022/09/13 18:59 by hcordell

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