adding IDF variable reporting code to OS via measure?
I have a swath of e+ output:variables I'd like to add to the reporting of an OS run. Does anyone has a favorite way of doing that?
Currently I'm post-processing by simulating the OS model, then adding my variables (IDF code) to the generated out.idf, then re-running the out.idf. I'm sure there's a slicker method. I have used the measure: addOutputVariable in the past, but it seems cumbersome to repeat that more than a few times.
Is there perhaps another measure out there that people use just to load in IDF code to the OSM, pre-run? This might be an excuse to write my first measure, but I'd be surprised if I'm the first to think this is a good idea.
Or, if there's an even better (and obvious) workflow, I'd be interested in that, too.
Looks like a duplicate of this post
As far as writing a measure to inject raw IDF text, you can ask that in a different question, but for the short answer look at this tariff measure. It grabs an IDF file out of the measures resource folder and imports specific types of IDF objects. It could import all IDF objects and could pull them in from any file on your computer vs. the resources directory (although that last part is problematic for cloud simulations).
@David Goldwasser it seems to me @Nick N is asking a different question than the one you linked, since he mentions having used the Add Output Variable measure, but is seeking an alternative to that workflow.
Indeed - we're taking the variables output from the simulation run and feeding them into another environment for modeling of a different (building-integrated) system. I had thought about that tariff measure earlier, but hadn't had the chance yet to learn if it was generally pulling in IDF code, or if it was selecting specific objects (which you mention it does). I'll look into it--either way, a good place to start.
Turns out I add everything from the file. I think I was just being selective in the arguments section to populate a choice list of possible tariffs by fuel.