Skip to content
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

Deleting the CCPP subdirectory #222

Open
nbren12 opened this issue Sep 23, 2021 · 6 comments
Open

Deleting the CCPP subdirectory #222

nbren12 opened this issue Sep 23, 2021 · 6 comments

Comments

@nbren12
Copy link
Contributor

nbren12 commented Sep 23, 2021

Would there be any objections to deleting the CCPP subdirectory since we don't actually use this for any builds? I think this has been proposed in the past by e.g @ofuhrer.

It's a potential source of conflicts with upstream, and it seems like a good opportunity to delete some effectively dead code.

I ran into this when comparing our code to the version Alexie and Vladimir are using for emulation: https://github.com/AlexBelochitski-NOAA/fv3atm_full_physics_nn_emulator.

@ofuhrer
Copy link
Contributor

ofuhrer commented Sep 23, 2021

Not sure if I suggested it, but I tend to agree with this. This directory introduces a lot of duplicate and dead code which is not helpful when searching, editing, grepping, ... throughout the code base. Adding it back would be trivial in case needed.

@nbren12
Copy link
Contributor Author

nbren12 commented Sep 23, 2021

@frodre you were using this at some point I recall, but needed to compile from the top-level UFS repo?

@frodre
Copy link
Contributor

frodre commented Sep 30, 2021

@nbren12, sorry I forgot to reply to this. I'm fine with removal too. We were compiling UFS at one point, but I don't plan or think we have plans for using that anytime soon.

@nbren12
Copy link
Contributor Author

nbren12 commented Sep 30, 2021

Thoughts @mcgibbon?

@mcgibbon
Copy link
Collaborator

I reference this directory periodically but I can go to the CCPP repo directly instead. The CCPP subdirectory is the main place I go when I want to understand what a part of the physics is actually doing. The main risk of looking elsewhere for this info is that upstream CCPP may receive updates our code will not.

@nbren12
Copy link
Contributor Author

nbren12 commented Sep 30, 2021

Ok. I think I'll remove it. I agree the CCPP package is easier to follow, but there are no guarantees that the CCPP code corresponds to the gfsphysics (although in practice this is true for some configs).

nbren12 added a commit that referenced this issue Sep 30, 2021
We don't actually use this code and the overlap with gfsphysics could be
confusing.

Resolves #222
@nbren12 nbren12 mentioned this issue Sep 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants