1. 27 Feb, 2020 1 commit
  2. 14 Jun, 2019 1 commit
  3. 25 Feb, 2019 1 commit
  4. 29 Jan, 2018 1 commit
  5. 28 Nov, 2016 1 commit
    • Alexis SALZMAN's avatar
      Mainly adapting to new FM interface to treat GAMAIN and avoid prb · 89ca0c12
      Alexis SALZMAN authored
      dam_pull_out
      ============
      Adapting to para version
      
      FastMarchingInterface,TLSGeom,TLSSolver
      =======================================
      Modify groups (sm, sub mesh) to enter FM with known fixed and volatile
      values. This is following new FM interface. It correct bug with previous
      interface where progression of the front was stopped by re-initialisation
      process (all new variation of phi removed by fast marching).
      Now buildBndIntNonlocal (TLSGEOM) is creating 2 set (bnd_part_nonlocal
      and bnd_nonlocal) in replacement of the original bnd_nonlocal. Those
      sets split boundary of non local zone in :
      * boundary with local mesh element (bnd_nonlocal)
      * boundary with part boundary (bnd_part_nonlocal)
      Has before it is do_bnd_in that control if we create bnd_part_nonlocal or
      not by calling GetBoundary or GetInteriorBoundary.
      In GetBoundary a dirty hack is used to identify part boundary and remove
      Gama_c.
      When do_bnd_in is 0 bnd_part_nonlocal exist but is empty.
      
      For FM, bnd_part_nonlocal is used has known volatile value. Says those
      part boundary value may or may not be re-initialized by FM. In the
      latter case those values are used for velocity computation as new extra
      modes with their values unmodified. This imply that on part
      boundary the level set live its own life when phi gradient enter the
      part.
      
      Unfortunately as can be seen, for now, in new dam_gamain test, setting
      bnd_part_nonlocal as volatile values may stop progression of the front
      just like before when all modified values are reset by FM.
      
      N. Chevaugeon suggested to create only volatile values for non modified
      values (values not updated during current time step). This look like a
      promising solution because removing these values from bnd_part_nonlocal
      and put them in bnd_nonlocal force them to be still present in velocity
      computation. It ensure that variation of phi is not destroyed. But it
      does not insure anymore that phi gradient norm is 1 around those values.
      This somehow must be the case when gradient direction start to be collinear
      to part boundary. In that case epsilon_ratio was supposed to do the job
      but for rather blunt variation of phi it is not clear if this will fits
      ours needs. So filtering like that bnd_part_nonlocal seems interesting.
      TODO
      
      About epsilon_ratio it have been forced to zero because really strange
      result where obtain with it (non same result in case where
      bnd_part_nonlocal is empty, non deterministic computation !???).
      To be analyzed.
      
      dam_gamain
      ==========
      This test case is to check if and how gamin feature works.
      It is a simple plate with a shear loading that force creation of crack
      with an angle of -45 degres (x axes). A default( removing of 2 elements)
      is placed in the diagonal of the plate a little closer to left upper
      corner. Mesh is regular and chosen to intentionally offers a line of
      nodes from default to corner. lc is chosen rather big so that number of
      element per lc is important.
      
      Without gamin non-local zone progress toward corner. When reaching
      part boundary modification of phi on it are clearly done by FM re-init only.
      It arrive to a point where bluntly in on step all corner is extra damaged (phi>lc).
      With gamain when reaching part boundary modification comes clearly from
      phi update in far more slower way. Crack continue on the diagonal.
      Unfortunately process is stopped by the case of delta-phi removed by FM.
      (see above for perspectives)
      
      In both case it is not clear how boundary condition have to be handle in
      omega+ zone. Without treatment like here it impose force on almost
      damaged material which induce maybe other estimate strain. To be check.
      89ca0c12
  6. 22 Jul, 2016 1 commit
    • Kévin Moreau's avatar
      This commit bring all this changes · 90d823ac
      Kévin Moreau authored
      * add an epsilon_ratio (between 0 and 1) in order to control the fmeik internal epsilon involved when comparing
      scalar values (a < b + epsilon is now a <b + epsilon_ratio*"edge length")
      
      it affects:
        - FastMarchingInterface.h
        - TLSSolver.{h,cc}
        - FormulationQSRemeshAniso.{h,cc}
      
      * modify anticipated end of program: now lambda doesn't have to belong to [0, 1].
      
      it affects:
        - FormulationQS.cc
      
      * change dissipated energy calculation. It is based on the primitive of function h(d).
      
      it affects:
        - FormulationQS.cc
        - MaterialElasticDamage.cc
        - MaterialFunction.{h,cc}
      
      * compute nonlocal part bounding box
      
      it affects:
        - TLSGeom.{h,cc}
        - TLSSolver.cc
      
      * minor simplification when transfering phi field, now only "int_duplicated" region is used.
      
      it affects:
        - MeshGeneration.{h,cc}
        - TLSGeom.cc
        - Formulation.cc
        - TLSSolver.cc
      
      * bug correction when transfer boundary and interior "in" after remeshing.
      
      it affects:
        - TLSGeom.cc
      
      * bug correction in correctLevelSetField: add a forgotten absolute value.
      
      it affects:
        - TLSSolver.cc
      
      * place guards with error message to help user detect bugs
      
      it affects:
        - FormulationQS.cc
        - TLSSolver.cc
      90d823ac
  7. 17 Jun, 2016 1 commit
    • Kévin Moreau's avatar
      This commit mainly · 49559c48
      Kévin Moreau authored
       * Implements Gamma_in using the fast marching
       * Adds parameter to activate/desactivate Gamma in
       * Merges Carole work
       * Removes some old stuff not maintained in atomic_test/
       * Defines new parameters in test case infinite_dam_notch
       * Cleans up (unifies) info.dat files in test/
       * Fixes a recent bug due to small refactoring in TLSGeom
       * Takes into account element orientation when enriching
       * Correct an old bug in Util.cc (it had no effect exept recently in Carole's work)
       * Improves superposition procedure using integration by part
       * Improves README
       * Adds energetic dissipation to AsymElastoDam
      49559c48
  8. 07 Jun, 2016 1 commit
  9. 03 Jun, 2016 1 commit
  10. 30 May, 2016 1 commit
  11. 03 May, 2016 1 commit
  12. 12 Feb, 2016 1 commit
    • Kevin Moreau's avatar
      New stable release. · 7e38f088
      Kevin Moreau authored
      Major changes:
        - integ_mesh is computed only on fully damaged support,
        - comp_mesh adds new vertices and edges inside the fully damaged zone and then erase useless entities,
        - the code is almost 3D,
        - algorithm part of the code moved to TLSAlgorithm, in order to share it with DamageBand, DamageBandDyn...
      
      Minor changes:
        - small improvement of Export,
        - get rid of every xIter except in TLSGeom so that if someone wants
        to use other kind of iterators (that deref in mEntity*),
        - dispatch code in several different files.
      
      TODO:
        - remove the TODO spread in the code (boring),
        - finish the cut of tetrahedra in Cutter,
        - clean deletion of mEntity* after adpating comp_mesh (I forgot to do this => memory leaks),
        - get rid of mEntity* (is it even possible?).
      
      
      
      
      git-svn-id: https://svn.ec-nantes.fr/eXlibris/Applis/TLSDuctile@2261 fbbead7c-fb4d-4173-aa67-51132c73c120
      7e38f088