CESM1_2_2_1 build error: ERROR 1, on CHEYENNE

[jknight]

Hi all,
I'm running into an error, that I haven't been able to solve when trying to build a new case with CESM1_2_2_1 on CHEYENNE.

The case I've built: ./create_newcase -case ~/cases/case02 -res f19_g16 -compset B_1850 -mach cheyenne

Attached are the errors I received, unfortunately I haven't been able to find any solutions.

Thank you in advance for your help,

Jacob

 

[jedwards]

Try updating PIO:

Release pio1_8_14 · NCAR/ParallelIO

update source but not build

github.com

 

[jknight]

Try updating PIO:

Release pio1_8_14 · NCAR/ParallelIO

update source but not build

github.com

Thank you for your fast reply, I have loaded the default pio module and the error still occurs. Attached are the modules I have loaded:

 

[jedwards]

no - you need to put that update into your source code tree - cesm1 doesn't use the pio module.

 

[jknight]

no - you need to put that update into your source code tree - cesm1 doesn't use the pio module.

ah yes, sorry I have also tried it with the update in my source code tree to no avail

 

[jedwards]

The error you are getting is with regard to memory size and it means that one or more static
variable(s) are requesting more memory than available in the model. One reason we have seen this is
that netcdf made a change some time ago that made some of their variable length arguments MAX_INT
as a way to discourage using them - this is what the pio update fixes. Another happens in pop if you have too few
ocn tasks specified. When you rebuild are you starting from scratch or are you trying to reuse parts of the previous build?
(Start from scratch).

 

[jknight]

The error you are getting is with regard to memory size and it means that one or more static
variable(s) are requesting more memory than available in the model. One reason we have seen this is
that netcdf made a change some time ago that made some of their variable length arguments MAX_INT
as a way to discourage using them - this is what the pio update fixes. Another happens in pop if you have too few
ocn tasks specified. When you rebuild are you starting from scratch or are you trying to reuse parts of the previous build?
(Start from scratch).

Right, thank you for explaining. I have been rebuilding from scratch each time.