cfe-lab / cfe-lab/MiCall

Review Micall user interface

Open
#208 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
21
Forks
11
Avg merge
12h 5m
Merged PRs (30d)
24

Description

Richard H. had some ideas to improve the user interface on the QAI site. We should review the ideas with James, Conan, Chanson, and Celia. After reviewing the ideas, create smaller issues for each of the changes.

  • Display the coloured scores for each region in a separate table that has the same layout as the raw and mapped counts table.
  • Clicking on an entry in one of the tables should bring up the coverage map as it does today, plus the row of coloured scores for all the regions on that sample.
  • Add a legend for the tables, particularly the error metrics. (Side 1, Side 2 down the left, and 1 - 14 across the top)
  • Display error metrics to one decimal place.
  • Two digits on the count of failed cycles in the error metrics table.
  • Should we report the count of failed cycles or censored cycles? That is, if cycle 100 out of 250 fails, should we report 1 or 151?

More ideas from Jeff:

  • Describe FASTA file header fields.
  • Display file name and path for raw data

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the existing tables, coverage map behavior, error metrics, and FASTA header display against the listed UI ideas. Resolve the open failed-versus-censored cycles question with the named collaborators, then create smaller issues for each agreed change; done means the review is complete and the work is decomposed.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data-visualization, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.