New package: MCPSolver v0.1.0

[JuliaRegistrator]

• Registering package: MCPSolver
• Repository: https://github.com/CLeARoboticsLab/MCPSolver.jl
• Created by: @dfridovi
• Version: v0.1.0
• Commit: e4d82f24d615bbbf69f77c434881f39f77901503
• Reviewed by: @dfridovi
• Reference: Register as new Julia package CLeARoboticsLab/MixedComplementarityProblems.jl#6
• Description: A custom interior point solver for mixed complementarity problems.

[gdalle]

Hi, congrats on the package! Since the acronym is not standard, can I suggest the name MixedComplementarityProblems.jl?

[dfridovi]

If possible, I'd like to keep it with the MCP acronym for two reasons. First, my sense is that this is one of two standard acronyms in the OR community for these problems (the other being MiCP) - cf. the textbook from Facchinei and Pang here. Second, I am basing this package off of ParametricMCPs, and the naming scheme should probably be consistent. Thoughts?

[github-actions]

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 registration

Please make sure that you have read the package naming guidelines.

2. AutoMerge Guidelines which are not met ❌

• There is no compat entry for julia.
• Package name similar to 2 existing packages.
  1. Similar to DCISolver. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  2. Similar to MPSolve. Damerau-Levenshtein distance 2 is at or below cutoff of 2.

3. Needs action: here's what to do next

1. Please try to update your package to conform to these guidelines. The General registry's README has an FAQ that can help figure out how to do so.
2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless the AutoMerge issue is that you skipped a version number).

If you need help fixing the AutoMerge issues, or want your pull request to be manually merged instead, please post a comment explaining what you need help with or why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the public Julia Slack for better visibility.

4. To pause or stop registration

If 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 [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

[gdalle]

I understand your concerns.

First, my sense is that this is one of two standard acronyms in the OR community for these problems

The reason behind my suggestion is that acronyms like this are only standard in one specific community, in this case OR. I also belong to that community and the acronym wasn't even obvious to me. It is never hurtful to have a longer package name. For instance, I developped a package called HiddenMarkovModels.jl and I didn't call it HMM.jl even though the abbreviation is pretty standard too. The only spelled out word in your package name is "Solver", and it is a pretty generic one.

Second, I am basing this package off of ParametricMCPs, and the naming scheme should probably be consistent.

That is a more valid reason, although I would also have objected to the registration of ParametricMCPs.jl for the same reasons.

[dfridovi]

Fair enough. I'll change it to something like MixedComplementarityProblems.jl per your initial suggestion.

[dfridovi]

Ok package is renamed as requested.

[gdalle]

Thanks!

[goerz]

Closing in favor of #120277