Currently, get-calibration-res API returns in JSON form the plot (when getPlot=True) with the entire photometry (light curve).
Instead, it should return the plot with the calibration results (one plot with many subplots for each filter, blue).
This plot is now returned (as png) in photometric data upload, but should also be available through get-calibration-res.
Additionally, instead of files, the request should allow for either a list of calibids, e.g.
calibid : [12345,234556]
or
filename : ['cat-Gaia19eyy-ROAD-not-matched.dat']
However, I think currently the call with filename does not work. I tried with
'files':['cat-Gaia19eyy-ROAD-not-matched.dat'],
or
'files':['296_cat-Gaia19eyy-ROAD-not-matched.dat'],
(which is the actual filename this file was stored)
for this point https://bh-tom2.astrolabs.pl/dataproducts/data/267687/
but always got the error: {'Error': 'File does not exist in the database'}
Currently, get-calibration-res API returns in JSON form the plot (when getPlot=True) with the entire photometry (light curve). Instead, it should return the plot with the calibration results (one plot with many subplots for each filter, blue). This plot is now returned (as png) in photometric data upload, but should also be available through get-calibration-res.
Additionally, instead of files, the request should allow for either a list of calibids, e.g. calibid : [12345,234556] or filename : ['cat-Gaia19eyy-ROAD-not-matched.dat']
However, I think currently the call with filename does not work. I tried with 'files':['cat-Gaia19eyy-ROAD-not-matched.dat'], or 'files':['296_cat-Gaia19eyy-ROAD-not-matched.dat'], (which is the actual filename this file was stored) for this point https://bh-tom2.astrolabs.pl/dataproducts/data/267687/
but always got the error: {'Error': 'File does not exist in the database'}