Chris Piker

(Potentially off topic) According to the 2.2.2 ICD, the properties are xCacheRange and xCacheResolution, have you seen any readers using some other property names? Just in case you do I'd prefer to fix any readers that don't follow the ICD instead of putting the burden on client programs to guess the property names.

I'm updating the tracers data source generation script to start adding the "-r" parameter to the das2_bin_avgsec reducer for line-plot data. Everything in Tracers test area that outputs as a lineplot will start providing min/max/avg unless the "Intrinsic Resolution" button is selected. I'm leaving out std. dev. for now because confidence intervals are what I was originally interested in but didn't know what to call it.

I'd imagine that a "no finer than" control would be a good idea (knowing George H). So to encapsulate the logic: DSDF says data source requires interval -> GUI controls minimum "interval=" GET parameter DSDF doesn't required interval -> GUI controls minimum "resolution=" GET parameter

I'd imagine that a "no finer than" control would be a good idea, knowing George H. So to encapsulate the logic: DSDF says data source requires interval -> GUI controls minimum "interval=" GET parameter DSDF doesn't required interval -> GUI controls minimum "resolution=" GET parameter

Nice. So here's a stream that contains nominal min/max, warn min/max (attached). To get the same thing into autoplot directly try: vap+das2server:https://tracers-dev.physics.uiowa.edu/stream?p2v5v_vmon&dataset=TRACERS-2/QL/EFI/HSK&intrinsic=true&start_time=2025-08-19T00:48:08.375Z&end_time=2025-08-19T00:51:59.625Z

Just got a look at the text viewer. Nice. A simple tool for a simple job. As far as sending the output to a browser goes, maybe the button for that could be in the window that displays the text. That way a user would have the option to open in a browser but not be required to do so.

Would you like to support viewing .CAT files from PDS3? I presume there's not a handler for .cat yet so this tool could handle those too... maybe? On a related note: after parsing, where does the descriptive text for variables end up inside the QDataset model?

Thanks for implementing this! Since people already have a browser and know how to operate it, they can put a link there if they want. I think there's value in keeping the workflow in-line. Looking forward to trying this out.