Add risk to dd

[adrianaghiozzi]

No description provided.

[orso82]

@adrianaghiozzi if you want to add the model name, we should try to conform to what IMAS generally does for all of its IDSs. I'll add some logic to generate_dd to copy the .code tree under the IDSs that we have added. This should allow you to use costing.code.name.

[adrianaghiozzi]

@orso82 Thanks, that would be great - this is just needed for the risk actor because the costs are grouped differently depending on whether it's ARIES or Sheffield (costing each coil system separately vs. all together) so the model determines how many fields are needed in dd.risk.engineering.loss

[orso82]

Uhm... I have not taken a look at the code, but it sounds like you are hardcoding the number of fields based on the model, which is definitely not a robust thing to do. Perhaps it would be best to just pick a model (say ARIES), and use the TF costs from that model for the evaluation of risk.

[codecov]

Codecov Report

Attention: Patch coverage is 60.00000% with 52 lines in your changes missing coverage. Please review.

Project coverage is 42.94%. Comparing base (13b7ff6) to head (30f66ef).

Files with missing lines	Patch %	Lines
src/dd.jl	60.00%	52 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master      #32      +/-   ##
==========================================
+ Coverage   42.87%   42.94%   +0.07%     
==========================================
  Files          14       14              
  Lines       30797    30926     +129     
==========================================
+ Hits        13203    13280      +77     
- Misses      17594    17646      +52     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.