Starting the schedule

From $1

  • You do not have permission to set restrictions on this page.

Obtaining the observation schedule

Once the observation trigger has been given each station should download the corresponding schedule file (vex format). The schedules can be downloaded here (to be updated).

The vex file should be downloaded to the Mark6 recorder as user oper into the directory  /home/oper.

Translating the vex file

The downloaded vex file must be converted to a mark6 schedule file. As user oper execute:

/home/oper/bin/vex2xml.py -f {vexfile} -s {code} 

{vexfile}: file name of the vexfile
{code}: two letter station code of your local station. 

IMPORTANT: The station code must match the 2-letter code assigned to your station in the vex-file exactly (case sensitive).

This will produce a file named after the vexfile but having the .xml extension in the current directory.

Loading the schedule

There are two ways to execute the schedule

standard execution

as user oper execute:
M6_CC -f {xmlfile} 

{xmlfile}: the xml file produced in the previous step

Note: you can load the schedule at any time prior to the observation slot.

scripted execution

the script start_eht.py will execute the schedule and in addition will automatically perform other tasks (e.g. 2-bit requantization) in the scan gaps.

download the script on your mark6 and put it to /home/oper/bin

as user oper:

start_eht.py {schedule.xml}

start_eht.py --help will display additional options
Tags: (Edit tags)
  • No tags
FileSizeDateAttached by 
start_eht.py
Version 1.1
5.44 kB09:42, 22 Mar 2015Helge RottmannActions
Comments (0)
You must login to post a comment.

 
Powered by MindTouch Core