[UNDER-DISCUSSION] Standardize the way to handle input files for Codes

[wangcj05]

---

Issue Description

Currently, there are no specific links between the input files and codes, especially for HybridModel, LogicalModel, EnsembleModel and CodeInterfaces. We need to standardize the way to handle this situation to increase the usability of the code.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

---

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?

[wangcj05]

Based on the raven team discussion, we also need to make some improvement on the Dummy Inputs that are currently required, but not actually used by the code.

[wangcj05]

Several options:

1. addition attribute for Input under Steps:
   
   May require significant modifications.
2. addition attribute for Input under Files:
   
   Minor modifications, but same input file can not be used for multiple models
3. addition node under Codes
   Code block can not be reused by other steps with different input files.

[wangcj05]

archived