Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • openfoam openfoam
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 383
    • Issues 383
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #1916

Closed
Open
Created Nov 09, 2020 by Thorsten Zirwes@g3

Testcases with Reacting Parcels Fail ('constantVolume' or 'volumeUpdateMethod' must be provided)

In the current develop branch (1d544540), many tutorial cases with reacting parcels fail. For example:

cd $FOAM_TUTORIALS/combustion/fireFoam/LES/smallPoolFire2D/
./Allrun

or

cd /work/fh2-project-devel/np4075/commit_Bilger_2006/openfoam-com/tutorials/lagrangian/reactingParcelFoam/counterFlowFlame2DLTS/
blockMesh
reactingParcelFoam

will both yield

--> FOAM FATAL ERROR: (openfoam-2010 patch=201012)
Either 'constantVolume' or 'volumeUpdateMethod'
 must be provided.
 The new keyword is 'volumeUpdateMethod'.
 Available methods are  :
 constantRho, constantVolume or updateRhoAndVol.
 'constantVolume' is either true/false

Adding the following entry in constant/reactingCloud1Properties fixes the problem.

constantProperties
{
    constantVolume true;
}

In version v2006, the cases work fine. The problem seems to originate from commit 11d17fec, more specifically here: https://develop.openfoam.com/Development/openfoam/-/blob/develop/src/lagrangian/intermediate/parcels/Templates/ReactingParcel/ReactingParcelI.H#L73

The constructor of constantProperties always requires a value to be specified, regardless if the particles are active or not.

Assignee
Assign to
Time tracking