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, the graphing and logging of the temperature of the cryostat is done entirely within javascript. This means that whenever the page is refreshed, it loses any of the information it has. It also only logs the most recent 20 seconds or so, which isn't great as the cryostat tends to cool down/heat up at much slower rates than that, and thus the graph wont be as useful as it could be.
A solution to this would be to log the temperature/time values within the adapter layer instead, and maintain one or more rolling buffers of temperature readings, with configurable limits on how many data points, and how frequently it should record them.
The text was updated successfully, but these errors were encountered:
Currently, the graphing and logging of the temperature of the cryostat is done entirely within javascript. This means that whenever the page is refreshed, it loses any of the information it has. It also only logs the most recent 20 seconds or so, which isn't great as the cryostat tends to cool down/heat up at much slower rates than that, and thus the graph wont be as useful as it could be.
A solution to this would be to log the temperature/time values within the adapter layer instead, and maintain one or more rolling buffers of temperature readings, with configurable limits on how many data points, and how frequently it should record them.
The text was updated successfully, but these errors were encountered: