Changes between Version 70 and Version 71 of Processing

Timestamp:

Jul 2, 2010, 8:23:36 AM (16 years ago)

Author:

rhenders

Comment:

--

Processing

@@ -20 +20 @@
 = Using {{{pantasks}}} =
 
-There are numerous {{{pantasks}}} servers. Their status can be checked with [http://ipp004.ifa.hawaii.edu/ippMonitor/czartool_labels.php Czartool], but it is often necessary to use a client directly. To do this {{pantasks_client}}, first move to the directory corresponding to the server of interest, which are all under {{{~ipp}}} on any cluster machine, for example {{{~ipp/stdscience/}}}, then run
+There are numerous {{{pantasks}}} servers. Their status can be checked with [http://ipp004.ifa.hawaii.edu/ippMonitor/czartool_labels.php Czartool], but it is often necessary to use a client directly. To do this, first move to the directory corresponding to the server of interest, which are all under {{{~ipp}}} on any cluster machine. For example, go to {{{~ipp/stdscience/}}}, then run
 
 {{{
@@ -59 +59 @@
 }}}
    
-The first column, 'AV', translates to Active and Valid, i.e. whether a process is running and whether it is valid at this point in time. For example, above, {{{+- ns.initday.load}}} is active, but is not valid at present since it is scheduled to run only once per day (to initialize the {{{nightlyscience}}} automation).
+The first column, 'AV', translates to '''A'''ctive and '''V'''alid, i.e. whether a process is running and whether it is valid at this point in time. For example, above, {{{+- ns.initday.load}}} is active, but is not valid at present since it is scheduled to run only once per day (to initialize the {{{nightlyscience}}} automation).
 
 The key thing to monitor here is the {{{Nfail}}} column. Depending on the process, different numbers of Nfail as a proportion of Njobs are deemed acceptable.
@@ -65 +65 @@
 = Morning duties: checking {{{summitcopy}}} and {{{burntool}}} =
 
-There is nothing to be processed if data has not been copied from the telescope. This is the job of {{{summitcopy}}}, which runs TODO every day. You can check that it has successfully copies files by TODO
-
-
-{{{burntool}}} is the next stage. Easiest way to check is to run the following in the stdscience {{{pantasks_client}}}
-
-
+There is nothing to be processed if data has not been copied from the telescope. This is the job of {{{summitcopy}}}, which runs slowly through night, then speeds once observations are complete every day. You can check that it has successfully copies files using [http://ipp004.ifa.hawaii.edu/ippMonitor/czartool_labels.php Czartool].
+
+After {{{summitcopy}}} comes {{{burntool}}}. Easiest way to check this is to run the following in the stdscience {{{pantasks_client}}}
 
 {{{
@@ -78 +75 @@
 You should see a 'book' entry with today's date, like
 
-
 {{{
 2010-05-27 BURNING
 }}}
-
 
 If not, something is wrong.
@@ -354 +349 @@
 Running {{{neb-host}}} with no arguments gives you a summary of the above for all hosts.
 
-= Rebuilding the IPP code =
-
-The IPP in use presently is located at
-
-{{{
-~ipp/ipp-20100211
-}}}
-
-If the code needs an update and rebuild, then:
-
- * stop pantasks (as above)
- * {{{cd ~ipp/ipp-20100211}}}
- * {{{svn update}}}
- * {{{psbuild -dev -optimize}}}
- * restart pantasks (as above)
+= Changing the code =
+
+This might mean rebuilding the current 'tag' (reflected in the directory name) or actually installing a new tag.
+
+== Rebuilding the current tag ==
+
+We will use the example of tag 20100701 which is store under 
+
+{{{
+~ipp/src/ipp-20100701
+}}}
+
+To update the code and rebuild, shutdown all {{{pantasks}}} (as shown above) then do the following.
+
+{{{
+cd ~ipp/src/ipp-20100701
+svn update
+psbuild -dev -optimize
+}}}
+
+
+Now restart all {{{pantasks}}} (as above).
+
+== Installing a new tag ==
+
+
+* shutdown all {{{pantasks}}} (as shown above)
+* change {{{~ipp/.tcshrc}}} to point at the new tag (it is good to confirm by logging out and in again)
+* fix the files which are still installation specific:
+ * edit {{{~ipp/.ptolemyrc}}  and change {{{CONFDIR}}} to point at the new location
+ * copy {{{nebulous.site.pro}}} to the working location (for now, just use the last installation version) eg
+
+{{{
+cp psconfig/ipp-20100623.lin64/share/pantasks/modules/nebulous.site.pro psconfig/ipp-20100701.lin64/share/pantasks/modules/nebulous.site.pro
+}}}
+
+
+* restart all {{{pantasks}}} (as above)
 
 = Who to contact =