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
Currently, we understand well that the light curve information should be stored in two output objects to normalize them. The first one is homogeneous data as found in light curves (ie. time, flux, fluxerror). The second one stores model truths. This normalization is sensible because the first table has one record per observation of an astrophysical object leading to (numObs times numObjects records, though some may be suppressed due to being trivially outside a transient object's lifetime) , while the second has one record per object. For a single class of objects these may be stored in arrays and serialized to disc in the form of csv/hdf/relational databases.
The situation is more complicated if there are different classes of objects. The light curve storage and serialization is still the same, but the serialiation of model truths is much harder as the parameters of different objects form an inhomogeneous set of records.
How should we attempt to serialize these data? Should we be using
many relational database tables with one table per class of object?
Many groups in a hdf file, with each group representing a class of objects and therefore homogeneous?
All files in a noSQL database ?
The text was updated successfully, but these errors were encountered:
Currently, we understand well that the light curve information should be stored in two output objects to normalize them. The first one is homogeneous data as found in light curves (ie.
time
,flux
,fluxerror
). The second one stores model truths. This normalization is sensible because the first table has one record per observation of an astrophysical object leading to (numObs times numObjects records, though some may be suppressed due to being trivially outside a transient object's lifetime) , while the second has one record per object. For a single class of objects these may be stored in arrays and serialized to disc in the form of csv/hdf/relational databases.The situation is more complicated if there are different classes of objects. The light curve storage and serialization is still the same, but the serialiation of model truths is much harder as the parameters of different objects form an inhomogeneous set of records.
How should we attempt to serialize these data? Should we be using
The text was updated successfully, but these errors were encountered: