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 tests failings for TwoPointBVPFunction #517

Closed
wants to merge 1 commit into from

Conversation

ErikQQY
Copy link
Member

@ErikQQY ErikQQY commented Oct 1, 2023

This should fix the tests failings in DiffEqBase.jl SciML/DiffEqBase.jl#940

@ChrisRackauckas @avik-pal

@codecov
Copy link

codecov bot commented Oct 1, 2023

Codecov Report

Merging #517 (25b27be) into master (75b1925) will increase coverage by 2.93%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master     #517      +/-   ##
==========================================
+ Coverage   53.37%   56.30%   +2.93%     
==========================================
  Files          50       50              
  Lines        3798     3806       +8     
==========================================
+ Hits         2027     2143     +116     
+ Misses       1771     1663     -108     
Files Coverage Δ
src/remake.jl 58.01% <83.33%> (+4.41%) ⬆️
src/problems/bvp_problems.jl 44.82% <55.55%> (+6.89%) ⬆️

... and 11 files with indirect coverage changes

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

@@ -119,25 +119,25 @@ struct BVProblem{uType, tType, isinplace, P, F, BF, PT, K} <:
else
@assert prob_type === problem_type "This indicates incorrect problem type specification! Users should never pass in `problem_type` kwarg, this exists exclusively for internal use."
end
return new{typeof(u0), typeof(_tspan), iip, typeof(p), typeof(f), typeof(bc),
typeof(problem_type), typeof(kwargs)}(f, bc, u0, _tspan, p, problem_type,
return new{typeof(u0), typeof(_tspan), iip, typeof(p), typeof(f), typeof(f.bc),
Copy link
Member

Choose a reason for hiding this comment

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

Why is the bc out here at all? Isn't it in the BVPFunction?

Copy link
Member

Choose a reason for hiding this comment

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

@avik-pal is it actually needed?

Copy link
Member

Choose a reason for hiding this comment

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

The bc was kept outside similar to the SDEProblem interface carrying around the g outside (I think?)

Copy link
Member

Choose a reason for hiding this comment

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

That was just fixed in the v2.0. I thought this was fixed in the v2.0 as well 😅. Fix and slip it in ASAP.

Copy link
Member Author

Choose a reason for hiding this comment

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

The modifications in BVProblem is similiar to SDEProblem, just try to make them consistent

Copy link
Member

Choose a reason for hiding this comment

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

SDEProblem is still carrying around g

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah, SDEProblem is still carrying g, so in this way I think we can still use prob.g to directly access g

Copy link
Member Author

Choose a reason for hiding this comment

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

Do we need to remove g in the problem struct?

@ChrisRackauckas
Copy link
Member

@avik-pal is this still needed after #518 ?

@ErikQQY ErikQQY mentioned this pull request Oct 7, 2023
3 tasks
@ChrisRackauckas
Copy link
Member

This PR is now out of date because of the changes in #518, so closing, but a similar PR to the new function form is required.

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