Changes between Version 2 and Version 3 of fullforce_intro
- Timestamp:
- Dec 10, 2013, 3:12:25 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
fullforce_intro
v2 v3 25 25 === Tables === 26 26 27 27 Here are my ideas for the structure of the tables. 28 28 29 29 {{{ … … 81 81 }}} 82 82 83 When process ed reads the skycal cmf and generates a cff file. Ehh why bother.83 When processing this run the skycal cmf and generates a cff file. Why bother. 84 84 Why not just create a new skycalRun? Because the skycalRun might have already 85 been used to build psps, etc and so we probably shouldn't rerun calibration. 85 been used to build psps, etc and so we probably shouldn't confuse things by 86 reruning calibration. 86 87 87 88 … … 114 115 == TOOL == 115 116 117 As usual we will define a tool for managing the tables. 116 118 117 119 {{{ … … 120 122 121 123 modes 122 -definebyquery define fullforce runs124 -definebyquery define fullforce runs 123 125 usual args to select warps 124 126 … … 131 133 132 134 -set_ arguments for all other parameters 133 -addresult134 -revert135 -updateffrun135 -addresult 136 -revert 137 -updateffrun 136 138 137 139 138 -definecffgenerate define a cffGenerateRun which will make a140 -definecffgenerate define a cffGenerateRun which will make a 139 141 cff file for a stack from the skycal outputs 140 142
