Subject to change, of course :)
Last updated: 2016-09-26
| Rational |
There is a desire to have more advanced data handling for Das2 clients.
Including handling for X-Y-Z scatter data streams, handling vectors as
vectors instead of three un-related data columns, and rendering scatter
data with triangular interpolation.
At present there are two different versions of the DasCore libraries.
Keeping two different version of the DasCore up to date is not viable given the small size of our developer group, furthermore the data model inside DasQCore is more flexible that the traditional model in DasCore. To un-fork development it is desired to put the core components of DasQCore on the Iowa servers so that both local apps and the Autoplot can work off the same set of basic capibilities. |
|---|---|
| Benefits |
The most direct benefits from this work would be Mars Express MARSIS data
displays followed by Fluxgate Magnetometer on Juno. The indirect benefits
of having all major client programs work off the same core allow for easier
rollout of advanced Das2 server capabilities as well. |
| Action Items |
|
| Current State |
|
| Rational | Currently readers that take parameters in addition to Time, Resoltution or time interval are not able to communicate thier parameter set to Das2 clients except in an ad-hoc way. By providing a format for extra parameters generic clients can display a meaningful set of GUI controls customized for each reader. |
|---|---|
| Benefits | All missions using Autoplot, which is everything but Voyager right now. |
| Action Items |
|
| Current State |
There is a proto-type of the new parameter DSDF elements in the Jedi
Basic Rates dataset. This could be updated as developers review and
comment on the existing format. See:
DSDF in Das2 stream
to look at how this information is sent to existing das clients.
See Das 2.3 next-gen interface for what kinds of things can be done with standardized parameter information. |
| Rational |
Currently Das2 Streams are converted to Das2 data objects within DasQCore and
then those objects are converted to QDatasets. This makes it difficult to
support <X> <Y> <Z> streams and to support combinding
<Y> and <YScan> planes in the same packet. In general converting
from Das2 Streams directly to QDatasets will reduce the maintenace overhead
of DasQCore with is a benefit in and of itself. |
|---|---|
| Benefits |
This upgrade would directly improve plotting for MARSIS data on Mars Express,
but would also make it easier to support upgrades to Das2 stream properties
such as systematically providing a generic set of statistics for time-averaged
data, thus this improvement would benefit Voyager displays as well. This
update will also make it easier to support Vector designations in Das2 streams
which can be used to indicate Color for events bars, thus benefiting the Waves
investigation on Juno as well as instruments on other missions. |
| Action Items |
The QStream reader needs to be upgraded to read Das2 headers as well as
QStream headers. |
| Current State | Not Started |
| Rational |
Though they are not a prevalent as QUBE data X-Y-Z scatter data
occure often enough that it would be nice to have a reneder able
to present them without jagged artifacts. |
|---|---|
| Benefits |
Apparent altitude data from the MARSIS instrument on Mars Express could be
plotted versus apparent altitude by Autoplot without requiring a dedicated
program. In addition, Level 5 Magnetic field and plasma density could
be plotted versus latitude and longitude if a scatter data renderer were
available.
Tight zooms of any sweep frequency analyzer data would benefit from more accurate display including the HFRH survey mode data on Juno as well as the Galileo, DE and ISEE data. |
| Action Items |
|
| Current State | Not Started |
