Skip to content
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

Questions regarding the Res2dInv export format #692

Closed
IsabellaLorenzen opened this issue Apr 3, 2024 · 1 comment
Closed

Questions regarding the Res2dInv export format #692

IsabellaLorenzen opened this issue Apr 3, 2024 · 1 comment

Comments

@IsabellaLorenzen
Copy link

Problem description

In my original res2dinv .dat file i had 9 IP-windows, but after filtering and exporting the .dat file using the exportRes2dInv(filtered_data, file_location) command, i only have 1 IP-window.

Also it is exported as a mixed array, is this different than my original multigradient array when i invert it?

If the number of IP-windows and array type influence the inversion, is it possible to specify IP-windows and array type during the export?

In the pictures below you can see the header for the original .dat file and the exported .dat file respectivly. (The data in the first picture continues horisontally with more IP-windows).
image
image

If possible, please add one or more labels to your issue, e.g. if you expect that your issue is rather a question than a problem with the code, please add the label "question".

@IsabellaLorenzen IsabellaLorenzen changed the title Question re the Res2dInv export format Questions regarding the Res2dInv export format Apr 3, 2024
@halbmy
Copy link
Contributor

halbmy commented Apr 3, 2024

As the exportRes2dInv function is part of the pyBERT module, please raise an issue here: https://gitlab.com/resistivity-net/bert
Therefore I am closing it.

The code seems not to support multiple windows yet and I will not find time and motivation to fix this (and I cannot test it as I am not using res2dinv). But I encourage you to have a look into that function, extend it and give it back to the community by providing the code.

@halbmy halbmy closed this as completed Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants