Running Simulation Starter w/o declaring NList arguments causes null pointer

UWB-Biocomputing / WorkBench

Software and data provenance management platform for simulations of dissociated cortical cultures.

https://uwb-biocomputing.github.io/WorkBench/

Apache License 2.0

1 stars 3 forks source link

Running Simulation Starter w/o declaring NList arguments causes null pointer #17

Open jConquest opened 4 years ago

jConquest commented 4 years ago

While the application currently allows users to run the Simulation Starter without importing the NList xml files (using default workbenchconfigfiles directory and hoping to find them there) it causes run time issues:

when attempting to analyze the script after completion, the NList internal object is set to null and causes a null pointer exception preventing the functionality of Analyze.
if default directory does not contain NList xml files, the simulation fails to parse input parameters and crashes

jConquest commented 3 years ago

keep in mind that if the user selects using NList input and does not provide said input, this would naturally lead to null pointer issues.

The thing to do here is to prevent workbench from trying to execute the simulation if it is missing NList input, given the user has selected to provide said input. This can be accomplished by ensuring that each type of the NList input has been imported by the DynamicInputConfigurationDialog before allowing for the user to click the next button.