As of now the client is non-hardware aware, meaning that it does not know parameter limits, resolutions, clock frequencies and such.
The same applies for the plotter, which relies on fixed time resolutions to properly display the time axis.
POSSIBLE SOLUTION
PLOTTER: Use a json/yaml from the exported experiment to tell the resolution of the time axis.
CLIENT: Support said json/yaml on experiment export and implement a hw context that can be fetched from the server which has a similar format as the configuration and includes limits and resolutions for the various parameters.
As of now the client is non-hardware aware, meaning that it does not know parameter limits, resolutions, clock frequencies and such.
The same applies for the plotter, which relies on fixed time resolutions to properly display the time axis.
POSSIBLE SOLUTION
PLOTTER: Use a json/yaml from the exported experiment to tell the resolution of the time axis.
CLIENT: Support said json/yaml on experiment export and implement a hw context that can be fetched from the server which has a similar format as the configuration and includes limits and resolutions for the various parameters.