This is an old revision of the document!
If possible, please try to record an entire experiment onto a single module. First, check to see how much data will be recorded, then check to see which modules are mounted in the Mark5, then choose one that is big enough. Here's how to do it:
At the end of the printed schedule summary is an estimate of the total amount of data that will be recorded for the experiment. For example, this experiment requires a tad under 1.4 TB:
. . . 203-1636b 6722 3C446 59 72 NEUTR 16:36:38 16:38:33 1:55 1354.0 * 203-1641 6739 0059+581 25 5 NEUTR 16:41:55 16:44:08 2:13 1357.7 * 203-1647 6756 1749+096 290 29 NEUTR 16:47:10 16:48:11 1:01 1362.0 * 203-1649 6773 0332-403 129 10 CCW 16:49:54 16:51:03 1:09 1363.9 * 203-1654 6790 1954-388 219 56 CCW 16:54:53 16:57:37 2:44 1366.1 * Total 1371.4 Gbytes Total number of scans: 400
Typing mk5=bank_set?
into eRemoteCtrl will return the VSNs of the modules currently loaded and their capacities in GB where the syntax is [Bank] [label]/[capacity]/[block size]
. Here's an example output:
2014.198.18:30:05.89/mk5/!bank_set? 0 : A : USN-0087/2000/1024 : B : HOB+0051/6000/1024 ;
So in this case Bank A is active (as it's listed first), it's label is USN-0087 and it has a capacity of 2000 GB. Bank B has HOB+0051 loaded and it's a 6000 GB module.
All R4, CRDS and CRF experiments need to be directly shipped to Washington, so put them on the smallest available module.
Everything else needs to be shipped to Hobart for e-transfer to the correlator. Therefore, two experiments, if they fit, can go on the same module. However, R1's do need to get to Hobart ASAP. Often there will be an R1 straight after another experiment. They can go on the same module, providing the R1 is the LAST experiment to be recorded to it (and there is enough disk space!).
So for example, if there has been an Austral and there is still 3TB left on the module, and the R1 will use 2.5TB, put them on the same module.