Changes between Version 3 and Version 4 of fullforce_intro

Timestamp:

Dec 10, 2013, 3:22:21 PM (13 years ago)

Author:

bills

Comment:

--

fullforce_intro

@@ -8 +8 @@
 version.
 
-The new full force stages of the pipeline will take these results
-back to the input exposures and measure psf and extended source photometry
-using the staticsky measurements as calibrated by skycal.
+The new full force stages of the pipeline will take certain static sky parameters
+back to the input exposures and measure psf and extended source photometry. 
 
-The input paramters for the full force photometry is a 'cff' file.
+The input parameters for the full force photometry are contained in a 'cff' file.
 For efficiency these will be generated during skycal processing.
 An optional processing stage is outlined here which may be used to
@@ -18 +17 @@
 the processing are necessary).
 
-After full force has been run for all of the  warps for a given skycell
+After full force has been run for all of the warps for a given skycell
 and filter, the results are then summarized though a TBD process.
 
@@ -54 +53 @@
 In that case skycal_id, and input_path_base would move there.
 
-At this level we're really doing the processing on the skycell, so the
+At this level we're really doing the processing on skycells, so the
 grouping by exposure might be less interesting. Avoiding the extra
-table simplifies things.
+table simplifies code.
 
 Is the 'Warp' in the table name needed? Would we ever do fullforce on
@@ -104 +103 @@
 }}}
 
-When processed this thing goes and generates a summary based on all of the
-results. (Kind of like addstar and dvo)
+When this thing is processed the results from the multiple warps are analyzed and we magically
+get the parameters for any object in the visible universe ;)
+(Kind of like addstar and dvo).
 
 XXX: At this stage should we be combining the 5 filter results for each