OpenStudio and Radiance lighting schedule export
Is there a way to apply the lighting schedules that are created by Radiance from one iteration to another? In other words, I have a model that has the envelope finalized, the only modifications I am making are to HVAC equipment. I could save a lot of time, and hard drive space, by running my first simulation with Radiance and then using the same lighting schedules created by that simulation in later simulations, instead of running the radiance simulation every single time I want to see the impact of changing a non-daylighting related parameter. Is this possible?
This would also be helpful for when I need to make modifications to the .idf file that I cannot make in OpenStudio. I would then be able to run a simulation directly in E+ with the Radiance lighting schedules.
You could always output the schedules to a file (csv or json) when running the Radiance measure and reimport them and apply to model (openstudio measure) before running the simulation.
Julien's point is well taken. The OpenStudio Radiance measure does save the shade schedules to CSV, but not the lighting schedules. Can I get a feature request up in here?
I have another feature request: could you update your picture to another john doe please?
@rpg777 Fix it!
@edixon16, I'm sure the measure mavens here could point you to something more concrete, but the general idea is you could write a custom measure that reads in your CSV and your model, gets the schedule(s) you wish to replace or update, and then applies them as a series of "OS:Schedule:FixedInterval" objects. Have a look at this script for sample code.
How do I get the CSV files? I have tried using the reporting measure ExportScheduleCSV and schedule_profile_report but it does not export the dimming schedules created by Radiance.
@Julien Marrec per your request, my profile pic has been updated to yet another image of Not Me.
@edixon16, yes, the Radiance-created lighting schedules are generated on the fly by that Ruby script I linked to, so you can't request them as an output variable or as part of a report measure, unfortunately. You could write them out yourself, though. The new schedule is created here, as an OpenStudio object. You could write it out as is, or to CSV or json, and then push it into other models. Does this make sense?
Yes, that makes sense now. I just started using OS a few months ago and have yet to create or modify my own measures so I may have to wait for this to be implemented. Although I am finding the solution to a lot of questions posted on here is usually creating a measure so I might have to start learning how to sooner rather than later.
Measures are what makes OS great. And it's really not that complicated, you can start by finding a measure that does soemthing similar and modify it slightly to achieve your goal. Doing a quick beginner tutorial on ruby is probably not a bad idea either
I was able to generate a csv file of the daylighting schedules. I tried importing an IDF with the Schedule:File objects I need for each schedule with both OS and the SketchUp plugin but it appears that this type of schedule can't be imported. Any suggestions for importing schedules to OS from a csv?