Repository navigation
How to forbid transition in a multiple state TPS network? #692
Description
Activity
This should be relatively easy to do, and the behavior should be this way by default (stop when you enter any state).
I think that all this will require is:
- modify
Transitionobjects to take a list offorbiddenvolumes (defaultNone) - modify the network code so that
from_state_pairsuses thatforbiddenvolume (also requires moving the creation of the set of initial and final states outside the loop)
@sroet tells me this is not urgent, and I have a lot of my plate right now, so I'll come back to fixing this at a later date.
- modify
I don't think this will create incompatibilities, so we can move it to 1.x milestone.
Metadata
Metadata
Assignees
Labels
No labels
I was trying to build a multiple state TPS network that excluded (or forbids) a specific transition, however I ran into some unexpected behaviour.
As can be seen in the ipynb in this directory, if I don't include the B <-> C transition, it doesn't stop the simulation when reaching state C from B (or reaching state B from C), but instead runs until it reaches max length, finds a self transition or a valid transition.
I wondered if this is the intended behaviour and if so, if there is a way to construct a TPSNetwork that stops the simulation when reaching any state and rejects if it is a B <-> C transition?