need help in my plot

[Goziephy]

Problem description

Need help with my plot

Please describe your issue here.
Good evening Prof., I sent you traveltime.TOM file the other day and you plotted it and share the code with me. Your plot appeals exactly as it is in reflexW software with scale 10 to 60 seconds on traveltime axis); But when i run the code with the file, my plot displaced the traveltime (y-axis) having 0.01 to 0.06 scale which is different from yours. Please what can i do?
Hope to hear from you

Your environment: Jupyter-notebook

Please provide the output of print(pygimli.Report()) here. If that does not
work, please give provide some additional information on your:

Operating system: Windows
Python version: 3.11.5
pyGIMLi version: Output of `print(pygimli.version):1.4.4
Way of installation: e.g. Conda package, manual compilation from source, etc.

Steps to reproduce

Tell us how to reproduce this issue. Ideally, you could paste the code that produces the error:

import pygimli as pg
...

Expected behavior

Tell us what should happen or what you want to achieve.
what do have the scale with you on traveltime axis

Actual behavior

Tell us what happens instead and/or provide the output of your script.

[halbmy]

Note that I added the line data["t"] /= 1000 because I guess the traveltime in the file is in obviously ms and not s. This needs to be changed in the import routine (if the TOM file always contains ms) but until then you will have to multiply by yourself.

[makeabhishek]

what is data[t]/=1000 in line 5? Just saw that same comment was made by Prof @halbmy

[halbmy]

the traveltimes are divided by 1000

[Goziephy]

Thank you all for replying, The code is now running fine, but the second step apparent velocity is not showing well. Attached is the screenshot of the code and the displace. Hope to get a response

[Goziephy]

Note that I added the line data["t"] /= 1000 because I guess the traveltime in the file is in obviously ms and not s. This needs to be changed in the import routine (if the TOM file always contains ms) but until then you will have to multiply by yourself.

Thank you prof., The code is now running fine, but the second step apparent velocity is not showing well. Attached is the screenshot of the code and the displace. Hope to get a response

[halbmy]

As the output says, you seem to have zero traveltime leading to infinite apparent velocity. Remove those data with data.remove(data["t"] <= 0]).

[Goziephy]

As the output says, you seem to have zero travel-time leading to infinite apparent velocity. Remove those data with data.remove(data["t"] <= 0]).

Thanks prof., the output from the code displaced this; as in the attached file but my apparent velocity is showing range 0.26. to 5.26. I don't know if the range is okay or needs to be multiplied. moreover there are some empty space in the model which i don't know if is okay too.

[Goziephy]

As the output says, you seem to have zero traveltime leading to infinite apparent velocity. Remove those data with data.remove(data["t"] <= 0]).

Thanks prof., the output from the code displaced this; as in the attached file but my apparent velocity is showing range 0.26. to 5.26. I don't know if the range is okay or needs to be multiplied. moreover there are some empty space in the model which i don't know if is okay too.

[halbmy]

I am pretty sure you DO need to multiply your data with 0.001 as discussed before. Which wave is so slow to have a traveltime of 60 seconds on a distance of 100m?? The lowest values would then be around 300m/s (the speed in air) and the highest at 5000 m/s (typical values for hard rock). The missing values are probably the ones with zero traveltime.

And please, don't send smartphone photos. You already have a notebook and can copy the output into the issue.

[Goziephy]

I am pretty sure you DO need to multiply your data with 0.001 as discussed before. Which wave is so slow to have a traveltime of 60 seconds on a distance of 100m?? The lowest values would then be around 300m/s (the speed in air) and the highest at 5000 m/s (typical values for hard rock). The missing values are probably the ones with zero travel-time.

And please, don't send smartphone photos. You already have a notebook and can copy the output into the issue.

Thank you prof., I multiplied 0.001 in the code and my velocity range is still showing 0.26 to 5.26. Attached is my output and script.


SRTD.txt

[Goziephy]

I am pretty sure you DO need to multiply your data with 0.001 as discussed before. Which wave is so slow to have a traveltime of 60 seconds on a distance of 100m?? The lowest values would then be around 300m/s (the speed in air) and the highest at 5000 m/s (typical values for hard rock). The missing values are probably the ones with zero traveltime.

And please, don't send smartphone photos. You already have a notebook and can copy the output into the issue.

Prof. the code is running fine if i run it in anaconda prompt but in jupyter-notebook is displacing 0.26 to 5.27 m/s for velocity

[halbmy]

The plots look correct. But if you run the same code on the command line and in a notebook (using the same pygimli in the same environment), the results should be the same.

[Goziephy]

The plots look correct. But if you run the same code on the command line and in a notebook (using the same pygimli in the same environment), the results should be the same.

Yes prof. is the same now IF I JOIN all the code together but i run this code below for fit between measured (crosses) and modeled (lines) travel-times and i am having a empty displace cells saying ( Line2D.set() got an unexpected keyword argument 'orientation'). Attached is the code, output and error message.

mgr.invert(secNodes=3, paraMaxCellSize=5.0,
zWeight=0.2, vTop=500, vBottom=5000, verbose=1)
mgr.showFit(firstPicks=True)

SRTT.txt

[halbmy]

Yes, that's definitely an error that need to be corrected. Thank you for point out.

[Goziephy]

Yes, that's definitely an error that need to be corrected. Thank you for point out.

Good evening Prof.,
Prof., the code is still not working yet. still showing as before

[halbmy]

TravelTimeManager.showFit() (firstPicks is True by default) shows the measured data as crosses along with the forward response as lines like demonstrated in the traveltime field data example

There was apparently some bug in one of the previous versions which was fixed with the last version v1.4.6.