View Issue Details

IDProjectCategoryView StatusLast Update
0001963OpenFOAMBugpublic2017-09-05 09:20
Reporterriefler Assigned Towill  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
PlatformGNU/LinuxOSUbuntuOS Version14.04
Summary0001963: icoUncoupledKinetmaticParcelFoam - wrong collision data positions output
DescriptionThe position data in <timePoint>/lagrangian/kinematicCloud/collisionRecordsWallPRel seems to be wrong; when I change the position of the particle in the attached case (./const/kinematicCloudPositions), e.g. change of y-position, the data in collisionRecordsWallPRel remains nearly the same, although the change in position is much larger. Additionally, the 'WallData' vector makes no sense for me.
Steps To Reproducerun icoUncoupledKinetmaticParcelFoam
TagsNo tags attached.

Activities

riefler

2016-01-06 11:44

reporter  

henry

2016-01-06 12:05

manager   ~0005802

Can you provide a patch to fix this problem?

riefler

2016-01-06 12:29

reporter   ~0005803

I would do; however, I don't know in which routine/C-file the collision position is calculated ('WallCollisionRecordI.H' is my last clue of 'pRel')

wyldckat

2017-09-02 16:43

updater   ~0008672

@riefler: Since you should be more familiar with this issue, could you test if this is still an issue with OpenFOAM 5.x or OpenFOAM-dev?

will

2017-09-05 09:20

manager   ~0008695

Last edited: 2017-09-05 09:20

PRel is the relative distance between the centre of the particle and the collision site. That's why it doesn't change.

WallData appears to be a tangential overlap vector. I don't know why this is stored or written as part of the collision records, but that's what it is.

Issue History

Date Modified Username Field Change
2016-01-06 11:44 riefler New Issue
2016-01-06 11:44 riefler File Added: icoUncoupled+Fiber-WrongPRel.zip
2016-01-06 12:05 henry Note Added: 0005802
2016-01-06 12:29 riefler Note Added: 0005803
2016-03-11 11:44 administrator Category 3.0.1 => (No Category)
2016-03-20 20:41 wyldckat Category (No Category) => Bug
2017-09-02 16:43 wyldckat Note Added: 0008672
2017-09-05 09:20 will Assigned To => will
2017-09-05 09:20 will Status new => closed
2017-09-05 09:20 will Resolution open => no change required
2017-09-05 09:20 will Note Added: 0008695
2017-09-05 09:20 will Note Edited: 0008695