PSNSC_MOPS requirements and notes (draft) --

Processing products

czar needs to make sure all faults and issues are cleared daily (early morning) for OSS, MSS, ESS, ThreePi? products

• chip-cam-warp -- nightly
• warp-stack diffims -- nightly
• datastore of WS diffim catalogs -- nightly
• stamps -- chip only from pstamp, MOPS has own stamp server that requires uncompressed image access

• MOPS looking at using visit 1-2, 2-3 when visit 4 lost due to weather/faults to increase just a pair to triple for tracklets -- currently by request
  • sometime seem to be auto-made and other times not? need update on both when known -- appears to be at least partially due to the .multi nightly science task (which is not right and shouldn't be happening as .multi was supposed to be multiple night return visits?) -- .multi look to be made intranight when the camera stage quality faults on visit 2 & 3 and then makes a visit 1-4 diffim since neither 1 nor 4 is used to make a diffim -- expect other combinations to then be possible as well?
  • lost visit mapping to be done -- typical losses from fault at camera for any visit due to FWHM cut, v4 lost often due to weather/closure

    v1 missing: v2-v3
    v2 missing: v1-v3
    v3 missing: v2-v4
    v4 missing: v2-v3
    

NEO targeted observations

FSS.nightlyscience, FSS.WS -- also needs to be finished by early morning

• obs_mode FSS (new 201608) -- 6 exposure, MD-like dither (rotation) plus small offsets -- so WSdiff only and published to normal MOPS datastore location
• chip->warp normal stdscience pantasks as with xSS
• WSdiff currently runs in ~ippmops/stdscience_ws to make uncompressed WSdiffs

Cleanup

Specific for MOPS needs

• chip -- 1 days
• warp -- ? days (no specific requirement)
• WW, WSdiff -- 1 days -- if disk space issue, can reduce this to 2 days as long as warps uncleaned the update time is minimal
  • maybe longer for the FSS WSdiff since special follow-up field
• datastore WSdiff catalog bundles -- Bill has script doing?
• pstamp -- manual cleanup like other ps_ud_%

Tasks to do

WS diffims for MOPS --

• 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)
• update w-band template stacks -- see below
• 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)
• exposure uniqueness required -- update .mops catalog format? (see below)
• publishing -- TBD

ppTranslate/ppMOPS -- .mops catalog format update/revision --

• evaluate contents again, remove/add new columns as needed -- must add skycell_id, chip XY and position
• merge WW and WSdiff catalog publishing to single product if possible -- conflict with timing possibly

w-band stack update for WSdiff --

• best seeing, uniform pixel coverage, WS level depth (about 10-20 best inputs to possibly allow quad stacks as well)

MOPS test samples --

• daily MOPS test quad -- label MOPS.dailytestset -- MOPS.dailytestset still in development
• ops tag modification test chunk -- MOPS.testchunk.OSSR.R15S2.0.Q.w.20140603
  • necessary comparison set for WW and WS diff for any development/modifications to ops tag
• special case test quads -- fast movers, comets, other? -- quads need to be selected/defined and run through IPP
• more automated checking for missing visit WWdiffs -- create by exposure status table in czardb for a night reset @initday?