Addresses #4647, wrap the E+ Table:Lookup, Table:IndependentVariableList, and Table:IndependentVariable objects

[jmarrec]

Pull request overview

Adjust tests to use the TableLookup or TableMultivariableLookup, conditionally based on the version of the SDK

Link to relevant GitHub Issue(s) if appropriate: NREL/OpenStudio#4652

Link to the Linux.deb installer to use for CI Testing. If not set, it will default to latest official release.
[OpenStudio Installer]: http://openstudio-ci-builds.s3-website-us-west-2.amazonaws.com/PR-4652/OpenStudio-3.4.1-alpha%2B45452eabd2-Ubuntu-18.04.deb

This Pull Request is concerning:

• Case 1 - NewTest: a new test for a new model API class,
• Case 2 - TestFix: a fix for an existing test. The GitHub issue should be referenced in the PR description
• Case 3 - NewTestForExisting: a new test for an already-existing model API class
• Case 4 - Other: Something else, like maintenance of the repo, or just committing test results with a new OpenStudio version.

---

Case 2: Fix for an existing test

Please include a link to the specific test you are modifying, and a description of the changes you have made and why they are required.

Work Checklist

The change:

• affects site kBTU results
• does not affect total site kBTU results

If it affects total site kBTU:

• Test has been run backwards (see Instructions for Running Docker) for all OpenStudio versions to update numbers
• Changes did not make the test fail in older OpenStudio versions where it used to pass
• Matching OSM has been replaced with the output of the ruby test for the oldest OpenStudio release where it passes.
• All new/changed out.osw have been committed for official OpenStudio versions only

Either way:

• Ruby test is still stable: when run multiple times on the same machine, it produces the same total site kBTU.

  • I ensured that I assign systems/loads/etc in a repeatable manner (eg: if I assign Terminals to thermalZones, I do model.getThermalZones.sort_by{|z| z.name.to_s}.each do ... so I am sure I put the same ZoneHVAC systems to the same zones regardless of their order)
  • I tested stability using process_results.py (see python process_results.py --help for usage).
    Please paste the text output or heatmap png generated after running the following commands:

    # Clean up all custom-tagged OSWs
    python process_results.py test-stability clean
    # Run your test 5 times in a row. Replace `testname_rb` (eg `airterminal_fourpipebeam_rb`)
    python process_results.py test-stability run -n testname_rb
    # Check that they all passed
    python process_results.py test-status --tagged
    # Check site kBTU differences
    python process_results.py heatmap --tagged
    

• If relevant, new fields that can be autosized have been added to autosize_hvac.rb to ensure the autosizedXXX values methods do work

---

Review Checklist

• Code style (indentation, variable names, strip trailing spaces)
• Functional code review (it has to work!)
• Matching OSM test has been added or # TODO added to model_tests.rb
• Appropriate out.osw have been committed
• Test is stable
• Object is tested in autosize_hvac as appropriate
• The appropriate labels have been added to this PR:
  • One of: NewTest, TestFix, NewTestForExisting, Other
  • If NewTest: add PendingOSM or AddedOSM

[joseph-robertson]

Have we verified equivalent results across the Gem::Version.new('3.4.0') switch?