Example to use the ReplaceOpenstudioModel measure

edit

David is correct regarding PAT support for attaching/uploading resources files. The SEB example projects in the PAT repository provide examples of this.

@Chienman The measure you are using appear to be from the 1.x PAT interface and was not intended for use outside of the PAT interface. I have an un-publixhed measure that I can clean up this weekend that will replace the building, but not simulation settings and weather data, will that work in your case or do simulation settings vary between models?. Also do any of your models have VRF systems? That is know issue with the measure I plan to publish? You can also use the PAT 2.1.1 interface instead of the spreadsheet, as it supports replacing models in the interface.

Hi David, we would very much appreciate you cleaning up the measure for use in the spreadsheet. We do not need the ability to modify simulation settings or weather data...just the osm model. We will be running sometimes up to 1000 simulations so it would extremely valuable to have only one spreadsheet, and 1000 osms referenced as opposed to 1000 spreadsheets/1000 osms.

We would like to use the VRF measure along with the replace OS model measure.If it's helpful, the number of zones in the model will not change for a single project (set of runs).

In other words, we won't be using the replace model measure with say an "H" shaped building and an "L" shaped building within the same project (spreadsheet).

Use of PAT 2.0 has been suggested to use a number of times, unfortunately that is not an option. Let me explain why. This platform we are developing for Perkins+Will is designed to use a variety of geometry interfaces like Grasshopper, but more importantly a web-based interface similar to VirtualPulse. The process must be fully automated...architect puts inputs into GUI, we generate OSM files and spreadsheet, push to a separate "pre-processing" server on AWS, and push the zips from the pre-processing server so the architect doesn't have to store measures or weather files on their computer.

So there cannot be a step where PAT is launched and things are manually specified. Is it planned to enable an API to PAT that we may be able to use in the future? It appears as though the spreadsheet will at some point become obsolete, which will be big problem for us unless another option we can automate to launch to OS is provided.

PAT (like the Spreadsheet) is a means of authoring the OSA file. Unlike the Spreadsheet, the input forms are structured and constrained to reduce the possibility of user input error. PAT also streamlines running things from a typical user's perspective - e.g. no rake commands. Both PAT and the Spreadsheet OSAs are consumed by the OpenStudio Meta CLI, so however you author that input file is really up to you as a developer. Cracking open the developer console in PAT and running an analysis will show you how the Meta CLI is called. Mimic that and you can do things however you want.

@bwelle, try the updated measure I posted to slack that uses `runner.workflow.findFile(external_model_name)' to find the file. As a result the measure argument now just requires the file name and extension.

I tested it in PAT with the file in 'seeds' directory, but in theory should work with Analysis Spreadsheet if setup for 2.x workflow. I think 'seeds' or 'resources' directory should be fine.

Ok, we ran the measure. It fails. Here's what we have. We use the OS spreadsheet here:

https://dl.dropboxusercontent.com/u/1...

We create a directory called osm_models to be put under "lib/osm_models, and zip up all the OSM models to go there from a directory called "Resources" on our own server.

Then in variables tab using your new measure, we will simply put our discrete OS model names, not the path.

We have confirmed that the OSM models from our server make their way to ../lib/osm_models/ on the OS server. We log onto OS server and see them there.

but your measure can't find them on the OS server under ../lib/osm_models/