The damage case definition has been updated to add past desires and support future extensions.
Features of the new damage case definition:
- All damage cases from all modules are in 1 list, each damage case can be calculated in any module.
- Per damage case you can specify for which module it is meant, possibly for all 3 (Loading, Hydrotables, Probdam), you can set which damage cases you want to see in the list.
- The complex intermediate stages are stored with the damage case itself, you can create multiple damage cases with the same damaged compartments, but with different (or no) complex intermediate stages.
- The number of damage cases, the number of damaged compartments per damage case and the number of complex intermediate stages is unlimited.
- You can lock damage cases.
- Per damage case you can select a different set of damage stability criteria for the final and intermediate stages (e.g. inland waterway/sea).
- Per damage case you can make a different choice for the liquid level during the intermediate stages (equal/unequal everywhere).
- Per damage case you can set whether the higher sub-damages are to be calculated (thus also in Loading and Hydrotables), these are no longer generated as complex intermediate stages but calculated internally.
When you start Loading, Hydrotables or Probdam all damage cases of all modules are listed and put in a new file with extension .DAM. After the existing files .pre_2021 is put, but they remain saved.
The following files are grouped together:
– .SCA damage cases Loading
– .SCI damage cases Hydrotables (maximum allowable VCG calculation for damage stability)
– .PD2 damage cases Probdam
– .PD3 calculation results for reuse in Probdam
– .TSS complex intermediate stages
If the damage case are converted to the new format, they cannot be used in older versions of PIAS.