Room by Room Specific LPD Issue

edit

Spaces inherit loads data from the Space Type definition. Once set load in space types, you cannot change them in the individual spaces interface.

On a practical level, adding individual lights to each space is incredibly time intensive. If you want exact room-by-room wattages, I would suggest removing lighting definitions from your spaces types and adding a single light object per room which sums the lighting power in that room, calculated from a spreadsheet. You can automate this by exporting the space name and total wattage to a .csv file, then using a custom OpenStudio measure to read the .csv, loop through your spaces, and add the light object with the given wattage.

To build upon @mdahlhausen's answer in more specific terms, here's what I've been doing to automate this stuff:

• Create a spreadsheet with columns ["model_space_name", "watt", "hours"].
  • You can have several lines that have the same "model_space_name", the space will then get multiple Lights objects.
  • You could also include your multiplier here if you wanted to... In my spreadsheet I actually have more columns, for eg Fixture (eg 'Fluorescent Linear T8 590mm, 2-18 Watt, electronic ballast'), Count, W/fixture and I calculate "watt" by doing Count times W/fixture
• Use Roo to parse the Excel spreadsheet
  • I find this convenient exactly because I have multiple columns and formulas and I don't need to export a CSV each time I change it.
  • You could also just export your spreadsheet to CSV and use the built-in CSV module if you find this easier.
• Define a ScheduleRuset in my model to use as a default profile. That would be SecondarySchool Bldg Light in your example, let's call it light_sch going forward
• Loop on parsed rows (from Excel),
  • use model.getSpaceByName(row["model_space_name"]).get to get the corresponding space, and create a new lighting object (you need to create a OpenStudio::Model::LightsDefinition and a OpenStudio::Model::Lights that references it).
  • The real key point here is to scale to the SecondarySchool Bldg Light to get the correct number of hours while maintaining the same profile. For this, I leverage openstudio-standards' ScheduleRuleset.annual_equivalent_full_load_hrs. I store the initial eflh = light_sch.annual_equivalent_full_load_hrs. For the lighting objects, I clone this schedule, get the ScheduleDay attached to it (it helps if there's only one...) and scale each value entered accordingly by looping on day_sch.times.with_index (new_value = old_value * daily_h * 365 / eflh.to_f).
  • Neat trick: I rename the cloned schedule like #{light_sch.name} - #{daily_h} hrs/day, so that in the loop I can test whether I already created it or not to avoid duplicating it many times unnecessarily.