Update documentation - #159
Conversation
|
Warning Rate limit exceeded
To continue reviewing without waiting, purchase usage credits in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThis PR updates documentation (BUILD.md, CONTRIBUTING.md, README.md) to reflect Neurolight Workbench branding, CI/CD details, and dual licensing; and adds CSV export functionality for detected peaks/troughs in the neuron trajectory and ROI intensity plot widgets. ChangesDocumentation Updates
Peak/Trough CSV Export Feature
Sequence DiagramsequenceDiagram
actor User
participant UI as Peak/Trough<br/>Export UI
participant Detector as Peak/Trough<br/>Detector
participant CSV as CSV<br/>Writer
participant Dialog as File Dialog /<br/>Message
User->>UI: Click "Export Peaks/Troughs"
UI->>Detector: Compute peaks/troughs from plot data
Detector-->>UI: Peak/trough records with frame, intensity
alt Data available
UI->>CSV: Write CSV (Neuron, Type, Frame, Time, Intensity)
CSV-->>Dialog: Show success message
Dialog-->>User: Export complete
else No data
UI->>Dialog: Show "no data" message
Dialog-->>User: Dismissed
else No peaks/troughs detected
UI->>Dialog: Show "no markers found" message
Dialog-->>User: Dismissed
end
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
36a4f4b to
65c7140
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/ui/neuron_trajectory_plot.py`:
- Around line 916-977: The export function _export_peaks_troughs_csv computes
peaks on each neuron's raw trace while the UI (_update_plot) shows peaks on the
smoothed average, confusing users; either rename the export action/button to
make "Per-Neuron" explicit (e.g., "Export Per-Neuron Peaks/Troughs (CSV)")
wherever the QAction/QPushButton is created, or add a brief
QMessageBox.information just before opening the file dialog in
_export_peaks_troughs_csv that clearly states "This will export peaks/troughs
for all neurons using unsmoothed raw traces" so users know the scope and data
source; update any tooltip text to match the new label/message to keep UI
consistent.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 1efe21ef-ff7c-4265-82de-92ecb137eee5
📒 Files selected for processing (5)
BUILD.mdCONTRIBUTING.mdREADME.mdsrc/ui/neuron_trajectory_plot.pysrc/ui/roi_intensity_plot.py
…ct state Co-authored-by: Cursor <cursoragent@cursor.com>
f8f1636 to
3c1e77e
Compare
…ain context Co-authored-by: Cursor <cursoragent@cursor.com>
This pull request updates the contributor and build documentation for the project, focusing on renaming the project to "Neurolight Workbench," clarifying build and release steps (especially for macOS), and providing much more detailed and up-to-date contribution guidelines. The changes also add comprehensive instructions for linting, formatting, and testing, and clarify the issue labeling and pull request process.
Documentation and Project Naming Updates:
BUILD.mdandCONTRIBUTING.mdfor consistency and clarity. [1] [2] [3] [4] [5] [6] [7]Build and Release Process Improvements:
BUILD.mdto document new macOS build, packaging, and signing steps, including.appbundle, DMG, and PKG installers, as well as environment requirements and enabling multiprocessing in frozen builds.Contribution and Development Guidelines:
CONTRIBUTING.mdwith instructions for using Ruff, describing both local and CI-based lint/format auto-fix workflows. [1] [2]src/directory structure. [1] [2]Testing and PR Process:
Licensing: