Outlier rejection analysis
Open
- Dominant language
- Jupyter Notebook
- Stars
- 524
- Forks
- 64
- Avg merge
- 4h 1m
- Merged PRs (30d)
- 3
Description
- Compare how Theia'a method of filtering by simulated pairwise (from global) vs. actual pairwise measurements helps
- Add to HTML plot the front-end inputs after each outlier rejection step
Also, add interface to Dask backend to plot progress as front-end proceeds
Contributor guide
Research direction
Start by reviewing Theia’s simulated-versus-actual pairwise filtering and the existing HTML plotting and Dask backend interfaces. Define which front-end inputs must be shown after each outlier-rejection step and how backend progress should be exposed, then validate both the comparison and end-to-end progress visualization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, jupyter-notebook
- Domain
- backend, data-visualization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100