I have a script which writes a .batch file to run another script, which I can run over an ssh with a headless Autoplot. Unfortunately there's no way to ran a batch script like this, so I can't run Doug's files.
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 once complete the task is moved to "completed".
Last edit: Jeremy Faden 2026-01-23
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.
Last edit: Jeremy Faden 2026-01-23
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I started working on a new GUI which initializes the command-line run batch code, and then monitors it. For example, you will be able to point it at a running batch job and be able to see the current status. The old GUI function will be supported by setting up the command line mode and then monitoring it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I realized there was a bug in the two-parameter mode, where the "implement defaults" was called twice, clearing the setting of the first parameter. This is fixed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I started this, but I realized the code is very dependent on the GUI and will need some refactoring.
I would really like to have this ability, for processing jobs on campus.
It's a very cold day in Iowa and I'm going to take this on. This should allow:
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 once complete the task is moved to "completed".
Last edit: Jeremy Faden 2026-01-23
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.
Last edit: Jeremy Faden 2026-01-23
This is released in 20260131a.
I started working on a new GUI which initializes the command-line run batch code, and then monitors it. For example, you will be able to point it at a running batch job and be able to see the current status. The old GUI function will be supported by setting up the command line mode and then monitoring it.
I realized there was a bug in the two-parameter mode, where the "implement defaults" was called twice, clearing the setting of the first parameter. This is fixed.