Issue RCAL-1405 was created on JIRA by Mairan Teodoro:
There is one data release product catalog product that we do not yet create but which it would be good to provide examples for database design purposes. These are the "forced subset" catalogs. They are produced like so:
https://github.com/spacetelescope/romancal/blob/main/romancal/scripts/make_regtestdata.sh#L223
We need to take the deep multiband segmentation map on each skycell and force it onto each pass coadd to produce a bunch of file names like:
r00001_dr1_s01001_270p65x70y49_f158_cat.asdf
These are the same file names as the L3 prompt file names that come out of the coaddition process. Let's just go ahead and overwrite those for now. A mildly better solution would be to skip the source catalog step on the during the roman_mos processing for data releases, so that the only catalogs that come out are the multiband ones and these new forced photometry ones.
Associated issue: spacetelescope/roman_simulate_dr#13
Issue RCAL-1405 was created on JIRA by Mairan Teodoro:
There is one data release product catalog product that we do not yet create but which it would be good to provide examples for database design purposes. These are the "forced subset" catalogs. They are produced like so:
https://github.com/spacetelescope/romancal/blob/main/romancal/scripts/make_regtestdata.sh#L223
We need to take the deep multiband segmentation map on each skycell and force it onto each pass coadd to produce a bunch of file names like:
r00001_dr1_s01001_270p65x70y49_f158_cat.asdf
These are the same file names as the L3 prompt file names that come out of the coaddition process. Let's just go ahead and overwrite those for now. A mildly better solution would be to skip the source catalog step on the during the roman_mos processing for data releases, so that the only catalogs that come out are the multiband ones and these new forced photometry ones.
Associated issue: spacetelescope/roman_simulate_dr#13