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

Difficulty using tomographic model #1003

Open
ar4 opened this issue Sep 12, 2018 · 8 comments
Open

Difficulty using tomographic model #1003

ar4 opened this issue Sep 12, 2018 · 8 comments

Comments

@ar4
Copy link

ar4 commented Sep 12, 2018

I have a regular grid subsurface model that I wish to use with SPECFEM2D, and want to use the built-in mesher. If I understand correctly, it seems that converting my model into the "tomo.xyz" format and then specifying the "tomo" material type in the Par file is probably the easiest way to do this. It took me quite a bit of trial and error to get SPECFEM2D to accept the Par file. I am documenting it here in case someone else has this problem. The difficulty I had may suggest that additional documentation of this topic would be helpful.

If I set the materials line to be:

1 -1 0 0 A 0 0 0 0 0 0 0 0 0 0

I get the error:

error reading material parameters line

which I believe occurs because shared/read_value_parameters.f90 expects a double instead of "A".

If instead of "A" I put 0 or a negative number, meshfem2D/read_material_table.f90 correctly reports:

Material # 1 will be read in an external tomography file (TOMOGRAPHY_FILE in Par_file)

But then meshfem2D/read_regions.f90 reports:

Material is fluid

which causes a problem, as I then get the error:

acoustic material in DATA/Par_file or external mesh redefined as non acoustic in define_external_model()

If instead of "A" in the vs slot, I put a large positive number (such as 1000.0), I get the error:

incorrect value of Poisson's ratio

even though vp in my tomo file is 1500 (so it seems to not be using that value to calculate Poisson's ratio). Finally, I discovered that setting the value to 0.5 seems to work.

@ar4 ar4 changed the title Unable to use tomographic model Difficulty using tomographic model Sep 12, 2018
@komatits
Copy link
Contributor

komatits commented Sep 12, 2018 via email

@pasansherath
Copy link

Hi @ar4 ,

Does the domain of the tomo.xyz file conform to that of the mesh?
Could you share your tomo.xyz and Par_file with me?

Thanks very much.
Pasan

@ar4
Copy link
Author

ar4 commented Apr 29, 2020 via email

@weisenhuang
Copy link

Hi @ar4 ,

Can you tell me how to convert model into the "tomo.xyz" format and then specifying the "tomo" material type in the Par file?

Thanks very much,
WeiSenHuang

@ar4
Copy link
Author

ar4 commented Sep 23, 2021 via email

@weisenhuang
Copy link

weisenhuang commented Sep 23, 2021 via email

@pasansherath
Copy link

Hi @weisenhuang,

I was able to use a tomographic model with SPECFEM2D about a year ago. Here is what I did.

The header of the 'tomo.xyz' file shoud have the following information.

x_min z_min x_max z_max
x_spacing z_spacing
nx nz
vp_min vp_max vs_min vs_max rho_min rho_max

Then we have to give the x z vp vs and rho values for each grid point in the tomographic model.

An extract from a 'tomo.xyz' file that I used is given below.

         0         0     120000      30000
     500     500
     241       61
   4000   8500       2222       4722       2800       3300
        0      0  8500  4722  3300
    500      0  8500  4722  3300
  1000      0  8500  4722  3300
  1500      0  8500  4722  3300
  2000      0  8500  4722  3300
  2500      0  8500  4722  3300
  3000      0  8500  4722  3300
  3500      0  8500  4722  3300
  4000      0  8500  4722  3300
  4500      0  8500  4722  3300
  5000      0  8500  4722  3300

In the Par_file you have to define the following.

Under # velocity and density models, define your model as follows
1 -1 0 0 0.5 0 0 0 0 0 0 0 0 0 0

Then you have to set the tomo.xyz file path. Make sure you give the right path (I guess it should be relative to the DATA folder).
TOMOGRAPHY_FILE = tomo.xyz

It should be good to go now.

Hope this helps you.

Cheers,
Pasan

@weisenhuang
Copy link

Hi @pasansherath ,

Your answer is very helpful to me.

Thanks very much.

WeiSenHuang

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

4 participants