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.

Sign up for GitHub

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

Jump to bottom

[TASK] Update scipy and tensorflow #1882

Closed
10 tasks done
joshua-cogliati-inl opened this issue Jul 8, 2022 · 1 comment
Closed
10 tasks done

[TASK] Update scipy and tensorflow #1882

joshua-cogliati-inl opened this issue Jul 8, 2022 · 1 comment
Labels
priority_minor task This tag should be used for any new capability, improvement or enanchment

Comments

@joshua-cogliati-inl
Copy link
Contributor

joshua-cogliati-inl commented Jul 8, 2022 •
edited
Loading

Issue Description

Is your feature request related to a problem? Please describe.
The version of scipy and tensorflow in RAVEN is preventing newer pythons from being used.

Describe the solution you'd like
Update scipy and tensorflow

Describe alternatives you've considered
Keep being stuck at python 3.7

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?
@joshua-cogliati-inl joshua-cogliati-inl added priority_minor task This tag should be used for any new capability, improvement or enanchment labels Jul 8, 2022
@joshua-cogliati-inl joshua-cogliati-inl mentioned this issue Jul 8, 2022
Merged
9 tasks
@joshua-cogliati-inl
Copy link
Contributor Author

Fixed with #1973

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority_minor task This tag should be used for any new capability, improvement or enanchment
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@joshua-cogliati-inl