|
[Sponsors] |
January 9, 2015, 06:58 |
impinged mass on patch cell faces
|
#1 |
Senior Member
Join Date: Jan 2010
Location: Stuttgart
Posts: 150
Rep Power: 16 |
Hello together,
I would like to visualize the mass of lagrangian particles that impignes the individual patch cell faces at the wall. Since it is possible to have the output of impinged mass over whole patches, with some implementation it should also be possible to calculate that for every single patch cell faces and visualize it afterwards in paraview. Does anybody of you have an idea how to start doing that? Thanks in advance and kind regards Chrisi |
|
January 9, 2015, 13:33 |
|
#2 |
Senior Member
Kyle Mooney
Join Date: Jul 2009
Location: San Francisco, CA USA
Posts: 323
Rep Power: 17 |
Hi Chrisi,
I'm not 100% sure but the 'facePostProcessing' CloudFunctionObject looks like it might do the trick. Code:
/src/largrangian/intermediate/submodels/CloudFunctionObjects/FacePostProcessing/ cheers! Kyle |
|
January 10, 2015, 08:48 |
|
#3 |
Senior Member
Join Date: Jan 2010
Location: Stuttgart
Posts: 150
Rep Power: 16 |
Hi Kyle,
thanks a lot that works! I only need to generate a new faceZone from my patches and run the facePostProcessing CloudFunctionObject on that new face zone. I am not that familiar with those CloudFunctionObject. Can you tell me how I can create new ones. As bases I would take that facePostProcessing. Which parts I have to compile new in my one librarys and how to link them correctly afterwards? Kind regards Chrisi |
|
January 13, 2015, 15:51 |
|
#4 |
Senior Member
Kyle Mooney
Join Date: Jul 2009
Location: San Francisco, CA USA
Posts: 323
Rep Power: 17 |
Hi Chrisi,
I think you can populate the cloudFunctions{} subdictionary which is at the bottom of the kinematicCloudProperties dictionary in most of the lagrangian tutorials. Usually you could just start out with something like this: Code:
cloudFunctions { myCloudfunctionObject { type facePostProcessing; } } Once you start the simulation it will halt every time the FO runs since you're missing the rest of the inputs. You could then start filling them in one by one. Alternatively you can inspect the constructor and dictionary readers in the FacePostProcessing.C source code (around lines 260) to get a better idea of the inputs its looking for. I hope that helps! Cheers, Kyle |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[snappyHexMesh] SnappyHexMesh for internal Flow | vishwa | OpenFOAM Meshing & Mesh Conversion | 24 | June 27, 2016 08:54 |
snappyhexmesh remove blockmesh geometry | philipp1 | OpenFOAM Running, Solving & CFD | 2 | December 12, 2014 10:58 |
foam-extend_3.1 decompose and pyfoam warning | shipman | OpenFOAM | 3 | July 24, 2014 08:14 |
[snappyHexMesh] snappyHexMesh won't work - zeros everywhere! | sc298 | OpenFOAM Meshing & Mesh Conversion | 2 | March 27, 2011 21:11 |
[Commercial meshers] Trimmed cell and embedded refinement mesh conversion issues | michele | OpenFOAM Meshing & Mesh Conversion | 2 | July 15, 2005 04:15 |