User Tools

Site Tools


Sidebar

projects

pct0 (bonus; due 20190821)
dsi0 (due 20190821)
wcp1 (due 20190821)
pct1 (due 20190828)
wcp2 (due 20190828)
ael0 (due 20190904)
sln0 (due 20190904)
pct2 (due 20190904)
wcp3 (due 20190904)
sln1 (due 20190911)
pct3 (due 20190911)
wcp4 (due 20190911)
sll0 (due 20190918)
pct4 (due 20190918)
wcp5 (due 20190918)
sll1 (due 20190925)
pct5 (due 20190925)
wcp6 (due 20190925)
sll2 (due 20191002)
pct6 (due 20191002)
wcp7 (due 20191002)
sll3 (due 20191009)
sll4 (due 20191009)
pct7 (due 20191009)
wcp8 (due 20191009)
dln0 (due 20191023)
dll0 (due 20191023)
pct8 (bonus; due 20191023)
pct9 (due 20191023)
wcp9 (due 20191023)
dll1 (due 20191030)
pctA (due 20191030)
wcpA (due 20191030)
dll2 (due 20191106)
dls0 (due 20191106)
pctB (due 20191106)
wcpB (due 20191106)
dlq0 (due 20191113)
pctC (due 20191113)
wcpC (due 20191113)
dlt0 (due 20191120)
EoCE (due 20191211)
haas:fall2019:data:projects:ael0:faq

AEL0 FAQ

projeval tests aren't passing, is this important?

I plan to use projeval when I evaluate your project (since it nicely automates so many important tests I'd otherwise have to do by hand), so yes: it is rather important.

Be sure you are conforming to project specifications! All things that need to output to STDOUT vs. STDERR.

What is going on in a specific projeval test?

projeval test data is located under /usr/local/etc/eval (additional directories for course desig and project therein).

Eventually there will be directory names by the number of each test, and inside will be four files:

  • args.txt: additional arguments appending to the command-line when running your program
  • desc.txt: description of the test (likely what you see on projeval output)
  • in.txt: program input sent into your program at runtime (STDIN redirection)
  • out.txt: program output that is expected (when program is run with args and input sent in; usually the very last line of output)
haas/fall2019/data/projects/ael0/faq.txt · Last modified: 2017/08/28 16:42 by 127.0.0.1