Integrate master into dev

[d-chambers]

Summary

Integrates the latest master (through #744) into dev. Because master's history was rebased at some point, its commits no longer share ancestry with the copies dev previously absorbed via the "Merge master into dev" squashes, so a flatten-rebase is unsafe. Instead this is a merge of master into dev with conflicts resolved in dev's favor (merge -X ours), keeping dev's feature/architecture work while pulling in master's non-conflicting changes. origin/dev is an ancestor of this branch, so landing it is a fast-forward.

What's included

• Merge commit integrating all 54 master PRs since the branches diverged (new transforms STALTA/FBE/kurtosis, Febus BSL/T1/mtx and SR4731 readers, spool read/merge speedups, specplot, numerous regression fixes, etc.).
• Deleted-in-dev modules stay deleted per dev's API cleanup: transform/fft.py and transform/spectro.py (replaced by fourier.py / viz.spectrogram).
• One follow-up fix: always specify an explicit ns unit when constructing np.datetime64 / np.timedelta64, closing the remaining unitless call sites (notably the flat-dump null-step sentinel in core/summary.py and the 0-D degenerate-array branches in utils/time.py). This avoids the numpy 2.5 unitless-NaT inconsistency.

Verification

• origin/dev and master are both fully contained; the merge commit has both parents. No commits lost from either side.
• Every spot-checked recent master fix (Fix error handling and kurtosis API ergonomics #742, Revert DASDAE compression options #744 revert, Fix DASDAE FileSpool patch attribute loading #736, Fix assorted regression edge cases #737, fix numpy 2.5 and overflow issue #716, Lazy import matplotlib and scipy.signal #740, Patch function data type #709, Pass kwargs through Patch.viz.spectrogram for 2D patches (fixes #661) #699, Feature/demedian demean #678) is materially present in dev's refactored form.
• Full non-remote test suite passes: 6946 passed, 152 skipped, 3 xfailed. Remote tests were skipped (network/env only).

Summary by CodeRabbit

• Bug Fixes

  • Improved consistency when handling dates and time durations by using nanosecond precision.
  • Improved timestamp parsing from supported filenames.
  • Empty HDF5 files without a detectable format now return a clear format error.

• Tests

  • Added coverage for format detection on empty HDF5 files.

Changelog

none

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 4894743a-edf9-4af2-b94d-c001e02cead7

📥 Commits

Reviewing files that changed from the base of the PR and between 96edf7a and 3dd0f91.

📒 Files selected for processing (3)

• dascore/core/summary.py
• dascore/utils/time.py
• tests/test_io/test_io_core.py

💤 Files with no reviewable changes (1)

• dascore/utils/time.py

🚧 Files skipped from review as they are similar to previous changes (1)

• dascore/core/summary.py

---

📝 Walkthrough

Walkthrough

The changes enforce explicit nanosecond precision across NumPy datetime and timedelta conversions, summary sentinels, and Sentek filename parsing. A test also verifies unknown-format handling for empty HDF5 files.

Changes

Nanosecond precision and format detection

Layer / File(s)	Summary
Time conversion utilities use explicit ns units dascore/utils/time.py	Datetime and timedelta conversion paths now construct NumPy values with explicit nanosecond precision.
Summary and Sentek timestamps use ns units dascore/core/summary.py, dascore/io/sentek/utils.py	The missing-step NaT sentinel and parsed Sentek filename timestamps now use explicit nanosecond units.
Empty HDF5 format detection coverage tests/test_io/test_io_core.py	Adds coverage confirming empty HDF5 files raise UnknownFiberFormatError when no fiber format is detected.

Suggested labels: IO, patch

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title matches the main change: merging master into dev.
Description check	✅ Passed	The description covers purpose, included changes, and verification, though it doesn't follow the template headings exactly.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dev_integrate

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.96%. Comparing base (d3d6520) to head (3dd0f91).

Additional details and impacted files

@@           Coverage Diff           @@
##              dev     #748   +/-   ##
=======================================
  Coverage   99.96%   99.96%           
=======================================
  Files         163      163           
  Lines       17087    17087           
=======================================
  Hits        17081    17081           
  Misses          6        6           

Flag	Coverage Δ
network	48.76% <33.33%> (ø)
unittests	99.95% <100.00%> (ø)

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

☔ View full report in Codecov by Harness.
📢 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.