Skip to content
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

Program received signal SIGILL: Illegal instruction. #1222

Open
raulleoncz opened this issue May 9, 2024 · 6 comments
Open

Program received signal SIGILL: Illegal instruction. #1222

raulleoncz opened this issue May 9, 2024 · 6 comments

Comments

@raulleoncz
Copy link

Hello,

First of all, I am sorry for the inconvenience. I have been trying to do a simulation in an acoustic-elastic medium but after some time steps I got the following error:

Program received signal SIGILL: Illegal instruction.
Backtrace for this error:
Could not print backtrace: executable file is not an executable
Could not print backtrace: executable file is not an executable
#0 0x100b32f33
#1 0x100b321db
#2 0x19990b583
zsh: illegal hardware instruction ./bin/xspecfem2D

The first time I though the simulation got unstable but after checking in the solver.log I noticed that the CFL condition was right, the number of grid points per wavelength was fine and I was using an adequate source frequency. After checking the log file I found that after 4000 time steps the 'Max absolute value of scalar field in fluid (acoustic)' and the 'Color image maximum amplitude' quickly skyrocketed to very large values:


Time step number 5 t = 0.0032 s out of 10000


We have done 4.00040001E-02 % of the total
Max norm of vector field in solid (elastic) = 0.00000000
Max absolute value of scalar field in fluid (acoustic) = 1.53421927E-02
Color image maximum amplitude = 4.0870062075555325E-003


Time step number 2000 t = 1.5992 s out of 10000


We have done 19.9919987 % of the total
Max norm of vector field in solid (elastic) = 1.48898596E-03
Max absolute value of scalar field in fluid (acoustic) = 236.648941
Color image maximum amplitude = 1.4626149786636233E-003


Time step number 4000 t = 3.1992 s out of 10000


We have done 39.9939995 % of the total
Max norm of vector field in solid (elastic) = 1718.72803
Max absolute value of scalar field in fluid (acoustic) = 19952228.0
Color image maximum amplitude = 2.1745527217967010E+022

At the end the error message says:
code became unstable and blew up (image_color_data)
Error detected, aborting MPI... proc 0

Here are some screenshots:
image
image

Has anyone had a similar problem?

Just in case I will add the log files. Thank you for your help!

solver.log

@homnath
Copy link

homnath commented May 9, 2024 via email

@raulleoncz
Copy link
Author

Thank you @homnath for your help, I really appreciate it.
I tried decreasing the time step and also modifying the mesh and the error is still there. Looking to the pictures, what I believe is that my simulation is having troubles dealing with the fluid-solid interface, this because the error always occurs at this point.

@homnath
Copy link

homnath commented May 15, 2024 via email

@raulleoncz
Copy link
Author

Actually, I am not working exactly with those properties.
I am doing some inversion examples using specfem2d as the solver. For this, I used a .xyz file to generate the necessary .bin files and after that, those bin files are the ones I am using for the simulation.
My starting configuration was this:

MODEL = default
SAVE_MODEL = binary
nbmodels = 2
1 -1 0 0 0.5 0 0 0 0 0 0 0 0 0 0
2 1 1000.0 1400.0 0 0 0 9999 9999 0 0 0 0 0 0
TOMOGRAPHY_FILE = ./DATA/Initial_data.xyz

Then, using the bin files I had to configure it this way:

MODEL = gll
nbmodels = 2
1 1 1000.0 1500.0 1000.0 0 0 9999 9999 0 0 0 0 0 0
2 1 1000.0 1400.0 0 0 0 9999 9999 0 0 0 0 0 0
TOMOGRAPHY_FILE = ./DATA/Initial_data.xyz

After a few iterations I got the above error at the same point. What I noticed is that when I changed
1 1 1000.0 1500.0 1000.0 0 0 9999 9999 0 0 0 0 0 0 to 1 1 1000.0 1500.0 0 0 0 9999 9999 0 0 0 0 0 0, specfem has no problem to do the simulation, maybe because the entire model is now acoustic. This made me think the problem is how we deal with the interfaz fluid-solid.

Thank you for your help.

@homnath
Copy link

homnath commented May 16, 2024 via email

@raulleoncz
Copy link
Author

Hello @homnath, sorry for my late response.

I have tried using different values, for example:
1 1 2600.0 3500.0 1700.0 0 0 9999 9999 0 0 0 0 0 0
2 1 1000.0 1400.0 0 0 0 9999 9999 0 0 0 0 0 0

But I got the same error. Now, I'm trying to modify the mesh, specially at the fluid-solid interface. Maybe using a more refined mesh could work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants