-
Notifications
You must be signed in to change notification settings - Fork 133
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
FDEM dataset #122
Comments
Both coil spacing and frequency can be vectors that can come from different instruments. The FDEM manager was one of the first manager developed ever and it needs to be modernized and expanded. |
Thanks for your quick answer, Enclosed are two file, EM31.csv, coil spacing at 3.66 and frequency 9800 Hz and CMD.csv coil spacing at 1.2 meter and Frequency at 31 kHz. In advance, thank you. I would not bring little help with a case study, if this is something you are looking for. Although I think you already have many dataset, just not the time to take care of it :) Cheers |
Well it is easy to read those files with numpy.genfromtxt. Are the field values units percentages of the primary field or apparent resistivities/conductivities? I guess the latter? So there is only an out-of-phase component? I am also a bit puzzled by the x and y coordinates. At the moment, the FDEM manager can only work with vertical magnetic dipoles (that's one of the things for the expansion), so with those two instruments you end up with only two data for each sounding, so even an inversion of a two-layer model (with 3 unknowns) does not make sense. Note that FDEM was made for multifrequency EM instruments measuring both in-phase and out phase. So I guess it will not help you here... |
Thanks for the answer Thomas, You don't have, or don't plan on coding V/H data coming form the same instrument? EM35/EM31 and so on? Thank you |
Well, we should just better document. Actually it could be possible to invert those four inphase components for a simple (2-3 layer or smooth) model, but I am not sure whether it is worth investing time before we have restructured the FDEM class(es). Yes, we will include both V and H components as e.g. the RESOLVE system that we use has both (of which the H is still neglected, what a shame). So stay tuned... Feel free to continue discussion in this issue even though I am now closing it as there is no todo right now (and there is a separate FDEM issue). |
Thank you Thomas, Best, e |
Hello,
First of all I'd like to congratulate you about the paper published in Computers in Geoscience, I found it very well explained and very pedagogical examples.
As labelled, my issue is rather a question relative to FDEM dataset.
Let me be clearer.
I have a dataset of 4 EM tools, having different coil spacing, different freqs... it does seem that my only option will be "importMaxminData". Correct?
Thanks for your answer.
best
e
The text was updated successfully, but these errors were encountered: