[DEFECT] Pathing errors from check_py_coverage

[caleb-sitton-inl]

---

Defect Description

Describe the defect

What did you expect to see happen?

The check_py_coverage.sh script should run correctly irrespective of the current directory from which the script is run.

What did you see instead?

When the check_py_coverage.sh script is run from the coverage_scripts directory, errors regarding module importing and pathing are returned.

Do you have a suggested fix for the development team?

More cautious pathing in the coverage scripts should fix the issue.

Describe how to Reproduce Steps to reproduce the behavior:

1. Run cd HERON/coverage_scripts
2. Run ./check_py_coverage.sh

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

Platform (please complete the following information):

• OS: [e.g. iOS]
• Version: [e.g. 22]
• Dependencies Installation: [CONDA or PIP]

---

For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

• [x] 1. Is it tagged with a type: defect or task?
• [x] 2. Is it tagged with a priority: critical, normal or minor?
• [x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
• [x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
• [x] 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?