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] Optimize vectors of values as variable sets #2385

Open
5 of 10 tasks
PaulTalbot-INL opened this issue Oct 7, 2024 · 0 comments
Open
5 of 10 tasks

[TASK] Optimize vectors of values as variable sets #2385

PaulTalbot-INL opened this issue Oct 7, 2024 · 0 comments
Labels
priority_minor task This tag should be used for any new capability, improvement or enanchment

Comments

@PaulTalbot-INL
Copy link
Collaborator


Issue Description

Currently the Optimizer can nominally take a vector of variable values using the syntax (for example, note shape parameter):

<variable name="source1_capacity" shape="10">
  <distribution>source1_capacity_dist_cat</distribution>
</variable>

However, samples from the optimizer appear to place the same value in all the spots within the vector, and changing that value simultaneously changes all the values in the vector. In reality, I want the optimizer to treat each element as a different variable. Investigations ongoing.


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?
@PaulTalbot-INL PaulTalbot-INL added priority_minor task This tag should be used for any new capability, improvement or enanchment labels Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority_minor task This tag should be used for any new capability, improvement or enanchment
Projects
None yet
Development

No branches or pull requests

1 participant