The Runner prioritizes its own settings over the input port. That is partly wanted behavior since the user is allowed to pick a simulation from the configuration menu and run it.
However, on resetting the node, the expected behavior would be that the Runner always prioritizes the simulation from the input port, otherwise any changes up the line (i.e. SImulation Configurator) do not have any effect on the Runner.
A possible solution is to delete the settings on reset.
A problem still occurs when a simulation is picked from the configuration menu after the Runner has been executed. Then the configuration menu doesn't behave as expected.
schuelet
commented
2 years ago
The Runner prioritizes its own settings over the input port. That is partly wanted behavior since the user is allowed to pick a simulation from the configuration menu and run it. However, on resetting the node, the expected behavior would be that the Runner always prioritizes the simulation from the input port, otherwise any changes up the line (i.e. SImulation Configurator) do not have any effect on the Runner.
A possible solution is to delete the settings on reset. A problem still occurs when a simulation is picked from the configuration menu after the Runner has been executed. Then the configuration menu doesn't behave as expected.