Skip to content

Fixes #11

Benoît LÉ requested to merge correctIssue11 into master

Added a tls_geom_representation parameter

This parameter is a "short cut" to set tls_geom_interface and use_enrichment and fast_marching_modal_space, which depend on each other most of the time. tls_geom_representation can have the following values:

  • single_cut : single cut + Lagrangian computation of non local fields (corresponds to tls_geom_interface = 0, use_enrichment = 3 and fast_marching_modal_space = 0)

  • double_cut : double cut + Lagrangian computation of non local fields (corresponds to tls_geom_interface = 2, use_enrichment = 5 and fast_marching_modal_space = 0)

  • double_cut_FM : double cut + Fast Marching modes computation of non local fields (corresponds to tls_geom_interface = 3, use_enrichment = 5 and fast_marching_modal_space = 0)

If tls_geom_representation has one of this values, the values of tls_geom_interface, use_enrichment and fast_marching_modal_space will be automatically set. Otherwise, if "tls_geom_representation = custom" the user has to choose (carefully) these values. This last case can be useful to test old historical versions, or to test new algorithms/methods if some are implemented in the future.

It was chosen by the author of this commit not to update the test cases, by removing tls_geom_interface, use_enrichment and fast_marching_modal_space from the damageinfo.dat file, because it would imply that these parameters are "obsolete", which could still be discussed ? This could be done in the future.

Merge request reports