ntnsndr/protocol-bicorder
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Suggestions on automating bicorder analysis #6

New Issue
Closed
opened 2025-12-05 22:40:01 +00:00 by ntnsndr · 3 comments
ntnsndr commented 2025-12-05 22:40:01 +00:00
Owner
Copy Link

From Venkatesh Rao on the SoP Discord:

  1. Default should be short form and it should auto-toggle to long-form if the short form isn’t converging to a clear classification.
  2. UI is a little confusing. If I didn’t already know to expect a slider id be confused by the ascii slider. Maybe a tool tip. And clearer association of the top/bottom legends with left/right. Though ideal would be nom-ascii proper graphics of course.
  3. Live feedback showing something like “Classification confidence: 30%”
  4. When it switches to predicted/automated, UI should maybe show a broader change like switch from red to green color scheme
  5. When done, a little info reward might be nice, like “Your protocol fits the MESSY SWARM cluster.” Like a personality test.
From Venkatesh Rao on the SoP Discord: > 1. Default should be short form and it should auto-toggle to long-form if the short form isn’t converging to a clear classification. > 2. UI is a little confusing. If I didn’t already know to expect a slider id be confused by the ascii slider. Maybe a tool tip. And clearer association of the top/bottom legends with left/right. Though ideal would be nom-ascii proper graphics of course. > 3. Live feedback showing something like “Classification confidence: 30%” > 4. When it switches to predicted/automated, UI should maybe show a broader change like switch from red to green color scheme > 5. When done, a little info reward might be nice, like “Your protocol fits the MESSY SWARM cluster.” Like a personality test.
ntnsndr commented 2025-12-18 17:45:26 +00:00
Author
Owner
Copy Link
  • > 1. Default should be short form and it should auto-toggle to long-form if the short form isn’t converging to a clear classification.

b461d759e5

  • > 2. UI is a little confusing. If I didn’t already know to expect a slider id be confused by the ascii slider. Maybe a tool tip. And clearer association of the top/bottom legends with left/right. Though ideal would be nom-ascii proper graphics of course.

7a57c29202

- [x] > 1. Default should be short form and it should auto-toggle to long-form if the short form isn’t converging to a clear classification. https://git.medlab.host/ntnsndr/protocol-bicorder/commit/b461d759e5e3452d24123b6ad964710aafd1767f - [x] > 2. UI is a little confusing. If I didn’t already know to expect a slider id be confused by the ascii slider. Maybe a tool tip. And clearer association of the top/bottom legends with left/right. Though ideal would be nom-ascii proper graphics of course. https://git.medlab.host/ntnsndr/protocol-bicorder/commit/7a57c292027db4f87587051c5f838921ca5a5565
ntnsndr commented 2026-01-17 16:23:16 +00:00
Author
Owner
Copy Link

When done, a little info reward might be nice, like “Your protocol fits the MESSY SWARM cluster.” Like a personality test.

On this point, explore options:

  • Provide modest celebratory feedback, not too cheesy, but make clear that the end has been reached, good job
  • Identify the cluster and summarize the characteristics
  • Suggest whether doing the long form is recommended, and provide that option
> When done, a little info reward might be nice, like “Your protocol fits the MESSY SWARM cluster.” Like a personality test. On this point, explore options: * Provide modest celebratory feedback, not too cheesy, but make clear that the end has been reached, good job * Identify the cluster and summarize the characteristics * Suggest whether doing the long form is recommended, and provide that option
ntnsndr commented 2026-01-18 06:00:23 +00:00
Author
Owner
Copy Link

Created much more live feedback and improved the experience of concluding the reading.

56d1f7e11e

Created much more live feedback and improved the experience of concluding the reading. https://git.medlab.host/ntnsndr/protocol-bicorder/commit/56d1f7e11e98b8b4697511d71c1d6b802728ea0e
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ntnsndr
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ntnsndr/protocol-bicorder#6
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?