[CIG-SEISMO] Asking SPECFEM2D SU format (other email)

[Kasper van Wijk]

Dimitiri, calling the files Uz_single.su or something, would take away
confusion. I don't think you need Uz_single_bin.su, as that would be
redundant.

Cheers,
Kasper


On 29 August 2013 23:47, Dimitri Komatitsch <komatitsch at lma.cnrs-mrs.fr>wrote:

>
> Dear all,
>
> Would it make sense to rename the binary files from *.bin to *.bin.su or
> to *_bin.su then (when SU_FORMAT is on), to avoid confusion?
>
> Or is it obvious that SU format is just a binary array?
>
> Let me know if you would like me to change that.
>
> Thanks,
> Dimitri.
>
> On 07/10/2013 06:55 PM, Yang Luo wrote:
>
>> Hi there,
>>
>
>  I have been away from the group for quite a while, so I'm not sure
>> whether anyone has modified that portion of the code.
>>
>
>  If no one has, the *.bin files are the seismograms in seismic unix
>> format, if you turn the SU_FORMAT on.
>>
>
>  Sometimes you need to swapbytes, before you can view it correctly in SU.
>>
>
>  Thanks,
>> Yang
>>
>>
>> On Mon, Jul 8, 2013 at 10:18 AM, Jungrak SON <jrson2011 at gmail.com
>> <mailto:jrson2011 at gmail.com>> wrote:
>>
>>     To whom it may concern,
>>
>>     Hi, My name is Jungrak Son who is MS student in Texas and have tried
>>     to use SPECFEM2D. Thankfully I found this precious software package
>>     and decided to prepare my thesis with using it. I made my own
>>     examples successfully, but I still have a little problem.
>>
>>     What I have done is below.
>>
>>     << SU_FORMAT = .true.   # output single precision binary seismograms
>>     in Seismic Unix format   >>
>>
>>     I also make << save_binary_seismograms_single = . true. >> .
>>
>>     However, I cannot find any file of extension *.su . I couldn't open
>>     " Ux_file_single.bin " and " Uz_file_single.bin " . I know how to
>>     get seismogram in ASCII format, using xmgrace, but I need to open it
>>     Seismic Unix.
>>
>>     One more thing, Can I use CUBIT not only for 3D but for 2D? The
>>     external 2D mesh example "canyon" was a little different from CUBIT
>>     output file and I could not find any python files in the package.
>>     Actually I am very good at using CUBIT, but SPECFEM3D seems much
>>     difficult to understand.
>>
>>
>>     I'm sorry to bother you, but studying SPECFEM alone is a little
>>     tough. Would you please help me to overcome these problem? Thanks
>>     for considering.
>>
>>     Sincerely,
>>
>>
>>     - Jungrak Son
>>
>>
>>     ______________________________**_________________
>>     CIG-SEISMO mailing list
>>     CIG-SEISMO at geodynamics.org <mailto:CIG-SEISMO@**geodynamics.org<CIG-SEISMO at geodynamics.org>
>> >
>>     http://geodynamics.org/cgi-**bin/mailman/listinfo/cig-**seismo<http://geodynamics.org/cgi-bin/mailman/listinfo/cig-seismo>
>>
>>
>>
>>
>> ______________________________**_________________
>> CIG-SEISMO mailing list
>> CIG-SEISMO at geodynamics.org
>> http://geodynamics.org/cgi-**bin/mailman/listinfo/cig-**seismo<http://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
> ______________________________**_________________
> CIG-SEISMO mailing list
> CIG-SEISMO at geodynamics.org
> http://geodynamics.org/cgi-**bin/mailman/listinfo/cig-**seismo<http://geodynamics.org/cgi-bin/mailman/listinfo/cig-seismo>
>



-- 
kasper van wijk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://geodynamics.org/pipermail/cig-seismo/attachments/20130830/4d5392d9/attachment.html>