User Tools

Site Tools


software:pcfs

This wiki is not maintained! Do not use this when setting up AuScope experiments!

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
software:pcfs [2011/01/20 01:43]
Jamie McCallum
software:pcfs [2019/08/12 23:11]
Guifre
Line 1: Line 1:
-====== PCFS utilities ​======+====== PCFS ======
  
-**FS clock errors**+**FS 9.11 updates**
  
-If the FS is complaining frequency of a formatter ​to FS time difference > 0.5s, it may be necessary ​to recalibrate the drift rate+Notes: 
 +  * [[software:FS 9.12.13| New 9.12.13 VGOS branch]] 
 +  * [[software:​yg_9.11.7_to_9.11.19| 9.11.7 ​to 9.11.19 at Yg]] 
 +  * [[software:​ke_9.11.1_to_9.11.4|9.11.1 ​to 9.11.4 at Ke]] 
 +  * [[software:​hb_9.11.3_to_9.11.4|9.11.3 to 9.11.4 at Hb]] 
 +  * [[software:​yg_9.11.3_to_9.11.4|9.11.3 to 9.11.4 at Yg]] 
 +  * [[software:​hb_9.10.5_to_9.11.3|9.10.5 to 9.11.3 at Hb]] 
 +  * [[software:​yg_9.11.2_to_9.11.3|9.11.2 to 9.11.3 at Yg]] 
 +  * [[software:​yg_9.11.1_to_9.11.2|9.11.1 to 9.11.2 at Yg]] 
 +  * [[software:​ke_9.10.4_to_9.11.1|9.10.4 to 9.11.1 at Ke]]
  
-The procedure is outlined in /​usr2/​fs/​misc/​fstime.txt +**FS v9.10.4**
-The guts of the procedure is:+
  
 +This version of the FS system is running all 3 of the AuScope sites.
 +It is installed into the usual /usr2 location.
 +The only major deviation from a standard install is the /​usr2/​control being a softlink to a directory /​usr2/​control.[hb|ke|yg].
  
-  - Ordered List Item Make sure there is a "​sy=run setcl &" in the "​initi"​ procedure of +Another relevant directory ​is /​usr2/​AuscopeUtils,​ which contains any AuScope code which is not reasonably stored within ​the control.* or st-9.10.4 directory.
-   the "​station"​ procedure library. ​ It should go as early as possible +
-   in the procedure. +
- - Make sure there is a "​sy=run setcl adapt &" in the "​midob"​ +
-   ​procedure in "​station"​. +
- Set-up the "time.ctl" file with the following steps ​Please note +
-   that this procedure should be repeated whenever you change FS +
-   ​computers or upgrade kernels. ​ Another case where you should redo +
-   this step is if the crystal has either because of aging or other +
-   ​reasons,​ like replacement,​ changed significantly in rate.+
  
-    - Put the following line in your "time.ctl" ​file as the only +This code is all stored within ​the "pcfs_prod" ​git repository on observer@ops-serv2:/​home/​observer/​gits/​pcfs_prod.git (see the section on [[software:​git|git]] for more instructions).
-      non-comment line:+
  
-        0.000 0.010 rate+**FS Updating Procedures**
  
-   B. Start the FS+Updating this code would be a matter of upgrading one site, git-adding ​the new fs-? and st-? directories,​ and git-rming the old ones after an appropriate settling period when the migration was confirmed to be successful. 
 +Obviously they could be git-rmed immediately,​ but this would be less convenient to roll back if problems were found.
  
-   CExecute ​the SNAP command: "sy=run setcl offset &"+Some care would need to be taken when migrating the contents of the new '​control'​ directory into the existing onesThe specific steps which will be taken will vary depending on the extent of the changes in the new FS. 
 +====== PCFS utilities ======
  
-   D. Leave the computer running for about one hour.  You can start +**FS clock errors**
-      and stop the FS, login and logout as many times as you wish. +
-      Just don't reboot the computer. +
- +
-   E. Execute the SNAP command: "​sy=run setcl rate &"​ +
- +
-   F. Execute the SNAP command: "​sy=run setcl save &"​ +
- +
-   G. At a shell prompt execute: +
- +
-        cd /​usr2/​control +
-        mv time.new time.ctl +
- +
-   As long as there were no communication or permission ​errors, your +
-   "​time.ctl"​ file should be updated with a reasonable rate value. +
-*** +
- +
-We can perform this after the observation,​ and it should be fixed. Until +
-we fix it properly by getting a permanent machine to replace the dead +
-hobart.+
  
-T+If the FS is complaining frequency of a formatter to FS time difference > 0.5s, it may be necessary to recalibrate the drift rate. The procedure is outlined in /​usr2/​fs/​misc/​fstime.txt. The guts of the procedure is:
  
  
-On Tue, 2010-08-10 at 09:45 +1000, Brett Reid wrote: +  ​Make sure there is "​sy=run setcl &" in the "​initi"​ procedure of the "​station"​ procedure library It should go as early as possible in the procedure
-> > Hi Guys, +  - Make sure there is a "​sy=run ​setcl adapt &" in the "​midob"​ procedure in "​station"​
-> > We are running ​different pcfs computer. +  - Set-up the "time.ctl" file with the following steps.  ​Please note that this procedure should be repeated whenever you change ​FS computers or upgrade kernels ​Another case where you should redo this step is if the crystal has either because of aging or other reasons, like replacement,​ changed significantly in rate. 
-> > On the new system we are getting error such as below+    * Put the following ​line in your "time.ctl" file as the only non-comment line:\\ \\ 0.000 0.010 rate \\ \\ 
-> >  +    * Start the FS 
-> > 2010.221.23:​15:​39.44?​ERROR sc  -13 setcl: formatter to FS time  +    * Execute the SNAP command"sy=run setcl offset ​&" 
-> > difference 0.5 seconds or greater +    * Leave the computer running for about one hour You can start and stop the FSlogin and logout as many times as you wishJust don't reboot the computer
-> > 2010.221.23:​17:​44.13?​ERROR sc  -13 setcl: formatter to FS time  +    * Execute the SNAP command"​sy=run ​setcl rate &" 
-> > difference 0.5 seconds or greater +    * Execute the SNAP command"​sy=run ​setcl save &" 
-> > 2010.221.23:​19:​45.09?ERROR sc  -13 setcl: formatter to FS time  +    * At a shell prompt execute:\\ \\ cd /usr2/control\\ mv time.new time.ctl\\ \\ As long as there were no communication or permission errors, your "time.ctl" file should be updated with reasonable rate value.
-> > difference 0.5 seconds ​or greater +
-> >  +
-> > Running sy=run setcl offset produces ​the following+
-> >  +
-> > 2010.221.23:​19:​45.09?​ERROR sc  ​-13 setclformatter to FS time  +
-> > difference ​0.5 seconds or greater +
-> > 2010.221.23:20:11.20;sy=run setcl offset +
-> > 2010.221.23:​20:​11.26#​setcl#​time/​1757666966,0,​2010,​221,​23,​20,​11.09,-4.259,​0.789,​-11 +
-> > 2010.221.23:20:11.26#setcl#​model/​old,​1263819362,​-2043,​1757382975,​-0.778,​1.543,​rate,​0,​unknown,​11,​0 +
-> > 2010.221.23:20:11.15#setcl#​model/​new,​1263819362,​-2057,​1757666966,​-0.778,​1.543,​rate,​0 +
-> >  +
-> >  +
-> > However the problem is not permanently fixed. +
-> >  +
-> > We have seen this before. I just cannot remember how to fix it  +
-> > permanently. Any ideas greatly appreciated. +
-> >  +
-> > We are running R1433 currently. +
-> >  +
-> > Regards, +
-> > Brett +
-> >  +
-> >  +
--- ##############################################​ Timothy Hoban VLBI Developer http://www-ra.phys.utas.edu.au/​auscope School of Maths and Physics University of Tasmania ##############################################​ Guilt should be a momentary pang to spur one into corrective actionAnything longer is wasted, and worse, selfish. - Mark Belletini ​+
/home/www/auscope/opswiki/data/pages/software/pcfs.txt · Last modified: 2019/08/12 23:11 by Guifre