[Shake-dev] Integration of accelerometer data to shakemap

Phuntsho Pelgay ppelgay at moea.gov.bt
Mon Oct 21 18:27:18 UTC 2019


Hi Charles
Thank you so much for the link. Will walk through.

On Tue, Oct 22, 2019 at 1:18 AM Charles (Contractor) Worden <
cbworden at contractor.usgs.gov> wrote:

> Hi Phuntsho,
>
> Regarding documentation for ShakeMap v4, we have a wiki that should guide
> you through the installation and setup:
>
> https://github.com/usgs/shakemap/wiki
>
> And an extensive manual here:
>
> http://usgs.github.io/shakemap/sm4_index.html
>
> Hopefully these will help with your work on ShakeMap.
>
> Bruce
>
>
> C. Bruce Worden
> Synergetics Inc. Contractor in support of USGS
> Please note that my USGS email address is now:
> cbworden at contractor.usgs.gov
>
>
>
>
> On Oct 21, 2019, at 11:36 AM, Phuntsho Pelgay <ppelgay at moea.gov.bt> wrote:
>
> Dear David and  Kuo-wan Lin
>
> Thank you so much for your prompt reply. Well, I am very much intrigued by
> the capabilities of Shakemap and ShakeCast. Being from Bhutan, located in
> Seismic hotbed, I am convinced that these systems can play pivotal role
> during large seismic event. Thus, I would be very much glad to attend the
> Singapore workshop in 2020.
>
> Well, regarding the version, I am already using the latest versions (V4)
> and given that there is little guide on this version is somewhat painful.
> However, I am hopeful of getting useful tips through this platform.
>
> Once again, thank you.
>
> On Mon, Oct 21, 2019 at 10:41 PM David Wald <wald at usgs.gov> wrote:
>
>> Dear Phuntsho,
>>
>>
>>
>> Thanks for your note.
>>
>>
>>
>> I attempt to *answer your questions below*, but feel free to contact me
>> directly for any others.
>>
>>
>>
>> *NOTE*: For anyone else working with ShakeMap in Asia (e.g., ASEAN/APEC
>> countries), we hope to hold a workshop associated with the upcoming
>> Understanding Risk Forum (UR2020) to be held in Singapore, May 18-22, 2020.
>> That is pending approval from the organizers. The workshop will be
>> “ShakeMap‐Related Research, Development, Operations, and Applications”. We
>> will notify the shake-dev list-server when we know more.
>>
>>
>>
>> @Phuntsho: This workshop would be beneficial for you and we’d be glad to
>> have you attend. We *hope* to be able to offer travel support pending
>> approval.
>>
>>
>>
>> Regards,
>>
>>
>>
>> David
>>
>> --
>>
>> David Wald, Ph.D.
>>
>> U.S. Geological Survey, Golden, CO
>>
>> wald at usgs.gov, (303) 273 8441
>>
>>
>>
>>
>>
>> From: Shake-dev <shake-dev-bounces at geohazards.usgs.gov> on behalf of
>> Phuntsho Pelgay <ppelgay at moea.gov.bt>
>>
>> Date: Saturday, October 19, 2019 at 12:00 AM
>>
>> To: <shake-dev at geohazards.usgs.gov>
>>
>> Subject: [Shake-dev] Integration of accelerometer data to shakemap
>>
>>
>>
>> Dear shakemap
>>
>> I have following questions regarding shakemap as I am new to it:
>>
>> 1. I have been trying to use our own accelerometer meter data ( aka
>> intensity meter ), which gives PGA, PGV and MMI,  in shakemap. However, I
>> am not quite sure how shakemap modules consider these data for calculation.
>> I have read technical guide for version 3.5 about macro seismic data. There
>> it says measured intensity data are weighted low for calculation of
>> shakemap. I have tried to convert our own intensity data to shakemap
>> readable xml and run the model. And I have played around the pga and MMI
>> values in that xml and run the shakemap module for the same event id to see
>> the changes in the outputs. But, I saw no changes in the outputs. So
>> my question is, how do we configure shakemap so that it uses only local
>> strong motion data to generate shakemap. Our objective is to monitor
>> earthquake intensity locally, and we have dense enough strong motion
>> stations.
>>
>>
>>
>> Depending on where you are in your efforts, you might (should?) consider
>> upgrading to ShakeMap V4. We can be of much more help on the latest system.
>> That said, you don’t need to put MMI values into the instrumental data
>> files that are used at ShakeMap input. Those values are computed separately
>> within ShakeMap. If do you have actual MMI data (assigned intensities),
>> they go in a separate input file (e.g., [macroseismic]_dat.xml), and those
>> “stations” should show up separately from the stations on your maps if the
>> data are properly formatted. You can run ShakeMap with stations only,
>> simply by *not* having any [macroseismic]_dat.xml files in the input
>> directory.
>>
>>
>>
>> 2. We are using seiscomp to generate shakemap event file. How do we link
>> shakemap to shakecast, so that latter automatically uses shakemap products?
>> I am sorry if this question is irrelevant here.
>>
>> You’ll have to be indicate what versions of ShakeMap/ShakeCast you are
>> using. Preferably, you’ll upgrade to V4 ShakeMap and ShakeCast since we
>> favor supporting the later versions of the software. In general, ShakeCast
>> retrieves data from USGS feeds, but one can simply configure ShakeCast to
>> point to your local directories (with products put there directly by a
>> co-hosted ShakeMap instance). You’ll need to make the event *downloads*
>> directory available to ShakeCast, but the details of this depend on the
>> versions in use. Kuo-wan Lin will see such queries to
>> shakecast-help at usgs.gov and will be glad to help you.
>>
>>
>>
>> Thank you in advance
>>
>> --
>>
>> null
>>
>>
>>
>>
>>
>>
>>
>> This email and any files transmitted with it are confidential and
>> intended solely for the use of the individual or entity to whom they are
>> addressed. If you have received this email in error please notify the
>> administrator. Please note that any views or opinions presented in this
>> email are solely those of the author and do not necessarily represent those
>> of the organization he/she works for. Finally, the recipient should check
>> this email and any attachments for the presence of viruses. The company
>> accepts no liability for any damage caused by any virus transmitted by this
>> email.
>>
>>
>>
>> _______________________________________________ Shake-dev mailing list
>> Shake-dev at geohazards.usgs.gov
>> https://geohazards.usgs.gov/mailman/listinfo/shake-dev
>>
>
>
> --
> Phuntsho Pelgay
> Executive Geologist
> Masters in Earth-Sciences
> The University of Melbourne
> Department of Geology and Mines
> # +975-17708109
> Project Links:
> SATREPS Project for Evaluation and Mitigation of Seismic Risk for
> Composite Masonry Buildings in Bhutan
> https://www.jst.go.jp/global/english/kadai/h2811_bhutan.html
>
>
> ------------------------------
>
>
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the administrator.
> Please note that any views or opinions presented in this email are solely
> those of the author and do not necessarily represent those of the
> organization he/she works for. Finally, the recipient should check this
> email and any attachments for the presence of viruses. The company accepts
> no liability for any damage caused by any virus transmitted by this email.
>
> ------------------------------
>
> _______________________________________________
> Shake-dev mailing list
> Shake-dev at geohazards.usgs.gov
> https://geohazards.usgs.gov/mailman/listinfo/shake-dev
>
>
> --
null

-- 








This email and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they are 
addressed. If you have received this email in error please notify the 
administrator. Please note that any views or opinions presented in this 
email are solely those of the author and do not necessarily represent those 
of the organization he/she works for. Finally, the recipient should check 
this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://geohazards.usgs.gov/pipermail/shake-dev/attachments/20191022/5ce2e377/attachment.html>


More information about the Shake-dev mailing list