Closed pauleve closed 3 years ago
I'm looking at this now, I see that indeed the method does not exist but it's not just a typo.
As the code does not set the initial state and the NuSMV export should already be capable of encoding the input nodes all by itself, it looks like this block of code is completely useless, but I miss the knowledge about why it was added in the first place.
@ptgm: do you know what happens here?
Looking at GINsim's code history, it seems related to a refactoring of the NuSMV export 2 years ago.
I would propose to remove the failing code block for now and look for a way to set the initial state, preferably in bioLQM rather than GINsim but this would require some refactoring and we have little time for it in the near future.
I'm all for removing code :-) So in case of input nodes, by default, the NuSMV export does not fix any value for them, right? It is fine if the export do not allow fixing some value for some variables in the NuSMV export, as soon as it is documented. Thus removing the code and adding a minimal docstring would do the job I think.
Input nodes should have a positive self-regulation: they will keep their initial value. We may still need a way to set this initial value.
With v0.4.2 and ginsim 3.0.0b-12
results in
The method
addFixedInput
is missing (disappeared?); moreover the behaviour of this NuSMV export with an initialState or input nodes should be documented (and possibly parameterised if relevant).