1. 02 Jun, 2020 1 commit
    • Mark Olesen's avatar
      ENH: unify use of dictionary method names · 3e43edf0
      Mark Olesen authored
      - previously introduced `getOrDefault` as a dictionary _get_ method,
        now complete the transition and use it everywhere instead of
        `lookupOrDefault`. This avoids mixed usage of the two methods that
        are identical in behaviour, makes for shorter names, and promotes
        the distinction between "lookup" access (ie, return a token stream,
        locate and return an entry) and "get" access (ie, the above with
        conversion to concrete types such as scalar, label etc).
      3e43edf0
  2. 19 Dec, 2019 1 commit
    • Zeljko Tukovic's avatar
      ENH: Adding interTrack code · 79588b9b
      Zeljko Tukovic authored
      1) New skewCorrectedSnGrad for non-orthogonal and skewness corrector
      2) New freeSurfacePressure and freeSurfacePressure working with
         interfaceTrackingFvMesh
      3) New interfaceTrackingFvMesh
      79588b9b
  3. 31 Oct, 2019 1 commit
  4. 06 Feb, 2019 1 commit
  5. 30 May, 2018 1 commit
  6. 13 Dec, 2017 1 commit
  7. 16 Mar, 2018 1 commit
    • Mark Olesen's avatar
      STYLE: more consistent use of dimensioned Zero · 2f86cdc7
      Mark Olesen authored
      - when constructing dimensioned fields that are to be zero-initialized,
        it is preferrable to use a form such as
      
            dimensionedScalar(dims, Zero)
            dimensionedVector(dims, Zero)
      
        rather than
      
            dimensionedScalar("0", dims, 0)
            dimensionedVector("zero", dims, vector::zero)
      
        This reduces clutter and also avoids any suggestion that the name of
        the dimensioned quantity has any influence on the field's name.
      
        An even shorter version is possible. Eg,
      
            dimensionedScalar(dims)
      
        but reduces the clarity of meaning.
      
      - NB: UniformDimensionedField is an exception to these style changes
        since it does use the name of the dimensioned type (instead of the
        regIOobject).
      2f86cdc7
  8. 14 Mar, 2018 1 commit
  9. 12 Mar, 2018 1 commit
  10. 14 Jun, 2017 1 commit
    • mattijs's avatar
      ENH: overset: Initial release of overset capability. · fd665b4a
      mattijs authored
      Adds overset discretisation to selected physics:
      - diffusion : overLaplacianDyMFoam
      - incompressible steady : overSimpleFoam
      - incompressible transient : overPimpleDyMFoam
      - compressible transient: overRhoPimpleDyMFoam
      - two-phase VOF: overInterDyMFoam
      
      The overset method chosen is a parallel, fully implicit implementation
      whereby the interpolation (from donor to acceptor) is inserted as an
      adapted discretisation on the donor cells, such that the resulting matrix
      can be solved using the standard linear solvers.
      
      Above solvers come with a set of tutorials, showing how to create and set-up
      simple simulations from scratch.
      fd665b4a
  11. 01 Dec, 2016 1 commit
    • Henry Weller's avatar
      dynamicMotionSolverListFvMesh: New mesh-motion solver supporting multiple moving regions · 1c687baa
      Henry Weller authored
      e.g. the motion of two counter-rotating AMI regions could be defined:
      
      dynamicFvMesh   dynamicMotionSolverListFvMesh;
      
      solvers
      (
          rotor1
          {
              solver solidBody;
      
              cellZone        rotor1;
      
              solidBodyMotionFunction  rotatingMotion;
              rotatingMotionCoeffs
              {
                  origin        (0 0 0);
                  axis          (0 0 1);
                  omega         6.2832; // rad/s
              }
          }
      
          rotor2
          {
              solver solidBody;
      
              cellZone        rotor2;
      
              solidBodyMotionFunction  rotatingMotion;
              rotatingMotionCoeffs
              {
                  origin        (0 0 0);
                  axis          (0 0 1);
                  omega         -6.2832; // rad/s
              }
          }
      );
      
      Any combination of motion solvers may be selected but there is no special
      handling of motion interaction; the motions are applied sequentially and
      potentially cumulatively.
      
      To support this new general framework the solidBodyMotionFvMesh and
      multiSolidBodyMotionFvMesh dynamicFvMeshes have been converted into the
      corresponding motionSolvers solidBody and multiSolidBody and the tutorials
      updated to reflect this change e.g. the motion in the mixerVesselAMI2D tutorial
      is now defined thus:
      
      dynamicFvMesh   dynamicMotionSolverFvMesh;
      
      solver solidBody;
      
      solidBodyCoeffs
      {
          cellZone        rotor;
      
          solidBodyMotionFunction  rotatingMotion;
          rotatingMotionCoeffs
          {
              origin        (0 0 0);
              axis          (0 0 1);
              omega         6.2832; // rad/s
          }
      }
      1c687baa
  12. 05 Aug, 2016 1 commit
  13. 30 Apr, 2016 1 commit
    • Henry Weller's avatar
      GeometricField: Renamed internalField() -> primitiveField() and... · 3c053c2f
      Henry Weller authored
      GeometricField: Renamed internalField() -> primitiveField() and dimensionedInternalField() -> internalField()
      
      These new names are more consistent and logical because:
      
      primitiveField():
      primitiveFieldRef():
          Provides low-level access to the Field<Type> (primitive field)
          without dimension or mesh-consistency checking.  This should only be
          used in the low-level functions where dimensional consistency is
          ensured by careful programming and computational efficiency is
          paramount.
      
      internalField():
      internalFieldRef():
          Provides access to the DimensionedField<Type, GeoMesh> of values on
          the internal mesh-type for which the GeometricField is defined and
          supports dimension and checking and mesh-consistency checking.
      3c053c2f
  14. 23 Apr, 2016 1 commit
  15. 16 Apr, 2016 1 commit
  16. 26 Feb, 2016 1 commit
  17. 27 Jun, 2016 1 commit
  18. 19 Dec, 2015 1 commit
  19. 19 Nov, 2015 2 commits
    • mattijs's avatar
      ENH: displacementMotionSolver: additional hierarchy · 8f5997bb
      mattijs authored
      - shm: have displacementMotionSolver as alternative mesh shrinker
        (instead of medialAxis).
      - updated iglooWithFridges tutorial to use displacementLaplacian
      - selectable interpolation from cells to points in the motion solvers
        using the 'interpolation' keyword:
          interpolation volPointInterpolation;    // default
          or
          interpolation patchCorrected (lowerWall upperWall);
      - wrapped up mesh shrinkers (see above) for use as a displacementMotionSolver
        (i.e. the opposite of the displacementMotionSolver mesh shrinker)
      8f5997bb
    • mattijs's avatar
      ENH: displacementMotionSolver: additional hierarchy · eb487eb9
      mattijs authored
      - shm: have displacementMotionSolver as alternative mesh shrinker
        (instead of medialAxis).
      - updated iglooWithFridges tutorial to use displacementLaplacian
      - selectable interpolation from cells to points in the motion solvers
        using the 'interpolation' keyword:
          interpolation volPointInterpolation;    // default
          or
          interpolation patchCorrected (lowerWall upperWall);
      - wrapped up mesh shrinkers (see above) for use as a displacementMotionSolver
        (i.e. the opposite of the displacementMotionSolver mesh shrinker)
      eb487eb9
  20. 31 Aug, 2012 2 commits
  21. 24 Aug, 2012 1 commit
  22. 14 Aug, 2011 1 commit
  23. 19 Jan, 2011 1 commit
  24. 14 Jan, 2011 1 commit
  25. 07 Jan, 2011 1 commit
  26. 05 Jan, 2011 2 commits
  27. 28 Jul, 2010 1 commit
  28. 12 Apr, 2010 1 commit
  29. 29 Mar, 2010 1 commit
  30. 21 Oct, 2009 1 commit
    • graham's avatar
      Changing · 92217930
      graham authored
          deltaT().value() to deltaTValue()
      and
          deltaT0().value() to deltaT0Value()
      across the whole code - faster to return especially if being used
      often, in each call to a submodel for example.
      92217930
  31. 31 Dec, 2008 1 commit
  32. 08 Dec, 2008 1 commit
  33. 21 Oct, 2008 1 commit
  34. 25 Jun, 2008 2 commits
  35. 15 Apr, 2008 1 commit