Add mean velocity force GUI support#244
Add mean velocity force GUI support#244kevinsmia1939 wants to merge 2 commits intojaheyns:masterfrom
Conversation
|
Thank you, this looks good! I'll just look into your queries and get back to you. |
porosityProperties is used and generated for the porousSimpleFoam solver (if the flow is incompressible/steady-state) and fvOptions is used for the other solvers.
You're right. I have unified these two, so that we only have a single fvOptions in system/. Please could you update your code accordingly?
This is probably a minor difference caused by different versions of FreeCAD or OpenCascade or similar. I'll investigate at some point, but for now we can ignore this. If you feel like making your test case into a macro and adding it to the CfdOF tests, that would be really helpful, since at the moment we don't have any test coverage for the periodic boundaries (or this new mean velocity force). |
34497aa to
207188b
Compare
|
Hi, I incorporated your changes, verify that codes works and test pass (other than that propeller test). I will be adding test to periodic boundary and mean velocity force in the next PR. |
124d822 to
39f03c2
Compare
Add mean velocity force GUI support fix ui incorporate changes fix ui fix icon initial periodic test initial periodic test remove unuse file add screenshot add screenshot add screenshot add screenshot
d81f6d6 to
5a237b2
Compare
|
I add test case, but it is a simple test that compare the case file output and known good value. |
This PR introduce initial implementation of adding meanVelocityForce into fvOptions. The new option is meanVelocityForce which apply constant mean velocity.
The example usage of meanvelocityforce is to impose a flow where there is no inlet boundary, in this example, a periodic boundaries are use, since imposing flow on periodic boundary is not allowed.
test4.FCStd.txt
This is the generated fvOptions inside case/constant
Current implementation has limitations:
Only constant velocity
selectionMode set to all, future work can support cellZone
Things that I noticed. Data/Templates/case/constant/fvOptions has settings for porousZones but if porous zones were added, the file porosityProperties will be generated instead of the one in fvOptions, is this the same thing?
There was also fvOptions_OF10 inside Data/Templates/case/Allrun for scalar transport, this might conflict, we might need to unify them in the future.
Note that majority of the code was generated with OpenAI Codex since I am not so familar with the code here. I practice my due diligence and test this new feature to validate the code.



There are test that failed, but it look like you tried to fix it in the previous commit, not sure why it fail again.