Using fvOptions in cfdemSolverPisoSTM

Submitted by napattorn1 on Fri, 08/07/2020 - 11:41

Hi all,

I am looking to impose a certain coded source term to scalar fields (temperature and species) in my fluidisation model which is adapted from the ErgunTestMPI model. There are quite a bit of examples on how to do this on the internet and I have followed some of them, however, I haven't been able to get the model to work. I have a few questions which I hope the experienced users here can help me out:

1. Inside the cfdemSolverPisoSTM.C and eulerianScalarField.C files, I see that fvOptions term is included in the governing equation for momentum and scale terms. Does this mean using fvOptions is possible for the solver I am using? The version history (3.6) states that fvOptions functionality is added to cfdemSolverPiso, so I wasn't sure if it is also the case for STM model.

3. I noticed that at the bottom of scalarTransportProperties dict file, fvOptions object for each scalar field is defined at the bottom of the scalarTransportProperties, e.g. fvOptionsT{}, fvOptionsC{}. Is this where I should define my fvOptions code? Or is it a reference that is used to lookup files with corresponding names in other location?

I have tried creating fvOptions and fvOptionsT files in both the constant and system folders inside CFD directory - the simulation runs as usual but no change in T field could be observed, as if the fvOptions file is not recognised by the solver at all.

Greatly appreciate anyone who could provide some insight into this.

ra474 | Fri, 07/16/2021 - 18:27

I tried fvOptions for cfdemSolverPisoSTM, for U field not scalar fields and it works fine. Maybe try that first. Also reviving this thread, it seems that fvOptions is featured in CFDEM cfdemSolverPiso and cfdemSolverPisoSTM, but not in cfdemSolverPisoScalar. Is any fix for this possible?