1. 22 Oct, 2018 1 commit
  2. 20 Oct, 2018 1 commit
  3. 19 Oct, 2018 1 commit
    • John Tourtellott's avatar
      Add recipe for Conda build · 922b2a2c
      John Tourtellott authored
      * Uses cmake toolchain to "cross compile" with conda env
      * Comments out vtk-dependent classes from polygon (Import, ExtractContours)
      * Incorporates MOAB build as part of the conda package build
  4. 10 Oct, 2018 1 commit
  5. 08 Oct, 2018 2 commits
  6. 02 Oct, 2018 1 commit
    • T.J. Corona's avatar
      Only check the version file if the variable "SMTK_VERSION" is not defined · 61dfb04d
      T.J. Corona authored
      We require smtk's version information to be included the CMake Project
      declaration in order to properly include smtk versions when using smtk as an
      SDK. We therefore do not have access to the variable ${PROJECT_SOURCE_DIR}
      at the time smtkVersion.cmake is read. We therefore use
      ${CMAKE_CURRENT_SOURCE_DIR}, since smtkVersion.cmake is called at the top
      level of smtk's build. We also guard against subsequent calls to
      smtkVersion.cmake where ${CMAKE_CURRENT_SOURCE_DIR} may no longer be set to
      the top level directory.
  7. 01 Oct, 2018 1 commit
  8. 27 Sep, 2018 2 commits
  9. 26 Sep, 2018 2 commits
  10. 24 Sep, 2018 2 commits
  11. 20 Sep, 2018 1 commit
  12. 18 Sep, 2018 1 commit
  13. 16 Aug, 2018 1 commit
  14. 15 Aug, 2018 1 commit
  15. 18 Jun, 2018 1 commit
    • T.J. Corona's avatar
      Introduce smtkDefaultPlugins library · 93ca07f9
      T.J. Corona authored
      With the new smtk plugin macro, whenever an smtk macro is created
      inside of smtk its plugin target is cached. After the core library
      and all of its sessions are configured, a library is generated whose
      sole function is to link against the plugins and expose them to a
      paraview-derived app.
  16. 15 Jun, 2018 1 commit
  17. 04 Jun, 2018 1 commit
  18. 31 May, 2018 1 commit
    • T.J. Corona's avatar
      Check for pvpython in $ParaView_CLEXECUTABLES_DIR before target · 7b10a0fb
      T.J. Corona authored
      SMTK has a CMake routine to find pvpython and use it to construct
      the right environment for smtk python. When on Windows and when
      building SMTK in developer mode, the paraview found by SMTK is
      its build tree. This is fine for building, but the build tree
      pvpython does not work on Windows. We therefore export the path
      to the install tree version of pvpython so SMTK can first check
      for this variable before getting pvpython through its paraview
  19. 30 May, 2018 1 commit
    • T.J. Corona's avatar
      FindPVPythonEnvironment: check for pvpython-launcher · 5dc5874d
      T.J. Corona authored
      On some operating systems and in certain configurations, ParaView creates a
      launcher for each of its executables. The launcher is responsible for
      setting up the appropriate environment and then launching the real
      executable. When a launcher is not available, it is likely because the
      rpath for the real executable has been set to accomplish the task of
      configuring the environment. We first check if ParaView has a launcher for
      pvpython, and fall back to using the real pvpython.
  20. 18 Apr, 2018 1 commit
    • Haocheng LIU's avatar
      FEATURE: Introduce a new rgg session and pin related ops · d551289f
      Haocheng LIU authored
      Add Pin:
      This op would just create a simple rgg with an input name and label.
      Then user should use edit pin operator to tweak its properties.
      Edit Pin:
      Given an input nuclear pin(aka aux_geom in SMTK), it provides
      user an interface to modify a pin by changing its properties,
      pieces and layers. Given a pin entity, it would first delete all its
      children(parts and layers) then add new child auxiliary geometries.
      When creating representation for aux_geoms,SMTK would check the
      pin first, then generate representations for itself and children.
      The canHandleAuxliaryGeometry function would update the bounding
      box for child auxiliary geometries one by one next.
      Add a delete entity operator to rgg session
  21. 13 Apr, 2018 1 commit
  22. 11 Apr, 2018 3 commits
  23. 22 Mar, 2018 1 commit
  24. 16 Mar, 2018 1 commit
  25. 16 Feb, 2018 1 commit
  26. 13 Feb, 2018 1 commit
  27. 27 Jan, 2018 1 commit
  28. 26 Jan, 2018 2 commits
  29. 23 Jan, 2018 1 commit
    • T.J. Corona's avatar
      Refactor operators. · dc574a3e
      T.J. Corona authored
      This commit contains many changes made by Haocheng, David and myself.
      It performs the following:
      a) move operators out of model and have them operate indpendently from
         model sessions
      b) operators now each have their own attribute collection, rather than being
         represented as single attributes from an attribute collection
      c) Separate XML descriptions from the base operator, loosening the requirement
         on operators to simply have a descriptive attribute (XML descriptions are
         now supported as a subclass of the base operator). This facilitates the
         construction of python operators without requiring an XML string describing
         their inputs
      c) introduce an operation manager that tracks the availability of operators.
         It has the following properties:
         i.   Registration of operators via a unique name (usually the c++ name of
              the operator)
         ii.  Provide a connection to a resource manager so that operations that
              construct resources will automatically register the new resources to
              the manager
         iii. Provide a list of available operators given an input selection (i.e.
              show which operators accept a given input)
      d) allow read/write locks on operations' input resources and add tests for
         asynchronous operations
      e) break static registration of operations and resources into a set of
         libraries that accompany the libraries in which they are defined. A library
         that provides static registration of a resource and associated operations
         for library smtkFoo is called smtkFooEnvironment, and the registration
         occurs in the foo::environment namespace
      f) deprecate the exodus session
      g) convert smtk::model and polygon, mesh and discrete sessions to use
         nlohmann::json instead of cJSON. With this change, we can hopefully remove
         cJSON from smtk
      h) provide operations for creating, loading and saving smtk resources
      i) update tests to use the new operation framework
      This merge is a work in progress, but has become too large to avoid merging
      into the msater branch. The outstanding issues are
      a) remove smtk::model::Operation from smtk (it is still required for the qt
      b) rename smtk::operation::NewOp smtk::operation::Operator
      c) fix Qt bindings to use the new operation infrastructure
      d) fix the infrastructure for meshing interop with remus to avoid using json
      e) remove cJSON from smtk
      f) switch resources' read/write/create methods from bare functors to smtk
         operators. This is more in keeping with the pattern of using operators to
         affect resources
      g) enable CGM session
      h) enable matplotlib extension
  30. 19 Jan, 2018 1 commit
  31. 16 Jan, 2018 1 commit
  32. 09 Oct, 2017 2 commits