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
Bedding point automation? #79
Comments
What do you mean by bedding point automation? |
Approximate from other data layers...as generally nowhere will have that field data recorded. |
Oh I understand. In my opinion, it would make more sense to integrate other datasets into implicit modelling and then get the bedding/orientation data from that. What type of datasets are you looking to use? |
Any we can access that will routinely cover whole states (or can be made to). |
We'd have to see how the particular dataset would be used by a geologist to estimate the bedding orientation. It would be different for different datasets. We already use the DEM and the interpreted geology which are usually available everywhere. This is enough information to make a starting model (provided there is enough resolution in the map to show different stratigraphic units to model). |
Ok - I haven't looked at this for a while - does this mean it has been changed to not fail - and produce a basic model if no bedding data exists at all in the particular area selected? |
I don't know if map2loop will fail if there is no bedding data, but I think it might @markjessell probably be able to help with that. I am just thinking about how to do it conceptually. I'm not sure how many use cases there are for it - I think the results would be very uncertain but it depends on what you are going to do with the point estimates. |
Yes, would be but I think the writeups on these things pretty much say that already. Basically, pick a point, build a basic 3D model to throw in a project. Exploration projects are also highly uncertain, so that doesn't matter either, in that sense. e.g. a geologist asks me if they can use map2loop [which has happened several times as they come across it] - I say 'no, not without fieldwork giving you this info'. Which will never be done, generally speaking, so will never be used, apart from if it happens to intersect on an extreme longshot one of the tiny areas it exists already. |
Conceptually, yes - that is the trick - I think there might be some planetary science ideas perhaps that might be useful. |
At the moment map2loop is hardwired to require at least 2 or 3 bedding measurements, but if you were willing to accept a model where, for example, all contacts were assumed to be dipping at 45 degrees, I could bypass this. I’ll have a go when Xmas meeting season dies down and see what that gives.
Mark Jessell
Professor/ Western Australian Fellow
Centre for Exploration Targeting/ SES • M006, Perth WA 6009 Australia
T +61 8 6488 5803 • E ***@***.***
…________________________________
From: RichardScottOZ ***@***.***>
Sent: Monday, November 8, 2021 7:15:55 AM
To: Loop3D/map2loop-2 ***@***.***>
Cc: Mark Jessell ***@***.***>; Mention ***@***.***>
Subject: Re: [Loop3D/map2loop-2] Bedding point automation? (Issue #79)
Conceptually, yes - that is the trick - I think there might be some planetary science tricks perhaps that might be useful.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FLoop3D%2Fmap2loop-2%2Fissues%2F79%23issuecomment-962699595&data=04%7C01%7Cmark.jessell%40uwa.edu.au%7C49c742876b53428ec9f608d9a2448ea1%7C05894af0cb2846d8871674cdb46e2226%7C0%7C0%7C637719237603715966%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=LXPR2kTwCZc%2FPSB%2F%2Bm%2BAla2oB6A9Rd2tmTb7IRPqHq4%3D&reserved=0>, or unsubscribe<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABUBSYDTVA3HR4JJDJDWKD3UK4CCXANCNFSM5HQBZKKA&data=04%7C01%7Cmark.jessell%40uwa.edu.au%7C49c742876b53428ec9f608d9a2448ea1%7C05894af0cb2846d8871674cdb46e2226%7C0%7C0%7C637719237603725964%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=FgvPwDow9rEfZ2XFu3cfEX7yR%2FVIwIDTMUtXb5rj2Xw%3D&reserved=0>.
|
Mark, Thanks - yes, maybe an option for this to toggle? Whatever you think would suit here in your professional opinion as a generic choice. That would be great. Also be happy to try and work something out to run many of them on AWS or something if you wanted to try many different numbers. I need to talk to some people about what they think re: calculations of such from other things. |
Ok. Shouldn’t be too hard to modify the code, just need some quiet time. Would also be curious to get your take on the tomofastx code.
Mark Jessell
Professor/ Western Australian Fellow
Centre for Exploration Targeting/ SES • M006, Perth WA 6009 Australia
T +61 8 6488 5803 • E ***@***.***
…________________________________
From: RichardScottOZ ***@***.***>
Sent: Monday, November 8, 2021 7:47:03 AM
To: Loop3D/map2loop-2 ***@***.***>
Cc: Mark Jessell ***@***.***>; Mention ***@***.***>
Subject: Re: [Loop3D/map2loop-2] Bedding point automation? (Issue #79)
Mark,
Thanks - yes, maybe an option for this to toggle? Whatever you think would suit here in your professional opinion as a generic choice. That would be great.
Also be happy to try and work something out to run many of them on AWS or something if you wanted to try many different numbers.
I need to talk to some people about what they think re: calculations of such from other things.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FLoop3D%2Fmap2loop-2%2Fissues%2F79%23issuecomment-962704583&data=04%7C01%7Cmark.jessell%40uwa.edu.au%7Cf684fc759c374fd50fee08d9a248e7b0%7C05894af0cb2846d8871674cdb46e2226%7C0%7C0%7C637719256282455618%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=iiFlYwAgRBeREosko44VxxovDDcBTqNxd5lYOLDR3dM%3D&reserved=0>, or unsubscribe<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABUBSYCXMCGCOCBVBH34BS3UK4FXPANCNFSM5HQBZKKA&data=04%7C01%7Cmark.jessell%40uwa.edu.au%7Cf684fc759c374fd50fee08d9a248e7b0%7C05894af0cb2846d8871674cdb46e2226%7C0%7C0%7C637719256282455618%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=rhgBSG8lV2Okz0P2ufyUD%2FY6y8we9R47moWpSBot3HM%3D&reserved=0>.
|
This? https://github.com/TOMOFAST/Tomofast-x Had not seen that one, so thanks. Was talking to someone Friday re: doing that sort of things with point inversions. I'd say the 'run on laptops' would have some caveats re: Windows given the gcc and mpi declarations. I can give it a shot though. |
Yeah - would probably try on an EC2 machine first, see how that goes. |
The example ran on a compute heavy machine (non parallel) in seconds, anyway. This one: Parfile_mansf_slice_wavelet.txt |
Did you manage to get to automagic bedding @markjessell ? |
Speaking of various students, anyone have anything clever here? |
Anyone tinkering here?
One of the geos expressed interest and I said can automatically make project models.... but only if we have this part.
The text was updated successfully, but these errors were encountered: