search

LSSTDESC / DC2-production

Configuration, production, validation specifications and tools for the DC2 Data Set.
BSD 3-Clause "New" or "Revised" License
11 stars 7 forks source link

Generate 2.1i DR1a DPDD-like data products (e.g., object catalog) #347

Closed yymao closed 5 years ago

yymao commented 5 years ago

Now that the 6-month processing of Run2.1i is complete, we need to generate 2.1i DPDD-like data products (e.g., object catalog) for the analysis teams.

Just when I am writing this, @heather999 informed me that @johannct has already run merge_tract_cat.py on IN2P3. If that's indeed the case, then it's just a matter of copying those files to NERSC and creating an entry in GCRCatalogs. (In this case, we can probably get this done fairly soon, and the esitimate that I gave @rmandelb would be wrong.)

@heather999 will copy the files to NERSC and I'll take a look.

The other question is whether we need to create DPDD-like catalogs for source and forced source, @wmwv?

johannct commented 5 years ago

yes it has been run, see under /sps/lsst/dataproducts/desc/DC2/Run2.1i/w_2019_19-v1/dpdd/calexp-v1:coadd-v1/object_table_summary. @airnandez or @heather999 can you deal with the transfer? EDIT: HOLD ON, THERE IS A SERIOUS ISSUE WITH THIS PSEUDO 6-MTH PROCESSING, WHICH IS ACTUALLY MUCH SHALLOWER THAN EXPECTED. THIS IS UNDERSTOOD, BUT NEEDS ACTION

johannct commented 5 years ago

For the forced sources, it is in the pipeline as well, but has not been run, because I face again the problem that we cannot run cModel photometry here. I will deal with that after I am done with checking metacal results

yymao commented 5 years ago

Sounds great. Thanks for the update @johannct!

yymao commented 5 years ago

I've made this issue narrower so that it's about DR1a only. For DR1a, we plan to provide only the object catalog (among all DPDD-like products), which is done and released.