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

Error building CESM 1.2.1 on Pleiades-san

S

santos

Member
And *that* didn't work, of course, because the gcc build of netCDF has module files that the Intel compiler can't read. I'm going to ask Francis Vitt about this.
 
S

santos

Member
And *that* didn't work, of course, because the gcc build of netCDF has module files that the Intel compiler can't read. I'm going to ask Francis Vitt about this.
 
S

santos

Member
And *that* didn't work, of course, because the gcc build of netCDF has module files that the Intel compiler can't read. I'm going to ask Francis Vitt about this.
 
S

santos

Member
Well, I think that Francis is the main person behind the pleiades port, but I don't have read access to all of his files, and he's in the CCWG meeting all day today. So let's see if he has anything once he gets back.The problem we usually have with pleiades is that its modules (and to a lesser extent, hardware) are updated relatively frequently, whereas the main projects we support on pleiades don't create builds for new runs as often. Hence the CESM releases tend to get out of date rather easily. I doubt that earlier CESM versions will do any better than CESM 1.2.1, since the problem is usually a machine change, not a CESM change. However, you can also try to figure this out yourself by talking to NAS support and/or doing your own trial and error.
 
S

santos

Member
Well, I think that Francis is the main person behind the pleiades port, but I don't have read access to all of his files, and he's in the CCWG meeting all day today. So let's see if he has anything once he gets back.The problem we usually have with pleiades is that its modules (and to a lesser extent, hardware) are updated relatively frequently, whereas the main projects we support on pleiades don't create builds for new runs as often. Hence the CESM releases tend to get out of date rather easily. I doubt that earlier CESM versions will do any better than CESM 1.2.1, since the problem is usually a machine change, not a CESM change. However, you can also try to figure this out yourself by talking to NAS support and/or doing your own trial and error.
 
S

santos

Member
Well, I think that Francis is the main person behind the pleiades port, but I don't have read access to all of his files, and he's in the CCWG meeting all day today. So let's see if he has anything once he gets back.The problem we usually have with pleiades is that its modules (and to a lesser extent, hardware) are updated relatively frequently, whereas the main projects we support on pleiades don't create builds for new runs as often. Hence the CESM releases tend to get out of date rather easily. I doubt that earlier CESM versions will do any better than CESM 1.2.1, since the problem is usually a machine change, not a CESM change. However, you can also try to figure this out yourself by talking to NAS support and/or doing your own trial and error.
 
You must log in or register to reply here.
Top