NatLabRockies / NatLabRockies/EnergyPlus

Review whether PLR or RTF should be used to scale source-side flows of equipment

Open
#9,986 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
1.6k
Forks
490
Avg merge
6d 21h
Merged PRs (30d)
22

Description

Issue overview

Related to #9966, there is a question about whether the source-side flows of a refrigerant cycle system (e.g., WSHP, heat recovery chillers), should be scaled by PLR (as they are now) or RTF (reflecting the operation of the compressor adding heat to the source side). If the source side flow cycles, it should maybe operate in coordination with the run time of the compressor, and not necessarily the load.

If this is the case, it will likely require changes in several objects that should handled at the same time.

Details

Some additional details for this issue (if relevant):

  • Platform (Operating system, version)
  • Version of EnergyPlus (if using an intermediate build, include SHA)
  • Unmethours link or helpdesk ticket number
Checklist

Add to this list or remove from it as applicable. This is a simple templated set of guidelines.

  • Defect file added (list location of defect file here)
  • Ticket added to Pivotal for defect (development team task)
  • Pull request created (the pull request will have additional tasks related to reviewing changes that fix this defect)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin with related issue #9966 and the existing source-side flow behavior for WSHP and heat recovery chillers. Compare PLR-based scaling with compressor runtime and RTF behavior, then identify the affected objects. Done means the choice is documented and the affected objects are handled consistently, with a defect file added if applicable.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
backend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.