1. 07 May, 2020 3 commits
  2. 11 Mar, 2020 1 commit
  3. 27 Feb, 2020 1 commit
  4. 20 Feb, 2020 1 commit
  5. 03 Feb, 2020 1 commit
  6. 27 Nov, 2019 1 commit
  7. 20 Nov, 2019 1 commit
  8. 07 Aug, 2019 1 commit
    • Benoit LE's avatar
      Bug correction in exportOnSpace · 9d0cd807
      Benoit LE authored
      Corrected parenthesis bug in exportOnSpace function, in the version which is
      used to export xTensor2.
      
      Remark : It was quite surprising that the code could even
      compile before ...
      9d0cd807
  9. 30 Jul, 2019 1 commit
    • Benoit LE's avatar
      Added a toExport function to PostProcessing · b769d03c
      Benoit LE authored
      May be useful if exporting a certain quantity requires some computations, but
      we want to do these computations only in the case where this quantity is
      supposed to be exported.
      b769d03c
  10. 28 Jun, 2019 2 commits
  11. 27 Jun, 2019 1 commit
  12. 14 Jun, 2019 1 commit
  13. 12 Mar, 2019 1 commit
  14. 01 Mar, 2019 1 commit
  15. 28 Feb, 2019 1 commit
  16. 25 Feb, 2019 1 commit
  17. 15 Feb, 2018 1 commit
  18. 29 Jan, 2018 1 commit
  19. 23 Jan, 2017 2 commits
    • Benoît LÉ's avatar
      Revert "Splitted updateMaterialVariables into two functions:... · fba586b9
      Benoît LÉ authored
      Revert "Splitted updateMaterialVariables into two functions: updateMaterialVariablesFromLevelSet can be used to deal with any internal variable which depends on the level set (not only the damage variable), updateMaterialVariables must then be used to update the other material variables (like eps_ref for instance)"
      
      This reverts commit 857b3d0c.
      fba586b9
    • Benoît LÉ's avatar
      Splitted updateMaterialVariables into two functions:... · 857b3d0c
      Benoît LÉ authored
      Splitted updateMaterialVariables into two functions: updateMaterialVariablesFromLevelSet can be used to deal with any internal variable which depends on the level set (not only the damage variable), updateMaterialVariables must then be used to update the other material variables (like eps_ref for instance)
      857b3d0c
  20. 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
  21. 14 Nov, 2016 1 commit
  22. 20 Sep, 2016 2 commits
  23. 16 Sep, 2016 1 commit
  24. 29 Jul, 2016 2 commits
  25. 25 Jul, 2016 1 commit
  26. 22 Jul, 2016 6 commits
    • Alexis SALZMAN's avatar
      Merge branch 'master' into para · 5b561468
      Alexis SALZMAN authored
      Conflicts:
      	src/TLSSolver.cc
              resolved : just two header set on the same line
      5b561468
    • Kévin Moreau's avatar
      ok · 3415cdbc
      Kévin Moreau authored
      3415cdbc
    • Kévin Moreau's avatar
      update infinite dam notch test case · dce1d447
      Kévin Moreau authored
      dce1d447
    • Kévin Moreau's avatar
      update mode atomic test case · ce676806
      Kévin Moreau authored
      ce676806
    • Kévin Moreau's avatar
      This commit bring the following changes · 0d20941f
      Kévin Moreau authored
      * clean up unused feature.
      
      it affects:
        - Export.cc
        - Import.cc
      
      * improvement of transfer of displacement field after remeshing
      
      it affects:
        - Formulation.cc
      
      * correct a small bug that happens sometimes in restart, "mean" vectors
      had wrong size after restart. It was always too long and filled with NaN.
      
      it affects:
        - FormulationQS.cc
      
      * had several "guards" that end computation and give an error message when
      something goes wrong.
      
      it affects:
        - TLSSolver.cc
        - FormulationQS.cc
      
      * correct an error in the getGrad function of CohesiveLinearHardeningFunction
      
      it affects:
        - MaterialFunction.cc
      
      * swap orientation in comp mesh generation. It seems that it is test case dependent.
      TO BE INVESTIGATED if your comp_mesh has two colours when plotting in GMSH.
      
      it affects:
        - MeshGeneration.h
      
      * correct a bug resulting from \Gamma_in recent commit. FastMarchingModeExtension
      was updating phi based on \Gamma_in. The obtained phi was not anymore corresponding
      to the iso-lc discretisation, it leads to damage equal to 1 inside the mechanical domain.
      It leads to singular stiffness matrix.
      
      it affects:
        - TLSSolver.cc
      0d20941f
    • 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
  27. 07 Jul, 2016 1 commit
  28. 24 Jun, 2016 1 commit
  29. 23 Jun, 2016 1 commit
    • Alexis SALZMAN's avatar
      Roll back to a unmodified version: only comment and basic para stuff present · 4852422c
      Alexis SALZMAN authored
      Modification, mainly buf_nodal_vec passed into a xDistVector and declare
      state in parallel are removed. This version have minimal change to work
      in // context with only one proc. Many comment are present to explain
      what have to be changed to work in distributed context. The previous
      commit have been tagged (WITHMODIF) to be able to get back to it when we
      will try to pass in distributed context.
      Many guard are present. They will be efficient to avoid mistake. Many
      other guard with comment are missing but this work will be done only if
      we pass in distributed context.
      4852422c