Indeed we deprecated removed the residential OpenStudio measures. They haven’t really been under active development for a while. This was a difficult decision, but they proved to have some significant problems. decision we went back and forth on. In theory, OS measures are supposed to be able to run independent of each other. However, due to the nature of these measures it was necessary to run them in a specific sequence because downstream measures often depended depend on the results of previous measures. It also meant we had to pass and track a lot of metadata meta data down the measure pipeline. In addition, the measures incurred high development/maintenance costs and were slow to run.

To solve some of these problems we have migrated the capabilities from those measures into a new single measure (available (under development at https://github.com/NREL/OpenStudio-HPXML). This takes a simplified HPXML description of a house and builds an OpenStudio model from it in one step. It ends up reducing the possibilities of errors in sequencing measures incorrectly and also reduces edge cases where measures are used in unanticipated ways. The measure also has far more capability (in terms of the residential technologies that can be modeled) and the workflow runtimes are significantly faster. The measure is already being used as the basis for BEopt, our work for DOE’s Home Energy Score, ResStock, and ERI calculations, the Energy Rating Index calculation, among a few other projects, and is used by several third-party software developers.projects. We expect a release of the measure with documentation in the next couple months

Note that while you can generate the residential HPXML file any way that you want for use with the above measure, there is we're also a single planning to create an OpenStudio measure over the next year that generates the file from inputs similar to the previous residential measures.

An archive of In the meantime if you just need access to the previous residential measures measures for your work, they are still being used in ResStock. You can be found in an older find the latest version of ResStock them here.. We are planning on deprecating their use and moving to the HPXML workflow for that project next year.

Indeed we removed the residential OpenStudio measures. They haven’t really been under active development for a while. This was a decision we went back and forth on. In theory, OS measures are supposed to be able to run independent of each other. However, due to the nature of these measures it was necessary to run them in a specific sequence because downstream measures depend on the results of previous measures. It also meant we had to pass and track a lot of meta data down the measure pipeline.

To solve some of these problems we have migrated the capabilities from those measures into a new single measure (under development at https://github.com/NREL/OpenStudio-HPXML). This takes a simplified HPXML description of a house and builds an OpenStudio model from it in one step. It ends up reducing the possibilities of errors in sequencing measures incorrectly and also reduces edge cases where measures are used in unanticipated ways. The measure also has far more capability (in terms of the residential technologies that can be modeled) and the workflow runtimes are significantly faster. The measure is already being used as the basis for our work for DOE’s Home Energy Score, ResStock, DOE's Weatherization Assistant, and the Energy Rating Index calculation, among a few other projects. We expect a release of the measure with documentation in the next couple months

Note that while you can generate the residential HPXML file any way that you want for use with the above measure, we're also planning to create an OpenStudio measure over the next year that generates the file from inputs similar to the previous residential measures.

In the meantime if you just need access to the previous measures for your work, they are still being used in ResStock. You can find the latest version of them here. We are planning on deprecating their use and moving to the HPXML workflow for that project next year.

Indeed we removed the residential OpenStudio measures. They haven’t really been under active development for a while. This was a decision we went back and forth on. In theory, OS measures are supposed to be able to run independent of each other. However, due to the nature of these measures it was necessary to run them in a specific sequence because downstream measures depend on the results of previous measures. It also meant we had to pass and track a lot of meta data down the measure pipeline.

To solve some of these problems we have migrated the capabilities from those measures into a new single measure (under development at https://github.com/NREL/OpenStudio-HPXML). This takes a simplified HPXML description of a house and builds an OpenStudio model from it in one step. It ends up reducing the possibilities of errors in sequencing measures incorrectly and also reduces edge cases where measures are used in unanticipated ways. The measure also has far more capability (in terms of the residential technologies that can be modeled) and the workflow runtimes are significantly faster. The measure is already being used as the basis for our work for DOE’s Home Energy Score, DOE's Weatherization Assistant, and the Energy Rating Index calculation, among a few other projects. We expect a release of the measure with documentation in the next couple months

Note that while you can generate the residential HPXML file any way that you want for use with the above measure, we're also planning to create an OpenStudio measure over the next year that generates the file from inputs similar to the previous residential measures.

In the meantime if you just need access to the previous measures for your work, they are still being used in ResStock. You can find the latest version of them here. We are planning on deprecating their use and moving to the HPXML workflow for that project next year.