update workshop materials

[wangcj05]

---

Issue Description

What did you expect to see happen?

The workshop should be up to date.

EDIT @alfoa : All the inputs in the workshop material should be part of our regression test system.

What did you see instead?

It is quite old now

Do you have a suggested fix for the development team?

Please attach the input file(s) that generate this error. The simpler the input, the faster we can find the issue.

---

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?

[alfoa]

@wangcj05 I added the following sentence as well:
All the inputs in the workshop material should be part of our regression test system.

[alfoa]

Closure checklist passed....

[wangcj05]

Email regarding this is sent to raven users, and the proposed email is:

Dear Users,
We recently realized that some tests for the RAVEN workshops are outdated and can not be executed. This issue has been resolved with PR#800 and is the modifications are currently available in the devel branch. Now all the tests under raven/doc/workshop are tested in the regression test systems. In this case, all the tests will be updated with any changes we made in the our devel branch.

Please let us know if you have any questions regarding these changes.

[PaulTalbot-INL]

Could we put a more positive spin on that, or did it already send?

If we highlighted more than "all workshop materials have been updated to the current RAVEN version and are tested in the regression system" instead of "we noticed a bunch weren't working", maybe that would highlight the contribution more?

[wangcj05]

I have sent it out already.

…

________________________________ From: Paul Talbot <[email protected]> Sent: Thursday, September 27, 2018 3:29:40 PM To: idaholab/raven Cc: Congjian Wang; Mention Subject: Re: [idaholab/raven] update workshop materials (#796) Could we put a more positive spin on that, or did it already send? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_idaholab_raven_issues_796-23issuecomment-2D425249357&d=DwMCaQ&c=54IZrppPQZKX9mLzcGdPfFD1hxrcB__aEkJFOKJFd00&r=vJsbMjnzR6ErmdvVqv2kNhwbKhk1o91w6B8VQ4EHCto&m=JCc8TBzKdFHD5B2l0DH6BVwFIFEyC68AHiEukuf4gjE&s=PQ9N0FDzQ4YPjjVqZ1YvrB_XbDAx0HCQ2fEptAoi9aM&e=>, or mute the thread<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AG-2D1712UEm7KyX2kC0Vfomb6XvtBjd-2DAks5ufUNEgaJpZM4WyVws&d=DwMCaQ&c=54IZrppPQZKX9mLzcGdPfFD1hxrcB__aEkJFOKJFd00&r=vJsbMjnzR6ErmdvVqv2kNhwbKhk1o91w6B8VQ4EHCto&m=JCc8TBzKdFHD5B2l0DH6BVwFIFEyC68AHiEukuf4gjE&s=-KDLZ7geXBlujhDtUPT9ZbqGEO7a9AujAhvYyk8KuCw&e=>.