You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Code tries to figure out the comment splitting on / leaving out the right part reading ESO headers. But keyword values are truncated before / when it includes one or more in its value.
The output of next python code snippet should provide the full instrument name with a revision ID on top of next input values:
HIERARCH ESO INS ID = 'GRAVITY/176642' / Instrument ID.
HIERARCH ESO INS ID = 'PIONIER/$Revision: 350678 $' / Instrument ID.
fromastroquery.eso.coreimportEsoClasseso=EsoClass()
headers=eso.get_headers(["GRAVI.2024-09-27T07:22:10.935","PIONI.2024-01-12T08:55:01.576"])
print(headers["HIERARCH ESO INS ID"])
At present time, the output is :
HIERARCH ESO INS ID
-------------------
GRAVIT
PIONIE
If this is a bug, I guess that a fix should also manage multiple quotes occurences with and without escaping and maybe other tricky cases ...
The text was updated successfully, but these errors were encountered:
The table reader has incorrectly set the string length, apparently:
No, this is the number of rows of the astropy.table.Table for the get_headers call where I queried two dataproduct IDs.
From the next line of code ( value = value.split('/', 1)[0].strip()) , the value is retrieved from the right part after the first '=' splitting with '/'. But the assumption that the left part contains the keyword value fails when the value itself contains a /
Code tries to figure out the comment splitting on / leaving out the right part reading ESO headers. But keyword values are truncated before / when it includes one or more in its value.
The output of next python code snippet should provide the full instrument name with a revision ID on top of next input values:
At present time, the output is :
If this is a bug, I guess that a fix should also manage multiple quotes occurences with and without escaping and maybe other tricky cases ...
The text was updated successfully, but these errors were encountered: