IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links
wiki:LAPintoPSPS

Version 50 (modified by heather, 13 years ago) ( diff )

--

  1. Ingest of LAP into PSPS
    1. Processing of LAP cam / skycal
    2. Queue LAP cam / skycal
    3. Build LAP cam skycal by slices
    4. Merge dvodb into big dvodb
    5. IPPtoPSPS creates batches based on slices
    6. PSPS loads batches
    7. Slices
    8. Heather's Notes on addstar etc
      1. First slice
        1. Statistics on slice18
      2. slice 18.2
      3. slice 16.2
      4. slice 8
      5. slice 8.2
      6. slice 10
      7. slice 10.2
      8. slice 12 and slice 12.2
      9. slice 14 and slice 14.2
      10. slice 16 and 16.2
      11. slice 18.2 and slice 18 skycal (redo)
      12. slice 20
      13. pause
      14. slice 22
      15. slice 00
      16. slice 02
      17. slice 04

Ingest of LAP into PSPS

This wiki describes the ingest of LAP processing (specifically, LAP.ThreePi.20120706) into PSPS. There are several steps (not all completely finished)

Processing of LAP cam / skycal

This is currently ongoing. The first slice is to do between 18hr and 20hr (which contains kepler). This is called slice18, see the description of the slices below. Once all the projections cells within slice18 (or slicexx) are done, we start building the minidvodbs

Queue LAP cam / skycal

Once all the cam/skycals are processed within slice18, they will be queued to be built as a pair of minidvodbs:

These are not like typical minidvodbs in the sense that they will not be restricted to the 500 entries or < 1 day old rules. This may be changed, however depending on how things go.

Some minor tasks:

  • add feature to addtool to queue by area of sky (this is apparently already done)
  • add tweaks to the minidvodb script so that we don't create new minidvodbs every day or 500 entries

Build LAP cam skycal by slices

  • once queued this is straightforward. Some tweaks may include to build the minidvodbs around the cluster (not just ipp004/ipp005)
  • see progress on either heather's addstar wiki (link) or from ippmonitor

Merge dvodb into big dvodb

  • we do not merge while ipptopsps is running. Once a slice of sky has been ingested and once ipptopsps stops, then we merge more slices together into the big one.
  • once the slices are merged into a big parallel dvodb, run the resort/averages/relphot commands on the big dvodb
  • note that we should only do the slices 1 at a time and on a machine with a lot of memory (ie ipp064). slice10 + slice10.part2 caused relphot to get swappy on ipp004 (22hr and I quit it), slice10 + ipp064 took 2 hours on relphot. 
    addstar -resort (stuff)
setphot -D CATDIR $catdir -update -ubercal -no-metadata ~ipp/ucalqw_noref.fits
relphot -D CATDIR $catdir -statmode WT_MEAN -max-density 2000 -basic-image-search -update g,r,i,z,y -nloop 16 -boundary-tree ~ipp/RINGS.V3.tree.v2.fits -D CAMERA gpc1
relastro -D CATDIR $catdir -update-objects -reset -update -D CAMERA gpc1 -D CATDIR $catdir

IPPtoPSPS creates batches based on slices

  • this happens once the merge is done for that slice and the relphot/addstar commands are run at a minimum on that slice. To avoid boundary problems, ippToPSPS will be 3 degrees less on all edges (see slices below)
  • the intent is to load neighboring slices. So, after slice18 is loaded, we load slice16, and the ranges within ipptopsps would be:
    • ra: 243 - 297 deg
    • dec: -33 to 75 deg
    • this is a combination of slice16 and slice18 with a 3 degree border, and i propose that we be very conservative with the cap.
  • task: need ways to monitor this

PSPS loads batches

  • nothing to say here, conrad or thomas can fill in details

Slices

These are the following slices, labeled by Heather. The goal is to load connected slices (ie if slice18 is first then load either slice20 or slice 16 next). This was last updated 4-11.

slice name ipptopsps ra dec cam skycal dvodb loccam skycal merged merged relphoted ingested by comments
load order addstar addstar mergeable mergeable cam skycal etc ipptopsps
slice0 0 to 2hr 20 to 75 deg yes yes ipp004 yes yes
slice0.2 0 to 2hr -30 to 20 deg yes yes ipp004 yes yes
slice2 2 to 4hr 20 to 75 deg yes yes ipp005 yes yes
slice2.2 2 to 4hr -30 to 20 deg yes in prog ipp005/007/008/009 yes in prog
slice4 4 to 6hr 20 to 75 deg
slice4.2 4 to 6hr -30 to 20 deg
slice6 6 to 8hr 20 to 75 deg
slice6.2 6 to 8hr -30 to 20 deg
slice8 8 to 10hr 20 to 75 deg partial partial ipp005 yes yes
slice8.2 8 to 10hr -30 to 20 deg partial partial ipp005 yes yes
slice10 2 * 10 to 12hr 20 to 75 deg done done ipp004 yes yes done done done in progress
slice10.2 3 * 10 to 12hr -30 to 20 deg done done ipp004 yes yes done done done in progress
slice12 4 * 12 to 14hr 20 to 75 deg done done ipp005 yes yes done done
slice12.2 5 * 12 to 14hr -30 to 20 deg done done ipp005 yes yes done done
slice14 14 to 16hr 20 to 75 deg done done ipp004 yes yes done done
slice14.2 14 to 16hr -30 to 20 deg done done ipp004 yes yes done done
slice16 16 to 18hr 20 to 75 deg done done ipp005 yes yes done done
slice16.2 16 to 18hr -30 to 20 deg done done ipp005 yes yes done done
slice18 1 18 to 20hr 20 to 75 deg done done ipp005 delstar in prg yes done done done OB done, P2/ST only kepler area done
slice18.2 18 to 20hr -30 to 20 deg done done ipp005 yes delstar in prog
slice20 20 to 22hr 20 to 75 deg done done ipp004 yes yes
slice20.2 20 to 22hr -30 to 20 deg done in progress ipp004/ipp010
slice22 22 to 24hr 20 to 75 deg done done ipp005 yes yes
slice22.2 22 to 24hr -30 to 20 deg done done ipp005
slice.top 0-24hr 70 -90 deg
  • means this is what is currently planned. this can change prior to the actual load. The ones without a * are the slices already loaded (and their order)
  • cam/skycal addstar : refers to the stage where we make minidvodbs by running addstar on cam/skycal exposures
  • dvodb loc : location where the minidvodbs live
  • cam/skycal mergeable : once a minidvodb is built a number of steps are done for sanity: delstar/addstar-resort/relphot/dvoverify. Once done it is ready to be merged into the big dvodb
  • merged cam/skycal : are the minidvodbs merged into the big dvodb
  • relphoted etc : once merged into the big dvodb, we run a series of commands (addstar resort, setphot, relphot, relastro) to get the dvodb ready for ingest
  • ingested by ipptopsps : have we ingested that slice yet?

The idea is that Heather will load into the dvodb all the exposures (cam stage) with a boresite within the ra/dec range, and all the projection cells within the ra/dec range for a given slice. This means that certainly there will be data outside the edges of the slices within a minidvodb slice. This is ok.

Here are 2 images of the proposed slice order (with the current skycal progress from 2013-03-01):

The goal is to ingest as much of the camera stage as possible, in order to properly calibrate the data

Heather's Notes on addstar etc

what follows now is heather's notes on ingest/slice construction. It will only be interesting to heather (for when other slices are needed), also as a log of what was done

First slice

First slice is slice18, but not entirely (we will only queue from 20 up):

The command to queue: 

addtool -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 
-set_minidvodb_group LAP.slice18.cam -set_minidvodb -set_label LAP.slice18.cam 
-stage cam -uncensored -ra_min 270 -ra_max 300 -decl_min 20 -decl_max 90 -dbname gpc1

and then I added the minidvodb: 

add.minidvodb    LAP.slice18.cam LAP.slice18.cam LAP.20120706 5 GPC1
add.label LAP.slice18.cam

the rest takes care of itself. I will add skycal probably tomorrow, once I verify that this part works fine.

I have queued the skycal after some modifications to addstar: 

 addtool -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice18.skycal -set_minidvodb -set_label LAP.slice18.skycal -stage skycal -ra_min 270 -ra_max 300 -decl_min 20 -decl_max 90 -dbname gpc1 -uncensored -simple

That is 33k of skycells. I add that to addstarlap: 

add.minidvodb    LAP.slice18.skycal LAP.slice18.skycal LAP.20120706 5 GPC1
add.label LAP.slice18.skycal

Statistics on slice18

Here are the statistics on slice18. I wanted to see how ingesting slice18 compares to ingesting the same area of sky with various older surveys (same area of sky)

The sql query : 

mysql> select minidvodb_group, stage,count(*), sum(dtime_addstar)/60/60/24., avg(dtime_addstar) from addProcessedExp join addRun using (add_id) join camRun on cam_id = stage_id join chipRun using (chip_id) join rawExp using (exp_id) where stage = 'cam' and addRun.state = 'full' and ra > 270*3.14/180 and ra < 300*3.14/180 and decl > 20*3.14/180 and decl < 90*3.14/180 group by minidvodb_group;

The result 

+-----------------------------+-------+----------+------------------------------+--------------------+
| minidvodb_group             | stage | count(*) | sum(dtime_addstar)/60/60/24. | avg(dtime_addstar) |
+-----------------------------+-------+----------+------------------------------+--------------------+
| (null)                      | cam   |      100 |            0.066631944444444 |              57.57 | 
| CNP.V2                      | cam   |      154 |            0.026168981376621 |    14.681818122988 | 
| LAP.slice18.cam             | cam   |     8951 |              7.0359143898167 |    67.914535055319 | 
| LAP.ThreePi.20110809        | cam   |     5288 |              4.6303240664607 |    75.654311524622 | 
| LAP.ThreePi.20110809.V2.Cam | cam   |     6532 |              4.4052546205013 |    58.269136437739 | 
| ThreePi                     | cam   |     2547 |              1.3785300813919 |    46.762857884672 | 
| ThreePi.V2                  | cam   |      639 |             0.27396990687759 |    37.043818394716 | 
| ThreePi.V3                  | cam   |     6095 |              3.0291319420299 |    42.939622607282 | 
+-----------------------------+-------+----------+------------------------------+--------------------+

So what can we take from this? First of all it thinks it took ~7 days to ingest almost all of LAP.slice18 (there are about 40 pending). It feels longer than that, more like 1.5 weeks. Heather suspects that this is due to only having dtime_addstar, and not dtime_total in the addProcessedExp table - so I think it should be longer,but not sure by how much. However, this affect will be throughout all processing (they are all processed the same way). What we can see is that slice18 so far has taking the longest time, but the average time is similar to LAP (V2 and 20110809). So it's a bit slower than ThreePi.V3 (I'm not sure why), but not that much slower... One thing that might cause problems is that ipp005 was both creating the dvo db and serving out files for ipptopsps - does this slow it down?

slice 18.2

This is the bottom half of slice 18. To queue the different parts: 

addtool -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 
-set_minidvodb_group LAP.slice18.part2.cam -set_minidvodb -set_label LAP.slice18.part2.cam 
-stage cam -uncensored -ra_min 270 -ra_max 300 -decl_min -35 -decl_max 20 -dbname gpc1

warning - I queued way more skycal than I intended for slice18.skycal - if you use decl instead of dec it doesn't complain and it also doesn't respect it. i set that label to drop

This is ok because the 'spiffing' happens on the mergeddvodb, so it will have all parts for the lower half of slice18 

addtool -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 
-set_minidvodb_group LAP.slice18.part2.skycal -set_minidvodb -set_label LAP.slice18.part2.skycal 
-stage skycal -uncensored -ra_min 270 -ra_max 300 -dec_min -35 -dec_max 20 -dbname gpc1

I am queueing LAP.slice18.part2.skycal (15:00 on 1-15-13). First though is asking pretend how many there are... it's taking more than 3 seconds to do that, so I'm going to go to the colloquium

ok it worked.. had some problems, first: use skycal as stage, not staticsky. second, I had already queued it before, oops. So this time there are only 6000 to process.. that's probably ok

slice 16.2

this is the next slice to be worked on. first step, queue the camera stage, as staticsky is not yet done. 

addtool -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 
-set_minidvodb_group LAP.slice16.part2.cam -set_minidvodb -set_label LAP.slice16.part2.cam 
-stage cam -uncensored -ra_min 240 -ra_max 270 -decl_min -35 -decl_max 20 -dbname gpc1

slice 8

queue cam stage for slice 8 (1-18-2013) 

addtool -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 
-set_minidvodb_group LAP.slice08.cam -set_minidvodb -set_label LAP.slice08.cam 
-stage cam -uncensored -ra_min 120 -ra_max 150 -decl_min 20 -decl_max 75 -dbname gpc1

queue skycal (9.5hr - 10 hr) :

{{{ addtool -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice08.skycal -set_minidvodb -set_label LAP.slice08.skycal -stage skycal -uncensored -ra_min 142.5 -ra_max 150 -dec_min 20 -dec_max 75 -dbname gpc1 -simple

}}}

slice 8.2

queue cam stage for slice 8.2 (1-18-2013) 

addtool -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 
-set_minidvodb_group LAP.slice08.part2.cam -set_minidvodb -set_label LAP.slice08.part2.cam 
-stage cam -uncensored -ra_min 120 -ra_max 150 -decl_min -35 -decl_max 20 -dbname gpc1

queue skycal (only to 9.5hr) (2-4-2013) 

addtool -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice08.part2.skycal -set_minidvodb -set_label LAP.slice08.part2.skycal -stage skycal -uncensored -ra_min 142.5 -ra_max 150 -dec_min -35 -dec_max 20 -dbname gpc1 -simple

slice 10

queue cam stage for slice 10 (2-5-2013) 

addtool -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 
-set_minidvodb_group LAP.slice10.cam -set_minidvodb -set_label LAP.slice10.cam 
-stage cam -uncensored -ra_min 150 -ra_max 180 -decl_min 20 -decl_max 75 -dbname gpc1

queue skycal (2-5-2013) 

addtool -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 
-set_minidvodb_group LAP.slice10.skycal -set_minidvodb -set_label LAP.slice10.skycal 
-stage skycal -uncensored -ra_min 150 -ra_max 180 -dec_min 20 -dec_max 75 -dbname gpc1 -simple

slice 10.2

cam (2-5-2013) 

addtool -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice10.part2.cam -set_minidvodb -set_label LAP.slice10.part2.cam -stage cam -uncensored -ra_min 150 -ra_max 180 -decl_min -35 -decl_max 20 -dbname gpc1 -simple | wc

skycal 2-5-2013 

addtool -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice10.part2.skycal -set_minidvodb -set_label LAP.slice10.part2.skycal -stage skycal -uncensored -ra_min 150 -ra_max 180 -dec_min -35 -dec_max 20 -dbname gpc1 -simple | wc

slice 12 and slice 12.2

queuing these 2-7-2013:

cam stage: 

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice12.part2.cam -set_minidvodb -set_label LAP.slice12.part2.cam -stage cam -uncensored -ra_min 180 -ra_max 210 -decl_min -35 -decl_max 20 -dbname gpc1 -simple | wc

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice12.cam -set_minidvodb -set_label LAP.slice12.cam -stage cam -uncensored -ra_min 180 -ra_max 210 -decl_min 20 -decl_max 75 -dbname gpc1 -simple | wc

skycal stage: 

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice12.part2.skycal -set_minidvodb -set_label LAP.slice12.part2.skycal -stage skycal -uncensored -ra_min 180 -ra_max 210 -dec_min -35 -dec_max 20 -dbname gpc1 -simple | wc

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice12.skycal -set_minidvodb -set_label LAP.slice12.skycal -stage skycal -uncensored -ra_min 180 -ra_max 210 -dec_min 20 -dec_max 75 -dbname gpc1 -simple | wc

slice 14 and slice 14.2

queueing these 2-18-2013

cam stage 

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice14.part2.cam -set_minidvodb -set_label LAP.slice14.part2.cam -stage cam -uncensored -ra_min 210 -ra_max 240 -decl_min -35 -decl_max 20 -dbname gpc1 -simple | wc

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice14.cam -set_minidvodb -set_label LAP.slice14.cam -stage cam -uncensored -ra_min 210 -ra_max 240 -decl_min 20 -decl_max 75 -dbname gpc1 -simple | wc

skycal stage: 

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice14.part2.skycal -set_minidvodb -set_label LAP.slice14.part2.skycal -stage skycal -uncensored -ra_min 210 -ra_max 240 -dec_min -35 -dec_max 20 -dbname gpc1 -simple | wc

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice14.skycal -set_minidvodb -set_label LAP.slice14.skycal -stage skycal -uncensored -ra_min 210 -ra_max 240 -dec_min 20 -dec_max 75 -dbname gpc1 -simple | wc

slice 16 and 16.2

16.2 cam already queued and processed. 16: 

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice16.cam -set_minidvodb -set_label LAP.slice16.cam -stage cam -uncensored -ra_min 240 -ra_max 270 -decl_min 20 -decl_max 75 -dbname gpc1 -simple | wc

skycal 

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice16.part2.skycal -set_minidvodb -set_label LAP.slice16.part2.skycal -stage skycal -uncensored -ra_min 240 -ra_max 270 -dec_min -35 -dec_max 20 -dbname gpc1 -simple | wc

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice16.skycal -set_minidvodb -set_label LAP.slice16.skycal -stage skycal -uncensored -ra_min 240 -ra_max 270 -dec_min 20 -dec_max 75 -dbname gpc1 -simple | wc

slice 18.2 and slice 18 skycal (redo)

this was after I first set all the addRuns and minidvodbs related to skycal aside: 

addtool -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice18.skycal -set_minidvodb -set_label LAP.slice18.skycal -stage skycal -uncensored -ra_min 270 -ra_max 300 -dec_min 20 -dec_max 70 -simple -dbname gpc1 

addtool  -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice18.part2.skycal -set_minidvodb -set_label LAP.slice18.part2.skycal -stage skycal -uncensored -ra_min 270 -ra_max 300 -dec_min -35 -dec_max 20 -simple -dbname gpc1

slice 20

(march 4) queue cam: 

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice20.part2.cam -set_minidvodb -set_label LAP.slice20.part2.cam -stage cam -uncensored -ra_min 300 -ra_max 330 -decl_min -35 -decl_max 20 -dbname gpc1 -simple | wc

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice20.cam -set_minidvodb -set_label LAP.slice20.cam -stage cam -uncensored -ra_min 300 -ra_max 330 -decl_min 20 -decl_max 75 -dbname gpc1 -simple | wc

skycal stage: 

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice20.part2.skycal -set_minidvodb -set_label LAP.slice20.part2.skycal -stage skycal -uncensored -ra_min 300 -ra_max 330 -dec_min -35 -dec_max 20 -dbname gpc1 -simple | wc

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice20.skycal -set_minidvodb -set_label LAP.slice20.skycal -stage skycal -uncensored -ra_min 300 -ra_max 330 -dec_min 20 -dec_max 75 -dbname gpc1 -simple | wc

pause

(march 12)

we had a pause at this point: we discovered duplicate cam/skycals were being ingested. This was fixed (there were 3 bugs required to trigger this):

  1. addstar.pro is safe and doesn't load duplicates now
  2. addstar will quit with an error code if it detects that you try to addstar an exposure that already exists
  3. addtool will quit with an error code if you try to addprocessedexp an already processed one

This prevents future problems. What about the old ones? They all have duplicates, those are removed by delstar. The delstar command was added to minidvodb_premerge.pl (this is the script that prepares a minidvodb to be ready for merging), and all the prior minidvodbs in state 'merge' were set back so that they all have minidvodb_premerge.pl rerun on them (this removes the duplicates).

all things are proceeding now.

slice 22

(march 13)

queue cam: 

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice22.part2.cam -set_minidvodb -set_label LAP.slice22.part2.cam -stage cam -uncensored -ra_min 330 -ra_max 360 -decl_min -35 -decl_max 20 -dbname gpc1 -simple | wc

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice22.cam -set_minidvodb -set_label LAP.slice22.cam -stage cam -uncensored -ra_min 330 -ra_max 360 -decl_min 20 -decl_max 75 -dbname gpc1 -simple | wc

skycal stage: 

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice22.part2.skycal -set_minidvodb -set_label LAP.slice22.part2.skycal -stage skycal -uncensored -ra_min 330 -ra_max 360 -dec_min -35 -dec_max 20 -dbname gpc1 -simple | wc

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice22.skycal -set_minidvodb -set_label LAP.slice22.skycal -stage skycal -uncensored -ra_min 330 -ra_max 360 -dec_min 20 -dec_max 75 -dbname gpc1 -simple | wc

note there's a typo - shouild be ra-min 330 (it was 320?) - didn't hurt us this time

slice 00

(march 27)

queue cam: 

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice00.part2.cam -set_minidvodb -set_label LAP.slice00.part2.cam -stage cam -uncensored -ra_min 0 -ra_max 30 -decl_min -35 -decl_max 20 -dbname gpc1 -simple | wc

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice00.cam -set_minidvodb -set_label LAP.slice00.cam -stage cam -uncensored -ra_min 0 -ra_max 30 -decl_min 20 -decl_max 75 -dbname gpc1 -simple | wc

skycal stage: 

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice00.part2.skycal -set_minidvodb -set_label LAP.slice00.part2.skycal -stage skycal -uncensored -ra_min 0 -ra_max 30 -dec_min -35 -dec_max 20 -dbname gpc1 -simple | wc

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice00.skycal -set_minidvodb -set_label LAP.slice00.skycal -stage skycal -uncensored -ra_min 0 -ra_max 30 -dec_min 20 -dec_max 75 -dbname gpc1 -simple | wc

slice 02

(march 27)

queue cam: 

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice02.part2.cam -set_minidvodb -set_label LAP.slice02.part2.cam -stage cam -uncensored -ra_min 30 -ra_max 60 -decl_min -35 -decl_max 20 -dbname gpc1 -simple | wc

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice02.cam -set_minidvodb -set_label LAP.slice02.cam -stage cam -uncensored -ra_min 30 -ra_max 60 -decl_min 20 -decl_max 75 -dbname gpc1 -simple | wc

skycal stage: 

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice02.part2.skycal -set_minidvodb -set_label LAP.slice02.part2.skycal -stage skycal -uncensored -ra_min 30 -ra_max 60 -dec_min -35 -dec_max 20 -dbname gpc1 -simple | wc

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice02.skycal -set_minidvodb -set_label LAP.slice02.skycal -stage skycal -uncensored -ra_min 30 -ra_max 60 -dec_min 20 -dec_max 75 -dbname gpc1 -simple | wc

slice 04

(april 17)

queue cam: 

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice04.part2.cam -set_minidvodb -set_label LAP.slice04.part2.cam -stage cam -uncensored -ra_min 60 -ra_max 90 -decl_min -35 -decl_max 20 -dbname gpc1 -simple | wc

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice04.cam -set_minidvodb -set_label LAP.slice04.cam -stage cam -uncensored -ra_min 60 -ra_max 90 -decl_min 20 -decl_max 75 -dbname gpc1 -simple | wc

skycal stage: 

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice04.part2.skycal -set_minidvodb -set_label LAP.slice04.part2.skycal -stage skycal -uncensored -ra_min 60 -ra_max 90 -dec_min -35 -dec_max 20 -dbname gpc1 -simple | wc

addtool  -pretend -definebyquery -label LAP.ThreePi.20120706 -set_dvodb LAP.20120706 -set_minidvodb_group LAP.slice04.skycal -set_minidvodb -set_label LAP.slice04.skycal -stage skycal -uncensored -ra_min 60 -ra_max 90 -dec_min 20 -dec_max 75 -dbname gpc1 -simple | wc

Attachments (5)

Download all attachments as: .zip

Note: See TracWiki for help on using the wiki.