Open edoddridge opened 7 years ago
This presumably has to do with the ConfigParser
class trying to be clever somehow about variable types. It must be possible to either persuade it, or post-process. Does the same thing not happen with other variables? Is there anything obviously special about slip
?
I've just tested freesurfFac
and it shows the same behaviour. I suspect other variables would too, but these ones are commonly set to zero or one, and hence we seem to be having numerical/boolean decision errors.
Setting them in the aronnax.conf
file seems to be a manageable workaround for now.
Stupid Python: python -c 'print 1 == True'
. We're probably going to need an explicit workaround for this disaster.
That's awkward.
Trying to override the value for
slip
in the config file by passing a new one todriver.simulate
results inslip
being set toyes
forslip=1.
, orno
forslip=0.
, rather than the numerical value.Setting it for a partial slip simulation, somewhere in the open interval (0, 1), produces the expected outcome.