This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
operations:documentation.ivs.mark5_module_selection [2016/08/31 04:06] Warren Hankey [So which module should I use?] |
operations:documentation.ivs.mark5_module_selection [2016/08/31 04:19] Warren Hankey [So which module should I use?] |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Choosing the right module for the experiment ====== | ====== Choosing the right module for the experiment ====== | ||
- | If possible, please try to record an entire experiment onto a single module. If it won't fit, please contact observatory staff - they will usually be able to put a module with enough space into the Mark 5. | + | If possible, please try to record an entire experiment onto a single module, most especially R4, CRDS, CRF, and R1 experiments. If it won't fit, please contact observatory staff - they will usually be able to put a module with enough space into the Mark 5. |
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: | 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: | ||
Line 7: | Line 7: | ||
===== Data requirement ===== | ===== Data requirement ===== | ||
- | On the AuScope IVS Module Allocation spreadsheet [[operations:log| Operations page]] there should be a data size indicated for the current experiment (2016 module allocation tab); otherwise refer to a similar historical experiment with a data size. On this spreadsheet the station staff also record which module has been allocated to the experiment and loaded in the Mk5. | + | On the [[operations:log|AuScope IVS Module Allocation spreadsheet]] there should be a data size indicated for the current experiment (2016 module allocation tab); otherwise refer to a similar historical experiment with a data size. On this spreadsheet the station staff also record which module has been provisionally allocated to the experiment and loaded in the Mk5. |
Also 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: | Also 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: | ||
Line 36: | Line 36: | ||
===== So which module should I use? ===== | ===== So which module should I use? ===== | ||
- | Rapid turnaround experiments, R1's and R4's should go on a module by themselves. Do not double up with other experiments. | + | Rapid turnaround experiments, R1's and R4's should go on a module by themselves, ditto CRDS and CRF; do not double up with other experiments. |
- | As a rule of thumb, the experiment should go on the smallest module it will fit on available in the Mark 5. | + | As a rule of thumb, the experiment should go on the smallest module it will fit on available in the Mark 5. Multiple experiments of other types (AUG, AOV, OHG, T2 etc.) can be recorded onto large modules where space allows |
==Doubling up== | ==Doubling up== | ||
Line 45: | Line 45: | ||
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. It is undesirable, but in a pinch the R1 can go on the same module with the last experiment, providing the R1 is the LAST experiment to be recorded (and there is enough disk space!). | 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. It is undesirable, but in a pinch the R1 can go on the same module with the last experiment, providing the R1 is the LAST experiment to be recorded (and there is enough disk space!). | ||
- | For example; there has been an Austral and there is still 3TB left on the module; there is no separate blank module to put the following R1 on; it is the middle of the night and there is no one at the observatory to load a blank module; the R1 will only use 2.5TB; then you can put the R1 on the same module after the Austral. | + | For example; there has been an Austral and there is still 3TB left on the module; there is no separate blank module to put the following R1 on; it is the middle of the night and there is no one at the observatory to load a blank module; the R1 will only use 2.5TB; then you may put the R1 on the same module after the Austral. In ordinary circumstances it would be preferred that the R1 go on a separate module. |