First time here? Check out the Help page!
1 | initial version |
PLEASE bring back ERI. ERI is very important as a means of gauging whether a package is code compliant, since one can compare the rating to the ERI path requirements for one's region.
I understand it's a bit of a moving target, but we only need ERI, not full HERS scores. Even if not making the minor updates for the more recent version of IECC 2018, keeping the old version would still be helpful since they typically don;t very that much. Simply indicate which version is being exported. For example, (depending on the version) REM/Rate provides 2015, 2018 and 2021 ERI as well as HERS.
2 | No.2 Revision |
PLEASE bring back ERI. ERI is very important as a means of gauging whether a package is code compliant, since one can compare the rating to the ERI path requirements for one's region.
I understand it's a bit of a moving target, but we only need ERI, not full HERS scores. Even if not making the minor updates for the more recent version of IECC 2018, IECC, keeping the old version would still be helpful since they typically don;t very don't vary that much. Simply indicate which version is being exported. generated. For example, (depending on the version) REM/Rate provides 2015, 2018 and 2021 ERI as well as HERS.
3 | No.3 Revision |
PLEASE bring back ERI. ERI is very important as a means of gauging whether a package is code compliant, since one can compare the rating to the ERI path requirements for one's region.
I understand it's a bit of a moving target, but we only need ERI, not full HERS scores. Even if not making the minor updates for more recent IECC, keeping the old version would still be helpful since they typically don't vary that much. Simply indicate which version is being generated. For example, (depending on the version) REM/Rate provides 2015, 2018 and 2021 ERI as well as HERS.
After all, NREL already has a separate project for calculating ERI's that it should be possible to leverage if the existing system is different and too crufty: https://github.com/NREL/OpenStudio-ERI
4 | No.4 Revision |
PLEASE bring back ERI. ERI is very important as a means of gauging whether a package is code compliant, since one can compare the rating to the ERI path requirements for one's region.
I understand it's a bit of a moving target, but we only need ERI, not full HERS scores. Even if not making the minor updates for more recent IECC, keeping the old version would still be helpful since they typically don't vary that much. Simply indicate which version is being generated. For example, (depending on the version) REM/Rate provides 2015, 2018 and 2021 ERI as well as HERS.
After all, NREL already has a separate project for calculating ERI's that it should be possible to leverage if the existing system is different and too crufty: all: https://github.com/NREL/OpenStudio-ERI
5 | No.5 Revision |
PLEASE bring back ERI. ERI is very important as a means of gauging whether a package is code compliant, since one can compare the rating to the ERI path requirements for one's region.
I understand it's a bit of a moving target, but we only need ERI, not full HERS scores. Even if not making the minor updates for more recent IECC, keeping the old version would still be helpful since they typically don't vary that much. Simply indicate which version is being generated. For example, (depending on the version) REM/Rate provides 2015, 2018 and 2021 ERI as well as HERS.
After all: https://github.com/NREL/OpenStudio-ERI