Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Add S kwarg toopRestriction#324

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
dpo merged 1 commit intoJuliaSmoothOptimizers:mainfromnHackel:addSRestriction
Apr 20, 2024

Conversation

@nHackel
Copy link
Contributor

This PR adds theS keyword to theopRestriction constructor. Thisfixes#323.

Since the operator has no type information of the storage type for a default cause ofS = Vector{T} as other operators ahve, I've opted to give him a default of nothing. IfS is nothing the normal operator is called, which will have a storage type ofVector{Int64}.

I did not add aopRestriction(...; kwargs...) for the constructors which fall back on other operators, since at a quick glance I didn't see such a pattern used in this package.

@github-actions
Copy link
Contributor

Package namelateststable
CaNNOLeS.jl
DCISolver.jl
FletcherPenaltySolver.jl
JSOSolvers.jl
Krylov.jl
NLPModels.jl
NLPModelsModifiers.jl
PROPACK.jl
Percival.jl
QuadraticModels.jl
SolverTools.jl

Copy link
Member

@geoffroylecontegeoffroyleconte left a comment

Choose a reason for hiding this comment

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

Thank you!

Copy link
Member

@dpodpo left a comment

Choose a reason for hiding this comment

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

This looks good, thank you!

For my own information, what shouldS be in your example in#323?

@dpodpo merged commitee2af5b intoJuliaSmoothOptimizers:mainApr 20, 2024
@nHackel
Copy link
ContributorAuthor

@dpo in that case it should have been aCuArray{Float32, 1, CUDA.Mem.DeviceBuffer}. The last parameter seems to describe the "memory"-type of the array and it might change in future version of CUDA if I understood their Docs/plans correctly

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@dpodpodpo approved these changes

@geoffroylecontegeoffroylecontegeoffroyleconte approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

MissingS keyword foropRestriction

3 participants

@nHackel@dpo@geoffroyleconte

[8]ページ先頭

©2009-2025 Movatter.jp