Open lmichel opened 3 years ago
On Wed, Apr 07, 2021 at 07:55:19PM -0700, Zarquan wrote:
If I remember correctly, the structure of the multi-band time series reflects the way that the data is collected on the spacecraft, how it is processed in their data processing pipelines,
No. The data on the spacecraft are cut-outs that are relayed down and analysed per-image, then combined and cross-identified in a rather complex process.
How this raw data is combined is certainly just a minor matter at the very end of this process.
I don't think that telling them they are doing it wrong is an option.
Why not? I'm sure they'll at least listen to us. And I'd say the point that column metadata changing per row is making things very difficult is a fairly strong one.
This is what they are trying to represent in their time series data.
The rotation of the spacecraft generates a repeated sequence of blue then red measurements, offset by a small time delay
as light from a source passes over the blue and then red photometer strips.
If I understand well your serialisation, you map a list of
NDPoint
, each one being composed withtime
GenericMeasure
I don not see how a client can see that the 1st dependant value is a magnitude and a second a flux.
This question is related to the discussion we have been having here