CFD Online Discussion Forums

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)
-   OpenFOAM Running, Solving & CFD (https://www.cfd-online.com/Forums/openfoam-solving/)
-   -   Attempt to run rhoPisoTwinParcelFoam on micro scale (https://www.cfd-online.com/Forums/openfoam-solving/88972-attempt-run-rhopisotwinparcelfoam-micro-scale.html)

jabecker May 31, 2011 10:44

Attempt to run rhoPisoTwinParcelFoam on micro scale
 
Hey Foamers,

I am in serious help. I am working in rhoPisoTwinParcelFoam (OF 1.7.0) and I got the tutorial up and running great. I started implementing my own case by making small changes one at a time, to ensure that it would compile after every change. First, I made the changes to the mesh shape (using the same dimensions, just turned into a cube). Second, I turned it into a laminar flow. Third, I turned off the thermoCloud1Properties (as I only have one type of parcel) and can change around the cloud positions in kinematicCloud1Positions. But, as soon as I try to make it on a micro scale, which is what I need for my case, I get the following error:

--> FOAM FATAL ERROR:
Cannot find parcel injection cell. Parcel position = (5e-06 5e-06 0)

From function Foam::InjectionModel<CloudType>::findCellAtPositio n(label&, vector&)
in file lnInclude/InjectionModel.C at line 176.

FOAM aborting

#0 Foam::error::printStack(Foam::Ostream&) in "/opt/openfoam170/lib/linux64GccDPOpt/libOpenFOAM.so"
#1 Foam::error::abort() in "/opt/openfoam170/lib/linux64GccDPOpt/libOpenFOAM.so"
#2 Foam::InjectionModel<Foam::KinematicCloud<Foam::ba sicKinematicParcel> >::findCellAtPosition(int&, Foam::Vector<double>&) in "/opt/openfoam170/lib/linux64GccDPOpt/liblagrangianIntermediate.so"
#3
in "/home/becker/OpenFOAM/becker-1.7.0/applications/bin/linux64GccDPOpt/rhoPisoTwinParcelFoam"
#4
in "/home/becker/OpenFOAM/becker-1.7.0/applications/bin/linux64GccDPOpt/rhoPisoTwinParcelFoam"
#5
in "/home/becker/OpenFOAM/becker-1.7.0/applications/bin/linux64GccDPOpt/rhoPisoTwinParcelFoam"
#6
in "/home/becker/OpenFOAM/becker-1.7.0/applications/bin/linux64GccDPOpt/rhoPisoTwinParcelFoam"
#7 __libc_start_main in "/lib/libc.so.6"
#8
in "/home/becker/OpenFOAM/becker-1.7.0/applications/bin/linux64GccDPOpt/rhoPisoTwinParcelFoam"
Aborted

I am really confused by this because the parcel injection cell is never specified:confused::confused:. It had worked perfectly fine before I changed the convertToMeters in the blockMeshDict from 1 to 0.000001 and the corresponding positions in kinematicCloud1Positions from 0.25 to 0.25e-5. When it says "Parcel position = (5e-06 5e-06 0)" it is just stating the first point from the kinematicCloud1Positions file. Does anyone have any idea how to get rid of this error? Any help would be greatly appreciated:D.

Thanks in advance,
Jen

jabecker June 9, 2011 08:35

Hey Everyone,

I just wanted to update you all with a solution (because I know how frustrating it is to look at a post and never find an answer or response). From my understanding, when you receive this error OpenFOAM does not recognize the stated injection parcel point. In my case, the parcel position was directly on the boundary and as long as I changed to be slight inside the boundary then the error went away.

So I started with the position (5e-06 5e-06 0) and all I did was change it to (4.99999e-06 4.99999e-06 0) and the error went away.

I hope this follow up helps at least one person in the future, as something similar sure would have saved me a lot of time and error.

Enjoy:D,
Jen

mayank.dce2k7 August 15, 2013 23:55

Thanks, it helped me.

sourav90 April 13, 2021 08:52

Quote:

Originally Posted by jabecker (Post 311258)
Hey Everyone,

I just wanted to update you all with a solution (because I know how frustrating it is to look at a post and never find an answer or response). From my understanding, when you receive this error OpenFOAM does not recognize the stated injection parcel point. In my case, the parcel position was directly on the boundary and as long as I changed to be slight inside the boundary then the error went away.

So I started with the position (5e-06 5e-06 0) and all I did was change it to (4.99999e-06 4.99999e-06 0) and the error went away.

I hope this follow up helps at least one person in the future, as something similar sure would have saved me a lot of time and error.

Enjoy:D,
Jen


Sure. Good job posting the solution. I fixed a similar issue with your idea :D


All times are GMT -4. The time now is 02:26.