reines / oversim-manager Goto Github PK

What happens if the main process is closed during a run? What should happen?

• Should shutdown all child OverSim processes.
• What about the data though - delete the result directory, or leave it? Somehow mark it was unfinished?

Sometimes child OverSim processes seem to drop to 0% CPU, but aren't finished. Needs investigating (maybe by directing stdout+stderr to somewhere useful...)

If a run fails it should be made much more obvious in the final summary, and maybe even at the time it fails (System.beep()?).

Some kind of configuration file should be used to specify the working directory path. It could also contain global overrides for omnetpp.ini configuration, and an override for the max number of cores to use.

Each thread should collate and process data for its completed runs before it notifies the manager of completion. The notification should pass this data to the manager, where it is combined with any existing data from other runs. When the manager is finishing this data should be processed and output to a CSV file.

It would be useful to add support for processing vector files into some format we can import directly into Minitab/SPSS.

It would be nice if we could print out of a summary of the parameters that will be used, and ask the user if they are correct, before the runs are started.

Parameters can have units in them. They are parsed correctly, but do we need to try extract the unit ourselves or can we simply pass the string through to the csv (i.e. is there an easy way in openoffice etc. to convert a column of Xs to simply X)?

At the moment we handle Xs and strip the s, but there are many types of units so ideally we should just pass the entire thing through.

At the moment we wait for all configurations to complete before processing data for them all. We should process data for each configuration as soon as it has completed.

Save a summary with run times etc to file upon completion of a config.

When trying to pass multiple configs to run.sh we get an error and build failure.

$ ./run.sh EpiChordValidation0-1way EpiChordValidation1-1way
./run.sh: line 3: [: EpiChordValidation0-1way: binary operator expected

There currently isn't really any...!

Started work on this in 795ce78.