Define behavior for roof-level repair scheduling and implement #18
Description
Problem:
- locations beyond the number of stories are not currently supported. For example, a 3-story building supports locations [1, 2, 3]. However in Pelicun, "roof" assigns components above the top story. For example, in a 3-story building, top assigns to story 3 while roof assigns to story 4.
In Pelicun, this was critical in order to access the correct EDP, since "floor" and "story" are different reference locations. However, in ATC-138, this distinction is only for repair scheduling/red-tagging.
Solution:
- Clarify definitions of locations like "roof", "top" and "all", with respect to ATC-138's story assignment convention
- Correct all references to num_stories, as well as arrays that are generated from this
- Correct all inputs built to the new convention