Debug wall collisions and particle state writing - #1745
Conversation
…s and collision check upper boundary
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1745 +/- ##
==========================================
+ Coverage 61.67% 61.71% +0.04%
==========================================
Files 84 84
Lines 21619 21642 +23
Branches 3196 3196
==========================================
+ Hits 13334 13357 +23
Misses 6093 6093
Partials 2192 2192 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Lines of Code
|
|
@sbryngelson I am pretty sure that this is not an issue with the branch, and I am beginning to have several branches all with scattered fixes to various things that I have been working on. Do we think that this is something to do with errors on the Phoenix runners, or have they been running successfully for others? Should I get on Phoenix and resolve this? |
Thanks for letting me know. I am desperately trying to fix everything, as runner behavior changed again. Your code is probably fine. |
Description
Branch created to debug some issues I was having with particles not colliding with one of the domain boundaries when slip wall was used. The solution wound up being that the variable populating slip wall BC at the top of the boundary was not populated on the GPU. Updates have been made.
While I was in the code, I also noticed that
ib_state_wrtwill not trigger in post-process is all IBs are from particle_clouds. This is because when it checks for the number of IBs to create the array, it was not including cloud particles, and therefore generated 0-lengthed arrays. I added the particle cloud count to this check, allowing it to store more IB information for output.Type of change (delete unused ones)
Testing
I generated a 2D, 2000 particle case as:
This case was run on an RTX 2080 Super with NVHPC/23.11
Checklist
Check these like this
[x]to indicate which of the below applies.