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

[INSTALL] set build_type=Release for crtm #827

Closed
AlexanderRichert-NOAA opened this issue Oct 16, 2023 · 8 comments
Closed

[INSTALL] set build_type=Release for crtm #827

AlexanderRichert-NOAA opened this issue Oct 16, 2023 · 8 comments
Assignees
Labels
INFRA JEDI Infrastructure

Comments

@AlexanderRichert-NOAA
Copy link
Collaborator

Note: Please search to see if an issue already exists for the software you are requesting to be installed.

Which software in the stack would you like installed?
crtm build_type=Release

What is the version/tag of the software?
(current)

What compilation options would you like set?
build_type=Release

Installation timeframe:
1.5.1

@AlexanderRichert-NOAA
Copy link
Collaborator Author

Requesting cmake build type 'Release' for crtm per convo with @DavidHuber-NOAA. @climbfuji, it looks like the default build_type in the crtm recipe as of 1.5.0 is RelWithDebInfo. How critical is this? And @DavidHuber-NOAA can you add some detail here on why you want the regular 'Release' build type?

@climbfuji
Copy link
Collaborator

We should also let @BenjaminTJohnson know about this suggested change.

@DavidHuber-NOAA
Copy link
Collaborator

@AlexanderRichert-NOAA Yes, CRTM built with RelWithDebInfo produces different results from Release when run within the GSI for the radiances from the microwave instruments amsua_n15, amsua_n18, amsua_n19, atms_npp, and atms_n20. Unfortunately, I do not have the regression test comparisons anymore between these two versions, but the differences were quite small as I recall. That said, I am amenable to keeping RelWithDebInfo if there is a good reason for it.

@BenjaminTJohnson
Copy link

@AlexanderRichert-NOAA sorry, just want to verify that this is CRTM v2.4.0, correct?

@AlexanderRichert-NOAA
Copy link
Collaborator Author

Correct-- spack-stack currently uses 2.4.0, then assuming we made this change, we would keep the setting moving forward.

@climbfuji
Copy link
Collaborator

PR spack/spack#41163 was just merged into spack develop. This PR changes the build type for CRTM to release. We should cherry-pick the PR (or at least the CRTM part of it) after #884 is merged.

@climbfuji
Copy link
Collaborator

This still needs to be done for releasde/1.6.0 (on release branch).

@climbfuji
Copy link
Collaborator

Closed via #919

@github-project-automation github-project-automation bot moved this from In Progress to Done in spack-stack-1.6.0 (2023 Q4) Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
INFRA JEDI Infrastructure
Projects
No open projects
Development

No branches or pull requests

6 participants