User Tools

Site Tools


operations:documentation.ivs.modules

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
operations:documentation.ivs.modules [2019/01/25 04:36]
Warren Hankey
operations:documentation.ivs.modules [2019/01/25 04:42] (current)
Warren Hankey
Line 2: Line 2:
  
 ==Allocating Modules== ==Allocating Modules==
-Check [[http://​131.217.63.180:​8000/​catalog/​ | Module and experiment library]] to see what size modules need to be loaded for the next couple of experiments. The Google spreadsheet ​is updated daily by a script, if the experiment is not listed it is because the schedule isn'​t ​yet ready, so look at a previous experiment of the same type in the spreadsheet ​for an idea of the data space required.+Check the [[http://​131.217.63.180:​8000/​catalog/​ | Module and experiment library]] to see what size modules need to be loaded for the next couple of experiments. The information ​is updated daily by a script, if the experiment is not listed it is because the observing notes file hasn'​t ​been posted ​, so look at a previous experiment of the same type in previous experiments ​for an idea of the data space required. If the sched or vex file is available, drudge the experiment and check the summary file which has a data total at the end.
  
-Make a note of the modules allocated to each experiment ​on the Google Spreadsheet as hbobserver+Make a note of the modules allocated to each experiment ​in the handover notes
-The staff at Ke and Yg check the spreadsheet ​and will also list the modules they have allocated.+The staff at Ke and Yg check the database ​and will also list the modules they have allocated.
  
-On a separate tab on the Google sheet is an inventory list  which should give some indication of the module ​stock at each station.+On the module ​page you can see all modules available and filter by station ​to see the inventory.
  
 R4's at Ke and Yg must go on a module by themselves, as they get shipped directly to Washington. R1's should also go on a module alone. R4's at Ke and Yg must go on a module by themselves, as they get shipped directly to Washington. R1's should also go on a module alone.
Line 25: Line 25:
 When Yg Ke modules first arrive in Hobart they are to be loaded into a spare Mark5, to be transferred from module disk-pack to a local storage location. When Yg Ke modules first arrive in Hobart they are to be loaded into a spare Mark5, to be transferred from module disk-pack to a local storage location.
 A Hb Ho experiment can be transferred to local storage immediately post experiment especially rapid R1 and R4. A Hb Ho experiment can be transferred to local storage immediately post experiment especially rapid R1 and R4.
-The [[http://fourier.phys.utas.edu.au/jmccallu/ajaxTest.html|Local Transfers]] page shows which experiments have been, or are currently uploading from module to local storage.+The  [[http://131.217.63.180:8000/catalog/ | Module and experiment library]] page shows which experiments have been, or are currently uploading from module to local storage.
  
 Once transferred to local storage the modules go into the tape room to be stored until correlated. Once transferred to local storage the modules go into the tape room to be stored until correlated.
Line 56: Line 56:
  
 ==Useful Scripts== ​ ==Useful Scripts== ​
-Some module utility scripts are available on ops1hb. list_correlation.py scans the master schedules pages for the last few years and looks for a correlation date on experiments involving our stations. It writes a list of correlated experiments to correlated.txt on ops1hb. If an experiment appears in this list e.g. <​code>​ cat correlated.txt | grep -i r1758 </​code>​ then the data can be erased from the module.+Some module utility scripts are available on ops1hb. ​Most of them update the database so the information is located on the experiment and module libray page. 
 +list_correlation.py scans the master schedules pages for the last few years and looks for a correlation date on experiments involving our stations. It writes a list of correlated experiments to correlated.txt on ops1hb. If an experiment appears in this list e.g. <​code>​ cat correlated.txt | grep -i r1758 </​code>​ then the data can be erased from the module.
  
 Also on ops1hb is data_summary.py which daily reads the master schedule, finds upcoming scheduled experiments with summary files, finds the data size for each station and writes this information to the Google module allocation spreadsheet. Also on ops1hb is data_summary.py which daily reads the master schedule, finds upcoming scheduled experiments with summary files, finds the data size for each station and writes this information to the Google module allocation spreadsheet.
/home/www/auscope/opswiki/data/pages/operations/documentation.ivs.modules.txt · Last modified: 2019/01/25 04:42 by Warren Hankey