Changes between Version 4 and Version 5 of fullforce_intro

Timestamp:

Dec 11, 2013, 12:05:48 PM (13 years ago)

Author:

bills

Comment:

--

fullforce_intro

@@ -27 +27 @@
 
 {{{
-fullForceWarpRun
-    ffw_id
-    warp_id
-    skycal_id           (sets sky_id and through stack_id, filter, 
-                         tess_id, skycell_id)
-    input_path_base     path that leads to cff file 
-                        Note: this is independent of the method
-                        used to generate the data. 
-                        The expectation is that the cffs will be generated
-                        during skycal processing. The data has been
-                        read and is available. zero point is done.
+CREATE TABLE fullForceRun (
+    ff_id           BIGINT NOT NULL AUTO_INCREMENT,
+    warp_id         BIGINT,
+    skycal_id       BIGINT,
+    sources_path_base VARCHAR(255),
+    state           VARCHAR(64),
+    workdir         VARCHAR(255),
+    label           VARCHAR(64),
+    data_group      VARCHAR(64),
+    dist_group      VARCHAR(64),
+    reduction       VARCHAR(64),
+    registered TIMESTAMP DEFAULT CURRENT_TIMESTAMP, -- time run was registered
+    PRIMARY KEY(ff_id),
+    KEY(state),
+    KEY(label),
+    KEY(data_group),
+    KEY(warp_id),
+    KEY(skycal_id),
+    FOREIGN KEY(warp_id) REFERENCES warpRun(warp_id),
+    FOREIGN KEY(skycal_id) REFERENCES skycalRun(skycal_id)
+) ENGINE=innodb DEFAULT CHARSET=latin1;
 
-    workdir
-    reduction           as usual specifies the recipe
-    label
-    data_group
-    dist_group
 }}}
 
@@ -57 +62 @@
 table simplifies code.
 
-Is the 'Warp' in the table name needed? Would we ever do fullforce on
-a diff or stack? I'm hesitant to use the stage, stage_id style structure
-(addRun, distribution) since that makes everything more complicated.
-The code sharing ends up being somewhat illusory.
+Note that this structure ties the full force run to a warp. One could imagine
+doing running it on a chip, diff, or stack. I'm hesitant to use the stage, stage_id style structure
+(addRun, distribution) because that makes everything more complicated.
+The code sharing ends up being somewhat illusory. Are five 10 line functions really
+better than one 50 line function with lots of cases?
 
 
@@ -107 +113 @@
 (Kind of like addstar and dvo).
 
-XXX: At this stage should we be combining the 5 filter results for each
-skycell? 
 
 ----