New package: BPM v3.0.0

[JuliaRegistrator]

• Registering package: BPM
• Repository: https://github.com/byuflowlab/BPM.jl
• Created by: @tylercritchfield
• Version: v3.0.0
• Commit: 75f8d392dd0f5599346807ada64d619fe9e3b255
• Reviewed by: @tylercritchfield
• Reference: byuflowlab/BPM.jl@75f8d39#commitcomment-180014993
• Description: A semi-empirical code for modeling the acoustics of propellers and turbines

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

• Name does not meet all of the following: starts with an upper-case letter, ASCII alphanumerics only, not all letters are upper-case.

• Name is not at least 5 characters long

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

  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 16 existing packages.

  Similar package names

  1. Similar to SPH. Damerau-Levenshtein distance 2 is at or below cutoff of 2. Normalized visual distance 1.48 is at or below cutoff of 2.50.
  2. Similar to SOM. Damerau-Levenshtein distance 2 is at or below cutoff of 2. Normalized visual distance 2.44 is at or below cutoff of 2.50.
  3. Similar to SMM. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  4. Similar to QSM. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  5. Similar to FDM. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  6. Similar to BED. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  7. Similar to GLM. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  8. Similar to BDF. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  9. Similar to XPA. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  10. Similar to NPZ. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  11. Similar to XAM. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  12. Similar to BBI. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  13. Similar to MPI. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  14. Similar to Bio. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  15. Similar to BAT. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  16. Similar to PPLM. 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.

[tylercritchfield]

I've fixed the compat issue, but now I would like to request a manual review of this package. The name BPM.jl has been used for several years now internally in our organization and by others using the code, so changing it would be inconvenient. It is also an acronym for three names: Brooks, Pope, and Marcolini, so it doesn't make sense to make any of the letters lowercase. This code runs a specific analysis developed by those three and is commonly referred to as the BPM method. While it is similar to other packages listed above which are also acronymns, it shouldn't get confused with any of them as anyone using this package will know the method as the BPM method already.

[goerz]

There is an extremely strong consensus that we're not merging 3-letter acronyms anymore. So, unfortunately, there is no way to have this package registered in the General registry without renaming it to something that meets the naming guidelines. If you think that the BPM acronym is extremely recognizable to your target audience, then it might be possible to keep it as part of the the package name; but it would have to be paired with a more explanatory suffix or prefix. Although I would also point out that "BPM" is very commonly understood to be "beats per minute". So something like AcousticBPM might actually be quite misleading. I'm not sure I have a specific suggestion for a great package name for you.