Aloha.
In an effort to debug my other issue, I've created a completely vanilla instance of WRF 4.1.3 and using WPS-4.0.2 on a Dell server with openmpi. I am using the 2-domains I've been working with for years and find that WRF fails after the first-time step with a seg fault. This is similar to the failure i have for auxhist5 on comet but obviously the symptoms will be different. This looks like a bug to me but could be something inadvertenly wrong in the configuration but I cannot find anything wrong. It would be a great help if someone here could offer a path to more debugging.
Mahalo.
============================================ partial rsl.error.* output from failure ==========================
WRF NUMBER OF TILES = 16
mediation_integrate.G 1944 DATASET=HISTORY
mediation_integrate.G 1945 grid%id 2 grid%oid 2
WRF NUMBER OF TILES FROM OMP_GET_MAX_THREADS = 16
Tile Strategy is not specified. Assuming 1D-Y
WRF TILE 1 IS 202 IE 302 JS 196 JE 202
WRF TILE 2 IS 202 IE 302 JS 203 JE 208
WRF TILE 3 IS 202 IE 302 JS 209 JE 214
WRF TILE 4 IS 202 IE 302 JS 215 JE 220
WRF TILE 5 IS 202 IE 302 JS 221 JE 226
WRF TILE 6 IS 202 IE 302 JS 227 JE 232
WRF TILE 7 IS 202 IE 302 JS 233 JE 238
WRF TILE 8 IS 202 IE 302 JS 239 JE 244
WRF TILE 9 IS 202 IE 302 JS 245 JE 250
WRF TILE 10 IS 202 IE 302 JS 251 JE 256
WRF TILE 11 IS 202 IE 302 JS 257 JE 262
WRF TILE 12 IS 202 IE 302 JS 263 JE 268
WRF TILE 13 IS 202 IE 302 JS 269 JE 274
WRF TILE 14 IS 202 IE 302 JS 275 JE 280
WRF TILE 15 IS 202 IE 302 JS 281 JE 286
WRF TILE 16 IS 202 IE 302 JS 287 JE 293
WRF NUMBER OF TILES = 16
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
Backtrace for this error:
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
In an effort to debug my other issue, I've created a completely vanilla instance of WRF 4.1.3 and using WPS-4.0.2 on a Dell server with openmpi. I am using the 2-domains I've been working with for years and find that WRF fails after the first-time step with a seg fault. This is similar to the failure i have for auxhist5 on comet but obviously the symptoms will be different. This looks like a bug to me but could be something inadvertenly wrong in the configuration but I cannot find anything wrong. It would be a great help if someone here could offer a path to more debugging.
Mahalo.
============================================ partial rsl.error.* output from failure ==========================
WRF NUMBER OF TILES = 16
mediation_integrate.G 1944 DATASET=HISTORY
mediation_integrate.G 1945 grid%id 2 grid%oid 2
WRF NUMBER OF TILES FROM OMP_GET_MAX_THREADS = 16
Tile Strategy is not specified. Assuming 1D-Y
WRF TILE 1 IS 202 IE 302 JS 196 JE 202
WRF TILE 2 IS 202 IE 302 JS 203 JE 208
WRF TILE 3 IS 202 IE 302 JS 209 JE 214
WRF TILE 4 IS 202 IE 302 JS 215 JE 220
WRF TILE 5 IS 202 IE 302 JS 221 JE 226
WRF TILE 6 IS 202 IE 302 JS 227 JE 232
WRF TILE 7 IS 202 IE 302 JS 233 JE 238
WRF TILE 8 IS 202 IE 302 JS 239 JE 244
WRF TILE 9 IS 202 IE 302 JS 245 JE 250
WRF TILE 10 IS 202 IE 302 JS 251 JE 256
WRF TILE 11 IS 202 IE 302 JS 257 JE 262
WRF TILE 12 IS 202 IE 302 JS 263 JE 268
WRF TILE 13 IS 202 IE 302 JS 269 JE 274
WRF TILE 14 IS 202 IE 302 JS 275 JE 280
WRF TILE 15 IS 202 IE 302 JS 281 JE 286
WRF TILE 16 IS 202 IE 302 JS 287 JE 293
WRF NUMBER OF TILES = 16
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
Backtrace for this error:
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error: