Activity for Autoplot
-
Jeremy Faden posted a comment on ticket #645
This will be in the next development release.
-
Here's where I enabled it before: System.getProperty("timetagMonitoringDas2StreamHandler","false").startsWith("t")
-
I'm going to implement this for TRACERS. Actually I thought there was an environment variable you could set to experiment with this, and I need to look for it.
-
DasProgressPanel constructor should be protected
-
Explicit resolution limit for Das2Server in the GUI
-
Implicit prints at the interactive command line need some work
-
Always create column names in ASCII tables
-
Cell
-
Always create column names in ASCII tables
-
Cell
-
Always create column names in ASCII tables
-
Always create column names in ASCII tables
-
Scan behavior when multiple plot elements are used
-
This is fixed.
-
Bug of the week goes to Ivar. This demonstrates: https://github.com/autoplot/dev/blob/master/bugs/sf/2788/demoBug2788.jy
-
Scan behavior when multiple plot elements are used
-
I'm committing changes to allow the resolution to be limited. A new "resolutionLimit" switch is added to URIs and the "interval" label is swapped for TCAs vs datasets.
-
where(spacecraft.eq(rbspa)) no complaint
-
I check for arg_0 and arg_1 starting with "where(" and reject in this case.
-
Chris Piker posted a comment on ticket #2787
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
-
Explicit resolution limit for Das2Server in the GUI
-
where(spacecraft.eq(rbspa)) no complaint
-
This is released in 20260131a.
-
Also worth mentioning is distribution functions often confuse the autoranging, where it'll pick xlog. This triggered the error.
-
Deadlock observed when plotting distribution functions, xlog
-
ASCII URI with pattern and wildcard ought to work
-
ASCII URI with pattern and wildcard ought to work
-
Also I ran into a PDS4 file which generates the error "Unsupported number of axes, only one, two, or three" which I believe is related (and was the motivation for updating the PDS4 library anyway). See the file mvn_sta_l2_d1-32e4d16a8m_20210511_v02_r04.xml (and I have a copy of this on my system /home/jbf/tmp/20260126/mvn_sta_l2_d1-32e4d16a8m_20210511_v02_r04.xml).
-
Also I ran into a PDS4 file which generates the error "Unsupported number of axes, only one, two, or three" which I believe is related (and was the motivation for updating the PDS4 library anyway).
-
This has been an issue for a while, where newer versions of the PDS4 library don't work with Autoplot on Java versions greater than 9 or so. I'm going to experiment with In-Sook's reader since its goals are more similar to Autoplot's, and will probably work more consistently.
-
See https://github.com/autoplot/dev/blob/master/demos/2019/20190726/runBatchNew.batch for an example.
-
setenv newBatchFileFormat=true will use the new format with 20260124a and newer.
-
Run batch tool file format
-
Now it runs the batch instead of printing that this isn't supported yet. This still needs lots of testing. There's a new package org.autoplot.batch and new class BatchProcessor which supports one parameter, minimally. This is much cleaner though and I'll refactor the GUI to use this instead.
-
Now it runs the batch instead of printing that this isn't supported yet. This still needs lots of testing.
-
It's a very cold day in Iowa and I'm going to take this on. This should allow: * separate the Model from the View * headless processing * multi-computer processing * improved batch file formatting (they are very hard to read and create from other programs) So the GUI will, when pressing the "go" button, write a .batch file which describes the run. In a subdirectory with a similar name, in a "queue" subdirectory, task descriptions will be written. Workers move tasks from "queue" to "pending", and...
-
It's a very cold day in Iowa and I'm going to take this on. This should allow: * separate the Model from the View * headless processing * multi-computer processing * improved batch file formatting (they are very hard to read and create from other programs)
-
It's a very cold day in Iowa and I'm going to take this on. This should allow: * separate the Model from the View * headless processing * multi-computer processing * improved batch file formatting (they are very hard to read and create from other programs
-
Strange behavior associated with new vperp vpar slice
-
I verified slice at datum works as well.
-
--script --help when PWD is used shows error
-
This is fixed, where printScriptUsage in AutoplotUI didn't set PWD.
-
~/fun/2025/xmas/letter spot9> autoplot --headless --script writeLabelsEnvelope2025.jy --help welcome to autoplot (v2026a_1) Jan 21, 2026 10:45:48 AM org.autoplot.AutoplotUI main INFO: welcome to autoplot (v2026a_1) Jan 21, 2026 10:45:48 AM org.autoplot.AutoplotUI$140$1 uncaughtException SEVERE: runtime exception: Traceback (innermost last): File "<string>", line 24, in ? NameError: PWD Traceback (innermost last): File "<string>", line 24, in ? NameError: PWD at org.python.core.Py.NameError(Py.java:182)...
-
--script --help when PWD is used shows error
-
It looks like it might load fine initially, and then the second use fails.
-
Also the label "Transmogrify" is not used.
-
transmogrify script shows where characters are not escaped property on server
-
I need to check on slice-by-value before closing this ticket.
-
This is fixed, where it was trying to use the v_perp index on time. We just reset the index to the max in this case.
-
Strange behavior associated with new vperp vpar slice
-
Strange behavior associated with new vperp vpar slice
-
HAPI client should use abouts.json and abouts-dev.json
-
Ivar was asking about this sort of thing, too. He'd like to have the option of setting serveral files at once, too.
-
The "save vap" dialog needs to be changed as well, as does the File->Add Plot From->Local file...
-
So the procedure is: 1. navigate to /Users/jbf/autoplot_data/config 2. edit system.properties 3. add the line "fileDialogNative=true" Restart Autoplot.
-
Option to use native file choosers
-
Run Batch to calculate ETA
-
Jython float must have floating point values enumerated
-
This was done. I was bothered a bit by whether or not the formatting in the examples should be used, but clearly this is not possible (1,1e2,1e4 will always be rendered as 1,100,10000 since they are just doubles). See https://github.com/autoplot/dev/tree/master/bugs/sf/2778
-
Item 3 (multi-thread graphics) was done mid-2025. I think there was another ticket for this.
-
Need standard way to run a vap on a file
-
This is fixed by converting the values to floats. I'm not sure I like this, since it's nice to allow the values to be expressed in the GUI the same as they are in the script (0 vs 0.0).
-
It seems like old threads aren't cleaned up, and my process keeps getting hung up. This needs more study.
-
(Item 10) The number of threads is easily adjustable in the Java class that manages, and this control should be available in the GUI.
-
(Item 9) Projection of ETA for the complete job would be fun and useful.
-
Item 1 was done earlier.
-
Item 6 is done.
-
(Item 8) The default number of threads should be 8. I ran with 32 on a very capable machine and it quickly ran out of memory, and the GUI was very sluggish. Item 8 is done in that the default is set and can be adjusted.
-
(Item 6) Also option to automatically scroll to the currently running job would be nice. Item 6 is done.
-
(Item 5) Also, when running multi-thread, the cancel button doesn't work. If you hit the cancel on the progress monitor, then the "Go" button remains insensitive. Item 5 is fixed.
-
"Also option to automatically scroll to the currently running job would be nice." is done.
-
Edit the parameters for the script: limit1= getParam('limit1', 0.1, 'limit of resolution', [0.1,1,2] ) limit2= getParam('limit2', 0.1, 'limit of resolution', [0.1,1.0,2.0] ) Note that the limit1 control doesn't allow 1 or 2 to be selected.
-
Run Batch multi-thread bugs
-
Items 1 and 2 are fixed. Item 3 can be worked around using the serial version of multiple-argument specification.
-
Run Batch multi-thread bugs
-
Run Batch multi-thread bugs
-
Autoplot unable to read ac_or_ssc_20230101_v01.cdf zvars and rvars
-
PDS4 support leaves FileChannels open, quickly filling tmp for batch processing
-
I believe this is fixed, and will be in the next release. I always pull out all the DataObjects, then scan through looking for specific types, and then the last operation is to close them all.
-
PDS4 support leaves FileChannels open, quickly filling tmp for batch processing
-
Also I don't think anyone besides me was using this, and maybe it's just as well to drop the feature.
-
See also https://sourceforge.net/p/autoplot/bugs/2757/
-
See also https://sourceforge.net/p/autoplot/bugs/2762/
-
RunBatch from the command line
-
I would really like to have this ability, for processing jobs on campus.
-
See https://github.com/autoplot/dev/blob/master/bugs/2025/20251231/demoBugGetDataSetsMonitor.jy
-
synchronize='nn' or synchronize='interpolate'
-
getDataSets should have synchronize option, improve feedback
-
verify getDataSets command doesn't provide monitor feedback
-
Yep it was a bug, where break was called so that the third argument was never checked. Also null is now allowed for the timerange parameter.
-
plots added in reverse order
-
Jython binding loop detector
-
Strange NoClassDefFoundError with StaticCodeAnalysis
-
digital renderer with bundles of data
-
This was done. It called a dataset without data "data" and it should either be called "ds" or "". It's called "" here.
-
To Autoplot's credit, it printed this perfectly, where 1in on the picture was 1in on the printout. I think this was on a Mac, printing to a PDF.
-
This doesn't show reliably.
-
Jython float must have floating point values enumerated
