User Tools

Site Tools


Sidebar

projects

dsi0 (20170826)
wcp1 (20170826)
ael0 [faq] (20170830)
wcp2 (20170902)
sln0 [faq] (20170906)
wcp3 (20170909)
sln1 [faq] [metrics] (20170913)
wcp4 (20170916)
sll0 [faq] [metrics] (20170920)
wcp5 (20170923)
sll1 [faq] [metrics] (20170927)
wcp6 (20170930)
sll2 [faq] [metrics] (20171004)
wcp7 (20171007)
sll3 [faq] [metrics] (20171018)
sll4 [faq] [metrics] (20171018)
wcp8 (20171021)
dln0 [faq] [metrics] (20171025)
dll0 [faq] [metrics] (20171025)
wcp9 (20171028)
dll1 [faq] [metrics] (20171101)
wcpA (20171104)
dll2 [faq] [metrics] (20171108)
dls0 [faq] [metrics] (20171108)
wcpB (20171111)
dlq0 [faq] [metrics] (20171115)
wcpC (20171118)
dlt0 [faq] [metrics] (20171129)
haas:fall2017: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/fall2017/data/projects/ael0/faq.txt · Last modified: 2017/08/28 16:42 by wedge