Skip to content
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

fix: use SII instead of explicitly accessing SciMLFunction.syms #626

Merged
merged 1 commit into from
Dec 14, 2023

Conversation

AayushSabharwal
Copy link
Member

No description provided.

@@ -51,6 +52,7 @@ ProgressLogging = "0.1"
Reexport = "0.2, 1.0"
Requires = "1.0"
SciMLBase = "1.79.0, 2"
SymbolicIndexingInterface = "0.3"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to not get resolved

Copy link
Member Author

@AayushSabharwal AayushSabharwal Nov 16, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not released yet
SciML/SymbolicIndexingInterface.jl#12

The changes here are due to SciML/SciMLBase.jl#532

Copy link

codecov bot commented Dec 13, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (8d53748) 0.11% compared to head (50e1e9e) 0.00%.
Report is 2 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##           master    #626      +/-   ##
=========================================
- Coverage    0.11%   0.00%   -0.12%     
=========================================
  Files          40      12      -28     
  Lines        2689    1141    -1548     
=========================================
- Hits            3       0       -3     
+ Misses       2686    1141    -1545     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@ChrisRackauckas
Copy link
Member

Did this work locally with the other pieces checked out?

@AayushSabharwal
Copy link
Member Author

AayushSabharwal commented Dec 13, 2023

I haven't tested it yet. There are more libraries that need a bump, but it looks like for some reason it can't pull in 0.14 Flux during tests which caps CUDA at 4, whereas LinearSolve needs 5.

EDIT: it seems test/Project.toml caps Flux at 0.13. My guess is that before this change, Optimization could pull in an older version of LinearSolve compatible with CUDA 4. Now it needs the latest LinearSolve, but can't pull in latest Flux.

@AayushSabharwal
Copy link
Member Author

ERROR: LoadError: Unsatisfiable requirements detected for package SparseArrays [2f01184e]:
 SparseArrays [2f01184e] log:
 ├─possible versions are: 0.0.0 or uninstalled (package in sysimage!)
 ├─restricted to versions 1.9.0-1 by OrdinaryDiffEq [1dea7af3] — no versions left
 │ └─OrdinaryDiffEq [1dea7af3] log:
 │   ├─possible versions are: 6.61.0 or uninstalled
 │   ├─restricted to versions 6.19.1-6 by SciMLSensitivity [1ed8b502], leaving only versions: 6.61.0
 │   │ └─SciMLSensitivity [1ed8b502] log:
 │   │   ├─possible versions are: 7.47.0 or uninstalled
 │   │   └─SciMLSensitivity [1ed8b502] is fixed to version 7.47.0
 │   └─OrdinaryDiffEq [1dea7af3] is fixed to version 6.61.0
 └─SparseArrays [2f01184e] is fixed to version 0.0.0

I don't even know what to make of this

@AayushSabharwal
Copy link
Member Author

This passes if Flux compat is bumped and 1.10 is used

@@ -61,6 +62,7 @@ ReverseDiff = "1"
SciMLBase = "1.79.0, 2"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't this need to be bumped?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why would it? Nothing in Optimization changed that prevents it from being compatible with previous versions of SciMLBase.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh I thought the RAT v3 or SII v0.3 changes would require it, but if that back compatibility is kept then we're good.

@ChrisRackauckas
Copy link
Member

Merging to unblock others.

@ChrisRackauckas ChrisRackauckas merged commit 5c01e51 into SciML:master Dec 14, 2023
6 of 26 checks passed
@@ -85,7 +85,7 @@ function SciMLBase.get_syms(sol::SciMLBase.OptimizationSolution{
C <:
MOIOptimizationNLPCache,
}
sol.cache.evaluator.f.syms
variable_symbols(sol.cache.evaluator.f)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't OptimizationMOI need its Project.toml updated?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bump on this.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I didn't realize. Thanks. I'll push these changes to the rerun CI PR

@Vaibhavdixit02
Copy link
Member

@AayushSabharwal
Copy link
Member Author

AayushSabharwal commented Dec 15, 2023

Yeah it won't pass until MTK is tagged. I ran it locally and tests pass.

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.

3 participants