Skip to content
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

shake map #120

Closed
joa-quim opened this issue Oct 11, 2018 · 16 comments · Fixed by #133
Closed

shake map #120

joa-quim opened this issue Oct 11, 2018 · 16 comments · Fixed by #133
Labels
longterm Long standing issues that need to be resolved

Comments

@joa-quim
Copy link
Member

What would be the interest of having a new module(s) to compute shake maps like those displayed by USGS?
I have it done (ported from my old MEX for GMT4) and makes it a breeze to compute the Vs30 grids as compared to the cumbersome (original) way.

The point is that I'm not a seismologist and if people start to ask questions the burden of it would probably had to go to @seisman

@PaulWessel
Copy link
Member

Right, we do want a seismologist's perspective on this. And @seisman is our man! What say you?

@seisman
Copy link
Member

seisman commented Oct 11, 2018

@joa-quim @PaulWessel I don't got what you're going to do. Can you explain more details?

@PaulWessel
Copy link
Member

@joa-quim , links please.

@joa-quim
Copy link
Member Author

joa-quim commented Oct 11, 2018

Well, I gave links (two). More, USGS shake maps
I have two modules that:

Compute the Vs30 (Vs velocities on the upper 30 meters) just from topography

vs30 palu_bat.grd -C1 -Glix_vs.grd

use that Vs30 grid and compute the shake map (intensity) of the recent Indonesia earthquake.

shake lix_vs.grd -Glixo.grd -Lline.dat -Ci -V -M7.5

The question is, is this an interesting module to have in GMT (in meca)?

@PaulWessel
Copy link
Member

Yes you did give links, sorry.

@joa-quim
Copy link
Member Author

I'm afraid this is falling on the oblivion category. @seisman, do you have a opinion on this?

@seisman
Copy link
Member

seisman commented Oct 18, 2018

Sorry for the late reply. I just came back from a field trip.

I know little about Vs30 and shakemap. The idea of shakemap is interesting. However, USGS has provided a Python module and CLI (https://github.com/usgs/shakemap) to generate near-real-time shakemap. Do we really need to rewrite it with GMT?

@joa-quim
Copy link
Member Author

Well, I did it because I already had it in Mirone but it was using GMT4. Since I hate loosing things I migrate it to GMT5 and created the vs30 module that is way more simple to use (and build) than the official version.

It's true that USGS has it but

  1. It's a Python code, not an executable
  2. Mac OSX or Linux operating systems. I.e, no Windows.

@seisman
Copy link
Member

seisman commented Oct 18, 2018

@joa-quim Feel free to add it into GMT. I'll try my best to answer related questions.

@PaulWessel
Copy link
Member

As we try to finish up GMT 6 for release, adding modules makes this more complicated, no. We have to draw the line soon.

@joa-quim
Copy link
Member Author

I don't mind to leave this to a 6.1 but by now I would like to have a copy in other place than my local repo only.

@PaulWessel
Copy link
Member

@leouieda and I discussed this and you could simply create a branch specifically for working on the shakemap but not merge it to master until after 6 is released.

@joa-quim
Copy link
Member Author

That's the solution I thought too. I only have to learn how to keep my local branch in sync with master, so that I can build a dll updated with all to use from Mirone.

@leouieda
Copy link
Member

@joa-quim you can git merge master from your branch any time you want to sync.

@stale
Copy link

stale bot commented Jan 23, 2019

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions.

@stale stale bot added the stale This will not be worked on label Jan 23, 2019
@joa-quim joa-quim added the longterm Long standing issues that need to be resolved label Jan 23, 2019
@stale stale bot removed the stale This will not be worked on label Jan 23, 2019
@joa-quim
Copy link
Member Author

Opened issue on USGS interest at vs30 grids generation
usgs/earthquake-global_vs30#45

obaney pushed a commit to obaney/gmt that referenced this issue Aug 18, 2021
Cleans up the base directory.
Keep contributing guide and code of conduct because those are important files
that people should see right away.
Fixes GenericMappingTools#120
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
longterm Long standing issues that need to be resolved
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants