View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003542 | OpenFOAM | Feature | public | 2020-08-31 09:30 | 2020-08-31 13:06 |
Reporter | peksa | Assigned To | henry | ||
Priority | low | Severity | feature | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Platform | GNU/Linux | OS | Ubuntu | OS Version | 15.04 |
Summary | 0003542: Consistent SIMPLE(C) not available in lagrangian PIMPLE-based solvers | ||||
Description | Dear developers, I was wondering whether there is a particular reason for lagrangian solver class not to support consistent SIMPLE (SIMPLEC) approach within the PIMPLE pressure coupling. I don't consider it a must feature but I'm interested to hear whether it is a rational decision and perhaps related to lagrangian source terms? Actually, I first noticed this because I was using a consistent keywork in fvSolution but didn't see any difference in solver performace. Perhaps a Warning message could be added to solvers which are not supporting SIMPLEC to prevent user misunderstandings / mistakes. -- peksa | ||||
Steps To Reproduce | See e.g. sprayFoam solver pEqn.H | ||||
Tags | No tags attached. | ||||
|
We don't have any Lagrangian cases for which it would be clearly beneficial. > Perhaps a Warning message could be added to solvers which are not supporting SIMPLEC to prevent user misunderstandings / mistakes. It would a substantial undertaking to add and maintain warning messages about functionality not present in all solvers. |
|
I agree with you, haven't seen any clear benefits either. Thank you for clarification. |
Date Modified | Username | Field | Change |
---|---|---|---|
2020-08-31 09:30 | peksa | New Issue | |
2020-08-31 09:37 | henry | Note Added: 0011480 | |
2020-08-31 09:46 | henry | Note Edited: 0011480 | |
2020-08-31 09:49 | peksa | Note Added: 0011481 | |
2020-08-31 13:06 | henry | Assigned To | => henry |
2020-08-31 13:06 | henry | Status | new => closed |
2020-08-31 13:06 | henry | Resolution | open => no change required |