You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Documentation for the MULLER2019 model has been updated on GPlates Web Service stating that the MULLER2019 model covers 0--250 Ma (as the paper also states). However, the API service allows points to be reconstructed up to 540 Ma for this model. A little digging required...
This should be addressed for v1.1.1.
As a side note, the MULLER2022 model is also now available and perhaps should be incorporated down the line.
The text was updated successfully, but these errors were encountered:
Sounds weird yes, and I don't feel like MUL19 and MUL22 are not returning the same results for the given a present-day point... We should probably put an artificial constraint on the rotation age using MUL19, and definitely include the MUL22 for the v.1.1.1!!
I can maybe try to get in touch with Sabin to know what's going on here.
MUL19 and MUL22 are using different continental polygons, so this would explain some differences. However, I agree that we should constrain MUL19 to 250 Ma as this is the intended time span of the model. Yes, please touch base with Sabin to find out why this is. It's possible that there is a bug on their end and it is calling the wrong model when using the API, or... MUL19 uses a different model past 250 Ma. Note, the API seems to have slowed down a lot as well in the past week. Might be worth asking about that too...
Documentation for the MULLER2019 model has been updated on GPlates Web Service stating that the MULLER2019 model covers 0--250 Ma (as the paper also states). However, the API service allows points to be reconstructed up to 540 Ma for this model. A little digging required...
This should be addressed for v1.1.1.
As a side note, the MULLER2022 model is also now available and perhaps should be incorporated down the line.
The text was updated successfully, but these errors were encountered: