User Tools

Site Tools


lbaops:producingschedules

Differences

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

Link to this comparison view

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