Move jigsaw_to_MPAS to mpas_tools#563
Conversation
|
This PR requires the changes to MPAS-Tools in MPAS-Dev/MPAS-Tools#311 |
TestingSo far, I successfully tested |
|
@mark-petersen and @pwolfram, this PR likely needs to go in at a point when |
testing_and_setup/compass/ocean/coastal/USDEQU120cr10rr2/build_mesh/config_culled_mesh.xml
Outdated
Show resolved
Hide resolved
testing_and_setup/compass/ocean/global_ocean/config_files/config_mesh_metrics.xml
Outdated
Show resolved
Hide resolved
Yep, that's exactly what I mean. We should only merge this at a point where |
|
Thanks @xylar, I understand now and agree. |
|
@mark-petersen-- thoughts on when you want to do the |
775a3ac to
669423c
Compare
669423c to
377e8a7
Compare
377e8a7 to
ed42331
Compare
|
This should be ready to rebase right after #485 gets merged. |
8e3c94e to
e647f20
Compare
TestingI am testing with a test build of I am testing through the Baselines are here: Runs with this branch are here: Many, many coastal test cases are broken and I am doing my best to fix them in #662. This will become the baseline. Baseline (from #662) finished:
Tests succeeded and bit-for-bit:
|
mark-petersen
left a comment
There was a problem hiding this comment.
@xylar I know there are some complications with timing and order here. Go ahead and merge when you are ready, and we can make additional changes if needed in another PR.
I don't think that's a safe attitude for this PR. I think every affected test case needs to be checked to make sure it is bit-for-bit before and after these changes. Otherwise, we will not have confidence in such an extensive set of changes, and it will likely affect everyone working with non-idealized test cases for awhile going forward. |
|
@xylar, I'm trying to test this. I need to load compass 0.1.9 on grizzly. The load latest is 0.1.8. I hate to say it, but I don't know how to create compass 0.1.9 locally myself. Are there instructions? I should really know how to do it. |
|
@mark-petersen, please use |
It's quite complicated. I have to make test builds of both |
|
Just FYI, I do plan to spend a considerable amount of time in the next 3-4 weeks writing documentation, and this will be part of the process I will be documenting. |
|
Thanks @xylar . I set up and ran test cases on grizzly with |
Like I've said, the mesh conversion tools really need to be replaced with xarray/dask versions that are faster and parallel. That would be a great project for the right student or postdoc... |
|
And thanks very much for testing. Let me know how it goes with |
|
@sbrus89, is this something you will have time to test today? |
It ran through init and began spin-up successfully. Also just ran QU240wISC successfully. |
|
@xylar, I'll try to run some tests this afternoon |
|
@sbrus89, wonderful! That would be much appreciated! |
|
This one worked: |
The safer order of operations would be for me to create |
|
OK. What if you do what's needed tomorrow morning Berlin time for compass 0.1.9, and I'll merge this tomorrow morning NM time? |
|
Perfect! (Assuming @sbrus89's testing goes well.) |
|
@mark-petersen, |
…3800) Update mpas-source: compass only This PR brings in a new mpas-source submodule with changes only to the ocean core. All of the changes are to the COMPASS testing code that is not used in E3SM, so this PR should have no effect on E3SM. The COMPASS commits are: * MPAS-Dev/MPAS-Model#563 'xylar/ocean/remove_jigsaw_to_mpas' * MPAS-Dev/MPAS-Model#662 'xylar/ocean/fix_broken_compass_tests' * MPAS-Dev/MPAS-Model#664 'xylar/ocean/fix_plot_initial_state' [BFB]
Update mpas-source: compass only This PR brings in a new mpas-source submodule with changes only to the ocean core. All of the changes are to the COMPASS testing code that is not used in E3SM, so this PR should have no effect on E3SM. The COMPASS commits are: * MPAS-Dev/MPAS-Model#563 'xylar/ocean/remove_jigsaw_to_mpas' * MPAS-Dev/MPAS-Model#662 'xylar/ocean/fix_broken_compass_tests' * MPAS-Dev/MPAS-Model#664 'xylar/ocean/fix_plot_initial_state' [BFB]
…develop Move jigsaw_to_MPAS to mpas_tools MPAS-Dev#563 This merge uses `mpas_tools.mesh.creation` instead of `jigsaw_to_MPAS`. These tools are being moved to MPAS-Tools to allow them to be used by other workflows, see MPAS-Dev#550. This merge includes: * removing the `jigsaw_to_MPAS` module from COMPASS * Updating the `compass` environment version to the one that includes * `mpas_tools` with `mesh.creation`. * Removing links to `jigsaw_to_MPAS` from several test cases * Calling `build_mesh` and `inject_bathymetry` from `mpas_tools` in test * cases that use these * Switching from `mpas_tools.conversion` to `mpas_tools.mesh.conversion` * (though the former still exists for backward compatibility) * A small fix to some cartopy-related axis calls that seem to be * depricated
This merge uses
mpas_tools.mesh.creationinstead ofjigsaw_to_MPAS. These tools are being moved to MPAS-Tools to allow them to be used by other workflows, see #550.This merge includes:
jigsaw_to_MPASmodule from COMPASScompassenvironment version to the one that includesmpas_toolswithmesh.creation.jigsaw_to_MPASfrom several test casesbuild_meshandinject_bathymetryfrommpas_toolsin test cases that use thesempas_tools.conversiontompas_tools.mesh.conversion(though the former still exists for backward compatibility)closes #550