-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logging pressure solver #135
base: master
Are you sure you want to change the base?
Conversation
test/test_psolver.jl
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where is the logger used in this example?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just by calling WaterLily.logger(...)
triggers the @debug
macros to print the expression behind to the log file. If this is not done @debug
is not evaluated. Line 37 of test_psolver.jl
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you include an example of reading the file? And add a sample plot as a comment to this PR?
I am not sure what to do with the plotting script for the logger, it's really ugly and I don't want to include in into
the result is this |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #135 +/- ##
==========================================
- Coverage 94.29% 93.28% -1.02%
==========================================
Files 12 12
Lines 526 536 +10
==========================================
+ Hits 496 500 +4
- Misses 30 36 +6 ☔ View full report in Codecov by Sentry. |
maybe we could have a |
Yes, that's should not go in src, but in examples or ext. |
I have added the logger as an extension (via I also renamed the pressure logger example to |
Reviving this PR. Now that we've move out examples, all that left is the logger. Is this ready to go? |
This looks good. I understand that the |
Yes, none of the macros ( |
This is done now; let me know if anything remains to be done. |
Yes, I think it is much better to have all the plots utils in the extension. |
These are the results of the benchmark. If we are happy with this, I will merge it.
|
Comparison should be also on the CPUx16 backend right? Anyways this looks good. Do you have the chance to test on GPU, such as DelftBlue? |
This is a draft pull request that implements some changes in the pressure solver.
A sample of the pressure solver log can be found here.
WaterLily.log
Changes:
@debug
viaLoggingExtras.jl
to monitor the pressure residuals, iterations, etc.remove the adaptive multilevel pressure solver and increase the size of the smallest domain to N>=8add a test of the impulsive flow around a cylinder to check the pressure forces and oscillations in the pressure field.Things to do:
@debug
macro and use@logmsg
instead for the pressure logging, see https://github.com/JuliaLogging/LoggingExtras.jl[ ] Type dispatch of the adaptive/non-adaptive multilevel pressure solver depending on the precision?[ ] some proper pressure solve tests