Activity for Chris Piker
-
Chris Piker posted a comment on ticket #2818
(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.
-
Thanks for the feature. Repeating ugly code is never fun, at least you have a sense of humor about it :-)
-
Showing the N components on the plot would be useful, but mostly I'm concerned with the data loading dialog box. For variables using LABL_PTR_1 there is a nice GUI where I can select a component of interest. For variables using LABL_PTR_2 I didn't see that option. Once the data are loaded they can be sliced to get a component so that's fine. But some users might have difficulty locating that option, so if the components were visible from the variable selection dialog box it would be welcome.
-
LABL_PTR_2
-
LABL_PTR_2
-
Looking over the list of registered mime types here: media-types the fits example, rfc4047 looks useful. Since the PDS is a somewhat open organization and not controlled by a single vendor I'd suggest something like the following for the full mime type: application/pds.label+xml; charset=utf-8 unless the PDS allows other encodings (which I hope they don't). This should allow things such as XPath expressions and stylesheets to still work.
-
Looking over the list of registered mime types here: media-types the fits example, rfc4047 looks useful. Since the PDS is a somewhat open organization and not controlled by a single vendor I'd suggest something like the following for the full mime type: application/pds.label+xml; charset=utf-8 unless the PDS allows other encodings (which I hope they don't).
-
Looking over the list of registered mime types here: media-types the fits example, rfc4047 looks useful. Since the PDS is a somewhat open organization and not controlled by a single vendor I'd suggest something like the following for the full mime type: **application/pds.label+xml; charset=utf-8** unless the PDS allows other encodings (which I hope they don't).
-
The following text from RFC 3023 might be useful here: If an XML document -- that is, the unprocessed, source XML document -- is readable by casual users, text/xml is preferable to application/xml. MIME user agents (and web user agents) that do not have explicit support for text/xml will treat it as text/plain, for example, by displaying the XML MIME entity as plain text. Application/xml is preferable when the XML MIME entity is unreadable by casual users. Similarly, text/xml-external-parsed-entity...
-
The following text from RFC 3023 might be useful here: If an XML document -- that is, the unprocessed, source XML document -- is readable by casual users, text/xml is preferable to application/xml. MIME user agents (and web user agents) that do not have explicit support for text/xml will treat it as text/plain, for example, by displaying the XML MIME entity as plain text. Application/xml is preferable when the XML MIME entity is unreadable by casual users. Similarly, text/xml-external-parsed-entity...
-
Since autoplot has a built-in python interpreter, would it be easy to have templates where the whole template file was just a python string template with dictionary replacement? For example: <Identification_Area> <logical_identifier> urn:nasa:pds:voyager2.pws.wf:data:%(beg.year)s-%(beg.month)s-%(beg.day)st%(beg.hour)s </logical_identifier> </Identification_Area> <Observation_Area> <Time_Coordinates> <start_date_time>%(begin)s</start_date_time> <stop_date_time>%(end)s</stop_date_time> ... The main...
-
wset updates
-
whoops, wrong axis
-
Join collapse debugged, property collapse implemented
-
Bug fix in 2.3 Waveform output
-
Bug fix in rank2 das2.3 exports
-
das2.3 export drafted, alpha code surely has bugs
-
Most of das2.3 export drafted
-
Refactored das2 stream export prior to 2.3/basic output implementation
-
Removed windows installer since it's a github project now
-
Initial windows installer
-
A hiezenbug, what a pain. How do you plan to resolve it?
-
Inital node traversial working, need to stop loading data on the event thread
-
Added dependence on dasCoreDatum package needed by DasProp class
-
Starting on node properties implementation, moved 2-phase construction into the open since it can require a progress monitor
-
Moved tree model to gui section
-
Moved common property lookup support for JSON based, or XML based nodes to a utility class to avoid redundant implementations
-
Started adding tree model and node variable property retrieval
-
Removed CWP reference to sub-project
-
Removed private properties and set ignore flags to keep them out
-
General layout of the das2 catalog dialog done, now to make it work
-
Moved catalog out of dasCoreUtil area as we don't want dasCoreUtil depending on CDF and HAPI libraries
-
Renamed the federated catalog source project since it's going to have to call the HAPI and CDF data sources as well
-
All nodes load. Check in prior to re-organization out of dasCoreUtil area.
-
Rename of core catalog classes. Only public interfaces and classes start with the name 'Das'
-
General catalog updates and commit before das catalog class renames
-
Bug fix in resourceUri requirements by data source type
-
Minor updates to track org.das2.catalog changes
-
Bug fix, should load exact node not nearest for reject test
-
Can now prepare the 'dc' source editor, navigation to root added
-
Moved to source name dc from dfc, it's easier to remember
-
Correcting project build errors for netbeans 8.2
-
Replace with netbeans 8.2 equivalents
-
Adding tag authority parsing. This one is odd compared to the rest of the URI schemes
-
Not sure if this is accurate since das2 catalogs don't need file paths, but nodes can be a standalone file, especially for testing
-
Preventing new data source from appearing in autoplot menus
-
Checking in non-netbeans 10 project configuration
-
Checking in non-netbeans 10 project configuration
-
Checking in non-netbeans 10 project configuration
-
Beginning sources for catalog source
-
New catalog source directory
-
added screen recorder jar
-
Updated das 2.3 output to handle co-sets (i.e. planes)
-
Bug fixes in Das 2.2 and 2.3 output, also first version of 2.3 stream that's ready for review
-
Options to export as Text or Binary das2 streams work as expected
-
Das2 streams exported from Autoplot now look the same as original read from server even when substitution text is included in the labels
-
Finished with initial draft of qdataset to das2 stream exporter
-
More support functions added for das2 header creation
-
More work no new qdataset serializer, draft not complete
-
Add redirection support that crosses protocol boundaries. Das servers may now redirect from http to https addresses
-
Reworking 'export as das2 stream' code
-
Handling HTTP error codes responses separately from HTTP success codes
1
