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