[CIG-SEISMO] assign external model specfem2D issue

[Dimitri Komatitsch]

Sorry, I meant "that is why the bug had remained undetected...".

The bug was, as you mentioned, that two parameters were missing in the 
subroutine definition.

Thanks,
Dimitri.

On 01/09/2015 06:08 PM, Dimitri Komatitsch wrote:
>
> Dear Eve, dear all,
>
> You are right, there was a small bug in that
> define_external_model_dummy() routine, which is unused by default (that
> was the bug has remained undetected).
>
> I fixed it on Dec 10 thus you just need to upgrade to the new version
> (typing "git pull" or doing a new "git checkout").
>
> Thanks,
> Best wishes,
>
> Dimitri.
>
>
> On 01/09/2015 04:58 PM, Eve Tsang-Hin-Sun wrote:
>> Dear all,
>>
>> I would like to run some simulations with solid and fluid layers. I saw
>> that there is an example provided in the EXAMPLES folder and was trying
>> to work on it to understand the details. I actually encountered some
>> problems when trying to assign an external velocity model. My first goal
>> is very simple as I just try to adapt the "define_external_model_dummy »
>> routine to the «  fluid_solid »
>>
>>
>>
>>
>>   case.
>>
>> As I understand it the variable « material_element » is a vector
>> containing the model number for each spectral element (so 1 or 2 in my
>> case). In the routine, each element is tested to read its model number
>> and then something happens (eg assigning some velocity values).
>>
>> In the Par_file_fluid_solid file, the fluid layer is numbered 2 and the
>> solid layer is numbered 1.
>>
>>
>> Any way, each time I try to run the code, I always get the same error :
>> STOP error: non acoustic material in DATA/Par_file or external mesh
>> redefined as acoustic in define_external_model()
>>
>> meaning that something is wrong in my Par_file or in my routine. Could
>> anyone explain to me why such an error would occur or what did I miss? I
>> also join the two files.
>>
>> My second problem concerns the «  read_external_file routine »  : in the
>> function, the « define_external_routine » is called. However the inputs
>> of the routine do not coincide with the ones given in the dummy example
>> (for example, gravity or Nsq). But the code compiles anyway…How is it
>> possible ? I admit that I am not fully familiar with f90…
>>
>> Thanks for your help.
>>
>> Regards,
>> Eve
>> --
>> Eve Tsang-Hin-Sun
>> Doctorante
>> Institut Universitaire Européen de la Mer (IUEM)
>> Laboratoires Domaines Océaniques (LDO)
>> Place Nicolas Copernic - 29280 Plouzané
>>
>>
>>
>> _______________________________________________
>> CIG-SEISMO mailing list
>> CIG-SEISMO at geodynamics.org
>> http://lists.geodynamics.org/cgi-bin/mailman/listinfo/cig-seismo
>>
>

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