Mark Rose
Mark Rose
The fix for #628 appears to solve this, too. See PR #629.
We are planning on making this a manual operation, but facilitated by a shell script to make the handover between ground stations easier. One could easily schedule such a script...
This is probably related to https://github.com/yamcs/yamcs/issues/685 also.
Yes, I can see that. Perhaps the initial value should be retained as a string, always (since it is submitted as a string anyway), but parsed according to its type...
It's possible the fix will solve our issues. There are two issues we need to make sure we handle: 1. Because some of our instruments take images, but do not...
The update to the RealtimeArchiveFiller solves the problem I found with values crossing interval boundaries, thanks! Will do some further testing to see if this request is no longer required.
Workaround: Using `source=replay` in the HTTP API causes the aggregate value to be retrieved (albeit more slowly because of the replay processor). Using `source='replay'` in the Python API also works.
Another update from one of our users: the problem does not occur when running Yamcs 5.4.5.
Here is the use case. Right now it is specific to OpenMCT, but other clients might also desire this behavior. To display a plot where the number of data points...
Ooh, sorry, misunderstood! Inserted myself where I didn't belong.