Electrical test result archival

Latest news

Basics

SCTDAQ produces results files, PS files, and root files for each test
sequence. 

The results files appear in $sctvar/results
    PS                      $sctvar/ps
    root                    $sctvar/data

UK-B scheme

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
the UK:

At Birmingham:
  Hybrid_Initial           (characterisation)
  Hybrid_Longterm          (longterm)
  Hybrid_Cold              (cold=0C, 10h)
  Hybrid_Completion        (confirmation)
 
At RAL:
  Hybrid_Reception         (confirmation)
  Module_Initial           (confirmation)
  Module_Completion        (characterisation)
 
At Universities:
  Module_Reception         (characterisation)
  Module_Longterm          (longterm)
 
At Oxford:
  Module_Acceptance        (confirmation)                                          

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

$archive/20220330200001/Hybrid_Initial/*.ps                 (***)
                                       *.txt
                                       index.html

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.

Auxiliary Tests

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

Device_Test_Retest1
Device_Test_Retest2
Device_Test_Retest3 ...

So that, for example, any shorter tests done after the Module_Longterm
test would be called

Module_Longterm_Retest1
Module_Longterm_Retest2 etc

Note that these tests themselves may be either Confirmation,
Characterisation or Longterm sequences, as needed for checking the
device on test.

Processing scripts

Only a small number of perl scripts are needed:

1. StoreTestResults.pl
       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.

2. BackupRawData.pl
       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.

3. MakeWebIndex.pl 
       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...)

4. UploadToRAL (not yet available)
       copies an the web directory (results/ps plus index.html file)
       up to the central repository at RAL.

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):

SctDAQWebLib.pl
       General utility routines (stuff in here actually does most of
       the work...)

LocalVariables.pl
       Special site-specific routines
       You will very likely need to edit this!!!

Web scripts

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
files. 

For the moment, the following script is available:

MakeModulePage.pl
       Composes a top index.html file for a specified device. This is
       a simple web page linking to individual test result pages.