Add method in recording service to return all ticks

[ikondrat]

What has changed and why?

Add method in recording service to return all ticks

How has it been tested?

Nothing to test

Summary by CodeRabbit

• New Features

  • Added access to ordered ticks for an MCAP sequence, including sequence numbers and timestamps.
  • Sequences without linked samples return an empty tick list.
  • Unknown sequences or sequences outside the specified dataset return no results.

• Tests

  • Added coverage for ordered ticks, empty sequences, unknown sequences, and dataset mismatches.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-21T15:33:54.292319Z	d1c0e95	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[coderabbitai]

Understand this PR’s impact

Explore downstream dependencies and potential security impact with Blast Radius.

View blast radius →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Advanced

Run ID: bd0973f0-8ef3-48cc-a1ae-cd99b85dbfad

📥 Commits

Reviewing files that changed from the base of the PR and between d1c0e95 and 8e158d7.

📒 Files selected for processing (2)

• lightly_studio/src/lightly_studio/services/recording_service/get_ticks.py
• lightly_studio/tests/services/recording_service/test_get_ticks.py

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

• lightly_studio/tests/services/recording_service/test_get_ticks.py

Included review availability: Your plan provides up to 4 included reviews per hour; 2 remain after this review.

---

📝 Walkthrough

Walkthrough

The recording service now exposes get_ticks and validates sequence ownership through linked samples and collections. Tests cover ordered ticks, empty results, unknown sequences, and dataset mismatches.

Changes

Recording tick retrieval

Layer / File(s)	Summary
Tick retrieval service and export lightly_studio/src/lightly_studio/services/recording_service/get_ticks.py, lightly_studio/src/lightly_studio/services/recording_service/__init__.py	Checks dataset ownership through sequence, sample, and collection resolvers. Retrieves sample links and exports get_ticks.
Tick retrieval validation lightly_studio/tests/services/recording_service/test_get_ticks.py	Tests ordered tick values, empty tick lists, unknown sequences, and mismatched dataset IDs.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Feature

Sequence Diagram(s)

sequenceDiagram
  participant get_ticks
  participant mcap_group_sequence_resolver
  participant sample_resolver
  participant collection_resolver
  participant sequence_resolver
  get_ticks->>mcap_group_sequence_resolver: Check sequence existence
  get_ticks->>sample_resolver: Resolve linked sample
  get_ticks->>collection_resolver: Resolve sample collection
  get_ticks->>sequence_resolver: Get sample links
  sequence_resolver-->>get_ticks: Return tick data

Loading

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description identifies the main change but omits the required changelog section and gives inaccurate testing information. The pull request adds tests, so “Nothing to test” is incomplete.	Add the changelog checklist and describe the tests in test_get_ticks.py, including the covered cases and how to run them. Include the motivation, issue context, and any dependencies if applicable.
Docstring Coverage	⚠️ Warning	Docstring coverage is 33.33% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 6 functions across 3 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: adding a recording service method that returns all ticks.
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.

• Fix all pre-merge checks with AI

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

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.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d1c0e95752

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[lightly-fast-track-bot]

✅  Fast Track: all required checks passed — auto-approved.

Guardrail	Result	Message
frontend/complexity	✅	0 file(s) checked.
backend/complexity	✅	3 file(s) checked, no violations.
backend/coverage	✅	1 file(s) checked at 90%. [PASS] lightly_studio/src/lightly_studio/services/recording_service/get_ticks.py: 94.7%
diff-size	✅	PR adds 155 line(s) (limit: 215).
frontend/coverage	✅	0 file(s) checked.

View the guardrail run

To run the guardrails locally, from fast_track/ run make install once, then make run-guardrails (or GUARDRAILS=<name1>,<name2> make run-guardrails for some guardrails).

_{Reflects 8e158d7.}