This wiki is not maintained! Do not use this when setting up AuScope experiments!

Differences

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

--- operations:documentation.ivs.modules [2017/04/05 01:46]
Warren Hankey
+++ operations:documentation.ivs.modules [2019/01/25 04:42] (current)
Warren Hankey
@@ Line 1: / Line 1: @@
-===Managing Mark5 Media===
+====Managing Mark5 Media====
-Check the Google module allocation spreadsheet, and the Master schedule to see what modules need to be loaded for the next couple of experiments.
+==Allocating Modules==
+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 in the handover notes.
+The staff at Ke and Yg check the database and will also list the modules they have allocated.
+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.
@@ Line 9: / Line 16: @@
  e.g. r4783hb is recorded, followed by R1784hb on the same module.
-Place a red sticker on the module, and label the experiment name clearly.
+It can be useful to make a note on the Handover Notes page for the experiment of which module to use, so the observer is reminded. You may wish to send the starting observer an email also.
+==Post Experiment==
+Place a red sticker on the module when it has been recorded to, and label the experiment name clearly.
+Modules from Yg and Ke are posted to Hobart, except for R4 experiments, shipped directly to Washington.
+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.
+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.
+The data is then uploaded from the local storage to Bonn or Washington. See the [[operations:documentation.ivs.etransfer|Transfers]] page for information on the details of this process.
+==Reusing Modules==
+Only when an experiment has been correlated (search IVS email, or use the useful scripts below) can the data be deleted from module. Locate the data module by experiment label in the the tape room.
+With Dimino running, ensure that the module only contains the correlated experiment data. The labels may be incomplete and not always to be trusted. On the Mark5 command line use <code> DirList | less </code> to scroll through  the list of scans on the disk to check  before you delete.
+When you are sure, double check you have the correct module and start tstDIMino at the command line, turn off the data safety with <code> protect=off </code> and then <code> reset=erase </code> to clear the data from the module. Check free space and vsn are as expected with <code> rtime?  </code> and <code> vsn?  </code>. Take the red sticker and experiment label off the module, it is ready for re-use.
+==Shipping Modules==
+Once data is deleted and modules are ready for re-use they need to be shipped to Yg and Ke, with enough held at Hobart to cover upcoming experiments. Modules need to be shipped back to Yg Ke at the same rate as they arrive or greater. Use [[http://www.freightmaster.startrack.com.au/fm2/mclient/main.html#|Star Track Freightmaster]] (say YES to java applet requests) and log in as Brett; login details are posted on the module rack in the tape room.
+The addresses for Yg Ke and Cd are in the address book on Frieghtmaster. Create a Consignment > New Consignment, Consignment Type = Standard,  for each addressee. The Reference should be in the form "318-"<station><no. of items>"blank". The leading "318-" being the most important.
+Under the Article Information tab choose, Service Level = OFF-PEAK . Enter the item information; number of items, total weight (no. of items x 10 [kg]), Package contains = "Computer data disks" and the dimensions as follows;
+for module box item in [cm], 34 wide, 48 long, 29 high and each weighs 10 [kg]. With all fields entered hit Print.
+Create a single booking for the day to be picked up, enter ready pick-up time and close of business time for the day. You don't need to print the confirmation of booking.
+Finally when all consignments are done and you have all labels attached and visible on boxes, go to Manifest, and choose all Consignments to be collected at the booking time. Print the form and sign the declaration of no dangerous goods, to give to the driver.
-When an experiment has been correlated (search IVS email, or use the useful scripts below) the data can be deleted from module. With Dimino running, ensure that the module only contains the correlated experiment data. The labels may be incomplete and not always to be trusted. On the Mark5 command line use <code> DirList | less </code> to scroll through  the list of scans on the disk to check  before you delete.
+To pack for shipment, re-use a box from the tape room, removing all old bar codes and address labels. Screw the sheet metal transport covers on the modules and tape the box up with the item shipping label printed from Freightmaster. Tape, screws et. for packaging found under large white board in control room.
-When you are sure, double check yoiu have the correct module and start tstDIMino at the command line, turn off the data safety with <code> protect=off </code> and then <code> reset=erase </code> to clear the data from the module. Check free space and vsn OK with <code> rtime?  </code> and <code> vsn?  </code>. Take the red sticker and experiment label off the module, ready for re-use.
 ==Useful Scripts==
-Some 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 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.

AuScope VLBI Operations Wiki

User Tools

Site Tools

This wiki is not maintained! Do not use this when setting up AuScope experiments!

Differences

Page Tools