E3SM-Project / E3SM-Project/scorpio

PIO1 fails on box_rearrange::compute_dest for a high-res E3SM G case

Open
#189 0 comments 0 reactions 1 assignee Claimed by @jayeshkrishna View on GitHub
bug High Priority Next Release PIO1_deprecated
Dominant language
C++
Stars
22
Forks
20
Avg merge
12d 19m
Merged PRs (30d)
1

Description

E3SM G case: compset GMPAS-NYF, res T62_oRRS18to6v3
PE layout: 9600x1 (single thread)
STOP_N=1 day
REST_OPTION=none
PIO stride = 1

Error log:
```
5900: box_rearrange.F90.in 787 5003 0
5900: 8671959 0 6912260
5900: 80 6913642
5900: box_rearrange.F90.in 787 5004 0
5900: 8671959 0 6913642
5900: 80 6915024
5900: box_rearrange.F90.in 787 5005 0
5900: 8671959 0 6915024
5900: 80 6916406
5900: box_rearrange.F90.in 787 5006 0
5900: 8671959 0 6916406
5900: 80 6917788
5900: box_rearrange::compute_dest:: ERROR: no destination found for compdof=
5900: 693756721
5900: box_rearrange::compute_dest:: INFO: gsize= 80 11135652
5900: box_rearrange::compute_dest:: INFO: nioproc 8058 ioproc 2328
```
[Comments]
1) PIO2 has no issue for the same settings using box rearranger.
2) A different PE layout 3072x1 has no issue.
3) A different PIO stride 64 has no issue.

It seems that PIO1 might fail to create box rearranger for specific input data.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.