View Issue Details

IDProjectCategoryView StatusLast Update
0004083OpenFOAMContributionpublic2024-05-23 11:19
ReporterApanasevich Assigned Towill  
Status closedResolutionno change required 
Platformamd64OSRocky LinuxOS Version8.6
Product Versiondev 
Summary0004083: fvModels: lookup a variable within a coded source term
DescriptionConfiguration considered: multiphaseEuler, multicomponent fluids, mass transfer between the phases.
Let's assume the liquid phase consists of two species "air" and "water" as given in turorial "bubbleColumnEvaporatingDissolving". In addition there is a passive scalar called "scalar.liquid" for which a transport equation is solved using phaseScalarTransport functionObject.

We also assume that a coded source term is added to the transport equation of a species (water.liquid) and to the transport eqiation of the passive scalar (scalar.liquid), i.e. there are two coded source terms defined in fvModels. Next assumption: both source terms depend on a variable "myVar". If "myVar" is defined only within the coded source term of species ("water.liquid") transport equation and it is lookup within the coded source term of passive scalar ('scalar.liquid') transport equation, the simulation crashes:

    request for volScalarField myVar.liquid from objectRegistry region0 failed
    available objects of type volScalarField are

If I do it vice versa: "myVar" is defiend within the coded source term of the passive scalar ("scalar.liquid") transport equation and it is lookup within the coded source term of species (water.lquid) transport equation, the simulation works fine.

I am attaching a test case (based on bubbleColumnEvaporatingDissolving tutorial) that demonstrates this issue. This report is for your information; I am not sure if it is a bug or a missing feature.
TagsNo tags attached.



2024-05-21 10:36



2024-05-23 11:19

manager   ~0013250

This is a usage issue, not a bug.

Issue History

Date Modified Username Field Change
2024-05-21 10:36 Apanasevich New Issue
2024-05-21 10:36 Apanasevich File Added:
2024-05-23 11:19 will Assigned To => will
2024-05-23 11:19 will Status new => closed
2024-05-23 11:19 will Resolution open => no change required
2024-05-23 11:19 will Note Added: 0013250