Revision history [back]

I'm writing an OpenStudio measure with a long list of options for many of the input parameters. Initially, I tried to use a secondary file to host all the constants to keep the measure file tidy but found that if I imported parameters into the measure.rb file the OpenStudio application did not appear to populate my lists when I did this (although I could see them in the measure.xml ?) So I tried looking through other measures and found most folks just kind of listed them all out in the measure.rb file. Is there no better best practice?

Measure I'm working on and how I had to use a module inside of measure.rb to get it to work:

• How I'm referencing a module inside measure.rb
• Module it's referencing

I would much rather have this list of inputs reference a dynamic reference that updates with the OpenStudio gem rather than have to update it in two places.

I'm writing an OpenStudio measure with a long list of options for many of the input parameters. Initially, I tried to use a secondary file to host all the constants to keep the measure file things tidy but found that if I imported importing parameters into the measure.rb file resulted in the OpenStudio application did not appear to populate populating my lists when I did this input dropdowns (although I could see them in the measure.xml ?) So I tried looking through other measures and found most folks just kind of listed them all out in the measure.rb file. Is there no better best practice?

Measure I'm working on and how I had to use a module inside of measure.rb to get it to work:

• How I'm referencing a module inside measure.rb
• Module it's referencing

I would much rather have this list of inputs reference a dynamic reference that updates with the OpenStudio gem rather than have to update it in two places.

I'm writing an OpenStudio measure with a long list of options for many of the input parameters. Initially, I tried to use a secondary file to host all the constants to keep things tidy but found importing parameters into the measure.rb file resulted in the OpenStudio application not populating my input dropdowns (although I could see them in the measure.xml ?) So I tried looking through other measures and found most folks just kind of listed them all out in the measure.rb file. Is there no better best practice?

Measure I'm MCVE directories for a working on and how I had to use a broken example of what I mean can be found here:

• Link to working and broken measure

You will see both measures populate the choice argument with a module called MyConstants:

choices_os_vector = OpenStudio::StringVector.new
option_list = MyConstants::CHOICE_LIST
option_list.each do |option|
  choices_os_vector << option
end

The only difference is that working example has the module inside of the measure.rb to get it to work:

• How I'm referencing a file while the broken example references the module inside measure.rb
• Module it's referencing

I would much rather have this list of inputs reference a dynamic reference that updates with the OpenStudio something like the OpenStudio Standards gem rather than have to update it in two places.