https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/OBSPROC-17 PFS observation processing/procedure <p>Currently, flux columns are assuming grizyj, but the datamodel can accommodate more flexible case. I would like to implement a feature to handle fluxes in arbitrary passbands in targetDB.</p> OBSPROC-17

Organize flux columns in the target table of targetDB

Task Normal Open Unresolved monodera monodera targetDB Thu, 16 Dec 2021 01:56:10 +0000 Thu, 5 Oct 2023 21:01:30 +0000 ets_target_database 0 1 <p>PostgreSQL supports ARRAY type, so I will use this.</p> <p> </p> <p><a href="https://docs.sqlalchemy.org/en/14/dialects/postgresql.html#sqlalchemy.dialects.postgresql.ARRAY" class="external-link" rel="nofollow">https://docs.sqlalchemy.org/en/14/dialects/postgresql.html#sqlalchemy.dialects.postgresql.ARRAY</a></p> <p>For flux columns in the targetDB, do we need the three kind of flux defined in the datamodel, (1) fiber_flux, (2) psf_flux, and (3) total_flux?</p> <p> </p> <p>(1) Fiber flux need a seeing correction, but at Phase 2 and during the designing process, seeing cannot be known.</p> <p>(2) PSF flux also need a PSF shape for extended source.</p> <p>(3) Total flux can be submitted at Phase 2, but it may not be useful for objects which extends much larger than the fiber diameter. In this case, fiber flux would be more appropriate.</p> <p> </p> <p>I can make these three, but if you have any suggestions, please let me know.</p> <p> </p> <p>Related question: do we also need to make magnitude columns or just fluxes in nJy are fine?</p> <p>Just a note:</p> <p> </p> <p>To host an arbitrary photometric data points, there are ARRAY and JSON/JSONB types available in PostgreSQL. At this point, which type should be used in what kind of photometry depends on the demand from the data processing. </p> <p> </p> <p>There could be 4 possibilities at this moment:</p> <p>(1) just list each filter as a column, e.g., total_flux_g_hsc, total_flux_g_gaia, etc.</p> <p>(2) use ARRAY type with a list of filters as another column.</p> <p>(3) use JSON/JSONB type with filter info in each json entry.</p> <p>(4) no photometry info in the targetdb (i.e., not be used in the data processing).</p> <p> </p> Relates OBSPROC-55 Development Epic Link OBSPROC-1 Rank 0|zzsssf: