You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary of the topic to be discussed with the development team
In a TEA being conducted, there ends up being two resources demanded by the "grid" component. These resources are called electricty1 and electricity2. At this point in the workflow both resources are in the same units and their total activity needs to be accounted for in the cashflow.
Is there a functional difference between having the for Grid A take in electricity1 and electricity2 versus having Grid A take electricity1 and a new (dummy) Grid B take electricity2? I guess it would be up to the user to make sure Grid B is identical to Grid A.
@GabrielSoto-INL Good question and something I thought about. They would need to use the SyntheticHistory in both grids and could potentially do that. I just wonder if that would cause confusion to the user having to send electricity to two identical grids.
Under Discussion Topic
Summary of the topic to be discussed with the development team
In a TEA being conducted, there ends up being two resources demanded by the "grid" component. These resources are called
electricty1
andelectricity2
. At this point in the workflow both resources are in the same units and their total activity needs to be accounted for in the cashflow.Should a user be able to specify something like:
With the caveat that they are expected to be in the same units and we will not catch any errors due to un-matching units?
Describe the solution you'd like to be implemented
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.
For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.
task
issue?The text was updated successfully, but these errors were encountered: