-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash in PAHM SCHISM intergation compiled with GNU on Docker #8
Comments
@pvelissariou1, when you have the time let's talk about this issue. I'm not sure if it's related to how I setup my dockerfile or it's the compiler version, etc. It used to work when your code was first added to SCHISM. I recently rebuilt the docker image I was using and I keep running into this issue. |
Note that if I try this with |
@josephzhang8 should I create a parallel issue on |
@pvelissariou1 as I mentioned in the email, I was unsuccessful running SCHISM-PAHM with either of the compilers in
I built this and then shelled into the container, loaded the same modules as above and ran |
The segfault I get is at: Thread 1 "pschism_PAHM_TV" received signal SIGSEGV, Segmentation fault.
0x00007f8e34e3e68a in __memcmp_avx2_movbe () from /lib64/libc.so.6
(gdb) where
#0 0x00007f8e34e3e68a in __memcmp_avx2_movbe () from /lib64/libc.so.6
#1 0x00007f8e369d5adf in _gfortran_compare_string ()
from /lib64/libgfortran.so.5
#2 0x0000000000551656 in __sortutils_MOD_stringlexcomp ()
#3 0x00000000005547c3 in __sortutils_MOD_indexxstring ()
#4 0x0000000000549819 in __parwind_MOD_readcsvbesttrackfile ()
#5 0x000000000044ea83 in schism_init_ ()
#6 0x0000000000404df5 in schism_main_ ()
#7 0x0000000000404ee4 in MAIN__ ()
#8 0x0000000000404c3d in main ()
(gdb) like before. The build log is attached: |
Subject: SCHISM segmentation faults with gfortran+openmpi
There are a couple of issues in the SCHISM code and a problem with some
OS libraries that openmpi is using, in core centOS, RedHat, Fedora, Ubuntu?.
openmpi, by default is using ucx (unified communication protocol) which is
broken
in the above core distributions.
In orion they have installed the very latest version of ucx that replaces
the default ucx library of the OS.
It seems that in the containers (both devel and run) ucx should be updated
to the latest stable version.
I'll investigate a bit further.
Regarding the SCHISM code, there are two issues:
a) storage for iwork3 is not allocated/deallocated properly
in src/Core/scribe_io.F90 (lines 191, 291)
and GFortran issues an error (see the attached files)
b) there are a few argument/rank mismatches (see the attached files) that
in newer versions
of GFortran are considered as errors (unless the flag
-fallow-argument-mismatch is passed to the compiler)
Panagiotis Velissariou, Ph.D., P.E.
UCAR Scientist
National Ocean and Atmospheric Administration
National Ocean Service
Office of Coast Survey CSDL/CMMB
Project Lead - Coastal Coupling
cell: (205) 227-9141
email: ***@***.***
…On Wed, Jul 6, 2022 at 2:49 PM Soroosh Mani ***@***.***> wrote:
The segfault I get is at:
Thread 1 "pschism_PAHM_TV" received signal SIGSEGV, Segmentation fault.0x00007f8e34e3e68a in __memcmp_avx2_movbe () from /lib64/libc.so.6
(gdb) where#0 0x00007f8e34e3e68a in __memcmp_avx2_movbe () from /lib64/libc.so.6#1 0x00007f8e369d5adf in _gfortran_compare_string ()
from /lib64/libgfortran.so.5#2 0x0000000000551656 in __sortutils_MOD_stringlexcomp ()#3 0x00000000005547c3 in __sortutils_MOD_indexxstring ()#4 0x0000000000549819 in __parwind_MOD_readcsvbesttrackfile ()#5 0x000000000044ea83 in schism_init_ ()#6 0x0000000000404df5 in schism_main_ ()#7 0x0000000000404ee4 in MAIN__ ()#8 0x0000000000404c3d in main ()
(gdb)
like before. The build log is attached:
schism_pahm_build.log
<https://github.com/noaa-ocs-modeling/PaHM/files/9057623/schism_pahm_build.log>
—
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APC7TP354X4YBX56UAHTXDTVSXPMDANCNFSM5YY3FKZQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi Takis:
RE: SCHISM code.
b) Argument mismatch can be allowed in gcc as you mentioned by adding the flags;
a) iwork3(): another developer also encountered the same error and after working with him on debugging, including adding a if(allocated()), the error was believed to be from an older MPI installation. Switching to newer versions worked. Iwork3(0 is a temp array only used in 1 routine, allocated and deallocated in the same routine.
-Joseph
Y. Joseph Zhang
Web: schism.wiki
Office: 804 684 7466
From: Panagiotis Velissariou ***@***.***>
Sent: Tuesday, July 12, 2022 1:12 AM
To: noaa-ocs-modeling/PaHM ***@***.***>
Cc: Y. Joseph Zhang ***@***.***>; Mention ***@***.***>
Subject: Re: [noaa-ocs-modeling/PaHM] Crash in PAHM SCHISM intergation compiled with GNU on Docker (Issue #8)
[EXTERNAL to VIMS received message]
Subject: SCHISM segmentation faults with gfortran+openmpi
There are a couple of issues in the SCHISM code and a problem with some
OS libraries that openmpi is using, in core centOS, RedHat, Fedora, Ubuntu?.
openmpi, by default is using ucx (unified communication protocol) which is
broken
in the above core distributions.
In orion they have installed the very latest version of ucx that replaces
the default ucx library of the OS.
It seems that in the containers (both devel and run) ucx should be updated
to the latest stable version.
I'll investigate a bit further.
Regarding the SCHISM code, there are two issues:
a) storage for iwork3 is not allocated/deallocated properly
in src/Core/scribe_io.F90 (lines 191, 291)
and GFortran issues an error (see the attached files)
b) there are a few argument/rank mismatches (see the attached files) that
in newer versions
of GFortran are considered as errors (unless the flag
-fallow-argument-mismatch is passed to the compiler)
Panagiotis Velissariou, Ph.D., P.E.
UCAR Scientist
National Ocean and Atmospheric Administration
National Ocean Service
Office of Coast Survey CSDL/CMMB
Project Lead - Coastal Coupling
cell: (205) 227-9141
email: ***@***.***<mailto:***@***.***>
On Wed, Jul 6, 2022 at 2:49 PM Soroosh Mani ***@***.***<mailto:***@***.***>> wrote:
The segfault I get is at:
Thread 1 "pschism_PAHM_TV" received signal SIGSEGV, Segmentation fault.0x00007f8e34e3e68a in __memcmp_avx2_movbe () from /lib64/libc.so.6
(gdb) where#0 0x00007f8e34e3e68a in __memcmp_avx2_movbe () from /lib64/libc.so.6#1 0x00007f8e369d5adf in _gfortran_compare_string ()
from /lib64/libgfortran.so.5#2 0x0000000000551656 in __sortutils_MOD_stringlexcomp ()#3 0x00000000005547c3 in __sortutils_MOD_indexxstring ()#4 0x0000000000549819 in __parwind_MOD_readcsvbesttrackfile ()#5 0x000000000044ea83 in schism_init_ ()#6 0x0000000000404df5 in schism_main_ ()#7 0x0000000000404ee4 in MAIN__ ()#8 0x0000000000404c3d in main ()
(gdb)
like before. The build log is attached:
schism_pahm_build.log
<https://github.com/noaa-ocs-modeling/PaHM/files/9057623/schism_pahm_build.log>
-
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APC7TP354X4YBX56UAHTXDTVSXPMDANCNFSM5YY3FKZQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***<mailto:***@***.***>>
-
Reply to this email directly, view it on GitHub<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnoaa-ocs-modeling%2FPaHM%2Fissues%2F8%23issuecomment-1181321755&data=05%7C01%7Cyjzhang%40vims.edu%7C27305322302d4e079d0d08da63c508ad%7C8cbcddd9588d4e3b9c1e2367dbdf1740%7C0%7C0%7C637931995153317357%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=W%2B5Qsv0asjN6K9jmlfeaQk%2FARrD7hdCpMFZ4JqlcowI%3D&reserved=0>, or unsubscribe<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFBKNZ2CB5W6TRABD5C2VATVTT5BRANCNFSM5YY3FKZQ&data=05%7C01%7Cyjzhang%40vims.edu%7C27305322302d4e079d0d08da63c508ad%7C8cbcddd9588d4e3b9c1e2367dbdf1740%7C0%7C0%7C637931995153317357%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=g9jeG6p7vFoWkOQs1%2FkAKq9k8LHC2%2BdeOTpJaijooNM%3D&reserved=0>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
Thanks Joseph,
I'll update openmpi to the latest version to see if the iwork3 issue is
resolved. But it is strange though.
On exit from the subroutine the storage of non-saved allocatable arrays
should be deallocated automatically.
The argument mismatch issue might need to be addressed in the future as I
think GFortran will remove the flag
and have this to be an error.
The rest of the segmentation faults come from the sys libraries.
I'll give it a try to fix these (basically in the containers) and I'll
report back so we keep track of these issues.
Takis
Panagiotis Velissariou, Ph.D., P.E.
UCAR Scientist
National Ocean and Atmospheric Administration
National Ocean Service
Office of Coast Survey CSDL/CMMB
Project Lead - Coastal Coupling
cell: (205) 227-9141
email: ***@***.***
On Tue, Jul 12, 2022 at 7:39 AM Joseph Zhang ***@***.***>
wrote:
… Hi Takis:
RE: SCHISM code.
b) Argument mismatch can be allowed in gcc as you mentioned by adding the
flags;
a) iwork3(): another developer also encountered the same error and after
working with him on debugging, including adding a if(allocated()), the
error was believed to be from an older MPI installation. Switching to newer
versions worked. Iwork3(0 is a temp array only used in 1 routine, allocated
and deallocated in the same routine.
-Joseph
Y. Joseph Zhang
Web: schism.wiki
Office: 804 684 7466
From: Panagiotis Velissariou ***@***.***>
Sent: Tuesday, July 12, 2022 1:12 AM
To: noaa-ocs-modeling/PaHM ***@***.***>
Cc: Y. Joseph Zhang ***@***.***>; Mention ***@***.***>
Subject: Re: [noaa-ocs-modeling/PaHM] Crash in PAHM SCHISM intergation
compiled with GNU on Docker (Issue #8)
[EXTERNAL to VIMS received message]
Subject: SCHISM segmentation faults with gfortran+openmpi
There are a couple of issues in the SCHISM code and a problem with some
OS libraries that openmpi is using, in core centOS, RedHat, Fedora,
Ubuntu?.
openmpi, by default is using ucx (unified communication protocol) which is
broken
in the above core distributions.
In orion they have installed the very latest version of ucx that replaces
the default ucx library of the OS.
It seems that in the containers (both devel and run) ucx should be updated
to the latest stable version.
I'll investigate a bit further.
Regarding the SCHISM code, there are two issues:
a) storage for iwork3 is not allocated/deallocated properly
in src/Core/scribe_io.F90 (lines 191, 291)
and GFortran issues an error (see the attached files)
b) there are a few argument/rank mismatches (see the attached files) that
in newer versions
of GFortran are considered as errors (unless the flag
-fallow-argument-mismatch is passed to the compiler)
Panagiotis Velissariou, Ph.D., P.E.
UCAR Scientist
National Ocean and Atmospheric Administration
National Ocean Service
Office of Coast Survey CSDL/CMMB
Project Lead - Coastal Coupling
cell: (205) 227-9141
email: ***@***.***<mailto:***@***.***>
On Wed, Jul 6, 2022 at 2:49 PM Soroosh Mani ***@***.***<mailto:
***@***.***>>
wrote:
> The segfault I get is at:
>
> Thread 1 "pschism_PAHM_TV" received signal SIGSEGV, Segmentation
fault.0x00007f8e34e3e68a in __memcmp_avx2_movbe () from /lib64/libc.so.6
> (gdb) where#0 0x00007f8e34e3e68a in __memcmp_avx2_movbe () from
/lib64/libc.so.6#1 0x00007f8e369d5adf in _gfortran_compare_string ()
> from /lib64/libgfortran.so.5#2 0x0000000000551656 in
__sortutils_MOD_stringlexcomp ()#3 0x00000000005547c3 in
__sortutils_MOD_indexxstring ()#4 0x0000000000549819 in
__parwind_MOD_readcsvbesttrackfile ()#5 0x000000000044ea83 in schism_init_
()#6 0x0000000000404df5 in schism_main_ ()#7 0x0000000000404ee4 in MAIN__
()#8 0x0000000000404c3d in main ()
> (gdb)
>
> like before. The build log is attached:
> schism_pahm_build.log
> <
https://github.com/noaa-ocs-modeling/PaHM/files/9057623/schism_pahm_build.log
>
>
> -
> Reply to this email directly, view it on GitHub
> <
#8 (comment)
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/APC7TP354X4YBX56UAHTXDTVSXPMDANCNFSM5YY3FKZQ
>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***<mailto:***@***.***>>
>
-
Reply to this email directly, view it on GitHub<
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnoaa-ocs-modeling%2FPaHM%2Fissues%2F8%23issuecomment-1181321755&data=05%7C01%7Cyjzhang%40vims.edu%7C27305322302d4e079d0d08da63c508ad%7C8cbcddd9588d4e3b9c1e2367dbdf1740%7C0%7C0%7C637931995153317357%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=W%2B5Qsv0asjN6K9jmlfeaQk%2FARrD7hdCpMFZ4JqlcowI%3D&reserved=0>,
or unsubscribe<
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFBKNZ2CB5W6TRABD5C2VATVTT5BRANCNFSM5YY3FKZQ&data=05%7C01%7Cyjzhang%40vims.edu%7C27305322302d4e079d0d08da63c508ad%7C8cbcddd9588d4e3b9c1e2367dbdf1740%7C0%7C0%7C637931995153317357%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=g9jeG6p7vFoWkOQs1%2FkAKq9k8LHC2%2BdeOTpJaijooNM%3D&reserved=0
>.
You are receiving this because you were mentioned.Message ID:
***@***.******@***.***>>
—
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APC7TP73BFZKOLZHSQCYE4DVTVRNLANCNFSM5YY3FKZQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thx Takis.
In scribe_io.F90, iwork3() was deallocated by the code (I always do that for all temp arrays). As you said, it's a very weird problem that I have no clue on.
-Joseph
Y. Joseph Zhang
Web: schism.wiki
Office: 804 684 7466
From: Panagiotis Velissariou ***@***.***>
Sent: Tuesday, July 12, 2022 9:32 AM
To: noaa-ocs-modeling/PaHM ***@***.***>
Cc: Y. Joseph Zhang ***@***.***>; Mention ***@***.***>
Subject: Re: [noaa-ocs-modeling/PaHM] Crash in PAHM SCHISM intergation compiled with GNU on Docker (Issue #8)
[EXTERNAL to VIMS received message]
Thanks Joseph,
I'll update openmpi to the latest version to see if the iwork3 issue is
resolved. But it is strange though.
On exit from the subroutine the storage of non-saved allocatable arrays
should be deallocated automatically.
The argument mismatch issue might need to be addressed in the future as I
think GFortran will remove the flag
and have this to be an error.
The rest of the segmentation faults come from the sys libraries.
I'll give it a try to fix these (basically in the containers) and I'll
report back so we keep track of these issues.
Takis
Panagiotis Velissariou, Ph.D., P.E.
UCAR Scientist
National Ocean and Atmospheric Administration
National Ocean Service
Office of Coast Survey CSDL/CMMB
Project Lead - Coastal Coupling
cell: (205) 227-9141
email: ***@***.***<mailto:***@***.***>
On Tue, Jul 12, 2022 at 7:39 AM Joseph Zhang ***@***.***<mailto:***@***.***>>
wrote:
Hi Takis:
RE: SCHISM code.
b) Argument mismatch can be allowed in gcc as you mentioned by adding the
flags;
a) iwork3(): another developer also encountered the same error and after
working with him on debugging, including adding a if(allocated()), the
error was believed to be from an older MPI installation. Switching to newer
versions worked. Iwork3(0 is a temp array only used in 1 routine, allocated
and deallocated in the same routine.
-Joseph
Y. Joseph Zhang
Web: schism.wiki
Office: 804 684 7466
From: Panagiotis Velissariou ***@***.***<mailto:***@***.***>>
Sent: Tuesday, July 12, 2022 1:12 AM
To: noaa-ocs-modeling/PaHM ***@***.***<mailto:***@***.***>>
Cc: Y. Joseph Zhang ***@***.***<mailto:***@***.***>>; Mention ***@***.***<mailto:***@***.***>>
Subject: Re: [noaa-ocs-modeling/PaHM] Crash in PAHM SCHISM intergation
compiled with GNU on Docker (Issue #8)
[EXTERNAL to VIMS received message]
Subject: SCHISM segmentation faults with gfortran+openmpi
There are a couple of issues in the SCHISM code and a problem with some
OS libraries that openmpi is using, in core centOS, RedHat, Fedora,
Ubuntu?.
openmpi, by default is using ucx (unified communication protocol) which is
broken
in the above core distributions.
In orion they have installed the very latest version of ucx that replaces
the default ucx library of the OS.
It seems that in the containers (both devel and run) ucx should be updated
to the latest stable version.
I'll investigate a bit further.
Regarding the SCHISM code, there are two issues:
a) storage for iwork3 is not allocated/deallocated properly
in src/Core/scribe_io.F90 (lines 191, 291)
and GFortran issues an error (see the attached files)
b) there are a few argument/rank mismatches (see the attached files) that
in newer versions
of GFortran are considered as errors (unless the flag
-fallow-argument-mismatch is passed to the compiler)
Panagiotis Velissariou, Ph.D., P.E.
UCAR Scientist
National Ocean and Atmospheric Administration
National Ocean Service
Office of Coast Survey CSDL/CMMB
Project Lead - Coastal Coupling
cell: (205) 227-9141
email: ***@***.***<mailto:***@***.***<mailto:***@***.***%3cmailto:***@***.***>>
On Wed, Jul 6, 2022 at 2:49 PM Soroosh Mani ***@***.***<mailto<mailto:***@***.***%3cmailto>:
***@***.***<mailto:***@***.***>>>
wrote:
> The segfault I get is at:
>
> Thread 1 "pschism_PAHM_TV" received signal SIGSEGV, Segmentation
fault.0x00007f8e34e3e68a in __memcmp_avx2_movbe () from /lib64/libc.so.6
> (gdb) where#0 0x00007f8e34e3e68a in __memcmp_avx2_movbe () from
/lib64/libc.so.6#1 0x00007f8e369d5adf in _gfortran_compare_string ()
> from /lib64/libgfortran.so.5#2 0x0000000000551656 in
__sortutils_MOD_stringlexcomp ()#3 0x00000000005547c3 in
__sortutils_MOD_indexxstring ()#4 0x0000000000549819 in
__parwind_MOD_readcsvbesttrackfile ()#5 0x000000000044ea83 in schism_init_
()#6 0x0000000000404df5 in schism_main_ ()#7 0x0000000000404ee4 in MAIN__
()#8 0x0000000000404c3d in main ()
> (gdb)
>
> like before. The build log is attached:
> schism_pahm_build.log
> <
https://github.com/noaa-ocs-modeling/PaHM/files/9057623/schism_pahm_build.log
>
>
> -
> Reply to this email directly, view it on GitHub
> <
#8 (comment)
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/APC7TP354X4YBX56UAHTXDTVSXPMDANCNFSM5YY3FKZQ
>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***<mailto:***@***.***<mailto:***@***.***%3cmailto:***@***.***>>>
>
-
Reply to this email directly, view it on GitHub<
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnoaa-ocs-modeling%2FPaHM%2Fissues%2F8%23issuecomment-1181321755&data=05%7C01%7Cyjzhang%40vims.edu%7C27305322302d4e079d0d08da63c508ad%7C8cbcddd9588d4e3b9c1e2367dbdf1740%7C0%7C0%7C637931995153317357%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=W%2B5Qsv0asjN6K9jmlfeaQk%2FARrD7hdCpMFZ4JqlcowI%3D&reserved=0>,
or unsubscribe<
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFBKNZ2CB5W6TRABD5C2VATVTT5BRANCNFSM5YY3FKZQ&data=05%7C01%7Cyjzhang%40vims.edu%7C27305322302d4e079d0d08da63c508ad%7C8cbcddd9588d4e3b9c1e2367dbdf1740%7C0%7C0%7C637931995153317357%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=g9jeG6p7vFoWkOQs1%2FkAKq9k8LHC2%2BdeOTpJaijooNM%3D&reserved=0
>.
You are receiving this because you were mentioned.Message ID:
***@***.******@***.***<mailto:***@***.******@***.***>>>
-
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APC7TP73BFZKOLZHSQCYE4DVTVRNLANCNFSM5YY3FKZQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***<mailto:***@***.***>>
-
Reply to this email directly, view it on GitHub<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnoaa-ocs-modeling%2FPaHM%2Fissues%2F8%23issuecomment-1181764954&data=05%7C01%7Cyjzhang%40vims.edu%7Cb4947898bb1248fd75d108da640ae278%7C8cbcddd9588d4e3b9c1e2367dbdf1740%7C0%7C0%7C637932295171401293%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xzxl3hv1y0n6FbWu9JnzXhPmjY7liT11DGDl14p31xo%3D&reserved=0>, or unsubscribe<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFBKNZZ65TGTJZVN4ZYU5RDVTVXURANCNFSM5YY3FKZQ&data=05%7C01%7Cyjzhang%40vims.edu%7Cb4947898bb1248fd75d108da640ae278%7C8cbcddd9588d4e3b9c1e2367dbdf1740%7C0%7C0%7C637932295171401293%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=OwvjJO1CXDrobLEftGokcsjo1Bmfljly4GvPMhC%2FQC8%3D&reserved=0>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
These cannot be avoided by our codes as the argument mismatch is raised by the MPI_ calls, which take variable type arguments. So unless this is fixed upstream (in MPI code), we have to use the |
The latest update on SCHISM+GFortran + (openmpi/mpich) is as follows:
1) with gfortran and openmpi versions 4.0.4, 4.1.0, 4.1.4 (latest) the
iwork3 array allocation issue persists
I used gfortran + openmpi (version 4.0.4) and schism crashed
(iwork3 issue and seg. faults)
2) with gfortran + mpich (on orion) the run seems to go through but
produces corrupted data outputs
and eventually the model crashes.
3) modifying the scribe_io.F90 for iwork3 as:
if (.not. allocated(iwork3)) allocate(iwork3(2,ns_max))
The run goes through but the model crashes (segmentation fault)
Attached are the log files from the compilation and run of schism that
might help understanding the issues.
Takis
Panagiotis Velissariou, Ph.D., P.E.
UCAR Scientist
National Ocean and Atmospheric Administration
National Ocean Service
Office of Coast Survey CSDL/CMMB
Project Lead - Coastal Coupling
cell: (205) 227-9141
email: ***@***.***
…On Tue, Jul 12, 2022 at 2:29 PM Carsten Lemmen ***@***.***> wrote:
there are a few argument/rank mismatches (see the attached files) that in
newer version of GFortran are considered as errors (unless the flag
-fallow-argument-mismatch is passed to the compiler)
These cannot be avoided by our codes as the argument mismatch is raised by
the MPI_ calls, which take variable type arguments. So unless this is fixed
upstream (in MPI code), we have to use the -fallow-argument-mismatch flag
in GCC>=10
—
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APC7TPZD5QGSHCGXHVNSXHLVTXBQTANCNFSM5YY3FKZQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Issue closed, fixed bugs for SCHISM/PAHM. Compiles fine now. |
When I try to run SCHISM with parametric wind forcing, I get the following error during initialization:
I run into this issue when compiling SCHISM using GNU. Here is the
Dockerfile
I use:and I run it using
from inside the container
Note that to start the container and have the SCHISM inputs, you need to set
SYS_PTRACE
cap and also bind directory of the input:The text was updated successfully, but these errors were encountered: