-
Notifications
You must be signed in to change notification settings - Fork 470
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
New package: Fminbnd v1.0.0 #119764
New package: Fminbnd v1.0.0 #119764
Conversation
JuliaRegistrator
commented
Nov 19, 2024
•
edited
Loading
edited
- Registering package: Fminbnd
- Repository: https://github.com/kagalenko-m-b/Fminbnd.jl
- Created by: @kagalenko-m-b
- Version: v1.0.0
- Commit: 976e4f3a3383a67e92e52286508e5819f8960f62
- Reviewed by: @kagalenko-m-b
- Reference: kagalenko-m-b/Fminbnd.jl@976e4f3#commitcomment-149775975
Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human. 1. New package registrationPlease make sure that you have read the package naming guidelines. 2. AutoMerge Guidelines are all met! ✅Your new package registration met all of the guidelines for auto-merging and is scheduled to be merged when the mandatory waiting period (3 days) has elapsed. 3. To pause or stop registrationIf you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text Tip: You can edit blocking comments to add |
This seems to be the followup from #99531. I'm not really clear on what the |
I might tentatively suggest |
I'd also strongly recommend leaving the name of the function exported by the package as |
There’re widely used matlab/octave functions ‘fminbnd’ and python’s ‘fminbound’ that also derive from netlib’s fmin. “Bnd” means that it searches minimum on a bounded interval. |
Hmm… okay, but you're very explicitly translating the Netlib code, which doesn't use that name 🤷 What I mean is: it very much seems like the name was chosen because it passes the automated name check, not because it's the most appropriate name for the package. But, I feel like a package name that indicates that this is the exact |
No. The name was chosen because matlab’s “fminbnd” is better known than netlib’s “fmin”. |
Then you should rewrite the |
I would also point out that your signature does not match the Matlab |
d22c7c1
to
9dc67ea
Compare
[noblock] Same Brent's method seems to be available in Optim.jl, see https://julianlsolvers.github.io/Optim.jl/stable/user/minimization/#Minimizing-a-univariate-function-on-a-bounded-interval |
Optim is a very large and complex package with many dependencies. For simple problems it may be desirable to have a standalone alternative. |
rule 8 of package naming guidelines:
also rule 4
I think naming aside, and I'm sorry to be too critical, but I would be a bit hesitant to say that this meets the quality standards to register in General in the first place. This package consists of a single function that is completely illegible. Could you at least try to factor out some of the |
I wouldn't come down quite as hard on this. I think if it implemented the same interface as Matlab and was documented as such (instead of a translation of the Netlib code), I'd be totally fine with Likewise, the way it is implemented now,
With the direct reference to Netlib, it's kinda cute, and I don't think I'd mind. This is really as close of a translation of the original code as possible. It would be interesting to also write this with modern (haha) control flows and benchmark if there is any difference at all in performance. |
Different implementation of the same algorithm is “unrelated”? |
|
Okay, that seems good to me… Just make sure that you retrigger the registration to really make sure that the correct commit gets tagged. Especially since you're using |
UUID: b7bab496-830c-4b53-8aec-8b9a988c40b4 Repo: https://github.com/kagalenko-m-b/Fminbnd.jl.git Tree: f806e59cf762df964f7e91c082523d8e61e4c4f3 Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a
9dc67ea
to
0f14ab3
Compare
…lia-actions/setup-julia-2 Bump julia-actions/setup-julia from 1 to 2
Let me know when this is good to go, and I’ll apply the override to merge it |
I believe it’s as ready as it’ll ever be. Not added the tag yet, but the comment from registrar states that it should be done automatically via tagbot after the package registration. |
Yes, do not create tags to create releases. Releases have to be registered first and then tagged afterwards (preferably via the bot) |
Looks like tagbot triggered automatically, thanks. |