NatLabRockies / NatLabRockies/SAM

Improve consistency and labeling of escalation functions

Open
#2,106 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C++
Stars
486
Forks
219
Avg merge
10h 10m
Merged PRs (30d)
2

Description

Community solar analysis for bill savings requires some cross referencing between the TPO host model and the community solar model. This can be confusing, because the TPO lease and PPA escalation inputs do not apply inflation by default (this is consistent with the PPA inputs elsewhere) but the subscription revenue inputs in community solar do apply inflation by default.

Definitely label these inputs more clearly (the electricity rates page is a good example of a clear label)

Consider whether any of the escalation functions in community solar need to change (are these more similar to PPA agreements than costs?)

Workaround for now is to subtract inflation from the escalation number when applying it to the community solar inputs.

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

Start by comparing the community solar subscription revenue inputs with the TPO lease and PPA escalation inputs, using the electricity rates page as the labeling example. Determine whether the community solar escalation functions should follow PPA behavior or retain their current inflation defaults; done means the inputs are clearly labeled and the chosen behavior is consistent.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.