Update Measure guide for 2.x measure tests

[DavidGoldwasser]

http://nrel.github.io/OpenStudio-user-documentation/reference/measure_writing_guide/#putting-it-all-together-a-complete-measure-test-file

There may be other areas to update as well.

• measure test
• valid output variables
• relationship between measure display name, name, class name, and directory anme

[DavidGoldwasser]

Found new restriction for measure output variable names. IfI have something like "test_cop2". It will be changed to "test_cop_2". Seems the rule is that letters and numbers should be separated by an underscore.

On measure name side it seems like multiple uppercase letters next to each other can create issues. Here is example

<name>bestesthe_reporting</name> <class_name>BESTESTHEReporting</class_name> <display_name>BESTEST HE Reporting</display_name>

This created issues in 2.x not for running, but only for populating output variable values in results. Here is what worked.

<name>bestest_he_reporting</name> <class_name>BestestHeReporting</class_name> <display_name>Bestest He Reporting</display_name>

@macumber not sure if there is anything in GUI that can be done to enforce this, but I'll at least get it into the documentation saying (Don't put multiple capital letters next to each other). Maybe there are cases where that would be fine, but for now I'll recommend avoiding them.

[jmarrec]

@DavidGoldwasser Is this true for 3.x too?

[DavidGoldwasser]

@jmarrec I think this is still valid. It is mostly a documentation task, but The Application could enforce name rules, but not sure how that would work. I have another task to add new measure and copy measure to CLI. Same issue could come up there.

[jmarrec]

Moved to NatLabRockies/OpenStudio-user-documentation#26