From komatitsch at lma.cnrs-mrs.fr  Thu Jun  7 18:25:58 2018
From: komatitsch at lma.cnrs-mrs.fr (Dimitri Komatitsch)
Date: Fri, 8 Jun 2018 03:25:58 +0200
Subject: [CIG-SEISMO] Fwd: Re:  Movie volume script
In-Reply-To: <1769f01d-f298-01bd-96c7-4b8d61340671@lma.cnrs-mrs.fr>
References: <tencent_E34FF80428967138ABCED640@qq.com>
 <1769f01d-f298-01bd-96c7-4b8d61340671@lma.cnrs-mrs.fr>
Message-ID: <fa084d73-01eb-6c27-8e9f-90f9d0181178@lma.cnrs-mrs.fr>


Dear Huihui,

Thank you very much for your bug report. I have now fixed the problem 
(the parameter is now USE_VTK_INSTEAD_OF_MESH defined in file 
src/auxiliaries/combine_vol_data_impl.f90 as a classical Fortran parameter).
I also updated the users manual.

Thank you,
Best regards,
Dimitri.

> -------- 
> Subject:  Re: [CIG-SEISMO] Movie volume script
> Date:     Thu, 17 May 2018 15:15:06 +0100
> From:     USTC <qfkq7850 at mail.ustc.edu.cn>
> Reply-To:     cig-seismo at geodynamics.org
> To:     cig-seismo <cig-seismo at geodynamics.org>
> 
> Hi all,
> 
> 
> I have fixed this problem (as follow) by change the source code 
> “$home/src/auxiliaries/combine_vol_data.F90”.  I deleted the conditional 
> statements for the compile, i.e., the line #ifdef 
> USE_VTK_INSTEAD_OF_MESH and the lines between #else and #endif. After 
> doing that, compile these f90 codes, and the compiled codes will combine 
> the volumes data into VTK-format files. Alternatively, you could try to 
> define the parameter USE_VTK_INSTEAD_OF_MESH in the Makefile or some 
> other places. Hope it helps.
> 
> 
> Best regards,
> 
> Huihui
> 
> 
>    Original Message
> *Sender:* USTC<qfkq7850 at mail.ustc.edu.cn>
> *Recipient:* cig-seismo at geodynamics.org
> *Date:* Wednesday, May 9, 2018 15:16
> *Subject:* Movie volume script
> 
> Hi the Specfem3D developers,
> 
> I am trying to use the script "combine_vol_data" to combine the output 
> files into VTK-format files. But I find combine_vol_data create *.mesh 
> files by default. The manual (page 76) suggests that I can change the 
> logical constant parameter USE_VTK_OUTPUT to .true. in 
> src/auxiliaries/combine_vol_data.f90 before the command "make 
> combine_vol_data", but I only find combine_vol_data.F90 in that 
> directory and there is no parameter USE_VTK_OUTPUT in this script. How 
> could I do to make combine_vol_data create VTK-format file in this 
> version of specfem3d? The version of the code and manual is the latest 
> one downloaded from the CIG website. Thanks in advance.
> 
> Best regards,
> Huihui Weng
> 

-- 
Dimitri Komatitsch, CNRS Research Director (DR CNRS)
Laboratory of Mechanics and Acoustics, Marseille, France
http://komatitsch.free.fr

From seis_phd at yahoo.com  Thu Jun 14 17:19:32 2018
From: seis_phd at yahoo.com (seisphd)
Date: Fri, 15 Jun 2018 00:19:32 +0000 (UTC)
Subject: [CIG-SEISMO] SPECFEM2D Moment tensor
References: <1029865547.637659.1529021972252.ref@mail.yahoo.com>
Message-ID: <1029865547.637659.1529021972252@mail.yahoo.com>

Dear SPECFEM2D developers and users, 

I would like to ask for your help on how to make a proper approximation on a station using a moment tensor as a source.
I ve gone through the manual and the papers describing the problem but I got  a little bit confused.
So if I have a Strike 322, Dip 40, Rake -72 foc mecthen I get 
Mxx  Myy  Mzz  Mxy  Mxz  Myz :0.54774   0.38886  -0.93661   0.50245  -0.28821   0.01560
If I use only Mxx Mzz Mxz its fine for the stations at distances bigger than the dimensions of the rapture. BUT only for the stations with 90deg azimuth.
In practice, how can I get the correct Mxx Mzz Mxz at a station with a different azimuth? Lets say 60 deg.
Can you please provide an example on that?



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.geodynamics.org/pipermail/cig-seismo/attachments/20180615/85476fab/attachment.html>

From physseismo at gmail.com  Fri Jun 15 16:37:33 2018
From: physseismo at gmail.com (phys seismo)
Date: Fri, 15 Jun 2018 23:37:33 +0000
Subject: [CIG-SEISMO] SPECFEM2D Moment tensor
Message-ID: <CANgnxsQCbGrAFPeu9TLGk4Vu_VN7kSfvK=kj3cVvB4547Vi6+A@mail.gmail.com>

Dear SPECFEM2D developers and users,

I would like to ask for your help on how to make a proper approximation on
a station using a moment tensor as a source.

I ve gone through the manual and the relative papers describing the problem
but I got  a little bit confused.

So if I have for example a Strike 322, Dip 40, Rake -72 foc mec
then I get

Mxx  Myy  Mzz  Mxy  Mxz  Myz :
0.54774   0.38886  -0.93661   0.50245  -0.28821   0.01560

If I use only Mxx Mzz Mxz its fine for the stations at distances bigger
than the dimensions of the rapture. BUT only for the stations with 90deg
azimuth.

In practice, how can I get the correct Mxx Mzz Mxz at a station with a
different azimuth? Lets say 60 deg.

Can you please provide an example on that? I am interested for P waves for
now

Thank you in advance, your help means a lot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.geodynamics.org/pipermail/cig-seismo/attachments/20180615/cd582355/attachment.html>

From zongboxu at u.boisestate.edu  Thu Jun 28 15:41:11 2018
From: zongboxu at u.boisestate.edu (Zongbo Xu)
Date: Thu, 28 Jun 2018 16:41:11 -0600
Subject: [CIG-SEISMO] About building topographic meshes
Message-ID: <CAPojvd4hWm=Rv1xsztsEC+UnpoWGSDKjP++MhvjFSQRTdo8-JQ@mail.gmail.com>

Hi SPECFEM3D developers

I was trying to build topographic meshes for SPECFEM3D. I tried Trelis
(Cubit) and internal mesher. I found issues with both:

1. Trelis. I tried the topography_model examples in CUBIT_GEOCUBIT, and the
examples did not work. The error I got is

Traceback (most recent call last):
  File "create_mesh.py", line 16, in <module>
    volumes.volumes(cfg)
  File "/usr/local/specfem3d/CUBIT_GEOCUBIT/geocubitlib/volumes.py", line
40, in volumes
    cfg = start.start_cfg(filename=filename)
  File "/usr/local/specfem3d/CUBIT_GEOCUBIT/geocubitlib/start.py", line
173, in start_cfg
    os.makedirs(cfg.working_dir)
AttributeError: 'attrdict' object has no attribute 'working_dir'

I was wondering if someone know how to fix the error.

2. The manual indicates that the internal mesher does not support CPML yet.
I was wondering if someone is improving the internal mesher to support CPML.

Thank you.

Best wishes,
Zongbo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.geodynamics.org/pipermail/cig-seismo/attachments/20180628/47c30674/attachment.html>