You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Null activities are assumed to have [0 0] constraints while unbounded activities have [0 :infinity]. Since they have different semantics, they should be visually distinguishable.
The text was updated successfully, but these errors were encountered:
I agree. The ability to distinguish null activities from non-null activities goes beyond the default temporal constraint. It's the fundamental semantic difference between a null activity (which isn't an activity) and a real activity that is even more important. For the observer of the TPN, they both appear as similar (often identical) arcs between nodes.
Often, null activities are drawn slightly differently, in that non-null activities are (always?) drawn horizontally while null activities are drawn at arbitrary angles. However, that's pretty subtle. Some other suggestions to distinguish null activities from non-null:
use a dashed line for the arc
use a thinner line for the arc
use an explicit "NULL" (or some other) activity label for all null activities [not a great idea, since it will clutter the TPN]
Let's NOT distinguish the null activities by color, since that would interfere with the normal expected coloring of execution state.
Null activities are effectively connectors of 2 nodes and they exist for historical reasons. Cytoscape based planviz used edges without arrows to indicate null activities and effectively distinguished null from non-null activities.
Null activities are assumed to have [0 0] constraints while unbounded activities have [0 :infinity]. Since they have different semantics, they should be visually distinguishable.
The text was updated successfully, but these errors were encountered: