This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
operations:documentation.ivs.mark5 [2011/05/16 00:55] yme [Setting up and configuring the Mark5 software] |
operations:documentation.ivs.mark5 [2013/02/25 01:16] Jamie McCallum |
||
---|---|---|---|
Line 8: | Line 8: | ||
===== Setting up and configuring the Mark5 software ===== | ===== Setting up and configuring the Mark5 software ===== | ||
- | Log in to mk5hb as oper:<code>ssh oper@mk5hb</code> | + | Log in to Mark5 you want to set up (either mk5hb, mk5ke or mk5yg) as oper. //Do this from within the pcfs[hb|ke|yg] VNC session so that the Mark5 software will continue to run even if the network link from Hobart to the telescope goes down.// e.g. <code>ssh oper@mk5hb</code> |
+ | There are two versions of the recording software currently in use. The original software is ''dimino'' which can support modules of up to 8 TB capacity (current used by Hb and Yg) and ''DIMino'' which supports 16 TB modules (in use at Ke). | ||
+ | |||
+ | Hb, Yg: | ||
First check if the dimino program is running: | First check if the dimino program is running: | ||
<code>ps -ef | grep dim</code> | <code>ps -ef | grep dim</code> | ||
If not, start it with | If not, start it with | ||
<code>dimino -m0&</code> | <code>dimino -m0&</code> | ||
+ | |||
+ | Ke: | ||
+ | First check if the DIMino program is running: | ||
+ | <code>ps -ef | grep DIM</code> | ||
+ | If not, start it with | ||
+ | <code>DIMino -m0&</code> | ||
+ | |||
+ | |||
===== Synchronising the Mark5 Clock ===== | ===== Synchronising the Mark5 Clock ===== | ||
- | The following steps are done through the Field System. If not already started, start the Field system software on pcfshb by starting a new terminal on pcfshb, and type: | + | The following steps are done through the Field System. If not already started, start the Field system software on pcfs[hb|ke|yg] by starting a new terminal in the VNC session on pcfs[hb|ke|yg], and type: |
<code>fs</code> | <code>fs</code> | ||
An ''oprin'' window will appear and Field System commands are typed here. | An ''oprin'' window will appear and Field System commands are typed here. | ||
Line 34: | Line 45: | ||
look for ''syncerr_eq_0'', and that the final number is less than ~5 ms. | look for ''syncerr_eq_0'', and that the final number is less than ~5 ms. | ||
- | If you see something like ''syncerr_gt_3'' then ''fmset'' may need to be run to synchronise the clocks. To do this, open a terminal on pcfshb, and type | + | If you see something like ''syncerr_gt_3'' then ''fmset'' may need to be run to synchronise the clocks. To do this, open a terminal on pcfs[hb|ke|yg], and type |
<code>fmset</code> | <code>fmset</code> | ||
When the interface appears, type | When the interface appears, type | ||
Line 56: | Line 67: | ||
Check the last numbers are the correct date at the start of the scan, duration, the data rate (should be 256 for the 8MHz mode, 128 for the 4 MHz mode) and 0 at the end for no problems. Then plot an autocorrelation from the data: | Check the last numbers are the correct date at the start of the scan, duration, the data rate (should be 256 for the 8MHz mode, 128 for the 4 MHz mode) and 0 at the end for no problems. Then plot an autocorrelation from the data: | ||
<code>postob</code> | <code>postob</code> | ||
+ | To clear the disk module, ONLY IF YOU'RE CERTAIN there is no data already on the disk! | ||
+ | <code> mk5=protect=off; mk5=reset=erase </code> | ||
[[operations:monitoring_autocor|Check that the spectra are OK]]. | [[operations:monitoring_autocor|Check that the spectra are OK]]. | ||
If there are dropped or strange-looking bands, the [[hardware:dbbc.reprogram|DBBC may need reprogramming]]. | If there are dropped or strange-looking bands, the [[hardware:dbbc.reprogram|DBBC may need reprogramming]]. |