Context Navigation

Changes between Version 11 and Version 12 of PS1_Operations

Timestamp:: Jun 2, 2010, 5:31:51 PM (16 years ago)
Author:: heather
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

PS1_Operations

-              v11
+              v12
  * replication: ippdb00
  * update: ippc13
  * pstamp: TBD
+ * pstamp: ippdb02
  * detrend: ippc06
  * addstar: ipp004
 …
 == Pantasks Servers ==
+=== Summit Copy ===
+All the servers start exactly the same way.  Their input files come pre-configured with a set of hosts, labels (and in the case of stdscience, survey tasks).  Everything is ready to go.  This is how to start one of the pantasks, for example, !SummitCopy:
  * Check which machine to use for the server, [wiki:PS1_Operations#Pantasks above].
 …
  * Start the server:
 {{{
 % ssh ipp@ippc07
+% ssh ipp@ippc01
 % cd summitcopy
 % pantasks_server &
 …
 }}}
+=== Registration ===
+ * Check which machine to use for the server, above.
+ * Start the server:
+{{{
+% ssh ipp@ippc09
+% cd registration
+% pantasks_server &
+}}}
+ * Start the client:
+{{{
+% cd ~ipp/registration
+% pantasks_client
+pantasks: server input input
+pantasks: setup
+pantasks: run
+}}}
+=== Replication ===
+ * Check which machine to use for the server, above.
+ * Start the server:
+{{{
+% ssh ipp@ippc004
+% cd replication
+% pantasks_server &
+}}}
+ * Start the client:
+{{{
+% cd ~ipp/replication
+% pantasks_client
+pantasks: server input input
+pantasks: setup
+pantasks: run
+}}}
+=== Standard science ===
+ * Check which machine to use for the server, above.
+ * Start the server:
+{{{
+% ssh ipp@ippc10
+% cd stdscience
+% pantasks_server &
+}}}
+ * Start the client:
+{{{
+% cd ~ipp/stdscience
+% pantasks_client
+pantasks: server input input
+pantasks: setup
+pantasks: load.hosts.wave1
+pantasks: load.hosts.wave2
+pantasks: load.hosts.wave3
+pantasks: load.hosts.compute
+pantasks: run
+pantasks: add.label (label)
+}}}
+Add as many hosts as needed.  Something like 1x1, 3x2, 4x3, 4xC is probably needed full full-scale operations.
+ * Add the survey automation information:
+{{{
+pantasks: survey.add.diff (label) (dist_group) (workdir)
+pantasks: survey.add.magic (label) (workdir)
+pantasks: survey.add.destreak (label) (workdir)
+pantasks: survey.add.dist (label)
+}}}
+Note that the magic and destreak workdir values currently must not be nebulous names, but UNIX paths.  For example:
+{{{
+pantasks: survey.add.diff throughput.20091104 throughput.20091104 neb://@HOST@.0/gpc1/throughput.20091104
+pantasks: survey.add.magic throughput.20091104 /data/ipp050.0/gpc1_destreak/throughput.20091104
+pantasks: survey.add.destreak throughput.20091104 /data/ipp050.0/gpc1_destreak/throughput.20091104
+pantasks: survey.add.dist throughput.20091104
+}}}
+=== Detection publication ===
+ * Check which machine to use for the server, above.
+ * Start the server:
+{{{
+% ssh ipp@ippc08
+% cd publishing
+% pantasks_server &
+}}}
+ * Start the client:
+{{{
+% cd ~ipp/publishing
+% pantasks_client
+pantasks: server input input
+pantasks: setup
+pantasks: run
+}}}
+=== Postage Stamp Server ===
+ * Check which machine to use for the server, above.
+ * Start the server:
+{{{
+% ssh ipp@ipp049
+% cd pstamp
+% pantasks_server &
+}}}
+ * Start the client:
+{{{
+% cd ~ipp/pstamp
+% pantasks_client
+pantasks: server input input
+pantasks: setup
+pantasks: add.hosts
+pantasks: run
+}}}
+=== Detrend Creation ===
+ * Check which machine to use for the server, above.
+ * Start the server:
+{{{
+% ssh ipp@ippc06
+% cd detrend
+% pantasks_server &
+}}}
+ * Start the client:
+{{{
+% cd ~ipp/detrend
+% pantasks_client
+pantasks: server input input
+pantasks: setup
+pantasks: run
+}}}
+If all of the pantasks need to be started or stopped, it is more efficient to use check_system.sh.
 == IPP User backup and restore ==
 …
 Important files in the home directory of the IPP user on the MHPCC cluster are saved to a backup with the script ~ipp/make.backup.  This uses rsync to save copies to a target backup location (currently /data/ipp004.0/ipp/operations).  To restore from this directory, use rsync.
+== Clean Checkout and Compile of IPP software ==
+Make sure the trunk compiles. When it compiles, make a tag, for example:
+{{{
+svn copy https://svn.pan-starrs.ifa.hawaii.edu/repo/ipp/trunk https://svn.pan-starrs.ifa.hawaii.edu/repo/tags/ipp-20100601
+}}}
+and checkout a copy of this tag into ~ipp/src/ipp-20100601
+compile it, using:
+{{{
+psbuild -ops -extbuild
+}}}
+This builds it with the required magic libraries (and
+errors out if magic cannot be built), and sets the '-dev' option as
+well (builds ippdb.src rather than using the checked in version).
+If database changes are required, update BOTH gpc1 and isp, to keep them in sync.
+Currently, the following files need to be updated, to point to the current build:
+ * .tcshrc
+ * .ptolemyrc
+ * addstar/ptolemyrc
+and the following file will need to be copied to the new location:
+ * psconfig/(OLD_BUILD).lin64/share/pantasks/modules/nebulous.site.pro
 == Updating Magic Code ==
 The magic and related software is stored in ~ipp/magic_tarballs with names like magic.20091023.tgz and ssa-core-cpp.20091023.tgz.  The active release is linked to ~ipp/magic.tgz and ~ipp/ssa-core-cpp.tgz.  If a magic update is provided, place the source code in magic_tarballs with an equivalent name and update the ~ipp link.  To build the new code, it is necessary to update the tree in the ipp build directory.  Go to the top-level magic directory in the tree (eg, ~ipp/ipp-svn/magic) and do the following steps:
+The magic and related software is stored in ~ipp/magic_tarballs with names like magic.20091023.tgz and ssa-core-cpp.20091023.tgz.  The active release is linked to ~ipp/magic.tgz and ~ipp/ssa-core-cpp.tgz.  If a magic update is provided, place the source code in magic_tarballs with an equivalent name and update the ~ipp link. The new code can be built manually (as opposed to using psbuild -ops), these are the steps. To build the new code, it is necessary to update the tree in the ipp build directory.  Go to the top-level magic directory in the tree (eg, ~ipp/ipp-svn/magic) and do the following steps:
 {{{
 psconfigure