Question about execution of CESM 1_2_1

[Jlu-zhe2wen]

We've successfully completed the execution of CESM 1_2_1 recently, however, we find that the parallelism (ntasks) should be set before ./cesm.setup, and if we change the parallelism (we also delete the locking handle in building scripts) the main program would report error when ATM initalize.

oes anyone know why the ntasks should be locked before building?

I'm computer science major and very interesting in this problem. Thanks

 

[erik]

Some of the CESM components require that the number of tasks be set at build time, as they hardwire the number of tasks into how they are built. Not, all of the CESM components do this however. Many of the components are configured so that the number of tasks is set at run time. But, to make the system consistent regardless of the configuration and because it doesn't hurt anything to require it be set at build-time we set it up that way.

 

[Jlu-zhe2wen]

Some of the CESM components require that the number of tasks be set at build time, as they hardwire the number of tasks into how they are built. Not, all of the CESM components do this however. Many of the components are configured so that the number of tasks is set at run time. But, to make the system consistent regardless of the configuration and because it doesn't hurt anything to require it be set at build-time we set it up that way.

Thank you for your answer. Further I want know which components can change their ntasks at run time?