Open cyarp opened 3 years ago
Possibly may also sometimes scheduling conflicts within a partition
Possibly when FSMs are involved as they contain state and are handled a little differently than standard delays - which should not be absorbed.
Actually, what I was seeing may be related to automated sub-blocking
Context expansion can sometimes cause communication cycles if nodes are absorbed into a context are from another partition.
Ideally, partitioning would occur after this point but manual partition specification occurs before.
For now, will stop context expansion at nodes in a different partition and will emit a warning.