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.

Sign up for GitHub

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

Jump to bottom

Make sure NEON or PLUMBER options are only in their own extension of the tower_site base class #2944

Open
ekluzek opened this issue Jan 27, 2025 · 0 comments
Open

Make sure NEON or PLUMBER options are only in their own extension of the tower_site base class #2944

ekluzek opened this issue Jan 27, 2025 · 0 comments
Assignees
@ekluzek
Labels
bfb bit-for-bit code health improving internal code structure to make easier to maintain (sustainability) enhancement new capability or improved behavior of existing capability test: python Pass clm_pymods test suite plus Python sys/unit tests before merging

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Jan 27, 2025

We want to make sure that the NEON and PLUMBER specific options are only in their own extension of the tower_site base class.
@ekluzek ekluzek added bfb bit-for-bit code health improving internal code structure to make easier to maintain (sustainability) enhancement new capability or improved behavior of existing capability test: python Pass clm_pymods test suite plus Python sys/unit tests before merging labels Jan 27, 2025
@ekluzek ekluzek self-assigned this Jan 27, 2025
@ekluzek ekluzek mentioned this issue Jan 27, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ekluzek ekluzek

Labels
bfb bit-for-bit code health improving internal code structure to make easier to maintain (sustainability) enhancement new capability or improved behavior of existing capability test: python Pass clm_pymods test suite plus Python sys/unit tests before merging
Projects
LMWG: Sprint Planning Board
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ekluzek