...
TARGPROG is an optional column, to be filled out at the discretion of the catalogue creator.
TARGNAME and TARGID
...
TARGNAME
...
This parameter is used to group IFU observations of the same target, in cases where stacks are required. This helps the Core Processing System (CPS) responsible for obtaining the data, to identify cases where the same astrophysical target is observed but the OBs executed were not related (via for example the "chained" directive).
An example would be LIFU observations of the core of M33. If a user requires 3 OBs, each one with different dither positionsdithering, then the CPS could not ordinarily stack these data, because they do not share the same Central CNAME Name (or CNAME, which is the WEAVE object name from coordinates). In the input FITS catalogue, these observations are represented by 5,427 rows: 603 fibres, dithered 3 times for 3 OBs. Each of these rows must be tied together by a common TARGNAME, e.g. "M33 bulge". This indicates to the CPS that these observations should be evaluated for stacking.
...
It is not always true that IFU observations with common TARGNAME will be stacked. Only common TARGNAMEs with sufficient overlap will be stacked by the CPS. However, if Contributed Data Products CPS data products exist to create larger mosaics from these data, then they should use the common TARGNAME to group L1 products.
...
IFU workflow package: https://ingbitbucket.ing.iac.es/projects/WVSWG/repos/ifu/browse/workflow
Configure software (used by the IFU workflow): https://weave-project.atlassian.net/wiki/spaces/WEAVE/pages/126615564/configure+for+Open+Time+users