User Tools

Site Tools


lbaops:producingschedules

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
lbaops:producingschedules [2006/03/12 08:24]
elenc
lbaops:producingschedules [2006/03/12 08:40]
elenc
Line 1: Line 1:
-Here are John Reynolds' instructions for producing SNAP and procedure\\+Here are John Reynolds' instructions for producing SNAP and procedure\ 
-files from ATCA schedules:\\\ +files from ATCA schedules:\
-\\\ +
-  -  Prepare AT SCHED schedule, as normal, on LEON.\ +
-   Allow additional setup time at Narrabri for calibration.\ +
-   Add 5 second offset to the reference time to synchronise ATCA source\ +
-   changes correctly.\+
 \ \
-  -  on LEON;\+1. Prepare AT SCHED schedule, as normal, on LEON.\ 
 +    *  Allow additional setup time at Narrabri for calibration.\ 
 +    *  Add 5 second offset to the reference time to synchronise ATCA source changes correctly.\
 \ \
-      $ run/nodebug at$run:vsched   (from VLBI account, $ VSCHED will do)\\+2. on LEON;\ 
-      AT schedfile : v100e2\\+      $ run/nodebug at$run:vsched   (from VLBI account, $ VSCHED will do)\ 
-      next file [none] :\\+      AT schedfile : v100e2\ 
-      FORTRAN STOP\\+      next file [none] :\ 
-      $ dd v100e2.*.\\\ +      FORTRAN STOP\ 
-\\\ +      $ dd v100e2.*.\
-      Directory $2$DKA300:[AT.SCHED]\\\ +
-\\\ +
-      V100E2.CAT;                   2/3        8-NOV-1998 11:45:47.45\\\ +
-      V100E2.DRG;                  16/18       8-NOV-1998 11:45:47.26\\\ +
-      V100E2.LBA;                   9/9        8-NOV-1998 11:45:47.37\\\ +
-      V100E2.SCH;                 172/174      8-NOV-1998 00:02:37.14\\\+
 \ \
-   The .DRG file is then used (next step) to make a simple SNAP file.\ +      Directory $2$DKA300:[AT.SCHED]\
-   The .LBA file is a skeleton for the LBA correlator.SCH file, while the\ +
-   .CAT file contains the source positions in standard AT format and can\ +
-   be simply copied to elleba::cor$db:*.TAB. (Note: these won't\ +
-   necessarily be the most precise positions for some sources though).\ +
-   The confusing naming conventions (.LBA => .SCH, .CAT => .TAB) are\ +
-   unfortunate legacies, but we're stuck with them short-term).\+
 \ \
-           $ skedr\ +      V100E2.CAT;                   2/3        8-NOV-1998 11:45:47.45
-           Input DRUDG file  v088i1.drg\\+      V100E2.DRG;                  16/18       8-NOV-1998 11:45:47.26
-\\\ +      V100E2.LBA;                   9/9        8-NOV-1998 11:45:47.37
-           Station code to select [P] :\\\ +      V100E2.SCH;                 172/174      8-NOV-1998 00:02:37.14
-\\\ +     The .DRG file is then used (next step) to make simple SNAP file. The .LBA file is a skeleton for the LBA correlator.SCH filewhile the .CAT file contains the source positions in standard AT format and can be simply copied to elleba::cor$db:*.TAB. (Note: these won't necessarily be the most precise positions for some sources though). The confusing naming conventions (.LBA => .SCH, .CAT => .TAB) are unfortunate legacies, but we're stuck with them short-term).\
-           Experiment name: [v088i1] :\\+
-            Write ATCA schedule [N] :\\\ +
-            Snap file epoch [J2000] :\\+
-           Station PARKES   : mount type AZEL\\\ +
-           Sources read from SKED file:     5\\\ +
-           SOURCE: 0823-500 has   scans\\\ +
-           SOURCE: 1718-649 has   1 scans\\\ +
-           SOURCE: J1729-22 has 111 scans\\\ +
-           SOURCEPSR1730  has 104 scans\\\ +
-           SOURCE1730-130 has   6 scans\\+
-\\\ +
-           Scans by baseline to selected station:\\\ +
-           ATCA01   PARKES   MOPRA\\\ +
-            223      223      223\\\ +
-            Normal Stop\\\ +
-\\\ +
-  -  The above produces skeleton SNAP file called, in this case,\ +
-   v088i1.snp which may now be hand-edited to add tape control.+
-   This is fairly straightfoward, but does require care and checking.\ +
-   See any recent examples of snap files to see how this is done.\+
 \ \
-  -  The companion .prc file is usually cribbed from any recent, similar+3Make the SNAP file\ 
-   experiment, modifying the experiment and, and the S2 mode where+          $ skedr
-   necessary.\+           Input DRUDG file :  v088i1.drg\
 \ \
-----\\\ +           Station code to select [P] :\ 
-\\\ +
-The second schedule is the field system schedule.  Again for most LBA\\+           Experiment name: [v088i1] :\ 
-observations this will be provided but for VSOP observations it needs\\+            Write ATCA schedule [N] :\ 
-to be made.  In case the field system schedule needs to be made, there\\+            Snap file epoch [J2000] :\ 
-are at least two ways to make it.  Firstly, and most simply if the\\+           Station PARKES   : mount type AZEL\ 
-user is inexperienced with the VLBI scheduling software SCHED (by \\+           Sources read from SKED file:     5\ 
-Craig Walker, NRAO), the ATCA schedule can be sent to John Reynolds\\+           SOURCE: 0823-500 has   1 scans\ 
-well before the experiment.  From the ATCA schedule the field\\+           SOURCE: 1718-649 has   1 scans\ 
-system schedules can be made for all the participating telescopes \\+           SOURCE: J1729-22 has 111 scans\ 
-and delivered to the correct places.\\+           SOURCE: PSR1730  has 104 scans\ 
-\\+           SOURCE: 1730-130 has   6 scans\ 
-Secondly, if the user is experienced with SCHED, they may wish to\\+\ 
-produce all of the schedules themselves.  In this case it is suggested\\+           Scans by baseline to selected station:
-that while preparing the schedule they consult John Reynolds and/or\\+           ATCA01   PARKES   MOPRA\ 
-Tasso Tzioumis, for advice on setup files, S2 configurations etc.\\+            223      223      223\ 
-When the keyin format file is prepared and passed through the SCHED\\+            Normal Stop\ 
-software the output includes two files, <filename>.sum and \\+
-<filename>.skd.  These are the two files of interest for producing\\+4. The above produces a skeleton SNAP file called, in this case, v088i1.snp which may now be hand-edited to add tape control. This is fairly straightfoward, but does require care and checking. See any recent examples of snap files to see how this is done.\ 
-the field system schedules.  To do this, follow these steps:\\+
-\\+5. The companion .prc file is usually cribbed from any recent, similar experiment, modifying the experiment and, and the S2 mode where necessary.\ 
-FTP the <filename>.sum and <filename>.skd files to one of the field system\\+
-pc machines (whichever is convenient).  At Narrabri this machine is\\+----\ 
-called v1ca.  Login with username oper.\\+
-\\+The second schedule is the field system schedule.  Again for most LBA\ 
-Move the two files to /usr2/sched\\+observations this will be provided but for VSOP observations it needs\ 
-\\+to be made.  In case the field system schedule needs to be made, there\ 
-Type drudg to run the software that converts the <filename>.skd file\\+are at least two ways to make it.  Firstly, and most simply if the\ 
-to the field system schedule.  Select the station you wish to create\\+user is inexperienced with the VLBI scheduling software SCHED (by \ 
-schedules for.  Select options 3 (create snap file) and 12 (create\\+Craig Walker, NRAO), the ATCA schedule can be sent to John Reynolds\ 
-procedure file).\\+well before the experiment.  From the ATCA schedule the field\ 
-\\+system schedules can be made for all the participating telescopes \ 
-Repeat the above procedure until all the schedules are made for all the\\+and delivered to the correct places.\ 
-stations.\\+
-\\+Secondly, if the user is experienced with SCHED, they may wish to\ 
-Move the snap file <filename>.snp for each station to the corresponding\\+produce all of the schedules themselves.  In this case it is suggested\ 
-field system machine in /usr2/sched and likewise the procedure file \\+that while preparing the schedule they consult John Reynolds and/or\ 
-<filename>.prc to /usr2/proc.  Alternatively, place all of the \\+Tasso Tzioumis, for advice on setup files, S2 configurations etc.\ 
-schedules on the VLBI FTP server in Epping and tell all of the relevant\\+When the keyin format file is prepared and passed through the SCHED\ 
-people at each station where they are so that they can be picked up\\+software the output includes two files, <filename>.sum and \ 
-and placed in the correct areas.\\+<filename>.skd.  These are the two files of interest for producing\ 
-\\+the field system schedules.  To do this, follow these steps:\ 
-Also, from the <filename>.skd file it is possible to create the CAOBS\\+
-schedule for the ATCA and the VLOBS schedule for Mopra.  This is done\\+FTP the <filename>.sum and <filename>.skd files to one of the field system\ 
-via a PERL script that can be found in \\+pc machines (whichever is convenient).  At Narrabri this machine is\ 
-\\+called v1ca.  Login with username oper.\ 
-/data/MORPHEUS_1/tingay/observing/vlba2sched/vlba2sched\\+
-\\+Move the two files to /usr2/sched\ 
-Run it on the <filename>.skd file by typing\\+
-\\+Type drudg to run the software that converts the <filename>.skd file\ 
-vlba2sched <filename>\\+to the field system schedule.  Select the station you wish to create\ 
-\\+schedules for.  Select options 3 (create snap file) and 12 (create\ 
-and selecting ATCA or Mopra for the schedule output.  The output will\\+procedure file).\ 
-be a <filename>_**.com file which can be run in the ATCA SCHED\\+
-software by going into SCHED and typing @<filename>_**.com\\+Repeat the above procedure until all the schedules are made for all the\ 
-\\+stations.\ 
-This PERL script is still under development and several things need to\\+
-be altered by hand in SCHED.  It is worth listing the SCHED output \\+Move the snap file <filename>.snp for each station to the corresponding\ 
-against the <filename>.sum file to see that the scan times etc all\\+field system machine in /usr2/sched and likewise the procedure file \ 
-agree.\\+<filename>.prc to /usr2/proc.  Alternatively, place all of the \ 
-\\+schedules on the VLBI FTP server in Epping and tell all of the relevant\ 
-The SCHED output should be placed in at$sched on LEON for the ATCA or\\+people at each station where they are so that they can be picked up\ 
-in at$sched on MOPRA for Mopra, or on the VLBI FTP server in Epping.\\\+and placed in the correct areas.\ 
 +
 +Also, from the <filename>.skd file it is possible to create the CAOBS\ 
 +schedule for the ATCA and the VLOBS schedule for Mopra.  This is done\ 
 +via a PERL script that can be found in \ 
 +
 +/data/MORPHEUS_1/tingay/observing/vlba2sched/vlba2sched\ 
 +
 +Run it on the <filename>.skd file by typing\ 
 +
 +vlba2sched <filename>
 +
 +and selecting ATCA or Mopra for the schedule output.  The output will\ 
 +be a <filename>_**.com file which can be run in the ATCA SCHED\ 
 +software by going into SCHED and typing @<filename>_**.com\ 
 +
 +This PERL script is still under development and several things need to\ 
 +be altered by hand in SCHED.  It is worth listing the SCHED output \ 
 +against the <filename>.sum file to see that the scan times etc all\ 
 +agree.\ 
 +
 +The SCHED output should be placed in at$sched on LEON for the ATCA or\ 
 +in at$sched on MOPRA for Mopra, or on the VLBI FTP server in Epping.\
  
  
lbaops/producingschedules.txt · Last modified: 2015/12/18 16:39 (external edit)