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
Would it make sense to rename the second column of the states table, currently called Diameter, to something like Depth or Length? This would make it more sense to me and would be more consistent with tlc's cli output
The text was updated successfully, but these errors were encountered:
The term 'diameter,' defined as "the longest shortest path between any two vertices in a graph", aligns with the statistical measurement. AFAIK 'Length' typically refers to the number of edges in a path, while 'depth' appears to correspond to a graph's thickness. The appearance of 'depth' in TLC's final result reporting likely serves to track the progress of the breadth-first search. Thus, it would perhaps be best to modify TLC, although such a change might potentially break TLC wrappers parsing its output.
Fortunately, both the VSCode extension and the TLA+ Toolbox are at least consistent and use "diameter."
Would it make sense to rename the second column of the states table, currently called
Diameter
, to something likeDepth
orLength
? This would make it more sense to me and would be more consistent with tlc's cli outputThe text was updated successfully, but these errors were encountered: