Changes between Version 1 and Version 2 of AddStar_PV2
- Timestamp:
- Oct 10, 2014, 2:26:53 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
AddStar_PV2
v1 v2 63 63 This is a bit tricky, because we do the first one first, STOP IT, then make a hosttable.dat and dvodist -out it 64 64 65 65 1. Decide which stscii will be the head node (usually I've been using either stsci00 or stsci01), and edit ippdvo2's ippconfig/site.config so that the slice we are working on (for this example, slice04.cam), points to stsci00.1 (or whatever disk is decided). Check that there is at least 500GB of space on the chosen drive. 66 66 67 67 68 68 2. queue the 'segments' 69 69 {{{ 70 70 survey.add.merge cam.slice04.0 LAP.PV2.V2.20130717.slice04.cam LAP.PV2.V2.slice04.0.cam … … 82 82 * the exception is the pole is one segment : LAP.PV2.V2.pole.cam (no segments) 83 83 84 84 3. check mysql that the first segment is loaded 85 85 86 86 {{{ … … 88 88 }}} 89 89 90 90 4. once there is at least 1 mergedvodbRUn listed, start the merge on that and turn it off: 91 91 add.mergedvodb LAP.PV2.V2.20130717.slice04.cam 92 92 mergedvodb.merge.on … … 95 95 }}} 96 96 97 97 5. wait for the merge to be done, without faults, for that first one 98 98 99 99 6. copy hosttable from one of the other LAP.ThreePi slices, do the following edits: 100 100 * make sure the slice# is correct 101 101 * make sure it is skycal or cam (as necessary) … … 103 103 * do not use stsci drives with < 500GB -- find those in the HostTable.dat and shift around as necessary 104 104 105 105 7. dvodist -out (path) 106 106 107 107 8. go back to pantasks and 108 108 109 109 {{{ … … 111 111 }}} 112 112 113 113 9. periodically check with commands 114 114 115 115 {{{ … … 117 117 }}} 118 118 119 119 10. if it faults, it needs to be redone (but you can set the mergedvodbProcessed.fault = 0 and the mergedvodbRun.state = 'broken', and revert to find if the others work fine 120 120 121 121 {{{
