Rename second column of states table from "Diameter" to "Depth"

[heidihoward]

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

[lemmy]

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."

[hwayne]

What if we added a tooltip indicator which explained the term? Something like this:

This would also help with teaching, lots of students don't realize there's tooltips!

(Though neither this nor the existing tooltip accurately explains what Depth means in simulation mode.)

[lemmy]

It would be confusing to speak of "longest behavior" when TLA defines a behavior as an infinite sequence of states.