-
Notifications
You must be signed in to change notification settings - Fork 147
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
Gmesh and specfem2D #324
Comments
can you send the Parfile and SOURCE file in order to check. |
Here the Parfile and source file: Thanks,
|
I am not sure it worked. Thanks, here "SOURCE.solid_fluid":#source 1. The components of a moment tensor source must be given in N.m, not in dyne.cm as in the DATA/CMTSOLUTION source file of the 3D version of the code. here "Par_file_Gmsh_solid_fluid.in":title of jobtitle = Shallow water 30 Hz Source middle 4 receiver sets forward or adjoint simulationSIMULATION_TYPE = 1 # 1 = forward, 2 = adjoint + kernels parameters concerning partitioningnproc = 4 # number of processes ngnod = 9 # number of control nodes per element (4 or 9) time step parametersnt = 2400 # total number of time steps source parametersNSOURCES = 1 # number of sources [source info read in CMTSOLUTION file] constants for attenuationN_SLS = 2 # number of standard linear solids for attenuation receiver set parameters for seismogramsseismotype = 4 # record 1=displ 2=veloc 3=accel 4=pressure 5=curl of displ 6=the fluid potential first receiver setnrec = 11 # number of receivers display parametersNSTEP_BETWEEN_OUTPUT_INFO = 300 # every how many time steps we display information about the simulation (costly, do not use a very small value) for JPEG color imagesoutput_color_image = .true. # output JPEG color image of the results every NSTEP_BETWEEN_OUTPUT_IMAGES time steps or not for PostScript snapshotsoutput_postscript_snapshot = .false. # output Postscript snapshot of the results for wavefield dumpsNSTEP_BETWEEN_OUTPUT_WAVE_DUMPS = 100 # every how many time steps we dump results of the simulation as ASCII or binary files (costly, do not use a very small value) output_grid_Gnuplot = .false. # save the grid in a text file or not velocity and density modelsnbmodels = 2 # nb of different models define models as I: (model_number,1,rho,Vp,Vs,0,0,QKappa Qmu) or II: (model_number,2,rho,c11,c13,c15,c33,c35,c55) or III: (model_number,3,rhos,rhof,phi,c,kxx,kxz,kzz,Ks,Kf,Kfr,etaf,mufr,Qmu).For istropic elastic/acoustic material use I and set Vs to zero to make a given model acoustic, for anisotropic elastic use II,and for isotropic poroelastic material use III. The mesh can contain acoustic, elastic, & poroelastic models simultaneously1 1 1000.d0 1500.d0 0.0d0 0 0 10.d0 10.d0 0 0 0 0 0 0 external mesh or notread_external_mesh = .true. absorbing boundary active or notPML_BOUNDARY_CONDITIONS = .false. for horizontal periodic conditions: detect common points between left and right edgesADD_PERIODIC_CONDITIONS = .false. horizontal periodicity distance for periodic conditionsPERIODIC_horiz_dist = 0.3597d0 grid point detection tolerance for periodic conditionsPERIODIC_DETECT_TOL = 3.3334d-6 #----------------------------------------------------------------------------- PARAMETERS FOR EXTERNAL MESHINGdata concerning mesh, when generated using third-party app (more info in README)(see also absorbing_conditions above)mesh_file = Mesh_solid_fluid_flat # file containing the mesh #----------------------------------------------------------------------------- PARAMETERS FOR INTERNAL MESHINGfile containing interfaces for internal meshinterfacesfile = Interface_flat_ASM_DGA_119_62kHz.dat geometry of the model (origin lower-left corner = 0,0) and mesh descriptionxmin = -1.d0 # abscissa of left side of the model absorbing boundaries parametersabsorbbottom = .true. define the different regions of the model in the (nx,nz) spectral element meshnbregions = 2 # nb of regions and model number for each |
I checked and found that you did a mistake an inversion of file names. Le 05/05/2015 23:08, gualtierilucia a écrit :
|
Where is this inversion? Do you mean the file name "solid_fluid.geo"? |
Hello,
I am having some problems generating the mesh configuration for specfem2D (version 7.0.0) using Gmesh. I cannot use the internal mesh since I need to build crossing interfaces.
Here the steps I followed:
I created the input file called “solid_fluid_flat.geo” (see below): this is a simple two layer model (top:fluid; bottom:solid) with a flat interface;
I wrote this input file using SPECFEM2D-7.0.0/EXAMPLES/Gmsh_example_MPI/SqrCirc.geo as reference.
I run gmsh (I tried both on mac OX (mesh downloaded from http://geuz.org/gmsh/) and on linux (gmsh-2.8.4-Linux from http://geuz.org/gmsh/bin/Linux/).:
gmsh -2 solid_fluid_flat.geo
on the shell
python SPECFEM2D-7.0.0/UTILS/Gmsh/LibGmsh2Specfem_convert_Gmsh_to_Specfem2D_official.py solid_fluid_flat -t F -b A -r A -l A
I get no errors up to this stage.
xmeshfem2D > OUTPUT_FILES/output_mesher.txt
and at this stage I get this:
At line 138 of file ./part_unstruct.F90 (unit = 990, file = 'Mesh_solid_fluid_flat')
Fortran runtime error: End of file
I am wondering if this is related to the fact that the manual says that the mesh should be built selecting a couple of options, “Subdivision algorithm” and “Element order" (page 10). How/Where can I set these options?
Thanks.
Regards,
Lucia
============================== solid_fluid_flat.geo =============================
km=1;
s=0.1;
lc1=1_km_s;
Point(1) = {-1_km,-1_km,0,lc1};
Point(2) = {1_km ,-1_km,0,lc1};
Point(3) = {1_km,1_km,0,lc1};
Point(4) = {-1_km,1_km,0,lc1};
Point(5) = {-1_km, 0.5_km,0,lc1};
Point(6) = {1_km, 0.5_km,0,lc1};
Line(1)={3,4};
Line(2)={4,1};
Line(3)={2,1};
Line(4)={2,3};
Line(5)={5,6};
Line(6)={1,5};
Line(7)={6,2};
Line(8)={4,5};
Line(9)={6,3};
Line Loop(100)={1,8,5,9};
Line Loop(200)={5,7,3,6};
Plane Surface(10)={100};
Plane Surface(11)={200};
Recombine Surface{10,11};
Mesh.SubdivisionAlgorithm = 1;
Physical Line("Top") = {1};
Physical Line("Left") = {2};
Physical Line("Bottom") = {3};
Physical Line("Right") = {4};
Physical Surface("M1") = {10};
Physical Surface("M2") = {11};
The text was updated successfully, but these errors were encountered: