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

Single column CVmix, BLM, KPP, EPBL don't exit cleanly when run with dynamic symmetric memory #300

Closed
nichannah opened this issue May 23, 2016 · 2 comments

Comments

@nichannah
Copy link
Collaborator

nichannah commented May 23, 2016

They crash with an error message like:

FATAL from PE 1: mpp_sync_self: size_recv does not match of data received
FATAL from PE 2: mpp_sync_self: size_recv does not match of data received
FATAL from PE 3: mpp_sync_self: size_recv does not match of data received

Do we want a user friendly message instead to indicate that this combination is not supported?

Full run output here:

https://climate-cms.nci.org.au/jenkins/job/mom-ocean.org/job/MOM6_run/build=DEBUG,compiler=intel,experiment=ocean_only-single_column-EPBL,memory_type=dynamic_symmetric/

https://climate-cms.nci.org.au/jenkins/job/mom-ocean.org/job/MOM6_run/build=DEBUG,compiler=intel,experiment=ocean_only-CVmix_SCM_tests-wind_only-EPBL,memory_type=dynamic_symmetric/15/console

@nichannah nichannah changed the title Single column BLM, KPP, EPBL don't exit cleanly when run with dynamic symmetric memory Single CVmix, BLM, KPP, EPBL don't exit cleanly when run with dynamic symmetric memory May 23, 2016
@nichannah nichannah changed the title Single CVmix, BLM, KPP, EPBL don't exit cleanly when run with dynamic symmetric memory Single column CVmix, BLM, KPP, EPBL don't exit cleanly when run with dynamic symmetric memory May 23, 2016
@adcroft
Copy link
Collaborator

adcroft commented May 26, 2016

This is a test with a horizontal grid of only 2x2 points. In #290 there is discussion about whether halo updates for halos wider than the compute domain work or even make sense. At GFDL we have been testing these experiments with only 1 core. For now, I recommend reducing the core count to 1. It is an open issue whether we should support 1 point per core but if we did then we could presumably reduce the problem size from 2x2 to 1x1 (i.e. truly single column).

@nichannah
Copy link
Collaborator Author

The test cases run on a single PE. Otherwise this is a duplicate of #298.

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

No branches or pull requests

2 participants