TLSImplicit issueshttp://git.gem.ec-nantes.fr/eXlibris/XTLS/TLSImplicit/-/issues2020-01-08T15:23:02Zhttp://git.gem.ec-nantes.fr/eXlibris/XTLS/TLSImplicit/-/issues/22Bug when using single cut with update_displacement_field = 12020-01-08T15:23:02ZBenoît LÉBug when using single cut with update_displacement_field = 1When running a computation with the single cut and with the option update_displacement_field = 1 (use of previous displacement field at the begining of a Newton Raphson loop), the computation may abort in the xtls::TLSEnrichment_3::updat...When running a computation with the single cut and with the option update_displacement_field = 1 (use of previous displacement field at the begining of a Newton Raphson loop), the computation may abort in the xtls::TLSEnrichment_3::updateValues.
A "quick" fix is to use update_displacement_field = 0, in order not to use the updateValues function. Note that this problem has not been observed with the double cut (tested on the Lshaped test case, with 8 different computations for the single cut and 8 different computations for the double cut).http://git.gem.ec-nantes.fr/eXlibris/XTLS/TLSImplicit/-/issues/18DAMAGEDZONELAW2018-09-07T13:41:23ZBenoît LÉDAMAGEDZONELAWIn specific_to_devel_stage.h, the macro DAMAGEDZONELAW is used:
- To switch between some evaluators inside compute_elastic (it was some king of "ancestor" of the class xEnergyModel) (for instance the Anisotropic evaluators ???)
- To swit...In specific_to_devel_stage.h, the macro DAMAGEDZONELAW is used:
- To switch between some evaluators inside compute_elastic (it was some king of "ancestor" of the class xEnergyModel) (for instance the Anisotropic evaluators ???)
- To switch between different behavior inside the fully damaged zone. This is done directly into the implementation of the evaluators of the stress tensors, tangent matrix, etc, in xEnergyModel.cc.
In the future, DAMAGEDZONELAW should be removed:
- xEnergyModel can eventually be used to switch between the evaluators
- If DAMAGEDZONELAW (which is specific to DamageBand) is removed, xEnergyModel could be put in Xfiles (for instance), to be usable in any other Appli than DamageBand
As there is no urgent need for the moment, things are kept as is, but if someday the evaluators of xEnergyModel are needed in another Appli, the cleaning/transfer will have to be done.http://git.gem.ec-nantes.fr/eXlibris/XTLS/TLSImplicit/-/issues/15Differences in exports between Lagrangian and Fast Marching computation of no...2018-04-26T08:04:21ZBenoît LÉDifferences in exports between Lagrangian and Fast Marching computation of non local fieldsSome quantities are exported only for one method and not the other (for instance, Y can be exported only with the Lagrangian method). Also, some exports have different names: for instance, Y is exported using the keyword Y_mean with the ...Some quantities are exported only for one method and not the other (for instance, Y can be exported only with the Lagrangian method). Also, some exports have different names: for instance, Y is exported using the keyword Y_mean with the Lagrangian method, and with the keyword Y_bar with the Fast Marching method.http://git.gem.ec-nantes.fr/eXlibris/XTLS/TLSImplicit/-/issues/12Parallel resolution2018-09-04T13:28:48ZBenoît LÉParallel resolutionNo parallel resolution is available anymore due to change to the new eXlibris parallel branch.
All strategies have to be recoded correctly.
Delayed until full distributed model is available.No parallel resolution is available anymore due to change to the new eXlibris parallel branch.
All strategies have to be recoded correctly.
Delayed until full distributed model is available.Alexis SALZMANAlexis SALZMANhttp://git.gem.ec-nantes.fr/eXlibris/XTLS/TLSImplicit/-/issues/4xIteratorRegion2018-04-26T08:04:22ZAlexis SALZMANxIteratorRegionIf those tools remains, a cleaning of parametis must be done. Use of new parmetis interface must be done.If those tools remains, a cleaning of parametis must be done. Use of new parmetis interface must be done.http://git.gem.ec-nantes.fr/eXlibris/XTLS/TLSImplicit/-/issues/3readReferenceLoad in DamageEvals2018-04-26T08:04:22ZBenoît LÉreadReferenceLoad in DamageEvalsBe careful: reference loading Fref is obtained by function readReferenceLoad in DamageEvals.h/cc. Currently the main.dat file is parsed, then the numerical value corresponding to the last occurrence of one the following keyword is taken...Be careful: reference loading Fref is obtained by function readReferenceLoad in DamageEvals.h/cc. Currently the main.dat file is parsed, then the numerical value corresponding to the last occurrence of one the following keyword is taken for the reference load (even if it is commented) : “ TRACTION_X” , “ TRACTION_Y” , “ TRACTION_Z” , “ PRESSURE” and “ STRESS.
Possible solution for readReferenceLoad implementation: read Fref directly from the xData, for instance, by giving to readReferenceLoad physical ID of boundary where Fref is applied, instead of parsing the main.dat.