[klorfj]

Hi everyone!

I have big trouble with getting access to fields, for example the mass fraction Y species fields, inside a lagrangian submodel:

-

-> FOAM FATAL ERROR:
Sum of mass fractions is zero for species 4(N2 O2 CO2 H2O)

I try to access the mesh and load a thermodynamic package, which should load the Y fields in a multiComponentMixture, with the following code:

// -------------------------------------------------------------------
//  Name:			calculate
//- Update surface reactions
//  Parameters:
//  dt				(I) - timestep
//  Re				(I) - Surface Reynolds number 
// (see \intermediate\parcels\Templates\ReactingHeterogeneousParcel.C)
//  nu				(I) - Surface nu number, mus/rhos 
// (see \intermediate\parcels\Templates\ReactingHeterogeneousParcel.C)
//  celli			(I) - Cell index
//  d				(I) - Diameter [m]
//  T				(I) - Temperature [K]
//  Tc				(I) - Continuous phase Temperature [K]
//  pc				(I) - Continuous phase pressure [Pa]
//  rhoc			(I) - Continuous phase density [kg/m3]
//  Uc				(I) - Continuous phase velocity [m/s]
//  mass			(I) - Mass [kg]
//  Ysolid			(I) - Mass fract. of remaining components in bed
//  F			  (I/O) - Cohesion factor 0 - 1	(summarized progress 
//						  of all reactions)
//  N				(I) - Flux of species emitted from particle
//  NCpW		  (I/?) - Sum Ni*Cpi*Wi of emission species, not used
//  dMassSolid	  (I/O) - Solid-phase mass transfer [kg]
//						  (Fe3O4, Fe2O3, CaCO3, CaO, Dolomite, MgO, 
//						  H2O)
//  dMassSRCarrier(I/O) - Carrier-phase mass transfer [kg]
//						  (O2, H2O, CO2, N2)
//  Returns:		Heat of reaction [J]
// -------------------------------------------------------------------
template<class CloudType>
Foam::scalar Foam::BEDSIMheterogeneousRate<CloudType>::calculate
(
    const scalar dt,
    const scalar Re,
    const scalar nu,
    const label celli,
    const scalar d,
    const scalar T,
    const scalar Tc,
    const scalar pc,
    const scalar rhoc,
    const vector Uc,    //New Uc local gas velocity vector
    const scalar mass,
    const scalarField& YSolid,
    scalarField& F,
    const scalar N,
    scalar& NCpW,
    scalarField& dMassSolid,
    scalarField& dMassSRCarrier
) const
{
	const objectRegistry& db = this->owner().db();
	const volVectorField& U = db.lookupObject<volVectorField>("U");
	const fvMesh& mesh = U.mesh();

	autoPtr<rhoReactionThermo> pMix(rhoReactionThermo::New(mesh));
	rhoReactionThermo& mix = pMix();
	SLGThermo slgThermo(mesh, mix);

...

}

Using the code below which works everywhere else except in the lagrangian model gives a compilation error

const objectRegistry& db = db();
const volVectorField& U = db().lookupObject<volVectorField>("U");

lnInclude/BEDSIMheterogeneousRate.C:549:60: error: expected primary-expression before ‘>’ token
  const volVectorField& U = db().lookupObject<volVectorField>("U");

I hope someone can help me!

/Örjan

[oswald]

You only have direct access to fields that are defined the cloud, if you are lucky. You can try with something like

this->owner().Uc()

for the carrier velocity.


Check your relevant ...Cloud.H in lagrangian/intermediate/clouds/Templates/...Cloud, there you will find a section with Member Functions giving you access to some fields.

[klorfj]

Thanks Oswald!

I found that I actually can access the Y fields via the mesh in the lagrangian model:


const fvMesh& mesh = this->owner().T().mesh();
const volScalarField& n2 = mesh.lookupObject<volScalarField>("N2");
const volScalarField& o2 = mesh.lookupObject<volScalarField>("O2");
const volScalarField& co2 = mesh.lookupObject<volScalarField>("CO2");
const volScalarField& h2o = mesh.lookupObject<volScalarField>("H2O");
const volVectorField& U = mesh.lookupObject<volVectorField>("U");

autoPtr<rhoReactionThermo> pMix(rhoReactionThermo::New(mesh));


But there is still something that is different with the mesh, because of the error when creating the thermodynamic package.

I think that when the termodynamic package is created, some problem with the mesh forces basicMultiComponentMixture.C to initialize the species Y_ fields to zero!

Can the mesh be checked for consistency to find out what's the problem?

Best regards!
/Örjan