This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
operations:documentation.test_recording_fs9.10.5 [2012/11/13 02:59] Jim Lovell created |
operations:documentation.test_recording_fs9.10.5 [2014/01/29 21:03] (current) ctrenham added RD expts for things that need the checkmk5 procedure |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Making a Test Recording ====== | ====== Making a Test Recording ====== | ||
- | Now make a test recording using the Mark5. This is done through the Operator Input window. | + | Now make a test recording using the Mark5. This is done through eRemoteControl or the Operator Input window. |
<code>disk_record=on | <code>disk_record=on | ||
Line 12: | Line 12: | ||
The output should appear in the pcfs[hb|ke|yg] VNC session and within a minute on the [[http://auscope.phys.utas.edu.au/spectra.php|Autocorrelation Spectra web page]]. Good data should contain quite flat bandpasses and zero phase. See [[operations:monitoring_autocor|autocorrelation spectra plots]] for an example and what problems to look out for. If there are dropped or strange-looking bands, the [[hardware:dbbc.reprogram|DBBC may need reprogramming]]. | The output should appear in the pcfs[hb|ke|yg] VNC session and within a minute on the [[http://auscope.phys.utas.edu.au/spectra.php|Autocorrelation Spectra web page]]. Good data should contain quite flat bandpasses and zero phase. See [[operations:monitoring_autocor|autocorrelation spectra plots]] for an example and what problems to look out for. If there are dropped or strange-looking bands, the [[hardware:dbbc.reprogram|DBBC may need reprogramming]]. | ||
- | To clear the disk module, ONLY IF YOU'RE CERTAIN there is no useful data (e.g. from a previous experiment) already on the disk! | + | Note: The checkmk5 procedure occurs before this, but just in case it hasn't been done: |
+ | For AUST and RD experiments, to get autocorrelation happening, the different bit rate etc will mean you need to redefine checkmk5 procedure from usual. Edit checkmk5 using pfmed. Look for older AUST proc file for example, define checkmk5 as... | ||
+ | <code>define checkmk5 13261230216x | ||
+ | sy=/home/oper/bin/auto_cor_check_web_2bit_8mhz_hb.sh & | ||
+ | scan_check | ||
+ | mk5=get_stats? | ||
+ | mk5=status?</code> | ||
+ | |||
+ | Editing instructions are here: [[operations:documentation.ivs.drudg_9.10.5]] | ||
+ | |||
+ | <note warning>DO NOT ERASE TEST SCANS UNLESS NECESSARY. They don't actually need to be deleted as they do not get picked up in transfers and erasing modules is a risky business!</note> | ||
+ | |||
+ | Many of the larger disks are now being used for more than one experiment to conserve modules, particularly the 16TB. | ||
+ | |||
+ | To clear the disk module, **ONLY IF YOU'RE CERTAIN there is no useful data** (e.g. from a previous experiment) already on the disk! | ||
<code>mk5=protect=off | <code>mk5=protect=off | ||
mk5=reset=erase </code> | mk5=reset=erase </code> |