-
Notifications
You must be signed in to change notification settings - Fork 849
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
Allow different OUTPUT_WRT_FREQ for each output file #1552
Conversation
This pull request introduces 25 alerts when merging 6ad89f7 into 3832a8f - view on LGTM.com new alerts:
|
This pull request introduces 25 alerts when merging 63bf74c into 3832a8f - view on LGTM.com new alerts:
|
This pull request introduces 25 alerts when merging 527357d into 2786e53 - view on LGTM.com new alerts:
|
This pull request introduces 22 alerts when merging 5a86fb1 into 2786e53 - view on LGTM.com new alerts:
|
I don't know why there are suddenly all these additional lgtm alerts. Most of them have nothing to do with what I did. I fixed 3 of them. |
This pull request introduces 22 alerts when merging e8fcf48 into 2786e53 - view on LGTM.com new alerts:
|
This pull request introduces 22 alerts when merging ca466b1 into 2786e53 - view on LGTM.com new alerts:
|
This pull request introduces 22 alerts when merging 97a1b1d into a288828 - view on LGTM.com new alerts:
|
This pull request introduces 22 alerts when merging 6ff6acd into c8ccde5 - view on LGTM.com new alerts:
|
This pull request introduces 22 alerts when merging 5a80ab7 into 4c3311f - view on LGTM.com new alerts:
|
This pull request introduces 22 alerts when merging 5f0af78 into 4c3311f - view on LGTM.com new alerts:
|
This pull request introduces 22 alerts when merging fac06fa into 3a5b668 - view on LGTM.com new alerts:
|
This pull request introduces 2 alerts when merging 3702598 into 3f3cb55 - view on LGTM.com new alerts:
|
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
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.
LGTM fixes below
This pull request introduces 2 alerts when merging d5bd78b into 3f3cb55 - view on LGTM.com new alerts:
|
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
Co-authored-by: Pedro Gomes <38071223+pcarruscag@users.noreply.github.com>
I'll update the documentation as well |
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.
LGTM
discadj_incomp_turb_NACA0012_sa now fails with a small difference in residuals. But this case passed the regression test on my machine. I don't see what could have triggered this change. |
Thanks, just rerunning the regression seemed to fix the discrepancy. OK, I'll merge, and I'll add another beer to the IOU list! |
Proposed Changes
Give a brief overview of your contribution here in a few sentences.
add frequency for each filename in OUTPUT_FILES:
OUTPUT_WRT_FREQ= 10, 100, 50
for dual timestepping, write only the restart files twice (for timestep n and n-1) and not the visualisation files.
history output accepts fields
marker_inlet does not need normalized vectors (removed the error message)
- DONE The suggestion was to just extend the OUTPUT_WRT_FREQ instead of introducing a new keyword VOLUME_OUTPUT_FREQUENCIES.
Related Work
Resolve any issues (bug fix or feature request), note any related PRs, or mention interactions with the work of others, if any.
#1495
#1539
#1493
PR Checklist
Put an X by all that apply. You can fill this out after submitting the PR. If you have any questions, don't hesitate to ask! We want to help. These are a guide for you to know what the reviewers will be looking for in your contribution.