1. 20 Nov, 2018 2 commits
    • Mark Olesen's avatar
      ENH: add read guard for dimensionedType constructors (#762) · dd87c983
      Mark Olesen authored
      - deprecate dimensionedType constructors using an Istream in favour of
        versions accepting a keyword and a dictionary.
        Dictionary entries are almost the exclusive means of read
        constructing a dimensionedType. By construct from the dictionary
        entry instead of doing a lookup() first, we can detect possible
        input errors such as too many tokens as a result of a input syntax
        Constructing a dimensionedType from a dictionary entry now has
        two forms.
        1.  dimensionedType(key, dims, dict);
            This is the constructor that will normally be used.
            It accepts entries with optional leading names and/or
            dimensions. If the entry contains dimensions, they are
            verified against the expected dimensions and an IOError is
            raised if they do not correspond. On conclusion, checks the
            token stream for any trailing rubbish.
        2.  dimensionedType(key, dict);
            This constructor is used less frequently.
            Similar to the previous description, except that it is initially
            dimensionless. If entry contains dimensions, they are used
            without further verification. The constructor also includes a
            token stream check.
            This constructor is useful when the dimensions are entirely
            defined from the dictionary input, but also when handling
            transition code where the input dimensions are not obvious from
            the source.
            This constructor can also be handy when obtaining values from
            a dictionary without needing to worry about the input dimensions.
            For example,
               Info<< "rho: " << dimensionedScalar("rho", dict).value() << nl;
            This will accept a large range of inputs without hassle.
      ENH: consistent handling of dimensionedType for inputs (#1083)
      BUG: incorrect Omega dimensions (fixes #2084)
    • Mark Olesen's avatar
      ENH: use dictionary::get<> instead of pTraits (#762) · efdbeae2
      Mark Olesen authored
      - check Istream in readBool in operator>> variant (#1033)
  2. 19 Nov, 2018 4 commits
  3. 16 Nov, 2018 3 commits
  4. 15 Nov, 2018 3 commits
  5. 14 Nov, 2018 2 commits
  6. 15 Nov, 2018 1 commit
    • Mark Olesen's avatar
      ENH: code reduction in MeshObject (#1071) · c5998105
      Mark Olesen authored
      - use forwarding templates for the factory method
      - avoid double use of dynamic_cast.
        Don't need implicit use in isA<>, can use result directly
      STYLE: updated iteration over HashTable of mesh objects
  7. 16 Nov, 2018 3 commits
  8. 15 Nov, 2018 1 commit
  9. 14 Nov, 2018 1 commit
  10. 15 Nov, 2018 1 commit
  11. 13 Nov, 2018 2 commits
  12. 12 Nov, 2018 9 commits
  13. 11 Nov, 2018 1 commit
  14. 10 Nov, 2018 3 commits
    • Mark Olesen's avatar
      ENH: simplify/extend objectRegistry code with templated predicates · 4965ea49
      Mark Olesen authored
      - replace explicit use of wordRe, wordRes, wordHashSet as filters
        with a MatchPredicate.
      - support filtering by class based on <Type> or predicates
    • Mark Olesen's avatar
      ENH: add IOobject::isHeaderClassName() method · f44e59fb
      Mark Olesen authored
      - in parameter form, check if it headerClassName() corresponds to the
        specified class name
      - in templated form, check if headerClassName() corresponds to the
        Type:typeName value.
        Specialization for <void> always returns true (ie, no checks)
    • Mark Olesen's avatar
      ENH: simplify/extend IOobjectList code with templated predicates · 8562e527
      Mark Olesen authored
      - replace explicit use of word, wordRe, wordRes, wordHashSet as filters
        with a MatchPredicate, since they all satisfy the requirements for
        use a predicate. This change reduces code duplication, allows other
        matcher types (eg, keyType) as well as lambda functions.
      - add special treatment for a 'const char*' parameter
        for lookupClass() and the now-deprecated single item lookup() method
        to promote these parameters to 'word'.
  15. 09 Nov, 2018 1 commit
    • Mark Olesen's avatar
      ENH: add IOobjectList::findObject() method · faaa93fd
      Mark Olesen authored
      - naming similar to objectRegistry, with unambiguous resolution.
        The lookup() methods have different return types depending on the
        calling parameter.
      STYLE: use IOobjectListTemplates.C for implementations
      - previously included as local definition within IOobjectList.C,
        but will be adding more templated methods soon.
      - adjust parameters (eg, matchName instead of matcher) to show their
      ENH: handle objectRegistry::names<void>(...)
      - this is equivalent to no Type restriction, and can be used when
        filtering names. Eg,
  16. 11 Nov, 2018 1 commit
  17. 09 Nov, 2018 1 commit
  18. 08 Nov, 2018 1 commit
    • Mark Olesen's avatar
      GIT: commit text missed in squashed merge · dff2569c
      Mark Olesen authored
          commit 3f9c7bf4
          commit 3cf177e7
      ENH: add geometric decomposition constraint (issue #921)
      - geometric decomposition constraints may be used to prevent the
        decomposition of regions of the mesh.
        The geometric constraint is applied according to the face centres,
        which define the connectivity between cells.
        Specified in decomposeParDict
                  type    geometric;
                          type    box;
                          min     (-10 -10 -10);
                          max     (1 1 1);
                          type    sphere;
                          origin  (-2 -2 1);
                          radius  1;
      ENH: add 'grow' option for geometric decomposition constraint (issue #921)
      - the 'grow' option includes an additional check to include cell faces
        for any cell that already has two or more of its faces "unblocked".
        This could indicate a connection over a corner, but does not distinguish
        between connectivity introduced by the constraint and the connectivity
        defined by other constraints.
      ENH: geometric decomposition constraint using topoSetFaceSource (issue #921)
      - replaced use of searchableSurface with a more general and
        more efficient topoSetFaceSource instead.
        Since searchableSurface is also available as a topoSetFaceSource,
        there is no loss in functionality, but using topoSetFaceSource allow
        directly looping over the faces without creating of an additional
        List of volumeTypes.