[CIG-SEISMO] Fwd: Anisotropy Model in SPECFEM3D_GLOBE

[Dimitri Komatitsch]

Dear all,

Would anybody know the answer to Quancheng Huang's question below?

Thank you very much,
Best regards,
Dimitri.

-------- Forwarded Message --------
Subject: 	Anisotropy Model in SPECFEM3D_GLOBE
Date: 	Mon, 16 Oct 2017 15:41:54 -0400
From: 	Quancheng Huang <qchuang at terpmail.umd.edu>
To: 	komatitsch at lma.cnrs-mrs.fr

Dear Prof. Komatitsch,

I’m a PhD student from University of Maryland. Recently, I’m using 
SPECFEM3D_GLOBE to do synthetic modeling about anisotropic structures in 
upper mantle. When I switch the model to *3D_anisotropic* in Par_file, I 
will always run into a bug like this for creating meshes:

/[compute-a20-7:69690] *** Process received signal ***/
/[compute-a20-7:69690] Signal: Floating point exception (8)/
/[compute-a20-7:69690] Signal code: Floating point divide-by-zero (3)/
/[compute-a20-7:69690] Failing at address: 0x4507c3/
/
/
/[compute-b18-12:42501] [ 0] /lib64/libpthread.so.0(+0xf7e0) 
[0x7f0c777d47e0]/
/[compute-b18-12:42501] [ 1] 
/lustre/qchuang/specfem3d_globe/bin/xmeshfem3D(get_vpvs_minmax_+0x1763) 
[0x4507c3]/
/[compute-b18-12:42501] [ 2] 
/lustre/qchuang/specfem3d_globe/bin/xmeshfem3D(check_mesh_resolution_+0x6c3) 
[0x451183]/
/[compute-b18-12:42501] [ 3] 
/lustre/qchuang/specfem3d_globe/bin/xmeshfem3D(create_regions_mesh_+0xbb8) 
[0x48a678]/
/[compute-b18-12:42501] [ 4] 
/lustre/qchuang/specfem3d_globe/bin/xmeshfem3D(create_meshes_+0x6b4) 
[0x46f304]/
/[compute-b18-12:42501] [ 5] 
/lustre/qchuang/specfem3d_globe/bin/xmeshfem3D(main+0x3e) [0x417fee]/
/[compute-b18-12:42501] [ 6] /lib64/libc.so.6(__libc_start_main+0xfd) 
[0x7f0c7744fd1d]/
/[compute-b18-12:42501] [ 7] 
/lustre/qchuang/specfem3d_globe/bin/xmeshfem3D() [0x41802d]/
/[compute-b18-12:42501] *** End of error message ***/
/
/
It is supposed to read in the Montagner (2002) model, which is a 
build-in model in the codes, when the model flag is switched to 
*3D_anisotropic. *I think the bug came from the 
*get_vpvs_minmax***subroutine but I can’t figure it out. I can run all 
the other tomography models except this 3D anisotropy model. Do you have 
any idea what the bug is?

Best Regards,

Quancheng Huang

Quancheng Huang
PhD Student
Department of Geology
University of Maryland
College Park, MD 20742

Email: qchuang at umd.edu <mailto:qchuang at umd.edu>
Tel: 202-848-8110