1. 17 Jun, 2021 1 commit
  2. 17 Mar, 2021 1 commit
  3. 21 Dec, 2020 1 commit
  4. 31 Oct, 2019 1 commit
  5. 16 Aug, 2019 1 commit
    • sergio's avatar
      ENH: Add components to allow overset with multiple motion solvers · d96ad1cd
      sergio authored
      1) Add softWall rigidBody restrain
      2) Add linearSpringDamper sixDoF restrain to work as soft rope
      3) dynamicMotionSolverListFvMesh changed to dictionary based input
      4) Add Time reference access to sixDof restraints
      5) Add drivenLinearMotion to solidBodyMotionFunctions.
      d96ad1cd
  6. 06 Feb, 2019 1 commit
  7. 17 Oct, 2018 1 commit
    • Mark OLESEN's avatar
      ENH: simplify objectRegistry access names (issue #322) · 8fabc325
      Mark OLESEN authored
        New name:  findObject(), cfindObject()
        Old name:  lookupObjectPtr()
      
            Return a const pointer or nullptr on failure.
      
        New name:  findObject()
        Old name:  --
      
            Return a non-const pointer or nullptr on failure.
      
        New name:  getObjectPtr()
        Old name:  lookupObjectRefPtr()
      
            Return a non-const pointer or nullptr on failure.
            Can be called on a const object and it will perform a
            const_cast.
      
      - use these updated names and functionality in more places
      
      NB: The older methods names are deprecated, but continue to be defined.
      8fabc325
  8. 09 Dec, 2016 1 commit
  9. 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
  10. 24 Aug, 2012 1 commit
  11. 23 Aug, 2012 3 commits
  12. 14 Aug, 2011 1 commit
  13. 19 Jan, 2011 1 commit
  14. 14 Jan, 2011 1 commit
  15. 07 Jan, 2011 1 commit
  16. 05 Jan, 2011 2 commits
  17. 28 Jul, 2010 1 commit
  18. 29 Apr, 2010 1 commit
  19. 29 Mar, 2010 1 commit
  20. 04 Dec, 2009 1 commit
  21. 31 Dec, 2008 1 commit
  22. 25 Jun, 2008 2 commits
  23. 15 Apr, 2008 1 commit