-
Notifications
You must be signed in to change notification settings - Fork 4
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
access-fms: create an SPD for ACCESS-NRI's FMS fork #162
Conversation
Can you please describe why a fork was needed, and provide a diff? |
Hi @penguian , The FMS SPR was forked because we do not want to use the upstream FMS repository. We want to use |
|
I created the diff myself.
|
Could you please explain why the package is called Also, could you briefly describe the reasoning for the other differences between the builtin |
Hi @penguian , IIRC, ACCESS-OM3 uses the upstream FMS SPR and ACCESS-OM2, with generic-tracer support, needs to use an older FMS. We needed to be able to build both and I think that's the reason for the Do you need to be able to build the upstream fiat package and the 'access' fiat package? If so, then IIRC, some of the differences are due to our FMS being much older. The decorators are because the Spack package name doesn't match the library name. I've tried to only include functionality we need in the SPR. BTW, The diff I pasted above is comparing our access-fms SPR to the |
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.
Approved. See the Conversation for comments.
No description provided.