Changes between Version 2 and Version 3 of IppTools_FAQ

Timestamp:

May 19, 2009, 3:53:51 PM (17 years ago)

Author:

giebink

Comment:

--

IppTools_FAQ

@@ -43 +43 @@
 For example, you can set up a chipRun with just the g-band MD01 exposures:
 
-<code>chiptool  <font color=green>-set_label MD01.g</font> -set_workdir /data/ipp004.0/gpc1/MD.SR -dbname PS1MD -definebyquery -ra_min 0.6 -ra_max 0.645 -decl_min -0.08 -decl_max -0.07 -exp_time_min 200 -filter g.00000 -simple</code>
+{{{
+chiptool -set_label MD01.g -set_workdir /data/ipp004.0/gpc1/MD.SR -dbname PS1MD -definebyquery -ra_min 0.6 -ra_max 0.645
+-decl_min -0.08 -decl_max -0.07 -exp_time_min 200 -filter g.00000 -simple
+}}}
 
 and then later on  (after initiating several other chipRuns for other fields and filters) you want to make a stack from all those exposures that you labeled with MD01.g:
 
-<code>stacktool -workdir MD.SR -dbname PS1MD -definebyquery <font color=green>-select_label MD01.g</font> -simple</code>
- 
+{{{
+stacktool -workdir MD.SR -dbname PS1MD -definebyquery<font color=green>-select_label MD01.g -simple
+}}} 
+
 ==== blocking ====
-If you have been consistently applying labels as you inject your data or as you start your chip processes, then you can efficiently use the ippTools label-blocking feature to select out just a particular subset that you do (or don't) want to process right away.  In any ippTool, use the <code>-block</code> option to set a block on a particular label.  Use <code>-unblock</code> to remove that block.  The <code>-masked</code> and <code>-unmasked</code> options will print out a list showing which exposures are carrying what labels, and whether or not they are currently being blocked from processing.  
+If you have been consistently applying labels as you inject your data or as you start your chip processes, then you can efficiently use the ippTools label-blocking feature to select out just a particular subset that you do (or don't) want to process right away.  In any ippTool, use the -block option to set a block on a particular label.  Use -unblock to remove that block.  The -masked and -unmasked options will print out a list showing which exposures are carrying what labels, and whether or not they are currently being blocked from processing.  
 
 === chiptool ===
@@ -66 +71 @@
 ==== -definebyquery ====
 
-You must define a workdir with <code>-workdir</code>.  It is recommended to use <code>-label</code> to keep things organized.  
+You must define a workdir with -workdir.  It is recommended to use -label to keep things organized.  
 
-use the <code>-select_</code> options to pick out the warped skyfiles you want to combine.  The <code>select_good_frac_min</code> option requires that each contributing skyfile has to have that fraction of its area with good pixels.
+use the -select_ options to pick out the warped skyfiles you want to combine.  The select_good_frac_min option requires that each contributing skyfile has to have that fraction of its area with good pixels.
 
-<code>-random</code> : if your <code>select</code> settings return a large number of skyfiles, then you may not want to stack them all together.  The random flag allows you to pick out a random subset from the collection of all matching skyfiles. 
+-random : if your select settings return a large number of skyfiles, then you may not want to stack them all together.  The random flag allows you to pick out a random subset from the collection of all matching skyfiles. 
 
-<code>-min_num</code> : you may only want to execute the stack when it has a certain number of contributing skyfiles.  Specifying the -min_num option tells stacktool to return an empty set unless it has at least min_num skyfiles. 
+-min_num : you may only want to execute the stack when it has a certain number of contributing skyfiles.  Specifying the -min_num option tells stacktool to return an empty set unless it has at least min_num skyfiles. 
 
-<code>-min_new</code>  : ??
+-min_new<  : ??
 
-<code>-min_frac</code> : ??
+-min_frac : ??
 
 
@@ -94 +99 @@
 ==== -definepoprun ====
 
-Use this option to set up a pop run (populated? popular? popsicle?) where you can explicitly specify the ID of both your template and input images.  Each may be either a warped skyfile (use <code>-input_warp_id</code> or <code>-template_warp_id</code>) or a summed skyfile produced by a previous stackRun (use <code>-input_stack_id</code> or <code>-template_stack_id</code>).
+Use this option to set up a pop run (populated? popular? popsicle?) where you can explicitly specify the ID of both your template and input images.  Each may be either a warped skyfile (use -input_warp_id or -template_warp_id) or a summed skyfile produced by a previous stackRun (use -input_stack_id or -template_stack_id).
 
 ==== -definebyquery ====