-
Notifications
You must be signed in to change notification settings - Fork 132
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
Challenges with ERT field data import - question #680
Comments
I would always prefer original instrument files as they bear more information (e.g. errors, current and voltage and not just apparent resistivity like in res2dinv). About the SuperSting import, there is an import routine in the pyBERT project (https://gitlab.com/resistivity-net/bert): https://gitlab.com/resistivity-net/bert/-/blob/master/python/pybert/importer/importData.py?ref_type=heads#L1845 |
The problem in your file is the following: the unified BERT/GIMLi format consists of a list of electrodes and then the ABMN columns are just indices into the electrode list, so instead of
you would have
|
I copied the specified 8 lines into a file
with the result
|
Thanks @halbmy. After a break for lunch, I re-read the BERT site and worked out what I had wrong there. And I agree, it's always good to go to the original where possible, but in my script to make my own BERT file, I carried over a few of those extra fields. After fixing the BERT format, and with using pybert for the stg file, both import and seem to work with anything I try, thanks! But maybe it's a separate issue, for both import approaches, I still only get this from print(data):
I don't know that it is critical for other functions, but it's useful to have that list of nonzero fields. |
Can you attach your stg file? |
Here it is (zipped as github rejected the stg file). I've been trying a few more things, and different approaches/inversion settings, and everything seems fine with it practically speaking. |
I realized that pyBERT was overwriting the |
Thanks Thomas - can I pull that update from git or somewhere? I think I installed pybert from an anaconda prompt. |
You don't really need this update if you |
Problem description
I've had some success with ERT import and inversion when I have Res2dInv formatted .dat files, but I'm hoping to be able to use pygimli as an alternative. The current source I have from the field is in .stg files from a Supersting instrument, but import is not working properly, and when I convert to what (to me) looks like the unified data format, import doesn't work at all.
Your environment
Steps to reproduce
The code is probably not very helpful, as the issue is simply with:
However, sample input may be helpful? My attempt at the UDF-ERT looks like this:
and the supersting file looks like this:
Expected behavior
I'm trying to produce a data container that I can use for inversion, but what I'm getting has issues
Actual behavior
From the file that I think is UDF-ERT, I get the following response:
followed by a wave of:
for every line/column combination, and then a wave of hundreds of:
and at the end, there is no data container. Even if this is not proper UDF-ERT, it is clearly ASCII in columns...but doesn't read as that either.
If I try to import the supersting file, I get this response:
and I then have a data container that appears to have the electrode positions and resistivity, but if I do a print(data), I don't get the information about which valid columns are there, and I can't do ert.show(data['??']) for any parameter except rhoa.
The text was updated successfully, but these errors were encountered: