Blog from December, 2004

here's a first idea on what the new schema might look like:

Release Table:

SystemTest Table:

Metadata Table:

OutputFile Table:

Release Table contains an entry for each RM checked out package.
SystemTest table contains all the test done for a specific entry in Release Table
Metadata table contains all the metadata of a specific test in SystemTest
OutputFile contains the files written out for a specific SystemTest.

I'm not sure how the triggering of it will work. I am considering making it a script that's part of the RM set of scripts which get executed in order.

Believe it or not there is some documentation of the old system. It's at

http://www-glast.slac.stanford.edu/software/SysTests/

Tony's summary of the kick-off system tests meeting on 12-15-04.

• Would like history plots from database (e.g time history of releases, or scatter plots of one value vs another).
• Inline display of comments on histograms.

Summary of Julie's December 7 email outlining improvements to the existing ASP based system tests front end.

• Allow selection of which GlastRelease or EngineeringModel version to look at with only one submit button.
• Reformat page which lists the list of tests for a given release to make each line narrower, so that more tests can be viewed in the same screen (this could be done by altering the "plot histos get tuples" box).
• In the datafiles section, make a link to the log file and the merit tuple, and make the systest name lead people to the plot histos interface.
• Show people how to download the raw root files from this page (they are always in the same dir as the tuple).
• Allow the threshold value to change and recalc the pass/fail values on the fly.
• Add a button to change the test that decides on pass/fail (i.e. to use something other than KS).
• Disable the row ("gray it out") if the status of a system test is pending or failed.
• If the entry is "NA" in the histogram_file field, then there should not be a link to "plot histos".
• Show histos that fail when one clicks on the fail button.
• Allow user to specify number of plots per page in addition to the meta data that is already displayed.
• Make plots clickable so that clicking on one would lead you back to the single plot page where one could do more fiddling.
• Use the axis labels from the ROOT files.
• Display the values of the under/overflow bins.
• Display values of the statisical comparison test(s).
• Add facility to rebin the histos (into bigger bins), something akin to what you get with a TH1F::Rebin() in root.
• Allow user to flag histos as being different but deemed not a problem (so that we can move towards a method for declaring a release to have passed or failed the systests).