| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
Sorry, something went wrong.
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #2595 +/- ##
=======================================
Coverage 92.14% 92.14%
=======================================
Files 248 248
Lines 50022 50022
Branches 4402 4402
=======================================
Hits 46091 46091
Misses 3222 3222
Partials 709 709
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry.
|
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB georgebisbas commented on 2025-05-02T06:30:10Z I think we usually have references at the last cell of a notebook. Not a strict rule though. JDBetteridge commented on 2025-05-02T12:36:06Z Fixed |
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB georgebisbas commented on 2025-05-02T06:30:11Z Line #1. # We import everything we need for the noterbook at the start notebook typo JDBetteridge commented on 2025-05-02T12:36:08Z Comment was superfluous anyway |
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB georgebisbas commented on 2025-05-02T06:30:12Z Should you add a comment on how it is (if it is) different from Deviot's builtin Ricker? JDBetteridge commented on 2025-05-02T12:36:09Z It isn't, but I really don't think it's necessary to invoke the wrath of examples.seismic.source.py that whole file could be 5 lines IMHO. I will change it if I'm instructed to, but this is much clearer |
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB georgebisbas commented on 2025-05-02T06:30:12Z Citation can be a link I guess JDBetteridge commented on 2025-05-02T12:36:14Z Fixed |
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB georgebisbas commented on 2025-05-02T06:30:13Z receiver* JDBetteridge commented on 2025-05-02T12:36:17Z Yes! |
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB georgebisbas commented on 2025-05-02T06:30:14Z Courant* |
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB georgebisbas commented on 2025-05-02T06:30:15Z Line #2. # space as per the work of Tam and Webb, Caunt Citations can be lifted to previous cell, and add link JDBetteridge commented on 2025-05-02T12:36:26Z Superfluous comment anyway |
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB georgebisbas commented on 2025-05-02T06:30:16Z velocity* |
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB georgebisbas commented on 2025-05-02T06:30:16Z Indistinguishable?* JDBetteridge commented on 2025-05-02T12:36:41Z Also see* 😂 |
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB mloubout commented on 2025-05-02T12:33:42Z Nitpicking: We usually group the imports as
lib
external
devito
so here would be
from functools import partial import numpy as np import scipy as sp import sympy as sym from matplotlib import patheffects import matplotlib.colors as colors import matplotlib.pyplot as plt from devito import Grid, Function, TimeFunction, SparseTimeFunction, Eq, Operator, solve |
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB mloubout commented on 2025-05-02T12:33:43Z THis should be available in examples/seismic/sources.py , maybe make it an importable function JDBetteridge commented on 2025-09-10T00:14:34Z This is going to be addressed in a refactor in a separate PR |
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB mloubout commented on 2025-05-02T12:33:44Z Spectrum (Fourier transform) is usualy plotted as continuous in geophys, so just plot not bar EdCaunt commented on 2025-06-02T11:01:47Z I quite like it as bars. It more clearly identifies the harmonics. I think conflating spectrum and spectral envelope is quite confusing really and probably bad practice, even if it is commonplace mloubout commented on 2025-08-05T12:43:38Z It's not clearer, people, especially the target audience, do not look at the Fourier spectrum like that, but as line plots. This makes it confusing. It's commonplace for a reason. JDBetteridge commented on 2025-09-10T00:14:55Z Fixed
|
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB mloubout commented on 2025-05-02T12:33:45Z Maybe point to where it's computed in examples/seismic/model.py so user/reader see it's implemented in the examples.
Also maybe h_min in case someone use different spacing in different dimensions |
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB mloubout commented on 2025-05-02T12:33:45Z Never seen that left one, that's interesting. EdCaunt commented on 2025-05-02T14:10:45Z It corresponds to the "squaring" effect of numerical dispersion on an expanding wavefront (effective velocity is greater off-axis and less on-axis).
|
Sorry, something went wrong.
|
Fixed View entire conversation on ReviewNB |
Sorry, something went wrong.
|
Comment was superfluous anyway View entire conversation on ReviewNB |
Sorry, something went wrong.
|
It isn't, but I really don't think it's necessary to invoke the wrath of examples.seismic.source.py that whole file could be 5 lines IMHO. I will change it if I'm instructed to, but this is much clearer View entire conversation on ReviewNB |
Sorry, something went wrong.
|
Fixed View entire conversation on ReviewNB |
Sorry, something went wrong.
|
Yes! View entire conversation on ReviewNB |
Sorry, something went wrong.
|
Superfluous comment anyway View entire conversation on ReviewNB |
Sorry, something went wrong.
|
Also see* 😂 View entire conversation on ReviewNB |
Sorry, something went wrong.
|
It corresponds to the "squaring" effect of numerical dispersion on an expanding wavefront (effective velocity is greater off-axis and less on-axis).
View entire conversation on ReviewNB |
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB EdCaunt commented on 2025-05-02T14:20:18Z Typo: "peeking" (to surreptitiously look at something), not "peaking" (to reach a highest point) |
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB mloubout commented on 2025-08-05T12:57:21Z Would print the whole array weights to show it gives you all the orders JDBetteridge commented on 2025-09-10T00:21:34Z This is done above in section 1 |
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB mloubout commented on 2025-08-05T12:57:21Z Can you make the grid coarser, the r=0.336 still shows dispersion would be "nicer" to go from no dispersion to dispersion JDBetteridge commented on 2025-09-10T00:22:57Z I think this is sufficient to get the point across
|
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB mloubout commented on 2025-08-05T12:57:22Z It is not unstable; unstable is for dt> Courant. It is just very dispersive. You can also point out that from the dispersion curves, when it gets dispersive, the high frequencies travel faster, which explains the early arrival. JDBetteridge commented on 2025-09-10T00:24:18Z You're right it's not unstable for this choice of velocity, but it is for the whole range considered as outlined in the introduction. This is what the calculation is based on. I will add clarification |
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB mloubout commented on 2025-08-05T12:57:23Z Label axis. |
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB mloubout commented on 2025-08-05T12:57:23Z It's still slightly dispersive for r=0.336, would go better with the message to have at least one clean case without dispersion visible. JDBetteridge commented on 2025-09-10T00:34:15Z We see that in the final example below |
Sorry, something went wrong.
|
View / edit / reply to this conversation on ReviewNB mloubout commented on 2025-08-05T12:57:24Z Maybe add some markers so can see both on the left JDBetteridge commented on 2025-09-10T00:37:08Z I made it dots |
Sorry, something went wrong.
There was a problem hiding this comment.
I think I'm pretty happy with this now
Sorry, something went wrong.
|
This adds widgets, they used to be part of ipython or matplotlib or notebook, but have been factored into their own package View entire conversation on ReviewNB |
Sorry, something went wrong.
|
This is going to be addressed in a refactor in a separate PR View entire conversation on ReviewNB |
Sorry, something went wrong.
|
Fixed
View entire conversation on ReviewNB |
Sorry, something went wrong.
|
I was referencing that whole section, but it's fixed now View entire conversation on ReviewNB |
Sorry, something went wrong.
|
They are optimal for accuracy according to the reference: of optimal formal order of accuracy View entire conversation on ReviewNB |
Sorry, something went wrong.
|
This is done above in section 1 View entire conversation on ReviewNB |
Sorry, something went wrong.
|
I think this is sufficient to get the point across
View entire conversation on ReviewNB |
Sorry, something went wrong.
|
You're right it's not unstable for this choice of velocity, but it is for the whole range considered as outlined in the introduction. This is what the calculation is based on. I will add clarification View entire conversation on ReviewNB |
Sorry, something went wrong.
|
We see that in the final example below View entire conversation on ReviewNB |
Sorry, something went wrong.
|
I made it dots View entire conversation on ReviewNB |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
No description provided.