Skip to content

Conversation

@d-chambers
Copy link
Contributor

@d-chambers d-chambers commented Sep 3, 2025

Description

Previously, part of the format check for Febus files looked at the instrument name. All the examples I had seen started with "fa" but it turns out this isn't always true. Since there are other strong checks, like the presence of "Source_X" datasets and specific attributes on each of these, I have simply removed this part of the febus format check.

Checklist

I have (if applicable):

  • referenced the GitHub issue this PR closes.
  • documented the new feature with docstrings or appropriate doc page.
  • included a test. See testing guidelines.
  • your name has been added to the contributors page (docs/contributors.md).
  • added the "ready_for_review" tag once the PR is ready to be reviewed.

Summary by CodeRabbit

  • Bug Fixes
    • Improved FEBUS dataset recognition by using attribute-based checks instead of requiring instrument names to follow a specific prefix. This reduces false negatives and increases compatibility with varied naming conventions, while preserving existing version detection behavior. Expect fewer misclassifications and smoother imports across diverse projects.
    • No user-facing API changes.

@d-chambers d-chambers added the IO Work for reading/writing different formats label Sep 3, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Sep 3, 2025

Walkthrough

Removes the top-level "fa" prefix check in _get_febus_version_str and initializes is_febus to True. Retains per-instrument checks for "Source" keys and required attributes, deriving version from Source Version. Adds an inline comment referencing #525. No public API or signatures changed.

Changes

Cohort / File(s) Summary
Febus utils version detection
dascore/io/febus/utils.py
Removed top-level instrument-name fingerprint check ("fa" prefix); set is_febus = True; kept per-instrument/source validations and version extraction from Source Version; added comment referencing issue #525; no API changes.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant Caller
  participant Utils as _get_febus_version_str
  participant Instruments as Instruments (dict)
  participant Sources as Sources (attrs)

  Caller->>Utils: call with dataset/attrs
  note right of Utils: Previous top-level key check (\"fa\" prefix) removed
  Utils->>Instruments: iterate instrument keys
  loop For each instrument
    Utils->>Sources: verify keys start with "Source"
    alt Required attrs present
      Utils->>Sources: read "Version"
    else Missing/invalid attrs
      Utils-->>Caller: return "" (empty string)
    end
  end
  Utils-->>Caller: return derived version string
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

  • Fix febus format empty file #492 — Also modifies _get_febus_version_str, adjusting detection logic around instrument keys; closely related to the removal of the "fa" prefix check.

Poem

I nibbled the rules, just one little bite,
The "fa" at the gate hopped out of sight.
Now sources speak, their Versions clear—
I twitch my nose: the path is here.
With gentle thumps, I test and see—
Attributes guide this bunny free. 🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between b79a338 and 67e4cd0.

📒 Files selected for processing (1)
  • dascore/io/febus/utils.py (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (15)
  • GitHub Check: test_code (macos-latest, 3.10)
  • GitHub Check: test_code (ubuntu-latest, 3.12)
  • GitHub Check: test_code (macos-latest, 3.12)
  • GitHub Check: test_code_min_deps (windows-latest, 3.13)
  • GitHub Check: test_code_min_deps (macos-latest, 3.12)
  • GitHub Check: test_code (windows-latest, 3.12)
  • GitHub Check: test_code_min_deps (windows-latest, 3.12)
  • GitHub Check: test_code (macos-latest, 3.11)
  • GitHub Check: test_code (windows-latest, 3.11)
  • GitHub Check: test_code (ubuntu-latest, 3.11)
  • GitHub Check: test_code_min_deps (ubuntu-latest, 3.13)
  • GitHub Check: test_code_min_deps (ubuntu-latest, 3.12)
  • GitHub Check: test_code (windows-latest, 3.10)
  • GitHub Check: test_code (ubuntu-latest, 3.10)
  • GitHub Check: test_code_min_deps (macos-latest, 3.13)
🔇 Additional comments (3)
dascore/io/febus/utils.py (3)

55-55: Good documentation of the change.

The comment clearly explains the motivation for removing the "fa" prefix requirement and references the relevant issue.


68-77: LGTM! The remaining validation logic is robust.

The function still performs meaningful validation by:

  1. Checking that all instrument keys contain only "Source" prefixed datasets
  2. Verifying that each Source dataset contains the expected attributes (AmpliPower, Hostname, WholeExtent, SamplingRate)
  3. Extracting version information from Source attributes

These checks provide stronger format validation than the removed "fa" prefix check, as they validate the actual structure and required metadata rather than just naming conventions.


63-63: Resolve review comment
Remaining validation—ensuring each group’s children start with Source and contain the required attributes—still enforces Febus format, so dropping the fa prefix check does not weaken validation.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix_febus_inst_code

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@codecov
Copy link

codecov bot commented Sep 3, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.87%. Comparing base (b79a338) to head (67e4cd0).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #525   +/-   ##
=======================================
  Coverage   99.87%   99.87%           
=======================================
  Files         122      122           
  Lines        9938     9938           
=======================================
  Hits         9926     9926           
  Misses         12       12           
Flag Coverage Δ
unittests 99.87% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@d-chambers d-chambers merged commit 639735b into master Sep 3, 2025
20 checks passed
@d-chambers d-chambers deleted the fix_febus_inst_code branch September 3, 2025 09:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

IO Work for reading/writing different formats

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants