Issue with using EXT for extracting data from TOUGH2 MESH and OUTPUT files
I have compiled and linked the EXT fortran source codes downloaded at: https://tough.lbl.gov/licensing-download/free-software-download/. I received the following error messages when using the created executable to extract data from TOUGH2 MESH and OUTPUT files. Could you please help me with this issue?
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
#0 0x7F3C4912E697
#1 0x7F3C4912ECDE
#2 0x7F3C4862A27F
#3 0x7F3C48749E76
#4 0x7F3C491F5E66
#5 0x7F3C491FA3FB
#6 0x405C51 in rmesh_
#7 0x401862 in MAIN__ at ext.f:?
Segmentation fault
3 replies
-
I can't tell from the error message what is wrong. Could you post your MESH and OUTPUT files? If they are too big, try creating a sample problem with a smaller MESH and output at just one time in the OUTPUT file, and post those.
-
I have posted the OUTPUT file. The MESH file is too big (910.3MB). The number of elements in the model is about 2538000, which is much higher than the allowed value specified in the ext.f file. I increased the "mnel" parameter in the ext.f file to 2600000, then got the following error messages when creating an executable.
(base) bash-4.2$ gfortran -o executable ext.f catalog.f inspect.f rmesh.f
/tmp/ccekVnwy.o: In function `MAIN__':
ext.f:(.text+0x989): relocation truncated to fit: R_X86_64_32S against symbol `ind_' defined in COMMON section in /tmp/ccekVnwy.o
ext.f:(.text+0x9f6): relocation truncated to fit: R_X86_64_32S against symbol `zo_' defined in COMMON section in /tmp/ccekVnwy.o
ext.f:(.text+0x2636): relocation truncated to fit: R_X86_64_32S against symbol `ec_' defined in COMMON section in /tmp/ccekVnwy.o
ext.f:(.text+0x2656): relocation truncated to fit: R_X86_64_32S against symbol `e_' defined in COMMON section in /tmp/ccekVnwy.o
ext.f:(.text+0x266e): relocation truncated to fit: R_X86_64_32S against symbol `e_' defined in COMMON section in /tmp/ccekVnwy.o
ext.f:(.text+0x2689): relocation truncated to fit: R_X86_64_32S against symbol `e_' defined in COMMON section in /tmp/ccekVnwy.o
ext.f:(.text+0x269d): relocation truncated to fit: R_X86_64_32S against symbol `e_' defined in COMMON section in /tmp/ccekVnwy.o
ext.f:(.text+0x2ec2): relocation truncated to fit: R_X86_64_32S against symbol `zo_' defined in COMMON section in /tmp/ccekVnwy.o
ext.f:(.text+0x31e8): relocation truncated to fit: R_X86_64_32S against symbol `zo_' defined in COMMON section in /tmp/ccekVnwy.o
ext.f:(.text+0x3552): relocation truncated to fit: R_X86_64_32S against symbol `zo_' defined in COMMON section in /tmp/ccekVnwy.o
collect2: error: ld returned 1 exit status -
Hmm, I am not sure Ext will work for such a big mesh. If anyone else has experience with this, please chime in.
The compilation error messages look to me like your computer memory is not big enough for such a large value of mnel - the symbols ind, zo, ec, etc. are defined in ext.f following allocation of an array with dimension mnel. Could you try running on a computer with bigger memory?
Also, I think you will need to increase mncon, mcat, and nhsh (number of connections, number of catalog entries, size of hash table) when you want to run a larger problem. I found an ext.f that I modified for bigger problems with:
mnel=1000000 (max number of elements in your MESH file)
mncon=3000000 (max number of connections in your MESH file)
mcat=3000000
nhsh=40000
These values will not be big enough for you, but they might give you an idea of how to scale up the values in the original ext.f.