-
Notifications
You must be signed in to change notification settings - Fork 353
Cleans up LIGHT data structures for greater efficiency #32
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
Cleans up LIGHT data structures for greater efficiency #32
Conversation
@@ -7,7 +7,7 @@ | |||
type (mpas_pool_type), pointer :: haloDataPool => NULL() | |||
! pool containing particle data not needing to be passed | |||
! between processors | |||
type (mpas_pool_type), pointer :: nonhaloDataPool => NULL() | |||
!type (mpas_pool_type), pointer :: nonhaloDataPool => NULL() |
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.
It looks like this is a simple repeated line error? It would need a separate framework PR, but would be easy and fast to get through.
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'm removing the nonHalo
feature until it is needed. But, you are right, it is a simple one-liner. I'll remove it and just leave it in framework for now because it isn't a big deal.
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.
It is now removed, so this shouldn't be dependent upon framework.
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.
@pwolfram I don't have time to test, but don't want to hold this up. Could you describe the testing you've done on this? It's good to compile in both intel and gnu, and compile using debug on one of them to catch unassigned variables. If you test using particles like that, then please merge after removing the framework line.
Whoops - I didn't look carefully enough. I need to make a branch |
I think it is possible to change the target branch of a PR. So after @mark-petersen creates the |
Good point - I see that now, thanks @mgduda |
I think I can just reorient the target branch for the merge. I don't think this needs to be rushed. |
6658d37
to
129debe
Compare
@mark-petersen, can you please let me know when you build the |
Thanks @mark-petersen! I've updated the base branch for the PR. |
1 similar comment
Thanks @mark-petersen! I've updated the base branch for the PR. |
Testing
|
Thanks for the testing info. Merge at will. |
Cleans up LIGHT data structures for improved inter-processor communication efficiency.
129debe
to
57f02a2
Compare
Make sure link/copy sources are absolute paths This allows config files to use relative paths and have them converted to absolute paths before links are created or files are copied. This is particularly useful when referring to MPAS-Model/ocean/develop or MPAS-Model/landice/develop.
* Use effective radii from microphysics by default * Changes for TEMPO submodule * Support for hail_aware microphysics * Add if statement to call hail-aware microphysics * Bug fix for hail-aware flag type * My python brain forgot the endif
Ocean/light restart cleanup
Removes code related to online autocorrelation computation, which is not used in practice.
Code cleanup removes communication needed for each particle for enhanced efficiency.
Results should be BFB under the current test cases.