search

kmaterna / Strain_2D

Strain rate modeling from GNSS velocity fields
MIT License
44 stars 19 forks source link

VISR issue #36

Open jlmaurer opened 8 months ago

jlmaurer commented 8 months ago

Trying to get visr running locally and having issues. Downloading sample files from website but vel_intrp.dat is no longer available at http://scec.ess.ucla.edu/~zshen/visr/visr.html, thus it's not currently possible to run the test dataset. Running on my own files results in a data file read error:

Fortran runtime error: Bad value during floating point read

Any ideas?

kmaterna commented 8 months ago

Could it be the same as this issue: https://github.com/kmaterna/Strain_2D/issues/32

Down in the comments, I sent a zip-file of a fortran source code that I have on my computer. It's possible the website files have changed on the visr webpage and we could talk to Zheng-Kang about it?

tobiscode commented 1 month ago

Hi,

I didn't want to bother finding the VISR files online and coded up an simplified version purely in Python. It runs pretty fast, has both distance and coverage options, doesn't need min_max_inc_smooth as it optimizes the curve automatically, but doesn't have the uncertainty_threshold or fault options. Since it's not really new code, but it does make things easier to use if you don't need the fault capabilities, I was wondering whether I should submit a PR with this code @kmaterna? It'll join my DISSTANS package soon so it wouldn't be a huge effort. We could call it "Simple VISR" or something like that?

Cheers

kmaterna commented 1 month ago

Hi @tobiscode, that would be very useful! More people are running into this visr-download issue over time, and it's unsustainable for me to keep uploading a zip of the files I downloaded 6 years ago... I would be happy to check out the branch and help with the config-file and other plumbing on the PR. Thank you very much!!

On Fri, Aug 16, 2024 at 10:18 AM Tobias Köhne @.***> wrote:

Hi,

I didn't want to bother finding the VISR files online and coded up an simplified version purely in Python. It runs pretty fast, has both distance and coverage options, doesn't need min_max_inc_smooth as it optimizes the curve automatically, but doesn't have the uncertainty_threshold or fault options. Since it's not really new code, but it does make things easier to use if you don't need the fault capabilities, I was wondering whether I should submit a PR with this code @kmaterna https://github.com/kmaterna? It'll join my DISSTANS https://github.com/tobiscode/disstans package soon so it wouldn't be a huge effort. We could call it "Simple VISR" or something like that?

Cheers

— Reply to this email directly, view it on GitHub https://github.com/kmaterna/Strain_2D/issues/36#issuecomment-2293875231, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC7QOVD3DST4VZZJKFMCFSLZRYYADAVCNFSM6AAAAABC757OQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJTHA3TKMRTGE . You are receiving this because you were mentioned.Message ID: @.***>