Summary for MD.PV2

  • MediumDeepFields summary page -- quick links to all up to date refstacks
  • MD.GR0 summary page -- summary of all reprocessing details and 2011/2012 refstacks and some deepstack samples
  • MD.PV1 summary page -- the data set that PV2 update reprocessing is based on

This is a summary of the MD.PV2 update processing (as started with MD04 in MD04.pv2_stacktest.20130903) initially for all MD exposures through September 2013. Some fields are still active (MD09,10,01,02) and some soon to be so (MD03,04), and all will have final exposures at the end of the survey (~February/March 2014) so all numbers will increase at least by a few. This has been finished for the survey observations through end of March 2014, however, there were a few more MD observations after that date for MD04,05,06 and need to be incorporated still (5/8/2014).

For PV2, all camera SMF and warp image products will remain online (i.e., not cleaned up) for loading into PSPS and for making the semi-final PV2 stack products.

Like GR0, will have summary for each field, but unlike GR0 will try and keep analysis and issues to other pages to reduce the length and load time for the summary page. Updates will be added from active fields and such on a MD by MD basis.

Status:

  • prior Sept. 2013 many issues being worked out for PV2 and MD (MD10.refstack.20130715)
  • 9/3 PV2 updates started for MD04 after M31 reprocessing finished -- MD04 not active field so PV2 temporary end date not defined by
  • 9/6 MD04 PV2 updates finished -- so can proceed rather quickly since only update processing
  • 10/17 PV2 updates started for MD03 -- choosing end of Sept. to be the temporary PV2 end date for update processing until end of survey Feb/March 2014
  • 10/20 MD03 PV2 updates finished
  • (lots of update processing when ever possible)
  • mid-Nov. essentially all MD fields finished -- still issues to resolve, but >90% done
  • 3/27/2014 remaining exposures processed as PV2
  • 4/2 PV2 final updates finished
  • 4/7 more MD exposures for MD04,05,06 to incorporate into the PV2 set.. MD04(8z,8y),MD05(16z),MD06(4z) and mostly marginal data

MD01

PV1 camera label -- data_group: mix of processing labels/data_groups, but all of PV1 type (cam_id>=434615)

label data_group
MD01.pv1.20130325 MD01.pv1.20130325
MD01.GR0.20121122 MD01.GR0.20121122
MD01.refstack.20120803 MD01.refstack.20120803
MD01.nightlystack MD01.<dateobs x--x>

There have been some test reprocessing that had to be accounted for -- czw.MDVDtest%..

PV2 camera (as well as chip, warp) label MD01.pv2.20131031, data_group left to what originally set as in order to be able to track backwards to the processing group.

Number totals through Sept. 2013: (will be more by end of survey to add)

  • not all exposures pass camera stage, FWHM>12 pixels or other quality issues
    | filter  | count(cam_id) | count(warp_id) |
    +---------+---------------+----------------+
    | g.00000 |           887 |            864 | 
    | i.00000 |           974 |            971 | 
    | r.00000 |           849 |            831 | 
    | y.00000 |          1018 |           1000 | 
    | z.00000 |          1264 |           1249 | 
    

PV2 warps will also be kept available (not cleaned up) for making deep stacks but also will be a accessible via the PSS/PSPS interface more quickly (release name MD01.PV2).

Loaded into release system as MD01.PV2 except for the camera quality faulted exposures.


MD02

PV1 camera label -- data_group: mix of processing labels/data_groups, but all of PV1 type (cam_id>=434615)

label data_group
MD02.pv1.20130325 MD02.pv1.20130325
MD02.GR0.20121210 MD02.GR0.20121210
MD02.refstack.20120927 MD02.refstack.20120927
MD02.nightlyscience MD02.<dateobs x--x>

Test reprocessing for MD02 properly sorted and none clearly needed to be avoided.

PV2 camera (as well as chip, warp) label MD02.pv2.20131101, data_group left to what originally set as in order to be able to track backwards to the processing group.

Number totals through Sept. 2013: (will be more by end of survey to add)

  • not all exposures pass camera stage, FWHM>12 pixels or other quality issues
    | filter  | count(cam_id) | count(warp_id) |
    +---------+---------------+----------------+
    | g.00000 |           590 |            573 | 
    | i.00000 |           746 |            744 | 
    | r.00000 |           609 |            602 | 
    | y.00000 |           847 |            822 | 
    | z.00000 |           911 |            901 | 
    

PV2 warps will also be kept available (not cleaned up) for making deep stacks but also will be a accessible via the PSS/PSPS interface more quickly (release name MD02.PV2).

Loaded into release system as MD02.PV2 except for the camera quality faulted exposures.


MD03

(from MD03.pv2_refstack.20131018#PV2updates)

PV1 camera label -- data_group: mix of processing labels/data_groups, but all of PV1 type (cam_id>=434615)

label data_group
MD03.pv1.20130326 MD03.pv1.20130326
MD03.refstack.20121101 MD03.refstack.20121101
MD03.GR0.20121212 MD03.GR0.20121212
MD03.nightlyscience MD03.<dateobs x--x>

Test reprocessing for MD03 properly sorted and none clearly needed to be avoided.

PV2 camera (as well as chip, warp) label MD03.pv2.20131018, data_group left to what originally set as in order to be able to track backwards to the processing group.

Number totals through Sept. 2013: (will be more by end of survey to add)

  • not all exposures pass camera stage, FWHM>12 pixels or other quality issues
    | filter  | count(cam_id) | count(warp_id) |
    +---------+---------------+----------------+
    | g.00000 |           733 |            720 | 
    | r.00000 |           709 |            707 | 
    | i.00000 |           871 |            869 | 
    | z.00000 |          1168 |           1151 | 
    | y.00000 |           903 |            898 | 
    

PV2 warps will also be kept available (not cleaned up) for making deep stacks but also will be a accessible via the PSS/PSPS interface more quickly (release name MD03.PV2).

Loaded into release system as MD03.PV2 except for the camera quality faulted exposures.


MD04

(from MD04.pv2_stacktest.20130903#MD04)

PV1 camera label -- data_group: mix of processing labels/data_groups, but all of PV1 type (cam_id>=434615)

label data_group
MD04.pv1.20130322 MD04.pv1.20130322
MD04.refstack.20121125 MD04.refstack.20121125
MD04.nightlyscience MD04.<obsdate 20121129--20130525>

There have been some test reprocessing that had to be avoided -- czw.MDVDtest%, czw.MDVD.MD04.%

PV2 camera (as well as chip, warp) label MD04.pv2.20130903, data_group left to what originally set as in order to be able to track backwards to the processing group.

With ipp047 data disk down, have found ~3% of exposures missing a related imfile (~half are the burn.tbl files that can be regenerated) and indicates serious need of fixing the replication of raw data. Also found some replicated but on a host (ipp064X) that no longer exists.. it is also possible some replicated products may be on the same host if push to the stsci nodes with 3 partitions..

Number totals through Sept. 2013: (will be more by end of survey)

  • not all exposures pass camera stage, FWHM>12 pixels or other quality issues
    | filter  | count(cam_id) | count(warp_id) |
    +---------+---------------+----------------+
    | g.00000 |           596 |            577 | 
    | r.00000 |           588 |            571 | 
    | i.00000 |           719 |            713 | 
    | z.00000 |           711 |            710 | 
    | y.00000 |           471 |            465 | 
    

PV2 warps will also be kept available (not cleaned up) for making deep stacks but also will be a accessible via the PSS/PSPS interface more quickly (release name MD04.PV2).

Loaded into release system as MD04.PV2 except for the camera quality faulted exposures.


MD05

PV1 camera label -- data_group: mix of processing labels/data_groups, but all of PV1 type (cam_id>=434615). MD05 had a large mix of GR0 reprocessing done for QUB.

label data_group
MD05.pv1.20130327 MD05.pv1.20130327
MD05.refstack.20121202 MD05.refstack.20121202
MD05.GR0.20121005 MD05.GR0.20121005
MD05.GR0.20121030 MD05.GR0.20121030
MD05.GR0.20121104 MD05.GR0.20121104
MD05.nightlyscience MD05.<dateobs x--x>

Test reprocessing for MD05 properly sorted and none clearly needed to be avoided.

PV2 camera (as well as chip, warp) label MD05.pv2.20131022, data_group left to what originally set as in order to be able to track backwards to the processing group.

Number totals through Sept. 2013: (will be more by end of survey to add)

  • not all exposures pass camera stage, FWHM>12 pixels or other quality issues
    | filter  | count(cam_id) | count(warp_id) |
    +---------+---------------+----------------+
    | g.00000 |           761 |            759 | 
    | i.00000 |           806 |            799 | 
    | r.00000 |           722 |            718 | 
    | y.00000 |           750 |            748 | 
    | z.00000 |           901 |            899 | 
    

PV2 warps will also be kept available (not cleaned up) for making deep stacks but also will be a accessible via the PSS/PSPS interface more quickly (release name MD05.PV2).

Loaded into release system as MD05.PV2 except for the camera quality faulted exposures.


MD06

PV1 camera label -- data_group: mix of processing labels/data_groups, but all of PV1 type (cam_id>=434615).

label data_group
MD06.pv1.20130326 MD06.pv1.20130326
MD06.refstack.20121221 MD06.refstack.20121221
MD06.nightlyscience MD06.<dateobs x--x>

Test reprocessing for MD06 properly sorted and none clearly needed to be avoided.

PV2 camera (as well as chip, warp) label MD06.pv2.20131025, data_group left to what originally set as in order to be able to track backwards to the processing group.

Number totals through Sept. 2013: (will be more by end of survey to add)

  • not all exposures pass camera stage, FWHM>12 pixels or other quality issues
    | filter  | count(cam_id) | count(warp_id) |
    +---------+---------------+----------------+
    | g.00000 |           737 |            730 | 
    | i.00000 |          1056 |           1051 | 
    | r.00000 |           743 |            735 | 
    | y.00000 |           662 |            658 | 
    | z.00000 |          1093 |           1085 | 
    

PV2 warps will also be kept available (not cleaned up) for making deep stacks but also will be a accessible via the PSS/PSPS interface more quickly (release name MD06.PV2).

Loaded into release system as MD06.PV2 except for the camera quality faulted exposures.


MD07

PV1 camera label -- data_group: mix of processing labels/data_groups, but all of PV1 type (cam_id>=434615).

label data_group
MD07.pv1.20130323 MD07.pv1.20130323
MD07.refstack.20130102 MD07.refstack.20130102
MD07.nightlyscience MD07.<dateobs x--x>

Test reprocessing for MD07 properly sorted and none clearly needed to be avoided except -- MD07.mehtest.20130307

PV2 camera (as well as chip, warp) label MD07.pv2.20131027, data_group left to what originally set as in order to be able to track backwards to the processing group.

Number totals through Sept. 2013: (will be more by end of survey to add)

  • not all exposures pass camera stage, FWHM>12 pixels or other quality issues
    | filter  | count(cam_id) | count(warp_id) |
    +---------+---------------+----------------+
    | g.00000 |           758 |            743 | 
    | i.00000 |          1012 |           1009 | 
    | r.00000 |           732 |            724 | 
    | y.00000 |           869 |            854 | 
    | z.00000 |          1082 |           1074 | 
    

PV2 warps will also be kept available (not cleaned up) for making deep stacks but also will be a accessible via the PSS/PSPS interface more quickly (release name MD07.PV2).

Loaded into release system as MD07.PV2 except for the camera quality faulted exposures.


MD08

PV1 camera label -- data_group: mix of processing labels/data_groups, but all of PV1 type (cam_id>=434615).

label data_group
MD08.pv1.20130403 MD08.pv1.20130403
MD08.refstack.20130401 MD08.refstack.20130401
MD08.nightlyscience MD08.<dateobs x--x>

Test reprocessing for MD08 properly sorted and none clearly needed to be avoided except -- czw.MOPStest

PV2 camera (as well as chip, warp) label MD08.pv2.20131028, data_group left to what originally set as in order to be able to track backwards to the processing group.

Number totals through Sept. 2013: (will be more by end of survey to add)

  • not all exposures pass camera stage, FWHM>12 pixels or other quality issues
    | filter  | count(cam_id) | count(warp_id) |
    +---------+---------------+----------------+
    | g.00000 |           723 |            713 | 
    | i.00000 |           901 |            892 | 
    | r.00000 |           732 |            722 | 
    | y.00000 |          1132 |           1097 | 
    | z.00000 |          1018 |           1008 | 
    

PV2 warps will also be kept available (not cleaned up) for making deep stacks but also will be a accessible via the PSS/PSPS interface more quickly (release name MD08.PV2).

Loaded into release system as MD08.PV2 except for the camera quality faulted exposures.


MD09

PV1 camera label -- data_group: mix of processing labels/data_groups, but all of PV1 type (cam_id>=434615).

label data_group
MD09.GR0 MD09.GR0
MD09.refstack MD09.refstack.20130613
MD09.nightlyscience MD09.<dateobs x--x>

Test reprocessing for MD09 properly sorted and none clearly needed to be avoided except -- czw.MOPStest, MD09_gr0_mehtest

PV2 camera (as well as chip, warp) label MD09.pv2.20131030, data_group left to what originally set as in order to be able to track backwards to the processing group.

Number totals through Sept. 2013: (will be more by end of survey to add)

  • not all exposures pass camera stage, FWHM>12 pixels or other quality issues
    | filter  | count(cam_id) | count(warp_id) |
    +---------+---------------+----------------+
    | g.00000 |           858 |            852 | 
    | i.00000 |           923 |            908 | 
    | r.00000 |           844 |            840 | 
    | y.00000 |           911 |            905 | 
    | z.00000 |          1036 |           1033 |
    

PV2 warps will also be kept available (not cleaned up) for making deep stacks but also will be a accessible via the PSS/PSPS interface more quickly (release name MD09.PV2).

Loaded into release system as MD09.PV2 except for the camera quality faulted exposures.


MD10

PV1 camera label -- data_group: mix of processing labels/data_groups, but all of PV1 type (cam_id>=434615).

label data_group
MD10.pv1.20130324 MD10.pv1.20130324
MD10.refstack.20120705 MD10.refstack.20120705
MD10.nightlyscience MD10.<dateobs x--x>

Test reprocessing for MD10 properly sorted and none clearly needed to be avoided except -- czw.MOPStest, other?

PV2 camera (as well as chip, warp) label MD10.pv2.20131103, data_group left to what originally set as in order to be able to track backwards to the processing group. Previous run label MD10.pv2.20130828 set had label changed to main label MD10.pv2.20131103.

Number totals through Sept. 2013: (will be more by end of survey to add)

  • not all exposures pass camera stage, FWHM>12 pixels or other quality issues
    | filter  | count(cam_id) | count(warp_id) |
    +---------+---------------+----------------+
    | g.00000 |           888 |            880 | 
    | i.00000 |           924 |            914 | 
    | r.00000 |           866 |            858 | 
    | y.00000 |           849 |            839 | 
    | z.00000 |          1056 |           1040 | 
    

PV2 warps will also be kept available (not cleaned up) for making deep stacks but also will be a accessible via the PSS/PSPS interface more quickly (release name MD10.PV2).

Loaded into release system as MD10.PV2 except for the camera quality faulted exposures.