You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 734c225
Browse filesBrowse the repository at this point in the historyBrowse files
Split events/visits into tabs, relocate Save project file, soften re-locate
Three things found by hands-on testing tonight:
1. "Detected events" and "Merged visits" were two full stacked tables -
a real trial can produce 1000+ raw event rows before merging, making
the merged table (usually much shorter and more useful) something you
had to scroll past everything else to reach. Split into a real ARIA
tablist, same mechanism already proven for Video/Path/Heat map/Raster
(not a new pattern) - each renders into its own panel, switch by
click or arrow keys.
2. "Save project file" was buried at the tail end of the Mouse Tracking
section, easy to miss even for the person who built it. Moved into
the Export section next to the CSV/XLSX downloads, with a one-line
distinction ("not spreadsheet data - a reloadable copy of this
trial's own work") so it doesn't read as a third export format.
3. Clicking a roster video that was named by a folder pick but never
actually opened fired a native OS file-picker with zero warning -
"it's in your list, but not really, go find it yourself." Now shows
an inline prompt with its own "Locate this file" button first, so the
system dialog is something you deliberately triggered, not a surprise.
Also (from an earlier fix this session, same root cause): the same
type-poke/type-entry/type-thigmotaxis class-name collision that made
Detected events unreadable also affected Merged visits - same fix
applied there too.
75/75 tests pass.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
<buttontype="button" id="rosterClearBtn" hidden>Clear all videos</button>
700
731
<divid="rosterClearConfirm" hidden>
701
732
<pid="rosterClearConfirmText"></p>
@@ -885,10 +916,6 @@ <h2>Videos</h2>
885
916
<canvasid="trackFailureStrip" width="640" height="24" aria-label="Tracking failure timeline: green is tracked, red is failed, across the whole video"></canvas>
886
917
</div>
887
918
<pclass="subtitle" id="trackScrubHint" hidden>Scrub the frame viewer above - green crosshair = tracked, red X = failed frame.</p>
888
-
889
-
<pclass="subtitle" id="saveProjectFileHint" hidden>Save a portable <code>_AUDITED.bmp.json</code> file with everything except the video itself (which stays wherever it already lives) - open it later, on any computer, to resume without re-tracking. Save it in the same folder as the video, next to it - the name makes it obvious at a glance, to you or anyone else, that this trial's already been done.</p>
<pclass="subtitle">Not spreadsheet data - a reloadable copy of this trial's own work, to resume later without re-tracking.</p>
986
+
<pclass="subtitle" id="saveProjectFileHint" hidden>Save a portable <code>_AUDITED.bmp.json</code> file with everything except the video itself (which stays wherever it already lives) - open it later, on any computer, to resume without re-tracking. Save it in the same folder as the video, next to it - the name makes it obvious at a glance, to you or anyone else, that this trial's already been done.</p>
<pclass="subtitle">Two visits to the same hole count as one unless the mouse fully disengaged in between.</p>
1170
-
<detailsclass="info-toggle">
1171
-
<summary>What does this mean?</summary>
1172
-
<pclass="subtitle">Two events at the same hole are merged into one visit when the raw center-density signal between them never drops close to baseline (reengage fraction x min center density) - a brief dip under the qualifying threshold doesn't end a visit, but a real return to baseline does. See DECISIONS.md 2026-09-04. Feeds the search-strategy classifier's visit sequence and the errors/perseverative-errors measure - not shown elsewhere yet.</p>
<pclass="subtitle">Two visits to the same hole count as one unless the mouse fully disengaged in between.</p>
1208
+
<detailsclass="info-toggle">
1209
+
<summary>What does this mean?</summary>
1210
+
<pclass="subtitle">Two events at the same hole are merged into one visit when the raw center-density signal between them never drops close to baseline (reengage fraction x min center density) - a brief dip under the qualifying threshold doesn't end a visit, but a real return to baseline does. See DECISIONS.md 2026-09-04. Feeds the search-strategy classifier's visit sequence and the errors/perseverative-errors measure - not shown elsewhere yet.</p>
0 commit comments