New package: HTBoost v0.1.0

[JuliaRegistrator]

• Registering package: HTBoost
• Repository: https://github.com/PaoloGiordani/HTBoost.jl
• Created by: @PaoloGiordani
• Version: v0.1.0
• Commit: dd4651428b2aa420ff53a766070256546092a95e
• Git reference: HEAD
• Description: Hytrid Tree Boosting
• Release notes:

Initial release of HTBoost package.

Features:

Refer to paper "Data Efficient Inference via Hybrid Tree Boosting".
Improved accuracy for (partially) smooth functions.
Includes improved accuracy for categorical features and missing values, if the underlying function is (partially) smooth.
Estimation of fixed parameters.
Improved accuracy for sparse structures (only a subset of features relevant).

[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 ❌

• The following dependencies do not have a [compat] entry that is upper-bounded and only includes a finite number of breaking releases: CategoricalArrays, ShiftedArrays

  Extended explanation

  Your package has a Project.toml file which might look something like the following:

  name = "YourPackage"
  uuid = "random id"
  authors = ["Author Names"]
  version = "major.minor"
  
  [deps]
  # Package dependencies
  # ...
  
  [compat]
  # ...

  Every package listed in [deps], along with julia itself, must also be listed under [compat] (if you don't have a [compat] section, make one!). See the Pkg docs for the syntax for compatibility bounds, and this documentation for more on the kinds of compat bounds required for AutoMerge.

• Package name similar to 2 existing packages.

  1. Similar to XGBoost. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  2. Similar to JLBoost. 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.

[PaoloGiordani]

block

[goerz]

I would recommend the package name HybridTreeBoosting

P.S.: There’s a typo in your package description

[PaoloGiordani]

Thank you. I have considered a more descriptive name, but I find it too long for common use. HTBoost (hybrid trees) seems reasonable given XGBoost (extreme gradient) and CatBoost (categorical). Paolo From: Michael Goerz ***@***.***> Sent: tirsdag 18. februar 2025 12:16 To: JuliaRegistries/General ***@***.***> Cc: Giordani, Paolo ***@***.***>; Mention ***@***.***> Subject: Re: [JuliaRegistries/General] New package: HTBoost v0.1.0 (PR #125337) I would recommend the package name HybridTreeBoosting — Reply to this email directly, view it on GitHub<#125337 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AUEOU5LIFRETBBAKELF6BBT2QMI6NAVCNFSM6AAAAABXLFBN3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRVGMZTQOJVG4>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>> [goerz]goerz left a comment (JuliaRegistries/General#125337)<#125337 (comment)> I would recommend the package name HybridTreeBoosting — Reply to this email directly, view it on GitHub<#125337 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AUEOU5LIFRETBBAKELF6BBT2QMI6NAVCNFSM6AAAAABXLFBN3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRVGMZTQOJVG4>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[goerz]

too long for common use

Long package names are very much the norm in the Julia ecosystem. As the guidelines say:

Err on the side of clarity, even if clarity seems long-winded to you.

This is something that’s very particular to Julia and very different from many other languages (C++ and Python in particular). HybridTreeBoosting is actually on the shorter side of Julia package names, but if you need it with a shorter name for local use, there’s always import HybridTreeBoosting as BTBoost.

Both XGBoost and CatBoost are wrappers around non-Julia libraries for which different guidelines are applicable, cf. point 6:

Packages that wrap external libraries or programs can be named after those libraries or programs.

This is not the case for HTBoost, so I don’t think I would be comfortable applying an override for the naming guidelines.