Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

Running CESM on NCAR's Yellowstone

J

jedwards

CSEG and Liaisons
Staff member
lsu said:
Can cseg make cesm1_0_3 supportive on yellowstone? I used to run cesm1_0_3 with tons of modifications on bluefire. Thanks! -lsu
Click to expand...

CESM1_0_5 is functionally equivalent to cesm1_0_3.
 
Y

yafangzhong@wisc_edu

Member
Hi,

I was trying to run CCSM3 T31 (/glade/p/cesm/releases/ccsm3_0_1_beta33) on Yellowstone today but got error messages as below. Anything to do with the PGI updating yesterday (i.e., 2/14/13)?

2:Abort(1) on node 2 (rank 2 in comm 1140850688): Fatal error in PMPI_Allgather: Invalid buffer pointer, error stack:
2:PMPI_Allgather(958): MPI_Allgather(sbuf=0x2dbb1b0, scount=1, MPI_INTEGER, rbuf=0x2dbb1b0, rcount=1, MPI_INTEGER, comm=0x84000001) failed
2:PMPI_Allgather(931): Buffers must not be aliased

Yafang
 
Y

yafangzhong@wisc_edu

Member
Hi,

I was trying to run CCSM3 T31 (/glade/p/cesm/releases/ccsm3_0_1_beta33) on Yellowstone today but got error messages as below. Anything to do with the PGI updating yesterday (i.e., 2/14/13)?

2:Abort(1) on node 2 (rank 2 in comm 1140850688): Fatal error in PMPI_Allgather: Invalid buffer pointer, error stack:
2:PMPI_Allgather(958): MPI_Allgather(sbuf=0x2dbb1b0, scount=1, MPI_INTEGER, rbuf=0x2dbb1b0, rcount=1, MPI_INTEGER, comm=0x84000001) failed
2:PMPI_Allgather(931): Buffers must not be aliased

Yafang
 
Y

yafangzhong@wisc_edu

Member
Hi,

I was trying to run CCSM3 T31 (/glade/p/cesm/releases/ccsm3_0_1_beta33) on Yellowstone today but got error messages as below. Anything to do with the PGI updating yesterday (i.e., 2/14/13)?

2:Abort(1) on node 2 (rank 2 in comm 1140850688): Fatal error in PMPI_Allgather: Invalid buffer pointer, error stack:
2:PMPI_Allgather(958): MPI_Allgather(sbuf=0x2dbb1b0, scount=1, MPI_INTEGER, rbuf=0x2dbb1b0, rcount=1, MPI_INTEGER, comm=0x84000001) failed
2:PMPI_Allgather(931): Buffers must not be aliased

Yafang
 
Y

yafangzhong@wisc_edu

Member
Hi,

I was trying to run CCSM3 T31 (/glade/p/cesm/releases/ccsm3_0_1_beta33) on Yellowstone today but got error messages as below. Anything to do with the PGI updating yesterday (i.e., 2/14/13)?

2:Abort(1) on node 2 (rank 2 in comm 1140850688): Fatal error in PMPI_Allgather: Invalid buffer pointer, error stack:
2:PMPI_Allgather(958): MPI_Allgather(sbuf=0x2dbb1b0, scount=1, MPI_INTEGER, rbuf=0x2dbb1b0, rcount=1, MPI_INTEGER, comm=0x84000001) failed
2:PMPI_Allgather(931): Buffers must not be aliased

Yafang
 
Y

yafangzhong@wisc_edu

Member
Hi,

I was trying to run CCSM3 T31 (/glade/p/cesm/releases/ccsm3_0_1_beta33) on Yellowstone today but got error messages as below. Anything to do with the PGI updating yesterday (i.e., 2/14/13)?

2:Abort(1) on node 2 (rank 2 in comm 1140850688): Fatal error in PMPI_Allgather: Invalid buffer pointer, error stack:
2:PMPI_Allgather(958): MPI_Allgather(sbuf=0x2dbb1b0, scount=1, MPI_INTEGER, rbuf=0x2dbb1b0, rcount=1, MPI_INTEGER, comm=0x84000001) failed
2:PMPI_Allgather(931): Buffers must not be aliased

Yafang
 
J

jedwards

CSEG and Liaisons
Staff member
Hi Yafang,

There is not enough information in your post for us to provide any help. If you could post the information required to reproduce the problem I will take a look.
It may be enough to just provide the location of your case directory.

Jim
 
J

jedwards

CSEG and Liaisons
Staff member
Hi Yafang,

There is not enough information in your post for us to provide any help. If you could post the information required to reproduce the problem I will take a look.
It may be enough to just provide the location of your case directory.

Jim
 
J

jedwards

CSEG and Liaisons
Staff member
Hi Yafang,

There is not enough information in your post for us to provide any help. If you could post the information required to reproduce the problem I will take a look.
It may be enough to just provide the location of your case directory.

Jim
 
J

jedwards

CSEG and Liaisons
Staff member
Hi Yafang,

There is not enough information in your post for us to provide any help. If you could post the information required to reproduce the problem I will take a look.
It may be enough to just provide the location of your case directory.

Jim
 
J

jedwards

CSEG and Liaisons
Staff member
Hi Yafang,

There is not enough information in your post for us to provide any help. If you could post the information required to reproduce the problem I will take a look.
It may be enough to just provide the location of your case directory.

Jim
 
J

jedwards

CSEG and Liaisons
Staff member
Try adding the file /glade/scratch/jedwards/cesmtests/ccsm3_test/SourceMods/src.clm/spmdMod.F90 to your test1/SourceMods/src.clm/ directory and rebuild.
 
J

jedwards

CSEG and Liaisons
Staff member
Try adding the file /glade/scratch/jedwards/cesmtests/ccsm3_test/SourceMods/src.clm/spmdMod.F90 to your test1/SourceMods/src.clm/ directory and rebuild.
 
J

jedwards

CSEG and Liaisons
Staff member
Try adding the file /glade/scratch/jedwards/cesmtests/ccsm3_test/SourceMods/src.clm/spmdMod.F90 to your test1/SourceMods/src.clm/ directory and rebuild.
 
J

jedwards

CSEG and Liaisons
Staff member
Try adding the file /glade/scratch/jedwards/cesmtests/ccsm3_test/SourceMods/src.clm/spmdMod.F90 to your test1/SourceMods/src.clm/ directory and rebuild.
 
You must log in or register to reply here.
Top