AllenInstitute / AllenInstitute/ACE
Panel improvements: ‘Explore an individual annotation”
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Low priority fix
- Improved color-coding. Allow more general coloring, rather than requiring a specific “direction” column in the input.
- How to define up/down with AD (we used abundance as discussed in teach paper)? Right now we also just require a direction field, but could consider a quantitative metric of effect size, multiple columns, etc. if that makes more sense. Tain is actually rerunning the analysis: color-coding by numeric effect size instead of categorical?
Completed
Always show annotation value on left. Then have consistent ordering of table and chart.It would also be great if the color palette was consistent (e.g. when there is only 2 levels then the "No change" becomes red vs green). RELATED: Fix the color issue on the ACE app with the up/down/none calls. Can hard-code as factors.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the individual-annotation panel and the input handling for direction and effect-size fields. Review how categorical colors are assigned, then clarify the intended numeric or multi-column rule with maintainers. Done means the panel supports the agreed coloring and up/down behavior without requiring a specific direction column.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- data-visualization, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100