emonier@mit_edu
New Member
Hi,
I am a new CAM user. I have compiled CAM3.1 with pgf90 (pgi/9.0-4), netcdf/3.6.2 and openmpi/1.3.3a to use on Linux x86_64 cluster, with spmd enabled. I have successfully ran T21,T31,T42,fv2x2.5,fv4x5 on 1 node with 8 cores. However, when running fv10x15, it fails and returns the following error message:
ENDRUN:SPMDINIT_DYN: less than 3 latitudes per subdomain
Similarly, when running fv4x5 on 2 nodes with 16 cores, I get the same error message.
My understanding is that the setup sends latitudinal bands to each core that have less than 3 latitude grid points, which fails when it comes to calculating finite volumes. I have seen in literature that people have run fv1.9x2.5 with up several 100 cores. What do I need to modify to do this? Is it possible to change the tiling so it tiles not only in latitude but in longitude as well?
Any help is welcome. Thanks
I am a new CAM user. I have compiled CAM3.1 with pgf90 (pgi/9.0-4), netcdf/3.6.2 and openmpi/1.3.3a to use on Linux x86_64 cluster, with spmd enabled. I have successfully ran T21,T31,T42,fv2x2.5,fv4x5 on 1 node with 8 cores. However, when running fv10x15, it fails and returns the following error message:
ENDRUN:SPMDINIT_DYN: less than 3 latitudes per subdomain
Similarly, when running fv4x5 on 2 nodes with 16 cores, I get the same error message.
My understanding is that the setup sends latitudinal bands to each core that have less than 3 latitude grid points, which fails when it comes to calculating finite volumes. I have seen in literature that people have run fv1.9x2.5 with up several 100 cores. What do I need to modify to do this? Is it possible to change the tiling so it tiles not only in latitude but in longitude as well?
Any help is welcome. Thanks