[TASK] Ray should use its own temporary directory

[joshua-cogliati-inl]

---

Issue Description

Is your feature request related to a problem? Please describe. We noticed that ray was trying to write to the file /tmp/ray/dashboard_url but it failed because another user already had created the file. This might be a problem.

Describe the solution you'd like It would be useful if we could tell ray to choose a temporary directory that is unique and not likely to be used already.

There is an option in Ray to disable the instance of the dashboard (used to monitor the resources on the fly). The setting is in Ray.init (double check that this is not already used in RAVEN)

---

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]

@alfoa

[alfoa]

@joshua-cogliati-inl can you address it?