User Tools

Site Tools


software:pcfs

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:46]
Jamie McCallum
software:pcfs [2019/08/12 23:11] (current)
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].
 +
 +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.
 +
 +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).
 +
 +**FS Updating Procedures**
 +
 +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.
 +
 +Some care would need to be taken when migrating the contents of the new '​control'​ directory into the existing ones. The specific steps which will be taken will vary depending on the extent of the changes in the new FS.
 +====== PCFS utilities ======
 +
 +**FS clock errors**
  
-  - Ordered List Item Make sure there is a "​sy=run setcl &" in the "​initi"​ procedure ​of +If the FS is complaining frequency ​of a formatter to FS time difference > 0.5sit may be necessary to recalibrate ​the drift rate. The procedure is outlined in /usr2/fs/​misc/​fstime.txtThe guts of the procedure is:
-   the "​station"​ procedure library. ​ It should go as early as possible +
-   in the procedure. +
- - Ordered List Item Make sure there is "​sy=run setcl adapt &" in the "​midob"​ +
-   ​procedure in "​station"​. +
- - Ordered List Item 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. +
-   * Unordered List Item Put the following line in your "time.ctl" file as the only +
-      non-comment line:\\ +
-        ​0.000 0.010 rate +
-   * Unordered List Item Start the FS +
-   * Unordered List Item Execute the SNAP command: "​sy=run setcl offset &"​ +
-   * Unordered List Item Leave the computer running for about one hour.  You can start +
-      and stop the FSlogin and logout as many times as you wish. +
-      Just don't reboot ​the computer. +
-   * Unordered List Item Execute the SNAP command: "​sy=run setcl rate &"​ +
-   * Unordered List Item Execute the SNAP command: "​sy=run setcl save &"​ +
-   * Unordered List Item 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. 
  
 +  - Make sure there is a "​sy=run setcl &" in the "​initi"​ procedure of 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 non-comment line:\\ \\ 0.000 0.010 rate \\ \\
 +    * Start the FS
 +    * Execute the SNAP command: "​sy=run setcl offset &"
 +    * Leave the computer running for about one hour.  You can start and stop the FS, login and logout as many times as you wish. Just don't reboot the computer.
 +    * Execute the SNAP command: "​sy=run setcl rate &"
 +    * Execute the SNAP command: "​sy=run setcl save &"
 +    * 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.
/home/www/auscope/opswiki/data/attic/software/pcfs.1295487961.txt.gz · Last modified: 2011/10/26 06:37 (external edit)