Model metadata to include output directory information

[cbroman-usnctech]

---

Issue Description

What did you expect to see happen?

Model output <DataOject> should include information regarding output data directory.

Output data is placed in a hierarchical data directories, i.e. optimization/b1_r1/output_data or sweep/1/output_data. From the SolutionExport stream .csv file there is not a convenient way to link back to the directory where the "raw" data is stored.

What did you see instead?

Model metadata adds a key such as dataDir (or dir) to link to the directory

Do you have a suggested fix for the development team?

i.e.

 obj           | dataDir                         | prefix  | batchId
 5.075957 | optimizeRun1/b1_r1/   | 1          | 1 

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

N/A

---

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?

[cbroman-usnctech]

Ping. @wangcj05 @mandd

[aalfonsi]

@wangcj05 @mandd do you think you guys can address this? If so, can you give us an ETA?

[wangcj05]

@aalfonsi I'm sorry there are other priorities that we need to work on. I would say I can start to look at this problem next week.

[aalfonsi]

@aalfonsi I'm sorry there are other priorities that we need to work on. I would say I can start to look at this problem next week.

@wangcj05 Thank you very much. We understand. Next week works great. Thank you again.

[cbroman-usnctech]

pinging @wangcj05 and @mandd if you might have capacity to work on this?