Page History

...

• It checks that calibration files exist where they are supposed to.
• It checks that the time you give it is valid.  If it is in the past or more than 24 hours in the future, it will give an error.  The 24 hours is an arbitrary limit just to make sure you're got giving it a very wrong date by accident.
• It checks if a calibration file with the same name is already in the database so you can't accidently accidentally enter a duplicate a file.
• For tracker files, it checks that the version number in the file name is higher than the current version. 
• For the other non-tracker files, it checks that the file name numbers are 6 greater than for the previous calibration file values, e.g, pedavr_658m_662m.xml should be followed by pedavr_664m_668m.xml .For non-tracker files, it and checks that the two numbers in the file name are 4 apart. Each file is meant to cover 6 megaseconds and are created from three 2 Ms files, so 240m-244m is made of the 240m, 242m, and 244m files.  These two checks are taken from information on the file name on the page Working Group on Calibration Issues. They can be relaxed if they end up being too strict.

The scripts are can be access in the conda environment called "calibrator" that is available on both the rhel6 and centos7 machines. This environment is also available on the SDF (with a slightly different activation command), but since the calibration files aren't (currently) accessible from the SDF, the update script won't work (it will give an error).  The two database viewing scripts will work, though.

...