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

Outdated RAVEN code interface docs #666

Closed
10 tasks done
AaronEpiney opened this issue May 29, 2018 · 2 comments · Fixed by #668
Closed
10 tasks done

Outdated RAVEN code interface docs #666

AaronEpiney opened this issue May 29, 2018 · 2 comments · Fixed by #668
Assignees
Labels
manuals priority_critical task This tag should be used for any new capability, improvement or enanchment

Comments

@AaronEpiney
Copy link
Collaborator

AaronEpiney commented May 29, 2018


Issue Description

The docs have not been updated fro the conversion module in the RrR code interface. See test test_raven_running_raven_int_models.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 improvement?
  • 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 stable branch? If yes, is there any issue tagged with stable (create if needed)?
  • 5. If the issue is being closed without a merge request, has an explanation of why it is being closed been provided?
@PaulTalbot-INL
Copy link
Collaborator

Proposed email for PR merge:

Hello, RAVEN users!

As of merge #668, RAVEN's "devel" branch has received a couple notable updates.

First off, we understand the install and update process has been cumbersome, and we've worked to streamline it.

Now, to update RAVEN, the following actions are consistent across all platforms. From the "raven" folder (~/projects/raven might be different depending on where you installed it):

  • git checkout devel
  • git pull
  • ./scripts/establish_conda_env.sh --install
  • ./build_raven

That's it! Setting up the python environment is done entirely through "establish_conda_env.sh" and make is rolled into "build_raven". The appropriate libraries will be installed through conda to be current with the branch of RAVEN that has been checked out.

Secondly, we have updated several libraries to newer versions, including plotting tool matplotlib as well as numerical tools scipy and numpy. This significantly sped up some processes on Windows and keeps us up to date with critical changes.

As always, let us know if you run into any issues!

@wangcj05
Copy link
Collaborator

Issue closure checklist is satisfied.

@wangcj05 wangcj05 added the task This tag should be used for any new capability, improvement or enanchment label Jul 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
manuals priority_critical task This tag should be used for any new capability, improvement or enanchment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants