Skip to content

fixes for MTK changes #1186

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

Merged
merged 53 commits into from
Mar 26, 2025
Merged

fixes for MTK changes #1186

merged 53 commits into from
Mar 26, 2025

Conversation

TorkelE
Copy link
Member

@TorkelE TorkelE commented Feb 17, 2025

Updates conservation laws to work with new remake version.

@isaacsas
Copy link
Member

This is probably never going to pass tests with the change in semantics for complete. We can no longer rely on the parameters of a completed system being the same as what was defined when creating the system, which I think a lot of tests rely on.

@isaacsas
Copy link
Member

We can also no longer rely on issetequal(parmeters(sys), get_ps(sys)) for a flattened system.

@TorkelE
Copy link
Member Author

TorkelE commented Feb 18, 2025

Let's see how this turns out. If something like what you suggest is really changing it would be one of the largest changes to Catalyst ever, probably after moving to maps as inputs to problems. Would probably take ages to figure out all the implications.

@isaacsas isaacsas changed the title Check new remake version WIP: fixes for MTK changes Feb 26, 2025
@isaacsas
Copy link
Member

@TorkelE let's just work in this PR to try to get tests working again.

I've handled the conservation law constants getting scalarized issue, and locally gotten tests in reactionsystem.jl working again.

@isaacsas
Copy link
Member

TODO:

  • isequivalent needs more comprehensive testing (perhaps a followup PR)?

@TorkelE
Copy link
Member Author

TorkelE commented Feb 26, 2025

I had some updates locally to sort out the new parameters, but there are quite a few recent MTK issues that are hard-blocking us so I stopped a bit:
SciML/ModelingToolkit.jl#3411
SciML/ModelingToolkit.jl#3410
SciML/ModelingToolkit.jl#3409
SciML/ModelingToolkit.jl#3408
SciML/ModelingToolkit.jl#3396

@isaacsas
Copy link
Member

OK, I'll get as much fixed here as I can modulo those issues and then plan to merge.

FYI, take a look at the changes to isequivalent. The nice feature is I added a debug kwarg that will printout specifically which fields are not the same. (I seem to always want this functionality when writing tests).

@isaacsas
Copy link
Member

@TorkelE everything before conservation laws should now work. I tried various combinations of guesses and missing but couldn’t get them to work. Are you ok if I merge this and we can resume if/when someone figures out how to handle that stuff?

@TorkelE
Copy link
Member Author

TorkelE commented Mar 5, 2025

If we want to merge this I am happy with it. Still quite a way to go to update to the latest everything, but not sure if it is possible yet.

@isaacsas
Copy link
Member

isaacsas commented Mar 5, 2025

No, we can keep this open. But it has a lot of fixes for the MTK changes, so we should just push to this PR as we work on tests going forward...

@TorkelE TorkelE closed this Mar 24, 2025
@TorkelE TorkelE reopened this Mar 24, 2025
@isaacsas
Copy link
Member

With the update to MTK in SciML/ModelingToolkit.jl#3496 tests now pass locally for me, so I think this is good once that is merged and a new MTK release is made.

@isaacsas isaacsas changed the title WIP: fixes for MTK changes fixes for MTK changes Mar 26, 2025
@isaacsas
Copy link
Member

@AayushSabharwal thanks for all your help with the various issues @TorkelE opened. We've finally got tests passing again! If as of now you find our tests start failing during MTK/SciMLBase downstream testing we would very much appreciate a heads up about what changes might be causing such issues and what we need to update.

@isaacsas isaacsas merged commit ba1e715 into master Mar 26, 2025
13 checks passed
@AayushSabharwal
Copy link
Member

Not a problem! Glad to get everything green again. And yeah, I'll make sure to avoid breaking Catalyst CI or at least inform you if I find outdated code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants