fossasia/visdom

Is there a way to change marker edge width and color?

Closed

#623 opened on May 10, 2019

View on GitHubContributor guide
 (5 comments) (0 reactions) (0 assignees)Python (1,152 forks)batch import
Fix Proposedenhancementhelp wanted

Repository metrics

Stars
 (9,831 stars)
PR merge metrics
 (Avg merge 9d 12h) (116 merged PRs in 30d)

Description

Is your feature request related to a problem? Please describe. When I use 3d Scatter chart, I need to customize the opts.markercolor which indicate the weights for different points. For instance, the darker of the points, the higher of the weight. However, the border of the points, which always assigned a darker color makes the visual evaluation harder.

So I'm wondering if there is any api or feature in the future provide the ability to change the marker edge width and color like what Plot.ly did.

Describe the solution you'd like Add more configurations in opts. like :

        self.vis.scatter(
            X=X,
            Y=Y,
            env=env,
            win=legend,
            opts=dict(
                markersize=2,
                markercolor=color_map,
                *markeredgewidth=0*
                name=legend,
                title=legend
            )
        )

image

Contributor guide

Research direction
The issue requests adding marker edge width and color options to the 3D scatter plot in visdom. To implement, locate the scatter function in the visdom source code, likely in `visdom/plots.py` or similar. The function currently accepts opts like `markersize` and `markercolor`. Add new opts `markeredgewidth` and `markeredgecolor` and pass them to the underlying Plotly trace (since visdom uses Plotly). Ensure these options are documented in the docstring and reflected in the frontend. Check existing tests for scatter to add test cases. No linked PRs or comments indicate prior work, so this is a fresh feature to implement.
Tech stack
python
Domain
data
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75