Changes for multi-level perturbations #2205
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ewquon
pushed a commit
to ewquon/ERF
that referenced
this pull request
Mar 29, 2025
* ML perturbation modifications * forgot to include ref_ratio factor * add inputs for mulitlevel perturbations, ABL style * fix typo and whitespaces --------- Co-authored-by: Adam Sidney Wise <[email protected]> Co-authored-by: Adam Sidney Wise <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR modifies the perturbation capability to handle multi-levels. The major changes are:
This capability should only work with static levels and not with adaptive mesh refinement.
Additionally, an input file has been added to /Exec/DryRegTests/TurbulentInflow to showcase multi-level perturbations (pictures attached here, as well). This input file is for an atmospheric boundary layer.
Note that this capability seems to only work with the "source" option. When selecting the "direct" option, the perturbations seem to compound resulting in much larger than desired perturbations.
Step 0:
Step 100 (notice the theta range):
