1. 20 Oct, 2018 1 commit
  2. 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
  3. 27 Sep, 2018 1 commit
    • T.J. Corona's avatar
      Changes to make SMTK work as a CMB thirdparty project. · 5d787001
      T.J. Corona authored
      This MR replaces CMAKE_PROJECT_NAME with PROJECT_NAME within SMTK so SMTK
      will build and install as a third party submodule of CMB. Also, the
      "subproject" delineation was removed from cJSON (which will soon be removed
      entirely), SMTKVTKExtensionMeshing, and SMTKDiscreteModel. Finally, the
      header test macro has been modified to accept as input the library
      associated with the header files.
  4. 26 Sep, 2018 1 commit
  5. 24 Sep, 2018 1 commit
  6. 16 Aug, 2018 1 commit
  7. 04 Jun, 2018 1 commit
  8. 13 Feb, 2018 1 commit
  9. 15 Aug, 2017 1 commit
  10. 23 Mar, 2017 1 commit
  11. 24 May, 2016 1 commit
  12. 26 Oct, 2015 1 commit
    • David Thompson's avatar
      Generalize the Exodus session; add a SLAC reader. · bd395985
      David Thompson authored
      This changes the way datasets are referenced in the Exodus session
      so that the structure of the reader's output does not have to
      match the Exodus reader's convention. Instead of using handles
      that refer to specific blocks in an Exodus reader's output,
      reference the VTK datasets themselves.
      This also adds support for reading SLAC NetCDF files via VTK's reader.
      Finally, this fixes several SMTK issues and provides a new operator:
      + Provide a global operator to export model JSON ("export model json").
      + Fix `model::Manager::modelOwningEntity`.
      + Fix problems with the SetProperty operator.
      + Fix the Exodus reader test to prevent the image test from failing.
  13. 15 Sep, 2015 1 commit
  14. 24 Aug, 2015 2 commits
  15. 29 Jul, 2015 2 commits
  16. 25 May, 2015 1 commit
  17. 22 May, 2015 1 commit
  18. 20 May, 2015 1 commit
  19. 23 Mar, 2015 1 commit
  20. 30 Jan, 2015 1 commit
  21. 28 Oct, 2014 1 commit
  22. 15 Aug, 2014 1 commit
  23. 08 Jul, 2014 1 commit
    • David Thompson's avatar
      Use the attribute system to specify operators. · da25ac93
      David Thompson authored
      Remove the `smtk/model/{Parameter,OperatorResult}` classes.
      They are replaced by adding a `specification()` method to
      the `Operator` class that returns an `AttributePtr` (typedef'd
      to `OperatorSpecification`). The `OperatorResult` class is
      also replaced by an `AttributePtr`.
      The attributes and their definitions are held by an
      attribute `Manager` owned by the `Bridge` whose model
      entities the operators can have as operands.
      Since the attribute system will be used for operators,
      it will be possible to determine operator names and
      parameters without instantiating an operator. (Instead,
      the attribute manager for the bridge can be asked for
      definitions.) Because of this, `Operator`s now use the
      same auto-init utilities as the `Bridge` classes.
      Upon an operator's static initialization, it registers
      itself with the proper subclass of `smtk::model::Bridge`,
      providing its name, a constructor function, and an XML
      definition of its parameters and another definition of
      its result values.
      When an instance of a Bridge subclass is constructed,
      each registered operator's XML definition is loaded into
      the bridge's attribute manager.
      Thus, bridges no longer keep a list of Operator instances;
      instead their attribute manager tracks available definitions.
      Operators now have a "specification" that is an AttributePtr
      specifying parameter values.
      The specification is null by default but can be set to an
      attribute with the proper definition (matching the one in the bridge's
      attribute manager).
      ImportJSON and ExportJSON provide methods for transporting attribute
      Since the XML reader does not provide a list of
      the toplevel attributes it reads, the JSON
      we export/import must store a copy of attribute
      name alongside the XML.
      This commit also adds smtkTypeMacro() to a large number
      of smtk::attribute classes so that templated methods operating
      on subclasses of Item and ItemDefinition can refer to
      shared pointers more easily.
      This commit makes the Bridge class's `operatorManager()`
      attribute manager held by pointer rather than by value.
      Because subclasses of DefaultBridge (like the TestForwardingBridge
      in the unitDefaultBridge test) are constructed by calling all
      subclass constructors, they would being initialized with the
      wrong static list of operator constructors if the manager
      was held by value. Now, when each Bridge
      subclass calls `initializeOperatorManager()` in its constructor,
      any previous subclass initialization is blown away by deleting
      the old `operatorManager()` and constructing a new one before
      populating it. It would be nice to have a `reset()` method on
      attribute::Manager. Sigh.
      Finally, this adds some helper methods to bridges and operators
      for obtaining the class name of an instance. The tests use this
      to aid in debugging.
      Silence silly shiboken signals: ignore warnings generated by
      shiboken-generated-code... at least for GNU and clang C++ compilers.
      A CMake function named smtk_operator_xml() is installed so that
      external projects (namely CMB) can use it. This function encodes
      an XML file as a C++ string for use in associating an `Operator`'s
      C++ implementation with its XML definition.
  24. 24 Oct, 2013 1 commit
    • David Thompson's avatar
      Fix SMTK macros to handle static build. · fba80fb8
      David Thompson authored
      When building with `BUILD_SHARED_LIBS=OFF`, CMake complains
      that SMTKCore cannot be installed properly because cJSON is
      not included in SMTK-targets. Adding `APPEND` to the `EXPORT`
      command allows CMake to track targets built in multiple
      directories, such as cJSON.
  25. 06 Sep, 2013 4 commits
  26. 31 Jul, 2013 1 commit
  27. 04 Jan, 2013 2 commits
  28. 28 Nov, 2012 1 commit
  29. 11 Jul, 2012 1 commit