Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.naic.edu/~palfa/doc/palfa.notes.050802 Дата изменения: Tue Aug 2 19:49:48 2005 Дата индексирования: Sun Apr 10 06:22:34 2016 Кодировка:

NOTES FOR PALFA OBSERVING (1 August 2005):

===============================================================================
[A. GENERATE SCHEDULE FILES AND UPDATE DATABASE]

0) Make sure you have palfa group permissions for your a/c
1) Log into fusion00 as yourself from any terminal.
2) Run
~palfa/bin/fill_observed
[y; passwd: 305m_adm] (to update database)

~palfa/bin/plot_pointings
(to see pointings that have been done)

~palfa/bin/makeobs_new
(to generate obs for current MJD (default) or a specific value
if mjd is specified at the command line)

autosched.cmd written locally [and postscript
file generated]; cp autosched.cmd to /share/obs4/usr/pulsar/p2030/autosched_date.cmd;
present file names have 'N' in their names since only the Northern
pointing of each set of 3 is being chosen, in sparse sampling mode)

===============================================================================
[B. ENSURE THAT THERE IS SUFFICIENT DISK SPACE]

Check the two firewire disks on each WAPP to make sure there is sufficient disk
space by logging into each wapp with ssh -l wapp wappn and doing a
df /export/firen1 and df /export/firen2 (n = 1, 4).
Roughly 130 Gbytes of space is needed for each session.

If there is not sufficient disk space, then a new firewire disk will need to be
formatted and swapped for one of the old ones. To do this on wappred1,

Log into wappred1 as root.
Unmount firewire disk (if one is already mounted).
umount /dev/sdd1 (do a dmesg if you are unsure what the device name is)
Remove and replace with disk to be used for observing.
wappred1 will recognize disk and tell you the device name (e.g. /dev/sdd1).
Mount firewire disk.
mount /dev/sdd1
Make a new filesystem.
mkfs.ext3 -T largefile4 -L VOLUME_ID /dev/sdd1
(VOLUME_ID is "palfa_c105" or similar)
Unmount disk.
umount /dev/sdd1

etc...until all disks have new filesystems.

To replace full disks on the wapp, for each wapp in turn, as root:

Save the "ls -l" output for the to-be-removed firewire disk in a file.
Unmount existing firewire disk.
umount /export/firen2 (or similar)
Remove and replace with new disk.
Mount new disk.
mount /export/firen2
(Sometimes there is a bit of a delay before the wapp will recognize the new
disk, so be patient!)
Change the ownership to wapp.
chown wapp /export/firen2
===============================================================================
[C. ENSURE LINKS ARE SET UP SO THAT DATA GETS WRITTEN TO FIREWIRE DISKS]

In each of the 4 WAPPs in turn, check that the soft link /share/wappn1 (where
n=1,2,3,4) points to the firewire disk that you would like to write to
(/export/firen1 or /export/firen2)

If not, then do the following as root --- for example on wapp3....

cd /share
rm wappn1
ln -s wappn1 /export/firen2
etc...

If there are non-PALFA observing sessions that will use the WAPPs before the next
PALFA run, switch the links back to /export/wappn1 (etc) at the end of the observing
session.

===============================================================================
[D. COLLECT DATA IN CONTROL ROOM]

Log in to observer2 as dtusr (get password from operator)

Click right mouse: 'CIMA online GUI', normal default version

Fill in box with 'Observers', 'Program' (p2030) and click on 'pulsar'

Click on ALFA, Disable quick Tsys, Select receiver now, Dismiss

[To monitor individual beam levels: in a separate X-term: alfaobswin &; Note
that levels in beam 1b are always low.]

On CIMA observer's interface:

Load/Save State:

- Load a saved state (alfa_pulsar_scan_1420_gui)
- Dismiss

Pointing Control:

- Catalog: e.g., psr_bright.cat

- Select bright pulsar for testing (B1933+16 is a good one!); point

Receiver IF/LO Control:

- New improved IFLO setup
- Apply this setup
- Dismiss

Click on Pulsar Observing:

In 'WAPP Datataking Control GUI'

- Configuration:

For setting levels:
Click on sum chans and change to 2 chan mode
Copy WAPP1 to all
Start Monitor
Auto Attenuation
Stop Observation

To check known pulsar, switch to 512 us sampling, 64 channels, and 32-bit mode. (Click on
wapp1 to select 32 bits).

Check known pulsar by running "Monitor" and, from wapp1, log in as user wapp and
run 'snap'. Click on 'Continuous' to get snap going. This can be done from dataview to get
a prettier color display. Stop Obs and close snap when happy.

Switch back to search params at end of run. Switch back to 64 us sampling, 256 channels,
16-bit, and summed chans mode and Copy WAPP1 to all. Take a short test observation of bright
pulsar after switching back. It is VERY IMPORTANT to do this test observation as the new params
will not be loaded unless this is done. Also nice to have this test observation for an immediate
check of the realtime processing.

Click 'More' in 'WAPP Datataking Control GUI', then 'Pulsar Catalog Observing'

Catalog: ap_cd1.cat
Command file: /share/obs4/usr/pulsar/p2030/autosched_25Jul05.cmd (open)
Click on 'Start WAPP Pulsar Catalog Observation'

To stop taking data: in 'AO Observer Display', click on 'End at next loop'
to stop after present integration, or 'Abort observation' to end now.
To restart on same command file after stopping, make sure the line
chosen does the paralactify command (presently, even lines on file,
starting with line 2).

To log in comments (which eventually get recorded in database): 'User
preferences', 'Log user comments'

===============================================================================
[E. START REALTIME PROCESSING]

On the dataview (or other) terminal, log into aspmaster as user alfa, run 'realtime',
click on 'Quick Processing' and wait for the pulsars to start rolling in!

==END===END===END===END===END===END===END===END===END===END===END===END===END==