-
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
Only resolve rigid plates when getting ridges and transforms #224
Comments
I found some side effects to plot_all_topologies() function after d7919a7 Before, the plot_all_topologies() plot boundaries + networks. After the change, the plot_all_topologies() plot boundaries only. In GPlately, the resolve topologies code is here Lines 445 to 459 in a29e3ae
Shall I make another call to pygplates.resolve_topologies() without the new parameter for self.topologies? Any other better ideas? ![]() ![]() |
Those points seem to live in Australia_Antarctica_Mesh_Topologies.gpml As a test, I would just open that GPML and turn the MORs into gpml:UnclassifiedFeature |
Yeah it sounds like Sabin's comment (in email) about changing lines from MOR to something else is the way to go. And his comment...
...hopefully doesn't affect us, but I think it depends on the model (ie, how the topological plates/networks were created). It might be that those points (he mentions) belong to topological lines (which would, in turn, have been added to topological plates/networks). If so, then as long as the topological lines are not labelled MOR then hopefully it should be OK - I think the points (that the topo lines reference, ie, join together into a line) don't need to be re-labelled. But if the points were directly added to the topological plates/networks (without an intermediate topological line) then it could still be an issue. |
todo: plot velocities |
@jcannon-gplates Do you still need me to plot the velocities on the ridges and transforms maps? DM told me that you are going to take care the ridges and transforms thing and asked me to switch to other tasks. By the way, the code for plotting maps and creating videos is here. |
No thanks. I had thought there might be a bug in the current ridge-transform separation algorithm, but DM said that it's an "inconsistency between the way plate boundaries are drawn and labelled and their correspondence to associated plate velocities. These inconsistences are minimal for post 200 ma times, but increase back in time".
Yes I'll start with that in pyGPlates (adding divergence/convergence along all plate boundaries) and then I'll return to use it in the ridge-transform separation in PTT. The new approach will be better suited to deal with those model inconsistencies in deep time. |
only resolve rigid plates by adding the parameter “resolve_topology_types=pygplates.ResolveTopologyType.boundary” to the pygplates.resolve_topologies() function
The COBs should not be there
The text was updated successfully, but these errors were encountered: