-
Notifications
You must be signed in to change notification settings - Fork 12
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
age-gridding gaps #182
Comments
Investigation is in process. Set to "medium" priority. Let me know if "high" priority is needed. |
Customer mentioned "the 1 Ga model". Need to confirm with customer which model exactly is mentioned here. |
I had sent an email to customer to clarify the meaning of "the 1 Ga model". Waiting for customer's response. |
I have put the intermediate files at https://repo.gplates.org/webdav/mchin/test-agegrid-output-20240613/. The model being used is merdith2021. sample_points/: sea floor seed points in both .gpmlz and .pkl format You may use macOS "Finder" to copy the files (login as Guest). Alternatively, you may use CyberDuck with "webdav" protocol to download the files. You may open the .gpmlz file in GPlates and colour the points by "FeatureAge". |
Investigation is still in progress. Need to find out why there are no "seed points" in certain areas. |
Thanks for putting that all together. I see what you mean now! The seed point GPML files are very large and slow (as you mentioned in the last meeting). Here’s a better way to do this – as done in the original isopolate - and should help a lot… Instead of saving as individual points you can save as a multipoint coverage. Basically, each point gets one or more scalar values – such as age, spreading rate, direction, obliquity, etc. But it’s all compactly stored in the GPML file – so it’s much smaller and loads faster. In isopolate, you can see how it’s done here (where this function shows how the age, spreading rate, direction, obliquity, etc, are added). This ultimately hinges around pygplates.Feature.set_geometry() (see the bottom example in that function). The following screenshot shows some old isopolate output (it’s actually lines instead of multipoints, but it’s the same idea, each point gets a different colour). And it’s easy to switch between the different output types (eg, age, spreading obliquity, etc) and colour each output type with a different palette. This is in grey layers (that aren’t commonly seen in GPlates). Also, if you could set the feature time-period on each GPML to [time+0.5, time-0.5] that would be great! Because it means we can load all the GPMLs at once and animate the time slider - and only one GPML will be visible at a time. That allows us to more easily animate the seed points to see where they go over time. Currently, when you animate the slider you also have to disable some layers at later times so they don’t overlap the current time. |
The seed points come from two sources. One is the initial oceanic points and the other is the middle ocean ridges. So either the old seed points move into the gap or the middle ocean ridges generate the new points, otherwise the gap is inevitable. |
Still no response from customer. Assume "the 1 Ga model" means any models which go back to 1000Ma, such as merdith2021, unless the customer says otherwise. |
Thanks for making those changes! Much easier to view now. I agree with your assessment. It appears the ocean plate is moving away from the continent. Which leaves a gap that cannot be captured by the seed points (for the reasons you stated). I guess that’s where the interpolation ideas bounced around in recent meetings (a separate concept than seed point reconstruction) might need to come into play. Just a minor point: in future if you add more than just seafloor ages to the sample points (eg, spreading rate/obliquity/etc) then it might be easier to view if all sample points are in a single file – only because with hundreds of file/layers (ie, one per time step) you’d have to go into each layer and select spreading rate, for example, if you wanted to switch from viewing seafloor age to spreading rate. And if that single file is too big then could always have one file every 100Myr or so, for example. |
yes, it is a good idea. |
@jcannon-gplates I tried to recall what decision had been made in the auscope meeting on 2 July, 2024, but my memory failed me again. Did we conclude anything in the meeting regarding this age gridding gaps? |
My memory is a bit sketchy on that too ;-) I think Dietmar mentioned just continuing with the changes that makes it easier to view for now, such as:
...then others might look into the gaps further. |
Then there's the issue of how to actually fill the gaps in the age-gridding. Sabin noted that the gap in this particular issue is an error in the model (ie, ocean crust wasn't subducting but instead going in reverse direction), and would need to be fixed in the model itself. For a general solution, I suggested we could add seed points in the gaps (assuming that once a model is fixed that you'd still have gaps here and there). So that could involve:
So yeah, just some random thoughts I mentioned in the meeting. But I think we'd all need to really discuss this again in future meeting before doing any work on a general solution. |
Thanks John. |
Here is an example of the gaps in the age-gridding process using the 1 Ga model.
![Screenshot 2024-06-04 at 4 43 51 PM](https://private-user-images.githubusercontent.com/2688316/336351047-7350074a-8ac4-4f4e-be7e-e3e7cdb78121.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQwMDE3MDYsIm5iZiI6MTcyNDAwMTQwNiwicGF0aCI6Ii8yNjg4MzE2LzMzNjM1MTA0Ny03MzUwMDc0YS04YWM0LTRmNGUtYmU3ZS1lM2U3Y2RiNzgxMjEucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgxOCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MThUMTcxNjQ2WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YTE2NDk2NzNhZTk1NDQ1OTQ5YjBkYWUwNzUwMzYxMTUwMjc5MmQ4MzBmYjA3ZTI2YzNjODNlOGNjYzg4NzJkNyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.XRbiSyHn6VIr-imG6QhCmbO8O5K-IyD_8s1Ln11Foa0)
The text was updated successfully, but these errors were encountered: