1. 14 Sep, 2015 4 commits
  2. 31 Aug, 2015 1 commit
    • Iulian Grindeanu's avatar
      FBiGeom fixes from valgrind · 65c6dadf
      Iulian Grindeanu authored
      it does not have any problems in debug mode, with valgrind
      it crashed on buildbot, when merged on develop branch
      need to understand why, keep it separate
  3. 20 Apr, 2015 2 commits
    • Iulian Grindeanu's avatar
      revert commit 5b0f0032 · 0af3b15f
      Iulian Grindeanu authored
      it seems to crash in optimized mode
      need to investigate more
      lifecycle still messy
    • Iulian Grindeanu's avatar
      valgrind related fixes · 5b0f0032
      Iulian Grindeanu authored
      on the FBiGeom interface
      lifecycle of FBiGeom instance and other objects (FBEngine, GeomTopoTool)
      was not correct;
      introduce another destructor for FBiGeom instance, which will clean
      fbengine and geom topo tool
  4. 19 May, 2014 1 commit
    • Iulian Grindeanu's avatar
      remove warning · 23d4cca4
      Iulian Grindeanu authored
      geom is not initialized yet, but the macro check is uing it to
      report errors
      print full message instead
  5. 18 Dec, 2012 1 commit
  6. 11 Jan, 2012 1 commit
  7. 14 Dec, 2011 1 commit
    • Iulian Grindeanu's avatar
      an example of the new FBiGeom instantiation, that will take as input an · c929034a
      Iulian Grindeanu authored
      iMesh instance (moab) and a "model root" set
      this function is a special brand, it makes a direct connection between
      iMesh and iGeom; right now, it can't be easily declared
      in FBiGeom.h, because it has the iMesh_Instance as input parameter. 
      The implementation of this new function (FBiGeom_newGeomFromMesh) is in
      FBiGeom_MOAB.cpp, but its declaration should be maybe somewhere else 
      (for the example to run, I just declared it extern in the test itself :( )
      git-svn-id: https://svn.mcs.anl.gov/repos/ITAPS/MOAB/trunk@5261 6162379e-bd28-0410-9a7d-b7f4dcfcad3c
  8. 29 Nov, 2011 1 commit
  9. 28 Apr, 2011 1 commit
  10. 25 Mar, 2011 1 commit
  11. 10 Mar, 2011 1 commit
  12. 15 Oct, 2010 1 commit
  13. 29 Sep, 2010 1 commit
    • Iulian Grindeanu's avatar
      Move smooth faceting in iGeom implementation in MOAB · 0dfcf55e
      Iulian Grindeanu authored
      right now, it is triggered by "SMOOTH;" option when loading a 
      file; At that moment, smooth initialization is performed.
      Currently, only a few iGeom methods are supported; most important are
      projection to surface and normal evaluation at a point (close) to the
      These are minimum requirements for a surface mesher like Camal Paver
      Maybe the "SMOOTH;" option should be part of "engine_opt", when a new 
      iGeom instance is created.
      git-svn-id: https://svn.mcs.anl.gov/repos/ITAPS/MOAB/trunk@4181 6162379e-bd28-0410-9a7d-b7f4dcfcad3c