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
api/results/{uuid}/json/ should return the entire content of potential result's hdf5 file. A subprocessor_id query param could allow to choose part of the content. A custom filter (as for ItemWaveViewFilter) could allow to describe hdf5 content structure in the schema.
another route may allow to provide hdf5 file content with start/stop and nb_pixel query params as for waveform, for under sampling on the backend side for zooming purpose. Particular focus has to be given to the multiple potential data types on the y axes (e.g. a column of value for a spectrogram, e.g. a single value for an onset detection or no y axes for a full track value or potentiel labeled data instead of numerical values).
The text was updated successfully, but these errors were encountered:
Tointoin
changed the title
[server] replace native django route /result/{uuid}/json/ with a DRF api/result/{uuid}/json/
[server] replace native django route /results/{uuid}/json/ with a DRF api/results/{uuid}/json/
Jun 1, 2020
@gnuletik @yomguy
api/results/{uuid}/json/
should return the entire content of potential result's hdf5 file. A subprocessor_id query param could allow to choose part of the content. A custom filter (as for ItemWaveViewFilter) could allow to describe hdf5 content structure in the schema.another route may allow to provide hdf5 file content with start/stop and nb_pixel query params as for waveform, for under sampling on the backend side for zooming purpose. Particular focus has to be given to the multiple potential data types on the y axes (e.g. a column of value for a spectrogram, e.g. a single value for an onset detection or no y axes for a full track value or potentiel labeled data instead of numerical values).
The text was updated successfully, but these errors were encountered: