-
Notifications
You must be signed in to change notification settings - Fork 145
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
Formatting fix for the write to obs_seq.final with cce #491
base: main
Are you sure you want to change the base?
Conversation
…s%next_time, and obs%cov_group
@hkershaw-brown there is still a bit of difference in these lines of the obs_seq.final. The first is with Intel, the second with cce after the formatting was added:
I added commas to the format statement because they are present in the obs_seq.final originally with cce. But they aren't with Intel. Similarly, there's extra spaces between values with intel. Do you think we should make them look identical in these ways as well? |
With edits made, the writes for obs%prev_time, obs%next_time, and obs%cov_group output as such for the different compilers.
cce is just missing some spacing. |
…bs_seq.final with intel and cce
Final edits fix the inconsistencies in the spacing so that all compilers produce the exact same output. This also matches the formatting for intel and gfortran on Cheyenne.
|
Description:
There are inconsistencies in the obs_seq.final formatting across compilers on Gust. Specifically, the cce compiler produces an output of 2*-1 rather than -1 -1 (for intel and ifx) for obs%prev_time, obs%next_time, and obs%cov_group
I added formatting to the write statement on line 2508 of obs_sequence_mod.f90
Fixes issue
Fixes #484
Types of changes
Documentation changes needed?
Tests
Ran filter with lorenz_96 on Gust with intel and cce, compared obs_seq.final files.
Checklist for merging
Checklist for release
Testing Datasets