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

Issues with OPFLOW and SOPFLOW APIs not working as intended #121

Open
3 of 13 tasks
Jayapreethi opened this issue Feb 13, 2024 · 1 comment
Open
3 of 13 tasks

Issues with OPFLOW and SOPFLOW APIs not working as intended #121

Jayapreethi opened this issue Feb 13, 2024 · 1 comment
Assignees

Comments

@Jayapreethi
Copy link
Collaborator

Issue type

  • New feature
  • Bug
  • Discussion
  • Other

Relates to

  • OPFLOW
  • SOPFLOW
  • SCOPFLOW
  • TCOPFLOW
  • CMake build system
  • Spack configuration
  • Manual
  • Web docs
  • Other

Summary

Encountering issues with certain APIs in the OPFLOW and SOPFLOW are not working as intended.

Affected APIs

OPFLOW
opflow.set_lines_monitored([...])
opflow.set_lines_monitored(n, "file")

SOPFLOW
ScenarioFileInputFormat
ScenarioUncertaintyType

It needs to be tested to determine whether the issue also occurs with other users, or we should find a way to handle these APIs.

@Jayapreethi Jayapreethi changed the title Issues with opflow and SOPFLOW APIs not working as intended Issues with OPFLOW and SOPFLOW APIs not working as intended Feb 13, 2024
@cameronrutherford
Copy link
Contributor

Are you able to reproduce the failures with a python source code file? It would be good to have a minimum reproducer in order to others to test out your issues.

Additionally, once we have determined what missing features there are, we should add relevant tests to our infrastructure. Perhaps it would be easiest to add a failing test first to verify the issue as well before we go and add a fix to our API.

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

No branches or pull requests

4 participants