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

[WIP] Ensemble #620

Closed
wants to merge 4 commits into from
Closed

[WIP] Ensemble #620

wants to merge 4 commits into from

Conversation

Vaibhavdixit02
Copy link
Member

No description provided.

@codecov
Copy link

codecov bot commented Oct 27, 2023

Codecov Report

Merging #620 (9daba63) into master (461d002) will increase coverage by 5.39%.
The diff coverage is 0.00%.

@@            Coverage Diff            @@
##           master    #620      +/-   ##
=========================================
+ Coverage    2.85%   8.25%   +5.39%     
=========================================
  Files          40      41       +1     
  Lines        2694    2714      +20     
=========================================
+ Hits           77     224     +147     
+ Misses       2617    2490     -127     
Files Coverage Δ
src/Optimization.jl 37.03% <ø> (ø)
src/ensemble.jl 0.00% <0.00%> (ø)

... and 7 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

src/ensemble.jl Outdated Show resolved Hide resolved
src/ensemble.jl Outdated
end

function SciMLBase.__solve(caches::Vector{OptimizationCache}, args...; kwargs...)
function SciMLBase.__init(prob::EnsembleProblem{T}, args...; trajectories, kwargs...) where {T <: OptimizationProblem}
Copy link
Member

Choose a reason for hiding this comment

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

this is missing all of the ensemblealgs.

@@ -3,6 +3,16 @@ function SciMLBase.EnsembleProblem(prob::OptimizationProblem, u0s::Vector{Vector
return SciMLBase.EnsembleProblem(prob; prob_func, kwargs...)
end

function SciMLBase.EnsembleProblem(prob::OptimizationProblem, trajectories::Int; kwargs...)
Copy link
Member

Choose a reason for hiding this comment

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

I'd just keep to the interface. This doesn't seem like a necessary shorthand to me.

Copy link
Member Author

Choose a reason for hiding this comment

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

I'd like to provide an automated way of doing the solves with initial points sampled, it would be useful. I can probably do it another way if you are opposed to this, but do note that the other dispatch is already not conforming fully with the current interface of creating these problems

Copy link
Member

Choose a reason for hiding this comment

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

it would be good to come up with such a shorthand at a higher level of the interface, since NonlinearProblem, NonlinearLeastSquaresProblem, etc. would want to do similar things.

@Vaibhavdixit02
Copy link
Member Author

superseeded by SciML/SciMLBase.jl#538

@Vaibhavdixit02 Vaibhavdixit02 deleted the ensemble branch November 8, 2023 03:18
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.

2 participants