Good idea, same goes for @clamadvi and @luc recent thread since Python users cannot use the develop branch as easily as Java users.
I’m not sure either. I haven’t seen much difference between two different configurations even when the tides are properly loaded in different data contexts.
Yes, sorry about that. One way I made it work in my test is by using different DataContext for the different tide models.
You can try this to avoid the problem.
And make sure to use the OceanTides constructor that doesn’t use the default data context (i.e. the one with the last argument being GravityFields)