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

Merge main candidate 2021-02-19 #177

Merged
merged 608 commits into from
Feb 26, 2021
Merged

Conversation

alperaltuntas
Copy link
Member

Merges the main candidate from GFDL:

https://github.com/NOAA-GFDL/MOM6/pull/1328

Source code tree hasn't been changed yet, so no MOM_interface change is needed.

testing: aux_mom.cheyenne_{intel,gnu}

Raphael Dussin and others added 30 commits December 14, 2020 18:04
…-ncar-2020-12-15

Main candidate from NCAR (12/15/2020)
Doxygen was not assigning some docstrings for multiline variable
declarations, so this patch splits those variables to one per line, with
updated docstrings.

Whitespace was also condensed in several of the declarations.
…update-to-GFDL-20201215

this is corresponding to GFDL main branch commit 20201218 (hash # 0f664aa)
Reduction in line length of any lines exceeding 120 characters.
  - Call ice shelf initialization from within initialize_MOM.
  - This removes suppport for rotation.
diagnostics and restarts during the call from initialize_MOM
Hallberg-NOAA and others added 16 commits February 13, 2021 09:04
  Use the new scale argument to MOM_write_field to simplify write_vertgrid_file
and write_ocean_geometry_file.  All output and answers are bitwise identical.
  Added and used the file_type as the handle for input and output, changing from
using an integer.  This changes the type of one of the required arguments to
write_field, write_MOM_field, create_file, reopen_file, get_file_info,
get_file_times, get_file_fields, write_metadata_axis and write_metadata_field,
and added new variants of open_file, close_file and flush_file using this new
type.  Also added the new routine file_is_open.  All answers are bitwise
identical, but there are changes to multiple I/O interfaces.
  Added the new optional scale argument to the real versions of the
read_variable routines.  All answers are bitwise identical, but there are
new optional arguments to public routines.
  Revised the depth list type used in MOM_sum_output to accommodate I/O using
ordinary routines, and to make the code creating, reading and writing it
potentially separable from the MOM_sum_output module by avoiding the use of the
MOM_sum_output control structure in most of the routines.  Also changed the
index 'l' to 'li' in some places to avoid having it misread as '1'.  All answers
are bitwise identical but there are changes in some subroutine arguments.
Fixing an indexing error in MOM_barotropic
MOM6: +I/O interface changes, including a new file_type
	- this addresses a bug in the apply_ALE_sponge routine which
  	had been passing zero values to the remapping routine for the
	target grid thicknesses.
@gustavo-marques
Copy link
Collaborator

@alperaltuntas, can you please reduce the line length in:
config_src/mct_driver/mom_surface_forcing_mct.F90, line 499
This has been caught in the new set of tests.

Also, it looks like one of the tests in near_boundary_unit_tests is failing. I will look into that.

@gustavo-marques
Copy link
Collaborator

@alperaltuntas, did you have to resolve conflicts in MOM_lateral_boundary_diffusion.F90? If so, this could be the reason why one of the unit tests is failing. Should I send a PR to main_candidate_2021-02-19 fixing this?

@alperaltuntas
Copy link
Member Author

can you please reduce the line length in

done.

did you have to resolve conflicts in MOM_lateral_boundary_diffusion.F90

Yes. Check out the following comparison vs. the original candidate.

NOAA-GFDL/MOM6@dev-gfdl-main-candidate-2021-02-19...NCAR:main_candidate_2021-02-19

Should I send a PR to main_candidate_2021-02-19 fixing this

Yes, please.

@gustavo-marques
Copy link
Collaborator

@alperaltuntas, the unit test is still failing and I could not replicate that. Any idea why unit tests are passing in #178 and not in this PR?

@alperaltuntas
Copy link
Member Author

@gustavo-marques weird. will look into it.

@alperaltuntas
Copy link
Member Author

@gustavo-marques It looks like the MOM_lateral_boundary_diffusion unit tests are already failing in the current dev/ncar, but are passing in main_candidate_2021-02-19. I confirmed that that's the case by running the unit tests on Cheyenne with gnu. So, I believe, once this PR gets merged, the unit tests will be fixed.

@gustavo-marques
Copy link
Collaborator

Ok, thanks. Will merge this now.

@gustavo-marques gustavo-marques merged commit 9ced10b into dev/ncar Feb 26, 2021
@alperaltuntas alperaltuntas deleted the main_candidate_2021-02-19 branch December 8, 2021 16:59
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 this pull request may close these issues.