PSNSC_NCU requirements and notes (draft) --

NCU observations -- processing needs to be finished by early morning for MOPS to use for NEO

• obs_mode NCU -- new, possibly start end Oct 2016
  • 4 chunks (returns) -- NCU1B...NCU4B; NCU1A...NCU4A -- see sequence below
    • B=color set, sequence wgwrwiwz per chunk (8 targets each)
    • A=w-band only, wwwwwwww (8 targets each)
  • 8 targets (fields) -- NCU1.1...NCU1.8; NCU2.1...NCU2.8; NCU3.1...NCU3.8 ; NCU4.1...NCU4.8 (chunk#.target#)
    • 4 above, 4 below ecliptic centered around opposition
  • no dither in a night (no rotation like MD/QUB/FSS) -- offset done each night mean motion retrograde (W along ecliptic, ~0.3 degrees?)
  • exposures per field --
    • griz -- A: 1/chunk * 4 chunks = 4
    • w --
      • B: 4/chunk * 4 chunks = 16
      • A: 8/chunk * 4 chunk = 32
  • 4 sequential nights, ~6 hr/night?
  • exptimes wgriz: 60,120,120,120,180s
  • run sequence then? or is color done each night? where is the dither offset added, for each chunk?
    • night 1: NCU1B, NCU2B, NCU3B, NCU4B -- only color queue -- return to exact position, no dither
    • night 2: NCU1A, NCU2A, NCU3A, NCU4A -- only w queue -- return each time to position (no dither), but has target/field center motion shift
    • night 3: NCU1A, NCU2A, NCU3A, NCU4A -- only w queue -- return each time to position (no dither), but has target/field center motion shift
    • night 4: NCU1A, NCU2A, NCU3A, NCU4A -- only w queue -- return each time to position (no dither), but has target/field center motion shift
  • comment string -- needs to be descriptive and easily parsed, need to check with MOPS for WS grouping/parsing issues (spaces) --
    • B: old format: NCU1B w4 NCU1.1 -- (chunk) (filter)(set number for w) (chunk#.target#) -- want to add "visit #" at end of comment (1-4), move filter location, connect chunk+target names
      • new format -- (chunk)-(chunk#.target#) (filter) (visit #)

        NCU1B-1.1 w visit 1
        NCU1B-1.2 w visit 1
        ...
        NCU1B-1.1 g visit 1
        NCU1B-1.2 g visit 1
        ...
        NCU1B-1.1 w visit 2
        NCU1B-1.2 w visit 2
        ...
        NCU1B-1.1 r visit 1
        ...
        NCU2B-2.1 w visit 1
        NCU2B-2.2 w visit 1
        ...
        NCU2B-2.1 g visit 1
        NCU2B-2.2 g visit 1
        ...
        NCU2B-2.1 w visit 2
        NCU2B-2.2 w visit 2
        ...
        NCU2B-2.1 r visit 1
        ...
        NCU3B-3.1 w visit 1
        ...
        

    • A: old format: NCU1A NCU1.1 -- (chunk) (chunk#.target#) -- add "w" so similar format for B and "visit #" at end of comment (1-8), move filter location, connect chunk+target names
      • new format make similar -- (chunk)-(chunk#.target#) (filter) (visit #)

        NCU1A-1.1 w visit 1
        NCU1A-1.2 w visit 1
        NCU1A-1.3 w visit 1
        ...
        NCU1A-1.1 w visit 2
        NCU1A-1.2 w visit 2
        ...
        NCU1A-1.1 w visit 8
        ...
        NCU2A-2.1 w visit 1
        NCU2A-2.2 w visit 1
        ...
        

• chip->warp normal stdscience pantasks as with xSS products (ipp-20141024 tag)
• WSdiff runs in ~ippmops/stdscience_ws with modified ipp-20141024 ops tag to make uncompressed WSdiffs (like FSS)
  • larger volume, may need more nodes -- must be uncompressed for MOPS stamps since large data volume
• WSdiff published to normal MOPS datastore location?

Processing products -- czar needs to make sure all faults and issues are cleared daily (early morning) for NCU.* products

• chip-cam-warp -- NCU.nightlyscience -- nightly
• warp-stack diffims -- NCU.WS.nightlyscience -- nightly
• publishing of WSdiffs -- (need datastore location to use from MOPS) -- nightly
• manually done -- not czar responsibility
  • nightly stack -- NCU.nightlyscience -- nightly, manually done to avoid any poor images
  • stack-stack diffims -- NCU.SS.nightlyscience -- nightly, likely automatic possible once manual stacks made
• stamps -- TBD

Cleanup --

• chip -- 1 day?
• warp -- 2 days (no specific requirement?)
• WSdiff -- 1 day? uncompressed so likely will need to limit and just do updates for stamps
• publishing WSdiff catalog bundles --
• pstamp -- manual cleanup like other ps_ud_%

Tasks to do --

• verify w-band stacks okay along ecliptic for opposition end October
• check processing rate/nodes for WSdiffs
• MOPS interested in SSdiff?
• publishing location for WSdiff by MOPS preference -- IPP-MOPS-TEST or IPP-MOPS-WS -- unique set so likely normal location