Upgrade measure costing
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
The issue names no files, tests, or entry points. Start by reviewing the repository structure and the openstudio-standards model mentioned in the scope, then determine where a cost engine and costing measure would fit. Done would require an agreed approach that accounts for location-specific data, proprietary costs, and the limits of zonal model accuracy.
Written by the indexing model from the issue text.
Description
There have been several requests to incorporate basic costing into measure packages.
Costing is tricky for several reasons:
- Our models make simplifications to geometry and HVAC system layouts. Measures based on building totals (envelope, window, total load) will be more accurate than measures that rely on accurate equipment sizes or counts (single zone HVAC). Until HVAC zoning and model geometry more closely matches reality, costing will be unreliable for any measure that depends on zonal system sizes and counts.
- Cost data is highly location specific and constantly changing
- Reliable cost data is proprietary and costly; even if we model costs accurately, it is not clear we would be able to share the results.
The feature scope includes:
- Incorporating a cost engine, potentially NRCAN's costing using RSMeans. This will likely be an openstudio-standards model.
- Creating a costing measure, or adjusting existing measures to add measure costs.
- Dominant language
- Ruby
- Stars
- 54
- Forks
- 28
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NatLabRockies/ComStock
-
Fresh comstockpostproc install fails on import: PyAthena 4.x requires SQLAlchemy 2 (AttributeError: sqlalchemy.types has no attribute DOUBLE)Possibly taken @JanghyunJK claimed this today. Openpostprocessing
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NatLabRockies/ComStock#473 ·
-
Sampling broken with dependency changesMay be free again @asparke2 claimed this 93 days ago, and no pull request is open. Openbug
NatLabRockies/ComStock#462 · 1 assignee ·
-
Update S3 workgroup in gap model queriesMay be free again @eringold claimed this 270 days ago, and no pull request is open. Open
NatLabRockies/ComStock#453 · 1 assignee ·
-
postprocessing
Difficulty 3/5 1-2 days Newbie friendliness 35/100
NatLabRockies/ComStock#452 ·
-
Postprocessing setup and READMEs out of dateMay be free again @ChristopherCaradonna claimed this 275 days ago, and no pull request is open. Openpostprocessing
NatLabRockies/ComStock#451 · 1 assignee ·
All issues in NatLabRockies/ComStock
Similar issues
-
Visual COBOL: missing 11.0 and 12.0, and 9.0 date differs from Rocket Software's lifecycle pageOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
endoflife-date/endoflife.date#11561 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug javascript
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
yegor256/netbout.rb#69 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yegor256/iccq.github.io#161 ·
Maintainers usually reply within 1 day