-
Notifications
You must be signed in to change notification settings - Fork 15
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
Add initial pertubation for cluster pgen #67
Merged
Merged
Changes from all commits
Commits
Show all changes
25 commits
Select commit
Hold shift + click to select a range
68de864
Move cluster pgen to MeshPgen to allow for reductions
pgrete abc0822
Prepare hse test case for init pert
pgrete 3905cc0
Git add sigma_v plus test for cluster pgen
pgrete 196afe9
Fix index error in cooling test
pgrete 8d05808
Move iFT to utils from turb driver
pgrete e046a66
Isolate fmft construtor
pgrete fbbe2dc
Separate OU and FT parts from turbulence pgen
pgrete cd2420c
Make FMFT smooth and consistent for mesh refinement runs
pgrete 83de454
Fix update of internal RNG state
pgrete 8c74b1d
Remove restriction on unit domain dims
pgrete 6ed8170
Fix k_vec check on device
pgrete 2571e1b
Add init perturb for velocity field
pgrete 429d1b1
Move construction of modes to shared util
pgrete a616d93
Allow ghost zones filling in FMFT
pgrete 639fcc1
Add initial magnetic field perturbations
pgrete b31f88e
Add doc for cluster init perturb
pgrete 3ebd164
Fix typo for using host view
pgrete 9b114e6
Fixed entropy for ASCENT output
4a5010f
Clarified feedback efficiency error
08ab35c
Merge branch 'main' into pgrete/init-pert
forrestglines bd3c556
WIP: Limit velocity and temperature in Kinetic jet injection region (…
forrestglines 4c51506
Merge branch 'main' into pgrete/init-pert
pgrete bc98afa
Enable first order flux correct for non-vl2 integrators
pgrete 0c6596a
Fix comments
pgrete 8057a63
Fix weird missing header for non-mpi non-hdf5 builds
pgrete File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
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 we change to peak wavelength for these parameters? Or provide that as an alternative option?
It's awkward for a problem parameter to have a different action depending on the box size, especially when we'll be testing a number of box sizes.
Could also normalize
k
by code length instead of box length butl
seems more intuitive.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.
I don't have a strong preference here. I guess I'm just used to normalized units.
I agree that
l
(incode_length
) would be the most intuitive parameter given that all other params of this pgen are also in code units.I'll add it.