1. 26 Jun, 2019 1 commit
  2. 25 Jun, 2019 1 commit
  3. 26 Jun, 2019 1 commit
  4. 18 Jun, 2019 1 commit
  5. 07 Jun, 2019 1 commit
    • Sergio Ferraris's avatar
      INT: Org integration of VOF, Euler phase solvers and models. · 8170f2ad
      Sergio Ferraris authored
      Integration of VOF MULES new interfaces. Update of VOF solvers and all instances
      of MULES in the code.
      Integration of reactingTwoPhaseEuler and reactingMultiphaseEuler solvers and sub-models
      Updating reactingEuler tutorials accordingly (most of them tested)
      New eRefConst thermo used in tutorials. Some modifications at thermo specie level
      affecting mostly eThermo. hThermo mostly unaffected
      New chtMultiRegionTwoPhaseEulerFoam solver for quenching and tutorial.
      Phases sub-models for reactingTwoPhaseEuler and reactingMultiphaseEuler were moved
      to src/phaseSystemModels/reactingEulerFoam in order to be used by BC for
      Update of interCondensatingEvaporatingFoam solver.
  6. 06 Jun, 2019 1 commit
    • Mark Olesen's avatar
      ENH: increase robustness of PrecisionAdaptor · bf9d74ba
      Mark Olesen authored
      - overload the ref() method to allow modification of the referenced
        (non-const) field directly. Same as constCast(), but less typing
        and less prone to error.
      - construct ConstPrecisionAdaptor from tmp for improved efficiency.
  7. 01 May, 2019 2 commits
    • Mark Olesen's avatar
      ENH: ensure that content changes in coded objects are noticed (#1293) · a85c55bb
      Mark Olesen authored
      - for codedFunctionObject and CodedSource the main code snippets
        were not included in the SHA1 calculation, which meant that many
        changes would not be noticed and no new library would be compiled.
        As a workaround, a dummy 'code' entry could be used solely for the
        purposes of generating a SHA1, but this is easily forgotten.
        We now allow tracking of the dynamicCodeContext for the coded
        objects and append to the SHA1 hasher with specific entries.
        This should solve the previous misbehaviour.
        We additionally add information about the ordering of the code
        sections. Suppose we have a coded function object (all code
        segments are optional) with the following:
            codeExecute "";
            codeWrite   #{ Info<< "Called\n"; #};
        which we subsequently change to this:
            codeExecute #{ Info<< "Called\n"; #};
            codeWrite   "";
        If the code strings are simply concatenated together, the SHA1 hashes
        will be identical. We thus 'salt' with their semantic locations,
        choosing tags that are unlikely to occur within the code strings
      - simplify the coded templates with constexpr for the SHA1sum
      - Correct the CodedSource to use 'codeConstrain' instead of
        'codeSetValue' for consistency with the underlying functions.
    • Mark Olesen's avatar
      ENH: replace processorFvPatchField specialization with 'if...' (#1304) · 83d26d19
      Mark Olesen authored
      - only apply component-wise transformCoupleField for non-scalar types
  8. 28 Apr, 2019 1 commit
  9. 26 Apr, 2019 1 commit
  10. 24 Apr, 2019 1 commit
  11. 17 Apr, 2019 3 commits
  12. 10 Apr, 2019 1 commit
  13. 04 Apr, 2019 1 commit
  14. 25 Mar, 2019 2 commits
  15. 22 Mar, 2019 1 commit
  16. 21 Mar, 2019 1 commit
  17. 19 Mar, 2019 1 commit
  18. 14 Mar, 2019 1 commit
  19. 28 Feb, 2019 1 commit
  20. 26 Mar, 2019 2 commits
  21. 22 Feb, 2019 1 commit
  22. 30 Apr, 2019 1 commit
    • Johan Roenby's avatar
      Introduced changes required to make isoAdvector and interIsoFoam work with... · 61c87b55
      Johan Roenby authored
      Introduced changes required to make isoAdvector and interIsoFoam work with morphing meshes: 1) In the alphaEqn.H U is made relative to mesh motion before the interface advection step, 2) in isoAdvection::advect() alpha must be multiplied by Vsc0()/Vsc(). Implementation tested and verified with 1) a spherical interface in a cubic domain with no flow, where the domain walls are squeezed together and 2) a spherical interfacee inside the sloshingCylinder, again with no flow, so the sphere should stay spherical, which it does.
  23. 18 Feb, 2019 1 commit
    • Kutalmis Bercin's avatar
      ENH: Digital-Filter Based Synthetic Turbulence Generation Method for LES/DES Inflows · 33ef139a
      Kutalmis Bercin authored
          Velocity boundary condition generating synthetic turbulence-alike
          time-series for LES and DES turbulent flow computations.
          To this end, two synthetic turbulence generators can be chosen:
          - Digital-filter method-based generator (DFM)
          Klein, M., Sadiki, A., and Janicka, J.
              A digital filter based generation of inflow data for spatially
              developing direct numerical or large eddy simulations,
              Journal of Computational Physics (2003) 186(2):652-665.
          - Forward-stepwise method-based generator (FSM)
          Xie, Z.-T., and Castro, I.
              Efficient generation of inflow conditions for large eddy simulation of
              street-scale flows, Flow, Turbulence and Combustion (2008) 81(3):449-470
          In DFM or FSM, a random number set (mostly white noise), and a group
          of target statistics (mostly mean flow, Reynolds stress tensor profiles and
          length-scale sets) are fused into a new number set (stochastic time-series,
          yet consisting of the statistics) by a chain of mathematical operations
          whose characteristics are designated by the target statistics, so that the
          realised statistics of the new sets could match the target.
          Random number sets ---->-|
                               DFM or FSM ---> New stochastic time-series consisting
                                   |           turbulence statistics
          Turbulence statistics ->-|
          The main difference between DFM and FSM is that the latter replaces the
          streamwise convolution summation in DFM by a simpler and a quantitatively
          justified equivalent procedure in order to reduce computational costs.
          Accordingly, the latter potentially brings resource advantages for
          computations involving relatively large length-scale sets and small
  24. 10 Feb, 2019 1 commit
  25. 07 Jan, 2019 1 commit
  26. 13 Feb, 2019 1 commit
  27. 11 Feb, 2019 1 commit
  28. 08 Feb, 2019 2 commits
  29. 07 Feb, 2019 2 commits
    • Mark Olesen's avatar
      ENH: code adjustments for updated NullObject · 078e3474
      Mark Olesen authored
      - can now safely use labelList::null() instead of emptyLabelList for
        return values. No special treatment required for lists.
        Possible replacements:
            if (notNull(list) && list.size())  ->  if (list.size())
            if (isNull(list) || list.empty())  ->  if (list.empty())
        The receiver may still wish to handle differently to distinguish
        between a null list and an empty list, but no additional special
        protection is required when obtaining sizes, traversing, outputting
    • mattijs's avatar
  30. 06 Feb, 2019 2 commits
  31. 05 Feb, 2019 1 commit
  32. 29 Jan, 2019 1 commit