Electrical test result archival
Notes by DGC, following discussions with PWP, Dave R, Graham B,
Jeff, Steve McM, Lars and others. Comments to DGC (errors are
13 February 2004: Note several new versions since last update of this news.
SctDAQWebLib.pl now at version 0.60: main changes are to include Strobe Delay
plot and to print the Gain/Noise/Offset table chip-by-chip (latter code is
09 June 2003: New script StoreIVLTT.pl; bug-fix to LocalVariables.pl
05 June 2003: SctDAQWebLib.pl version 0.53: various minor changes,
particularly to link LTT data/ps files in the html table. Please
upgrade! (Upgrade all files you use, including LocalVariables.pl,
14 March 2003: New, rewritten, version of SctDAQWebLib.pl and
MakeWebIndex.pl now available. Please upgrade!
SCTDAQ produces results files, PS files, and root files for each test
The results files appear in $sctvar/results
The UK-B scheme is to archive the results and ps files to secure
web-viewable storage at RAL.
Root files will be backed up locally at the individual testing
sites, and not all stored systematically at RAL.
We have defined a set of standard test sequences we expect to do in
Hybrid_Cold (cold=0C, 10h)
We will use these "test sequence names" as part of the directory tree
for the results/ps(=web) archive. The basic proposal is to have these
files archive in a tree with directory names like
These will be made in the individual testing sites and then be copied
to the central RAL store.
For the root files, there is no central store defined, but each
testing site is expected to keep their own backed-up archive of the
root files for production test sequences.
In addition to the standard test sequences above, which are needed for
the standard QA, it is often useful to make additional tests to verify
questionable points, etc.
The indexing software is set up to use the naming convention that
auxiliary tests done after any step Device_Test above should be called
So that, for example, any shorter tests done after the Module_Longterm
test would be called
Note that these tests themselves may be either Confirmation,
Characterisation or Longterm sequences, as needed for checking the
device on test.
Only a small number of perl scripts are needed:
copies results/ps files on Windows from $sctvar to a local
archive for the results/ps files; this latter archive has the
structure (***) shown above; this archive could be on a
local unix machine running samba, but the assumption is that it
is accessible directly on the windows filesystem.
See the next script if you need to store IVLTT results.
is a ***NEW*** (Jun 03) script. It does the same as
StoreTestResults.pl, but works for IVLTT tests (on their
own). Don't use it for other tests.
copies root files for a given run from $sctvar to a local
archive of root files; this might be on a remote windows or
unix machine, the current version assumes the backup is
accessible directly as a windows filessystem.
makes an index file from the results/ps files available in a
given directory; at RAL this would run on windows, at
Birmingham usually on unix. (This was the original script which
started all this...)
These scripts require two perl libraries, which should sit in the same
directory as the scripts (the scripts should normally be run after
chd'ing to that directory):
General utility routines (stuff in here actually does most of
Special site-specific routines
You will very likely need to edit this!!!
Some scripts are needed to make index pages of the individual tests
and modules, but these may be very simple. Similarly the famous
getfile.pl needs to be written for database access to the archived
For the moment, the following script is available:
Composes a top index.html file for a specified device. This is
a simple web page linking to individual test result pages.