Changes between Version 10 and Version 11 of PSNSC_MOPS
- Timestamp:
- Feb 21, 2017, 1:05:11 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PSNSC_MOPS
v10 v11 44 44 * image files uncompressed -- either in processing or a copy on ipp032 -- ~10TB/night extra space used (20TB since data kept for 36hrs), processing seems ok (network i/o, dtime, faults were all acceptable) 45 45 * update w-band template stacks -- see below 46 * could be using WS for i-band always -- need to test detection threshold like done for WWdiff (test chunk is in w-band, but use same threshold for all filters in WW )46 * could be using WS for i-band always -- need to test detection threshold like done for WWdiff (test chunk is in w-band, but use same threshold for all filters in WWdiff and even that could/should be adjusted at least for dynamic s/n cuts in MOPS) 47 47 * exposure uniqueness required -- update .mops catalog format? (see below) 48 48 * publishing -- TBD … … 54 54 w-band stack update for WSdiff -- 55 55 * best seeing, uniform pixel coverage, WS level depth (about 10-20 best inputs to possibly allow quad stacks as well) 56 * warps ready, need to run stacking and evaluate coverage (cleanup of poor edge cases) 57 * by default will use the different LAP.PV3W set RA~7-16hr unless find a problem 56 58 57 59 MOPS test samples -- 58 * daily MOPS test quad -- label MOPS.dailytestset -- [wiki:MOPS.dailytestset] still in development60 * daily MOPS test quad -- label MOPS.dailytestset -- [wiki:MOPS.dailytestset] -- still in development 59 61 * ops tag modification test chunk -- [wiki:MOPS.testchunk.OSSR.R15S2.0.Q.w.20140603] 60 62 * necessary comparison set for WW and WS diff for any development/modifications to ops tag 63 * need to define a test chunk for i-band probably -- different s/n dynamics? different stacks in WSdiffs at the very least 61 64 * special case test quads -- fast movers, comets, other? -- quads need to be selected/defined and run through IPP 62 65 * more automated checking for missing visit WWdiffs -- create by exposure status table in czardb for a night reset @initday?
