Skip to content

New package: RINEX v0.1.0#161767

Closed
JuliaRegistrator wants to merge 1 commit into
masterfrom
registrator-rinex-28565f2c-v0.1.0-7967a2e59f
Closed

New package: RINEX v0.1.0#161767
JuliaRegistrator wants to merge 1 commit into
masterfrom
registrator-rinex-28565f2c-v0.1.0-7967a2e59f

Conversation

@JuliaRegistrator

Copy link
Copy Markdown
Contributor

UUID: 28565f2c-cea1-4611-871d-1d57561f65b6
Repo: https://github.com/JuliaGNSS/RINEX.jl.git
Tree: 0b16c669fc235dd37b75eacbc26f20735b259eb0

Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3
@github-actions

Copy link
Copy Markdown
Contributor

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.

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.

@giove-a

giove-a commented Jul 19, 2026

Copy link
Copy Markdown

[noblock] This package is named after RINEX (Receiver Independent Exchange Format), the standard GNSS data interchange format defined by the IGS (https://igs.org/wg/rinex/). The all-caps spelling is the canonical and only spelling of the format name used in the GNSS field — a mixed-case "Rinex" would be unfamiliar to the target audience. The package implements a writer for RINEX 3.05 observation and navigation files.

Registered precedents for standard format/protocol acronyms include NMEA.jl, FITSIO.jl, SBML.jl, and OSQP.jl. We would therefore like to ask for a manual review and merge with the name kept as RINEX.jl. Thank you!

@goerz

goerz commented Jul 19, 2026

Copy link
Copy Markdown
Member

My recommendation would be RINEXWriter - not just because of the capitalization, but because that’s a standard suffix I would recommend for a file writer

@JuliaTagBot JuliaTagBot added the AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. label Jul 19, 2026
@zsoerenm

Copy link
Copy Markdown

[noblock] We anticipate to also use it as a reader in the future. I think RINEX.jl fits well, but we are open for other suggestions.

@goerz

goerz commented Jul 20, 2026

Copy link
Copy Markdown
Member

We anticipate to also use it as a reader in the future.

In that case, RINEXFiles or RINEXFormat

@siebc

siebc commented Jul 20, 2026

Copy link
Copy Markdown

We ended up using RINEXParser.jl. (#161833). Thank you for your recommendations!

@goerz

goerz commented Jul 20, 2026

Copy link
Copy Markdown
Member

Closing in favor of #161833

@goerz goerz closed this Jul 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. new package

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants