Home | Overview | Browser | Access | Login | Cookbook 
   VSA logo

Glossary of VSA attributes

This Glossary alphabetically lists all attributes used in the VSAv20240329 database(s) held in the VSA. If you would like to have more information about the schema tables please use the VSAv20240329 Schema Browser (other Browser versions).
A B C D E F G H I J K L M
N O P Q R S T U V W X Y Z

O

NameSchema TableDatabaseDescriptionTypeLengthUnitDefault ValueUnified Content Descriptor
o1Eta sharksTilePawPrints SHARKSv20210222 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta sharksTilePawPrints SHARKSv20210421 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta sharksTilePawTDOnly SHARKSv20210222 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta sharksTilePawTDOnly SHARKSv20210421 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta ultravistaTilePawPrints ULTRAVISTADR4 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta ultravistaTilePawTDOnly ULTRAVISTADR4 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vhsTilePawPrints VHSDR1 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vhsTilePawPrints VHSDR2 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vhsTilePawPrints VHSDR3 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vhsTilePawPrints VHSDR4 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vhsTilePawPrints VHSDR5 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vhsTilePawPrints VHSDR6 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vhsTilePawPrints VHSv20120926 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vhsTilePawPrints VHSv20130417 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vhsTilePawPrints VHSv20140409 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vhsTilePawPrints VHSv20150108 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vhsTilePawPrints VHSv20160114 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vhsTilePawPrints VHSv20160507 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vhsTilePawPrints VHSv20170630 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vhsTilePawPrints VHSv20180419 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vhsTilePawPrints VHSv20201209 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vhsTilePawPrints VHSv20231101 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vhsTilePawTDOnly VHSDR1 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vhsTilePawTDOnly VHSDR2 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vhsTilePawTDOnly VHSDR3 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vhsTilePawTDOnly VHSDR4 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vhsTilePawTDOnly VHSDR5 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vhsTilePawTDOnly VHSDR6 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vhsTilePawTDOnly VHSv20120926 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vhsTilePawTDOnly VHSv20130417 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vhsTilePawTDOnly VHSv20140409 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vhsTilePawTDOnly VHSv20150108 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vhsTilePawTDOnly VHSv20160114 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vhsTilePawTDOnly VHSv20160507 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vhsTilePawTDOnly VHSv20170630 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vhsTilePawTDOnly VHSv20180419 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vhsTilePawTDOnly VHSv20201209 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vhsTilePawTDOnly VHSv20231101 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta videoTilePawPrints VIDEODR2 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta videoTilePawPrints VIDEODR3 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta videoTilePawPrints VIDEODR4 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta videoTilePawPrints VIDEODR5 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta videoTilePawPrints VIDEOv20111208 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta videoTilePawTDOnly VIDEODR2 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta videoTilePawTDOnly VIDEODR3 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta videoTilePawTDOnly VIDEODR4 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta videoTilePawTDOnly VIDEODR5 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta videoTilePawTDOnly VIDEOv20111208 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vikingTilePawPrints VIKINGDR2 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vikingTilePawPrints VIKINGDR3 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vikingTilePawPrints VIKINGDR4 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vikingTilePawPrints VIKINGv20110714 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vikingTilePawPrints VIKINGv20111019 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vikingTilePawPrints VIKINGv20130417 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vikingTilePawPrints VIKINGv20140402 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vikingTilePawPrints VIKINGv20150421 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vikingTilePawPrints VIKINGv20151230 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vikingTilePawPrints VIKINGv20160406 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vikingTilePawPrints VIKINGv20161202 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vikingTilePawPrints VIKINGv20170715 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vikingTilePawTDOnly VIKINGDR2 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vikingTilePawTDOnly VIKINGDR3 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vikingTilePawTDOnly VIKINGDR4 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vikingTilePawTDOnly VIKINGv20111019 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vikingTilePawTDOnly VIKINGv20130417 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vikingTilePawTDOnly VIKINGv20140402 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vikingTilePawTDOnly VIKINGv20150421 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vikingTilePawTDOnly VIKINGv20151230 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vikingTilePawTDOnly VIKINGv20160406 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vikingTilePawTDOnly VIKINGv20161202 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vikingTilePawTDOnly VIKINGv20170715 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawPrints VMCDR1 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCDR2 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCDR3 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCDR4 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCDR5 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20110816 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20110909 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20120126 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20121128 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20130304 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20130805 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20140428 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20140903 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20150309 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20151218 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20160311 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20160822 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20170109 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20170411 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20171101 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20180702 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20181120 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20191212 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20210708 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20230816 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawPrints VMCv20240226 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcTilePawTDOnly VMCDR1 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCDR2 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCDR3 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCDR4 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCDR5 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20110816 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20110909 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20120126 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20121128 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20130304 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20130805 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20140428 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20140903 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20150309 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20151218 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20160311 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20160822 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20170109 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20170411 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20171101 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20180702 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20181120 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20191212 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20210708 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20230816 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcTilePawTDOnly VMCv20240226 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vmcdeepTilePawPrints VMCDEEPv20230713 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vmcdeepTilePawTDOnly VMCDEEPv20230713 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vvvTilePawPrints VVVDR1 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vvvTilePawPrints VVVDR2 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vvvTilePawPrints VVVDR5 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vvvTilePawPrints VVVv20110718 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Eta vvvTilePawTDOnly VVVDR1 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vvvTilePawTDOnly VVVDR2 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1Eta vvvTilePawTDOnly VVVDR5 Offset of O1 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o1ExtNum sharksTilePawPrints SHARKSv20210421 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum sharksTilePawPrints, sharksTilePawTDOnly SHARKSv20210222 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum ultravistaTilePawPrints, ultravistaTilePawTDOnly ULTRAVISTADR4 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vhsTilePawPrints VHSDR2 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vhsTilePawPrints VHSDR3 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vhsTilePawPrints VHSDR4 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vhsTilePawPrints VHSDR5 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vhsTilePawPrints VHSDR6 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vhsTilePawPrints VHSv20120926 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vhsTilePawPrints VHSv20130417 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vhsTilePawPrints VHSv20140409 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vhsTilePawPrints VHSv20150108 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vhsTilePawPrints VHSv20160114 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vhsTilePawPrints VHSv20160507 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vhsTilePawPrints VHSv20170630 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vhsTilePawPrints VHSv20180419 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vhsTilePawPrints VHSv20201209 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vhsTilePawPrints VHSv20231101 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vhsTilePawPrints, vhsTilePawTDOnly VHSDR1 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum videoTilePawPrints VIDEODR3 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum videoTilePawPrints VIDEODR4 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum videoTilePawPrints VIDEODR5 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum videoTilePawPrints VIDEOv20111208 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum videoTilePawPrints, videoTilePawTDOnly VIDEODR2 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vikingTilePawPrints VIKINGDR3 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vikingTilePawPrints VIKINGDR4 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vikingTilePawPrints VIKINGv20110714 the extension number of the O1 detection int 4   -99999999 meta.id
o1ExtNum vikingTilePawPrints VIKINGv20111019 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vikingTilePawPrints VIKINGv20130417 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vikingTilePawPrints VIKINGv20140402 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vikingTilePawPrints VIKINGv20150421 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vikingTilePawPrints VIKINGv20151230 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vikingTilePawPrints VIKINGv20160406 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vikingTilePawPrints VIKINGv20161202 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vikingTilePawPrints VIKINGv20170715 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vikingTilePawPrints, vikingTilePawTDOnly VIKINGDR2 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCDR2 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCDR3 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCDR4 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCDR5 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20110816 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20110909 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20120126 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20121128 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20130304 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20130805 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20140428 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20140903 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20150309 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20151218 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20160311 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20160822 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20170109 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20170411 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20171101 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20180702 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20181120 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20191212 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20210708 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20230816 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints VMCv20240226 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcTilePawPrints, vmcTilePawTDOnly VMCDR1 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vmcdeepTilePawPrints, vmcdeepTilePawTDOnly VMCDEEPv20230713 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vvvTilePawPrints VVVDR2 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vvvTilePawPrints VVVDR5 the extension number of the O1 detection tinyint 1   2 meta.id
o1ExtNum vvvTilePawPrints VVVv20110718 the extension number of the O1 detection int 4   -99999999 meta.id
o1ExtNum vvvTilePawPrints, vvvTilePawTDOnly VVVDR1 the extension number of the O1 detection tinyint 1   2 meta.id
o1mfID sharksTileSet SHARKSv20210222 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID sharksTileSet SHARKSv20210421 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID ultravistaTileSet ULTRAVISTADR4 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vhsTileSet VHSDR1 the UID of the relevant offset O1 multiframe bigint 8     obs.field
o1mfID vhsTileSet VHSDR2 the UID of the relevant offset O1 multiframe bigint 8     obs.field
o1mfID vhsTileSet VHSDR3 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vhsTileSet VHSDR4 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vhsTileSet VHSDR5 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vhsTileSet VHSDR6 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vhsTileSet VHSv20120926 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vhsTileSet VHSv20130417 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vhsTileSet VHSv20140409 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vhsTileSet VHSv20150108 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vhsTileSet VHSv20160114 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vhsTileSet VHSv20160507 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vhsTileSet VHSv20170630 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vhsTileSet VHSv20180419 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vhsTileSet VHSv20201209 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vhsTileSet VHSv20231101 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID videoTileSet VIDEODR2 the UID of the relevant offset O1 multiframe bigint 8     obs.field
o1mfID videoTileSet VIDEODR3 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID videoTileSet VIDEODR4 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID videoTileSet VIDEODR5 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID videoTileSet VIDEOv20111208 the UID of the relevant offset O1 multiframe bigint 8     obs.field
o1mfID vikingTileSet VIKINGDR2 the UID of the relevant offset O1 multiframe bigint 8     obs.field
o1mfID vikingTileSet VIKINGDR3 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vikingTileSet VIKINGDR4 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vikingTileSet VIKINGv20110714 the UID of the relevant offset O1 multiframe bigint 8     obs.field
o1mfID vikingTileSet VIKINGv20111019 the UID of the relevant offset O1 multiframe bigint 8     obs.field
o1mfID vikingTileSet VIKINGv20130417 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vikingTileSet VIKINGv20140402 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vikingTileSet VIKINGv20150421 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vikingTileSet VIKINGv20151230 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vikingTileSet VIKINGv20160406 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vikingTileSet VIKINGv20161202 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vikingTileSet VIKINGv20170715 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCDR1 the UID of the relevant offset O1 multiframe bigint 8     obs.field
o1mfID vmcTileSet VMCDR2 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCDR3 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCDR4 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCDR5 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCv20110816 the UID of the relevant offset O1 multiframe bigint 8     obs.field
o1mfID vmcTileSet VMCv20110909 the UID of the relevant offset O1 multiframe bigint 8     obs.field
o1mfID vmcTileSet VMCv20120126 the UID of the relevant offset O1 multiframe bigint 8     obs.field
o1mfID vmcTileSet VMCv20121128 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCv20130304 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCv20130805 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCv20140428 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCv20140903 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCv20150309 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCv20151218 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCv20160311 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCv20160822 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCv20170109 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCv20170411 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCv20171101 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCv20180702 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCv20181120 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCv20191212 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCv20210708 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCv20230816 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcTileSet VMCv20240226 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vmcdeepTileSet VMCDEEPv20230713 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vvvTileSet VVVDR1 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vvvTileSet VVVDR2 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vvvTileSet VVVDR5 the UID of the relevant offset O1 multiframe bigint 8     meta.id;obs.field
o1mfID vvvTileSet VVVv20110718 the UID of the relevant offset O1 multiframe bigint 8     obs.field
o1SeqNum sharksTilePawPrints SHARKSv20210421 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum sharksTilePawPrints, sharksTilePawTDOnly SHARKSv20210222 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum ultravistaTilePawPrints, ultravistaTilePawTDOnly ULTRAVISTADR4 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vhsTilePawPrints VHSDR2 the running number of the O1 detection int 4   -99999999 meta.id
o1SeqNum vhsTilePawPrints VHSDR3 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vhsTilePawPrints VHSDR4 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vhsTilePawPrints VHSDR5 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vhsTilePawPrints VHSDR6 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vhsTilePawPrints VHSv20120926 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vhsTilePawPrints VHSv20130417 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vhsTilePawPrints VHSv20140409 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vhsTilePawPrints VHSv20150108 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vhsTilePawPrints VHSv20160114 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vhsTilePawPrints VHSv20160507 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vhsTilePawPrints VHSv20170630 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vhsTilePawPrints VHSv20180419 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vhsTilePawPrints VHSv20201209 the running number of the O1 detection int 4   -99999999 meta.id
o1SeqNum vhsTilePawPrints VHSv20231101 the running number of the O1 detection int 4   -99999999 meta.id
o1SeqNum vhsTilePawPrints, vhsTilePawTDOnly VHSDR1 the running number of the O1 detection int 4   -99999999 meta.id
o1SeqNum videoTilePawPrints VIDEODR3 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum videoTilePawPrints VIDEODR4 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum videoTilePawPrints VIDEODR5 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum videoTilePawPrints VIDEOv20111208 the running number of the O1 detection int 4   -99999999 meta.id
o1SeqNum videoTilePawPrints, videoTilePawTDOnly VIDEODR2 the running number of the O1 detection int 4   -99999999 meta.id
o1SeqNum vikingTilePawPrints VIKINGDR3 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vikingTilePawPrints VIKINGDR4 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vikingTilePawPrints VIKINGv20110714 the running number of the O1 detection int 4   -99999999 meta.id
o1SeqNum vikingTilePawPrints VIKINGv20111019 the running number of the O1 detection int 4   -99999999 meta.id
o1SeqNum vikingTilePawPrints VIKINGv20130417 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vikingTilePawPrints VIKINGv20140402 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vikingTilePawPrints VIKINGv20150421 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vikingTilePawPrints VIKINGv20151230 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vikingTilePawPrints VIKINGv20160406 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vikingTilePawPrints VIKINGv20161202 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vikingTilePawPrints VIKINGv20170715 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vikingTilePawPrints, vikingTilePawTDOnly VIKINGDR2 the running number of the O1 detection int 4   -99999999 meta.id
o1SeqNum vmcTilePawPrints VMCDR2 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vmcTilePawPrints VMCDR3 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vmcTilePawPrints VMCDR4 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vmcTilePawPrints VMCDR5 the running number of the O1 detection int 4   -99999999 meta.id
o1SeqNum vmcTilePawPrints VMCv20110816 the running number of the O1 detection int 4   -99999999 meta.id
o1SeqNum vmcTilePawPrints VMCv20110909 the running number of the O1 detection int 4   -99999999 meta.id
o1SeqNum vmcTilePawPrints VMCv20120126 the running number of the O1 detection int 4   -99999999 meta.id
o1SeqNum vmcTilePawPrints VMCv20121128 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vmcTilePawPrints VMCv20130304 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vmcTilePawPrints VMCv20130805 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vmcTilePawPrints VMCv20140428 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vmcTilePawPrints VMCv20140903 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vmcTilePawPrints VMCv20150309 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vmcTilePawPrints VMCv20151218 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vmcTilePawPrints VMCv20160311 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vmcTilePawPrints VMCv20160822 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vmcTilePawPrints VMCv20170109 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vmcTilePawPrints VMCv20170411 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vmcTilePawPrints VMCv20171101 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vmcTilePawPrints VMCv20180702 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vmcTilePawPrints VMCv20181120 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vmcTilePawPrints VMCv20191212 the running number of the O1 detection int 4   -99999999 meta.id
o1SeqNum vmcTilePawPrints VMCv20210708 the running number of the O1 detection int 4   -99999999 meta.id
o1SeqNum vmcTilePawPrints VMCv20230816 the running number of the O1 detection int 4   -99999999 meta.id
o1SeqNum vmcTilePawPrints VMCv20240226 the running number of the O1 detection int 4   -99999999 meta.id
o1SeqNum vmcTilePawPrints, vmcTilePawTDOnly VMCDR1 the running number of the O1 detection int 4   -99999999 meta.id
o1SeqNum vmcdeepTilePawPrints, vmcdeepTilePawTDOnly VMCDEEPv20230713 the running number of the O1 detection int 4   -99999999 meta.id
o1SeqNum vvvTilePawPrints VVVDR2 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vvvTilePawPrints VVVDR5 the running number of the O1 detection int 4   -99999999 meta.number
o1SeqNum vvvTilePawPrints VVVv20110718 the running number of the O1 detection int 4   -99999999 meta.id
o1SeqNum vvvTilePawPrints, vvvTilePawTDOnly VVVDR1 the running number of the O1 detection int 4   -99999999 meta.number
o1Xi sharksTilePawPrints SHARKSv20210222 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi sharksTilePawPrints SHARKSv20210421 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi sharksTilePawTDOnly SHARKSv20210222 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi sharksTilePawTDOnly SHARKSv20210421 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi ultravistaTilePawPrints ULTRAVISTADR4 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi ultravistaTilePawTDOnly ULTRAVISTADR4 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vhsTilePawPrints VHSDR1 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vhsTilePawPrints VHSDR2 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vhsTilePawPrints VHSDR3 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vhsTilePawPrints VHSDR4 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vhsTilePawPrints VHSDR5 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vhsTilePawPrints VHSDR6 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vhsTilePawPrints VHSv20120926 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vhsTilePawPrints VHSv20130417 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vhsTilePawPrints VHSv20140409 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vhsTilePawPrints VHSv20150108 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vhsTilePawPrints VHSv20160114 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vhsTilePawPrints VHSv20160507 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vhsTilePawPrints VHSv20170630 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vhsTilePawPrints VHSv20180419 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vhsTilePawPrints VHSv20201209 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vhsTilePawPrints VHSv20231101 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vhsTilePawTDOnly VHSDR1 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vhsTilePawTDOnly VHSDR2 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vhsTilePawTDOnly VHSDR3 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vhsTilePawTDOnly VHSDR4 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vhsTilePawTDOnly VHSDR5 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vhsTilePawTDOnly VHSDR6 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vhsTilePawTDOnly VHSv20120926 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vhsTilePawTDOnly VHSv20130417 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vhsTilePawTDOnly VHSv20140409 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vhsTilePawTDOnly VHSv20150108 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vhsTilePawTDOnly VHSv20160114 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vhsTilePawTDOnly VHSv20160507 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vhsTilePawTDOnly VHSv20170630 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vhsTilePawTDOnly VHSv20180419 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vhsTilePawTDOnly VHSv20201209 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vhsTilePawTDOnly VHSv20231101 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi videoTilePawPrints VIDEODR2 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi videoTilePawPrints VIDEODR3 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi videoTilePawPrints VIDEODR4 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi videoTilePawPrints VIDEODR5 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi videoTilePawPrints VIDEOv20111208 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi videoTilePawTDOnly VIDEODR2 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi videoTilePawTDOnly VIDEODR3 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi videoTilePawTDOnly VIDEODR4 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi videoTilePawTDOnly VIDEODR5 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi videoTilePawTDOnly VIDEOv20111208 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vikingTilePawPrints VIKINGDR2 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vikingTilePawPrints VIKINGDR3 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vikingTilePawPrints VIKINGDR4 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vikingTilePawPrints VIKINGv20110714 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vikingTilePawPrints VIKINGv20111019 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vikingTilePawPrints VIKINGv20130417 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vikingTilePawPrints VIKINGv20140402 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vikingTilePawPrints VIKINGv20150421 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vikingTilePawPrints VIKINGv20151230 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vikingTilePawPrints VIKINGv20160406 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vikingTilePawPrints VIKINGv20161202 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vikingTilePawPrints VIKINGv20170715 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vikingTilePawTDOnly VIKINGDR2 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vikingTilePawTDOnly VIKINGDR3 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vikingTilePawTDOnly VIKINGDR4 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vikingTilePawTDOnly VIKINGv20111019 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vikingTilePawTDOnly VIKINGv20130417 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vikingTilePawTDOnly VIKINGv20140402 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vikingTilePawTDOnly VIKINGv20150421 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vikingTilePawTDOnly VIKINGv20151230 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vikingTilePawTDOnly VIKINGv20160406 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vikingTilePawTDOnly VIKINGv20161202 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vikingTilePawTDOnly VIKINGv20170715 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawPrints VMCDR1 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCDR2 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCDR3 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCDR4 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCDR5 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20110816 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20110909 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20120126 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20121128 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20130304 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20130805 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20140428 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20140903 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20150309 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20151218 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20160311 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20160822 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20170109 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20170411 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20171101 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20180702 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20181120 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20191212 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20210708 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20230816 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawPrints VMCv20240226 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcTilePawTDOnly VMCDR1 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCDR2 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCDR3 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCDR4 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCDR5 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20110816 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20110909 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20120126 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20121128 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20130304 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20130805 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20140428 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20140903 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20150309 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20151218 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20160311 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20160822 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20170109 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20170411 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20171101 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20180702 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20181120 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20191212 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20210708 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20230816 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcTilePawTDOnly VMCv20240226 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vmcdeepTilePawPrints VMCDEEPv20230713 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vmcdeepTilePawTDOnly VMCDEEPv20230713 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vvvTilePawPrints VVVDR1 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vvvTilePawPrints VVVDR2 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vvvTilePawPrints VVVDR5 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vvvTilePawPrints VVVv20110718 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o1Xi vvvTilePawTDOnly VVVDR1 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vvvTilePawTDOnly VVVDR2 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o1Xi vvvTilePawTDOnly VVVDR5 Offset of O1 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Eta sharksTilePawPrints SHARKSv20210222 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta sharksTilePawPrints SHARKSv20210421 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta sharksTilePawTDOnly SHARKSv20210222 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta sharksTilePawTDOnly SHARKSv20210421 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta ultravistaTilePawPrints ULTRAVISTADR4 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta ultravistaTilePawTDOnly ULTRAVISTADR4 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vhsTilePawPrints VHSDR1 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vhsTilePawPrints VHSDR2 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vhsTilePawPrints VHSDR3 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vhsTilePawPrints VHSDR4 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vhsTilePawPrints VHSDR5 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vhsTilePawPrints VHSDR6 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vhsTilePawPrints VHSv20120926 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vhsTilePawPrints VHSv20130417 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vhsTilePawPrints VHSv20140409 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vhsTilePawPrints VHSv20150108 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vhsTilePawPrints VHSv20160114 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vhsTilePawPrints VHSv20160507 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vhsTilePawPrints VHSv20170630 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vhsTilePawPrints VHSv20180419 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vhsTilePawPrints VHSv20201209 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vhsTilePawPrints VHSv20231101 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vhsTilePawTDOnly VHSDR1 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vhsTilePawTDOnly VHSDR2 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vhsTilePawTDOnly VHSDR3 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vhsTilePawTDOnly VHSDR4 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vhsTilePawTDOnly VHSDR5 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vhsTilePawTDOnly VHSDR6 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vhsTilePawTDOnly VHSv20120926 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vhsTilePawTDOnly VHSv20130417 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vhsTilePawTDOnly VHSv20140409 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vhsTilePawTDOnly VHSv20150108 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vhsTilePawTDOnly VHSv20160114 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vhsTilePawTDOnly VHSv20160507 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vhsTilePawTDOnly VHSv20170630 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vhsTilePawTDOnly VHSv20180419 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vhsTilePawTDOnly VHSv20201209 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vhsTilePawTDOnly VHSv20231101 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta videoTilePawPrints VIDEODR2 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta videoTilePawPrints VIDEODR3 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta videoTilePawPrints VIDEODR4 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta videoTilePawPrints VIDEODR5 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta videoTilePawPrints VIDEOv20111208 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta videoTilePawTDOnly VIDEODR2 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta videoTilePawTDOnly VIDEODR3 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta videoTilePawTDOnly VIDEODR4 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta videoTilePawTDOnly VIDEODR5 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta videoTilePawTDOnly VIDEOv20111208 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vikingTilePawPrints VIKINGDR2 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vikingTilePawPrints VIKINGDR3 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vikingTilePawPrints VIKINGDR4 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vikingTilePawPrints VIKINGv20110714 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vikingTilePawPrints VIKINGv20111019 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vikingTilePawPrints VIKINGv20130417 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vikingTilePawPrints VIKINGv20140402 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vikingTilePawPrints VIKINGv20150421 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vikingTilePawPrints VIKINGv20151230 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vikingTilePawPrints VIKINGv20160406 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vikingTilePawPrints VIKINGv20161202 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vikingTilePawPrints VIKINGv20170715 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vikingTilePawTDOnly VIKINGDR2 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vikingTilePawTDOnly VIKINGDR3 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vikingTilePawTDOnly VIKINGDR4 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vikingTilePawTDOnly VIKINGv20111019 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vikingTilePawTDOnly VIKINGv20130417 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vikingTilePawTDOnly VIKINGv20140402 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vikingTilePawTDOnly VIKINGv20150421 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vikingTilePawTDOnly VIKINGv20151230 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vikingTilePawTDOnly VIKINGv20160406 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vikingTilePawTDOnly VIKINGv20161202 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vikingTilePawTDOnly VIKINGv20170715 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawPrints VMCDR1 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCDR2 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCDR3 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCDR4 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCDR5 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20110816 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20110909 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20120126 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20121128 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20130304 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20130805 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20140428 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20140903 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20150309 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20151218 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20160311 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20160822 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20170109 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20170411 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20171101 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20180702 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20181120 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20191212 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20210708 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20230816 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawPrints VMCv20240226 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcTilePawTDOnly VMCDR1 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCDR2 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCDR3 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCDR4 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCDR5 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20110816 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20110909 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20120126 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20121128 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20130304 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20130805 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20140428 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20140903 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20150309 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20151218 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20160311 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20160822 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20170109 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20170411 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20171101 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20180702 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20181120 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20191212 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20210708 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20230816 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcTilePawTDOnly VMCv20240226 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vmcdeepTilePawPrints VMCDEEPv20230713 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vmcdeepTilePawTDOnly VMCDEEPv20230713 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vvvTilePawPrints VVVDR1 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vvvTilePawPrints VVVDR2 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vvvTilePawPrints VVVDR5 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vvvTilePawPrints VVVv20110718 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Eta vvvTilePawTDOnly VVVDR1 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vvvTilePawTDOnly VVVDR2 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2Eta vvvTilePawTDOnly VVVDR5 Offset of O2 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o2ExtNum sharksTilePawPrints SHARKSv20210421 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum sharksTilePawPrints, sharksTilePawTDOnly SHARKSv20210222 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum ultravistaTilePawPrints, ultravistaTilePawTDOnly ULTRAVISTADR4 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vhsTilePawPrints VHSDR2 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vhsTilePawPrints VHSDR3 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vhsTilePawPrints VHSDR4 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vhsTilePawPrints VHSDR5 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vhsTilePawPrints VHSDR6 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vhsTilePawPrints VHSv20120926 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vhsTilePawPrints VHSv20130417 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vhsTilePawPrints VHSv20140409 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vhsTilePawPrints VHSv20150108 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vhsTilePawPrints VHSv20160114 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vhsTilePawPrints VHSv20160507 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vhsTilePawPrints VHSv20170630 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vhsTilePawPrints VHSv20180419 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vhsTilePawPrints VHSv20201209 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vhsTilePawPrints VHSv20231101 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vhsTilePawPrints, vhsTilePawTDOnly VHSDR1 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum videoTilePawPrints VIDEODR3 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum videoTilePawPrints VIDEODR4 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum videoTilePawPrints VIDEODR5 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum videoTilePawPrints VIDEOv20111208 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum videoTilePawPrints, videoTilePawTDOnly VIDEODR2 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vikingTilePawPrints VIKINGDR3 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vikingTilePawPrints VIKINGDR4 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vikingTilePawPrints VIKINGv20110714 the extension number of the O2 detection int 4   -99999999 meta.id
o2ExtNum vikingTilePawPrints VIKINGv20111019 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vikingTilePawPrints VIKINGv20130417 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vikingTilePawPrints VIKINGv20140402 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vikingTilePawPrints VIKINGv20150421 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vikingTilePawPrints VIKINGv20151230 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vikingTilePawPrints VIKINGv20160406 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vikingTilePawPrints VIKINGv20161202 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vikingTilePawPrints VIKINGv20170715 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vikingTilePawPrints, vikingTilePawTDOnly VIKINGDR2 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCDR2 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCDR3 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCDR4 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCDR5 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20110816 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20110909 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20120126 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20121128 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20130304 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20130805 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20140428 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20140903 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20150309 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20151218 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20160311 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20160822 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20170109 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20170411 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20171101 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20180702 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20181120 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20191212 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20210708 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20230816 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints VMCv20240226 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcTilePawPrints, vmcTilePawTDOnly VMCDR1 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vmcdeepTilePawPrints, vmcdeepTilePawTDOnly VMCDEEPv20230713 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vvvTilePawPrints VVVDR2 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vvvTilePawPrints VVVDR5 the extension number of the O2 detection tinyint 1   2 meta.id
o2ExtNum vvvTilePawPrints VVVv20110718 the extension number of the O2 detection int 4   -99999999 meta.id
o2ExtNum vvvTilePawPrints, vvvTilePawTDOnly VVVDR1 the extension number of the O2 detection tinyint 1   2 meta.id
o2mfID sharksTileSet SHARKSv20210222 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID sharksTileSet SHARKSv20210421 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID ultravistaTileSet ULTRAVISTADR4 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vhsTileSet VHSDR1 the UID of the relevant offset O2 multiframe bigint 8     obs.field
o2mfID vhsTileSet VHSDR2 the UID of the relevant offset O2 multiframe bigint 8     obs.field
o2mfID vhsTileSet VHSDR3 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vhsTileSet VHSDR4 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vhsTileSet VHSDR5 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vhsTileSet VHSDR6 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vhsTileSet VHSv20120926 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vhsTileSet VHSv20130417 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vhsTileSet VHSv20140409 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vhsTileSet VHSv20150108 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vhsTileSet VHSv20160114 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vhsTileSet VHSv20160507 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vhsTileSet VHSv20170630 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vhsTileSet VHSv20180419 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vhsTileSet VHSv20201209 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vhsTileSet VHSv20231101 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID videoTileSet VIDEODR2 the UID of the relevant offset O2 multiframe bigint 8     obs.field
o2mfID videoTileSet VIDEODR3 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID videoTileSet VIDEODR4 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID videoTileSet VIDEODR5 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID videoTileSet VIDEOv20111208 the UID of the relevant offset O2 multiframe bigint 8     obs.field
o2mfID vikingTileSet VIKINGDR2 the UID of the relevant offset O2 multiframe bigint 8     obs.field
o2mfID vikingTileSet VIKINGDR3 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vikingTileSet VIKINGDR4 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vikingTileSet VIKINGv20110714 the UID of the relevant offset O2 multiframe bigint 8     obs.field
o2mfID vikingTileSet VIKINGv20111019 the UID of the relevant offset O2 multiframe bigint 8     obs.field
o2mfID vikingTileSet VIKINGv20130417 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vikingTileSet VIKINGv20140402 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vikingTileSet VIKINGv20150421 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vikingTileSet VIKINGv20151230 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vikingTileSet VIKINGv20160406 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vikingTileSet VIKINGv20161202 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vikingTileSet VIKINGv20170715 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCDR1 the UID of the relevant offset O2 multiframe bigint 8     obs.field
o2mfID vmcTileSet VMCDR2 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCDR3 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCDR4 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCDR5 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCv20110816 the UID of the relevant offset O2 multiframe bigint 8     obs.field
o2mfID vmcTileSet VMCv20110909 the UID of the relevant offset O2 multiframe bigint 8     obs.field
o2mfID vmcTileSet VMCv20120126 the UID of the relevant offset O2 multiframe bigint 8     obs.field
o2mfID vmcTileSet VMCv20121128 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCv20130304 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCv20130805 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCv20140428 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCv20140903 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCv20150309 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCv20151218 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCv20160311 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCv20160822 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCv20170109 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCv20170411 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCv20171101 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCv20180702 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCv20181120 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCv20191212 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCv20210708 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCv20230816 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcTileSet VMCv20240226 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vmcdeepTileSet VMCDEEPv20230713 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vvvTileSet VVVDR1 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vvvTileSet VVVDR2 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vvvTileSet VVVDR5 the UID of the relevant offset O2 multiframe bigint 8     meta.id;obs.field
o2mfID vvvTileSet VVVv20110718 the UID of the relevant offset O2 multiframe bigint 8     obs.field
o2SeqNum sharksTilePawPrints SHARKSv20210421 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum sharksTilePawPrints, sharksTilePawTDOnly SHARKSv20210222 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum ultravistaTilePawPrints, ultravistaTilePawTDOnly ULTRAVISTADR4 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vhsTilePawPrints VHSDR2 the running number of the O2 detection int 4   -99999999 meta.id
o2SeqNum vhsTilePawPrints VHSDR3 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vhsTilePawPrints VHSDR4 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vhsTilePawPrints VHSDR5 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vhsTilePawPrints VHSDR6 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vhsTilePawPrints VHSv20120926 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vhsTilePawPrints VHSv20130417 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vhsTilePawPrints VHSv20140409 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vhsTilePawPrints VHSv20150108 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vhsTilePawPrints VHSv20160114 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vhsTilePawPrints VHSv20160507 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vhsTilePawPrints VHSv20170630 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vhsTilePawPrints VHSv20180419 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vhsTilePawPrints VHSv20201209 the running number of the O2 detection int 4   -99999999 meta.id
o2SeqNum vhsTilePawPrints VHSv20231101 the running number of the O2 detection int 4   -99999999 meta.id
o2SeqNum vhsTilePawPrints, vhsTilePawTDOnly VHSDR1 the running number of the O2 detection int 4   -99999999 meta.id
o2SeqNum videoTilePawPrints VIDEODR3 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum videoTilePawPrints VIDEODR4 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum videoTilePawPrints VIDEODR5 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum videoTilePawPrints VIDEOv20111208 the running number of the O2 detection int 4   -99999999 meta.id
o2SeqNum videoTilePawPrints, videoTilePawTDOnly VIDEODR2 the running number of the O2 detection int 4   -99999999 meta.id
o2SeqNum vikingTilePawPrints VIKINGDR3 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vikingTilePawPrints VIKINGDR4 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vikingTilePawPrints VIKINGv20110714 the running number of the O2 detection int 4   -99999999 meta.id
o2SeqNum vikingTilePawPrints VIKINGv20111019 the running number of the O2 detection int 4   -99999999 meta.id
o2SeqNum vikingTilePawPrints VIKINGv20130417 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vikingTilePawPrints VIKINGv20140402 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vikingTilePawPrints VIKINGv20150421 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vikingTilePawPrints VIKINGv20151230 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vikingTilePawPrints VIKINGv20160406 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vikingTilePawPrints VIKINGv20161202 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vikingTilePawPrints VIKINGv20170715 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vikingTilePawPrints, vikingTilePawTDOnly VIKINGDR2 the running number of the O2 detection int 4   -99999999 meta.id
o2SeqNum vmcTilePawPrints VMCDR2 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vmcTilePawPrints VMCDR3 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vmcTilePawPrints VMCDR4 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vmcTilePawPrints VMCDR5 the running number of the O2 detection int 4   -99999999 meta.id
o2SeqNum vmcTilePawPrints VMCv20110816 the running number of the O2 detection int 4   -99999999 meta.id
o2SeqNum vmcTilePawPrints VMCv20110909 the running number of the O2 detection int 4   -99999999 meta.id
o2SeqNum vmcTilePawPrints VMCv20120126 the running number of the O2 detection int 4   -99999999 meta.id
o2SeqNum vmcTilePawPrints VMCv20121128 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vmcTilePawPrints VMCv20130304 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vmcTilePawPrints VMCv20130805 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vmcTilePawPrints VMCv20140428 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vmcTilePawPrints VMCv20140903 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vmcTilePawPrints VMCv20150309 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vmcTilePawPrints VMCv20151218 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vmcTilePawPrints VMCv20160311 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vmcTilePawPrints VMCv20160822 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vmcTilePawPrints VMCv20170109 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vmcTilePawPrints VMCv20170411 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vmcTilePawPrints VMCv20171101 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vmcTilePawPrints VMCv20180702 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vmcTilePawPrints VMCv20181120 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vmcTilePawPrints VMCv20191212 the running number of the O2 detection int 4   -99999999 meta.id
o2SeqNum vmcTilePawPrints VMCv20210708 the running number of the O2 detection int 4   -99999999 meta.id
o2SeqNum vmcTilePawPrints VMCv20230816 the running number of the O2 detection int 4   -99999999 meta.id
o2SeqNum vmcTilePawPrints VMCv20240226 the running number of the O2 detection int 4   -99999999 meta.id
o2SeqNum vmcTilePawPrints, vmcTilePawTDOnly VMCDR1 the running number of the O2 detection int 4   -99999999 meta.id
o2SeqNum vmcdeepTilePawPrints, vmcdeepTilePawTDOnly VMCDEEPv20230713 the running number of the O2 detection int 4   -99999999 meta.id
o2SeqNum vvvTilePawPrints VVVDR2 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vvvTilePawPrints VVVDR5 the running number of the O2 detection int 4   -99999999 meta.number
o2SeqNum vvvTilePawPrints VVVv20110718 the running number of the O2 detection int 4   -99999999 meta.id
o2SeqNum vvvTilePawPrints, vvvTilePawTDOnly VVVDR1 the running number of the O2 detection int 4   -99999999 meta.number
o2Xi sharksTilePawPrints SHARKSv20210222 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi sharksTilePawPrints SHARKSv20210421 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi sharksTilePawTDOnly SHARKSv20210222 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi sharksTilePawTDOnly SHARKSv20210421 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi ultravistaTilePawPrints ULTRAVISTADR4 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi ultravistaTilePawTDOnly ULTRAVISTADR4 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vhsTilePawPrints VHSDR1 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vhsTilePawPrints VHSDR2 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vhsTilePawPrints VHSDR3 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vhsTilePawPrints VHSDR4 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vhsTilePawPrints VHSDR5 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vhsTilePawPrints VHSDR6 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vhsTilePawPrints VHSv20120926 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vhsTilePawPrints VHSv20130417 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vhsTilePawPrints VHSv20140409 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vhsTilePawPrints VHSv20150108 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vhsTilePawPrints VHSv20160114 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vhsTilePawPrints VHSv20160507 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vhsTilePawPrints VHSv20170630 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vhsTilePawPrints VHSv20180419 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vhsTilePawPrints VHSv20201209 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vhsTilePawPrints VHSv20231101 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vhsTilePawTDOnly VHSDR1 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vhsTilePawTDOnly VHSDR2 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vhsTilePawTDOnly VHSDR3 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vhsTilePawTDOnly VHSDR4 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vhsTilePawTDOnly VHSDR5 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vhsTilePawTDOnly VHSDR6 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vhsTilePawTDOnly VHSv20120926 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vhsTilePawTDOnly VHSv20130417 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vhsTilePawTDOnly VHSv20140409 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vhsTilePawTDOnly VHSv20150108 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vhsTilePawTDOnly VHSv20160114 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vhsTilePawTDOnly VHSv20160507 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vhsTilePawTDOnly VHSv20170630 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vhsTilePawTDOnly VHSv20180419 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vhsTilePawTDOnly VHSv20201209 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vhsTilePawTDOnly VHSv20231101 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi videoTilePawPrints VIDEODR2 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi videoTilePawPrints VIDEODR3 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi videoTilePawPrints VIDEODR4 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi videoTilePawPrints VIDEODR5 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi videoTilePawPrints VIDEOv20111208 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi videoTilePawTDOnly VIDEODR2 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi videoTilePawTDOnly VIDEODR3 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi videoTilePawTDOnly VIDEODR4 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi videoTilePawTDOnly VIDEODR5 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi videoTilePawTDOnly VIDEOv20111208 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vikingTilePawPrints VIKINGDR2 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vikingTilePawPrints VIKINGDR3 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vikingTilePawPrints VIKINGDR4 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vikingTilePawPrints VIKINGv20110714 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vikingTilePawPrints VIKINGv20111019 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vikingTilePawPrints VIKINGv20130417 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vikingTilePawPrints VIKINGv20140402 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vikingTilePawPrints VIKINGv20150421 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vikingTilePawPrints VIKINGv20151230 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vikingTilePawPrints VIKINGv20160406 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vikingTilePawPrints VIKINGv20161202 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vikingTilePawPrints VIKINGv20170715 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vikingTilePawTDOnly VIKINGDR2 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vikingTilePawTDOnly VIKINGDR3 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vikingTilePawTDOnly VIKINGDR4 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vikingTilePawTDOnly VIKINGv20111019 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vikingTilePawTDOnly VIKINGv20130417 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vikingTilePawTDOnly VIKINGv20140402 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vikingTilePawTDOnly VIKINGv20150421 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vikingTilePawTDOnly VIKINGv20151230 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vikingTilePawTDOnly VIKINGv20160406 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vikingTilePawTDOnly VIKINGv20161202 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vikingTilePawTDOnly VIKINGv20170715 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawPrints VMCDR1 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCDR2 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCDR3 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCDR4 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCDR5 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20110816 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20110909 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20120126 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20121128 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20130304 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20130805 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20140428 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20140903 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20150309 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20151218 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20160311 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20160822 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20170109 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20170411 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20171101 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20180702 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20181120 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20191212 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20210708 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20230816 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawPrints VMCv20240226 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcTilePawTDOnly VMCDR1 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCDR2 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCDR3 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCDR4 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCDR5 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20110816 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20110909 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20120126 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20121128 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20130304 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20130805 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20140428 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20140903 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20150309 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20151218 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20160311 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20160822 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20170109 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20170411 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20171101 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20180702 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20181120 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20191212 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20210708 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20230816 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcTilePawTDOnly VMCv20240226 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vmcdeepTilePawPrints VMCDEEPv20230713 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vmcdeepTilePawTDOnly VMCDEEPv20230713 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vvvTilePawPrints VVVDR1 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vvvTilePawPrints VVVDR2 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vvvTilePawPrints VVVDR5 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vvvTilePawPrints VVVv20110718 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o2Xi vvvTilePawTDOnly VVVDR1 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vvvTilePawTDOnly VVVDR2 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o2Xi vvvTilePawTDOnly VVVDR5 Offset of O2 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Eta sharksTilePawPrints SHARKSv20210222 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta sharksTilePawPrints SHARKSv20210421 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta sharksTilePawTDOnly SHARKSv20210222 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta sharksTilePawTDOnly SHARKSv20210421 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta ultravistaTilePawPrints ULTRAVISTADR4 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta ultravistaTilePawTDOnly ULTRAVISTADR4 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vhsTilePawPrints VHSDR1 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vhsTilePawPrints VHSDR2 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vhsTilePawPrints VHSDR3 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vhsTilePawPrints VHSDR4 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vhsTilePawPrints VHSDR5 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vhsTilePawPrints VHSDR6 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vhsTilePawPrints VHSv20120926 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vhsTilePawPrints VHSv20130417 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vhsTilePawPrints VHSv20140409 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vhsTilePawPrints VHSv20150108 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vhsTilePawPrints VHSv20160114 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vhsTilePawPrints VHSv20160507 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vhsTilePawPrints VHSv20170630 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vhsTilePawPrints VHSv20180419 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vhsTilePawPrints VHSv20201209 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vhsTilePawPrints VHSv20231101 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vhsTilePawTDOnly VHSDR1 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vhsTilePawTDOnly VHSDR2 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vhsTilePawTDOnly VHSDR3 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vhsTilePawTDOnly VHSDR4 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vhsTilePawTDOnly VHSDR5 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vhsTilePawTDOnly VHSDR6 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vhsTilePawTDOnly VHSv20120926 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vhsTilePawTDOnly VHSv20130417 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vhsTilePawTDOnly VHSv20140409 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vhsTilePawTDOnly VHSv20150108 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vhsTilePawTDOnly VHSv20160114 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vhsTilePawTDOnly VHSv20160507 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vhsTilePawTDOnly VHSv20170630 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vhsTilePawTDOnly VHSv20180419 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vhsTilePawTDOnly VHSv20201209 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vhsTilePawTDOnly VHSv20231101 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta videoTilePawPrints VIDEODR2 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta videoTilePawPrints VIDEODR3 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta videoTilePawPrints VIDEODR4 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta videoTilePawPrints VIDEODR5 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta videoTilePawPrints VIDEOv20111208 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta videoTilePawTDOnly VIDEODR2 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta videoTilePawTDOnly VIDEODR3 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta videoTilePawTDOnly VIDEODR4 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta videoTilePawTDOnly VIDEODR5 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta videoTilePawTDOnly VIDEOv20111208 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vikingTilePawPrints VIKINGDR2 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vikingTilePawPrints VIKINGDR3 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vikingTilePawPrints VIKINGDR4 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vikingTilePawPrints VIKINGv20110714 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vikingTilePawPrints VIKINGv20111019 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vikingTilePawPrints VIKINGv20130417 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vikingTilePawPrints VIKINGv20140402 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vikingTilePawPrints VIKINGv20150421 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vikingTilePawPrints VIKINGv20151230 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vikingTilePawPrints VIKINGv20160406 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vikingTilePawPrints VIKINGv20161202 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vikingTilePawPrints VIKINGv20170715 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vikingTilePawTDOnly VIKINGDR2 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vikingTilePawTDOnly VIKINGDR3 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vikingTilePawTDOnly VIKINGDR4 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vikingTilePawTDOnly VIKINGv20111019 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vikingTilePawTDOnly VIKINGv20130417 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vikingTilePawTDOnly VIKINGv20140402 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vikingTilePawTDOnly VIKINGv20150421 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vikingTilePawTDOnly VIKINGv20151230 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vikingTilePawTDOnly VIKINGv20160406 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vikingTilePawTDOnly VIKINGv20161202 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vikingTilePawTDOnly VIKINGv20170715 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawPrints VMCDR1 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCDR2 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCDR3 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCDR4 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCDR5 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20110816 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20110909 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20120126 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20121128 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20130304 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20130805 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20140428 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20140903 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20150309 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20151218 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20160311 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20160822 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20170109 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20170411 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20171101 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20180702 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20181120 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20191212 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20210708 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20230816 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawPrints VMCv20240226 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcTilePawTDOnly VMCDR1 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCDR2 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCDR3 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCDR4 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCDR5 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20110816 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20110909 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20120126 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20121128 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20130304 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20130805 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20140428 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20140903 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20150309 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20151218 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20160311 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20160822 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20170109 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20170411 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20171101 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20180702 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20181120 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20191212 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20210708 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20230816 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcTilePawTDOnly VMCv20240226 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vmcdeepTilePawPrints VMCDEEPv20230713 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vmcdeepTilePawTDOnly VMCDEEPv20230713 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vvvTilePawPrints VVVDR1 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vvvTilePawPrints VVVDR2 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vvvTilePawPrints VVVDR5 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vvvTilePawPrints VVVv20110718 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Eta vvvTilePawTDOnly VVVDR1 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vvvTilePawTDOnly VVVDR2 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3Eta vvvTilePawTDOnly VVVDR5 Offset of O3 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o3ExtNum sharksTilePawPrints SHARKSv20210421 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum sharksTilePawPrints, sharksTilePawTDOnly SHARKSv20210222 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum ultravistaTilePawPrints, ultravistaTilePawTDOnly ULTRAVISTADR4 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vhsTilePawPrints VHSDR2 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vhsTilePawPrints VHSDR3 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vhsTilePawPrints VHSDR4 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vhsTilePawPrints VHSDR5 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vhsTilePawPrints VHSDR6 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vhsTilePawPrints VHSv20120926 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vhsTilePawPrints VHSv20130417 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vhsTilePawPrints VHSv20140409 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vhsTilePawPrints VHSv20150108 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vhsTilePawPrints VHSv20160114 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vhsTilePawPrints VHSv20160507 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vhsTilePawPrints VHSv20170630 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vhsTilePawPrints VHSv20180419 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vhsTilePawPrints VHSv20201209 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vhsTilePawPrints VHSv20231101 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vhsTilePawPrints, vhsTilePawTDOnly VHSDR1 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum videoTilePawPrints VIDEODR3 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum videoTilePawPrints VIDEODR4 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum videoTilePawPrints VIDEODR5 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum videoTilePawPrints VIDEOv20111208 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum videoTilePawPrints, videoTilePawTDOnly VIDEODR2 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vikingTilePawPrints VIKINGDR3 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vikingTilePawPrints VIKINGDR4 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vikingTilePawPrints VIKINGv20110714 the extension number of the O3 detection int 4   -99999999 meta.id
o3ExtNum vikingTilePawPrints VIKINGv20111019 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vikingTilePawPrints VIKINGv20130417 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vikingTilePawPrints VIKINGv20140402 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vikingTilePawPrints VIKINGv20150421 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vikingTilePawPrints VIKINGv20151230 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vikingTilePawPrints VIKINGv20160406 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vikingTilePawPrints VIKINGv20161202 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vikingTilePawPrints VIKINGv20170715 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vikingTilePawPrints, vikingTilePawTDOnly VIKINGDR2 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCDR2 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCDR3 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCDR4 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCDR5 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20110816 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20110909 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20120126 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20121128 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20130304 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20130805 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20140428 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20140903 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20150309 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20151218 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20160311 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20160822 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20170109 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20170411 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20171101 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20180702 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20181120 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20191212 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20210708 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20230816 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints VMCv20240226 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcTilePawPrints, vmcTilePawTDOnly VMCDR1 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vmcdeepTilePawPrints, vmcdeepTilePawTDOnly VMCDEEPv20230713 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vvvTilePawPrints VVVDR2 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vvvTilePawPrints VVVDR5 the extension number of the O3 detection tinyint 1   2 meta.id
o3ExtNum vvvTilePawPrints VVVv20110718 the extension number of the O3 detection int 4   -99999999 meta.id
o3ExtNum vvvTilePawPrints, vvvTilePawTDOnly VVVDR1 the extension number of the O3 detection tinyint 1   2 meta.id
o3mfID sharksTileSet SHARKSv20210222 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID sharksTileSet SHARKSv20210421 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID ultravistaTileSet ULTRAVISTADR4 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vhsTileSet VHSDR1 the UID of the relevant offset O3 multiframe bigint 8     obs.field
o3mfID vhsTileSet VHSDR2 the UID of the relevant offset O3 multiframe bigint 8     obs.field
o3mfID vhsTileSet VHSDR3 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vhsTileSet VHSDR4 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vhsTileSet VHSDR5 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vhsTileSet VHSDR6 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vhsTileSet VHSv20120926 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vhsTileSet VHSv20130417 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vhsTileSet VHSv20140409 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vhsTileSet VHSv20150108 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vhsTileSet VHSv20160114 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vhsTileSet VHSv20160507 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vhsTileSet VHSv20170630 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vhsTileSet VHSv20180419 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vhsTileSet VHSv20201209 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vhsTileSet VHSv20231101 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID videoTileSet VIDEODR2 the UID of the relevant offset O3 multiframe bigint 8     obs.field
o3mfID videoTileSet VIDEODR3 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID videoTileSet VIDEODR4 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID videoTileSet VIDEODR5 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID videoTileSet VIDEOv20111208 the UID of the relevant offset O3 multiframe bigint 8     obs.field
o3mfID vikingTileSet VIKINGDR2 the UID of the relevant offset O3 multiframe bigint 8     obs.field
o3mfID vikingTileSet VIKINGDR3 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vikingTileSet VIKINGDR4 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vikingTileSet VIKINGv20110714 the UID of the relevant offset O3 multiframe bigint 8     obs.field
o3mfID vikingTileSet VIKINGv20111019 the UID of the relevant offset O3 multiframe bigint 8     obs.field
o3mfID vikingTileSet VIKINGv20130417 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vikingTileSet VIKINGv20140402 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vikingTileSet VIKINGv20150421 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vikingTileSet VIKINGv20151230 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vikingTileSet VIKINGv20160406 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vikingTileSet VIKINGv20161202 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vikingTileSet VIKINGv20170715 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCDR1 the UID of the relevant offset O3 multiframe bigint 8     obs.field
o3mfID vmcTileSet VMCDR2 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCDR3 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCDR4 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCDR5 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCv20110816 the UID of the relevant offset O3 multiframe bigint 8     obs.field
o3mfID vmcTileSet VMCv20110909 the UID of the relevant offset O3 multiframe bigint 8     obs.field
o3mfID vmcTileSet VMCv20120126 the UID of the relevant offset O3 multiframe bigint 8     obs.field
o3mfID vmcTileSet VMCv20121128 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCv20130304 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCv20130805 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCv20140428 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCv20140903 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCv20150309 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCv20151218 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCv20160311 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCv20160822 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCv20170109 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCv20170411 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCv20171101 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCv20180702 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCv20181120 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCv20191212 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCv20210708 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCv20230816 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcTileSet VMCv20240226 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vmcdeepTileSet VMCDEEPv20230713 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vvvTileSet VVVDR1 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vvvTileSet VVVDR2 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vvvTileSet VVVDR5 the UID of the relevant offset O3 multiframe bigint 8     meta.id;obs.field
o3mfID vvvTileSet VVVv20110718 the UID of the relevant offset O3 multiframe bigint 8     obs.field
o3SeqNum sharksTilePawPrints SHARKSv20210421 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum sharksTilePawPrints, sharksTilePawTDOnly SHARKSv20210222 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum ultravistaTilePawPrints, ultravistaTilePawTDOnly ULTRAVISTADR4 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vhsTilePawPrints VHSDR2 the running number of the O3 detection int 4   -99999999 meta.id
o3SeqNum vhsTilePawPrints VHSDR3 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vhsTilePawPrints VHSDR4 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vhsTilePawPrints VHSDR5 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vhsTilePawPrints VHSDR6 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vhsTilePawPrints VHSv20120926 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vhsTilePawPrints VHSv20130417 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vhsTilePawPrints VHSv20140409 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vhsTilePawPrints VHSv20150108 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vhsTilePawPrints VHSv20160114 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vhsTilePawPrints VHSv20160507 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vhsTilePawPrints VHSv20170630 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vhsTilePawPrints VHSv20180419 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vhsTilePawPrints VHSv20201209 the running number of the O3 detection int 4   -99999999 meta.id
o3SeqNum vhsTilePawPrints VHSv20231101 the running number of the O3 detection int 4   -99999999 meta.id
o3SeqNum vhsTilePawPrints, vhsTilePawTDOnly VHSDR1 the running number of the O3 detection int 4   -99999999 meta.id
o3SeqNum videoTilePawPrints VIDEODR3 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum videoTilePawPrints VIDEODR4 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum videoTilePawPrints VIDEODR5 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum videoTilePawPrints VIDEOv20111208 the running number of the O3 detection int 4   -99999999 meta.id
o3SeqNum videoTilePawPrints, videoTilePawTDOnly VIDEODR2 the running number of the O3 detection int 4   -99999999 meta.id
o3SeqNum vikingTilePawPrints VIKINGDR3 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vikingTilePawPrints VIKINGDR4 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vikingTilePawPrints VIKINGv20110714 the running number of the O3 detection int 4   -99999999 meta.id
o3SeqNum vikingTilePawPrints VIKINGv20111019 the running number of the O3 detection int 4   -99999999 meta.id
o3SeqNum vikingTilePawPrints VIKINGv20130417 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vikingTilePawPrints VIKINGv20140402 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vikingTilePawPrints VIKINGv20150421 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vikingTilePawPrints VIKINGv20151230 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vikingTilePawPrints VIKINGv20160406 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vikingTilePawPrints VIKINGv20161202 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vikingTilePawPrints VIKINGv20170715 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vikingTilePawPrints, vikingTilePawTDOnly VIKINGDR2 the running number of the O3 detection int 4   -99999999 meta.id
o3SeqNum vmcTilePawPrints VMCDR2 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vmcTilePawPrints VMCDR3 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vmcTilePawPrints VMCDR4 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vmcTilePawPrints VMCDR5 the running number of the O3 detection int 4   -99999999 meta.id
o3SeqNum vmcTilePawPrints VMCv20110816 the running number of the O3 detection int 4   -99999999 meta.id
o3SeqNum vmcTilePawPrints VMCv20110909 the running number of the O3 detection int 4   -99999999 meta.id
o3SeqNum vmcTilePawPrints VMCv20120126 the running number of the O3 detection int 4   -99999999 meta.id
o3SeqNum vmcTilePawPrints VMCv20121128 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vmcTilePawPrints VMCv20130304 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vmcTilePawPrints VMCv20130805 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vmcTilePawPrints VMCv20140428 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vmcTilePawPrints VMCv20140903 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vmcTilePawPrints VMCv20150309 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vmcTilePawPrints VMCv20151218 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vmcTilePawPrints VMCv20160311 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vmcTilePawPrints VMCv20160822 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vmcTilePawPrints VMCv20170109 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vmcTilePawPrints VMCv20170411 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vmcTilePawPrints VMCv20171101 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vmcTilePawPrints VMCv20180702 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vmcTilePawPrints VMCv20181120 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vmcTilePawPrints VMCv20191212 the running number of the O3 detection int 4   -99999999 meta.id
o3SeqNum vmcTilePawPrints VMCv20210708 the running number of the O3 detection int 4   -99999999 meta.id
o3SeqNum vmcTilePawPrints VMCv20230816 the running number of the O3 detection int 4   -99999999 meta.id
o3SeqNum vmcTilePawPrints VMCv20240226 the running number of the O3 detection int 4   -99999999 meta.id
o3SeqNum vmcTilePawPrints, vmcTilePawTDOnly VMCDR1 the running number of the O3 detection int 4   -99999999 meta.id
o3SeqNum vmcdeepTilePawPrints, vmcdeepTilePawTDOnly VMCDEEPv20230713 the running number of the O3 detection int 4   -99999999 meta.id
o3SeqNum vvvTilePawPrints VVVDR2 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vvvTilePawPrints VVVDR5 the running number of the O3 detection int 4   -99999999 meta.number
o3SeqNum vvvTilePawPrints VVVv20110718 the running number of the O3 detection int 4   -99999999 meta.id
o3SeqNum vvvTilePawPrints, vvvTilePawTDOnly VVVDR1 the running number of the O3 detection int 4   -99999999 meta.number
o3Xi sharksTilePawPrints SHARKSv20210222 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi sharksTilePawPrints SHARKSv20210421 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi sharksTilePawTDOnly SHARKSv20210222 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi sharksTilePawTDOnly SHARKSv20210421 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi ultravistaTilePawPrints ULTRAVISTADR4 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi ultravistaTilePawTDOnly ULTRAVISTADR4 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vhsTilePawPrints VHSDR1 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vhsTilePawPrints VHSDR2 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vhsTilePawPrints VHSDR3 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vhsTilePawPrints VHSDR4 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vhsTilePawPrints VHSDR5 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vhsTilePawPrints VHSDR6 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vhsTilePawPrints VHSv20120926 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vhsTilePawPrints VHSv20130417 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vhsTilePawPrints VHSv20140409 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vhsTilePawPrints VHSv20150108 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vhsTilePawPrints VHSv20160114 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vhsTilePawPrints VHSv20160507 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vhsTilePawPrints VHSv20170630 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vhsTilePawPrints VHSv20180419 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vhsTilePawPrints VHSv20201209 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vhsTilePawPrints VHSv20231101 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vhsTilePawTDOnly VHSDR1 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vhsTilePawTDOnly VHSDR2 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vhsTilePawTDOnly VHSDR3 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vhsTilePawTDOnly VHSDR4 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vhsTilePawTDOnly VHSDR5 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vhsTilePawTDOnly VHSDR6 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vhsTilePawTDOnly VHSv20120926 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vhsTilePawTDOnly VHSv20130417 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vhsTilePawTDOnly VHSv20140409 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vhsTilePawTDOnly VHSv20150108 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vhsTilePawTDOnly VHSv20160114 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vhsTilePawTDOnly VHSv20160507 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vhsTilePawTDOnly VHSv20170630 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vhsTilePawTDOnly VHSv20180419 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vhsTilePawTDOnly VHSv20201209 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vhsTilePawTDOnly VHSv20231101 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi videoTilePawPrints VIDEODR2 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi videoTilePawPrints VIDEODR3 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi videoTilePawPrints VIDEODR4 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi videoTilePawPrints VIDEODR5 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi videoTilePawPrints VIDEOv20111208 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi videoTilePawTDOnly VIDEODR2 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi videoTilePawTDOnly VIDEODR3 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi videoTilePawTDOnly VIDEODR4 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi videoTilePawTDOnly VIDEODR5 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi videoTilePawTDOnly VIDEOv20111208 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vikingTilePawPrints VIKINGDR2 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vikingTilePawPrints VIKINGDR3 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vikingTilePawPrints VIKINGDR4 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vikingTilePawPrints VIKINGv20110714 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vikingTilePawPrints VIKINGv20111019 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vikingTilePawPrints VIKINGv20130417 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vikingTilePawPrints VIKINGv20140402 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vikingTilePawPrints VIKINGv20150421 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vikingTilePawPrints VIKINGv20151230 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vikingTilePawPrints VIKINGv20160406 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vikingTilePawPrints VIKINGv20161202 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vikingTilePawPrints VIKINGv20170715 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vikingTilePawTDOnly VIKINGDR2 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vikingTilePawTDOnly VIKINGDR3 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vikingTilePawTDOnly VIKINGDR4 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vikingTilePawTDOnly VIKINGv20111019 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vikingTilePawTDOnly VIKINGv20130417 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vikingTilePawTDOnly VIKINGv20140402 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vikingTilePawTDOnly VIKINGv20150421 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vikingTilePawTDOnly VIKINGv20151230 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vikingTilePawTDOnly VIKINGv20160406 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vikingTilePawTDOnly VIKINGv20161202 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vikingTilePawTDOnly VIKINGv20170715 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawPrints VMCDR1 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCDR2 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCDR3 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCDR4 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCDR5 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20110816 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20110909 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20120126 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20121128 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20130304 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20130805 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20140428 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20140903 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20150309 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20151218 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20160311 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20160822 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20170109 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20170411 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20171101 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20180702 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20181120 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20191212 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20210708 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20230816 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawPrints VMCv20240226 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcTilePawTDOnly VMCDR1 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCDR2 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCDR3 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCDR4 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCDR5 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20110816 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20110909 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20120126 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20121128 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20130304 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20130805 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20140428 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20140903 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20150309 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20151218 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20160311 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20160822 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20170109 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20170411 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20171101 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20180702 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20181120 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20191212 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20210708 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20230816 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcTilePawTDOnly VMCv20240226 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vmcdeepTilePawPrints VMCDEEPv20230713 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vmcdeepTilePawTDOnly VMCDEEPv20230713 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vvvTilePawPrints VVVDR1 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vvvTilePawPrints VVVDR2 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vvvTilePawPrints VVVDR5 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vvvTilePawPrints VVVv20110718 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o3Xi vvvTilePawTDOnly VVVDR1 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vvvTilePawTDOnly VVVDR2 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o3Xi vvvTilePawTDOnly VVVDR5 Offset of O3 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Eta sharksTilePawPrints SHARKSv20210222 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta sharksTilePawPrints SHARKSv20210421 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta sharksTilePawTDOnly SHARKSv20210222 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta sharksTilePawTDOnly SHARKSv20210421 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta ultravistaTilePawPrints ULTRAVISTADR4 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta ultravistaTilePawTDOnly ULTRAVISTADR4 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vhsTilePawPrints VHSDR1 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vhsTilePawPrints VHSDR2 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vhsTilePawPrints VHSDR3 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vhsTilePawPrints VHSDR4 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vhsTilePawPrints VHSDR5 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vhsTilePawPrints VHSDR6 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vhsTilePawPrints VHSv20120926 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vhsTilePawPrints VHSv20130417 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vhsTilePawPrints VHSv20140409 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vhsTilePawPrints VHSv20150108 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vhsTilePawPrints VHSv20160114 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vhsTilePawPrints VHSv20160507 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vhsTilePawPrints VHSv20170630 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vhsTilePawPrints VHSv20180419 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vhsTilePawPrints VHSv20201209 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vhsTilePawPrints VHSv20231101 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vhsTilePawTDOnly VHSDR1 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vhsTilePawTDOnly VHSDR2 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vhsTilePawTDOnly VHSDR3 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vhsTilePawTDOnly VHSDR4 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vhsTilePawTDOnly VHSDR5 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vhsTilePawTDOnly VHSDR6 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vhsTilePawTDOnly VHSv20120926 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vhsTilePawTDOnly VHSv20130417 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vhsTilePawTDOnly VHSv20140409 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vhsTilePawTDOnly VHSv20150108 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vhsTilePawTDOnly VHSv20160114 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vhsTilePawTDOnly VHSv20160507 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vhsTilePawTDOnly VHSv20170630 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vhsTilePawTDOnly VHSv20180419 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vhsTilePawTDOnly VHSv20201209 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vhsTilePawTDOnly VHSv20231101 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta videoTilePawPrints VIDEODR2 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta videoTilePawPrints VIDEODR3 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta videoTilePawPrints VIDEODR4 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta videoTilePawPrints VIDEODR5 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta videoTilePawPrints VIDEOv20111208 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta videoTilePawTDOnly VIDEODR2 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta videoTilePawTDOnly VIDEODR3 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta videoTilePawTDOnly VIDEODR4 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta videoTilePawTDOnly VIDEODR5 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta videoTilePawTDOnly VIDEOv20111208 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vikingTilePawPrints VIKINGDR2 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vikingTilePawPrints VIKINGDR3 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vikingTilePawPrints VIKINGDR4 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vikingTilePawPrints VIKINGv20110714 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vikingTilePawPrints VIKINGv20111019 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vikingTilePawPrints VIKINGv20130417 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vikingTilePawPrints VIKINGv20140402 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vikingTilePawPrints VIKINGv20150421 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vikingTilePawPrints VIKINGv20151230 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vikingTilePawPrints VIKINGv20160406 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vikingTilePawPrints VIKINGv20161202 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vikingTilePawPrints VIKINGv20170715 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vikingTilePawTDOnly VIKINGDR2 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vikingTilePawTDOnly VIKINGDR3 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vikingTilePawTDOnly VIKINGDR4 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vikingTilePawTDOnly VIKINGv20111019 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vikingTilePawTDOnly VIKINGv20130417 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vikingTilePawTDOnly VIKINGv20140402 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vikingTilePawTDOnly VIKINGv20150421 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vikingTilePawTDOnly VIKINGv20151230 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vikingTilePawTDOnly VIKINGv20160406 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vikingTilePawTDOnly VIKINGv20161202 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vikingTilePawTDOnly VIKINGv20170715 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawPrints VMCDR1 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCDR2 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCDR3 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCDR4 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCDR5 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20110816 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20110909 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20120126 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20121128 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20130304 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20130805 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20140428 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20140903 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20150309 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20151218 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20160311 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20160822 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20170109 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20170411 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20171101 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20180702 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20181120 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20191212 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20210708 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20230816 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawPrints VMCv20240226 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcTilePawTDOnly VMCDR1 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCDR2 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCDR3 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCDR4 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCDR5 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20110816 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20110909 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20120126 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20121128 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20130304 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20130805 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20140428 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20140903 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20150309 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20151218 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20160311 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20160822 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20170109 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20170411 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20171101 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20180702 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20181120 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20191212 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20210708 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20230816 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcTilePawTDOnly VMCv20240226 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vmcdeepTilePawPrints VMCDEEPv20230713 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vmcdeepTilePawTDOnly VMCDEEPv20230713 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vvvTilePawPrints VVVDR1 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vvvTilePawPrints VVVDR2 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vvvTilePawPrints VVVDR5 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vvvTilePawPrints VVVv20110718 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Eta vvvTilePawTDOnly VVVDR1 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vvvTilePawTDOnly VVVDR2 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4Eta vvvTilePawTDOnly VVVDR5 Offset of O4 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o4ExtNum sharksTilePawPrints SHARKSv20210421 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum sharksTilePawPrints, sharksTilePawTDOnly SHARKSv20210222 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum ultravistaTilePawPrints, ultravistaTilePawTDOnly ULTRAVISTADR4 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vhsTilePawPrints VHSDR2 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vhsTilePawPrints VHSDR3 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vhsTilePawPrints VHSDR4 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vhsTilePawPrints VHSDR5 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vhsTilePawPrints VHSDR6 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vhsTilePawPrints VHSv20120926 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vhsTilePawPrints VHSv20130417 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vhsTilePawPrints VHSv20140409 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vhsTilePawPrints VHSv20150108 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vhsTilePawPrints VHSv20160114 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vhsTilePawPrints VHSv20160507 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vhsTilePawPrints VHSv20170630 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vhsTilePawPrints VHSv20180419 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vhsTilePawPrints VHSv20201209 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vhsTilePawPrints VHSv20231101 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vhsTilePawPrints, vhsTilePawTDOnly VHSDR1 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum videoTilePawPrints VIDEODR3 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum videoTilePawPrints VIDEODR4 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum videoTilePawPrints VIDEODR5 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum videoTilePawPrints VIDEOv20111208 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum videoTilePawPrints, videoTilePawTDOnly VIDEODR2 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vikingTilePawPrints VIKINGDR3 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vikingTilePawPrints VIKINGDR4 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vikingTilePawPrints VIKINGv20110714 the extension number of the O4 detection int 4   -99999999 meta.id
o4ExtNum vikingTilePawPrints VIKINGv20111019 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vikingTilePawPrints VIKINGv20130417 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vikingTilePawPrints VIKINGv20140402 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vikingTilePawPrints VIKINGv20150421 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vikingTilePawPrints VIKINGv20151230 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vikingTilePawPrints VIKINGv20160406 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vikingTilePawPrints VIKINGv20161202 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vikingTilePawPrints VIKINGv20170715 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vikingTilePawPrints, vikingTilePawTDOnly VIKINGDR2 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCDR2 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCDR3 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCDR4 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCDR5 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20110816 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20110909 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20120126 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20121128 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20130304 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20130805 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20140428 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20140903 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20150309 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20151218 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20160311 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20160822 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20170109 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20170411 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20171101 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20180702 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20181120 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20191212 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20210708 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20230816 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints VMCv20240226 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcTilePawPrints, vmcTilePawTDOnly VMCDR1 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vmcdeepTilePawPrints, vmcdeepTilePawTDOnly VMCDEEPv20230713 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vvvTilePawPrints VVVDR2 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vvvTilePawPrints VVVDR5 the extension number of the O4 detection tinyint 1   2 meta.id
o4ExtNum vvvTilePawPrints VVVv20110718 the extension number of the O4 detection int 4   -99999999 meta.id
o4ExtNum vvvTilePawPrints, vvvTilePawTDOnly VVVDR1 the extension number of the O4 detection tinyint 1   2 meta.id
o4mfID sharksTileSet SHARKSv20210222 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID sharksTileSet SHARKSv20210421 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID ultravistaTileSet ULTRAVISTADR4 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vhsTileSet VHSDR1 the UID of the relevant offset O4 multiframe bigint 8     obs.field
o4mfID vhsTileSet VHSDR2 the UID of the relevant offset O4 multiframe bigint 8     obs.field
o4mfID vhsTileSet VHSDR3 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vhsTileSet VHSDR4 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vhsTileSet VHSDR5 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vhsTileSet VHSDR6 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vhsTileSet VHSv20120926 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vhsTileSet VHSv20130417 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vhsTileSet VHSv20140409 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vhsTileSet VHSv20150108 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vhsTileSet VHSv20160114 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vhsTileSet VHSv20160507 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vhsTileSet VHSv20170630 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vhsTileSet VHSv20180419 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vhsTileSet VHSv20201209 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vhsTileSet VHSv20231101 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID videoTileSet VIDEODR2 the UID of the relevant offset O4 multiframe bigint 8     obs.field
o4mfID videoTileSet VIDEODR3 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID videoTileSet VIDEODR4 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID videoTileSet VIDEODR5 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID videoTileSet VIDEOv20111208 the UID of the relevant offset O4 multiframe bigint 8     obs.field
o4mfID vikingTileSet VIKINGDR2 the UID of the relevant offset O4 multiframe bigint 8     obs.field
o4mfID vikingTileSet VIKINGDR3 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vikingTileSet VIKINGDR4 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vikingTileSet VIKINGv20110714 the UID of the relevant offset O4 multiframe bigint 8     obs.field
o4mfID vikingTileSet VIKINGv20111019 the UID of the relevant offset O4 multiframe bigint 8     obs.field
o4mfID vikingTileSet VIKINGv20130417 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vikingTileSet VIKINGv20140402 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vikingTileSet VIKINGv20150421 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vikingTileSet VIKINGv20151230 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vikingTileSet VIKINGv20160406 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vikingTileSet VIKINGv20161202 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vikingTileSet VIKINGv20170715 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCDR1 the UID of the relevant offset O4 multiframe bigint 8     obs.field
o4mfID vmcTileSet VMCDR2 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCDR3 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCDR4 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCDR5 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCv20110816 the UID of the relevant offset O4 multiframe bigint 8     obs.field
o4mfID vmcTileSet VMCv20110909 the UID of the relevant offset O4 multiframe bigint 8     obs.field
o4mfID vmcTileSet VMCv20120126 the UID of the relevant offset O4 multiframe bigint 8     obs.field
o4mfID vmcTileSet VMCv20121128 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCv20130304 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCv20130805 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCv20140428 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCv20140903 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCv20150309 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCv20151218 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCv20160311 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCv20160822 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCv20170109 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCv20170411 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCv20171101 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCv20180702 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCv20181120 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCv20191212 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCv20210708 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCv20230816 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcTileSet VMCv20240226 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vmcdeepTileSet VMCDEEPv20230713 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vvvTileSet VVVDR1 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vvvTileSet VVVDR2 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vvvTileSet VVVDR5 the UID of the relevant offset O4 multiframe bigint 8     meta.id;obs.field
o4mfID vvvTileSet VVVv20110718 the UID of the relevant offset O4 multiframe bigint 8     obs.field
o4SeqNum sharksTilePawPrints SHARKSv20210421 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum sharksTilePawPrints, sharksTilePawTDOnly SHARKSv20210222 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum ultravistaTilePawPrints, ultravistaTilePawTDOnly ULTRAVISTADR4 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vhsTilePawPrints VHSDR2 the running number of the O4 detection int 4   -99999999 meta.id
o4SeqNum vhsTilePawPrints VHSDR3 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vhsTilePawPrints VHSDR4 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vhsTilePawPrints VHSDR5 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vhsTilePawPrints VHSDR6 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vhsTilePawPrints VHSv20120926 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vhsTilePawPrints VHSv20130417 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vhsTilePawPrints VHSv20140409 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vhsTilePawPrints VHSv20150108 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vhsTilePawPrints VHSv20160114 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vhsTilePawPrints VHSv20160507 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vhsTilePawPrints VHSv20170630 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vhsTilePawPrints VHSv20180419 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vhsTilePawPrints VHSv20201209 the running number of the O4 detection int 4   -99999999 meta.id
o4SeqNum vhsTilePawPrints VHSv20231101 the running number of the O4 detection int 4   -99999999 meta.id
o4SeqNum vhsTilePawPrints, vhsTilePawTDOnly VHSDR1 the running number of the O4 detection int 4   -99999999 meta.id
o4SeqNum videoTilePawPrints VIDEODR3 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum videoTilePawPrints VIDEODR4 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum videoTilePawPrints VIDEODR5 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum videoTilePawPrints VIDEOv20111208 the running number of the O4 detection int 4   -99999999 meta.id
o4SeqNum videoTilePawPrints, videoTilePawTDOnly VIDEODR2 the running number of the O4 detection int 4   -99999999 meta.id
o4SeqNum vikingTilePawPrints VIKINGDR3 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vikingTilePawPrints VIKINGDR4 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vikingTilePawPrints VIKINGv20110714 the running number of the O4 detection int 4   -99999999 meta.id
o4SeqNum vikingTilePawPrints VIKINGv20111019 the running number of the O4 detection int 4   -99999999 meta.id
o4SeqNum vikingTilePawPrints VIKINGv20130417 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vikingTilePawPrints VIKINGv20140402 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vikingTilePawPrints VIKINGv20150421 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vikingTilePawPrints VIKINGv20151230 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vikingTilePawPrints VIKINGv20160406 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vikingTilePawPrints VIKINGv20161202 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vikingTilePawPrints VIKINGv20170715 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vikingTilePawPrints, vikingTilePawTDOnly VIKINGDR2 the running number of the O4 detection int 4   -99999999 meta.id
o4SeqNum vmcTilePawPrints VMCDR2 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vmcTilePawPrints VMCDR3 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vmcTilePawPrints VMCDR4 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vmcTilePawPrints VMCDR5 the running number of the O4 detection int 4   -99999999 meta.id
o4SeqNum vmcTilePawPrints VMCv20110816 the running number of the O4 detection int 4   -99999999 meta.id
o4SeqNum vmcTilePawPrints VMCv20110909 the running number of the O4 detection int 4   -99999999 meta.id
o4SeqNum vmcTilePawPrints VMCv20120126 the running number of the O4 detection int 4   -99999999 meta.id
o4SeqNum vmcTilePawPrints VMCv20121128 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vmcTilePawPrints VMCv20130304 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vmcTilePawPrints VMCv20130805 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vmcTilePawPrints VMCv20140428 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vmcTilePawPrints VMCv20140903 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vmcTilePawPrints VMCv20150309 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vmcTilePawPrints VMCv20151218 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vmcTilePawPrints VMCv20160311 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vmcTilePawPrints VMCv20160822 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vmcTilePawPrints VMCv20170109 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vmcTilePawPrints VMCv20170411 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vmcTilePawPrints VMCv20171101 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vmcTilePawPrints VMCv20180702 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vmcTilePawPrints VMCv20181120 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vmcTilePawPrints VMCv20191212 the running number of the O4 detection int 4   -99999999 meta.id
o4SeqNum vmcTilePawPrints VMCv20210708 the running number of the O4 detection int 4   -99999999 meta.id
o4SeqNum vmcTilePawPrints VMCv20230816 the running number of the O4 detection int 4   -99999999 meta.id
o4SeqNum vmcTilePawPrints VMCv20240226 the running number of the O4 detection int 4   -99999999 meta.id
o4SeqNum vmcTilePawPrints, vmcTilePawTDOnly VMCDR1 the running number of the O4 detection int 4   -99999999 meta.id
o4SeqNum vmcdeepTilePawPrints, vmcdeepTilePawTDOnly VMCDEEPv20230713 the running number of the O4 detection int 4   -99999999 meta.id
o4SeqNum vvvTilePawPrints VVVDR2 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vvvTilePawPrints VVVDR5 the running number of the O4 detection int 4   -99999999 meta.number
o4SeqNum vvvTilePawPrints VVVv20110718 the running number of the O4 detection int 4   -99999999 meta.id
o4SeqNum vvvTilePawPrints, vvvTilePawTDOnly VVVDR1 the running number of the O4 detection int 4   -99999999 meta.number
o4Xi sharksTilePawPrints SHARKSv20210222 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi sharksTilePawPrints SHARKSv20210421 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi sharksTilePawTDOnly SHARKSv20210222 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi sharksTilePawTDOnly SHARKSv20210421 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi ultravistaTilePawPrints ULTRAVISTADR4 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi ultravistaTilePawTDOnly ULTRAVISTADR4 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vhsTilePawPrints VHSDR1 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vhsTilePawPrints VHSDR2 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vhsTilePawPrints VHSDR3 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vhsTilePawPrints VHSDR4 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vhsTilePawPrints VHSDR5 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vhsTilePawPrints VHSDR6 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vhsTilePawPrints VHSv20120926 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vhsTilePawPrints VHSv20130417 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vhsTilePawPrints VHSv20140409 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vhsTilePawPrints VHSv20150108 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vhsTilePawPrints VHSv20160114 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vhsTilePawPrints VHSv20160507 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vhsTilePawPrints VHSv20170630 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vhsTilePawPrints VHSv20180419 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vhsTilePawPrints VHSv20201209 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vhsTilePawPrints VHSv20231101 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vhsTilePawTDOnly VHSDR1 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vhsTilePawTDOnly VHSDR2 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vhsTilePawTDOnly VHSDR3 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vhsTilePawTDOnly VHSDR4 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vhsTilePawTDOnly VHSDR5 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vhsTilePawTDOnly VHSDR6 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vhsTilePawTDOnly VHSv20120926 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vhsTilePawTDOnly VHSv20130417 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vhsTilePawTDOnly VHSv20140409 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vhsTilePawTDOnly VHSv20150108 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vhsTilePawTDOnly VHSv20160114 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vhsTilePawTDOnly VHSv20160507 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vhsTilePawTDOnly VHSv20170630 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vhsTilePawTDOnly VHSv20180419 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vhsTilePawTDOnly VHSv20201209 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vhsTilePawTDOnly VHSv20231101 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi videoTilePawPrints VIDEODR2 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi videoTilePawPrints VIDEODR3 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi videoTilePawPrints VIDEODR4 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi videoTilePawPrints VIDEODR5 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi videoTilePawPrints VIDEOv20111208 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi videoTilePawTDOnly VIDEODR2 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi videoTilePawTDOnly VIDEODR3 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi videoTilePawTDOnly VIDEODR4 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi videoTilePawTDOnly VIDEODR5 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi videoTilePawTDOnly VIDEOv20111208 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vikingTilePawPrints VIKINGDR2 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vikingTilePawPrints VIKINGDR3 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vikingTilePawPrints VIKINGDR4 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vikingTilePawPrints VIKINGv20110714 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vikingTilePawPrints VIKINGv20111019 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vikingTilePawPrints VIKINGv20130417 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vikingTilePawPrints VIKINGv20140402 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vikingTilePawPrints VIKINGv20150421 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vikingTilePawPrints VIKINGv20151230 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vikingTilePawPrints VIKINGv20160406 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vikingTilePawPrints VIKINGv20161202 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vikingTilePawPrints VIKINGv20170715 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vikingTilePawTDOnly VIKINGDR2 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vikingTilePawTDOnly VIKINGDR3 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vikingTilePawTDOnly VIKINGDR4 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vikingTilePawTDOnly VIKINGv20111019 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vikingTilePawTDOnly VIKINGv20130417 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vikingTilePawTDOnly VIKINGv20140402 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vikingTilePawTDOnly VIKINGv20150421 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vikingTilePawTDOnly VIKINGv20151230 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vikingTilePawTDOnly VIKINGv20160406 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vikingTilePawTDOnly VIKINGv20161202 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vikingTilePawTDOnly VIKINGv20170715 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawPrints VMCDR1 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCDR2 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCDR3 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCDR4 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCDR5 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20110816 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20110909 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20120126 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20121128 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20130304 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20130805 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20140428 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20140903 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20150309 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20151218 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20160311 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20160822 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20170109 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20170411 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20171101 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20180702 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20181120 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20191212 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20210708 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20230816 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawPrints VMCv20240226 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcTilePawTDOnly VMCDR1 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCDR2 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCDR3 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCDR4 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCDR5 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20110816 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20110909 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20120126 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20121128 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20130304 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20130805 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20140428 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20140903 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20150309 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20151218 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20160311 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20160822 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20170109 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20170411 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20171101 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20180702 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20181120 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20191212 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20210708 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20230816 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcTilePawTDOnly VMCv20240226 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vmcdeepTilePawPrints VMCDEEPv20230713 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vmcdeepTilePawTDOnly VMCDEEPv20230713 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vvvTilePawPrints VVVDR1 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vvvTilePawPrints VVVDR2 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vvvTilePawPrints VVVDR5 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vvvTilePawPrints VVVv20110718 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o4Xi vvvTilePawTDOnly VVVDR1 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vvvTilePawTDOnly VVVDR2 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o4Xi vvvTilePawTDOnly VVVDR5 Offset of O4 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Eta sharksTilePawPrints SHARKSv20210222 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta sharksTilePawPrints SHARKSv20210421 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta sharksTilePawTDOnly SHARKSv20210222 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta sharksTilePawTDOnly SHARKSv20210421 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta ultravistaTilePawPrints ULTRAVISTADR4 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta ultravistaTilePawTDOnly ULTRAVISTADR4 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vhsTilePawPrints VHSDR1 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vhsTilePawPrints VHSDR2 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vhsTilePawPrints VHSDR3 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vhsTilePawPrints VHSDR4 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vhsTilePawPrints VHSDR5 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vhsTilePawPrints VHSDR6 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vhsTilePawPrints VHSv20120926 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vhsTilePawPrints VHSv20130417 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vhsTilePawPrints VHSv20140409 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vhsTilePawPrints VHSv20150108 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vhsTilePawPrints VHSv20160114 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vhsTilePawPrints VHSv20160507 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vhsTilePawPrints VHSv20170630 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vhsTilePawPrints VHSv20180419 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vhsTilePawPrints VHSv20201209 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vhsTilePawPrints VHSv20231101 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vhsTilePawTDOnly VHSDR1 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vhsTilePawTDOnly VHSDR2 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vhsTilePawTDOnly VHSDR3 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vhsTilePawTDOnly VHSDR4 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vhsTilePawTDOnly VHSDR5 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vhsTilePawTDOnly VHSDR6 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vhsTilePawTDOnly VHSv20120926 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vhsTilePawTDOnly VHSv20130417 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vhsTilePawTDOnly VHSv20140409 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vhsTilePawTDOnly VHSv20150108 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vhsTilePawTDOnly VHSv20160114 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vhsTilePawTDOnly VHSv20160507 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vhsTilePawTDOnly VHSv20170630 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vhsTilePawTDOnly VHSv20180419 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vhsTilePawTDOnly VHSv20201209 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vhsTilePawTDOnly VHSv20231101 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta videoTilePawPrints VIDEODR2 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta videoTilePawPrints VIDEODR3 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta videoTilePawPrints VIDEODR4 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta videoTilePawPrints VIDEODR5 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta videoTilePawPrints VIDEOv20111208 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta videoTilePawTDOnly VIDEODR2 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta videoTilePawTDOnly VIDEODR3 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta videoTilePawTDOnly VIDEODR4 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta videoTilePawTDOnly VIDEODR5 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta videoTilePawTDOnly VIDEOv20111208 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vikingTilePawPrints VIKINGDR2 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vikingTilePawPrints VIKINGDR3 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vikingTilePawPrints VIKINGDR4 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vikingTilePawPrints VIKINGv20110714 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vikingTilePawPrints VIKINGv20111019 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vikingTilePawPrints VIKINGv20130417 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vikingTilePawPrints VIKINGv20140402 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vikingTilePawPrints VIKINGv20150421 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vikingTilePawPrints VIKINGv20151230 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vikingTilePawPrints VIKINGv20160406 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vikingTilePawPrints VIKINGv20161202 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vikingTilePawPrints VIKINGv20170715 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vikingTilePawTDOnly VIKINGDR2 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vikingTilePawTDOnly VIKINGDR3 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vikingTilePawTDOnly VIKINGDR4 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vikingTilePawTDOnly VIKINGv20111019 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vikingTilePawTDOnly VIKINGv20130417 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vikingTilePawTDOnly VIKINGv20140402 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vikingTilePawTDOnly VIKINGv20150421 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vikingTilePawTDOnly VIKINGv20151230 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vikingTilePawTDOnly VIKINGv20160406 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vikingTilePawTDOnly VIKINGv20161202 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vikingTilePawTDOnly VIKINGv20170715 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawPrints VMCDR1 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCDR2 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCDR3 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCDR4 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCDR5 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20110816 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20110909 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20120126 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20121128 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20130304 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20130805 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20140428 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20140903 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20150309 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20151218 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20160311 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20160822 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20170109 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20170411 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20171101 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20180702 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20181120 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20191212 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20210708 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20230816 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawPrints VMCv20240226 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcTilePawTDOnly VMCDR1 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCDR2 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCDR3 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCDR4 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCDR5 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20110816 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20110909 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20120126 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20121128 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20130304 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20130805 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20140428 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20140903 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20150309 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20151218 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20160311 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20160822 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20170109 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20170411 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20171101 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20180702 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20181120 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20191212 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20210708 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20230816 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcTilePawTDOnly VMCv20240226 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vmcdeepTilePawPrints VMCDEEPv20230713 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vmcdeepTilePawTDOnly VMCDEEPv20230713 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vvvTilePawPrints VVVDR1 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vvvTilePawPrints VVVDR2 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vvvTilePawPrints VVVDR5 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vvvTilePawPrints VVVv20110718 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Eta vvvTilePawTDOnly VVVDR1 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vvvTilePawTDOnly VVVDR2 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5Eta vvvTilePawTDOnly VVVDR5 Offset of O5 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o5ExtNum sharksTilePawPrints SHARKSv20210421 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum sharksTilePawPrints, sharksTilePawTDOnly SHARKSv20210222 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum ultravistaTilePawPrints, ultravistaTilePawTDOnly ULTRAVISTADR4 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vhsTilePawPrints VHSDR2 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vhsTilePawPrints VHSDR3 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vhsTilePawPrints VHSDR4 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vhsTilePawPrints VHSDR5 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vhsTilePawPrints VHSDR6 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vhsTilePawPrints VHSv20120926 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vhsTilePawPrints VHSv20130417 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vhsTilePawPrints VHSv20140409 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vhsTilePawPrints VHSv20150108 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vhsTilePawPrints VHSv20160114 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vhsTilePawPrints VHSv20160507 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vhsTilePawPrints VHSv20170630 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vhsTilePawPrints VHSv20180419 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vhsTilePawPrints VHSv20201209 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vhsTilePawPrints VHSv20231101 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vhsTilePawPrints, vhsTilePawTDOnly VHSDR1 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum videoTilePawPrints VIDEODR3 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum videoTilePawPrints VIDEODR4 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum videoTilePawPrints VIDEODR5 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum videoTilePawPrints VIDEOv20111208 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum videoTilePawPrints, videoTilePawTDOnly VIDEODR2 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vikingTilePawPrints VIKINGDR3 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vikingTilePawPrints VIKINGDR4 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vikingTilePawPrints VIKINGv20110714 the extension number of the O5 detection int 4   -99999999 meta.id
o5ExtNum vikingTilePawPrints VIKINGv20111019 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vikingTilePawPrints VIKINGv20130417 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vikingTilePawPrints VIKINGv20140402 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vikingTilePawPrints VIKINGv20150421 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vikingTilePawPrints VIKINGv20151230 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vikingTilePawPrints VIKINGv20160406 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vikingTilePawPrints VIKINGv20161202 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vikingTilePawPrints VIKINGv20170715 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vikingTilePawPrints, vikingTilePawTDOnly VIKINGDR2 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCDR2 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCDR3 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCDR4 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCDR5 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20110816 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20110909 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20120126 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20121128 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20130304 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20130805 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20140428 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20140903 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20150309 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20151218 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20160311 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20160822 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20170109 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20170411 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20171101 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20180702 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20181120 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20191212 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20210708 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20230816 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints VMCv20240226 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcTilePawPrints, vmcTilePawTDOnly VMCDR1 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vmcdeepTilePawPrints, vmcdeepTilePawTDOnly VMCDEEPv20230713 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vvvTilePawPrints VVVDR2 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vvvTilePawPrints VVVDR5 the extension number of the O5 detection tinyint 1   2 meta.id
o5ExtNum vvvTilePawPrints VVVv20110718 the extension number of the O5 detection int 4   -99999999 meta.id
o5ExtNum vvvTilePawPrints, vvvTilePawTDOnly VVVDR1 the extension number of the O5 detection tinyint 1   2 meta.id
o5mfID sharksTileSet SHARKSv20210222 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID sharksTileSet SHARKSv20210421 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID ultravistaTileSet ULTRAVISTADR4 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vhsTileSet VHSDR1 the UID of the relevant offset O5 multiframe bigint 8     obs.field
o5mfID vhsTileSet VHSDR2 the UID of the relevant offset O5 multiframe bigint 8     obs.field
o5mfID vhsTileSet VHSDR3 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vhsTileSet VHSDR4 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vhsTileSet VHSDR5 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vhsTileSet VHSDR6 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vhsTileSet VHSv20120926 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vhsTileSet VHSv20130417 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vhsTileSet VHSv20140409 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vhsTileSet VHSv20150108 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vhsTileSet VHSv20160114 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vhsTileSet VHSv20160507 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vhsTileSet VHSv20170630 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vhsTileSet VHSv20180419 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vhsTileSet VHSv20201209 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vhsTileSet VHSv20231101 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID videoTileSet VIDEODR2 the UID of the relevant offset O5 multiframe bigint 8     obs.field
o5mfID videoTileSet VIDEODR3 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID videoTileSet VIDEODR4 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID videoTileSet VIDEODR5 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID videoTileSet VIDEOv20111208 the UID of the relevant offset O5 multiframe bigint 8     obs.field
o5mfID vikingTileSet VIKINGDR2 the UID of the relevant offset O5 multiframe bigint 8     obs.field
o5mfID vikingTileSet VIKINGDR3 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vikingTileSet VIKINGDR4 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vikingTileSet VIKINGv20110714 the UID of the relevant offset O5 multiframe bigint 8     obs.field
o5mfID vikingTileSet VIKINGv20111019 the UID of the relevant offset O5 multiframe bigint 8     obs.field
o5mfID vikingTileSet VIKINGv20130417 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vikingTileSet VIKINGv20140402 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vikingTileSet VIKINGv20150421 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vikingTileSet VIKINGv20151230 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vikingTileSet VIKINGv20160406 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vikingTileSet VIKINGv20161202 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vikingTileSet VIKINGv20170715 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCDR1 the UID of the relevant offset O5 multiframe bigint 8     obs.field
o5mfID vmcTileSet VMCDR2 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCDR3 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCDR4 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCDR5 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCv20110816 the UID of the relevant offset O5 multiframe bigint 8     obs.field
o5mfID vmcTileSet VMCv20110909 the UID of the relevant offset O5 multiframe bigint 8     obs.field
o5mfID vmcTileSet VMCv20120126 the UID of the relevant offset O5 multiframe bigint 8     obs.field
o5mfID vmcTileSet VMCv20121128 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCv20130304 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCv20130805 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCv20140428 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCv20140903 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCv20150309 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCv20151218 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCv20160311 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCv20160822 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCv20170109 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCv20170411 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCv20171101 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCv20180702 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCv20181120 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCv20191212 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCv20210708 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCv20230816 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcTileSet VMCv20240226 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vmcdeepTileSet VMCDEEPv20230713 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vvvTileSet VVVDR1 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vvvTileSet VVVDR2 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vvvTileSet VVVDR5 the UID of the relevant offset O5 multiframe bigint 8     meta.id;obs.field
o5mfID vvvTileSet VVVv20110718 the UID of the relevant offset O5 multiframe bigint 8     obs.field
o5SeqNum sharksTilePawPrints SHARKSv20210421 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum sharksTilePawPrints, sharksTilePawTDOnly SHARKSv20210222 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum ultravistaTilePawPrints, ultravistaTilePawTDOnly ULTRAVISTADR4 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vhsTilePawPrints VHSDR2 the running number of the O5 detection int 4   -99999999 meta.id
o5SeqNum vhsTilePawPrints VHSDR3 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vhsTilePawPrints VHSDR4 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vhsTilePawPrints VHSDR5 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vhsTilePawPrints VHSDR6 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vhsTilePawPrints VHSv20120926 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vhsTilePawPrints VHSv20130417 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vhsTilePawPrints VHSv20140409 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vhsTilePawPrints VHSv20150108 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vhsTilePawPrints VHSv20160114 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vhsTilePawPrints VHSv20160507 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vhsTilePawPrints VHSv20170630 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vhsTilePawPrints VHSv20180419 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vhsTilePawPrints VHSv20201209 the running number of the O5 detection int 4   -99999999 meta.id
o5SeqNum vhsTilePawPrints VHSv20231101 the running number of the O5 detection int 4   -99999999 meta.id
o5SeqNum vhsTilePawPrints, vhsTilePawTDOnly VHSDR1 the running number of the O5 detection int 4   -99999999 meta.id
o5SeqNum videoTilePawPrints VIDEODR3 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum videoTilePawPrints VIDEODR4 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum videoTilePawPrints VIDEODR5 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum videoTilePawPrints VIDEOv20111208 the running number of the O5 detection int 4   -99999999 meta.id
o5SeqNum videoTilePawPrints, videoTilePawTDOnly VIDEODR2 the running number of the O5 detection int 4   -99999999 meta.id
o5SeqNum vikingTilePawPrints VIKINGDR3 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vikingTilePawPrints VIKINGDR4 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vikingTilePawPrints VIKINGv20110714 the running number of the O5 detection int 4   -99999999 meta.id
o5SeqNum vikingTilePawPrints VIKINGv20111019 the running number of the O5 detection int 4   -99999999 meta.id
o5SeqNum vikingTilePawPrints VIKINGv20130417 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vikingTilePawPrints VIKINGv20140402 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vikingTilePawPrints VIKINGv20150421 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vikingTilePawPrints VIKINGv20151230 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vikingTilePawPrints VIKINGv20160406 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vikingTilePawPrints VIKINGv20161202 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vikingTilePawPrints VIKINGv20170715 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vikingTilePawPrints, vikingTilePawTDOnly VIKINGDR2 the running number of the O5 detection int 4   -99999999 meta.id
o5SeqNum vmcTilePawPrints VMCDR2 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vmcTilePawPrints VMCDR3 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vmcTilePawPrints VMCDR4 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vmcTilePawPrints VMCDR5 the running number of the O5 detection int 4   -99999999 meta.id
o5SeqNum vmcTilePawPrints VMCv20110816 the running number of the O5 detection int 4   -99999999 meta.id
o5SeqNum vmcTilePawPrints VMCv20110909 the running number of the O5 detection int 4   -99999999 meta.id
o5SeqNum vmcTilePawPrints VMCv20120126 the running number of the O5 detection int 4   -99999999 meta.id
o5SeqNum vmcTilePawPrints VMCv20121128 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vmcTilePawPrints VMCv20130304 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vmcTilePawPrints VMCv20130805 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vmcTilePawPrints VMCv20140428 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vmcTilePawPrints VMCv20140903 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vmcTilePawPrints VMCv20150309 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vmcTilePawPrints VMCv20151218 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vmcTilePawPrints VMCv20160311 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vmcTilePawPrints VMCv20160822 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vmcTilePawPrints VMCv20170109 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vmcTilePawPrints VMCv20170411 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vmcTilePawPrints VMCv20171101 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vmcTilePawPrints VMCv20180702 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vmcTilePawPrints VMCv20181120 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vmcTilePawPrints VMCv20191212 the running number of the O5 detection int 4   -99999999 meta.id
o5SeqNum vmcTilePawPrints VMCv20210708 the running number of the O5 detection int 4   -99999999 meta.id
o5SeqNum vmcTilePawPrints VMCv20230816 the running number of the O5 detection int 4   -99999999 meta.id
o5SeqNum vmcTilePawPrints VMCv20240226 the running number of the O5 detection int 4   -99999999 meta.id
o5SeqNum vmcTilePawPrints, vmcTilePawTDOnly VMCDR1 the running number of the O5 detection int 4   -99999999 meta.id
o5SeqNum vmcdeepTilePawPrints, vmcdeepTilePawTDOnly VMCDEEPv20230713 the running number of the O5 detection int 4   -99999999 meta.id
o5SeqNum vvvTilePawPrints VVVDR2 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vvvTilePawPrints VVVDR5 the running number of the O5 detection int 4   -99999999 meta.number
o5SeqNum vvvTilePawPrints VVVv20110718 the running number of the O5 detection int 4   -99999999 meta.id
o5SeqNum vvvTilePawPrints, vvvTilePawTDOnly VVVDR1 the running number of the O5 detection int 4   -99999999 meta.number
o5Xi sharksTilePawPrints SHARKSv20210222 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi sharksTilePawPrints SHARKSv20210421 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi sharksTilePawTDOnly SHARKSv20210222 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi sharksTilePawTDOnly SHARKSv20210421 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi ultravistaTilePawPrints ULTRAVISTADR4 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi ultravistaTilePawTDOnly ULTRAVISTADR4 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vhsTilePawPrints VHSDR1 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vhsTilePawPrints VHSDR2 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vhsTilePawPrints VHSDR3 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vhsTilePawPrints VHSDR4 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vhsTilePawPrints VHSDR5 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vhsTilePawPrints VHSDR6 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vhsTilePawPrints VHSv20120926 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vhsTilePawPrints VHSv20130417 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vhsTilePawPrints VHSv20140409 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vhsTilePawPrints VHSv20150108 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vhsTilePawPrints VHSv20160114 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vhsTilePawPrints VHSv20160507 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vhsTilePawPrints VHSv20170630 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vhsTilePawPrints VHSv20180419 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vhsTilePawPrints VHSv20201209 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vhsTilePawPrints VHSv20231101 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vhsTilePawTDOnly VHSDR1 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vhsTilePawTDOnly VHSDR2 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vhsTilePawTDOnly VHSDR3 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vhsTilePawTDOnly VHSDR4 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vhsTilePawTDOnly VHSDR5 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vhsTilePawTDOnly VHSDR6 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vhsTilePawTDOnly VHSv20120926 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vhsTilePawTDOnly VHSv20130417 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vhsTilePawTDOnly VHSv20140409 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vhsTilePawTDOnly VHSv20150108 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vhsTilePawTDOnly VHSv20160114 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vhsTilePawTDOnly VHSv20160507 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vhsTilePawTDOnly VHSv20170630 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vhsTilePawTDOnly VHSv20180419 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vhsTilePawTDOnly VHSv20201209 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vhsTilePawTDOnly VHSv20231101 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi videoTilePawPrints VIDEODR2 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi videoTilePawPrints VIDEODR3 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi videoTilePawPrints VIDEODR4 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi videoTilePawPrints VIDEODR5 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi videoTilePawPrints VIDEOv20111208 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi videoTilePawTDOnly VIDEODR2 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi videoTilePawTDOnly VIDEODR3 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi videoTilePawTDOnly VIDEODR4 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi videoTilePawTDOnly VIDEODR5 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi videoTilePawTDOnly VIDEOv20111208 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vikingTilePawPrints VIKINGDR2 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vikingTilePawPrints VIKINGDR3 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vikingTilePawPrints VIKINGDR4 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vikingTilePawPrints VIKINGv20110714 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vikingTilePawPrints VIKINGv20111019 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vikingTilePawPrints VIKINGv20130417 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vikingTilePawPrints VIKINGv20140402 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vikingTilePawPrints VIKINGv20150421 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vikingTilePawPrints VIKINGv20151230 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vikingTilePawPrints VIKINGv20160406 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vikingTilePawPrints VIKINGv20161202 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vikingTilePawPrints VIKINGv20170715 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vikingTilePawTDOnly VIKINGDR2 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vikingTilePawTDOnly VIKINGDR3 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vikingTilePawTDOnly VIKINGDR4 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vikingTilePawTDOnly VIKINGv20111019 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vikingTilePawTDOnly VIKINGv20130417 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vikingTilePawTDOnly VIKINGv20140402 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vikingTilePawTDOnly VIKINGv20150421 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vikingTilePawTDOnly VIKINGv20151230 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vikingTilePawTDOnly VIKINGv20160406 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vikingTilePawTDOnly VIKINGv20161202 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vikingTilePawTDOnly VIKINGv20170715 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawPrints VMCDR1 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCDR2 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCDR3 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCDR4 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCDR5 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20110816 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20110909 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20120126 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20121128 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20130304 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20130805 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20140428 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20140903 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20150309 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20151218 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20160311 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20160822 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20170109 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20170411 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20171101 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20180702 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20181120 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20191212 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20210708 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20230816 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawPrints VMCv20240226 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcTilePawTDOnly VMCDR1 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCDR2 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCDR3 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCDR4 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCDR5 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20110816 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20110909 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20120126 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20121128 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20130304 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20130805 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20140428 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20140903 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20150309 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20151218 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20160311 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20160822 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20170109 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20170411 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20171101 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20180702 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20181120 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20191212 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20210708 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20230816 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcTilePawTDOnly VMCv20240226 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vmcdeepTilePawPrints VMCDEEPv20230713 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vmcdeepTilePawTDOnly VMCDEEPv20230713 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vvvTilePawPrints VVVDR1 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vvvTilePawPrints VVVDR2 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vvvTilePawPrints VVVDR5 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vvvTilePawPrints VVVv20110718 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o5Xi vvvTilePawTDOnly VVVDR1 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vvvTilePawTDOnly VVVDR2 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o5Xi vvvTilePawTDOnly VVVDR5 Offset of O5 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Eta sharksTilePawPrints SHARKSv20210222 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta sharksTilePawPrints SHARKSv20210421 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta sharksTilePawTDOnly SHARKSv20210222 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta sharksTilePawTDOnly SHARKSv20210421 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta ultravistaTilePawPrints ULTRAVISTADR4 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta ultravistaTilePawTDOnly ULTRAVISTADR4 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vhsTilePawPrints VHSDR1 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vhsTilePawPrints VHSDR2 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vhsTilePawPrints VHSDR3 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vhsTilePawPrints VHSDR4 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vhsTilePawPrints VHSDR5 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vhsTilePawPrints VHSDR6 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vhsTilePawPrints VHSv20120926 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vhsTilePawPrints VHSv20130417 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vhsTilePawPrints VHSv20140409 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vhsTilePawPrints VHSv20150108 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vhsTilePawPrints VHSv20160114 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vhsTilePawPrints VHSv20160507 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vhsTilePawPrints VHSv20170630 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vhsTilePawPrints VHSv20180419 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vhsTilePawPrints VHSv20201209 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vhsTilePawPrints VHSv20231101 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vhsTilePawTDOnly VHSDR1 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vhsTilePawTDOnly VHSDR2 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vhsTilePawTDOnly VHSDR3 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vhsTilePawTDOnly VHSDR4 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vhsTilePawTDOnly VHSDR5 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vhsTilePawTDOnly VHSDR6 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vhsTilePawTDOnly VHSv20120926 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vhsTilePawTDOnly VHSv20130417 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vhsTilePawTDOnly VHSv20140409 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vhsTilePawTDOnly VHSv20150108 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vhsTilePawTDOnly VHSv20160114 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vhsTilePawTDOnly VHSv20160507 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vhsTilePawTDOnly VHSv20170630 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vhsTilePawTDOnly VHSv20180419 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vhsTilePawTDOnly VHSv20201209 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vhsTilePawTDOnly VHSv20231101 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta videoTilePawPrints VIDEODR2 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta videoTilePawPrints VIDEODR3 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta videoTilePawPrints VIDEODR4 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta videoTilePawPrints VIDEODR5 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta videoTilePawPrints VIDEOv20111208 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta videoTilePawTDOnly VIDEODR2 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta videoTilePawTDOnly VIDEODR3 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta videoTilePawTDOnly VIDEODR4 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta videoTilePawTDOnly VIDEODR5 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta videoTilePawTDOnly VIDEOv20111208 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vikingTilePawPrints VIKINGDR2 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vikingTilePawPrints VIKINGDR3 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vikingTilePawPrints VIKINGDR4 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vikingTilePawPrints VIKINGv20110714 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vikingTilePawPrints VIKINGv20111019 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vikingTilePawPrints VIKINGv20130417 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vikingTilePawPrints VIKINGv20140402 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vikingTilePawPrints VIKINGv20150421 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vikingTilePawPrints VIKINGv20151230 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vikingTilePawPrints VIKINGv20160406 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vikingTilePawPrints VIKINGv20161202 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vikingTilePawPrints VIKINGv20170715 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vikingTilePawTDOnly VIKINGDR2 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vikingTilePawTDOnly VIKINGDR3 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vikingTilePawTDOnly VIKINGDR4 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vikingTilePawTDOnly VIKINGv20111019 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vikingTilePawTDOnly VIKINGv20130417 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vikingTilePawTDOnly VIKINGv20140402 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vikingTilePawTDOnly VIKINGv20150421 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vikingTilePawTDOnly VIKINGv20151230 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vikingTilePawTDOnly VIKINGv20160406 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vikingTilePawTDOnly VIKINGv20161202 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vikingTilePawTDOnly VIKINGv20170715 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawPrints VMCDR1 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCDR2 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCDR3 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCDR4 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCDR5 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20110816 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20110909 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20120126 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20121128 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20130304 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20130805 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20140428 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20140903 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20150309 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20151218 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20160311 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20160822 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20170109 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20170411 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20171101 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20180702 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20181120 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20191212 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20210708 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20230816 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawPrints VMCv20240226 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcTilePawTDOnly VMCDR1 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCDR2 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCDR3 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCDR4 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCDR5 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20110816 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20110909 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20120126 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20121128 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20130304 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20130805 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20140428 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20140903 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20150309 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20151218 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20160311 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20160822 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20170109 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20170411 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20171101 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20180702 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20181120 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20191212 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20210708 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20230816 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcTilePawTDOnly VMCv20240226 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vmcdeepTilePawPrints VMCDEEPv20230713 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vmcdeepTilePawTDOnly VMCDEEPv20230713 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vvvTilePawPrints VVVDR1 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vvvTilePawPrints VVVDR2 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vvvTilePawPrints VVVDR5 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vvvTilePawPrints VVVv20110718 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Eta vvvTilePawTDOnly VVVDR1 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vvvTilePawTDOnly VVVDR2 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6Eta vvvTilePawTDOnly VVVDR5 Offset of O6 detection from master position (+north/-south) real 4 arcsec -0.9999995e9 pos.eq.dec;arith.diff
o6ExtNum sharksTilePawPrints SHARKSv20210421 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum sharksTilePawPrints, sharksTilePawTDOnly SHARKSv20210222 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum ultravistaTilePawPrints, ultravistaTilePawTDOnly ULTRAVISTADR4 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vhsTilePawPrints VHSDR2 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vhsTilePawPrints VHSDR3 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vhsTilePawPrints VHSDR4 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vhsTilePawPrints VHSDR5 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vhsTilePawPrints VHSDR6 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vhsTilePawPrints VHSv20120926 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vhsTilePawPrints VHSv20130417 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vhsTilePawPrints VHSv20140409 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vhsTilePawPrints VHSv20150108 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vhsTilePawPrints VHSv20160114 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vhsTilePawPrints VHSv20160507 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vhsTilePawPrints VHSv20170630 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vhsTilePawPrints VHSv20180419 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vhsTilePawPrints VHSv20201209 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vhsTilePawPrints VHSv20231101 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vhsTilePawPrints, vhsTilePawTDOnly VHSDR1 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum videoTilePawPrints VIDEODR3 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum videoTilePawPrints VIDEODR4 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum videoTilePawPrints VIDEODR5 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum videoTilePawPrints VIDEOv20111208 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum videoTilePawPrints, videoTilePawTDOnly VIDEODR2 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vikingTilePawPrints VIKINGDR3 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vikingTilePawPrints VIKINGDR4 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vikingTilePawPrints VIKINGv20110714 the extension number of the O6 detection int 4   -99999999 meta.id
o6ExtNum vikingTilePawPrints VIKINGv20111019 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vikingTilePawPrints VIKINGv20130417 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vikingTilePawPrints VIKINGv20140402 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vikingTilePawPrints VIKINGv20150421 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vikingTilePawPrints VIKINGv20151230 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vikingTilePawPrints VIKINGv20160406 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vikingTilePawPrints VIKINGv20161202 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vikingTilePawPrints VIKINGv20170715 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vikingTilePawPrints, vikingTilePawTDOnly VIKINGDR2 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCDR2 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCDR3 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCDR4 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCDR5 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20110816 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20110909 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20120126 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20121128 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20130304 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20130805 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20140428 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20140903 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20150309 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20151218 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20160311 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20160822 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20170109 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20170411 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20171101 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20180702 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20181120 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20191212 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20210708 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20230816 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints VMCv20240226 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcTilePawPrints, vmcTilePawTDOnly VMCDR1 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vmcdeepTilePawPrints, vmcdeepTilePawTDOnly VMCDEEPv20230713 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vvvTilePawPrints VVVDR2 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vvvTilePawPrints VVVDR5 the extension number of the O6 detection tinyint 1   2 meta.id
o6ExtNum vvvTilePawPrints VVVv20110718 the extension number of the O6 detection int 4   -99999999 meta.id
o6ExtNum vvvTilePawPrints, vvvTilePawTDOnly VVVDR1 the extension number of the O6 detection tinyint 1   2 meta.id
o6mfID sharksTileSet SHARKSv20210222 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID sharksTileSet SHARKSv20210421 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID ultravistaTileSet ULTRAVISTADR4 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vhsTileSet VHSDR1 the UID of the relevant offset O6 multiframe bigint 8     obs.field
o6mfID vhsTileSet VHSDR2 the UID of the relevant offset O6 multiframe bigint 8     obs.field
o6mfID vhsTileSet VHSDR3 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vhsTileSet VHSDR4 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vhsTileSet VHSDR5 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vhsTileSet VHSDR6 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vhsTileSet VHSv20120926 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vhsTileSet VHSv20130417 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vhsTileSet VHSv20140409 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vhsTileSet VHSv20150108 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vhsTileSet VHSv20160114 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vhsTileSet VHSv20160507 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vhsTileSet VHSv20170630 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vhsTileSet VHSv20180419 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vhsTileSet VHSv20201209 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vhsTileSet VHSv20231101 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID videoTileSet VIDEODR2 the UID of the relevant offset O6 multiframe bigint 8     obs.field
o6mfID videoTileSet VIDEODR3 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID videoTileSet VIDEODR4 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID videoTileSet VIDEODR5 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID videoTileSet VIDEOv20111208 the UID of the relevant offset O6 multiframe bigint 8     obs.field
o6mfID vikingTileSet VIKINGDR2 the UID of the relevant offset O6 multiframe bigint 8     obs.field
o6mfID vikingTileSet VIKINGDR3 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vikingTileSet VIKINGDR4 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vikingTileSet VIKINGv20110714 the UID of the relevant offset O6 multiframe bigint 8     obs.field
o6mfID vikingTileSet VIKINGv20111019 the UID of the relevant offset O6 multiframe bigint 8     obs.field
o6mfID vikingTileSet VIKINGv20130417 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vikingTileSet VIKINGv20140402 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vikingTileSet VIKINGv20150421 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vikingTileSet VIKINGv20151230 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vikingTileSet VIKINGv20160406 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vikingTileSet VIKINGv20161202 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vikingTileSet VIKINGv20170715 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCDR1 the UID of the relevant offset O6 multiframe bigint 8     obs.field
o6mfID vmcTileSet VMCDR2 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCDR3 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCDR4 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCDR5 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCv20110816 the UID of the relevant offset O6 multiframe bigint 8     obs.field
o6mfID vmcTileSet VMCv20110909 the UID of the relevant offset O6 multiframe bigint 8     obs.field
o6mfID vmcTileSet VMCv20120126 the UID of the relevant offset O6 multiframe bigint 8     obs.field
o6mfID vmcTileSet VMCv20121128 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCv20130304 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCv20130805 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCv20140428 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCv20140903 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCv20150309 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCv20151218 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCv20160311 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCv20160822 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCv20170109 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCv20170411 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCv20171101 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCv20180702 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCv20181120 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCv20191212 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCv20210708 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCv20230816 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcTileSet VMCv20240226 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vmcdeepTileSet VMCDEEPv20230713 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vvvTileSet VVVDR1 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vvvTileSet VVVDR2 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vvvTileSet VVVDR5 the UID of the relevant offset O6 multiframe bigint 8     meta.id;obs.field
o6mfID vvvTileSet VVVv20110718 the UID of the relevant offset O6 multiframe bigint 8     obs.field
o6SeqNum sharksTilePawPrints SHARKSv20210421 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum sharksTilePawPrints, sharksTilePawTDOnly SHARKSv20210222 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum ultravistaTilePawPrints, ultravistaTilePawTDOnly ULTRAVISTADR4 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vhsTilePawPrints VHSDR2 the running number of the O6 detection int 4   -99999999 meta.id
o6SeqNum vhsTilePawPrints VHSDR3 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vhsTilePawPrints VHSDR4 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vhsTilePawPrints VHSDR5 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vhsTilePawPrints VHSDR6 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vhsTilePawPrints VHSv20120926 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vhsTilePawPrints VHSv20130417 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vhsTilePawPrints VHSv20140409 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vhsTilePawPrints VHSv20150108 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vhsTilePawPrints VHSv20160114 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vhsTilePawPrints VHSv20160507 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vhsTilePawPrints VHSv20170630 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vhsTilePawPrints VHSv20180419 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vhsTilePawPrints VHSv20201209 the running number of the O6 detection int 4   -99999999 meta.id
o6SeqNum vhsTilePawPrints VHSv20231101 the running number of the O6 detection int 4   -99999999 meta.id
o6SeqNum vhsTilePawPrints, vhsTilePawTDOnly VHSDR1 the running number of the O6 detection int 4   -99999999 meta.id
o6SeqNum videoTilePawPrints VIDEODR3 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum videoTilePawPrints VIDEODR4 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum videoTilePawPrints VIDEODR5 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum videoTilePawPrints VIDEOv20111208 the running number of the O6 detection int 4   -99999999 meta.id
o6SeqNum videoTilePawPrints, videoTilePawTDOnly VIDEODR2 the running number of the O6 detection int 4   -99999999 meta.id
o6SeqNum vikingTilePawPrints VIKINGDR3 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vikingTilePawPrints VIKINGDR4 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vikingTilePawPrints VIKINGv20110714 the running number of the O6 detection int 4   -99999999 meta.id
o6SeqNum vikingTilePawPrints VIKINGv20111019 the running number of the O6 detection int 4   -99999999 meta.id
o6SeqNum vikingTilePawPrints VIKINGv20130417 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vikingTilePawPrints VIKINGv20140402 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vikingTilePawPrints VIKINGv20150421 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vikingTilePawPrints VIKINGv20151230 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vikingTilePawPrints VIKINGv20160406 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vikingTilePawPrints VIKINGv20161202 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vikingTilePawPrints VIKINGv20170715 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vikingTilePawPrints, vikingTilePawTDOnly VIKINGDR2 the running number of the O6 detection int 4   -99999999 meta.id
o6SeqNum vmcTilePawPrints VMCDR2 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vmcTilePawPrints VMCDR3 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vmcTilePawPrints VMCDR4 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vmcTilePawPrints VMCDR5 the running number of the O6 detection int 4   -99999999 meta.id
o6SeqNum vmcTilePawPrints VMCv20110816 the running number of the O6 detection int 4   -99999999 meta.id
o6SeqNum vmcTilePawPrints VMCv20110909 the running number of the O6 detection int 4   -99999999 meta.id
o6SeqNum vmcTilePawPrints VMCv20120126 the running number of the O6 detection int 4   -99999999 meta.id
o6SeqNum vmcTilePawPrints VMCv20121128 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vmcTilePawPrints VMCv20130304 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vmcTilePawPrints VMCv20130805 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vmcTilePawPrints VMCv20140428 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vmcTilePawPrints VMCv20140903 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vmcTilePawPrints VMCv20150309 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vmcTilePawPrints VMCv20151218 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vmcTilePawPrints VMCv20160311 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vmcTilePawPrints VMCv20160822 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vmcTilePawPrints VMCv20170109 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vmcTilePawPrints VMCv20170411 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vmcTilePawPrints VMCv20171101 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vmcTilePawPrints VMCv20180702 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vmcTilePawPrints VMCv20181120 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vmcTilePawPrints VMCv20191212 the running number of the O6 detection int 4   -99999999 meta.id
o6SeqNum vmcTilePawPrints VMCv20210708 the running number of the O6 detection int 4   -99999999 meta.id
o6SeqNum vmcTilePawPrints VMCv20230816 the running number of the O6 detection int 4   -99999999 meta.id
o6SeqNum vmcTilePawPrints VMCv20240226 the running number of the O6 detection int 4   -99999999 meta.id
o6SeqNum vmcTilePawPrints, vmcTilePawTDOnly VMCDR1 the running number of the O6 detection int 4   -99999999 meta.id
o6SeqNum vmcdeepTilePawPrints, vmcdeepTilePawTDOnly VMCDEEPv20230713 the running number of the O6 detection int 4   -99999999 meta.id
o6SeqNum vvvTilePawPrints VVVDR2 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vvvTilePawPrints VVVDR5 the running number of the O6 detection int 4   -99999999 meta.number
o6SeqNum vvvTilePawPrints VVVv20110718 the running number of the O6 detection int 4   -99999999 meta.id
o6SeqNum vvvTilePawPrints, vvvTilePawTDOnly VVVDR1 the running number of the O6 detection int 4   -99999999 meta.number
o6Xi sharksTilePawPrints SHARKSv20210222 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi sharksTilePawPrints SHARKSv20210421 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi sharksTilePawTDOnly SHARKSv20210222 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi sharksTilePawTDOnly SHARKSv20210421 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi ultravistaTilePawPrints ULTRAVISTADR4 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi ultravistaTilePawTDOnly ULTRAVISTADR4 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vhsTilePawPrints VHSDR1 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vhsTilePawPrints VHSDR2 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vhsTilePawPrints VHSDR3 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vhsTilePawPrints VHSDR4 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vhsTilePawPrints VHSDR5 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vhsTilePawPrints VHSDR6 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vhsTilePawPrints VHSv20120926 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vhsTilePawPrints VHSv20130417 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vhsTilePawPrints VHSv20140409 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vhsTilePawPrints VHSv20150108 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vhsTilePawPrints VHSv20160114 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vhsTilePawPrints VHSv20160507 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vhsTilePawPrints VHSv20170630 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vhsTilePawPrints VHSv20180419 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vhsTilePawPrints VHSv20201209 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vhsTilePawPrints VHSv20231101 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vhsTilePawTDOnly VHSDR1 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vhsTilePawTDOnly VHSDR2 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vhsTilePawTDOnly VHSDR3 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vhsTilePawTDOnly VHSDR4 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vhsTilePawTDOnly VHSDR5 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vhsTilePawTDOnly VHSDR6 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vhsTilePawTDOnly VHSv20120926 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vhsTilePawTDOnly VHSv20130417 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vhsTilePawTDOnly VHSv20140409 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vhsTilePawTDOnly VHSv20150108 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vhsTilePawTDOnly VHSv20160114 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vhsTilePawTDOnly VHSv20160507 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vhsTilePawTDOnly VHSv20170630 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vhsTilePawTDOnly VHSv20180419 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vhsTilePawTDOnly VHSv20201209 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vhsTilePawTDOnly VHSv20231101 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi videoTilePawPrints VIDEODR2 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi videoTilePawPrints VIDEODR3 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi videoTilePawPrints VIDEODR4 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi videoTilePawPrints VIDEODR5 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi videoTilePawPrints VIDEOv20111208 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi videoTilePawTDOnly VIDEODR2 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi videoTilePawTDOnly VIDEODR3 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi videoTilePawTDOnly VIDEODR4 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi videoTilePawTDOnly VIDEODR5 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi videoTilePawTDOnly VIDEOv20111208 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vikingTilePawPrints VIKINGDR2 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vikingTilePawPrints VIKINGDR3 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vikingTilePawPrints VIKINGDR4 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vikingTilePawPrints VIKINGv20110714 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vikingTilePawPrints VIKINGv20111019 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vikingTilePawPrints VIKINGv20130417 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vikingTilePawPrints VIKINGv20140402 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vikingTilePawPrints VIKINGv20150421 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vikingTilePawPrints VIKINGv20151230 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vikingTilePawPrints VIKINGv20160406 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vikingTilePawPrints VIKINGv20161202 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vikingTilePawPrints VIKINGv20170715 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vikingTilePawTDOnly VIKINGDR2 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vikingTilePawTDOnly VIKINGDR3 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vikingTilePawTDOnly VIKINGDR4 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vikingTilePawTDOnly VIKINGv20111019 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vikingTilePawTDOnly VIKINGv20130417 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vikingTilePawTDOnly VIKINGv20140402 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vikingTilePawTDOnly VIKINGv20150421 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vikingTilePawTDOnly VIKINGv20151230 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vikingTilePawTDOnly VIKINGv20160406 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vikingTilePawTDOnly VIKINGv20161202 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vikingTilePawTDOnly VIKINGv20170715 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawPrints VMCDR1 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCDR2 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCDR3 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCDR4 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCDR5 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20110816 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20110909 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20120126 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20121128 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20130304 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20130805 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20140428 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20140903 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20150309 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20151218 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20160311 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20160822 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20170109 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20170411 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20171101 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20180702 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20181120 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20191212 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20210708 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20230816 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawPrints VMCv20240226 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcTilePawTDOnly VMCDR1 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCDR2 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCDR3 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCDR4 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCDR5 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20110816 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20110909 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20120126 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20121128 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20130304 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20130805 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20140428 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20140903 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20150309 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20151218 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20160311 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20160822 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20170109 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20170411 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20171101 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20180702 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20181120 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20191212 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20210708 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20230816 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcTilePawTDOnly VMCv20240226 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vmcdeepTilePawPrints VMCDEEPv20230713 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vmcdeepTilePawTDOnly VMCDEEPv20230713 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vvvTilePawPrints VVVDR1 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vvvTilePawPrints VVVDR2 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vvvTilePawPrints VVVDR5 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vvvTilePawPrints VVVv20110718 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
When associating individual passband detections into merged sources, a generous (in terms of the positional uncertainties) pairing radius of 1.0 arcseconds is used. Such a large association criterion can of course lead to spurious pairings in the merged sources lists (although note that between passband pairs, handshake pairing is done: both passbands must agree that the candidate pair is their nearest neighbour for the pair to propagate through into the merged source table). In order to help filter spurious pairings out, and assuming that large positional offsets between the different passband detections are not expected (e.g. because of source motion, or larger than usual positional uncertainties) then the attributes Xi and Eta can be used to filter any pairings with suspiciously large offsets in one or more bands. For example, for a clean sample of QSOs from the VHS, you might wish to insist that the offsets in the selected sample are all below 0.5 arcsecond: simply add WHERE clauses into the SQL sample selection script to exclude all Xi and Eta values larger than the threshold you want. NB: the master position is the position of the detection in the shortest passband in the set, rather than the ra/dec of the source as stored in source attributes of the same name. The former is used in the pairing process, while the latter is generally the optimally weighted mean position from an astrometric solution or other combinatorial process of all individual detection positions across the available passbands.
o6Xi vvvTilePawTDOnly VVVDR1 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vvvTilePawTDOnly VVVDR2 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
o6Xi vvvTilePawTDOnly VVVDR5 Offset of O6 detection from master position (+east/-west) real 4 arcsec -0.9999995e9 pos.eq.ra;arith.diff
obj_id decapsSource DECAPS Unique DECaPS object ID {catalogue TType keyword: obj_id} bigint 8     meta.id;meta.main
objAltName1 ObjectThin PS1DR2 Alternate name for this object. varchar 32     meta.id
objAltName2 ObjectThin PS1DR2 Altername name for this object. varchar 32     meta.id
objAltName3 ObjectThin PS1DR2 Altername name for this object. varchar 32     meta.id
object Multiframe SHARKSv20210222 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe SHARKSv20210421 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe ULTRAVISTADR4 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VHSDR1 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VHSDR2 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VHSDR3 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VHSDR4 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VHSDR5 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VHSDR6 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VHSv20120926 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VHSv20130417 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VHSv20140409 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VHSv20150108 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VHSv20160114 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VHSv20160507 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VHSv20170630 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VHSv20180419 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VHSv20201209 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VHSv20231101 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VIDEODR2 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VIDEODR3 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VIDEODR4 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VIDEODR5 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VIDEOv20100513 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VIDEOv20111208 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VIKINGDR2 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VIKINGDR3 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VIKINGDR4 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VIKINGv20110714 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VIKINGv20111019 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VIKINGv20130417 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VIKINGv20140402 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VIKINGv20150421 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VIKINGv20151230 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VIKINGv20160406 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VIKINGv20161202 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VIKINGv20170715 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCDEEPv20230713 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCDR1 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCDR2 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCDR3 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCDR4 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCDR5 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20110816 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20110909 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20120126 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20121128 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20130304 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20130805 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20140428 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20140903 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20150309 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20151218 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20160311 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20160822 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20170109 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20170411 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20171101 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20180702 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20181120 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20191212 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20210708 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20230816 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VMCv20240226 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VVVDR1 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VVVDR2 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VVVDR5 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VVVXDR1 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VVVv20100531 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object Multiframe VVVv20110718 Original target. {image primary HDU keyword: OBJECT} varchar 32   NONE  
object sharksMultiframe, ultravistaMultiframe, vhsMultiframe, videoMultiframe, vikingMultiframe, vmcMultiframe, vvvMultiframe VSAQC Original target. varchar 32   NONE  
object_id masterDR2 SKYMAPPER Global unique object ID in the master table. bigint 8     meta.id;meta.main
objectID MapApertureIDsultraVistaMapLc, MapApertureIDsultravistaDual ULTRAVISTADR4 The UID of the object within this survey programme table bigint 8      
objectID MapApertureIDsvikingZY_selJ VIKINGZYSELJv20160909 The UID of the object within this survey programme table bigint 8      
objectID MapApertureIDsvikingZY_selJ VIKINGZYSELJv20170124 The UID of the object within this survey programme table bigint 8      
OBJID agntwomass, denisi, denisj, durukst, fsc, hes, hipass, nvss, rass, shapley, sumss, supercos, twomass SIXDF unique ID number int 4      
OBJID akari_lmc_psa_v1, akari_lmc_psc_v1 AKARI Internal Object ID char 8      
objID Detection, MeanObject, StackObjectAttributes, StackObjectThin PS1DR2 Unique object identifier. bigint 8      
objID ObjectThin PS1DR2 Unique object identifier. bigint 8     meta.id;meta.main
objID sharksDetection SHARKSv20210222 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID sharksDetection SHARKSv20210421 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID ukirtFSstars VIDEOv20100513 Faint standard unique identifier (FS number; see Hawarden et al. 2001, MN, 325, 563) bigint 8      
objID ukirtFSstars VIKINGv20110714 Faint standard unique identifier (FS number; see Hawarden et al. 2001, MN, 325, 563) bigint 8      
objID ukirtFSstars VVVv20100531 Faint standard unique identifier (FS number; see Hawarden et al. 2001, MN, 325, 563) bigint 8      
objID ultravistaDetection ULTRAVISTADR4 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vhsDetection VHSDR1 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vhsDetection VHSDR2 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vhsDetection VHSDR3 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vhsDetection VHSDR4 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vhsDetection VHSDR5 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vhsDetection VHSDR6 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vhsDetection VHSv20120926 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vhsDetection VHSv20130417 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vhsDetection VHSv20140409 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vhsDetection VHSv20150108 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vhsDetection VHSv20160114 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vhsDetection VHSv20160507 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vhsDetection VHSv20170630 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vhsDetection VHSv20180419 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vhsDetection VHSv20201209 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vhsDetection VHSv20231101 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vhsListRemeasurement VHSDR1 Unique identifier for this detection, or default for no detection bigint 8   -99999999 ID_MAIN_-
objID videoDetection VIDEODR2 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID videoDetection VIDEODR3 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID videoDetection VIDEODR4 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID videoDetection VIDEODR5 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID videoDetection VIDEOv20100513 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID videoDetection VIDEOv20111208 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID videoListRemeasurement VIDEOv20100513 Unique identifier for this detection, or default for no detection bigint 8   -99999999 ID_MAIN_-
objID vikingDetection VIKINGDR2 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vikingDetection VIKINGDR3 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vikingDetection VIKINGDR4 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vikingDetection VIKINGv20110714 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vikingDetection VIKINGv20111019 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vikingDetection VIKINGv20130417 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vikingDetection VIKINGv20140402 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vikingDetection VIKINGv20150421 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vikingDetection VIKINGv20151230 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vikingDetection VIKINGv20160406 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vikingDetection VIKINGv20161202 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vikingDetection VIKINGv20170715 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vikingListRemeasurement VIKINGv20110714 Unique identifier for this detection, or default for no detection bigint 8   -99999999 ID_MAIN_-
objID vikingListRemeasurement VIKINGv20111019 Unique identifier for this detection, or default for no detection bigint 8   -99999999 ID_MAIN_-
objID vmcDetection VMCDR1 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCDR2 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCDR3 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCDR4 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCDR5 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20110816 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20110909 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20120126 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20121128 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20130304 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20130805 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20140428 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20140903 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20150309 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20151218 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20160311 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20160822 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20170109 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20170411 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20171101 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20180702 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20181120 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20191212 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20210708 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20230816 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcDetection VMCv20240226 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vmcListRemeasurement VMCv20110816 Unique identifier for this detection, or default for no detection bigint 8   -99999999 ID_MAIN_-
objID vmcListRemeasurement VMCv20110909 Unique identifier for this detection, or default for no detection bigint 8   -99999999 ID_MAIN_-
objID vmcdeepDetection VMCDEEPv20230713 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vvvDetection VVVDR1 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vvvDetection VVVDR2 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vvvDetection VVVv20100531 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vvvDetection, vvvDetectionPawPrints, vvvDetectionTiles VVVDR5 Unique identifier for this detection or default for no detection bigint 8   -99999999 meta.id;meta.main
This attribute is included to provide a single identification number for real detection rows (objID>0) when making cross-neighbour tables between source and detection. In general, users should NOT use this attribute for look-ups between the source and detection tables, because every detector frame has a default row in the detection table, so there are many, many thousands of rows with objID=-99999999 in each detection table which will be associated with every look-up of objID=-99999999 from source (i.e. those rows for which there is no detection or no frame in a particular passband). See the glossary entry for objID in source tables for more information.
objID vvvListRemeasurement VVVv20100531 Unique identifier for this detection, or default for no detection bigint 8   -99999999 ID_MAIN_-
objID vvvListRemeasurement VVVv20110718 Unique identifier for this detection, or default for no detection bigint 8   -99999999 ID_MAIN_-
objIDName MapSurveyTables SHARKSv20210222 The source unique identifier in the table varchar 16     meta.id
objIDName MapSurveyTables SHARKSv20210421 The source unique identifier in the table varchar 16     meta.id
objIDName MapSurveyTables ULTRAVISTADR4 The source unique identifier in the table varchar 16     meta.id
objIDName MapSurveyTables VHSv20201209 The source unique identifier in the table varchar 16     meta.id
objIDName MapSurveyTables VHSv20231101 The source unique identifier in the table varchar 16     meta.id
objIDName MapSurveyTables VMCDEEPv20230713 The source unique identifier in the table varchar 16     meta.id
objIDName MapSurveyTables VMCDR5 The source unique identifier in the table varchar 16     meta.id
objIDName MapSurveyTables VMCv20191212 The source unique identifier in the table varchar 16     meta.id
objIDName MapSurveyTables VMCv20210708 The source unique identifier in the table varchar 16     meta.id
objIDName MapSurveyTables VMCv20230816 The source unique identifier in the table varchar 16     meta.id
objIDName MapSurveyTables VMCv20240226 The source unique identifier in the table varchar 16     meta.id
objIDName MapSurveyTables VVVDR5 The source unique identifier in the table varchar 16     meta.id
objIDName MapSurveyTables VVVXDR1 The source unique identifier in the table varchar 16     meta.id
objInfoFlag ObjectThin PS1DR2 Information flag bitmask indicating details of the photometry. Values listed in ObjectInfoFlags int 4   0 meta.code
objName ObjectThin PS1DR2 IAU name for this object. varchar 32     meta.id
OBJNAME1 akari_lmc_psa_v1, akari_lmc_psc_v1 AKARI Source identifier(an acronym of the catalog) char 10      
OBJNAME2 akari_lmc_psa_v1, akari_lmc_psc_v1 AKARI Source identifier(Jhhmmss.ss-ddmmss.s) char 19      
objNameHMS ObjectThin PS1DR2 Alternate Pan-STARRS name for this object. varchar 32     meta.id
objPopularName ObjectThin PS1DR2 Well known name for this object. varchar 140     meta.id
obReqs RequiredFilters SHARKSv20210222 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters SHARKSv20210421 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters ULTRAVISTADR4 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VHSDR5 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VHSDR6 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VHSv20160114 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VHSv20160507 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VHSv20170630 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VHSv20180419 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VHSv20201209 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VHSv20231101 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VIKINGv20151230 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VIKINGv20160406 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VIKINGv20161202 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VIKINGv20170715 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VMCDEEPv20230713 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VMCDR4 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VMCDR5 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VMCv20151218 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VMCv20160311 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VMCv20160822 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VMCv20170109 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VMCv20170411 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VMCv20171101 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VMCv20180702 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VMCv20181120 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VMCv20191212 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VMCv20210708 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VMCv20230816 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VMCv20240226 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VSAQC For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VVVDR5 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
obReqs RequiredFilters VVVXDR1 For wide shallow surveys with small number of epochs, what OB requirements for each epoch. varchar 32   NONE meta.note
OBS_CLASS twoxmm, twoxmm_v1_2, twoxmmi_dr3_v1_0 XMM Quality classification of the whole observation based on the area flagged as bad in the manual flagging process as compared to the whole detection area. 0 means nothing has been flagged; 1 indicates that 0% < area < 0.1% of the total detection mask has been flagged; 2 indicates that 0.1% <= area < 1% has been flagged; 3 indicates that 1% <= area < 10% has been flagged; 4 indicates that 10% <= area < 100% has been flagged; and 5 means that the whole field was flagged as bad. int 4      
OBS_CLASS xmm3dr4 XMM Quality classification of the whole observation based on the area flagged as bad in the manual flagging process as compared to the whole detection area. 0 means nothing has been flagged; 1 indicates that 0% < area < 0.1% of the total detection mask has been flagged; 2 indicates that 0.1% <= area < 1% has been flagged; 3 indicates that 1% <= area < 10% has been flagged; 4 indicates that 10% <= area < 100% has been flagged; and 5 means that the whole field was flagged as bad. smallint 2      
OBS_ID xmm3dr4 XMM The XMM-Newton observation identification. varchar 50      
obsAirm MultiframeEsoKeys SHARKSv20210222 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys SHARKSv20210421 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys ULTRAVISTADR4 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VHSDR1 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VHSDR2 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VHSDR3 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VHSDR4 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VHSDR5 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VHSDR6 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VHSv20120926 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VHSv20130417 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VHSv20140409 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VHSv20150108 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VHSv20160114 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VHSv20160507 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VHSv20170630 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VHSv20180419 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VHSv20201209 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VHSv20231101 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VIDEODR2 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VIDEODR3 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VIDEODR4 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VIDEODR5 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VIDEOv20111208 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VIKINGDR2 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VIKINGDR3 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VIKINGDR4 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VIKINGv20110714 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VIKINGv20111019 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VIKINGv20130417 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VIKINGv20140402 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VIKINGv20150421 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VIKINGv20151230 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VIKINGv20160406 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VIKINGv20161202 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VIKINGv20170715 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCDEEPv20230713 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCDR1 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCDR2 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCDR3 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCDR4 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCDR5 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20110816 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20110909 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20120126 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20121128 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20130304 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20130805 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20140428 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20140903 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20150309 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20151218 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20160311 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20160822 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20170109 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20170411 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20171101 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20180702 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20181120 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20191212 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20210708 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20230816 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VMCv20240226 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VSAQC Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VVVDR1 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VVVDR2 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VVVDR5 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VVVXDR1 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAirm MultiframeEsoKeys VVVv20110718 Requested maximum airmass {image primary HDU keyword: HIERARCH ESO OBS AIRM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys SHARKSv20210222 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys SHARKSv20210421 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys ULTRAVISTADR4 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VHSDR1 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VHSDR2 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VHSDR3 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VHSDR4 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VHSDR5 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VHSDR6 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VHSv20120926 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VHSv20130417 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VHSv20140409 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VHSv20150108 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VHSv20160114 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VHSv20160507 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VHSv20170630 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VHSv20180419 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VHSv20201209 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VHSv20231101 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VIDEODR2 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VIDEODR3 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VIDEODR4 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VIDEODR5 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VIDEOv20111208 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VIKINGDR2 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VIKINGDR3 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VIKINGDR4 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VIKINGv20110714 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VIKINGv20111019 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VIKINGv20130417 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VIKINGv20140402 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VIKINGv20150421 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VIKINGv20151230 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VIKINGv20160406 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VIKINGv20161202 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VIKINGv20170715 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCDEEPv20230713 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCDR1 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCDR2 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCDR3 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCDR4 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCDR5 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20110816 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20110909 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20120126 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20121128 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20130304 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20130805 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20140428 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20140903 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20150309 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20151218 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20160311 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20160822 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20170109 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20170411 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20171101 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20180702 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20181120 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20191212 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20210708 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20230816 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VMCv20240226 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VSAQC Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VVVDR1 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VVVDR2 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VVVDR5 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VVVXDR1 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiFwhm MultiframeEsoKeys VVVv20110718 Requested maximum seeing {image primary HDU keyword: HIERARCH ESO OBS AMBI FWHM} real 4   -0.9999995e9  
obsAmbiTrans MultiframeEsoKeys SHARKSv20210222 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys SHARKSv20210421 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys ULTRAVISTADR4 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VHSDR1 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VHSDR2 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VHSDR3 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VHSDR4 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VHSDR5 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VHSDR6 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VHSv20120926 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VHSv20130417 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VHSv20140409 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VHSv20150108 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VHSv20160114 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VHSv20160507 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VHSv20170630 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VHSv20180419 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VHSv20201209 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VHSv20231101 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VIDEODR2 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VIDEODR3 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VIDEODR4 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VIDEODR5 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VIDEOv20111208 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VIKINGDR2 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VIKINGDR3 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VIKINGDR4 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VIKINGv20110714 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VIKINGv20111019 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VIKINGv20130417 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VIKINGv20140402 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VIKINGv20150421 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VIKINGv20151230 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VIKINGv20160406 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VIKINGv20161202 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VIKINGv20170715 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCDEEPv20230713 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCDR1 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCDR2 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCDR3 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCDR4 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCDR5 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20110816 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20110909 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20120126 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20121128 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20130304 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20130805 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20140428 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20140903 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20150309 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20151218 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20160311 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20160822 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20170109 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20170411 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20171101 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20180702 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20181120 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20191212 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20210708 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20230816 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VMCv20240226 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VSAQC Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VVVDR1 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VVVDR2 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VVVDR5 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VVVXDR1 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsAmbiTrans MultiframeEsoKeys VVVv20110718 Requested sky transparency {image primary HDU keyword: HIERARCH ESO OBS AMBI TRANS} varchar 64   NONE  
obsContainerID MultiframeEsoKeys SHARKSv20210222 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys SHARKSv20210421 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys ULTRAVISTADR4 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VHSDR1 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VHSDR2 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VHSDR3 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VHSDR4 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VHSDR5 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VHSDR6 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VHSv20120926 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VHSv20130417 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VHSv20140409 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VHSv20150108 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VHSv20160114 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VHSv20160507 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VHSv20170630 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VHSv20180419 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VHSv20201209 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VHSv20231101 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VIDEODR2 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VIDEODR3 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VIDEODR4 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VIDEODR5 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VIDEOv20111208 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VIKINGDR2 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VIKINGDR3 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VIKINGDR4 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VIKINGv20110714 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VIKINGv20111019 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VIKINGv20130417 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VIKINGv20140402 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VIKINGv20150421 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VIKINGv20151230 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VIKINGv20160406 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VIKINGv20161202 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VIKINGv20170715 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCDEEPv20230713 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCDR1 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCDR2 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCDR3 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCDR4 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCDR5 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20110816 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20110909 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20120126 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20121128 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20130304 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20130805 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20140428 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20140903 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20150309 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20151218 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20160311 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20160822 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20170109 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20170411 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20171101 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20180702 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20181120 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20191212 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20210708 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20230816 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VMCv20240226 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VSAQC Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VVVDR1 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VVVDR2 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VVVDR5 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VVVXDR1 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerID MultiframeEsoKeys VVVv20110718 Scheduling container ID {image primary HDU keyword: HIERARCH ESO OBS CONTAINER ID} bigint 8   -99999999  
obsContainerType MultiframeEsoKeys SHARKSv20210222 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys SHARKSv20210421 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys ULTRAVISTADR4 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VHSDR1 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VHSDR2 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VHSDR3 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VHSDR4 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VHSDR5 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VHSDR6 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VHSv20120926 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VHSv20130417 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VHSv20140409 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VHSv20150108 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VHSv20160114 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VHSv20160507 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VHSv20170630 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VHSv20180419 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VHSv20201209 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VHSv20231101 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VIDEODR2 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VIDEODR3 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VIDEODR4 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VIDEODR5 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VIDEOv20111208 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VIKINGDR2 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VIKINGDR3 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VIKINGDR4 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VIKINGv20110714 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VIKINGv20111019 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VIKINGv20130417 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VIKINGv20140402 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VIKINGv20150421 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VIKINGv20151230 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VIKINGv20160406 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VIKINGv20161202 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VIKINGv20170715 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCDEEPv20230713 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCDR1 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCDR2 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCDR3 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCDR4 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCDR5 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20110816 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20110909 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20120126 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20121128 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20130304 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20130805 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20140428 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20140903 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20150309 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20151218 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20160311 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20160822 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20170109 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20170411 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20171101 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20180702 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20181120 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20191212 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20210708 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20230816 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VMCv20240226 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VSAQC Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VVVDR1 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VVVDR2 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VVVDR5 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VVVXDR1 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
obsContainerType MultiframeEsoKeys VVVv20110718 Scheduling container type {image primary HDU keyword: HIERARCH ESO OBS CONTAINER TYPE} varchar 64   NONE  
Obsdate ravedr5Source RAVE Observation Date (YYYYMMDD) int 4 YYYYMMDD   time.obs
OBSDEC spectra SIXDF observed dec (J2000 degrees) float 8 degrees    
obsDid MultiframeEsoKeys SHARKSv20210222 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys SHARKSv20210421 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys ULTRAVISTADR4 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VHSDR1 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VHSDR2 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VHSDR3 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VHSDR4 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VHSDR5 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VHSDR6 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VHSv20120926 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VHSv20130417 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VHSv20140409 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VHSv20150108 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VHSv20160114 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VHSv20160507 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VHSv20170630 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VHSv20180419 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VHSv20201209 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VHSv20231101 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VIDEODR2 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VIDEODR3 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VIDEODR4 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VIDEODR5 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VIDEOv20100513 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VIDEOv20111208 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VIKINGDR2 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VIKINGDR3 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VIKINGDR4 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VIKINGv20110714 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VIKINGv20111019 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VIKINGv20130417 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VIKINGv20140402 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VIKINGv20150421 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VIKINGv20151230 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VIKINGv20160406 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VIKINGv20161202 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VIKINGv20170715 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCDEEPv20230713 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCDR1 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCDR2 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCDR3 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCDR4 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCDR5 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20110816 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20110909 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20120126 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20121128 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20130304 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20130805 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20140428 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20140903 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20150309 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20151218 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20160311 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20160822 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20170109 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20170411 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20171101 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20180702 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20181120 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20191212 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20210708 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20230816 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VMCv20240226 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VSAQC OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VVVDR1 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VVVDR2 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VVVDR5 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VVVXDR1 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VVVv20100531 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
obsDid MultiframeEsoKeys VVVv20110718 OBS Dictionary {image primary HDU keyword: HIERARCH ESO OBS DID} varchar 32   NONE  
observation_time phot_variable_time_series_g_fov GAIADR1 Barycentric light-travle time corrected timestamp for each FoV observation float 8 Barycentric JD in TCB - 2455197.5 days   time.epoch
observed StdFieldInfo VIDEOv20100513 yes or no identifier - have the secondary standards been set up? tinyint 1   0  
observed StdFieldInfo VIKINGv20110714 yes or no identifier - have the secondary standards been set up? tinyint 1   0  
observed StdFieldInfo VVVv20100531 yes or no identifier - have the secondary standards been set up? tinyint 1   0  
observer Multiframe SHARKSv20210222 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe SHARKSv20210421 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe ULTRAVISTADR4 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VHSDR1 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VHSDR2 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VHSDR3 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VHSDR4 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VHSDR5 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VHSDR6 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VHSv20120926 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VHSv20130417 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VHSv20140409 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VHSv20150108 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VHSv20160114 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VHSv20160507 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VHSv20170630 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VHSv20180419 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VHSv20201209 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VHSv20231101 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VIDEODR2 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VIDEODR3 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VIDEODR4 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VIDEODR5 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VIDEOv20100513 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VIDEOv20111208 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VIKINGDR2 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VIKINGDR3 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VIKINGDR4 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VIKINGv20110714 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VIKINGv20111019 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VIKINGv20130417 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VIKINGv20140402 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VIKINGv20150421 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VIKINGv20151230 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VIKINGv20160406 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VIKINGv20161202 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VIKINGv20170715 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCDEEPv20230713 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCDR1 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCDR2 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCDR3 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCDR4 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCDR5 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20110816 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20110909 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20120126 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20121128 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20130304 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20130805 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20140428 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20140903 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20150309 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20151218 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20160311 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20160822 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20170109 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20170411 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20171101 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20180702 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20181120 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20191212 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20210708 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20230816 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VMCv20240226 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VVVDR1 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VVVDR2 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VVVDR5 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VVVXDR1 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VVVv20100531 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer Multiframe VVVv20110718 Name of observer. {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
observer sharksMultiframe, ultravistaMultiframe, vhsMultiframe, videoMultiframe, vikingMultiframe, vmcMultiframe, vvvMultiframe VSAQC Name of observer. varchar 64   NONE  
obsExectime MultiframeEsoKeys SHARKSv20210222 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys SHARKSv20210421 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys ULTRAVISTADR4 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VHSDR1 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VHSDR2 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VHSDR3 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VHSDR4 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VHSDR5 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VHSDR6 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VHSv20120926 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VHSv20130417 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VHSv20140409 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VHSv20150108 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VHSv20160114 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VHSv20160507 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VHSv20170630 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VHSv20180419 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VHSv20201209 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VHSv20231101 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VIDEODR2 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VIDEODR3 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VIDEODR4 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VIDEODR5 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VIDEOv20100513 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VIDEOv20111208 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VIKINGDR2 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VIKINGDR3 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VIKINGDR4 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VIKINGv20110714 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VIKINGv20111019 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VIKINGv20130417 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VIKINGv20140402 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VIKINGv20150421 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VIKINGv20151230 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VIKINGv20160406 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VIKINGv20161202 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VIKINGv20170715 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCDEEPv20230713 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCDR1 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCDR2 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCDR3 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCDR4 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCDR5 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20110816 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20110909 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20120126 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20121128 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20130304 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20130805 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20140428 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20140903 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20150309 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20151218 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20160311 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20160822 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20170109 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20170411 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20171101 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20180702 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20181120 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20191212 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20210708 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20230816 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VMCv20240226 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VSAQC Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VVVDR1 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VVVDR2 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VVVDR5 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VVVXDR1 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VVVv20100531 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsExectime MultiframeEsoKeys VVVv20110718 Expected execution time {image primary HDU keyword: HIERARCH ESO OBS EXECTIME} smallint 2   -9999  
obsGrp MultiframeEsoKeys SHARKSv20210222 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys SHARKSv20210421 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys ULTRAVISTADR4 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VHSDR1 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VHSDR2 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VHSDR3 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VHSDR4 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VHSDR5 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VHSDR6 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VHSv20120926 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VHSv20130417 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VHSv20140409 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VHSv20150108 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VHSv20160114 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VHSv20160507 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VHSv20170630 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VHSv20180419 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VHSv20201209 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VHSv20231101 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VIDEODR2 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VIDEODR3 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VIDEODR4 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VIDEODR5 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VIDEOv20100513 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VIDEOv20111208 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VIKINGDR2 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VIKINGDR3 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VIKINGDR4 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VIKINGv20110714 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VIKINGv20111019 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VIKINGv20130417 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VIKINGv20140402 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VIKINGv20150421 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VIKINGv20151230 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VIKINGv20160406 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VIKINGv20161202 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VIKINGv20170715 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCDEEPv20230713 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCDR1 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCDR2 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCDR3 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCDR4 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCDR5 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20110816 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20110909 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20120126 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20121128 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20130304 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20130805 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20140428 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20140903 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20150309 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20151218 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20160311 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20160822 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20170109 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20170411 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20171101 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20180702 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20181120 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20191212 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20210708 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20230816 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VMCv20240226 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VSAQC linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VVVDR1 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VVVDR2 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VVVDR5 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VVVXDR1 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VVVv20100531 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
obsGrp MultiframeEsoKeys VVVv20110718 linked blocks {image primary HDU keyword: HIERARCH ESO OBS GRP} varchar 4   NONE  
OBSID twoxmm, twoxmm_v1_2, twoxmmi_dr3_v1_0 XMM The XMM-Newton observation identification. varchar 10      
obsID MultiframeEsoKeys SHARKSv20210222 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys SHARKSv20210421 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys ULTRAVISTADR4 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VHSDR1 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VHSDR2 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VHSDR3 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VHSDR4 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VHSDR5 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VHSDR6 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VHSv20120926 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VHSv20130417 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VHSv20140409 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VHSv20150108 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VHSv20160114 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VHSv20160507 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VHSv20170630 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VHSv20180419 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VHSv20201209 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VHSv20231101 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VIDEODR2 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VIDEODR3 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VIDEODR4 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VIDEODR5 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VIDEOv20100513 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VIDEOv20111208 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VIKINGDR2 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VIKINGDR3 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VIKINGDR4 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VIKINGv20110714 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VIKINGv20111019 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VIKINGv20130417 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VIKINGv20140402 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VIKINGv20150421 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VIKINGv20151230 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VIKINGv20160406 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VIKINGv20161202 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VIKINGv20170715 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCDEEPv20230713 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCDR1 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCDR2 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCDR3 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCDR4 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCDR5 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20110816 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20110909 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20120126 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20121128 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20130304 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20130805 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20140428 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20140903 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20150309 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20151218 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20160311 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20160822 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20170109 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20170411 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20171101 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20180702 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20181120 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20191212 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20210708 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20230816 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VMCv20240226 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VSAQC Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VVVDR1 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VVVDR2 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VVVDR5 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VVVXDR1 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VVVv20100531 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
obsID MultiframeEsoKeys VVVv20110718 Observation block ID {image primary HDU keyword: HIERARCH ESO OBS ID} int 4   -99999999  
OBSID_R spectra SIXDF obsid in R frame varchar 32      
OBSID_V spectra SIXDF obsid in V frame varchar 32      
obsMoonDist MultiframeEsoKeys SHARKSv20210222 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys SHARKSv20210421 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys ULTRAVISTADR4 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VHSDR1 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VHSDR2 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VHSDR3 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VHSDR4 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VHSDR5 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VHSDR6 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VHSv20120926 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VHSv20130417 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VHSv20140409 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VHSv20150108 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VHSv20160114 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VHSv20160507 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VHSv20170630 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VHSv20180419 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VHSv20201209 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VHSv20231101 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VIDEODR2 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VIDEODR3 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VIDEODR4 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VIDEODR5 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VIDEOv20111208 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VIKINGDR2 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VIKINGDR3 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VIKINGDR4 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VIKINGv20110714 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VIKINGv20111019 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VIKINGv20130417 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VIKINGv20140402 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VIKINGv20150421 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VIKINGv20151230 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VIKINGv20160406 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VIKINGv20161202 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VIKINGv20170715 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCDEEPv20230713 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCDR1 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCDR2 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCDR3 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCDR4 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCDR5 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20110816 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20110909 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20120126 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20121128 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20130304 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20130805 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20140428 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20140903 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20150309 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20151218 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20160311 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20160822 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20170109 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20170411 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20171101 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20180702 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20181120 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20191212 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20210708 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20230816 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VMCv20240226 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VSAQC Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VVVDR1 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VVVDR2 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VVVDR5 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VVVXDR1 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonDist MultiframeEsoKeys VVVv20110718 Requested minimum angular distance to the moon {image primary HDU keyword: HIERARCH ESO OBS MOON DIST} real 4 deg? -0.9999995e9  
obsMoonFli MultiframeEsoKeys SHARKSv20210222 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys SHARKSv20210421 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys ULTRAVISTADR4 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VHSDR1 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VHSDR2 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VHSDR3 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VHSDR4 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VHSDR5 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VHSDR6 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VHSv20120926 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VHSv20130417 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VHSv20140409 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VHSv20150108 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VHSv20160114 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VHSv20160507 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VHSv20170630 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VHSv20180419 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VHSv20201209 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VHSv20231101 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VIDEODR2 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VIDEODR3 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VIDEODR4 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VIDEODR5 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VIDEOv20111208 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VIKINGDR2 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VIKINGDR3 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VIKINGDR4 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VIKINGv20110714 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VIKINGv20111019 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VIKINGv20130417 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VIKINGv20140402 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VIKINGv20150421 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VIKINGv20151230 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VIKINGv20160406 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VIKINGv20161202 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VIKINGv20170715 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCDEEPv20230713 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCDR1 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCDR2 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCDR3 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCDR4 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCDR5 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20110816 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20110909 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20120126 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20121128 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20130304 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20130805 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20140428 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20140903 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20150309 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20151218 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20160311 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20160822 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20170109 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20170411 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20171101 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20180702 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20181120 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20191212 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20210708 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20230816 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VMCv20240226 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VSAQC Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VVVDR1 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VVVDR2 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VVVDR5 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VVVXDR1 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsMoonFli MultiframeEsoKeys VVVv20110718 Requested maximum fractional lunar illumination {image primary HDU keyword: HIERARCH ESO OBS MOON FLI} real 4   -0.9999995e9  
obsName MultiframeEsoKeys SHARKSv20210222 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys SHARKSv20210421 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys ULTRAVISTADR4 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VHSDR1 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VHSDR2 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VHSDR3 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VHSDR4 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VHSDR5 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VHSDR6 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VHSv20120926 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VHSv20130417 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VHSv20140409 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VHSv20150108 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VHSv20160114 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VHSv20160507 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VHSv20170630 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VHSv20180419 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VHSv20201209 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VHSv20231101 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VIDEODR2 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VIDEODR3 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VIDEODR4 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VIDEODR5 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VIDEOv20100513 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VIDEOv20111208 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VIKINGDR2 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VIKINGDR3 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VIKINGDR4 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VIKINGv20110714 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VIKINGv20111019 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VIKINGv20130417 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VIKINGv20140402 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VIKINGv20150421 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VIKINGv20151230 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VIKINGv20160406 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VIKINGv20161202 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VIKINGv20170715 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCDEEPv20230713 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCDR1 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCDR2 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCDR3 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCDR4 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCDR5 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20110816 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20110909 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20120126 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20121128 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20130304 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20130805 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20140428 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20140903 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20150309 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20151218 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20160311 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20160822 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20170109 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20170411 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20171101 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20180702 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20181120 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20191212 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20210708 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20230816 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VMCv20240226 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VSAQC Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VVVDR1 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VVVDR2 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VVVDR5 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VVVXDR1 Survey tile designation {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VVVv20100531 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsName MultiframeEsoKeys VVVv20110718 OB name {image primary HDU keyword: HIERARCH ESO OBS NAME} varchar 64   NONE  
obsNum Multiframe SHARKSv20210222 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe SHARKSv20210421 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe ULTRAVISTADR4 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VHSDR1 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VHSDR2 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VHSDR3 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VHSDR4 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VHSDR5 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VHSDR6 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VHSv20120926 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VHSv20130417 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VHSv20140409 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VHSv20150108 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VHSv20160114 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VHSv20160507 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VHSv20170630 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VHSv20180419 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VHSv20201209 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VHSv20231101 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VIDEODR2 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VIDEODR3 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VIDEODR4 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VIDEODR5 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VIDEOv20100513 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VIDEOv20111208 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VIKINGDR2 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VIKINGDR3 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VIKINGDR4 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VIKINGv20110714 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VIKINGv20111019 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VIKINGv20130417 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VIKINGv20140402 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VIKINGv20150421 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VIKINGv20151230 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VIKINGv20160406 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VIKINGv20161202 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VIKINGv20170715 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCDEEPv20230713 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCDR1 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCDR2 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCDR3 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCDR4 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCDR5 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20110816 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20110909 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20120126 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20121128 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20130304 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20130805 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20140428 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20140903 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20150309 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20151218 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20160311 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20160822 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20170109 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20170411 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20171101 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20180702 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20181120 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20191212 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20210708 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20230816 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VMCv20240226 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VVVDR1 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VVVDR2 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VVVDR5 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VVVXDR1 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VVVv20100531 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum Multiframe VVVv20110718 Observation number {image primary HDU keyword: OBSNUM} int 4   -99999999  
obsNum sharksMultiframe, ultravistaMultiframe, vhsMultiframe, videoMultiframe, vikingMultiframe, vmcMultiframe, vvvMultiframe VSAQC Observation number int 4   -99999999  
obsObserver MultiframeEsoKeys SHARKSv20210222 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys SHARKSv20210421 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys ULTRAVISTADR4 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VHSDR1 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VHSDR2 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VHSDR3 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VHSDR4 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VHSDR5 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VHSDR6 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VHSv20120926 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VHSv20130417 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VHSv20140409 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VHSv20150108 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VHSv20160114 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VHSv20160507 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VHSv20170630 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VHSv20180419 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VHSv20201209 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VHSv20231101 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VIDEODR2 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VIDEODR3 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VIDEODR4 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VIDEODR5 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VIDEOv20100513 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VIDEOv20111208 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VIKINGDR2 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VIKINGDR3 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VIKINGDR4 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VIKINGv20110714 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VIKINGv20111019 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VIKINGv20130417 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VIKINGv20140402 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VIKINGv20150421 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VIKINGv20151230 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VIKINGv20160406 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VIKINGv20161202 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VIKINGv20170715 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCDEEPv20230713 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCDR1 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCDR2 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCDR3 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCDR4 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCDR5 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20110816 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20110909 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20120126 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20121128 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20130304 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20130805 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20140428 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20140903 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20150309 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20151218 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20160311 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20160822 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20170109 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20170411 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20171101 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20180702 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20181120 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20191212 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20210708 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20230816 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VMCv20240226 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VSAQC Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VVVDR1 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VVVDR2 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VVVDR5 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VVVXDR1 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VVVv20100531 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsObserver MultiframeEsoKeys VVVv20110718 Observer Name {image primary HDU keyword: HIERARCH ESO OBS OBSERVER} varchar 64   NONE  
obsPiCoiID MultiframeEsoKeys SHARKSv20210222 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys SHARKSv20210421 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys ULTRAVISTADR4 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VHSDR1 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VHSDR2 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VHSDR3 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VHSDR4 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VHSDR5 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VHSDR6 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VHSv20120926 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VHSv20130417 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VHSv20140409 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VHSv20150108 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VHSv20160114 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VHSv20160507 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VHSv20170630 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VHSv20180419 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VHSv20201209 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VHSv20231101 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VIDEODR2 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VIDEODR3 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VIDEODR4 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VIDEODR5 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VIDEOv20100513 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VIDEOv20111208 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VIKINGDR2 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VIKINGDR3 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VIKINGDR4 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VIKINGv20110714 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VIKINGv20111019 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VIKINGv20130417 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VIKINGv20140402 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VIKINGv20150421 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VIKINGv20151230 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VIKINGv20160406 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VIKINGv20161202 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VIKINGv20170715 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCDEEPv20230713 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCDR1 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCDR2 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCDR3 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCDR4 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCDR5 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20110816 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20110909 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20120126 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20121128 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20130304 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20130805 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20140428 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20140903 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20150309 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20151218 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20160311 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20160822 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20170109 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20170411 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20171101 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20180702 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20181120 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20191212 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20210708 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20230816 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VMCv20240226 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VSAQC ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VVVDR1 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VVVDR2 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VVVDR5 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VVVXDR1 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VVVv20100531 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiID MultiframeEsoKeys VVVv20110718 ESO internal PI-COI ID {image primary HDU keyword: HIERARCH ESO OBS PI-COI ID} int 4   -99999999  
obsPiCoiName MultiframeEsoKeys SHARKSv20210222 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys SHARKSv20210421 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys ULTRAVISTADR4 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VHSDR1 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VHSDR2 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VHSDR3 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VHSDR4 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VHSDR5 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VHSDR6 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VHSv20120926 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VHSv20130417 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VHSv20140409 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VHSv20150108 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VHSv20160114 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VHSv20160507 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VHSv20170630 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VHSv20180419 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VHSv20201209 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VHSv20231101 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VIDEODR2 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VIDEODR3 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VIDEODR4 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VIDEODR5 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VIDEOv20100513 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VIDEOv20111208 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VIKINGDR2 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VIKINGDR3 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VIKINGDR4 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VIKINGv20110714 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VIKINGv20111019 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VIKINGv20130417 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VIKINGv20140402 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VIKINGv20150421 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VIKINGv20151230 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VIKINGv20160406 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VIKINGv20161202 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VIKINGv20170715 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCDEEPv20230713 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCDR1 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCDR2 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCDR3 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCDR4 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCDR5 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20110816 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20110909 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20120126 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20121128 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20130304 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20130805 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20140428 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20140903 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20150309 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20151218 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20160311 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20160822 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20170109 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20170411 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20171101 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20180702 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20181120 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20191212 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20210708 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20230816 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VMCv20240226 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VSAQC PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VVVDR1 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VVVDR2 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VVVDR5 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VVVXDR1 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VVVv20100531 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsPiCoiName MultiframeEsoKeys VVVv20110718 PI-COI name {image primary HDU keyword: HIERARCH ESO OBS PI-COI NAME} varchar 64   NONE  
obsProgID MultiframeEsoKeys SHARKSv20210222 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys SHARKSv20210421 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys ULTRAVISTADR4 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VHSDR1 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VHSDR2 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VHSDR3 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VHSDR4 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VHSDR5 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VHSDR6 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VHSv20120926 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VHSv20130417 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VHSv20140409 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VHSv20150108 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VHSv20160114 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VHSv20160507 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VHSv20170630 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VHSv20180419 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VHSv20201209 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VHSv20231101 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VIDEODR2 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VIDEODR3 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VIDEODR4 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VIDEODR5 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VIDEOv20100513 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VIDEOv20111208 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VIKINGDR2 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VIKINGDR3 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VIKINGDR4 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VIKINGv20110714 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VIKINGv20111019 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VIKINGv20130417 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VIKINGv20140402 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VIKINGv20150421 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VIKINGv20151230 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VIKINGv20160406 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VIKINGv20161202 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VIKINGv20170715 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCDEEPv20230713 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCDR1 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCDR2 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCDR3 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCDR4 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCDR5 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20110816 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20110909 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20120126 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20121128 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20130304 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20130805 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20140428 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20140903 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20150309 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20151218 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20160311 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20160822 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20170109 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20170411 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20171101 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20180702 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20181120 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20191212 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20210708 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20230816 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VMCv20240226 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VSAQC ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VVVDR1 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VVVDR2 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VVVDR5 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VVVXDR1 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VVVv20100531 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
obsProgID MultiframeEsoKeys VVVv20110718 ESO program identification {image primary HDU keyword: HIERARCH ESO OBS PROG ID} varchar 16   NONE  
OBSRA spectra SIXDF observed ra (J2000 degrees) float 8 degrees    
obsStart MultiframeEsoKeys SHARKSv20210222 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys SHARKSv20210421 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys ULTRAVISTADR4 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VHSDR1 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VHSDR2 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VHSDR3 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VHSDR4 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VHSDR5 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VHSDR6 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VHSv20120926 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VHSv20130417 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VHSv20140409 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VHSv20150108 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VHSv20160114 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VHSv20160507 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VHSv20170630 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VHSv20180419 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VHSv20201209 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VHSv20231101 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VIDEODR2 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VIDEODR3 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VIDEODR4 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VIDEODR5 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VIDEOv20100513 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VIDEOv20111208 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VIKINGDR2 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VIKINGDR3 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VIKINGDR4 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VIKINGv20110714 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VIKINGv20111019 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VIKINGv20130417 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VIKINGv20140402 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VIKINGv20150421 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VIKINGv20151230 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VIKINGv20160406 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VIKINGv20161202 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VIKINGv20170715 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCDEEPv20230713 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCDR1 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCDR2 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCDR3 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCDR4 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCDR5 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20110816 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20110909 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20120126 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20121128 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20130304 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20130805 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20140428 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20140903 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20150309 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20151218 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20160311 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20160822 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20170109 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20170411 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20171101 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20180702 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20181120 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20191212 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20210708 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20230816 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VMCv20240226 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VSAQC OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VVVDR1 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VVVDR2 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VVVDR5 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VVVXDR1 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VVVv20100531 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsStart MultiframeEsoKeys VVVv20110718 OB start time {image primary HDU keyword: HIERARCH ESO OBS START} datetime 8   12-31-9999  
obsTargName MultiframeEsoKeys SHARKSv20210222 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys SHARKSv20210421 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys ULTRAVISTADR4 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VHSDR1 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VHSDR2 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VHSDR3 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VHSDR4 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VHSDR5 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VHSDR6 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VHSv20120926 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VHSv20130417 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VHSv20140409 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VHSv20150108 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VHSv20160114 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VHSv20160507 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VHSv20170630 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VHSv20180419 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VHSv20201209 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VHSv20231101 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VIDEODR2 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VIDEODR3 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VIDEODR4 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VIDEODR5 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VIDEOv20100513 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VIDEOv20111208 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VIKINGDR2 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VIKINGDR3 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VIKINGDR4 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VIKINGv20110714 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VIKINGv20111019 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VIKINGv20130417 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VIKINGv20140402 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VIKINGv20150421 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VIKINGv20151230 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VIKINGv20160406 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VIKINGv20161202 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VIKINGv20170715 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCDEEPv20230713 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCDR1 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCDR2 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCDR3 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCDR4 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCDR5 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20110816 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20110909 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20120126 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20121128 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20130304 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20130805 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20140428 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20140903 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20150309 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20151218 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20160311 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20160822 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20170109 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20170411 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20171101 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20180702 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20181120 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20191212 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20210708 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20230816 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VMCv20240226 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VSAQC OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VVVDR1 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VVVDR2 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VVVDR5 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VVVXDR1 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VVVv20100531 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obsTargName MultiframeEsoKeys VVVv20110718 OB target name {image primary HDU keyword: HIERARCH ESO OBS TARG NAME} varchar 32   NONE  
obStatus Multiframe SHARKSv20210222 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe SHARKSv20210421 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe ULTRAVISTADR4 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VHSDR1 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VHSDR2 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VHSDR3 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VHSDR4 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VHSDR5 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VHSDR6 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VHSv20120926 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VHSv20130417 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VHSv20140409 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VHSv20150108 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VHSv20160114 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VHSv20160507 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VHSv20170630 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VHSv20180419 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VHSv20201209 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VHSv20231101 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VIDEODR2 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VIDEODR3 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VIDEODR4 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VIDEODR5 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VIDEOv20111208 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VIKINGDR2 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VIKINGDR3 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VIKINGDR4 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VIKINGv20110714 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VIKINGv20111019 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VIKINGv20130417 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VIKINGv20140402 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VIKINGv20150421 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VIKINGv20151230 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VIKINGv20160406 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VIKINGv20161202 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VIKINGv20170715 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCDEEPv20230713 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCDR1 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCDR2 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCDR3 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCDR4 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCDR5 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20110816 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20110909 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20120126 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20121128 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20130304 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20130805 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20140428 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20140903 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20150309 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20151218 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20160311 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20160822 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20170109 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20170411 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20171101 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20180702 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20181120 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20191212 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20210708 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20230816 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VMCv20240226 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VVVDR1 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VVVDR2 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VVVDR5 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VVVXDR1 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus Multiframe VVVv20110718 OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. {image primary HDU keyword: OBSTATUS} varchar 32   NONE ??
obStatus sharksMultiframe, ultravistaMultiframe, vhsMultiframe, videoMultiframe, vikingMultiframe, vmcMultiframe, vvvMultiframe VSAQC OB status, can be 'Completed', 'Executed' (which means it has to be repeated) or 'Aborted'. varchar 32   NONE ??
obsTime Detection PS1DR2 Modified Julian Date at the midpoint of the observation. float 8 days -999  
obsTplno MultiframeEsoKeys SHARKSv20210222 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys SHARKSv20210421 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys ULTRAVISTADR4 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VHSDR1 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VHSDR2 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VHSDR3 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VHSDR4 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VHSDR5 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VHSDR6 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VHSv20120926 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VHSv20130417 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VHSv20140409 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VHSv20150108 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VHSv20160114 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VHSv20160507 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VHSv20170630 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VHSv20180419 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VHSv20201209 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VHSv20231101 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VIDEODR2 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VIDEODR3 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VIDEODR4 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VIDEODR5 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VIDEOv20100513 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VIDEOv20111208 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VIKINGDR2 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VIKINGDR3 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VIKINGDR4 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VIKINGv20110714 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VIKINGv20111019 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VIKINGv20130417 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VIKINGv20140402 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VIKINGv20150421 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VIKINGv20151230 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VIKINGv20160406 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VIKINGv20161202 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VIKINGv20170715 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCDEEPv20230713 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCDR1 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCDR2 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCDR3 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCDR4 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCDR5 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20110816 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20110909 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20120126 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20121128 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20130304 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20130805 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20140428 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20140903 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20150309 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20151218 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20160311 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20160822 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20170109 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20170411 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20171101 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20180702 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20181120 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20191212 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20210708 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20230816 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VMCv20240226 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VSAQC Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VVVDR1 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VVVDR2 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VVVDR5 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VVVXDR1 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VVVv20100531 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obsTplno MultiframeEsoKeys VVVv20110718 Template number within OB {image primary HDU keyword: HIERARCH ESO OBS TPLNO} smallint 2   -9999  
obstype Multiframe SHARKSv20210222 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe SHARKSv20210421 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe ULTRAVISTADR4 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VHSDR1 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VHSDR2 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VHSDR3 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VHSDR4 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VHSDR5 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VHSDR6 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VHSv20120926 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VHSv20130417 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VHSv20140409 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VHSv20150108 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VHSv20160114 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VHSv20160507 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VHSv20170630 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VHSv20180419 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VHSv20201209 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VHSv20231101 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VIDEODR2 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VIDEODR3 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VIDEODR4 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VIDEODR5 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VIDEOv20100513 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VIDEOv20111208 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VIKINGDR2 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VIKINGDR3 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VIKINGDR4 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VIKINGv20110714 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VIKINGv20111019 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VIKINGv20130417 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VIKINGv20140402 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VIKINGv20150421 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VIKINGv20151230 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VIKINGv20160406 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VIKINGv20161202 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VIKINGv20170715 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCDEEPv20230713 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCDR1 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCDR2 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCDR3 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCDR4 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCDR5 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20110816 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20110909 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20120126 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20121128 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20130304 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20130805 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20140428 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20140903 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20150309 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20151218 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20160311 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20160822 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20170109 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20170411 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20171101 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20180702 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20181120 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20191212 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20210708 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20230816 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VMCv20240226 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VVVDR1 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VVVDR2 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VVVDR5 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VVVXDR1 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VVVv20100531 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype Multiframe VVVv20110718 Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) {image primary HDU keyword: HIERARCH ESO DPR TYPE} varchar 32   NONE  
obstype sharksMultiframe, ultravistaMultiframe, vhsMultiframe, videoMultiframe, vikingMultiframe, vmcMultiframe, vvvMultiframe VSAQC Type (BIAS|DARK|ARC|FLAT|OBJECT|SKY) varchar 32   NONE  
ocsDet1Imgname MultiframeEsoKeys SHARKSv20210222 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys SHARKSv20210421 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys ULTRAVISTADR4 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VHSDR1 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VHSDR2 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VHSDR3 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VHSDR4 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VHSDR5 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VHSDR6 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VHSv20120926 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VHSv20130417 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VHSv20140409 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VHSv20150108 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VHSv20160114 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VHSv20160507 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VHSv20170630 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VHSv20180419 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VHSv20201209 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VHSv20231101 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VIDEODR2 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VIDEODR3 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VIDEODR4 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VIDEODR5 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VIDEOv20100513 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VIDEOv20111208 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VIKINGDR2 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VIKINGDR3 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VIKINGDR4 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VIKINGv20110714 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VIKINGv20111019 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VIKINGv20130417 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VIKINGv20140402 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VIKINGv20150421 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VIKINGv20151230 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VIKINGv20160406 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VIKINGv20161202 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VIKINGv20170715 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCDEEPv20230713 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCDR1 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCDR2 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCDR3 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCDR4 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCDR5 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20110816 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20110909 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20120126 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20121128 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20130304 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20130805 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20140428 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20140903 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20150309 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20151218 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20160311 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20160822 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20170109 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20170411 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20171101 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20180702 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20181120 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20191212 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20210708 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20230816 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VMCv20240226 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VSAQC Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VVVDR1 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VVVDR2 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VVVDR5 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VVVXDR1 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VVVv20100531 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsDet1Imgname MultiframeEsoKeys VVVv20110718 Data File Name. {image primary HDU keyword: HIERARCH ESO OCS DET1 IMGNAME} varchar 16   NONE  
ocsExpno MultiframeEsoKeys SHARKSv20210222 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys SHARKSv20210421 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys ULTRAVISTADR4 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VHSDR1 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VHSDR2 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VHSDR3 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VHSDR4 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VHSDR5 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VHSDR6 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VHSv20120926 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VHSv20130417 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VHSv20140409 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VHSv20150108 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VHSv20160114 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VHSv20160507 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VHSv20170630 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VHSv20180419 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VHSv20201209 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VHSv20231101 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VIDEODR2 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VIDEODR3 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VIDEODR4 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VIDEODR5 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VIDEOv20100513 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VIDEOv20111208 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VIKINGDR2 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VIKINGDR3 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VIKINGDR4 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VIKINGv20110714 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VIKINGv20111019 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VIKINGv20130417 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VIKINGv20140402 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VIKINGv20150421 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VIKINGv20151230 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VIKINGv20160406 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VIKINGv20161202 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VIKINGv20170715 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCDEEPv20230713 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCDR1 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCDR2 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCDR3 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCDR4 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCDR5 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20110816 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20110909 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20120126 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20121128 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20130304 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20130805 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20140428 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20140903 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20150309 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20151218 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20160311 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20160822 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20170109 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20170411 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20171101 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20180702 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20181120 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20191212 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20210708 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20230816 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VMCv20240226 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VSAQC Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VVVDR1 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VVVDR2 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VVVDR5 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VVVXDR1 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VVVv20100531 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsExpno MultiframeEsoKeys VVVv20110718 Exposure number of dwell {image primary HDU keyword: HIERARCH ESO OCS EXPNO} smallint 2   -9999  
ocsNexp MultiframeEsoKeys SHARKSv20210222 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys SHARKSv20210421 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys ULTRAVISTADR4 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VHSDR1 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VHSDR2 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VHSDR3 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VHSDR4 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VHSDR5 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VHSDR6 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VHSv20120926 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VHSv20130417 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VHSv20140409 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VHSv20150108 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VHSv20160114 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VHSv20160507 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VHSv20170630 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VHSv20180419 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VHSv20201209 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VHSv20231101 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VIDEODR2 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VIDEODR3 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VIDEODR4 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VIDEODR5 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VIDEOv20100513 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VIDEOv20111208 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VIKINGDR2 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VIKINGDR3 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VIKINGDR4 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VIKINGv20110714 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VIKINGv20111019 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VIKINGv20130417 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VIKINGv20140402 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VIKINGv20150421 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VIKINGv20151230 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VIKINGv20160406 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VIKINGv20161202 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VIKINGv20170715 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCDEEPv20230713 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCDR1 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCDR2 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCDR3 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCDR4 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCDR5 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20110816 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20110909 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20120126 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20121128 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20130304 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20130805 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20140428 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20140903 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20150309 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20151218 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20160311 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20160822 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20170109 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20170411 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20171101 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20180702 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20181120 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20191212 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20210708 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20230816 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VMCv20240226 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VSAQC Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VVVDR1 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VVVDR2 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VVVDR5 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VVVXDR1 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VVVv20100531 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsNexp MultiframeEsoKeys VVVv20110718 Number of exposures per dwell {image primary HDU keyword: HIERARCH ESO OCS NEXP} smallint 2   -9999  
ocsRecipe MultiframeEsoKeys SHARKSv20210222 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys SHARKSv20210421 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys ULTRAVISTADR4 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VHSDR1 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VHSDR2 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VHSDR3 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VHSDR4 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VHSDR5 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VHSDR6 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VHSv20120926 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VHSv20130417 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VHSv20140409 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VHSv20150108 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VHSv20160114 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VHSv20160507 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VHSv20170630 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VHSv20180419 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VHSv20201209 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VHSv20231101 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VIDEODR2 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VIDEODR3 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VIDEODR4 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VIDEODR5 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VIDEOv20100513 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VIDEOv20111208 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VIKINGDR2 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VIKINGDR3 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VIKINGDR4 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VIKINGv20110714 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VIKINGv20111019 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VIKINGv20130417 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VIKINGv20140402 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VIKINGv20150421 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VIKINGv20151230 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VIKINGv20160406 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VIKINGv20161202 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VIKINGv20170715 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCDEEPv20230713 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCDR1 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCDR2 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCDR3 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCDR4 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCDR5 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20110816 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20110909 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20120126 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20121128 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20130304 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20130805 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20140428 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20140903 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20150309 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20151218 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20160311 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20160822 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20170109 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20170411 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20171101 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20180702 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20181120 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20191212 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20210708 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20230816 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VMCv20240226 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VSAQC Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VVVDR1 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VVVDR2 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VVVDR5 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VVVXDR1 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VVVv20100531 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsRecipe MultiframeEsoKeys VVVv20110718 Data reduction recipe to be used {image primary HDU keyword: HIERARCH ESO OCS RECIPE} varchar 8   NONE  
ocsReqtime MultiframeEsoKeys SHARKSv20210222 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys SHARKSv20210421 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys ULTRAVISTADR4 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VHSDR1 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VHSDR2 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VHSDR3 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VHSDR4 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VHSDR5 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VHSDR6 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VHSv20120926 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VHSv20130417 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VHSv20140409 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VHSv20150108 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VHSv20160114 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VHSv20160507 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VHSv20170630 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VHSv20180419 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VHSv20201209 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VHSv20231101 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VIDEODR2 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VIDEODR3 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VIDEODR4 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VIDEODR5 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VIDEOv20100513 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VIDEOv20111208 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VIKINGDR2 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VIKINGDR3 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VIKINGDR4 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VIKINGv20110714 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VIKINGv20111019 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VIKINGv20130417 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VIKINGv20140402 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VIKINGv20150421 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VIKINGv20151230 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VIKINGv20160406 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VIKINGv20161202 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VIKINGv20170715 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCDEEPv20230713 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCDR1 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCDR2 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCDR3 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCDR4 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCDR5 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20110816 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20110909 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20120126 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20121128 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20130304 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20130805 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20140428 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20140903 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20150309 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20151218 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20160311 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20160822 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20170109 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20170411 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20171101 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20180702 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20181120 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20191212 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20210708 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20230816 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VMCv20240226 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VSAQC Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VVVDR1 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VVVDR2 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VVVDR5 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VVVXDR1 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VVVv20100531 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsReqtime MultiframeEsoKeys VVVv20110718 Requested integration time [s] {image primary HDU keyword: HIERARCH ESO OCS REQTIME} float 8   -0.9999995e9  
ocsSadtAosa1ID MultiframeEsoKeys SHARKSv20210222 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys SHARKSv20210421 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys ULTRAVISTADR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VHSDR1 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VHSDR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VHSDR3 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VHSDR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VHSDR5 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VHSDR6 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VHSv20120926 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VHSv20130417 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VHSv20140409 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VHSv20150108 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VHSv20160114 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VHSv20160507 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VHSv20170630 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VHSv20180419 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VHSv20201209 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VHSv20231101 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VIDEODR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VIDEODR3 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VIDEODR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VIDEODR5 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VIDEOv20100513 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VIDEOv20111208 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VIKINGDR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VIKINGDR3 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VIKINGDR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VIKINGv20110714 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VIKINGv20111019 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VIKINGv20130417 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VIKINGv20140402 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VIKINGv20150421 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VIKINGv20151230 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VIKINGv20160406 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VIKINGv20161202 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VIKINGv20170715 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCDEEPv20230713 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCDR1 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCDR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCDR3 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCDR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCDR5 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20110816 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20110909 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20120126 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20121128 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20130304 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20130805 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20140428 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20140903 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20150309 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20151218 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20160311 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20160822 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20170109 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20170411 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20171101 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20180702 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20181120 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20191212 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20210708 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20230816 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VMCv20240226 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VSAQC AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VVVDR1 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VVVDR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VVVDR5 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VVVXDR1 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VVVv20100531 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa1ID MultiframeEsoKeys VVVv20110718 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA1 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys SHARKSv20210222 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys SHARKSv20210421 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys ULTRAVISTADR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VHSDR1 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VHSDR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VHSDR3 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VHSDR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VHSDR5 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VHSDR6 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VHSv20120926 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VHSv20130417 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VHSv20140409 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VHSv20150108 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VHSv20160114 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VHSv20160507 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VHSv20170630 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VHSv20180419 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VHSv20201209 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VHSv20231101 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VIDEODR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VIDEODR3 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VIDEODR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VIDEODR5 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VIDEOv20100513 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VIDEOv20111208 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VIKINGDR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VIKINGDR3 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VIKINGDR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VIKINGv20110714 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VIKINGv20111019 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VIKINGv20130417 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VIKINGv20140402 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VIKINGv20150421 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VIKINGv20151230 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VIKINGv20160406 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VIKINGv20161202 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VIKINGv20170715 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCDEEPv20230713 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCDR1 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCDR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCDR3 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCDR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCDR5 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20110816 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20110909 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20120126 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20121128 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20130304 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20130805 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20140428 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20140903 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20150309 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20151218 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20160311 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20160822 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20170109 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20170411 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20171101 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20180702 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20181120 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20191212 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20210708 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20230816 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VMCv20240226 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VSAQC AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VVVDR1 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VVVDR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VVVDR5 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VVVXDR1 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VVVv20100531 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa2ID MultiframeEsoKeys VVVv20110718 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA2 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys SHARKSv20210222 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys SHARKSv20210421 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys ULTRAVISTADR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VHSDR1 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VHSDR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VHSDR3 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VHSDR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VHSDR5 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VHSDR6 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VHSv20120926 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VHSv20130417 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VHSv20140409 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VHSv20150108 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VHSv20160114 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VHSv20160507 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VHSv20170630 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VHSv20180419 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VHSv20201209 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VHSv20231101 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VIDEODR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VIDEODR3 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VIDEODR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VIDEODR5 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VIDEOv20100513 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VIDEOv20111208 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VIKINGDR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VIKINGDR3 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VIKINGDR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VIKINGv20110714 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VIKINGv20111019 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VIKINGv20130417 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VIKINGv20140402 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VIKINGv20150421 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VIKINGv20151230 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VIKINGv20160406 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VIKINGv20161202 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VIKINGv20170715 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCDEEPv20230713 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCDR1 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCDR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCDR3 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCDR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCDR5 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20110816 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20110909 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20120126 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20121128 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20130304 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20130805 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20140428 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20140903 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20150309 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20151218 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20160311 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20160822 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20170109 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20170411 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20171101 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20180702 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20181120 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20191212 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20210708 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20230816 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VMCv20240226 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VSAQC AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VVVDR1 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VVVDR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VVVDR5 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VVVXDR1 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VVVv20100531 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa3ID MultiframeEsoKeys VVVv20110718 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA3 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys SHARKSv20210222 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys SHARKSv20210421 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys ULTRAVISTADR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VHSDR1 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VHSDR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VHSDR3 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VHSDR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VHSDR5 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VHSDR6 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VHSv20120926 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VHSv20130417 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VHSv20140409 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VHSv20150108 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VHSv20160114 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VHSv20160507 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VHSv20170630 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VHSv20180419 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VHSv20201209 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VHSv20231101 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VIDEODR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VIDEODR3 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VIDEODR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VIDEODR5 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VIDEOv20100513 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VIDEOv20111208 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VIKINGDR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VIKINGDR3 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VIKINGDR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VIKINGv20110714 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VIKINGv20111019 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VIKINGv20130417 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VIKINGv20140402 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VIKINGv20150421 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VIKINGv20151230 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VIKINGv20160406 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VIKINGv20161202 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VIKINGv20170715 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCDEEPv20230713 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCDR1 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCDR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCDR3 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCDR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCDR5 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20110816 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20110909 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20120126 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20121128 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20130304 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20130805 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20140428 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20140903 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20150309 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20151218 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20160311 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20160822 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20170109 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20170411 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20171101 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20180702 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20181120 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20191212 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20210708 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20230816 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VMCv20240226 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VSAQC AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VVVDR1 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VVVDR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VVVDR5 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VVVXDR1 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VVVv20100531 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa4ID MultiframeEsoKeys VVVv20110718 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA4 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys SHARKSv20210222 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys SHARKSv20210421 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys ULTRAVISTADR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VHSDR1 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VHSDR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VHSDR3 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VHSDR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VHSDR5 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VHSDR6 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VHSv20120926 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VHSv20130417 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VHSv20140409 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VHSv20150108 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VHSv20160114 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VHSv20160507 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VHSv20170630 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VHSv20180419 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VHSv20201209 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VHSv20231101 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VIDEODR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VIDEODR3 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VIDEODR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VIDEODR5 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VIDEOv20100513 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VIDEOv20111208 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VIKINGDR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VIKINGDR3 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VIKINGDR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VIKINGv20110714 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VIKINGv20111019 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VIKINGv20130417 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VIKINGv20140402 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VIKINGv20150421 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VIKINGv20151230 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VIKINGv20160406 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VIKINGv20161202 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VIKINGv20170715 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCDEEPv20230713 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCDR1 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCDR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCDR3 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCDR4 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCDR5 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20110816 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20110909 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20120126 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20121128 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20130304 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20130805 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20140428 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20140903 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20150309 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20151218 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20160311 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20160822 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20170109 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20170411 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20171101 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20180702 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20181120 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20191212 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20210708 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20230816 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VMCv20240226 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VSAQC AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VVVDR1 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VVVDR2 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VVVDR5 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VVVXDR1 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VVVv20100531 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosa5ID MultiframeEsoKeys VVVv20110718 AO star A ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSA5 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys SHARKSv20210222 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys SHARKSv20210421 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys ULTRAVISTADR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VHSDR1 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VHSDR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VHSDR3 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VHSDR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VHSDR5 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VHSDR6 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VHSv20120926 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VHSv20130417 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VHSv20140409 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VHSv20150108 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VHSv20160114 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VHSv20160507 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VHSv20170630 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VHSv20180419 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VHSv20201209 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VHSv20231101 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VIDEODR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VIDEODR3 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VIDEODR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VIDEODR5 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VIDEOv20100513 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VIDEOv20111208 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VIKINGDR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VIKINGDR3 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VIKINGDR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VIKINGv20110714 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VIKINGv20111019 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VIKINGv20130417 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VIKINGv20140402 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VIKINGv20150421 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VIKINGv20151230 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VIKINGv20160406 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VIKINGv20161202 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VIKINGv20170715 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCDEEPv20230713 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCDR1 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCDR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCDR3 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCDR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCDR5 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20110816 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20110909 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20120126 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20121128 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20130304 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20130805 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20140428 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20140903 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20150309 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20151218 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20160311 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20160822 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20170109 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20170411 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20171101 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20180702 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20181120 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20191212 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20210708 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20230816 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VMCv20240226 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VSAQC AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VVVDR1 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VVVDR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VVVDR5 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VVVXDR1 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VVVv20100531 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb1ID MultiframeEsoKeys VVVv20110718 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB1 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys SHARKSv20210222 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys SHARKSv20210421 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys ULTRAVISTADR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VHSDR1 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VHSDR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VHSDR3 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VHSDR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VHSDR5 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VHSDR6 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VHSv20120926 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VHSv20130417 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VHSv20140409 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VHSv20150108 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VHSv20160114 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VHSv20160507 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VHSv20170630 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VHSv20180419 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VHSv20201209 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VHSv20231101 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VIDEODR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VIDEODR3 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VIDEODR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VIDEODR5 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VIDEOv20100513 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VIDEOv20111208 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VIKINGDR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VIKINGDR3 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VIKINGDR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VIKINGv20110714 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VIKINGv20111019 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VIKINGv20130417 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VIKINGv20140402 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VIKINGv20150421 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VIKINGv20151230 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VIKINGv20160406 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VIKINGv20161202 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VIKINGv20170715 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCDEEPv20230713 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCDR1 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCDR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCDR3 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCDR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCDR5 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20110816 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20110909 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20120126 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20121128 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20130304 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20130805 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20140428 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20140903 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20150309 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20151218 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20160311 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20160822 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20170109 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20170411 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20171101 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20180702 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20181120 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20191212 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20210708 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20230816 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VMCv20240226 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VSAQC AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VVVDR1 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VVVDR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VVVDR5 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VVVXDR1 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VVVv20100531 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb2ID MultiframeEsoKeys VVVv20110718 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB2 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys SHARKSv20210222 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys SHARKSv20210421 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys ULTRAVISTADR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VHSDR1 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VHSDR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VHSDR3 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VHSDR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VHSDR5 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VHSDR6 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VHSv20120926 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VHSv20130417 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VHSv20140409 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VHSv20150108 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VHSv20160114 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VHSv20160507 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VHSv20170630 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VHSv20180419 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VHSv20201209 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VHSv20231101 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VIDEODR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VIDEODR3 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VIDEODR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VIDEODR5 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VIDEOv20100513 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VIDEOv20111208 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VIKINGDR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VIKINGDR3 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VIKINGDR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VIKINGv20110714 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VIKINGv20111019 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VIKINGv20130417 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VIKINGv20140402 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VIKINGv20150421 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VIKINGv20151230 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VIKINGv20160406 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VIKINGv20161202 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VIKINGv20170715 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCDEEPv20230713 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCDR1 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCDR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCDR3 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCDR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCDR5 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20110816 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20110909 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20120126 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20121128 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20130304 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20130805 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20140428 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20140903 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20150309 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20151218 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20160311 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20160822 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20170109 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20170411 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20171101 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20180702 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20181120 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20191212 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20210708 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20230816 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VMCv20240226 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VSAQC AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VVVDR1 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VVVDR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VVVDR5 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VVVXDR1 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VVVv20100531 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb3ID MultiframeEsoKeys VVVv20110718 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB3 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys SHARKSv20210222 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys SHARKSv20210421 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys ULTRAVISTADR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VHSDR1 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VHSDR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VHSDR3 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VHSDR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VHSDR5 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VHSDR6 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VHSv20120926 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VHSv20130417 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VHSv20140409 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VHSv20150108 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VHSv20160114 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VHSv20160507 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VHSv20170630 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VHSv20180419 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VHSv20201209 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VHSv20231101 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VIDEODR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VIDEODR3 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VIDEODR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VIDEODR5 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VIDEOv20100513 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VIDEOv20111208 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VIKINGDR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VIKINGDR3 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VIKINGDR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VIKINGv20110714 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VIKINGv20111019 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VIKINGv20130417 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VIKINGv20140402 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VIKINGv20150421 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VIKINGv20151230 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VIKINGv20160406 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VIKINGv20161202 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VIKINGv20170715 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCDEEPv20230713 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCDR1 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCDR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCDR3 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCDR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCDR5 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20110816 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20110909 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20120126 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20121128 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20130304 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20130805 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20140428 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20140903 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20150309 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20151218 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20160311 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20160822 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20170109 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20170411 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20171101 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20180702 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20181120 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20191212 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20210708 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20230816 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VMCv20240226 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VSAQC AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VVVDR1 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VVVDR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VVVDR5 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VVVXDR1 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VVVv20100531 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb4ID MultiframeEsoKeys VVVv20110718 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB4 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys SHARKSv20210222 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys SHARKSv20210421 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys ULTRAVISTADR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VHSDR1 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VHSDR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VHSDR3 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VHSDR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VHSDR5 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VHSDR6 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VHSv20120926 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VHSv20130417 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VHSv20140409 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VHSv20150108 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VHSv20160114 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VHSv20160507 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VHSv20170630 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VHSv20180419 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VHSv20201209 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VHSv20231101 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VIDEODR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VIDEODR3 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VIDEODR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VIDEODR5 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VIDEOv20100513 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VIDEOv20111208 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VIKINGDR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VIKINGDR3 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VIKINGDR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VIKINGv20110714 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VIKINGv20111019 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VIKINGv20130417 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VIKINGv20140402 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VIKINGv20150421 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VIKINGv20151230 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VIKINGv20160406 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VIKINGv20161202 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VIKINGv20170715 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCDEEPv20230713 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCDR1 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCDR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCDR3 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCDR4 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCDR5 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20110816 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20110909 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20120126 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20121128 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20130304 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20130805 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20140428 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20140903 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20150309 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20151218 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20160311 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20160822 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20170109 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20170411 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20171101 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20180702 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20181120 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20191212 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20210708 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20230816 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VMCv20240226 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VSAQC AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VVVDR1 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VVVDR2 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VVVDR5 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VVVXDR1 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VVVv20100531 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtAosb5ID MultiframeEsoKeys VVVv20110718 AO star B ID {image primary HDU keyword: HIERARCH ESO OCS SADT AOSB5 ID} varchar 16   NONE  
ocsSadtCatID MultiframeEsoKeys SHARKSv20210222 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys SHARKSv20210421 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys ULTRAVISTADR4 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VHSDR1 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VHSDR2 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VHSDR3 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VHSDR4 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VHSDR5 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VHSDR6 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VHSv20120926 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VHSv20130417 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VHSv20140409 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VHSv20150108 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VHSv20160114 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VHSv20160507 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VHSv20170630 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VHSv20180419 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VHSv20201209 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VHSv20231101 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VIDEODR2 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VIDEODR3 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VIDEODR4 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VIDEODR5 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VIDEOv20100513 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VIDEOv20111208 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VIKINGDR2 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VIKINGDR3 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VIKINGDR4 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VIKINGv20110714 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VIKINGv20111019 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VIKINGv20130417 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VIKINGv20140402 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VIKINGv20150421 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VIKINGv20151230 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VIKINGv20160406 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VIKINGv20161202 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VIKINGv20170715 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCDEEPv20230713 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCDR1 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCDR2 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCDR3 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCDR4 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCDR5 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20110816 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20110909 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20120126 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20121128 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20130304 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20130805 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20140428 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20140903 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20150309 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20151218 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20160311 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20160822 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20170109 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20170411 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20171101 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20180702 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20181120 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20191212 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20210708 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20230816 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VMCv20240226 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VSAQC Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VVVDR1 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VVVDR2 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VVVDR5 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VVVXDR1 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VVVv20100531 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtCatID MultiframeEsoKeys VVVv20110718 Guide star catalogue used {image primary HDU keyword: HIERARCH ESO OCS SADT CAT ID} varchar 32   NONE  
ocsSadtGs1ID MultiframeEsoKeys SHARKSv20210222 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys SHARKSv20210421 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys ULTRAVISTADR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VHSDR1 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VHSDR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VHSDR3 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VHSDR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VHSDR5 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VHSDR6 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VHSv20120926 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VHSv20130417 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VHSv20140409 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VHSv20150108 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VHSv20160114 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VHSv20160507 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VHSv20170630 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VHSv20180419 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VHSv20201209 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VHSv20231101 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VIDEODR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VIDEODR3 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VIDEODR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VIDEODR5 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VIDEOv20100513 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VIDEOv20111208 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VIKINGDR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VIKINGDR3 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VIKINGDR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VIKINGv20110714 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VIKINGv20111019 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VIKINGv20130417 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VIKINGv20140402 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VIKINGv20150421 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VIKINGv20151230 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VIKINGv20160406 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VIKINGv20161202 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VIKINGv20170715 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCDEEPv20230713 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCDR1 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCDR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCDR3 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCDR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCDR5 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20110816 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20110909 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20120126 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20121128 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20130304 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20130805 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20140428 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20140903 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20150309 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20151218 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20160311 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20160822 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20170109 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20170411 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20171101 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20180702 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20181120 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20191212 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20210708 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20230816 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VMCv20240226 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VSAQC Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VVVDR1 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VVVDR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VVVDR5 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VVVXDR1 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VVVv20100531 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs1ID MultiframeEsoKeys VVVv20110718 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS1 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys SHARKSv20210222 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys SHARKSv20210421 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys ULTRAVISTADR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VHSDR1 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VHSDR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VHSDR3 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VHSDR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VHSDR5 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VHSDR6 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VHSv20120926 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VHSv20130417 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VHSv20140409 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VHSv20150108 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VHSv20160114 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VHSv20160507 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VHSv20170630 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VHSv20180419 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VHSv20201209 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VHSv20231101 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VIDEODR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VIDEODR3 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VIDEODR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VIDEODR5 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VIDEOv20100513 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VIDEOv20111208 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VIKINGDR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VIKINGDR3 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VIKINGDR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VIKINGv20110714 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VIKINGv20111019 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VIKINGv20130417 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VIKINGv20140402 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VIKINGv20150421 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VIKINGv20151230 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VIKINGv20160406 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VIKINGv20161202 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VIKINGv20170715 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCDEEPv20230713 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCDR1 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCDR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCDR3 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCDR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCDR5 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20110816 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20110909 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20120126 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20121128 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20130304 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20130805 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20140428 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20140903 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20150309 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20151218 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20160311 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20160822 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20170109 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20170411 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20171101 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20180702 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20181120 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20191212 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20210708 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20230816 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VMCv20240226 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VSAQC Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VVVDR1 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VVVDR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VVVDR5 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VVVXDR1 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VVVv20100531 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs2ID MultiframeEsoKeys VVVv20110718 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS2 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys SHARKSv20210222 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys SHARKSv20210421 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys ULTRAVISTADR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VHSDR1 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VHSDR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VHSDR3 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VHSDR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VHSDR5 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VHSDR6 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VHSv20120926 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VHSv20130417 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VHSv20140409 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VHSv20150108 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VHSv20160114 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VHSv20160507 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VHSv20170630 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VHSv20180419 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VHSv20201209 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VHSv20231101 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VIDEODR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VIDEODR3 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VIDEODR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VIDEODR5 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VIDEOv20100513 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VIDEOv20111208 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VIKINGDR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VIKINGDR3 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VIKINGDR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VIKINGv20110714 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VIKINGv20111019 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VIKINGv20130417 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VIKINGv20140402 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VIKINGv20150421 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VIKINGv20151230 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VIKINGv20160406 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VIKINGv20161202 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VIKINGv20170715 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCDEEPv20230713 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCDR1 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCDR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCDR3 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCDR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCDR5 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20110816 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20110909 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20120126 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20121128 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20130304 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20130805 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20140428 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20140903 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20150309 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20151218 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20160311 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20160822 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20170109 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20170411 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20171101 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20180702 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20181120 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20191212 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20210708 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20230816 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VMCv20240226 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VSAQC Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VVVDR1 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VVVDR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VVVDR5 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VVVXDR1 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VVVv20100531 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs3ID MultiframeEsoKeys VVVv20110718 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS3 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys SHARKSv20210222 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys SHARKSv20210421 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys ULTRAVISTADR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VHSDR1 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VHSDR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VHSDR3 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VHSDR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VHSDR5 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VHSDR6 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VHSv20120926 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VHSv20130417 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VHSv20140409 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VHSv20150108 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VHSv20160114 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VHSv20160507 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VHSv20170630 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VHSv20180419 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VHSv20201209 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VHSv20231101 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VIDEODR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VIDEODR3 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VIDEODR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VIDEODR5 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VIDEOv20100513 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VIDEOv20111208 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VIKINGDR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VIKINGDR3 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VIKINGDR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VIKINGv20110714 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VIKINGv20111019 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VIKINGv20130417 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VIKINGv20140402 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VIKINGv20150421 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VIKINGv20151230 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VIKINGv20160406 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VIKINGv20161202 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VIKINGv20170715 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCDEEPv20230713 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCDR1 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCDR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCDR3 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCDR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCDR5 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20110816 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20110909 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20120126 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20121128 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20130304 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20130805 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20140428 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20140903 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20150309 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20151218 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20160311 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20160822 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20170109 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20170411 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20171101 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20180702 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20181120 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20191212 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20210708 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20230816 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VMCv20240226 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VSAQC Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VVVDR1 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VVVDR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VVVDR5 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VVVXDR1 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VVVv20100531 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs4ID MultiframeEsoKeys VVVv20110718 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS4 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys SHARKSv20210222 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys SHARKSv20210421 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys ULTRAVISTADR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VHSDR1 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VHSDR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VHSDR3 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VHSDR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VHSDR5 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VHSDR6 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VHSv20120926 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VHSv20130417 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VHSv20140409 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VHSv20150108 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VHSv20160114 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VHSv20160507 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VHSv20170630 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VHSv20180419 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VHSv20201209 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VHSv20231101 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VIDEODR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VIDEODR3 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VIDEODR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VIDEODR5 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VIDEOv20100513 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VIDEOv20111208 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VIKINGDR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VIKINGDR3 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VIKINGDR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VIKINGv20110714 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VIKINGv20111019 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VIKINGv20130417 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VIKINGv20140402 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VIKINGv20150421 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VIKINGv20151230 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VIKINGv20160406 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VIKINGv20161202 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VIKINGv20170715 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCDEEPv20230713 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCDR1 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCDR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCDR3 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCDR4 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCDR5 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20110816 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20110909 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20120126 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20121128 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20130304 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20130805 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20140428 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20140903 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20150309 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20151218 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20160311 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20160822 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20170109 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20170411 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20171101 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20180702 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20181120 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20191212 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20210708 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20230816 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VMCv20240226 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VSAQC Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VVVDR1 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VVVDR2 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VVVDR5 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VVVXDR1 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VVVv20100531 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtGs5ID MultiframeEsoKeys VVVv20110718 Guide star ID {image primary HDU keyword: HIERARCH ESO OCS SADT GS5 ID} varchar 16   NONE  
ocsSadtIpID MultiframeEsoKeys SHARKSv20210222 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys SHARKSv20210421 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys ULTRAVISTADR4 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VHSDR1 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VHSDR2 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VHSDR3 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VHSDR4 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VHSDR5 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VHSDR6 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VHSv20120926 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VHSv20130417 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VHSv20140409 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VHSv20150108 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VHSv20160114 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VHSv20160507 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VHSv20170630 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VHSv20180419 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VHSv20201209 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VHSv20231101 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VIDEODR2 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VIDEODR3 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VIDEODR4 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VIDEODR5 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VIDEOv20100513 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VIDEOv20111208 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VIKINGDR2 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VIKINGDR3 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VIKINGDR4 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VIKINGv20110714 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VIKINGv20111019 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VIKINGv20130417 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VIKINGv20140402 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VIKINGv20150421 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VIKINGv20151230 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VIKINGv20160406 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VIKINGv20161202 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VIKINGv20170715 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCDEEPv20230713 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCDR1 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCDR2 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCDR3 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCDR4 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCDR5 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20110816 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20110909 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20120126 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20121128 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20130304 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20130805 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20140428 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20140903 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20150309 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20151218 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20160311 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20160822 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20170109 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20170411 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20171101 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20180702 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20181120 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20191212 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20210708 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20230816 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VMCv20240226 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VSAQC Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VVVDR1 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VVVDR2 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VVVDR5 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VVVXDR1 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VVVv20100531 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsSadtIpID MultiframeEsoKeys VVVv20110718 Creator software ve {image primary HDU keyword: HIERARCH ESO OCS SADT IP ID} varchar 32   NONE  
ocsTargAlphaobj MultiframeEsoKeys SHARKSv20210222 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys SHARKSv20210421 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys ULTRAVISTADR4 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VHSDR1 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VHSDR2 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VHSDR3 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VHSDR4 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VHSDR5 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VHSDR6 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VHSv20120926 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VHSv20130417 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VHSv20140409 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VHSv20150108 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VHSv20160114 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VHSv20160507 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VHSv20170630 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VHSv20180419 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VHSv20201209 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VHSv20231101 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VIDEODR2 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VIDEODR3 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VIDEODR4 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VIDEODR5 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VIDEOv20100513 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VIDEOv20111208 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VIKINGDR2 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VIKINGDR3 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VIKINGDR4 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VIKINGv20110714 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VIKINGv20111019 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VIKINGv20130417 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VIKINGv20140402 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VIKINGv20150421 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VIKINGv20151230 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VIKINGv20160406 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VIKINGv20161202 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VIKINGv20170715 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCDEEPv20230713 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCDR1 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCDR2 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCDR3 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCDR4 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCDR5 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20110816 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20110909 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20120126 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20121128 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20130304 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20130805 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20140428 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20140903 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20150309 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20151218 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20160311 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20160822 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20170109 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20170411 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20171101 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20180702 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20181120 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20191212 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20210708 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20230816 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VMCv20240226 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VSAQC RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VVVDR1 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VVVDR2 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VVVDR5 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VVVXDR1 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VVVv20100531 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargAlphaobj MultiframeEsoKeys VVVv20110718 RA of target object [HHMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG ALPHAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys SHARKSv20210222 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys SHARKSv20210421 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys ULTRAVISTADR4 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VHSDR1 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VHSDR2 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VHSDR3 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VHSDR4 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VHSDR5 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VHSDR6 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VHSv20120926 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VHSv20130417 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VHSv20140409 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VHSv20150108 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VHSv20160114 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VHSv20160507 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VHSv20170630 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VHSv20180419 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VHSv20201209 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VHSv20231101 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VIDEODR2 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VIDEODR3 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VIDEODR4 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VIDEODR5 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VIDEOv20100513 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VIDEOv20111208 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VIKINGDR2 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VIKINGDR3 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VIKINGDR4 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VIKINGv20110714 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VIKINGv20111019 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VIKINGv20130417 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VIKINGv20140402 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VIKINGv20150421 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VIKINGv20151230 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VIKINGv20160406 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VIKINGv20161202 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VIKINGv20170715 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCDEEPv20230713 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCDR1 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCDR2 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCDR3 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCDR4 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCDR5 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20110816 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20110909 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20120126 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20121128 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20130304 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20130805 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20140428 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20140903 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20150309 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20151218 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20160311 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20160822 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20170109 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20170411 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20171101 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20180702 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20181120 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20191212 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20210708 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20230816 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VMCv20240226 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VSAQC Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VVVDR1 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VVVDR2 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VVVDR5 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VVVXDR1 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VVVv20100531 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargDeltaobj MultiframeEsoKeys VVVv20110718 Dec of target object [DDMMSS.TTT] {image primary HDU keyword: HIERARCH ESO OCS TARG DELTAOBJ} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys SHARKSv20210222 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys SHARKSv20210421 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys ULTRAVISTADR4 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VHSDR1 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VHSDR2 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VHSDR3 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VHSDR4 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VHSDR5 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VHSDR6 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VHSv20120926 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VHSv20130417 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VHSv20140409 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VHSv20150108 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VHSv20160114 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VHSv20160507 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VHSv20170630 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VHSv20180419 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VHSv20201209 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VHSv20231101 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VIDEODR2 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VIDEODR3 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VIDEODR4 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VIDEODR5 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VIDEOv20100513 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VIDEOv20111208 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VIKINGDR2 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VIKINGDR3 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VIKINGDR4 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VIKINGv20110714 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VIKINGv20111019 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VIKINGv20130417 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VIKINGv20140402 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VIKINGv20150421 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VIKINGv20151230 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VIKINGv20160406 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VIKINGv20161202 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VIKINGv20170715 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCDEEPv20230713 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCDR1 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCDR2 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCDR3 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCDR4 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCDR5 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20110816 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20110909 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20120126 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20121128 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20130304 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20130805 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20140428 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20140903 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20150309 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20151218 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20160311 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20160822 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20170109 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20170411 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20171101 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20180702 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20181120 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20191212 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20210708 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20230816 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VMCv20240226 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VSAQC Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VVVDR1 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VVVDR2 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VVVDR5 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VVVXDR1 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VVVv20100531 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargX MultiframeEsoKeys VVVv20110718 Pointing origin X coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG X} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys SHARKSv20210222 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys SHARKSv20210421 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys ULTRAVISTADR4 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VHSDR1 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VHSDR2 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VHSDR3 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VHSDR4 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VHSDR5 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VHSDR6 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VHSv20120926 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VHSv20130417 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VHSv20140409 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VHSv20150108 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VHSv20160114 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VHSv20160507 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VHSv20170630 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VHSv20180419 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VHSv20201209 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VHSv20231101 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VIDEODR2 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VIDEODR3 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VIDEODR4 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VIDEODR5 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VIDEOv20100513 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VIDEOv20111208 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VIKINGDR2 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VIKINGDR3 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VIKINGDR4 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VIKINGv20110714 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VIKINGv20111019 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VIKINGv20130417 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VIKINGv20140402 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VIKINGv20150421 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VIKINGv20151230 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VIKINGv20160406 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VIKINGv20161202 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VIKINGv20170715 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCDEEPv20230713 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCDR1 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCDR2 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCDR3 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCDR4 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCDR5 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20110816 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20110909 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20120126 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20121128 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20130304 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20130805 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20140428 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20140903 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20150309 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20151218 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20160311 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20160822 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20170109 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20170411 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20171101 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20180702 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20181120 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20191212 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20210708 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20230816 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VMCv20240226 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VSAQC Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VVVDR1 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VVVDR2 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VVVDR5 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VVVXDR1 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VVVv20100531 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
ocsTargY MultiframeEsoKeys VVVv20110718 Pointing origin Y coord [mm] {image primary HDU keyword: HIERARCH ESO OCS TARG Y} float 8   -0.9999995e9  
offset mcps_lmcSource, mcps_smcSource MCPS MCPS/2MASS astrometric offset real 4 arcseconds    
offsetID Multiframe SHARKSv20210222 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe SHARKSv20210421 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe ULTRAVISTADR4 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VHSDR1 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VHSDR2 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VHSDR3 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VHSDR4 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VHSDR5 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VHSDR6 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VHSv20120926 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VHSv20130417 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VHSv20140409 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VHSv20150108 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VHSv20160114 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VHSv20160507 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VHSv20170630 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VHSv20180419 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VHSv20201209 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VHSv20231101 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VIDEODR2 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VIDEODR3 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VIDEODR4 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VIDEODR5 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VIDEOv20100513 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VIDEOv20111208 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VIKINGDR2 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VIKINGDR3 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VIKINGDR4 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VIKINGv20110714 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VIKINGv20111019 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VIKINGv20130417 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VIKINGv20140402 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VIKINGv20150421 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VIKINGv20151230 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VIKINGv20160406 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VIKINGv20161202 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VIKINGv20170715 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCDEEPv20230713 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCDR1 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCDR2 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCDR3 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCDR4 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCDR5 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20110816 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20110909 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20120126 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20121128 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20130304 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20130805 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20140428 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20140903 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20150309 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20151218 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20160311 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20160822 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20170109 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20170411 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20171101 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20180702 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20181120 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20191212 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20210708 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20230816 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VMCv20240226 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VVVDR1 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VVVDR2 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VVVDR5 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VVVXDR1 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VVVv20100531 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID Multiframe VVVv20110718 Sequence number of offset {image primary HDU keyword: OFFSET_I} smallint 2   -9999  
offsetID sharksMultiframe, ultravistaMultiframe, vhsMultiframe, videoMultiframe, vikingMultiframe, vmcMultiframe, vvvMultiframe VSAQC Sequence number of offset smallint 2   -9999  
offsetName Multiframe SHARKSv20210222 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe SHARKSv20210421 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe ULTRAVISTADR4 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VHSDR1 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VHSDR2 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VHSDR3 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VHSDR4 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VHSDR5 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VHSDR6 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VHSv20120926 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VHSv20130417 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VHSv20140409 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VHSv20150108 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VHSv20160114 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VHSv20160507 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VHSv20170630 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VHSv20180419 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VHSv20201209 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VHSv20231101 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VIDEODR2 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VIDEODR3 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VIDEODR4 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VIDEODR5 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VIDEOv20100513 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VIDEOv20111208 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VIKINGDR2 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VIKINGDR3 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VIKINGDR4 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VIKINGv20110714 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VIKINGv20111019 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VIKINGv20130417 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VIKINGv20140402 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VIKINGv20150421 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VIKINGv20151230 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VIKINGv20160406 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VIKINGv20161202 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VIKINGv20170715 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCDEEPv20230713 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCDR1 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCDR2 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCDR3 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCDR4 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCDR5 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20110816 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20110909 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20120126 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20121128 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20130304 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20130805 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20140428 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20140903 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20150309 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20151218 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20160311 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20160822 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20170109 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20170411 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20171101 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20180702 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20181120 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20191212 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20210708 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20230816 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VMCv20240226 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VVVDR1 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VVVDR2 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VVVDR5 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VVVXDR1 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VVVv20100531 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName Multiframe VVVv20110718 Name of offset pattern {image primary HDU keyword: OFFST_ID} varchar 8   NONE  
offsetName sharksMultiframe, ultravistaMultiframe, vhsMultiframe, videoMultiframe, vikingMultiframe, vmcMultiframe, vvvMultiframe VSAQC Name of offset pattern varchar 8   NONE  
offSetNum Multiframe SHARKSv20210222 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe SHARKSv20210421 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe ULTRAVISTADR4 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VHSDR1 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VHSDR2 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VHSDR3 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VHSDR4 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VHSDR5 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VHSDR6 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VHSv20120926 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VHSv20130417 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VHSv20140409 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VHSv20150108 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VHSv20160114 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VHSv20160507 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VHSv20170630 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VHSv20180419 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VHSv20201209 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VHSv20231101 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VIDEODR2 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VIDEODR3 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VIDEODR4 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VIDEODR5 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VIDEOv20100513 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VIDEOv20111208 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VIKINGDR2 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VIKINGDR3 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VIKINGDR4 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VIKINGv20110714 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VIKINGv20111019 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VIKINGv20130417 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VIKINGv20140402 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VIKINGv20150421 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VIKINGv20151230 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VIKINGv20160406 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VIKINGv20161202 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VIKINGv20170715 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCDEEPv20230713 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCDR1 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCDR2 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCDR3 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCDR4 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCDR5 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20110816 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20110909 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20120126 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20121128 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20130304 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20130805 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20140428 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20140903 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20150309 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20151218 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20160311 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20160822 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20170109 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20170411 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20171101 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20180702 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20181120 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20191212 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20210708 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20230816 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VMCv20240226 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VVVDR1 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VVVDR2 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VVVDR5 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VVVXDR1 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VVVv20100531 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum Multiframe VVVv20110718 First OBSNUM in offset sequence {image primary HDU keyword: OFFSTNUM} int 4   -99999999  
offSetNum sharksMultiframe, ultravistaMultiframe, vhsMultiframe, videoMultiframe, vikingMultiframe, vmcMultiframe, vvvMultiframe VSAQC First OBSNUM in offset sequence int 4   -99999999  
offsetPos RequiredStack SHARKSv20210222 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack SHARKSv20210421 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack ULTRAVISTADR4 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VHSDR1 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VHSDR2 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VHSDR3 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VHSDR4 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VHSDR5 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VHSDR6 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VHSv20120926 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VHSv20130417 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VHSv20150108 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VHSv20160114 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VHSv20160507 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VHSv20170630 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VHSv20180419 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VHSv20201209 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VHSv20231101 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VIDEODR2 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VIDEODR3 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VIDEODR4 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VIDEODR5 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VIDEOv20100513 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VIDEOv20111208 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VIKINGDR2 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VIKINGDR3 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VIKINGDR4 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VIKINGv20110714 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VIKINGv20111019 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VIKINGv20130417 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VIKINGv20150421 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VIKINGv20151230 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VIKINGv20160406 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VIKINGv20161202 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VIKINGv20170715 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCDEEPv20230713 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCDR1 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCDR3 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCDR4 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCDR5 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20110816 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20110909 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20120126 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20121128 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20130304 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20130805 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20140428 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20140903 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20150309 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20151218 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20160311 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20160822 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20170109 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20170411 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20171101 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20180702 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20181120 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20191212 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20210708 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20230816 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VMCv20240226 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VSAQC Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VVVDR1 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VVVDR2 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VVVDR5 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VVVXDR1 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VVVv20100531 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetPos RequiredStack VVVv20110718 Identity of offset position [1: -1,-1;2: -1,0; 3: -1,1; 4: 1,-1; 5: 1,0; 6: 1,1] tinyint 1   -9999  
offsetX Multiframe SHARKSv20210222 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe SHARKSv20210421 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe ULTRAVISTADR4 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VHSDR1 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VHSDR2 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VHSDR3 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VHSDR4 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VHSDR5 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VHSDR6 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VHSv20120926 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VHSv20130417 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VHSv20140409 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VHSv20150108 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VHSv20160114 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VHSv20160507 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VHSv20170630 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VHSv20180419 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VHSv20201209 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VHSv20231101 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VIDEODR2 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VIDEODR3 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VIDEODR4 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VIDEODR5 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VIDEOv20100513 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VIDEOv20111208 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VIKINGDR2 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VIKINGDR3 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VIKINGDR4 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VIKINGv20110714 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VIKINGv20111019 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VIKINGv20130417 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VIKINGv20140402 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VIKINGv20150421 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VIKINGv20151230 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VIKINGv20160406 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VIKINGv20161202 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VIKINGv20170715 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCDEEPv20230713 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCDR1 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCDR2 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCDR3 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCDR4 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCDR5 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20110816 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20110909 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20120126 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20121128 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20130304 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20130805 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20140428 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20140903 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20150309 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20151218 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20160311 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20160822 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20170109 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20170411 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20171101 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20180702 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20181120 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20191212 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20210708 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20230816 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VMCv20240226 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VVVDR1 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VVVDR2 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VVVDR5 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VVVXDR1 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VVVv20100531 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX Multiframe VVVv20110718 X offset [arcsec] {image primary HDU keyword: OFFSET_X} real 4   -0.9999995e9  
offsetX sharksMultiframe, ultravistaMultiframe, vhsMultiframe, videoMultiframe, vikingMultiframe, vmcMultiframe, vvvMultiframe VSAQC X offset [arcsec] real 4   -0.9999995e9  
offsetY Multiframe SHARKSv20210222 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe SHARKSv20210421 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe ULTRAVISTADR4 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VHSDR1 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VHSDR2 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VHSDR3 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VHSDR4 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VHSDR5 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VHSDR6 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VHSv20120926 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VHSv20130417 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VHSv20140409 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VHSv20150108 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VHSv20160114 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VHSv20160507 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VHSv20170630 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VHSv20180419 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VHSv20201209 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VHSv20231101 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VIDEODR2 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VIDEODR3 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VIDEODR4 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VIDEODR5 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VIDEOv20100513 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VIDEOv20111208 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VIKINGDR2 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VIKINGDR3 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VIKINGDR4 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VIKINGv20110714 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VIKINGv20111019 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VIKINGv20130417 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VIKINGv20140402 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VIKINGv20150421 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VIKINGv20151230 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VIKINGv20160406 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VIKINGv20161202 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VIKINGv20170715 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCDEEPv20230713 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCDR1 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCDR2 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCDR3 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCDR4 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCDR5 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20110816 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20110909 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20120126 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20121128 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20130304 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20130805 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20140428 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20140903 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20150309 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20151218 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20160311 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20160822 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20170109 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20170411 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20171101 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20180702 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20181120 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20191212 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20210708 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20230816 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VMCv20240226 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VVVDR1 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VVVDR2 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VVVDR5 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VVVXDR1 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VVVv20100531 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY Multiframe VVVv20110718 Y offset [arcsec] {image primary HDU keyword: OFFSET_Y} real 4   -0.9999995e9  
offsetY sharksMultiframe, ultravistaMultiframe, vhsMultiframe, videoMultiframe, vikingMultiframe, vmcMultiframe, vvvMultiframe VSAQC Y offset [arcsec] real 4   -0.9999995e9  
ogle2ID ogle3LpvLmcSource, ogle3LpvSmcSource OGLE OGLE-II ID varchar 15     meta.id
ogle3Field ogle3LpvLmcSource, ogle3LpvSmcSource OGLE OGLE-III field varchar 8     obs.param;obs.field
ogle3Num ogle3LpvLmcSource, ogle3LpvSmcSource OGLE OGLE-III database number int 4     meta.number
oneSecMLVg Filter SHARKSv20210421 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter ULTRAVISTADR4 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VHSDR1 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VHSDR2 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VHSDR3 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VHSDR4 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VHSDR5 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VHSDR6 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VHSv20120926 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VHSv20130417 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VHSv20150108 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VHSv20160114 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VHSv20160507 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VHSv20170630 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VHSv20180419 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VHSv20201209 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VHSv20231101 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VIDEODR2 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VIDEODR3 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VIDEODR4 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VIDEODR5 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VIDEOv20100513 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VIDEOv20111208 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VIKINGDR2 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VIKINGDR3 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VIKINGDR4 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VIKINGv20110714 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VIKINGv20111019 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VIKINGv20130417 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VIKINGv20150421 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VIKINGv20151230 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VIKINGv20160406 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VIKINGv20161202 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VIKINGv20170715 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCDEEPv20230713 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCDR1 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCDR3 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCDR4 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCDR5 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20110816 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20110909 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20120126 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20121128 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20130304 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20130805 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20140428 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20140903 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20150309 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20151218 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20160311 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20160822 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20170109 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20170411 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20171101 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20180702 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20181120 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20191212 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20210708 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20230816 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VMCv20240226 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VSAQC The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VVVDR1 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VVVDR2 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VVVDR5 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VVVXDR1 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VVVv20100531 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter VVVv20110718 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
oneSecMLVg Filter, FilterSections SHARKSv20210222 The Vega magnitude limit of a 1s exposure in this filter real 4 mag -0.9999995e9  
orgDate rosat_bsc, rosat_fsc ROSAT date when source was included (MM-DD-YYYY) datetime 8 mm-dd-yyyy   time.epoch
ORIENT grs_ngpSource, grs_ranSource, grs_sgpSource TWODFGRS Orientation measured in degrees clockwise from E to W: orient = 180/pi * atan(2*sxy/((sxx + syy)*(1 + e)-syy)) real 4      
orient sharksAstrometricInfo SHARKSv20210222 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient sharksAstrometricInfo SHARKSv20210421 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient ultravistaAstrometricInfo ULTRAVISTADR4 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vhsAstrometricInfo VHSDR6 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vhsAstrometricInfo VHSv20170630 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vhsAstrometricInfo VHSv20180419 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vhsAstrometricInfo VHSv20201209 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vhsAstrometricInfo VHSv20231101 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient videoAstrometricInfo VIDEODR2 Orientation of axes float 8 degrees -0.9999995e9 ??
orient videoAstrometricInfo VIDEODR3 Orientation of axes float 8 degrees -0.9999995e9 pos.posAng
orient videoAstrometricInfo VIDEODR4 Orientation of axes float 8 degrees -0.9999995e9 pos.posAng
orient videoAstrometricInfo VIDEODR5 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient videoAstrometricInfo VIDEOv20111208 Orientation of axes float 8 degrees -0.9999995e9 ??
orient vikingAstrometricInfo VIKINGDR2 Orientation of axes float 8 degrees -0.9999995e9 ??
orient vikingAstrometricInfo VIKINGDR3 Orientation of axes float 8 degrees -0.9999995e9 pos.posAng
orient vikingAstrometricInfo VIKINGDR4 Orientation of axes float 8 degrees -0.9999995e9 pos.posAng
orient vikingAstrometricInfo VIKINGv20110714 Orientation of axes float 8 degrees -0.9999995e9 ??
orient vikingAstrometricInfo VIKINGv20111019 Orientation of axes float 8 degrees -0.9999995e9 ??
orient vikingAstrometricInfo VIKINGv20130417 Orientation of axes float 8 degrees -0.9999995e9 pos.posAng
orient vikingAstrometricInfo VIKINGv20140402 Orientation of axes float 8 degrees -0.9999995e9 pos.posAng
orient vikingAstrometricInfo VIKINGv20150421 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vikingAstrometricInfo VIKINGv20151230 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vikingAstrometricInfo VIKINGv20160406 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vikingAstrometricInfo VIKINGv20161202 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vikingAstrometricInfo VIKINGv20170715 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCDR1 Orientation of axes float 8 degrees -0.9999995e9 ??
orient vmcAstrometricInfo VMCDR2 Orientation of axes float 8 degrees -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCDR3 Orientation of axes float 8 degrees -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCDR4 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCDR5 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCv20110816 Orientation of axes float 8 degrees -0.9999995e9 ??
orient vmcAstrometricInfo VMCv20110909 Orientation of axes float 8 degrees -0.9999995e9 ??
orient vmcAstrometricInfo VMCv20120126 Orientation of axes float 8 degrees -0.9999995e9 ??
orient vmcAstrometricInfo VMCv20121128 Orientation of axes float 8 degrees -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCv20130304 Orientation of axes float 8 degrees -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCv20130805 Orientation of axes float 8 degrees -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCv20140428 Orientation of axes float 8 degrees -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCv20140903 Orientation of axes float 8 degrees -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCv20150309 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCv20151218 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCv20160311 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCv20160822 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCv20170109 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCv20170411 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCv20171101 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCv20180702 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCv20181120 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCv20191212 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCv20210708 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCv20230816 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vmcAstrometricInfo VMCv20240226 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vmcdeepAstrometricInfo VMCDEEPv20230713 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vvvAstrometricInfo VVVDR1 Orientation of axes float 8 degrees -0.9999995e9 pos.posAng
orient vvvAstrometricInfo VVVDR2 Orientation of axes float 8 degrees -0.9999995e9 pos.posAng
orient vvvAstrometricInfo VVVDR5 Orientation of axes float 8 radians -0.9999995e9 pos.posAng
orient vvvAstrometricInfo VVVv20110718 Orientation of axes float 8 degrees -0.9999995e9 ??
orientation RequiredMosaicTopLevel SHARKSv20210222 Orientation of image x-axis to N-S. If default, use natural orientation of input images. real 4 deg -0.9999995e9  
orientation RequiredMosaicTopLevel SHARKSv20210421 Orientation of image x-axis to N-S. If default, use natural orientation of input images. real 4 deg -0.9999995e9  
orientation RequiredMosaicTopLevel ULTRAVISTADR4 Orientation of image x-axis to N-S. If default, use natural orientation of input images. real 4 deg -0.9999995e9  
orientation RequiredMosaicTopLevel VHSv20201209 Orientation of image x-axis to N-S. If default, use natural orientation of input images. real 4 deg -0.9999995e9  
orientation RequiredMosaicTopLevel VHSv20231101 Orientation of image x-axis to N-S. If default, use natural orientation of input images. real 4 deg -0.9999995e9  
orientation RequiredMosaicTopLevel VMCDEEPv20230713 Orientation of image x-axis to N-S. If default, use natural orientation of input images. real 4 deg -0.9999995e9  
orientation RequiredMosaicTopLevel VMCDR5 Orientation of image x-axis to N-S. If default, use natural orientation of input images. real 4 deg -0.9999995e9  
orientation RequiredMosaicTopLevel VMCv20191212 Orientation of image x-axis to N-S. If default, use natural orientation of input images. real 4 deg -0.9999995e9  
orientation RequiredMosaicTopLevel VMCv20210708 Orientation of image x-axis to N-S. If default, use natural orientation of input images. real 4 deg -0.9999995e9  
orientation RequiredMosaicTopLevel VMCv20230816 Orientation of image x-axis to N-S. If default, use natural orientation of input images. real 4 deg -0.9999995e9  
orientation RequiredMosaicTopLevel VMCv20240226 Orientation of image x-axis to N-S. If default, use natural orientation of input images. real 4 deg -0.9999995e9  
orientation RequiredMosaicTopLevel VVVDR5 Orientation of image x-axis to N-S. If default, use natural orientation of input images. real 4 deg -0.9999995e9  
orientation RequiredMosaicTopLevel VVVXDR1 Orientation of image x-axis to N-S. If default, use natural orientation of input images. real 4 deg -0.9999995e9  
origfile Multiframe SHARKSv20210222 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe SHARKSv20210421 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe ULTRAVISTADR4 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VHSDR1 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VHSDR2 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VHSDR3 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VHSDR4 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VHSDR5 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VHSDR6 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VHSv20120926 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VHSv20130417 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VHSv20140409 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VHSv20150108 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VHSv20160114 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VHSv20160507 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VHSv20170630 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VHSv20180419 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VHSv20201209 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VHSv20231101 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VIDEODR2 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VIDEODR3 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VIDEODR4 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VIDEODR5 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VIDEOv20100513 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VIDEOv20111208 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VIKINGDR2 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VIKINGDR3 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VIKINGDR4 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VIKINGv20110714 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VIKINGv20111019 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VIKINGv20130417 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VIKINGv20140402 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VIKINGv20150421 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VIKINGv20151230 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VIKINGv20160406 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VIKINGv20161202 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VIKINGv20170715 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCDEEPv20230713 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCDR1 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCDR2 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCDR3 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCDR4 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCDR5 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20110816 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20110909 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20120126 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20121128 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20130304 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20130805 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20140428 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20140903 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20150309 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20151218 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20160311 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20160822 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20170109 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20170411 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20171101 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20180702 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20181120 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20191212 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20210708 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20230816 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VMCv20240226 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VVVDR1 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VVVDR2 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VVVDR5 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VVVXDR1 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VVVv20100531 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile Multiframe VVVv20110718 Original File Name {image primary HDU keyword: ORIGFILE} varchar 32   NONE  
origfile sharksMultiframe, ultravistaMultiframe, vhsMultiframe, videoMultiframe, vikingMultiframe, vmcMultiframe, vvvMultiframe VSAQC Original File Name varchar 32   NONE  
origid smashdr2_source SMASH ID used for this detection in the original als/alf chip file int 4      
origin Multiframe SHARKSv20210222 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe SHARKSv20210421 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe ULTRAVISTADR4 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VHSDR1 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VHSDR2 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VHSDR3 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VHSDR4 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VHSDR5 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VHSDR6 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VHSv20120926 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VHSv20130417 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VHSv20140409 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VHSv20150108 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VHSv20160114 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VHSv20160507 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VHSv20170630 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VHSv20180419 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VHSv20201209 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VHSv20231101 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VIDEODR2 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VIDEODR3 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VIDEODR4 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VIDEODR5 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VIDEOv20100513 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VIDEOv20111208 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VIKINGDR2 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VIKINGDR3 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VIKINGDR4 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VIKINGv20110714 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VIKINGv20111019 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VIKINGv20130417 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VIKINGv20140402 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VIKINGv20150421 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VIKINGv20151230 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VIKINGv20160406 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VIKINGv20161202 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VIKINGv20170715 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCDEEPv20230713 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCDR1 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCDR2 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCDR3 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCDR4 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCDR5 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20110816 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20110909 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20120126 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20121128 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20130304 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20130805 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20140428 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20140903 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20150309 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20151218 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20160311 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20160822 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20170109 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20170411 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20171101 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20180702 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20181120 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20191212 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20210708 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20230816 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VMCv20240226 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VVVDR1 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VVVDR2 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VVVDR5 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VVVXDR1 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VVVv20100531 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin Multiframe VVVv20110718 European Southern Observatory {image primary HDU keyword: ORIGIN} varchar 4   NONE  
origin sharksMultiframe, ultravistaMultiframe, vhsMultiframe, videoMultiframe, vikingMultiframe, vmcMultiframe, vvvMultiframe VSAQC European Southern Observatory varchar 4   NONE  
original_ext_source_id gaia_hip_tycho2_match GAIADR1 Original source identified in Hipparcos/Tycho2 varchar 16     id.cross
origVSArel vmcCepheidVariables VMCv20160311 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16   'NONE' meta.id
origVSArel vmcCepheidVariables VMCv20160822 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16   'NONE' meta.id
origVSArel vmcCepheidVariables VMCv20170109 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16   'NONE' meta.id
origVSArel vmcCepheidVariables VMCv20170411 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16   'NONE' meta.id
origVSArel vmcCepheidVariables VMCv20171101 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16   'NONE' meta.id
origVSArel vmcCepheidVariables VMCv20180702 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16   'NONE' meta.id
origVSArel vmcCepheidVariables VMCv20181120 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16   'NONE' meta.id
origVSArel vmcCepheidVariables VMCv20191212 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16   'NONE' meta.id
origVSArel vmcCepheidVariables VMCv20210708 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16   'NONE' meta.id
origVSArel vmcCepheidVariables VMCv20230816 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16   'NONE' meta.id
origVSArel vmcCepheidVariables VMCv20240226 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16   'NONE' meta.id
origVSArel vmcCepheidVariables, vmcEclipsingBinaryVariables VMCDR4 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16   'NONE' meta.id
origVSArel vmcRRlyraeVariables VMCDR4 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16     meta.id
origVSArel vmcRRlyraeVariables VMCv20160822 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16     meta.id
origVSArel vmcRRlyraeVariables VMCv20170109 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16     meta.id
origVSArel vmcRRlyraeVariables VMCv20170411 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16     meta.id
origVSArel vmcRRlyraeVariables VMCv20171101 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16     meta.id
origVSArel vmcRRlyraeVariables VMCv20180702 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16     meta.id
origVSArel vmcRRlyraeVariables VMCv20181120 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16     meta.id
origVSArel vmcRRlyraeVariables VMCv20191212 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16     meta.id
origVSArel vmcRRlyraeVariables VMCv20210708 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16     meta.id
origVSArel vmcRRlyraeVariables VMCv20230816 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16     meta.id
origVSArel vmcRRlyraeVariables VMCv20240226 VSA release from which Ks data was used {catalogue TType keyword: ORIG_DB} varchar 16     meta.id
origVSAsourceID vmcCepheidVariables VMCDR4 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcCepheidVariables VMCv20160311 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcCepheidVariables VMCv20160822 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcCepheidVariables VMCv20170109 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcCepheidVariables VMCv20170411 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcCepheidVariables VMCv20171101 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcCepheidVariables VMCv20180702 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcCepheidVariables VMCv20181120 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcCepheidVariables VMCv20191212 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcCepheidVariables VMCv20210708 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcCepheidVariables VMCv20230816 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcCepheidVariables VMCv20240226 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcEclipsingBinaryVariables VMCDR4 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcEclipsingBinaryVariables VMCv20140903 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: SOURCEID} bigint 8     meta.id
origVSAsourceID vmcEclipsingBinaryVariables VMCv20150309 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: SOURCEID} bigint 8     meta.id
origVSAsourceID vmcEclipsingBinaryVariables VMCv20151218 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: SOURCEID} bigint 8     meta.id
origVSAsourceID vmcEclipsingBinaryVariables VMCv20160311 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcEclipsingBinaryVariables VMCv20160822 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcEclipsingBinaryVariables VMCv20170109 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcEclipsingBinaryVariables VMCv20170411 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcEclipsingBinaryVariables VMCv20171101 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcEclipsingBinaryVariables VMCv20180702 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcEclipsingBinaryVariables VMCv20181120 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcEclipsingBinaryVariables VMCv20191212 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcEclipsingBinaryVariables VMCv20210708 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcEclipsingBinaryVariables VMCv20230816 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcEclipsingBinaryVariables VMCv20240226 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8   -99999999 meta.id
origVSAsourceID vmcRRlyraeVariables VMCDR4 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8     meta.id
origVSAsourceID vmcRRlyraeVariables VMCv20160822 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8     meta.id
origVSAsourceID vmcRRlyraeVariables VMCv20170109 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8     meta.id
origVSAsourceID vmcRRlyraeVariables VMCv20170411 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8     meta.id
origVSAsourceID vmcRRlyraeVariables VMCv20171101 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8     meta.id
origVSAsourceID vmcRRlyraeVariables VMCv20180702 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8     meta.id
origVSAsourceID vmcRRlyraeVariables VMCv20181120 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8     meta.id
origVSAsourceID vmcRRlyraeVariables VMCv20191212 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8     meta.id
origVSAsourceID vmcRRlyraeVariables VMCv20210708 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8     meta.id
origVSAsourceID vmcRRlyraeVariables VMCv20230816 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8     meta.id
origVSAsourceID vmcRRlyraeVariables VMCv20240226 VSA sourceID in VSA release from which Ks data was used {catalogue TType keyword: ID_VMC} bigint 8     meta.id
overLaps RequiredMapAverages SHARKSv20210222 Average over overlaps (use with average over deep frames and source merging) 0/N N/Y tinyint 1   0  
overLaps RequiredMapAverages SHARKSv20210421 Average over overlaps (use with average over deep frames and source merging) 0/N N/Y tinyint 1   0  
overLaps RequiredMapAverages ULTRAVISTADR4 Average over overlaps (use with average over deep frames and source merging) 0/N N/Y tinyint 1   0  
overLaps RequiredMapAverages VHSv20201209 Average over overlaps (use with average over deep frames and source merging) 0/N N/Y tinyint 1   0  
overLaps RequiredMapAverages VHSv20231101 Average over overlaps (use with average over deep frames and source merging) 0/N N/Y tinyint 1   0  
overLaps RequiredMapAverages VMCDEEPv20230713 Average over overlaps (use with average over deep frames and source merging) 0/N N/Y tinyint 1   0  
overLaps RequiredMapAverages VMCDR5 Average over overlaps (use with average over deep frames and source merging) 0/N N/Y tinyint 1   0  
overLaps RequiredMapAverages VMCv20191212 Average over overlaps (use with average over deep frames and source merging) 0/N N/Y tinyint 1   0  
overLaps RequiredMapAverages VMCv20210708 Average over overlaps (use with average over deep frames and source merging) 0/N N/Y tinyint 1   0  
overLaps RequiredMapAverages VMCv20230816 Average over overlaps (use with average over deep frames and source merging) 0/N N/Y tinyint 1   0  
overLaps RequiredMapAverages VMCv20240226 Average over overlaps (use with average over deep frames and source merging) 0/N N/Y tinyint 1   0  
overLaps RequiredMapAverages VVVDR5 Average over overlaps (use with average over deep frames and source merging) 0/N N/Y tinyint 1   0  
overLaps RequiredMapAverages VVVXDR1 Average over overlaps (use with average over deep frames and source merging) 0/N N/Y tinyint 1   0  


Home | Overview | Browser | Access | Login | Cookbook
Listing | FreeSQL
Links | Credits

WFAU, Institute for Astronomy,
Royal Observatory, Blackford Hill
Edinburgh, EH9 3HJ, UK

vsa-support@roe.ac.uk
29/03/2024