Recent Changes - Search:

HomePage

LBA

Mt Pleasant 26m

Ceduna 30m

Mt Pleasant 14m

Ceduna-Hobart Interferometer

Schedules

AuScope

PmWiki

edit SideBar

Pulsar Observing

MtPleasant26m.PulsarObserving History

Hide minor edits - Show changes to markup

February 03, 2017, at 03:43 AM by Jim Palfreyman -
Changed lines 128-129 from:
‘’‘./track_3C353_O
to:
./track_3C353_O
February 03, 2017, at 03:42 AM by Jim Palfreyman - Updated
Changed lines 113-114 from:
to:
  • Window 1, top far-right has a newsmerd window, type:
at -f fire_cal 1200
  • or some time during your observation. This fires the noise diodes for polarisation calibration.
February 03, 2017, at 03:40 AM by Jim Palfreyman - Updated
Added lines 87-114:

Observing

  • Move onto Vela. In Window 1/2, bottom right type:
./track vel15183
  • Now to observe until Vela sets, in Window 1/2 top left:
./record 2015_183 1376 set
  • Or for something shorter:
./record 2015_183 1376 1h
  • Note that 19h of observation takes about 4 Tb of disk space.
  • We are now recording. If you have set the levels up correctly, the channel figures should be reading 33,33,17,17 or something close.
  • In the other hovsi window (Window 1/2, top right) type:
./agc 2015_183 1376 (but use the date and frequency you are recording in!)
  • This will pull data from the last fully recorded 10 second data file and check the levels. If incorrect, it will adjust the attenuators on Palfreyman’s Delight automatically. This is repeated every 5 minutes. This is automatically killed when recording is finished.
  • In window 1/2 (bottom left) type:
./stow set (as oper@hobart if it’s not there).
  • This waits until Vela sets then kills the onsource script and parks the dish when the experiment is over. Again very important so Vela is not tracked into the limits as it sets. Note that ./stow 5h 50m will wait 5h 50m before ending the experiment.
Changed lines 119-124 from:
  • We now need to the relevant directories on hovsi for calibration and observation. In the Window 1/2 on newsmerd there is a hovsi terminal at top left, type:
df -h

and make sure /mnt/sirius16 is present.

  • If this directory is not mounted, say after a power failure, then (as root) type:
to:
  • If after a power failure, /mnt/sirius16 is not mounted then (as root) type:
Changed lines 122-128 from:
  • You now need the year (e.g. 2014), day-of-year (e.g. 176) and observation frequency (e.g. 1376). Type the following commands:
to:
  • Move to the calibration source:
‘’‘./track_3C353_O
  • On newsmerd in jimp, type in without <CR>:
./fire_cal
  • You now need the year (e.g. 2014), day-of-year (e.g. 176) and observation frequency (e.g. 1376). Type the following command:
Changed lines 131-172 from:
  • For calibration we need to temporarily move off Vela. In the Field System (Window 5) type:
source=velaoff,083521,−470000,2000
  • We now need to run the noise diodes for a calibration. In a newsmerd window type:
calu -m sam26m (and press return when prompted with rakbus.)
samtest -c 5 -d 0.5 -i 0 -n 1 -s 120 -f 30 (followed by sam26m but DON’T press return yet!)
  • Now on hovsi (Window 3, top left):
cd /mnt/sirius16/pulsar/J0835–4510_R/2014_176/1376
vsib_record -m 2 -w 64 -f 10s -t 90s -o CAL_J0835–4510 (but press Return on samtest first, then this one.)
  • Wait until vsib_record has finished. samtest will follow soon after.

Observing

  • Move back onto Vela. In the Field System (Window 5) type:
source=vela,083521,−451035,2000
  • Now to observe until Vela sets:
~/jimp/record 2015_183 1376 set
  • Or for something shorter:
~/jimp/record 2015_183 1376 1h
  • Note that 19h of observation takes about 4 Tb of disk space.
  • We are now recording. If you have set the levels up correctly, the channel figures should be reading 33,33,17,17 or something close.
  • In another hovsi window (Window 3, top right) type:
~/jimp/agc 2015_183 1376 (but use the directory you are recording in!)
  • This will pull data from the last fully recorded 10 second data file and check the levels. If incorrect, it will adjust the attenuators on Palfreyman’s Delight automatically. This is repeated every 5 minutes. This is automatically killed when recording is finished.
  • In window 3 (bottom left) type:
~/jimp/stow set (as oper@hobart if it’s not there).
  • This waits until Vela sets then kills the onsource script and parks the dish when the experiment is over. Again very important so Vela is not tracked into the limits as it sets. Note that ~/jimp/stow 5 50 will wait 5h 50m before ending the experiment.
to:
  • Now hit <CR> on fire_cal, followed by record_fluxcal. Wait 90 sec.
  • Now we need to temporarily move north of the source. In Window 1/2, bottom right type:
./track_3C353_N
  • Then repeat fire_cal and record_fluxcal commands above, but change it to 3C353_N
  • Then repeat using 3C353_S
February 03, 2017, at 03:26 AM by Jim Palfreyman - Updated
Added lines 87-90:

Flux calibration

  • This only needs to be done occasionally or when the setup has changed.
Changed lines 92-95 from:
cd /mnt/sirius16/pulsar
  • If these directories are not mounted, say after a power failure, then the special interface to sirius may need to be configured (as root):
ifconfig eth0 192.168.1.2 (unlikely to need this)
to:
df -h

and make sure /mnt/sirius16 is present.

  • If this directory is not mounted, say after a power failure, then (as root) type:
Changed lines 100-102 from:
mkdir J0835–4510_R/2014_176
mkdir J0835–4510_R/2014_176/1376
to:
./record_fluxcal 3C353_O 2014_176 1376
Added lines 116-118:

Observing

February 03, 2017, at 03:21 AM by Jim Palfreyman - Updated
Changed lines 48-49 from:
  • Select the receiver using the OTTER interface on Window 3 (run ./OTTER_interface.sh on newsmerd if you cannot find it). Most observations will be in L-band which is receiver 2. Wait for the platform to move into place (this can be checked on the live page). Make sure it is set to Direct and Quad OUT. The noise diodes should also be off.
to:
  • Select the receiver using the OTTER interface on Window 3, bottom right (run ./OTTER_interface.sh on newsmerd if you cannot find it). Most observations will be in L-band which is receiver 2. Wait for the platform to move into place (this can be checked on the live page). Make sure it is set to Direct and Quad OUT. The noise diodes should also be off.
Changed line 54 from:
  • Set the local oscillators. This will be in window 3 top middle, (or run ./oscillator_gui.sh on oper@hobart if you cannot find it). For an observation at 1376 MHz (a good spot currently) the settings are:
to:
  • Set the local oscillators. This will be in window 3 top left, (or run ./oscillator_gui.sh on oper@hobart if you cannot find it). For an observation at 1376 MHz (a good spot currently) the settings are:
Changed line 60 from:
  • Configure Palfreymans Delight. This will be in window 3 bottom right, (or run ./PalfreymansClient.sh on newsmerd if you cannot find it). You will want:
to:
  • Configure Palfreymans Delight. This will be in window 3 bottom left, (or run ./PalfreymansClient.sh on newsmerd if you cannot find it). You will want:
Changed lines 69-71 from:
  • Point the telescope to Vela (visible when LMST is between 23:07:44 and 18:04:00). In the window to the right of the (oper@hobart) field system type (assuming its 2015 day 183):
~/jimp/track vel15183
to:
  • Point the telescope to Vela (visible when LMST is between 23:07:44 and 18:04:00). In window 1, bottom right (oper@hobart) type (assuming its 2015 day 183):
cd jimp
./track vel15183
Changed lines 79-80 from:
  • Configure the BG3 cable. Behind cabinet 6 make sure the rainbow cable 1 goes into Ch 1 and 2 goes into Ch 2. The small cable with the large connector should go into Recorder Out. The other end of those three cable should go directly to the back right connecter on the board of the vsib box.
to:
  • Configure the BG3 cable. Behind cabinet 6 make sure the rainbow cable 1 goes into Ch 1 and 2 goes into Ch 2. The small cable with the large connector should go into Recorder Out. The other end of those three cable should go directly to the back right connector on the board of the vsib box.
Changed lines 83-84 from:
  • Type P for Profile and L for Load and enter PSR64_N.PRO. After getting Waiting for Setup, press S. If you get a communications error then try loading VSOP_HO.PRO and then reload PSR64_N.PRO. If there are still issues, close down the DAS software and re-launch with VSOP_HO.PRO, then PSR64_N.PRO.
to:
  • Type P for Profile and L for Load and enter PSR64_N.PRO. After getting Waiting for Setup, press S. If you get a communications error then try loading VSOP_HO.PRO, do Setup, and then reload PSR64_N.PRO. If there are still issues, close down the DAS software and re-launch with VSOP_HO.PRO, then PSR64_N.PRO.
Changed line 91 from:
ifconfig eth0 192.168.1.2
to:
ifconfig eth0 192.168.1.2 (unlikely to need this)
Changed lines 353-380 from:

Once data is flowing to a storage area on hovsi, you can begin processing it with the Origin. See Aidan for details as the system is still somewhat experimental.

to:

Once data is flowing to a storage area on hovsi, you can begin processing it with the Origin. See Aidan for details as the system is still somewhat experimental.

  • We now need to the relevant directories on hovsi for calibration and observation. In the Window 1/2 on newsmerd there is a hovsi terminal at top left, type:
cd /mnt/sirius16/pulsar
  • If these directories are not mounted, say after a power failure, then the special interface to sirius may need to be configured (as root):
ifconfig eth0 192.168.1.2 (unlikely to need this)
mount /mnt/sirius16
  • You now need the year (e.g. 2014), day-of-year (e.g. 176) and observation frequency (e.g. 1376). Type the following commands:
mkdir J0835–4510_R/2014_176
mkdir J0835–4510_R/2014_176/1376
  • For calibration we need to temporarily move off Vela. In the Field System (Window 5) type:
source=velaoff,083521,−470000,2000
  • We now need to run the noise diodes for a calibration. In a newsmerd window type:
calu -m sam26m (and press return when prompted with rakbus.)
samtest -c 5 -d 0.5 -i 0 -n 1 -s 120 -f 30 (followed by sam26m but DON’T press return yet!)
  • Now on hovsi (Window 3, top left):
cd /mnt/sirius16/pulsar/J0835–4510_R/2014_176/1376
vsib_record -m 2 -w 64 -f 10s -t 90s -o CAL_J0835–4510 (but press Return on samtest first, then this one.)
  • Wait until vsib_record has finished. samtest will follow soon after.
  • Move back onto Vela. In the Field System (Window 5) type:
source=vela,083521,−451035,2000
March 28, 2016, at 11:39 PM by Jim P - Small change
Changed lines 11-12 from:
vncviewer newsmerd:1 (the usual hungry container password)
to:
vncviewer newsmerd:1
March 28, 2016, at 11:39 PM by 131.217.62.2 -
Changed lines 35-36 from:
vncviewer newsmerd:1 (the usual hungry container password)
to:
vncviewer newsmerd:1
July 03, 2015, at 04:13 AM by Jim P -
Changed lines 13-16 from:
  • Go to window 3 (or window 1) where most of the action happens. The top left window is where the recording on hovsi happens. Use ^C to stop that.
  • The bottom left window is sleeping waiting for observing to finish. Use ^C to stop the sleep. The telescope used to park when doing this. It no longer does.
to:
  • Go to window 1 or window 2 where the action happens. One window will be running and the other may be scheduled to run. If you have a shell prompt then nothing is waiting. You pretty much have to ^C each window that is not at a shell prompt.
  • The top left window is where the recording on hovsi happens. Use ^C to stop that.
  • The bottom left window is sleeping waiting for observing to finish. Use ^C to stop the sleep. The telescope used to park when doing this. It no longer does. It is vital for your experiment that you stop this.
Added lines 21-22:
  • Bottom right has a window running onsource. Use ^C to stop this.
Changed lines 26-29 from:
  • Next to the fs (or window 1, bottom right) is a window running onsource. Use ^C to stop this.
  • Email Jim (jim77742@gmail.com) to let him know what you’ve done.
to:
  • Email Jim (jim77742@gmail.com) to let him know what you’ve done.
Changed line 39 from:
  • Window 3 typically has all the main windows required and window 5 has the Field System which is also needed. If the field system is not running type:
to:
  • Window 1 or 2 typically has all the main windows required and window 5 has the Field System which is also needed. If the field system is not running type:
Changed line 42 from:
  • If the cryo temps aren’t showing regularly (not important for pulsars, but for others using S/X) type:
to:
  • If the cryo temps aren’t showing regularly in the field system (not important for pulsars, but for others using S/X) type:
Changed line 69 from:
  • Point the telescope to Vela (visible when LMST is between 00:00 and 17:00). In the window to the right of the (oper@hobart) field system type (assuming its 2015 day 183):
to:
  • Point the telescope to Vela (visible when LMST is between 23:07:44 and 18:04:00). In the window to the right of the (oper@hobart) field system type (assuming its 2015 day 183):
Changed line 86 from:
  • We now need to the relevant directories on hovsi for calibration and observation. In the Window 3 on newsmerd there is a hovsi terminal at top left, type:
to:
  • We now need to the relevant directories on hovsi for calibration and observation. In the Window 1/2 on newsmerd there is a hovsi terminal at top left, type:
Changed lines 124-127 from:
~/jimp/agc 2015_183 1376 19 (but use the directory you are recording in and the proper length in hours!)
  • This will pull data from the last fully recorded 10 second data file and check the levels. If incorrect, it will adjust the attenuators on Palfreyman’s Delight automatically. This is repeated every 5 minutes. Make sure you put the time in hours (used above) so this script stops. If you don’t do this properly it will possibly affect other people’s experiments.
to:
~/jimp/agc 2015_183 1376 (but use the directory you are recording in!)
  • This will pull data from the last fully recorded 10 second data file and check the levels. If incorrect, it will adjust the attenuators on Palfreyman’s Delight automatically. This is repeated every 5 minutes. This is automatically killed when recording is finished.
Changed lines 139-152 from:

As an example, Vela is currently set and it is day 179 in 2014.

  • In window 5, just to the right of the field system (hobart) type:
date; ~/jimp/velars -s -d; date; ~/jimp/track vel15184
  • In window 3 top left (hovsi) type:
date; ~/jimp/velars -s -d; date; ~/jimp/record 2015_184 1376 set
  • In window 3 top right (hovsi) type:
date; ~/jimp/velars -s -d; date; ~/jimp/agc 2015_184 1376 19
  • In window 3 bottom left (hobart) type:
date; ~/jimp/velars -s -d; date; ~/jimp/stow set
to:

As an example, Vela is currently set and it is day 184 in 2015.

  • In window 1/2 bottom right type:
date; ~/jimp/velars -s -d; date; sleep 10s; ~/jimp/track vel15184
  • In window 1/2 top left (hovsi) type:
date; ~/jimp/velars -s -d; date; sleep 10s; ~/jimp/record 2015_184 1376 set
  • In window 1/2 top right (hovsi) type:
date; ~/jimp/velars -s -d; date; sleep 10s; ~/jimp/agc 2015_184 1376 19
  • In window 1/2 bottom left (hobart) type:
date; ~/jimp/velars -s -d; sleep 10s; date; ~/jimp/stow set

The 10 sec sleep is just to avoid a race condition where for 1 second, vela is up and down at the same time!

July 02, 2015, at 05:44 AM by Jim P -
Changed lines 115-116 from:
‘’‘~/jimp/record 2015_183 1376 1h
to:
~/jimp/record 2015_183 1376 1h
July 02, 2015, at 05:42 AM by Jim P -
Deleted lines 39-43:
  • Start a new log file. In the Field System type:
log=velYYDDD
  • Where YY is the year and ddd is the day-of-year number (e.g. log=vel14176). This is important so all issues including wind stows can be tracked. If you are just following these instruction for a museum tour to get the Flashing Blue Light™ going then don’t worry about this step.
July 02, 2015, at 05:40 AM by Jim P - Big changes in recording commands - for less operator error
Changed lines 13-16 from:
  • Go to window 3 where most of the action happens. The top left window is where the recording on hovsi happens. Use ^C to stop that.
  • The bottom left window is sleeping waiting for observing to finish. Use ^C to stop the sleep. The regular “onsource” processes that recovers from wind stows will be killed and the telescope will now park.
to:
  • Go to window 3 (or window 1) where most of the action happens. The top left window is where the recording on hovsi happens. Use ^C to stop that.
  • The bottom left window is sleeping waiting for observing to finish. Use ^C to stop the sleep. The telescope used to park when doing this. It no longer does.
Added lines 22-23:
  • Next to the fs (or window 1, bottom right) is a window running onsource. Use ^C to stop this.
Changed lines 72-74 from:
  • Point the telescope to Vela (visible when LMST is between 00:00 and 17:00). In the field system type:
source=vela,083521,−451035,2000
to:
  • Point the telescope to Vela (visible when LMST is between 00:00 and 17:00). In the window to the right of the (oper@hobart) field system type (assuming its 2015 day 183):
~/jimp/track vel15183
  • If Vela is not up, it will move there and track when it rises.
Changed line 89 from:
  • We now need to set up some relevant directories on hovsi for calibration and observation. In the Window 3 on newsmerd there is a hovsi terminal at top left, type:
to:
  • We now need to the relevant directories on hovsi for calibration and observation. In the Window 3 on newsmerd there is a hovsi terminal at top left, type:
Deleted lines 96-97:
mkdir J0835–4510_S/2014_176
mkdir J0835–4510_S/2014_176/1376
Changed lines 116-121 from:
  • Now to observe:
cd /mnt/sirius16/pulsar/J0835–4510_S/2014_176/1376
vsib_record -m 2 -w 64 -f 10s -t 16h -o PSR_J0835–4510
  • Instead of 16h you will need to use another figure. Check current LMST and work out to the nearest hour (rounding down) how much time until 17:00:00. Note that 4h of observation takes about 1 Tb of disk space.
to:
  • Now to observe until Vela sets:
~/jimp/record 2015_183 1376 set
  • Or for something shorter:
‘’‘~/jimp/record 2015_183 1376 1h
  • Note that 19h of observation takes about 4 Tb of disk space.
Changed lines 127-128 from:
~/jimp/vela /mnt/sirius16/pulsar/J0835–4510_S/2014_176/1376 16 (but use the directory you are recording in and the length in hours!)
to:
~/jimp/agc 2015_183 1376 19 (but use the directory you are recording in and the proper length in hours!)
Deleted lines 130-131:
  • In window 5 (just to the right of the field system) type ~/jimp/onsource (as oper@hobart if it’s not there). This checks every five minutes that the telescope is tracking Vela. It’s main use is for recovering from wind stows.
Changed lines 132-136 from:
sleep 5h; killall onsource; date; inject_snap source=stow (as oper@hobart if it’s not there).
  • This kills the onsource script and parks the dish when the experiment is over. Again very important so Vela is not tracked into the limits as it sets.
to:
~/jimp/stow set (as oper@hobart if it’s not there).
  • This waits until Vela sets then kills the onsource script and parks the dish when the experiment is over. Again very important so Vela is not tracked into the limits as it sets. Note that ~/jimp/stow 5 50 will wait 5h 50m before ending the experiment.
Changed lines 140-141 from:

It is now possible to kick off an observation in advance. The receiver needs to be in place, directories created, noise diode test completed, oscillators set up, DAS configured, and levels roughly set.

to:

It is now possible to kick off an observation in advance, even if one is running. The receiver needs to be in place, directories created, noise diode test completed, oscillators set up, DAS configured, and levels roughly set.

Changed lines 145-146 from:
date; inject_snap log=vel14179; sleep <whatever>m; date; inject_snap source=azel,1541540,043018; date; ~/jimp/velars -r -d; date; inject_snap source=vela,083521,−451035,2000; sleep 1m; ~/jimp/onsource
to:
date; ~/jimp/velars -s -d; date; ~/jimp/track vel15184
Changed lines 148-149 from:
to:
date; ~/jimp/velars -s -d; date; ~/jimp/record 2015_184 1376 set
Changed lines 151-152 from:
to:
date; ~/jimp/velars -s -d; date; ~/jimp/agc 2015_184 1376 19
Changed lines 154-155 from:
date; ~/jimp/velars -r -d; date; ~/jimp/velars -s -d -w; date; killall onsource; inject_snap source=stow
to:
date; ~/jimp/velars -s -d; date; ~/jimp/stow set
June 26, 2015, at 01:31 AM by Jim P - Added L band for Ceduna
Changed lines 179-180 from:
  • For L band, the Agilent is set to 6.2 GHz and SML01 and SML02 should be set to 428 MHz at 7 dB for a central frequency of 1376 MHz.
to:
  • For L band 1376 MHz, the Agilent is set to 6.2 GHz and SML01 and SML02 should be set to 428 MHz at 7 dB.
  • For L band 1668 MHz, the Agilent is set to 6.2 GHz and SML01 and SML02 should be set to 720 MHz at 7 dB.
  • If L band has been set up with circulars then 1668 is most likely optimal.
June 26, 2015, at 01:12 AM by Jim P - Added L band for Ceduna
Added lines 179-180:
  • For L band, the Agilent is set to 6.2 GHz and SML01 and SML02 should be set to 428 MHz at 7 dB for a central frequency of 1376 MHz.
May 16, 2015, at 01:04 PM by Jim Palfreyman -
Changed lines 142-143 from:
date; inject_snap log=vel14179; ~/jimp/velars -r -d; date; inject_snap source=vela,083521,−451035,2000; sleep 3m; ~/jimp/onsource
to:
date; inject_snap log=vel14179; sleep <whatever>m; date; inject_snap source=azel,1541540,043018; date; ~/jimp/velars -r -d; date; inject_snap source=vela,083521,−451035,2000; sleep 1m; ~/jimp/onsource
May 15, 2015, at 09:49 PM by Jim Palfreyman -
Changed lines 148-149 from:
to:
April 30, 2015, at 04:11 AM by Jim Palfreyman - Added info about genesis at Ceduna
Added lines 191-192:
  • psrchive software is on genesis if local processing is required. Otherwise:
April 01, 2015, at 11:33 PM by Jim Palfreyman -
Changed line 141 from:
  • In window 5, just to the right of the field system type:
to:
  • In window 5, just to the right of the field system (hobart) type:
March 20, 2015, at 04:28 AM by Jim Palfreyman -
Changed lines 170-171 from:
vncviewer pcfsd:0
to:
vncviewer pcfscd:0
February 23, 2015, at 11:53 AM by Jim Palfreyman -
Changed lines 139-140 from:

As an example, our observation is in 6 hours 45 minutes time and is for 17 hours long. It is day 179 in 2014.

to:

As an example, Vela is currently set and it is day 179 in 2014.

February 23, 2015, at 11:51 AM by Jim Palfreyman - New code - velars
Changed lines 142-143 from:
date; inject_snap log=vel14179; sleep 6h 45m; date; inject_snap source=vela,083521,−451035,2000; sleep 1m; ~/jimp/onsource
to:
date; inject_snap log=vel14179; ~/jimp/velars -r -d; date; inject_snap source=vela,083521,−451035,2000; sleep 3m; ~/jimp/onsource
Changed lines 145-146 from:
to:
Changed lines 148-149 from:
to:
Changed lines 151-152 from:
date; sleep 16h 45m; date; sleep 17h; date; killall onsource; inject_snap source=stow
to:
date; ~/jimp/velars -r -d; date; ~/jimp/velars -s -d -w; date; killall onsource; inject_snap source=stow
February 16, 2015, at 05:11 AM by Jim Palfreyman -
Changed line 159 from:
check=*,-rx (for temperature warnings)
to:
check=*,-rx (for temperature warnings)
February 16, 2015, at 05:10 AM by Jim Palfreyman -
Changed line 159 from:
check=*,-rx
to:
check=*,-rx (for temperature warnings)
January 22, 2015, at 02:00 AM by Jim P -
Changed lines 228-229 from:

Typically this is run from a vncsession onto hex0. If the server is not running type (as root@hex0):

to:

Typically this is run from a vncsession onto hex0. If the server is not running type (as pulsar@hex0):

January 20, 2015, at 05:40 AM by Jim Palfreyman - Added vncserver commands
Added lines 33-34:

If the server is not running you need to run vncserver -alwaysshared -geometry 1280×720 preferably from the desktop.

Changed lines 226-227 from:

Once the data has been collected it needs to be processed. This is done using the hex cluster which is connected to the RDSI storage. But first the data has to be moved there. Log onto sirius (aka mk5ce) and type:

to:

Once the data has been collected it needs to be processed. This is done using the hex cluster which is connected to the RDSI storage. But first the data has to be moved there.

Typically this is run from a vncsession onto hex0. If the server is not running type (as root@hex0):

vncserver -alwaysshared -geometry 1280×720

Log onto sirius (aka mk5ce) and type:

January 17, 2015, at 05:05 AM by Jim Palfreyman - Added new .create commands
Added lines 256-259:

To create today.ft (which is an integration of all the pulses for the day):

‘’‘./create_today 2014_123/1376
Changed lines 294-301 from:
to:

To create daily.tim (which is the arrival times of all the today.ft files):

./create_daily

To use tempo2 to see these daily summaries (way less points to deal with and great for creating an ephemeris):

tempo2 -gr plk -us -grdev 20/xs -f /imports/rdsi/pulsar/MTP26M/J0835–4510_S/J0835–4510.eph daily.tim
January 15, 2015, at 09:16 AM by 147.69.172.134 -
Added line 159:
check=*,-if
January 14, 2015, at 02:22 AM by Jim Palfreyman - More commands
Changed lines 277-289 from:
to:

To pull out good timings of all data so far so this in the J0835–4510_S directory:

cat 2014*/1376/timing/*fixed.tim |grep -v C › allsofar_fixed.tim

Then to pull out 5000 random samples:

shuf -n 5000 allsofar_fixed.tim > allsofar_fixed_5000.tim

The use tempo2 to see it all:

tempo2 -gr plk -npsr 1 -nobs 10000 -us -grdev 20/xs -f /imports/rdsi/pulsar/MTP26M/J0835–4510_S/J0835–4510.eph allsofar_fixed_5000
January 14, 2015, at 01:17 AM by Jim Palfreyman -
Changed lines 265-266 from:

To create spa file:

to:

To create the all.spa file in the spa directory:

January 14, 2015, at 01:15 AM by Jim Palfreyman -
Changed lines 233-236 from:

This move the directory into a spot for hexb to process. This is not strictly necessary (i.e. all files could be in one spot) but makes things efficient when processing large amounts of data. It does require manual supervision but it is still way faster. Now start processing:

‘’‘lbapsr_master.csh /mnt/rdsi/pulsar/process/MTP26M/hexb Hobart 8
to:

This moves the directory into a spot for hexb to process. This is not strictly necessary (i.e. all files could be in one spot) but makes things efficient when processing large amounts of data. It does require manual supervision but it is still way faster. Now start processing:

lbapsr_master.csh /mnt/rdsi/pulsar/process/MTP26M/hexb Hobart 8
Changed lines 247-248 from:

Note that in all the following commands do NOT have a trailing / on the directory name! To move all the raw files into their own directory run:

to:

Note that in all the following commands, do NOT use a trailing / on the directory name! To move all the raw files into their own directory run:

Changed lines 263-264 from:

After deleting bad observations save a new .tim file in tempo2 format as fixed.tim. Save a .par file as today.par.

to:

After deleting bad observations in tempo2, save a new .tim file in tempo2 format as fixed.tim. Save a .par file as today.par.

January 14, 2015, at 01:13 AM by Jim Palfreyman - Added processing commands
Deleted line 218:
Added lines 221-279:

Processing Data

Once the data has been collected it needs to be processed. This is done using the hex cluster which is connected to the RDSI storage. But first the data has to be moved there. Log onto sirius (aka mk5ce) and type:

rsync —stats —ignore-existing —remove-source-files -v -t -r /exports/sirius_internal16/pulsar/J0835–4510_S/ /mnt/rdsi/pulsar/process/MTP26M/J0835–4510_S; date

Next we need to process. Log onto a hex node (say hexb) and:

cd /mnt/rdsi/pulsar/process/MTP26M/J0835–4510_S
mv 2014_123 /mnt/rdsi/pulsar/process/MTP26M/hexb/J0835–4510_S
pushd /mnt/rdsi/pulsar/process/MTP26M/hexb/J0835–4510_S

This move the directory into a spot for hexb to process. This is not strictly necessary (i.e. all files could be in one spot) but makes things efficient when processing large amounts of data. It does require manual supervision but it is still way faster. Now start processing:

‘’‘lbapsr_master.csh /mnt/rdsi/pulsar/process/MTP26M/hexb Hobart 8

This can be repeated for as many hex nodes as required.

After a directory is completed:

mv 2014_123 /mnt/rdsi/pulsar/MTP26M/J0835–4510_S

This puts it in with the rest. Now go there:

cd /mnt/rdsi/pulsar/MTP26M/J0835–4510_S

Note that in all the following commands do NOT have a trailing / on the directory name! To move all the raw files into their own directory run:

./create_raw 2014_123/1376

To create .ft files in a timing directory:

./create_ft 2014_123/1376

To create an all.tim file in the timing directory:

./create_tim 2014_123/1376

To run tempo2:

./create_tempo2files 2014_123/1376

After deleting bad observations save a new .tim file in tempo2 format as fixed.tim. Save a .par file as today.par.

To create spa file:

./create_spa 2014_123/1376

Note that all of these commands only run on one core. You can background them and run up to 8 on a single hex machine.

Down the track and it’s time to free up space by deleting those large lba files, type:

./create_raw.keep 2014_123/1376

This will search the spa output for bright and consecutive pulses and moves those .lba files to a raw.keep directory. Once you’ve verified this command has done that to your satisfaction, copy/paste the rm -rf 2014_123/1376/raw command to delete the raw directory. Please use the copy/paste - this prevents typos and deleting the wrong directory!!



\\\

January 07, 2015, at 10:56 PM by Jim Palfreyman -
Changed lines 155-156 from:
  • The Field System will sometimes pop up errors on baseband converters, e.g. “?ERROR ch −308 vd total power integrator overflow”. These are benign but the most annoying aspect is they cause the vnc window to pop to the top and become the focus for your keyboard. Not good! Type:
check=*,-vd, check=*,-rx and/or check=*,-ifd as well. Note that -vd and -ifd need to be adjusted depending on the error.
to:
  • The Field System will sometimes pop up errors on baseband converters, e.g. “?ERROR ch −308 vd total power integrator overflow”. These are benign but the most annoying aspect is they cause the vnc window to pop to the top and become the focus for your keyboard. Not good! Type one or all of:
check=*,-vd
check=*,-rx
check=*,-ifd
(Note that -vd and -ifd need to be adjusted depending on the error.)
January 07, 2015, at 10:55 PM by Jim Palfreyman - Added extra command under Annoying Things
Changed line 156 from:
check=*,-vd and check=*,-ifd as well. Note that -vd and -ifd need to be adjusted depending on the error.
to:
check=*,-vd, check=*,-rx and/or check=*,-ifd as well. Note that -vd and -ifd need to be adjusted depending on the error.
December 22, 2014, at 10:45 PM by Jim Palfreyman -
Added line 195:
December 22, 2014, at 10:44 PM by Jim Palfreyman - Handy plot commands
Added lines 194-217:

Some Useful Plotting Commands All commands use a 10 second .ar file that live in the RDSI structure.

  • To plot a waterfall diagram:
psrplot -p Y -j Fp -D 10/xs blah.ar
  • To integrate a whole 10 sec file:
psrplot -p D -j FTp -D 10/xs blah.ar
  • To pick out a single pulse (say number 42):
psrplot -p D -j Fp -c subint=42 -D 10/xs blah.ar
  • To pick out a single pulse (say number 42) and centre on 0.5:
psrplot -p D -j Fp -c subint=42 -j ‘centre cof’ -D 10/xs blah.ar
  • To pick out a single pulse (say number 42), centre on 0.5, and zoom:
psrplot -p D -j Fp -c subint=42 -j ‘centre cof’ -c ‘x:range=(0.45,0.55)’ -D 10/xs blah.ar
  • To pick out a single pulse (say number 42), centre on 0.5, zoom, and put x units in milliseconds:
psrplot -p D -j Fp -c subint=42 -j ‘centre cof’ -c ‘x:range=(0.45,0.55)’ -c ‘x:unit=ms’ -D 10/xs blah.ar



\\\

December 22, 2014, at 10:32 PM by Jim Palfreyman - More ceduna stuff
Changed line 185 from:
  • After recording, the data can be moved to a portable usb drive by, as root, typing something like:
to:
  • After recording, the data can be moved to a portable usb drive. To mount, as root, type something like:
Added lines 187-188:
  • Then to move data (not as root) type:
Changed line 191 from:
  • Note that this rsync command will remove files, but leave the directory structure behind. It’s usually a good idea to clean up that structure afterwards.
to:
  • Note that this rsync command will remove files, but leave the directory structure behind. It’s usually a good idea to clean up that structure afterwards. Also, if this rsync command is interrupted (by ^C or otherwise), then if run again it will pick up from where it left off.
December 22, 2014, at 10:28 PM by Jim Palfreyman - More ceduna stuff
Changed lines 185-189 from:
  • After recording, the data can be moved to …
to:
  • After recording, the data can be moved to a portable usb drive by, as root, typing something like:
mount /dev/sdd1 /mnt/usb1
rsync —stats —ignore-existing —remove-source-files -v -t -r /exports/xraid/Al_1/pulsar /mnt/usb1
  • Note that this rsync command will remove files, but leave the directory structure behind. It’s usually a good idea to clean up that structure afterwards.
December 22, 2014, at 10:06 PM by Jim Palfreyman - Adding Ceduna
Deleted line 1:

\\\

Deleted lines 156-163:

The Current Program

Observing of the Vela pulsar (J0835–4510) is currently occurring whenever the 26m telescope is otherwise free. Vela is visible 17 hours a day (LMST 00:00–17:00) and will generate 4 Tb of data if a full day is observed. This is being stored on rdsi. In the past the raw “.lba” files were processed and discarded. We now plan to keep them so further processing can be conducted on interesting events.

This Vela pulsar collection is currently by far the largest single pulse archive in the world. And expanding. There is plenty of scope for further study on the data collected. If this interests you then please contact Jim Palfreyman (jim7742@gmail.com).

Added lines 159-185:

Observing at Ceduna

The receiver at Ceduna is manually loaded by Bev. These instructions are for observing in C band (4.8 GHz).

  • Log onto ares and then type:
vncviewer pcfsd:0
  • If the field system is not running in a window then type fs.
  • To set the oscillators type:
./oscillator_gui.sh
  • For C band, the Agilent is irrelevant and SML01 and SML02 should be set to 436 MHz at 7 dB for a central frequency of 4816 MHz. Note the band is reversed.
  • To start the DAS, run das, load vsop_ho.pro first (or if a comms error) and then load psr64_n.pro
  • To set the attenuation levels run:
~/lovells_folley/folley_interface
  • Note that O means On and X means Off. Try to get as close to 127 on the DAS as possible.
  • To record, using the field system move on target and then:
ssh vlbi@cdvsi
  • And then move to an appropriate xraid to record as per Hobart.
  • After recording, the data can be moved to …
Changed lines 187-188 from:
to:



The Current Program

Observing of the Vela pulsar (J0835–4510) is currently occurring whenever the 26m telescope is otherwise free. Vela is visible 17 hours a day (LMST 00:00–17:00) and will generate 4 Tb of data if a full day is observed. This is being stored on rdsi. In the past the raw “.lba” files were processed and discarded. We now plan to keep them so further processing can be conducted on interesting events.

This Vela pulsar collection is currently by far the largest single pulse archive in the world. And expanding. There is plenty of scope for further study on the data collected. If this interests you then please contact Jim Palfreyman (jim77742@gmail.com).







December 16, 2014, at 03:00 AM by Jim Palfreyman -
Changed lines 154-155 from:
to:

Annoying things

  • The Field System will sometimes pop up errors on baseband converters, e.g. “?ERROR ch −308 vd total power integrator overflow”. These are benign but the most annoying aspect is they cause the vnc window to pop to the top and become the focus for your keyboard. Not good! Type:
check=*,-vd and check=*,-ifd as well. Note that -vd and -ifd need to be adjusted depending on the error.
November 03, 2014, at 03:12 AM by Jim P -
Added lines 40-41:
  • Where YY is the year and ddd is the day-of-year number (e.g. log=vel14176). This is important so all issues including wind stows can be tracked. If you are just following these instruction for a museum tour to get the Flashing Blue Light™ going then don’t worry about this step.
Deleted lines 44-45:
  • Where YY is the year and ddd is the day-of-year number (e.g. log=vel14176). This is important so all issues including wind stows can be tracked. If you are just following these instruction for a museum tour to get the Flashing Blue Light™ going then don’t worry about this step.
November 03, 2014, at 03:11 AM by Jim P - Added cryomon
Added lines 40-42:
  • If the cryo temps aren’t showing regularly (not important for pulsars, but for others using S/X) type:
cryomon@!,5m
June 29, 2014, at 11:31 AM by Jim Palfreyman -
Changed lines 133-134 from:

It is now possible to kick of an observation in advance. The receiver needs to be in place, directories created, noise diode test completed, oscillators set up, DAS configured, and levels roughly set.

to:

It is now possible to kick off an observation in advance. The receiver needs to be in place, directories created, noise diode test completed, oscillators set up, DAS configured, and levels roughly set.

June 29, 2014, at 11:29 AM by Jim Palfreyman -
Added lines 1-2:



\\\

June 29, 2014, at 11:29 AM by Jim Palfreyman -
Changed lines 23-25 from:
to:





Changed lines 121-131 from:
  • In window 5 (just to the right of the field system) type ~/jimp/onsource (as oper@hobart if it’s not there). This checks every five minutes that the telescope is tracking Vela. It’s main use is for recovering from windstows.
  • In window 3 (bottom left) type sleep 5h; killall onsource; date; inject_snap source=stow (as oper@hobart if it’s not there). This kills the onsource script and parks the dish when the experiment is over. Again very important so Vela is not tracked into the limits as it sets.
to:
June 29, 2014, at 01:52 AM by Jim Palfreyman -
Changed lines 138-140 from:
to:







June 27, 2014, at 08:02 AM by Jim Palfreyman -
Deleted line 0:
Changed lines 120-122 from:
to:
  • In window 5 (just to the right of the field system) type ~/jimp/onsource (as oper@hobart if it’s not there). This checks every five minutes that the telescope is tracking Vela. It’s main use is for recovering from windstows.
  • In window 3 (bottom left) type sleep 5h; killall onsource; date; inject_snap source=stow (as oper@hobart if it’s not there). This kills the onsource script and parks the dish when the experiment is over. Again very important so Vela is not tracked into the limits as it sets.
June 26, 2014, at 06:06 AM by Jim Palfreyman -
Deleted line 1:
Changed lines 8-9 from:

If you are doing some observing then it is imperative you follow these instructions and close down the Vela observation properly otherwise your data almost certainly will be stuffed.

to:

If you are doing some observing then it is imperative you follow these instructions and close down the Vela observation properly otherwise your data almost certainly will be stuffed.

Changed lines 17-18 from:
  • Top right there is a window with date/time and two numbers on each line. Use ^C to stop that. This changes attenuator levels. It is vital you stop this.
to:
  • Top right there is a window with date/time and two numbers on each line. Use ^C to stop that. This automatically changes attenuator levels. It is vital for your experiment that you stop this.
Added lines 131-136:

Old notes - this may no longer be accurate

June 26, 2014, at 03:15 AM by Jim Palfreyman -
Added lines 1-2:
Changed lines 5-8 from:

So you’ve got an urgent observing session and Jim Palfreyman (0407882718) is using the telescope to observe the Vela pulsar, you can’t get hold of him and you need to do your thing.

It is imperative you follow these instructions and close down the Vela observation properly otherwise your data may be stuffed.

to:

So you’ve got an urgent thing to do with the telescope and Jim Palfreyman (0407882718) is using it to observe the Vela pulsar, you can’t get hold of him and you need to do your thing.

If your thing is oiling the gears or polishing the focus cabin (or other such tasks that don’t involve the receiving and recording chain), then just use vdesk to move the dish, lock it off with the key, hit the stop button, and do your thing. When finished restore the key and stop button, and observing will continue automatically. Email Jim (jim77742@gmail.com) to let him know the stoppage times.

If you are doing some observing then it is imperative you follow these instructions and close down the Vela observation properly otherwise your data almost certainly will be stuffed.

June 25, 2014, at 12:55 PM by Jim Palfreyman -
Changed lines 121-125 from:

The Current Program

Observing of the Vela pulsar (J0835–4510) is currently occurring whenever the 26m telescope is otherwise free. Vela is visible 17 hours a day (LMST 00:00–17:00) and will generate 4 Tb of data if a full day is observed. This is being stored on rdsi. In the past the raw “.lba” files were processed and discarded. We now plan to keep them so further processing can be conducted on interesting events.

to:

The Current Program

Observing of the Vela pulsar (J0835–4510) is currently occurring whenever the 26m telescope is otherwise free. Vela is visible 17 hours a day (LMST 00:00–17:00) and will generate 4 Tb of data if a full day is observed. This is being stored on rdsi. In the past the raw “.lba” files were processed and discarded. We now plan to keep them so further processing can be conducted on interesting events.

This Vela pulsar collection is currently by far the largest single pulse archive in the world. And expanding. There is plenty of scope for further study on the data collected. If this interests you then please contact Jim Palfreyman (jim7742@gmail.com).

June 25, 2014, at 12:50 PM by Jim Palfreyman -
Changed lines 116-120 from:
  • This will pull data from the last fully recorded 10 second data file and check the levels. If incorrect, it will adjust the attenuators on Palfreyman’s Delight automatically. This is repeated every 5 minutes. Make sure you put the time in hours (used above) so this script stops. If you don’t it will possible affect other people’s experiments.
to:
  • This will pull data from the last fully recorded 10 second data file and check the levels. If incorrect, it will adjust the attenuators on Palfreyman’s Delight automatically. This is repeated every 5 minutes. Make sure you put the time in hours (used above) so this script stops. If you don’t do this properly it will possibly affect other people’s experiments.
June 25, 2014, at 12:47 PM by Jim Palfreyman -
Changed lines 114-120 from:
~/jimp/vela /mnt/sirius16/pulsar/J0835–4510_S/2014_176/1376 (but use the directory you are record in!)
  • This will pull data from the last fully recorded 10 second data file and check the levels. If incorrect, it will adjust the attenuators on Palfreyman’s Delight automatically. This is repeated every 10 minutes. Do not forget to ^C this when finished an observation otherwise the next observer will get strange results!! (This script needs to be modified to take a time limit.)
to:
~/jimp/vela /mnt/sirius16/pulsar/J0835–4510_S/2014_176/1376 16 (but use the directory you are recording in and the length in hours!)
  • This will pull data from the last fully recorded 10 second data file and check the levels. If incorrect, it will adjust the attenuators on Palfreyman’s Delight automatically. This is repeated every 5 minutes. Make sure you put the time in hours (used above) so this script stops. If you don’t it will possible affect other people’s experiments.
June 25, 2014, at 10:51 AM by Jim Palfreyman -
Changed lines 59-61 from:
  • These last two setting will not affect pulsar recording but are used to display pulses on the oscilloscope and the Flashing Blue Light™.
  • Point the telescope to Vela (visible when LMST is between 00:00 and 17:00). In the Field System type:
to:
  • These last two setting will not affect pulsar observation but are standard for other observations.
  • Point the telescope to Vela (visible when LMST is between 00:00 and 17:00). In the field system type:
Changed lines 64-65 from:
  • Wait for the telescope to say Tracking on the live page. The oscilloscope traces should be showing pulses and The Flashing Blue Light™ should be flickering. Gently adjust the Balance knob on the DC amplifier above the chart recorder for maximum effect. (If you are only setting this up for a tour demo - then you can stop here, just park the dish (source=stow in the field system) when finished.)
to:
  • Wait for the telescope to say Tracking on the live page. The oscilloscope traces should be showing pulses and The Flashing Blue Light™ should be flickering. Gently adjust the Balance knob on the DC amplifier above the chart recorder for maximum effect. Turn the volume knob up on the speakers to hear the pulsar. Remind the tour that they are hearing pulses that left the pulsar 1000 years ago.
  • If you are only setting this up for a tour demo - then you can stop here, just park the dish (source=stow in the field system) when finished.
June 25, 2014, at 10:35 AM by Jim Palfreyman -
Changed lines 1-2 from:

Cancelling a Running Observation

to:

Cancelling a Running Pulsar Observation

Changed lines 24-25 from:

Observing Instructions

to:

Starting a Vela Pulsar Observation

June 25, 2014, at 10:34 AM by Jim Palfreyman -
Changed lines 1-2 from:

bigCancelling a Running Observation

to:

Cancelling a Running Observation

June 25, 2014, at 10:33 AM by Jim Palfreyman -
Changed lines 1-4 from:

Cancelling a Running Observation

So you’ve got an urgent observing session and Jim Palfreyman is using the telescope to observe the Vela pulsar, you can’t get hold of him and you need to do your thing.

to:

bigCancelling a Running Observation

So you’ve got an urgent observing session and Jim Palfreyman (0407882718) is using the telescope to observe the Vela pulsar, you can’t get hold of him and you need to do your thing.

Changed lines 19-21 from:
to:
  • Email Jim (jim77742@gmail.com) to let him know what you’ve done.
June 24, 2014, at 01:22 PM by Jim Palfreyman -
Changed lines 68-69 from:
  • Type P for Profile and L for Load and enter PSR64_N.PRO. After getting Waiting for Setup, press S. If you get a communications error then try loading VSOP_HO.PRO and then reload PSR64_N.PRO. Press Space so you can see the levels. These need to be 128 ± 4 at worst. The attenuation levels entered previously adjust these. Each 0.1 dB roughly moves the level by 1. Again, you only need to be in the ball park at this point, because it is automatically adjusted later.
to:
  • Type P for Profile and L for Load and enter PSR64_N.PRO. After getting Waiting for Setup, press S. If you get a communications error then try loading VSOP_HO.PRO and then reload PSR64_N.PRO. If there are still issues, close down the DAS software and re-launch with VSOP_HO.PRO, then PSR64_N.PRO.
  • Press Space so you can see the levels. These need to be 128 ± 4 at worst. The attenuation levels entered previously adjust these. Each 0.1 dB roughly moves the level by 1. Again, you only need to be in the ball park at this point, because it is automatically adjusted later.
June 24, 2014, at 01:20 PM by Jim Palfreyman -
Changed lines 62-63 from:
  • Wait for the telescope to say Tracking on the live page. The oscilloscope traces should be showing pulses and The Flashing Blue Light™ should be flickering. Gently adjust the Balance knob on the DC amplifier above the chart recorder for maximum effect. (If you are only setting this up for a tour demo - then you can stop here, just park the dish (source=stow in the field system) when finished.)
to:
  • Wait for the telescope to say Tracking on the live page. The oscilloscope traces should be showing pulses and The Flashing Blue Light™ should be flickering. Gently adjust the Balance knob on the DC amplifier above the chart recorder for maximum effect. (If you are only setting this up for a tour demo - then you can stop here, just park the dish (source=stow in the field system) when finished.)
June 24, 2014, at 01:19 PM by Jim Palfreyman -
Changed lines 62-63 from:
  • Wait for the telescope to say Tracking on the live page. The oscilloscope traces should be showing pulses and The Flashing Blue Light™ should be flickering. Gently adjust the Balance knob on the DC amplifier above the chart recorder for maximum effect. (If you are only setting this up for a tour demo - then you can stop here, just park the dish when finished.)
to:
  • Wait for the telescope to say Tracking on the live page. The oscilloscope traces should be showing pulses and The Flashing Blue Light™ should be flickering. Gently adjust the Balance knob on the DC amplifier above the chart recorder for maximum effect. (If you are only setting this up for a tour demo - then you can stop here, just park the dish (source=stow in the field system) when finished.)
June 24, 2014, at 01:18 PM by Jim Palfreyman -
Changed lines 48-49 from:
SMY01 off (can be set to 688 MHz/7 dBm if you are at the observatory and want to confirm the signals are being received using the spectrum analyser.
to:
SMY01 off (can be set to 688 MHz/7 dBm if you are at the observatory and want to confirm the signals are being received using the spectrum analyser)
June 24, 2014, at 01:15 PM by Jim Palfreyman -
Changed lines 1-2 from:

Cancelling a running observation

to:

Cancelling a Running Observation

June 24, 2014, at 01:15 PM by Jim Palfreyman -
Changed lines 1-2 from:

Cancelling Instructions

to:

Cancelling a running observation

June 24, 2014, at 01:14 PM by Jim Palfreyman -
Deleted line 0:
Changed line 16 from:
  • Go to the Field System and change the log file using:
to:
  • Go to the Field System (window 5) and change the log file using:
Changed line 27 from:
  • Window 3 typically has all the main windows required and Window 5 has the Field System which is also needed. If the Field System is not running type:
to:
  • Window 3 typically has all the main windows required and window 5 has the Field System which is also needed. If the field system is not running type:
Changed line 44 from:
  • Set the local oscillators. This will be in Window 3 (or run ./oscillator_gui.sh on oper@hobart if you cannot find it). For an observation at 1376 MHz (a good spot currently) the settings are:
to:
  • Set the local oscillators. This will be in window 3 top middle, (or run ./oscillator_gui.sh on oper@hobart if you cannot find it). For an observation at 1376 MHz (a good spot currently) the settings are:
Changed line 50 from:
  • Configure Palfreymans Delight. This will be in Window 3 (or run ./PalfreymansClient.sh on newsmerd if you cannot find it). You will want:
to:
  • Configure Palfreymans Delight. This will be in window 3 bottom right, (or run ./PalfreymansClient.sh on newsmerd if you cannot find it). You will want:
June 24, 2014, at 01:12 PM by Jim Palfreyman - Major update
Changed lines 1-2 from:

2014–06–24 This page is currently under construction by Jim Palfreyman

to:
Changed lines 4-7 from:

So you’ve got an urgent observing session and Jim P is using the telescope to observe the Vela pulsar, you can’t get hold of him and you need to do your thing.

It is imperative you follow these instructions and close down the Vela observation properly otherwise your date may be stuffed.

to:

So you’ve got an urgent observing session and Jim Palfreyman is using the telescope to observe the Vela pulsar, you can’t get hold of him and you need to do your thing.

It is imperative you follow these instructions and close down the Vela observation properly otherwise your data may be stuffed.

June 24, 2014, at 01:11 PM by Jim Palfreyman - Major update - to be continued
Changed lines 5-6 from:

So you’ve got an urgent observing session and Jim P is using the telescope to observe the Vela pulsar and you need to do your thing. It is imperative you close down the Vela observation properly otherwise your observing may be destroyed.

to:

So you’ve got an urgent observing session and Jim P is using the telescope to observe the Vela pulsar, you can’t get hold of him and you need to do your thing.

It is imperative you follow these instructions and close down the Vela observation properly otherwise your date may be stuffed.

Changed lines 10-17 from:
vncviewer newsmerd:1 (the usual hungry password)
  • Go to window 3 where most of the action happens. The top left window is where the recording happens. Use ^C to stop that.
  • The bottom left window is sleeping waiting for observing to finish. Use ^C to stop the sleep. The regular “onsource” processes that recovers from wind stows will be killed. The telescope will now park.
  • Top right there is a window with date/date and two numbers on each line. Use ^C to stop that. This changes attenuator levels. It is vital you stop this.
to:
vncviewer newsmerd:1 (the usual hungry container password)
  • Go to window 3 where most of the action happens. The top left window is where the recording on hovsi happens. Use ^C to stop that.
  • The bottom left window is sleeping waiting for observing to finish. Use ^C to stop the sleep. The regular “onsource” processes that recovers from wind stows will be killed and the telescope will now park.
  • Top right there is a window with date/time and two numbers on each line. Use ^C to stop that. This changes attenuator levels. It is vital you stop this.
Changed lines 19-21 from:
log=<your file> (you will probably do this anyway, but it’s just a reminder.)
to:
log=<your file> (you will probably do this anyway for your experiment, but this is just a reminder.)
Changed lines 26-27 from:
  • The best way to observe Vela is to use the vnc session that is running permanently on newsmerd. Connect to it remotely by using vncviewer newsmerd:1 with the usual password. Window 3 typically has all the main windows required and Window 5 has the Field System which is also needed. If the Field System is not running type fs as oper@hobart.
to:
  • Connect to the vnc session on newsmerd remotely by using:
vncviewer newsmerd:1 (the usual hungry container password)
  • Window 3 typically has all the main windows required and Window 5 has the Field System which is also needed. If the Field System is not running type:
fs (as oper@hobart)
Changed lines 35-37 from:
  • Where YY is the year and ddd is the day-of-year number (e.g. log=vel14176). This is important so all issues including wind stows can be tracked. If you are just doing this for a tour to get the Flashing Blue Light ™ going then don’t worry about this step.
to:
  • Where YY is the year and ddd is the day-of-year number (e.g. log=vel14176). This is important so all issues including wind stows can be tracked. If you are just following these instruction for a museum tour to get the Flashing Blue Light™ going then don’t worry about this step.
Changed lines 38-41 from:
source=stow (or use vdesk/drvon/park if the Field System is not being used).
  • Select the receiver using the OTTER interface on Window 3 (run ./OTTER_interface.sh on newsmerd if you cannot find it). Mostly this will be L-band which is receiver 2. Wait for the platform to move into place (this can be checked on the live page). Make sure it is set to Direct and Quad OUT. The noise diodes should also be off. If the receiver platform doesn’t move, the switch on the receiver selector is probably set to Manual. If you are working remotely then you may now facepalm and curse the person who left it that way. If there is no one at the observatory then go start your car.
to:
source=stow
  • Select the receiver using the OTTER interface on Window 3 (run ./OTTER_interface.sh on newsmerd if you cannot find it). Most observations will be in L-band which is receiver 2. Wait for the platform to move into place (this can be checked on the live page). Make sure it is set to Direct and Quad OUT. The noise diodes should also be off.
  • If the receiver platform doesn’t move, the switch on the receiver selector is probably set to Manual. If you are working remotely you may facepalm now, followed by a curse to the person who left it that way. If there is no one at the observatory then go start your car.
Changed lines 46-53 from:
  • Set the local oscillators. This will be in Window 3 (or run ./oscillator_gui.sh on oper@hobart is you cannot find it). For an observation at 1376 MHz (a good spot currently) the Agilent needs to be set at 4.1 GHz/16 dBm and both the SML01/SML02 neede to be set at 876 MHz/7 dBm. SMY01 should be off for the experiment, but can be set to 688 MHz/7 dBm if you want to confirm the signals are being received using the spectrum analyser.
  • Configure Palfreymans Delight. This will be in Window 3 (or run ./PalfreymansClient.sh on newsmerd if you cannot find it). You will want Channel 1 on Multifeed RCP and Channel 2 on Multifeed LCP. Set the DAS attenuation to roughly 11 and 14. (This will be automatically adjusted later on). Set DC Input to Channel 1 &2: External SLD. DC Attenuation should be set at 5 dB. These last two setting will not affect pulsar recording but are used to display pulses on the oscilloscope and the Flashing Blue Light ™.
  • Point the telescope to Vela (visible when LMST is between 00:00 and 17:00). In the Field System type: →source=vela,083521,−451035,2000
  • Wait for the telescope to say Tracking on the live page. The oscilloscope traces should be showing pulses and The Flashing Blue Light ™ should be flickering. Gently adjust the Balance knob on the DC amplifier above the chart recorder for maximum effect. (If you are only setting this up for a tour demo - then you can stop here, just park the dish when finished.)
to:
  • Set the local oscillators. This will be in Window 3 (or run ./oscillator_gui.sh on oper@hobart if you cannot find it). For an observation at 1376 MHz (a good spot currently) the settings are:
Agilent 4.1 GHz/16 dBm
SML01 876 MHz/7 dBm
SML02 876 MHz/7 dBm
SMY01 off (can be set to 688 MHz/7 dBm if you are at the observatory and want to confirm the signals are being received using the spectrum analyser.
  • Configure Palfreymans Delight. This will be in Window 3 (or run ./PalfreymansClient.sh on newsmerd if you cannot find it). You will want:
Channel 1 on Multifeed RCP
Channel 2 on Multifeed LCP
DAS attenuation to roughly 11 and 14. (This will be automatically adjusted later on).
DC Input to External SLD
DC Attenuation to 5 dB.
  • These last two setting will not affect pulsar recording but are used to display pulses on the oscilloscope and the Flashing Blue Light™.
  • Point the telescope to Vela (visible when LMST is between 00:00 and 17:00). In the Field System type:
source=vela,083521,−451035,2000
  • Wait for the telescope to say Tracking on the live page. The oscilloscope traces should be showing pulses and The Flashing Blue Light™ should be flickering. Gently adjust the Balance knob on the DC amplifier above the chart recorder for maximum effect. (If you are only setting this up for a tour demo - then you can stop here, just park the dish when finished.)
Changed lines 68-72 from:
  • Configure the DAS profile. If remote, then use vncviewer das:1 with the password c… otherwise walk over to the DAS. Type P for Profile and L for Load and enter PSR64_N.PRO. After getting Waiting for Setup, press S. If you get a communications error then try loading VSOP_HO.PRO and then reload PSR64_N.PRO. Press Space so you can see the levels. These need to be 128 ± 4 at worst. The attenuation levels entered previously adjust these. Each 0.1 dB roughly moves the level by 1. Again, you only need to be in the ball park at this point, because it is automatically adjusted later.
  • We now need to set up some relevant directories on hovsi for calibration and observation. In the Window 3 on newsmerd there is a hovsi terminal, type:
cd /mnt/sirius16/pulsar (If these directories are not mounted, say after a power failure, then the special interface to sirius may need to be configured as root: ifconfig eth0 192.168.1.2 followed by mount /mnt/sirius16).
to:
  • Configure the DAS profile. If remote, then use vncviewer das:1 with the password con… otherwise walk over to the DAS.
  • Type P for Profile and L for Load and enter PSR64_N.PRO. After getting Waiting for Setup, press S. If you get a communications error then try loading VSOP_HO.PRO and then reload PSR64_N.PRO. Press Space so you can see the levels. These need to be 128 ± 4 at worst. The attenuation levels entered previously adjust these. Each 0.1 dB roughly moves the level by 1. Again, you only need to be in the ball park at this point, because it is automatically adjusted later.
  • We now need to set up some relevant directories on hovsi for calibration and observation. In the Window 3 on newsmerd there is a hovsi terminal at top left, type:
cd /mnt/sirius16/pulsar
  • If these directories are not mounted, say after a power failure, then the special interface to sirius may need to be configured (as root):
ifconfig eth0 192.168.1.2
mount /mnt/sirius16
Changed line 85 from:
  • For calibration we need to temporarily move off Vela. In the Field System type:
to:
  • For calibration we need to temporarily move off Vela. In the Field System (Window 5) type:
Changed lines 90-92 from:
samtest -c 5 -d 0.5 -i 0 -n 1 -s 120 -f 30 (followed by sam26m but DON’T press return yet
  • Now on hovsi:
to:
samtest -c 5 -d 0.5 -i 0 -n 1 -s 120 -f 30 (followed by sam26m but DON’T press return yet!)
  • Now on hovsi (Window 3, top left):
Changed line 98 from:
  • Move back onto Vela. In the Field System type:
to:
  • Move back onto Vela. In the Field System (Window 5) type:
Changed lines 105-106 from:
  • Instead of 16h you will need to use another figure. Check current LMST and work out to the nearest hour (rounding down) how much time until 17:00:00. Note that 4h of observation takes about 1 Tb.
to:
  • Instead of 16h you will need to use another figure. Check current LMST and work out to the nearest hour (rounding down) how much time until 17:00:00. Note that 4h of observation takes about 1 Tb of disk space.
Changed lines 109-111 from:
  • In another hovsi window type:
~/jimp/vela /mnt/sirius16/pulsar/J0835–4510_S/2014_176/1376
to:
  • In another hovsi window (Window 3, top right) type:
~/jimp/vela /mnt/sirius16/pulsar/J0835–4510_S/2014_176/1376 (but use the directory you are record in!)
June 24, 2014, at 12:48 PM by Jim Palfreyman - Major update - to be continued
Changed lines 3-4 from:

Observing instructions

to:

Cancelling Instructions

So you’ve got an urgent observing session and Jim P is using the telescope to observe the Vela pulsar and you need to do your thing. It is imperative you close down the Vela observation properly otherwise your observing may be destroyed.

  • vnc to newsmerd:
vncviewer newsmerd:1 (the usual hungry password)
  • Go to window 3 where most of the action happens. The top left window is where the recording happens. Use ^C to stop that.
  • The bottom left window is sleeping waiting for observing to finish. Use ^C to stop the sleep. The regular “onsource” processes that recovers from wind stows will be killed. The telescope will now park.
  • Top right there is a window with date/date and two numbers on each line. Use ^C to stop that. This changes attenuator levels. It is vital you stop this.
  • Go to the Field System and change the log file using:
log=<your file> (you will probably do this anyway, but it’s just a reminder.)

Observing Instructions

June 24, 2014, at 12:37 PM by Jim Palfreyman - Major update - to be continued
Changed lines 5-7 from:

The best way to observe Vela is to use the vnc session that is running permanently on newsmerd. Connect to it remotely by using vncviewer newsmerd:1 with the usual password. Window 3 typically has all the main windows required and Window 5 has the Field System which is also needed. If the Field System is not running type fs as oper@hobart.

Start a new log file. In the Field System type:

to:
  • The best way to observe Vela is to use the vnc session that is running permanently on newsmerd. Connect to it remotely by using vncviewer newsmerd:1 with the usual password. Window 3 typically has all the main windows required and Window 5 has the Field System which is also needed. If the Field System is not running type fs as oper@hobart.
  • Start a new log file. In the Field System type:
Changed lines 10-39 from:

Where YY is the year and ddd is the day-of-year number (e.g. log=vel14176). This is important so all issues including wind stows can be tracked. If you are just doing this for a tour to get the Flashing Blue Light ™ going then don’t worry about this step.

Make sure the dish is parked. In the Field System type:

source=stow

(or use vdesk/drvon/park if the Field System is not being used).

Select the receiver using the OTTER interface on Window 3 (run ./OTTER_interface.sh on newsmerd if you cannot find it). Mostly this will be L-band which is receiver 2. Wait for the platform to move into place (this can be checked on the live page). Make sure it is set to Direct and Quad OUT. The noise diodes should also be off. If the receiver platform doesn’t move, the switch on the receiver selector is probably set to Manual. If you are working remotely then you may now facepalm and curse the person who left it that way. If there is no one at the observatory then go start your car.

Check the L-band temperatures, voltages and currents. Currently the 20K stage is typically around 12K and the 70K around 82K. The voltages should be reasonably close to what’s stated (say 10–15%) and the currents should be about 3,10,15 mA on 1,2,3 respectively for both A and B.

Set the local oscillators. This will be in Window 3 (or run ./oscillator_gui.sh on oper@hobart is you cannot find it). For an observation at 1376 MHz (a good spot currently) the Agilent needs to be set at 4.1 GHz/16 dBm and both the SML01/SML02 neede to be set at 876 MHz/7 dBm. SMY01 should be off for the experiment, but can be set to 688 MHz/7 dBm if you want to confirm the signals are being received using the spectrum analyser.

Configure Palfreymans Delight. This will be in Window 3 (or run ./PalfreymansClient.sh on newsmerd if you cannot find it). You will want Channel 1 on Multifeed RCP and Channel 2 on Multifeed LCP. Set the DAS attenuation to roughly 11 and 14. (This will be automatically adjusted later on). Set DC Input to Channel 1 &2: External SLD. DC Attenuation should be set at 5 dB. These last two setting will not affect pulsar recording but are used to display pulses on the oscilloscope and the Flashing Blue Light ™.

Point the telescope to Vela (visible when LMST is between 00:00 and 17:00). In the Field System type: →source=vela,083521,−451035,2000

Wait for the telescope to say Tracking on the live page. The oscilloscope traces should be showing pulses and The Flashing Blue Light ™ should be flickering. Gently adjust the Balance knob on the DC amplifier above the chart recorder for maximum effect. (If you are only setting this up for a tour demo - then you can stop here, just park the dish when finished.)

Configure the BG3 cable. Behind cabinet 6 make sure the rainbow cable 1 goes into Ch 1 and 2 goes into Ch 2. The small cable with the large connector should go into Recorder Out. The other end of those three cable should go directly to the back right connecter on the board of the vsib box.

Configure the DAS profile. If remote, then use vncviewer das:1 with the password c… otherwise walk over to the DAS. Type P for Profile and L for Load and enter PSR64_N.PRO. After getting Waiting for Setup, press S. If you get a communications error then try loading VSOP_HO.PRO and then reload PSR64_N.PRO. Press Space so you can see the levels. These need to be 128 ± 4 at worst. The attenuation levels entered previously adjust these. Each 0.1 dB roughly moves the level by 1. Again, you only need to be in the ball park at this point, because it is automatically adjusted later.

We now need to set up some relevant directories on hovsi for calibration and observation. In the Window 3 on newsmerd there is a hovsi terminal, type:

cd /mnt/sirius16/pulsar

(If these directories are not mounted, say after a power failure, then the special interface to sirius may need to be configured as root: ifconfig eth0 192.168.1.2 followed by mount /mnt/sirius16).

You now need the year (e.g. 2014), day-of-year (e.g. 176) and observation frequency (e.g. 1376). Type the following commands:

to:
  • Where YY is the year and ddd is the day-of-year number (e.g. log=vel14176). This is important so all issues including wind stows can be tracked. If you are just doing this for a tour to get the Flashing Blue Light ™ going then don’t worry about this step.
  • Make sure the dish is parked. In the Field System type:
source=stow (or use vdesk/drvon/park if the Field System is not being used).
  • Select the receiver using the OTTER interface on Window 3 (run ./OTTER_interface.sh on newsmerd if you cannot find it). Mostly this will be L-band which is receiver 2. Wait for the platform to move into place (this can be checked on the live page). Make sure it is set to Direct and Quad OUT. The noise diodes should also be off. If the receiver platform doesn’t move, the switch on the receiver selector is probably set to Manual. If you are working remotely then you may now facepalm and curse the person who left it that way. If there is no one at the observatory then go start your car.
  • Check the L-band temperatures, voltages and currents. Currently the 20K stage is typically around 12K and the 70K around 82K. The voltages should be reasonably close to what’s stated (say 10–15%) and the currents should be about 3,10,15 mA on 1,2,3 respectively for both A and B.
  • Set the local oscillators. This will be in Window 3 (or run ./oscillator_gui.sh on oper@hobart is you cannot find it). For an observation at 1376 MHz (a good spot currently) the Agilent needs to be set at 4.1 GHz/16 dBm and both the SML01/SML02 neede to be set at 876 MHz/7 dBm. SMY01 should be off for the experiment, but can be set to 688 MHz/7 dBm if you want to confirm the signals are being received using the spectrum analyser.
  • Configure Palfreymans Delight. This will be in Window 3 (or run ./PalfreymansClient.sh on newsmerd if you cannot find it). You will want Channel 1 on Multifeed RCP and Channel 2 on Multifeed LCP. Set the DAS attenuation to roughly 11 and 14. (This will be automatically adjusted later on). Set DC Input to Channel 1 &2: External SLD. DC Attenuation should be set at 5 dB. These last two setting will not affect pulsar recording but are used to display pulses on the oscilloscope and the Flashing Blue Light ™.
  • Point the telescope to Vela (visible when LMST is between 00:00 and 17:00). In the Field System type: →source=vela,083521,−451035,2000
  • Wait for the telescope to say Tracking on the live page. The oscilloscope traces should be showing pulses and The Flashing Blue Light ™ should be flickering. Gently adjust the Balance knob on the DC amplifier above the chart recorder for maximum effect. (If you are only setting this up for a tour demo - then you can stop here, just park the dish when finished.)
  • Configure the BG3 cable. Behind cabinet 6 make sure the rainbow cable 1 goes into Ch 1 and 2 goes into Ch 2. The small cable with the large connector should go into Recorder Out. The other end of those three cable should go directly to the back right connecter on the board of the vsib box.
  • Configure the DAS profile. If remote, then use vncviewer das:1 with the password c… otherwise walk over to the DAS. Type P for Profile and L for Load and enter PSR64_N.PRO. After getting Waiting for Setup, press S. If you get a communications error then try loading VSOP_HO.PRO and then reload PSR64_N.PRO. Press Space so you can see the levels. These need to be 128 ± 4 at worst. The attenuation levels entered previously adjust these. Each 0.1 dB roughly moves the level by 1. Again, you only need to be in the ball park at this point, because it is automatically adjusted later.
  • We now need to set up some relevant directories on hovsi for calibration and observation. In the Window 3 on newsmerd there is a hovsi terminal, type:
cd /mnt/sirius16/pulsar (If these directories are not mounted, say after a power failure, then the special interface to sirius may need to be configured as root: ifconfig eth0 192.168.1.2 followed by mount /mnt/sirius16).
  • You now need the year (e.g. 2014), day-of-year (e.g. 176) and observation frequency (e.g. 1376). Type the following commands:
Changed line 41 from:

For calibration we need to temporarily move off Vela. In the Field System type:

to:
  • For calibration we need to temporarily move off Vela. In the Field System type:
Changed line 44 from:

We now need to run the noise diodes for a calibration. In a newsmerd window type:

to:
  • We now need to run the noise diodes for a calibration. In a newsmerd window type:
Changed line 48 from:

Now on hovsi:

to:
  • Now on hovsi:
Changed lines 52-53 from:

Wait until vsib_record has finished. samtest will follow soon after.

to:
  • Wait until vsib_record has finished. samtest will follow soon after.
Changed lines 63-66 from:

We are now recording. If you have set the levels up correctly, the channel figures should be reading 33,33,17,17 or something close. In another hovsi window type: ~/jimp/vela /mnt/sirius16/pulsar/J0835–4510_S/2014_176/1376. This will pull data from the last fully recorded 10 second data file and check the levels. If incorrect, it will adjust the attenuators on Palfreyman’s Delight automatically. This is repeated every 10 minutes. Do not forget to ^C this when finished an observation otherwise the next observer will get strange results!! (This script needs to be modified to take a time limit.)

to:
  • We are now recording. If you have set the levels up correctly, the channel figures should be reading 33,33,17,17 or something close.
  • In another hovsi window type:
~/jimp/vela /mnt/sirius16/pulsar/J0835–4510_S/2014_176/1376
  • This will pull data from the last fully recorded 10 second data file and check the levels. If incorrect, it will adjust the attenuators on Palfreyman’s Delight automatically. This is repeated every 10 minutes. Do not forget to ^C this when finished an observation otherwise the next observer will get strange results!! (This script needs to be modified to take a time limit.)
June 24, 2014, at 12:33 PM by Jim Palfreyman -
Changed lines 48-49 from:

We now need to run the noise diodes for a calibration. In a newsmerd window type calu -m sam26m and press return when prompted with rakbus. Then type samtest -c 5 -d 0.5 -i 0 -n 1 -s 120 -f 30 followed by sam26m but DON’T press return yet. Now on hovsi:

to:

We now need to run the noise diodes for a calibration. In a newsmerd window type:

calu -m sam26m (and press return when prompted with rakbus.)
samtest -c 5 -d 0.5 -i 0 -n 1 -s 120 -f 30 (followed by sam26m but DON’T press return yet

Now on hovsi:

Changed lines 54-55 from:
vsib_record -m 2 -w 64 -f 10s -t 90s -o CAL_J0835–4510 (but press Return on samtest first, then this one.
to:
vsib_record -m 2 -w 64 -f 10s -t 90s -o CAL_J0835–4510 (but press Return on samtest first, then this one.)
Changed lines 58-61 from:
  1. Move back onto Vela. In the Field System type source=vela,083521,−451035,2000
  2. Now to observe:
to:
  • Move back onto Vela. In the Field System type:
source=vela,083521,−451035,2000
  • Now to observe:
Changed lines 65-66 from:

Instead of 16h you will need to use another figure. Check current LMST and work out to the nearest hour (rounding down) how much time until 17:00:00. Note that 4h of observation takes about 1 Tb.

to:
  • Instead of 16h you will need to use another figure. Check current LMST and work out to the nearest hour (rounding down) how much time until 17:00:00. Note that 4h of observation takes about 1 Tb.
June 24, 2014, at 12:29 PM by Jim Palfreyman -
Changed lines 7-29 from:
Start a new log file. In the Field System type
log=velYYDDD
where YY is the year and ddd is the day-of-year number (e.g. log=vel14176). This is important so all issues including wind stows can be tracked. If you are just doing this for a tour to get the Flashing Blue Light ™ going then don’t worry about this step.
  1. Make sure the dish is parked. In the Field System type source=stow (or use vdesk/drvon/park if the Field System is not being used).
  2. Select the receiver using the OTTER interface on Window 3 (run ./OTTER_interface.sh on newsmerd if you cannot find it). Mostly this will be L-band which is receiver 2. Wait for the platform to move into place (this can be checked on the live page). Make sure it is set to Direct and Quad OUT. The noise diodes should also be off. If the receiver platform doesn’t move, the switch on the receiver selector is probably set to Manual. If you are working remotely then you may now facepalm and curse the person who left it that way. If there is no one at the observatory then go start your car.
  3. Check the L-band temperatures, voltages and currents. Currently the 20K stage is typically around 12K and the 70K around 82K. The voltages should be reasonably close to what’s stated (say 10–15%) and the currents should be about 3,10,15 mA on 1,2,3 respectively for both A and B.
  4. Set the local oscillators. This will be in Window 3 (or run ./oscillator_gui.sh on oper@hobart is you cannot find it). For an observation at 1376 MHz (a good spot currently) the Agilent needs to be set at 4.1 GHz/16 dBm and both the SML01/SML02 neede to be set at 876 MHz/7 dBm. SMY01 should be off for the experiment, but can be set to 688 MHz/7 dBm if you want to confirm the signals are being received using the spectrum analyser.
  5. Configure Palfreymans Delight. This will be in Window 3 (or run ./PalfreymansClient.sh on newsmerd if you cannot find it). You will want Channel 1 on Multifeed RCP and Channel 2 on Multifeed LCP. Set the DAS attenuation to roughly 11 and 14. (This will be automatically adjusted later on). Set DC Input to Channel 1 &2: External SLD. DC Attenuation should be set at 5 dB. These last two setting will not affect pulsar recording but are used to display pulses on the oscilloscope and the Flashing Blue Light ™.
  6. Point the telescope to Vela (visible when LMST is between 00:00 and 17:00). In the Field System type source=vela,083521,−451035,2000. Wait for the telescope to say Tracking on the live page. The oscilloscope traces should be showing pulses and The Flashing Blue Light ™ should be flickering. Gently adjust the Balance knob on the DC amplifier above the chart recorder for maximum effect. (If you are only setting this up for a tour demo - then you can stop here, just park the dish when finished.)
  7. Configure the BG3 cable. Behind cabinet 6 make sure the rainbow cable 1 goes into Ch 1 and 2 goes into Ch 2. The small cable with the large connector should go into Recorder Out. The other end of those three cable should go directly to the back right connecter on the board of the vsib box.
  8. Configure the DAS profile. If remote, then use vncviewer das:1 with the password c… otherwise walk over to the DAS. Type P for Profile and L for Load and enter PSR64_N.PRO. After getting Waiting for Setup, press S. If you get a communications error then try loading VSOP_HO.PRO and then reload PSR64_N.PRO. Press Space so you can see the levels. These need to be 128 ± 4 at worst. The attenuation levels entered previously adjust these. Each 0.1 dB roughly moves the level by 1. Again, you only need to be in the ball park at this point, because it is automatically adjusted later.
  9. We now need to set up some relevant directories on hovsi for calibration and observation. In the Window 3 on newsmerd there is a hovsi terminal, type cd /mnt/sirius16/pulsar (If these directories are not mounted, say after a power failure, then the special interface to sirius may need to be configured as root: ifconfig eth0 192.168.1.2 followed by mount /mnt/sirius16). You now need the year (e.g. 2014), day-of-year (e.g. 176) and observation frequency (e.g. 1376). Type the following commands:
to:

Start a new log file. In the Field System type:

log=velYYDDD

Where YY is the year and ddd is the day-of-year number (e.g. log=vel14176). This is important so all issues including wind stows can be tracked. If you are just doing this for a tour to get the Flashing Blue Light ™ going then don’t worry about this step.

Make sure the dish is parked. In the Field System type:

source=stow

(or use vdesk/drvon/park if the Field System is not being used).

Select the receiver using the OTTER interface on Window 3 (run ./OTTER_interface.sh on newsmerd if you cannot find it). Mostly this will be L-band which is receiver 2. Wait for the platform to move into place (this can be checked on the live page). Make sure it is set to Direct and Quad OUT. The noise diodes should also be off. If the receiver platform doesn’t move, the switch on the receiver selector is probably set to Manual. If you are working remotely then you may now facepalm and curse the person who left it that way. If there is no one at the observatory then go start your car.

Check the L-band temperatures, voltages and currents. Currently the 20K stage is typically around 12K and the 70K around 82K. The voltages should be reasonably close to what’s stated (say 10–15%) and the currents should be about 3,10,15 mA on 1,2,3 respectively for both A and B.

Set the local oscillators. This will be in Window 3 (or run ./oscillator_gui.sh on oper@hobart is you cannot find it). For an observation at 1376 MHz (a good spot currently) the Agilent needs to be set at 4.1 GHz/16 dBm and both the SML01/SML02 neede to be set at 876 MHz/7 dBm. SMY01 should be off for the experiment, but can be set to 688 MHz/7 dBm if you want to confirm the signals are being received using the spectrum analyser.

Configure Palfreymans Delight. This will be in Window 3 (or run ./PalfreymansClient.sh on newsmerd if you cannot find it). You will want Channel 1 on Multifeed RCP and Channel 2 on Multifeed LCP. Set the DAS attenuation to roughly 11 and 14. (This will be automatically adjusted later on). Set DC Input to Channel 1 &2: External SLD. DC Attenuation should be set at 5 dB. These last two setting will not affect pulsar recording but are used to display pulses on the oscilloscope and the Flashing Blue Light ™.

Point the telescope to Vela (visible when LMST is between 00:00 and 17:00). In the Field System type: →source=vela,083521,−451035,2000

Wait for the telescope to say Tracking on the live page. The oscilloscope traces should be showing pulses and The Flashing Blue Light ™ should be flickering. Gently adjust the Balance knob on the DC amplifier above the chart recorder for maximum effect. (If you are only setting this up for a tour demo - then you can stop here, just park the dish when finished.)

Configure the BG3 cable. Behind cabinet 6 make sure the rainbow cable 1 goes into Ch 1 and 2 goes into Ch 2. The small cable with the large connector should go into Recorder Out. The other end of those three cable should go directly to the back right connecter on the board of the vsib box.

Configure the DAS profile. If remote, then use vncviewer das:1 with the password c… otherwise walk over to the DAS. Type P for Profile and L for Load and enter PSR64_N.PRO. After getting Waiting for Setup, press S. If you get a communications error then try loading VSOP_HO.PRO and then reload PSR64_N.PRO. Press Space so you can see the levels. These need to be 128 ± 4 at worst. The attenuation levels entered previously adjust these. Each 0.1 dB roughly moves the level by 1. Again, you only need to be in the ball park at this point, because it is automatically adjusted later.

We now need to set up some relevant directories on hovsi for calibration and observation. In the Window 3 on newsmerd there is a hovsi terminal, type:

cd /mnt/sirius16/pulsar

(If these directories are not mounted, say after a power failure, then the special interface to sirius may need to be configured as root: ifconfig eth0 192.168.1.2 followed by mount /mnt/sirius16).

You now need the year (e.g. 2014), day-of-year (e.g. 176) and observation frequency (e.g. 1376). Type the following commands:

Changed lines 45-48 from:
  1. For calibration we need to move off Vela. In the Field System type source=velaoff,083521,−470000,2000
  2. We now need to run the noise diodes for a calibration. In a newsmerd window type calu -m sam26m and press return when prompted with rakbus. Then type samtest -c 5 -d 0.5 -i 0 -n 1 -s 120 -f 30 followed by sam26m but DON’T press return yet. Now on hovsi:
to:

For calibration we need to temporarily move off Vela. In the Field System type:

source=velaoff,083521,−470000,2000

We now need to run the noise diodes for a calibration. In a newsmerd window type calu -m sam26m and press return when prompted with rakbus. Then type samtest -c 5 -d 0.5 -i 0 -n 1 -s 120 -f 30 followed by sam26m but DON’T press return yet. Now on hovsi:

June 24, 2014, at 12:24 PM by Jim Palfreyman -
Changed lines 8-9 from:
log=velYYDDD
to:
log=velYYDDD
June 24, 2014, at 12:23 PM by Jim Palfreyman - Major update - to be continued
Changed lines 7-8 from:
  1. Start a new log file. In the Field System type log=velYYDDD where YY is the year and ddd is the day-of-year number (e.g. log=vel14176). This is important so all issue including wind stows can be tracked. If you are just doing this for a tour to get the Flashing Blue Light ™ going then don’t worry about this step.
to:
Start a new log file. In the Field System type
log=velYYDDD
where YY is the year and ddd is the day-of-year number (e.g. log=vel14176). This is important so all issues including wind stows can be tracked. If you are just doing this for a tour to get the Flashing Blue Light ™ going then don’t worry about this step.
June 24, 2014, at 04:32 AM by Jim Palfreyman - Major update - to be continued
June 24, 2014, at 03:53 AM by Jim Palfreyman - Major update - to be continued
Changed lines 23-34 from:
  1. Configure the DAS profile. If remote, then use vncviewer das:1 with the password c… otherwise walk over to the DAS. Type P for Profile and L for Load and enter PSR64_N.PRO. After getting Waiting for Setup, press S. If you get a communicaitons error then try loading VSOP_HO.PRO and then reload PSR64_N.PRO. Press Space so you can see the levels. These need to be 128 ± 4 at worst. The attenuation levels entered previously adjust these. Each 0.1 dB roughly moves the level by 1. Again, you only need to be in the ball park at this point, because it is automatically adjusted later.
  2. We now need to set up some relevant directories on hovsi for calibration and observation. First go to /mnt/sirius16/pulsar (If these directories are not mounted, say after a power failure, then the special interface to sirius may need to be configured as root: ifconfig eth0 192.168.1.2 followed by mount /mnt/sirius16). You now need the year YYYY, day-of-year DDD and observation frequency FFFF. Type the following commands:
mkdir J0835–4510_S/YYYY_DDD
  1. We now need to run the noise diodes for a calibration. In a newsmerd window type calu -m sam26m and press return when prompted with rakbus. Then type samtest -c 5 -d 0.5 -i 0 -n 1 -s 120 -f 30 followed by sam26m but DON’T press return yet.
to:
  1. Configure the DAS profile. If remote, then use vncviewer das:1 with the password c… otherwise walk over to the DAS. Type P for Profile and L for Load and enter PSR64_N.PRO. After getting Waiting for Setup, press S. If you get a communications error then try loading VSOP_HO.PRO and then reload PSR64_N.PRO. Press Space so you can see the levels. These need to be 128 ± 4 at worst. The attenuation levels entered previously adjust these. Each 0.1 dB roughly moves the level by 1. Again, you only need to be in the ball park at this point, because it is automatically adjusted later.
  2. We now need to set up some relevant directories on hovsi for calibration and observation. In the Window 3 on newsmerd there is a hovsi terminal, type cd /mnt/sirius16/pulsar (If these directories are not mounted, say after a power failure, then the special interface to sirius may need to be configured as root: ifconfig eth0 192.168.1.2 followed by mount /mnt/sirius16). You now need the year (e.g. 2014), day-of-year (e.g. 176) and observation frequency (e.g. 1376). Type the following commands:
mkdir J0835–4510_S/2014_176
mkdir J0835–4510_S/2014_176/1376
mkdir J0835–4510_R/2014_176
mkdir J0835–4510_R/2014_176/1376
  1. For calibration we need to move off Vela. In the Field System type source=velaoff,083521,−470000,2000
  2. We now need to run the noise diodes for a calibration. In a newsmerd window type calu -m sam26m and press return when prompted with rakbus. Then type samtest -c 5 -d 0.5 -i 0 -n 1 -s 120 -f 30 followed by sam26m but DON’T press return yet. Now on hovsi:
cd /mnt/sirius16/pulsar/J0835–4510_R/2014_176/1376
vsib_record -m 2 -w 64 -f 10s -t 90s -o CAL_J0835–4510 (but press Return on samtest first, then this one.

Wait until vsib_record has finished. samtest will follow soon after.

  1. Move back onto Vela. In the Field System type source=vela,083521,−451035,2000
  2. Now to observe:
cd /mnt/sirius16/pulsar/J0835–4510_S/2014_176/1376
vsib_record -m 2 -w 64 -f 10s -t 16h -o PSR_J0835–4510

Instead of 16h you will need to use another figure. Check current LMST and work out to the nearest hour (rounding down) how much time until 17:00:00. Note that 4h of observation takes about 1 Tb.

We are now recording. If you have set the levels up correctly, the channel figures should be reading 33,33,17,17 or something close. In another hovsi window type: ~/jimp/vela /mnt/sirius16/pulsar/J0835–4510_S/2014_176/1376. This will pull data from the last fully recorded 10 second data file and check the levels. If incorrect, it will adjust the attenuators on Palfreyman’s Delight automatically. This is repeated every 10 minutes. Do not forget to ^C this when finished an observation otherwise the next observer will get strange results!! (This script needs to be modified to take a time limit.)

June 24, 2014, at 03:34 AM by Jim Palfreyman - Major update - to be continued
Changed lines 7-8 from:
  1. Start a new log file. In the Field System type log=velYYDDD where YY is the year and ddd is the day-of-year number (e.g. log=vel14176). This is important so all issue including wind stows can be tracked.
to:
  1. Start a new log file. In the Field System type log=velYYDDD where YY is the year and ddd is the day-of-year number (e.g. log=vel14176). This is important so all issue including wind stows can be tracked. If you are just doing this for a tour to get the Flashing Blue Light ™ going then don’t worry about this step.
Changed lines 19-20 from:
  1. Point the telescope to Vela (visible when LMST is between 00:00 and 17:00). In the Field System type source=vela,083521,−451035,2000. Wait for the telescope to say Tracking on the live page. The oscilloscope traces should be showing pulses and The Flashing Blue Light ™ should be flickering. Gently adjust the Balance knob on the DC amplifier above the chart recorder for maximum effect.
to:
  1. Point the telescope to Vela (visible when LMST is between 00:00 and 17:00). In the Field System type source=vela,083521,−451035,2000. Wait for the telescope to say Tracking on the live page. The oscilloscope traces should be showing pulses and The Flashing Blue Light ™ should be flickering. Gently adjust the Balance knob on the DC amplifier above the chart recorder for maximum effect. (If you are only setting this up for a tour demo - then you can stop here, just park the dish when finished.)
Changed lines 23-26 from:
  1. Configure the DAS profile. If remote, then use vncviewer das:1 with the password c… otherwise walk over to the DAS. Type P for Profile and L for Load and enter PSR64_N.PRO. After getting Waiting for Setup, press S. If you get a communicaitons error then try loading VSOP_HO.PRO and then reload PSR64_N.PRO. Press Space so you can see the levels. These need to be 128 ± 4 at worst. The attenuation levels to previously adjust these. Each 0.1 dB roughly moves the level by 1. Again, you only need to be in the ball park at this point, because it is automatically adjusted later.
to:
  1. Configure the DAS profile. If remote, then use vncviewer das:1 with the password c… otherwise walk over to the DAS. Type P for Profile and L for Load and enter PSR64_N.PRO. After getting Waiting for Setup, press S. If you get a communicaitons error then try loading VSOP_HO.PRO and then reload PSR64_N.PRO. Press Space so you can see the levels. These need to be 128 ± 4 at worst. The attenuation levels entered previously adjust these. Each 0.1 dB roughly moves the level by 1. Again, you only need to be in the ball park at this point, because it is automatically adjusted later.
  2. We now need to set up some relevant directories on hovsi for calibration and observation. First go to /mnt/sirius16/pulsar (If these directories are not mounted, say after a power failure, then the special interface to sirius may need to be configured as root: ifconfig eth0 192.168.1.2 followed by mount /mnt/sirius16). You now need the year YYYY, day-of-year DDD and observation frequency FFFF. Type the following commands:
mkdir J0835–4510_S/YYYY_DDD
  1. We now need to run the noise diodes for a calibration. In a newsmerd window type calu -m sam26m and press return when prompted with rakbus. Then type samtest -c 5 -d 0.5 -i 0 -n 1 -s 120 -f 30 followed by sam26m but DON’T press return yet.
June 24, 2014, at 02:46 AM by Jim Palfreyman - Major update - to be continued
Changed lines 21-24 from:
  1. Configure the BG3 cable. Behind cabinet 6 make sure the rainbow cable 1 goes into Ch 1 and 2 goes into Ch 2. The small cable with the large connector should go into Recorder Out. The other end of those three cable should go directly to the back right connecter on the board of the vsic.
to:
  1. Configure the BG3 cable. Behind cabinet 6 make sure the rainbow cable 1 goes into Ch 1 and 2 goes into Ch 2. The small cable with the large connector should go into Recorder Out. The other end of those three cable should go directly to the back right connecter on the board of the vsib box.
  2. Configure the DAS profile. If remote, then use vncviewer das:1 with the password c… otherwise walk over to the DAS. Type P for Profile and L for Load and enter PSR64_N.PRO. After getting Waiting for Setup, press S. If you get a communicaitons error then try loading VSOP_HO.PRO and then reload PSR64_N.PRO. Press Space so you can see the levels. These need to be 128 ± 4 at worst. The attenuation levels to previously adjust these. Each 0.1 dB roughly moves the level by 1. Again, you only need to be in the ball park at this point, because it is automatically adjusted later.
June 24, 2014, at 02:31 AM by Jim Palfreyman - Major update - to be continued
Changed lines 17-18 from:
  1. Configure Palfreymans Delight. This will be in Window 3 (or run ./PalfreymansClient.sh on newsmerd if you cannot find it). You will want Channel 1 on Multifeed RCP and Channel 2 on Multifeed LCP. Set the DAS attenuation to roughly 11 and 14. (This will be automatically adjusted later on). Set DC Input to Channel 1 &2: External SLD. DC Attenuation should be set at 5 dB. These last two setting will not affect pulsar recording but are used to display pulses on the oscilloscope and the flashing blue light ™.
to:
  1. Configure Palfreymans Delight. This will be in Window 3 (or run ./PalfreymansClient.sh on newsmerd if you cannot find it). You will want Channel 1 on Multifeed RCP and Channel 2 on Multifeed LCP. Set the DAS attenuation to roughly 11 and 14. (This will be automatically adjusted later on). Set DC Input to Channel 1 &2: External SLD. DC Attenuation should be set at 5 dB. These last two setting will not affect pulsar recording but are used to display pulses on the oscilloscope and the Flashing Blue Light ™.
  2. Point the telescope to Vela (visible when LMST is between 00:00 and 17:00). In the Field System type source=vela,083521,−451035,2000. Wait for the telescope to say Tracking on the live page. The oscilloscope traces should be showing pulses and The Flashing Blue Light ™ should be flickering. Gently adjust the Balance knob on the DC amplifier above the chart recorder for maximum effect.
  3. Configure the BG3 cable. Behind cabinet 6 make sure the rainbow cable 1 goes into Ch 1 and 2 goes into Ch 2. The small cable with the large connector should go into Recorder Out. The other end of those three cable should go directly to the back right connecter on the board of the vsic.
June 24, 2014, at 02:21 AM by Jim Palfreyman - Major update - to be continued
Changed lines 5-6 from:

The best way to observe Vela is to use the vnc session that is running permanently on newsmerd. Connect to it remotely by using vncviewer newsmerd:1 with the usual password. Window 3 typically has all the main windows required and Window 5 has the Field System which is also needed.

to:

The best way to observe Vela is to use the vnc session that is running permanently on newsmerd. Connect to it remotely by using vncviewer newsmerd:1 with the usual password. Window 3 typically has all the main windows required and Window 5 has the Field System which is also needed. If the Field System is not running type fs as oper@hobart.

  1. Start a new log file. In the Field System type log=velYYDDD where YY is the year and ddd is the day-of-year number (e.g. log=vel14176). This is important so all issue including wind stows can be tracked.
Changed lines 11-12 from:
  1. Select the receiver using the OTTER interface (./OTTER_interface.sh on newsmerd). Mostly this will be L-band which is receiver 2. Wait for the platform to move into place (this can be checked on the live page). Make sure it is set to Direct and Quad OUT. The noise diodes should also be off. If the receiver platform doesn’t move, the switch on the receiver selector is probably set to Manual. If you are working remotely then you may now facepalm and curse the person who left it that way. If there is no one at the observatory then go start your car.
to:
  1. Select the receiver using the OTTER interface on Window 3 (run ./OTTER_interface.sh on newsmerd if you cannot find it). Mostly this will be L-band which is receiver 2. Wait for the platform to move into place (this can be checked on the live page). Make sure it is set to Direct and Quad OUT. The noise diodes should also be off. If the receiver platform doesn’t move, the switch on the receiver selector is probably set to Manual. If you are working remotely then you may now facepalm and curse the person who left it that way. If there is no one at the observatory then go start your car.
Added lines 15-18:
  1. Set the local oscillators. This will be in Window 3 (or run ./oscillator_gui.sh on oper@hobart is you cannot find it). For an observation at 1376 MHz (a good spot currently) the Agilent needs to be set at 4.1 GHz/16 dBm and both the SML01/SML02 neede to be set at 876 MHz/7 dBm. SMY01 should be off for the experiment, but can be set to 688 MHz/7 dBm if you want to confirm the signals are being received using the spectrum analyser.
  2. Configure Palfreymans Delight. This will be in Window 3 (or run ./PalfreymansClient.sh on newsmerd if you cannot find it). You will want Channel 1 on Multifeed RCP and Channel 2 on Multifeed LCP. Set the DAS attenuation to roughly 11 and 14. (This will be automatically adjusted later on). Set DC Input to Channel 1 &2: External SLD. DC Attenuation should be set at 5 dB. These last two setting will not affect pulsar recording but are used to display pulses on the oscilloscope and the flashing blue light ™.
June 24, 2014, at 02:00 AM by Jim Palfreyman - Major update - to be continued
Changed lines 5-9 from:

The best way to observe Vela is to use the vnc session that is running permanently on newsmerd. Connect to it remotely by using vncviewer

  1. Make sure the dish is parked. Either use “”vdesk/drvon/park”“ or the Field System “source=stow”.
  2. Select
to:

The best way to observe Vela is to use the vnc session that is running permanently on newsmerd. Connect to it remotely by using vncviewer newsmerd:1 with the usual password. Window 3 typically has all the main windows required and Window 5 has the Field System which is also needed.

  1. Make sure the dish is parked. In the Field System type source=stow (or use vdesk/drvon/park if the Field System is not being used).
  2. Select the receiver using the OTTER interface (./OTTER_interface.sh on newsmerd). Mostly this will be L-band which is receiver 2. Wait for the platform to move into place (this can be checked on the live page). Make sure it is set to Direct and Quad OUT. The noise diodes should also be off. If the receiver platform doesn’t move, the switch on the receiver selector is probably set to Manual. If you are working remotely then you may now facepalm and curse the person who left it that way. If there is no one at the observatory then go start your car.
  3. Check the L-band temperatures, voltages and currents. Currently the 20K stage is typically around 12K and the 70K around 82K. The voltages should be reasonably close to what’s stated (say 10–15%) and the currents should be about 3,10,15 mA on 1,2,3 respectively for both A and B.
June 24, 2014, at 01:45 AM by Jim Palfreyman - Major update - to be continued
Changed lines 5-6 from:

The best way to observe Vela is to use the vnc session that is running permanently on newsmerd. Connect to it remotely by using “”vncviewer”“

to:

The best way to observe Vela is to use the vnc session that is running permanently on newsmerd. Connect to it remotely by using vncviewer

June 24, 2014, at 01:45 AM by Jim Palfreyman - Major update - to be continued
Changed lines 5-8 from:

To observe the Vela pulsar do the following:

  1. Test1
  2. Test2
to:

The best way to observe Vela is to use the vnc session that is running permanently on newsmerd. Connect to it remotely by using “”vncviewer”“

  1. Make sure the dish is parked. Either use “”vdesk/drvon/park”“ or the Field System “source=stow”.
  2. Select
June 24, 2014, at 01:42 AM by Jim Palfreyman - Major update - to be continued
Changed lines 1-2 from:

2014–06–24 This page is currently under construction

to:

2014–06–24 This page is currently under construction by Jim Palfreyman

Observing instructions

To observe the Vela pulsar do the following:

  1. Test1
  2. Test2
June 24, 2014, at 01:35 AM by Jim Palfreyman - Major update - to be continued
Changed lines 1-3 from:

This page is outdated and will be updated shortly!

to:

2014–06–24 This page is currently under construction

The Current Program

Observing of the Vela pulsar (J0835–4510) is currently occurring whenever the 26m telescope is otherwise free. Vela is visible 17 hours a day (LMST 00:00–17:00) and will generate 4 Tb of data if a full day is observed. This is being stored on rdsi. In the past the raw “.lba” files were processed and discarded. We now plan to keep them so further processing can be conducted on interesting events.

Changed lines 10-13 from:

Mt Pleasant is equipped with a dual-pol, 64 MHz bandwidth baseband recorder and SGI Origin 3400 supercomputer that can be used together as a pulsar coherent dedispersion system. The telescope signal is routed into the ATNF data acquisition system (DAS) in the same way as for VLBI or correlator observations. The output of the DAS is fed into the eVLBI recorder via the “BG3” cable and the eVLBI software (“vsib_record”) is used to record data to the Hobart XRaid storage unit connected to hovsi.

The data can be processed by the supercomputer at any time, during or after the observations. A set of scripts have been written to automate the transfer and processing of baseband data for pulsar observations. When running, these scripts will copy data from the XRaid to the Origin 3400 one file at a time and run the coherent dedispersion and folding software (“dspsr”) on each file, using an ephemeris from the collection kept in $TZPAR. The Origin 3400 originally had 24 processors but one of the blades developed a fault before it was given to the observatory and will not run reliably. It is best to leave this blade turned off (there is a red sticker over the power button) or the whole machine will crash on average once a day. The remaining blades have a total of 20 processors. At best (for low dispersion measures) this allows processing at a rate roughly 1/3 real-time. There is 1GB of memory per processor, which is usually enough but can be insufficient if very high-resolution processing is attempted (single pulses with lots of frequency channels and phase bins for example).

to:

Mt Pleasant is equipped with a dual-pol, 64 MHz bandwidth baseband recorder and a 48 core cluster that can be used together as a pulsar coherent dedispersion system. The telescope signal is routed into the ATNF data acquisition system (DAS) in the same way as for VLBI or correlator observations. The output of the DAS is fed into the eVLBI recorder via the “BG3” cable and the eVLBI software (“vsib_record”) is used to record data to “hovsi” which is connected (via a dedicated ethernet cable) to the 24 Tb host “sirius”.

The data can be processed at any time, during or after the observations. A set of scripts have been written to automate the transfer and processing of baseband data for pulsar observations. When running, these scripts will copy data from the XRaid to the Origin 3400 one file at a time and run the coherent dedispersion and folding software (“dspsr”) on each file, using an ephemeris from the collection kept in $TZPAR. The Origin 3400 originally had 24 processors but one of the blades developed a fault before it was given to the observatory and will not run reliably. It is best to leave this blade turned off (there is a red sticker over the power button) or the whole machine will crash on average once a day. The remaining blades have a total of 20 processors. At best (for low dispersion measures) this allows processing at a rate roughly 1/3 real-time. There is 1GB of memory per processor, which is usually enough but can be insufficient if very high-resolution processing is attempted (single pulses with lots of frequency channels and phase bins for example).

March 07, 2014, at 11:45 AM by Jim Palfreyman - Outdated
Added lines 1-3:

This page is outdated and will be updated shortly!

September 20, 2007, at 05:38 AM by Aidan -
Changed lines 5-6 from:

The data can be processed by the supercomputer at any time, during or after the observations. A set of scripts have been written to automate the transfer and processing of baseband data for pulsar observations. When running, these scripts will copy data from the XRaid to the Origin 3400 one file at a time and run the coherent dedispersion and folding software (“dspsr”) on each file, using an ephemeris from the collection kept in $TZPAR. The Origin 3400 has 24 processors and up to 24 jobs can be run simultaneously. At best (for low dispersion measures) this allows processing at a rate roughly 1/3 real-time.

to:

The data can be processed by the supercomputer at any time, during or after the observations. A set of scripts have been written to automate the transfer and processing of baseband data for pulsar observations. When running, these scripts will copy data from the XRaid to the Origin 3400 one file at a time and run the coherent dedispersion and folding software (“dspsr”) on each file, using an ephemeris from the collection kept in $TZPAR. The Origin 3400 originally had 24 processors but one of the blades developed a fault before it was given to the observatory and will not run reliably. It is best to leave this blade turned off (there is a red sticker over the power button) or the whole machine will crash on average once a day. The remaining blades have a total of 20 processors. At best (for low dispersion measures) this allows processing at a rate roughly 1/3 real-time. There is 1GB of memory per processor, which is usually enough but can be insufficient if very high-resolution processing is attempted (single pulses with lots of frequency channels and phase bins for example).

Changed lines 11-12 from:

When using vsib_record to take pulsar data, please ensure that the DAS is running the profile called PSR64_N.PRO. This profile disables the automatic gain control system, which is essential when observing bright pulsars (otherwise, the AGC tries to remove each incoming pulse and you end up with a large artificial dip on the trailing edge of the profile). This profile operates the DAS in 64 MHz mode, which requires a special cable (the BG3 cable) to interface between the correlator ports on the DAS and the input to the VSIC converter card. This is quite different to the “normal” eVLBI mode of operation where the S2 data output port it used. The vsib_record program should be run with the arguments “-m 2 -w 64″ to ensure correct operation.

to:

When using vsib_record to take pulsar data, please ensure that the DAS is running the profile called PSR64_N.PRO. This profile disables the automatic gain control system, which is essential when observing bright pulsars (otherwise, the AGC tries to remove each incoming pulse and you end up with a large artificial dip on the trailing edge of the profile). This profile operates the DAS in 64 MHz mode, which requires a special cable (the BG3 cable) to interface between the correlator ports on the DAS and the input to the VSIC converter card. This is quite different to the “normal” eVLBI mode of operation where the S2 data output port it used. The vsib_record program should be run with the arguments “-m 2 -w 64″ to ensure correct recording.

July 19, 2007, at 02:03 AM by Aidan Hotan - Minor corrections
Changed lines 3-6 from:

Mt Pleasant is equiped with a dual-pol, 64 MHz bandwidth baseband recorder and SGI Origin 3400 supercomputer that can be used together as a pulsar coherent dedispersion system. The telescope signal is routed into the ATNF DAS in the same way as for a VLBI or spectral line correlator observation. The output of the DAS is fed into the eVLBI recorder via the “BG3” cable and the eVLBI software (“vsib_record”) is used to record data to the Hobart XRaid storage unit.

The data can be processed by the supercomputer at any time, during or after the observations. A set of scripts have been written to automate the transfer and processing of baseband data for pulsar observations. When running, these scripts will copy data from the XRaid to the Origin 3400 one file at a time and run the coherent dedispersion and folding software (“dspsr”) on each file, using an ephemeris from the collection kept in $TZPAR. The Origin 3400 has 24 processors and up to 24 jobs can be run simultaneously. At best (for low dispersion measures) this allows processing at a rate roughly 1/3 of real-time.

to:

Mt Pleasant is equipped with a dual-pol, 64 MHz bandwidth baseband recorder and SGI Origin 3400 supercomputer that can be used together as a pulsar coherent dedispersion system. The telescope signal is routed into the ATNF data acquisition system (DAS) in the same way as for VLBI or correlator observations. The output of the DAS is fed into the eVLBI recorder via the “BG3” cable and the eVLBI software (“vsib_record”) is used to record data to the Hobart XRaid storage unit connected to hovsi.

The data can be processed by the supercomputer at any time, during or after the observations. A set of scripts have been written to automate the transfer and processing of baseband data for pulsar observations. When running, these scripts will copy data from the XRaid to the Origin 3400 one file at a time and run the coherent dedispersion and folding software (“dspsr”) on each file, using an ephemeris from the collection kept in $TZPAR. The Origin 3400 has 24 processors and up to 24 jobs can be run simultaneously. At best (for low dispersion measures) this allows processing at a rate roughly 1/3 real-time.

Changed lines 11-15 from:

When using vsib_record to take pulsar data, please ensure that the DAS is running the profile called PSR64_N.PRO. This profile disables the automatic gain control system, which is essential when observing bright pulsars (otherwise, the AGC tries to remove each incoming pulse and you end up with a large artificial dip on the trailing edge of the profile). This profile causes the DAS to run in 64 MHz mode, which requires a special cable (the BG3 cable) to interface between the correlator ports on the DAS and the input to the VSIC converter card. The vsib_record program should be run with the arguments “-m 2 -w 64″ to ensure correct operation.

Data can be recorded to any of the large devices connected to the eVLBI machine, “hovsi”, in a subdirectory called “pulsar”. For example, to use the first set of XRaid disks, record to “/data/xraid0_0/pulsar/”. Within the pulsar directory, you should construct a series of nested directories named after the source, day of year and observing frequency. This directory structure is crucial. At the moment, no information regarding the telescope coordinates or system setup can be stored in the baseband data files, so the pulsar processing software reads all the information it needs from the names of the directories in which the data are stored. You should start with the source name in J2000 format. For the Vela pulsar this would be “J0835–4510″. Inside the source directory you should create one (or more) directories named for the data, in the format “YYYY-DOY”. For example, 2007_183. Inside the date directory, you should create directories named after the observing frequency in MHz. Files should be recorded inside these frequency directories.

Once data is flowing to a storage area on hovsi, you can log on to the Origin 3400 and begin processing. See Aidan for details as the system is still somewhat experimental.

to:

When using vsib_record to take pulsar data, please ensure that the DAS is running the profile called PSR64_N.PRO. This profile disables the automatic gain control system, which is essential when observing bright pulsars (otherwise, the AGC tries to remove each incoming pulse and you end up with a large artificial dip on the trailing edge of the profile). This profile operates the DAS in 64 MHz mode, which requires a special cable (the BG3 cable) to interface between the correlator ports on the DAS and the input to the VSIC converter card. This is quite different to the “normal” eVLBI mode of operation where the S2 data output port it used. The vsib_record program should be run with the arguments “-m 2 -w 64″ to ensure correct operation.

Data can be recorded to any of the mass storage devices connected to the eVLBI machine, “hovsi”, in a subdirectory called “pulsar”. For example, to use the first set of XRaid disks, record to “/data/xraid0_0/pulsar”. Within the pulsar directory, you should construct a series of nested directories named after the source, day of year and observing frequency. This directory structure is critical. At the moment, no information regarding the telescope coordinates or system setup can be stored in the baseband data files produced by vsib_record, so the pulsar processing software reads all the information it needs from the names of the directories in which the data are located. You should start with the source name in J2000 format. For the Vela pulsar this would be “J0835–4510″. Inside the source directory you should create one (or more) directories named for the date, in the format “YYYY-DOY”. For example, 2007_183. Inside the date directory, you should create directories named after the observing frequency in MHz. Files should be recorded inside these frequency directories.

Once data is flowing to a storage area on hovsi, you can begin processing it with the Origin. See Aidan for details as the system is still somewhat experimental.

July 05, 2007, at 06:03 AM by aidan -
Changed lines 3-19 from:

Mt Pleasant is equiped with a dual-pol, 64 MHz bandwidth baseband recorder and SGI Origin 3400 supercomputer that can be used together as a pulsar coherent dedispersion system. The telescope signal is routed into the ATNF DAS in the same way as for a VLBI or spectral line correlator observation. The output of the DAS is fed into the eVLBI recorder via the “BG3” cable and the eVLBI software (“vsib_record”) is used to record data to the Hobart XRaid storage unit.

The data can be processed by the supercomputer at any time, during or after the observations. A set of scripts have been written to automate the transfer and processing of baseband data for pulsar observations. When running, these scripts will copy data from the XRaid to the Origin 3400 one file at a time and run the coherent dedispersion and folding software (“dspsr”) on each file, using an ephemeris from the collection kept in $TZPAR. The Origin 3400 has 24 processors and up to 24 jobs can be run simultaneously. At best (for low dispersion measures) this allows processing at a rate roughly 1/3 of real-time.

Processed files are transferred across the network to a TPAC-based mass storage device that is mounted as /imports/tpac/pulsar on the radio astronomy server, ares.

to:

Mt Pleasant is equiped with a dual-pol, 64 MHz bandwidth baseband recorder and SGI Origin 3400 supercomputer that can be used together as a pulsar coherent dedispersion system. The telescope signal is routed into the ATNF DAS in the same way as for a VLBI or spectral line correlator observation. The output of the DAS is fed into the eVLBI recorder via the “BG3” cable and the eVLBI software (“vsib_record”) is used to record data to the Hobart XRaid storage unit.

The data can be processed by the supercomputer at any time, during or after the observations. A set of scripts have been written to automate the transfer and processing of baseband data for pulsar observations. When running, these scripts will copy data from the XRaid to the Origin 3400 one file at a time and run the coherent dedispersion and folding software (“dspsr”) on each file, using an ephemeris from the collection kept in $TZPAR. The Origin 3400 has 24 processors and up to 24 jobs can be run simultaneously. At best (for low dispersion measures) this allows processing at a rate roughly 1/3 of real-time.

Processed files are transferred across the network to a TPAC-based mass storage device that is mounted as /imports/tpac/pulsar on the radio astronomy server, ares.

Changed lines 11-31 from:

When using vsib_record to take pulsar data, please ensure that the DAS is running the profile called PSR64_N.PRO. This profile disables the automatic gain control system, which is essential when observing bright pulsars (otherwise, the AGC tries to remove each incoming pulse and you end up with a large artificial dip on the trailing edge of the profile). This profile causes the DAS to run in 64 MHz mode, which requires a special cable (the BG3 cable) to interface between the correlator ports on the DAS and the input to the VSIC converter card. The vsib_record program should be run with the arguments “-m 2 -w 64″ to ensure correct operation.

Data can be recorded to any of the large devices connected to the eVLBI machine, “hovsi”, in a subdirectory called “pulsar”. For example, to use the first set of XRaid disks, record to “/data/xraid0_0/pulsar/”. Within the pulsar directory, you should construct a series of nested directories named after the source, day of year and observing frequency. This directory structure is crucial. At the moment, no information regarding the telescope coordinates or system setup can be stored in the baseband data files, so the pulsar processing software reads all the information it needs from the names of the directories in which the data are stored. You should start with the source name in J2000 format. For the Vela pulsar this would be “J0835–4510″. Inside the source directory you should create one (or more) directories named for the data, in the format “YYYY-DOY”. For example, 2007_183. Inside the date directory, you should create directories named after the observing frequency in MHz. Files should be recorded inside these frequency directories.

Once data is flowing to a storage area on hovsi, you can log on to the Origin 3400 and begin processing. See Aidan for details.

to:

When using vsib_record to take pulsar data, please ensure that the DAS is running the profile called PSR64_N.PRO. This profile disables the automatic gain control system, which is essential when observing bright pulsars (otherwise, the AGC tries to remove each incoming pulse and you end up with a large artificial dip on the trailing edge of the profile). This profile causes the DAS to run in 64 MHz mode, which requires a special cable (the BG3 cable) to interface between the correlator ports on the DAS and the input to the VSIC converter card. The vsib_record program should be run with the arguments “-m 2 -w 64″ to ensure correct operation.

Data can be recorded to any of the large devices connected to the eVLBI machine, “hovsi”, in a subdirectory called “pulsar”. For example, to use the first set of XRaid disks, record to “/data/xraid0_0/pulsar/”. Within the pulsar directory, you should construct a series of nested directories named after the source, day of year and observing frequency. This directory structure is crucial. At the moment, no information regarding the telescope coordinates or system setup can be stored in the baseband data files, so the pulsar processing software reads all the information it needs from the names of the directories in which the data are stored. You should start with the source name in J2000 format. For the Vela pulsar this would be “J0835–4510″. Inside the source directory you should create one (or more) directories named for the data, in the format “YYYY-DOY”. For example, 2007_183. Inside the date directory, you should create directories named after the observing frequency in MHz. Files should be recorded inside these frequency directories.

Once data is flowing to a storage area on hovsi, you can log on to the Origin 3400 and begin processing. See Aidan for details as the system is still somewhat experimental.

July 05, 2007, at 06:01 AM by aidan - pulsar processing instructions
Added lines 29-42:

Data can be recorded to any of the large devices connected to the eVLBI machine, “hovsi”, in a subdirectory called “pulsar”. For example, to use the first set of XRaid disks, record to “/data/xraid0_0/pulsar/”. Within the pulsar directory, you should construct a series of nested directories named after the source, day of year and observing frequency. This directory structure is crucial. At the moment, no information regarding the telescope coordinates or system setup can be stored in the baseband data files, so the pulsar processing software reads all the information it needs from the names of the directories in which the data are stored. You should start with the source name in J2000 format. For the Vela pulsar this would be “J0835–4510″. Inside the source directory you should create one (or more) directories named for the data, in the format “YYYY-DOY”. For example, 2007_183. Inside the date directory, you should create directories named after the observing frequency in MHz. Files should be recorded inside these frequency directories.

Once data is flowing to a storage area on hovsi, you can log on to the Origin 3400 and begin processing. See Aidan for details.

July 05, 2007, at 05:54 AM by aidan -
Added lines 1-2:

Coherent Dedispersion

Changed lines 15-28 from:

a rate roughly 1/3 of real-time.

to:

a rate roughly 1/3 of real-time.

Processed files are transferred across the network to a TPAC-based mass storage device that is mounted as /imports/tpac/pulsar on the radio astronomy server, ares.

Instructions

When using vsib_record to take pulsar data, please ensure that the DAS is running the profile called PSR64_N.PRO. This profile disables the automatic gain control system, which is essential when observing bright pulsars (otherwise, the AGC tries to remove each incoming pulse and you end up with a large artificial dip on the trailing edge of the profile). This profile causes the DAS to run in 64 MHz mode, which requires a special cable (the BG3 cable) to interface between the correlator ports on the DAS and the input to the VSIC converter card. The vsib_record program should be run with the arguments “-m 2 -w 64″ to ensure correct operation.

July 05, 2007, at 05:37 AM by aidan -
Added lines 1-13:

Mt Pleasant is equiped with a dual-pol, 64 MHz bandwidth baseband recorder and SGI Origin 3400 supercomputer that can be used together as a pulsar coherent dedispersion system. The telescope signal is routed into the ATNF DAS in the same way as for a VLBI or spectral line correlator observation. The output of the DAS is fed into the eVLBI recorder via the “BG3” cable and the eVLBI software (“vsib_record”) is used to record data to the Hobart XRaid storage unit.

The data can be processed by the supercomputer at any time, during or after the observations. A set of scripts have been written to automate the transfer and processing of baseband data for pulsar observations. When running, these scripts will copy data from the XRaid to the Origin 3400 one file at a time and run the coherent dedispersion and folding software (“dspsr”) on each file, using an ephemeris from the collection kept in $TZPAR. The Origin 3400 has 24 processors and up to 24 jobs can be run simultaneously. At best (for low dispersion measures) this allows processing at a rate roughly 1/3 of real-time.

Edit - History - Print - Recent Changes - Search
Page last modified on February 03, 2017, at 03:43 AM