Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TASK] Allow a variable/data object as an input to alpha #50

Open
10 tasks
Jderrill opened this issue Mar 28, 2022 · 1 comment
Open
10 tasks

[TASK] Allow a variable/data object as an input to alpha #50

Jderrill opened this issue Mar 28, 2022 · 1 comment
Labels
task New feature or request

Comments

@Jderrill
Copy link


Issue Description

Is your feature request related to a problem? Please describe.
I have a raven -> python -> teal workflow that will incur cost at different times based on the inputs that come from the RAVEN sampler. For example, the cost kicks in at year 5 in one case, but year 6 in another. The other years are zero cost. In a simple run I would use alpha as the flag so TEAL knows when to apply cost (ie 0 0 0 0 0 -1 0), but I can't have that exist statically in the TEAL xml when it may change based on sampled inputs.

Describe the solution you'd like
The ability to manipulate alpha from outside of the TEAL xml. In practice, I am not sure how this would work. Could be some type of adder to the XML?


For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

  • 1. Is it tagged with a type: defect or task?
  • 2. Is it tagged with a priority: critical, normal or minor?
  • 3. If it will impact requirements or requirements tests, is it tagged with requirements?
  • 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
  • 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

  • 1. If the issue is a defect, is the defect fixed?
  • 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
  • 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
  • 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
  • 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
@Jderrill Jderrill added the task New feature or request label Mar 28, 2022
@alfoa
Copy link
Collaborator

alfoa commented Oct 10, 2023

@dylanjm @worseliz @wangcj05 @AaronEpiney @GabrielSoto-INL It would be very nice if this becomes possible soon . Any plan for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants