|
[Sponsors] |
problem running case, what exactly happens deppends on what way you run the case |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
February 29, 2024, 18:41 |
problem running case, what exactly happens deppends on what way you run the case
|
#1 |
New Member
stijn
Join Date: Feb 2024
Posts: 7
Rep Power: 2 |
Hi,
I have a problem with a openfoam case i want to run, what i am trying to do is performing a simulation of the thermal evolution of the fluid in a pipe surounded by air, but if i try to run my case it doesn’t work, what goes wrong is weirdly enhough dependent on how i try to run the case, if i try manualy it gives a warning and a error and if i try to run it with Allrun-parallel it gives other warnings and a other error, but if i try to run it with Allrun-serial it appears to run but it does not get anywhere, for example i ran the case for 15 hours, but the first result hasn’t showed up yet, and so it appears to run in loops, if i am wrong please show me, but i would expect that i would at least have the first result after 15 hours wit a i7-8750H proccesor with 6 cores and a case with only 625000 cells, i think the problem has something to do with the boundry conditions I got this warning with every run i tried This warning did i get at snappyHexMesh --> FOAM Warning : Displacement (2.326676e-06 1.125094e-05 -3.009801e-06) at mesh point 6246 coord (0.09072973 0.725292 -0.0627314) points through the surrounding patch faces Smoothing displacement ... This warrning did i get with log.changeDictionary.*: --> FOAM Warning : From bool merge(bool, Foam::dictionary&, const Foam::dictionary&, bool, const Foam::HashTable<Foam::List<Foam::word> >&) in file changeDictionary.C at line 304 Reading "/home/stijn/OpenFOAM/OpenFOAM-v2012/tutorials/own_cases/pipe_heat_loss_test/system/air/changeDictionaryDict.boundary" at line 21 to 41 Ignoring non-existing entry minY when i tried to do the case manualy i got a error like this one And with log.chtMultiRegionFoam i got this error --> FOAM FATAL ERROR: (openfoam-2012) cannot be called for a calculatedFvPatchField on patch pipeenclosed_internalfluid of field U in file "/home/stijn/OpenFOAM/OpenFOAM-v2012/tutorials/own_cases/pipe_heat_loss_test/0/internalfluid/U" You are probably trying to solve for a field with a default boundary condition. From Foam::tmp<Foam::Field<Type> > Foam::calculatedFvPatchField<Type>::gradientIntern alCoeffs() const [with Type = Foam::Vector<double>] in file fields/fvPatchFields/basic/calculated/calculatedFvPatchField.C at line 188. And when i tried to run the case with Allrun-parallel i got warnings an errors: This warning did i get with log.redistributePar.reconstruct-*: --> FOAM Warning : From int main(int, char**) in file redistributePar.C at line 2400 Working in decompose or reconstruction mode automatically implies -overwrite This error did i get with log.redistributePar.redist-air: [1] --> FOAM FATAL ERROR: (openfoam-2012) [1] Non-processor patches not synchronised. Master patch 0 name:inlet type:inlet Processor 1 patch 0 has name:minX type:genericPatch[2] And i get this error at log.chtMultiRegionFoam: --> FOAM FATAL ERROR: (openfoam-2012) [3] On patch procBoundary3to4 trying to access out of range neighbour processor 4. This can happen if trying to run on an incorrect number of processors [3] [3] From virtual void Foam:rocessorPolyPatch::initUpdateMesh(Foam::Pst reamBuffers&) [3] in file meshes/polyMesh/polyPatches/constraint/processor/processorPolyPatch.C at line 368. all files of this case are available on this link: https://1drv.ms/f/s!Agflt1nDTyHxhlNo...BjJ-I?e=zCzsLX |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Problem with foam-extend 4.0 ggi parallel run | Metikurke | OpenFOAM Running, Solving & CFD | 1 | December 6, 2018 16:51 |
Problem in foam-extend 4.0 ggi parallel run | Metikurke | OpenFOAM Running, Solving & CFD | 0 | February 20, 2018 07:34 |
Case running in parallel gives error whereby running in serial works | Harak | OpenFOAM Running, Solving & CFD | 8 | October 17, 2015 12:12 |
tableProperties.lookup(Y[i].name()) problem when run my case | zqlhzx | OpenFOAM Running, Solving & CFD | 0 | December 12, 2013 04:30 |
Free surface boudary conditions with SOLA-VOF | Fan | Main CFD Forum | 10 | September 9, 2006 13:24 |