Code Monkey home page Code Monkey logo

dessia-tech / plot_data Goto Github PK

View Code? Open in Web Editor NEW
2.0 1.0 0.0 27.78 MB

Library to plot and draw your data on web browser in html format with Python command

Home Page: https://github.com/Dessia-tech/plot_data

License: GNU Lesser General Public License v2.1

Python 35.31% TypeScript 58.77% JavaScript 0.49% Shell 0.15% HTML 5.28%
parallel-plot dataviz figure figures frame geometry2d histogram html plot python scatter typescript htmlplot data-science engineering

plot_data's Introduction

Plot Data: Plot and draw your Python data on your web browser

npm (scoped) npm bundle size (minified) npm GitHub last commit

Introduction

Plot Data is a Python library that allows to plot and draw interactive figures on your web browser. With Plot Data you will be able to draw:

  • Scatters: image

  • Graphs: image

  • Histograms: image

  • Parallel plots: image

  • Draws: image

  • And put this all together in a Multiplot: image

Install

npm i plot-data

Usage

import * as plotdata from 'plot-data';

Develop

npm i
npm run dev

Documentation

Python: https://documentation.dessia.tech/plot_data/python/
Typescript: https://documentation.dessia.tech/plot_data/typescript/

Changelog

Check the changelog here

plot_data's People

Contributors

axelringhausen avatar dumouchelp avatar ghislainj avatar jeremie-ch avatar masfaraud avatar natsudzn avatar tanguylo avatar wirajandasilva avatar younesdessia avatar

Stargazers

 avatar  avatar

Watchers

 avatar

plot_data's Issues

Save / load configuration

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

  • What is the expected behavior?
    Saving / Loading a configuration (coordinates, scaling, selected points, plot types, etc)

  • What is the motivation / use case for changing the behavior?

  • Possible fixes

  • Please tell us about your environment:

    • branch:
    • commit:
    • python version:

Configure local default values from script

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?
    There is no way of changing behavior of default settings from script

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

  • What is the expected behavior?

Maybe we should see if it is possible

  • What is the motivation / use case for changing the behavior?

  • Possible fixes

  • Please tell us about your environment:

    • branch:
    • commit:
    • python version:

Plot_data selection possible with only associated_elements specified

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?
    Plot_data selection possible with only associated_elements specified

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Possible fixes

  • Please tell us about your environment:

    • branch:
    • commit:
    • python version:

Failure when calling load_from_file

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?
    image

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages
    Call a json file using a plot_data object through load_from_file()

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Possible fixes

  • Please tell us about your environment:

    • branch:
    • commit:
    • python version:

Log scale when plotting a Graph2D

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?

Allow the user to display a log scale when plotting a Graph2D

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Possible fixes

  • Please tell us about your environment:

    • branch:
    • commit:
    • python version:

Scatter Matrix Plot

  • I'm submitting a ...
    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.

A nice feature would be to have a scatter matrix plot

image

Integer Numbers in ParallelPlot

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?
    A parameter is discretized in 10 for its representation in the parallelplot. It often produces floating represented values for intialy interger numbers.

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

  • What is the expected behavior?
    Possibility to specify the interval between two successive numbers in the graph.

  • What is the motivation / use case for changing the behavior?

  • Possible fixes

  • Please tell us about your environment:

    • branch: master
    • commit: 0.8.5
    • python version: 3.8

LineSegment2D not displayed

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?

LineSegment2D is not displayed.

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

You can check it here. > plot_data/script/test_objects/primitive_group_test.py, by running this script.

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Possible fixes

  • Please tell us about your environment:

    • branch: master
    • commit:
    • python version:

Graph representation

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

  • What is the expected behavior?
    Creating an object dedicated to representing graphs.
    Some interesting features are :

    • A layout function
    • The representation of weights, distances and other labels
    • Moving nodes by dragging and dropping with your mouse
    • Highlighting and selection features
  • What is the motivation / use case for changing the behavior?

  • Possible fixes

  • Please tell us about your environment:

    • branch:
    • commit:
    • python version:

File editing

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

  • What is the expected behavior?
    Create a function in standalone mode that writes selected points indices in a txt file.

  • What is the motivation / use case for changing the behavior?

  • Possible fixes

  • Please tell us about your environment:

    • branch:
    • commit:
    • python version:

Is name usable in to_disp_attribute_names ?


elements = [{'name': 'CONFIG 1',
  'length_pipe': 8.920698939198246,
  'min_length_pipe': 0.7119027216330243,
  'max_length_pipe': 1.4792896624259773,
  'avg_length_pipe': 1.1150873673997808,
  'mini_distance_between_block': 0.030000000000000082,
  'maxi_distance_between_block': 0.13000000000000012},
 {'name': 'CONFIG 2',
  'length_pipe': 6.85902156118525,
  'min_length_pipe': 0.41895064761469547,
  'max_length_pipe': 1.3236557977320382,
  'avg_length_pipe': 0.8573776951481562,
  'mini_distance_between_block': 0.029681644159311606,
  'maxi_distance_between_block': 0.6187083319303209},
 {'name': 'CONFIG 3',
  'length_pipe': 5.273043755389396,
  'min_length_pipe': 0.1249460085369101,
  'max_length_pipe': 0.9020225953545109,
  'avg_length_pipe': 0.8573776951481562,
  'mini_distance_between_block': 0.08944271909999157,
  'maxi_distance_between_block': 0.33000000000000007}]
to_disp_attribute_names = ['name','length_pipe','min_length_pipe','max_length_pipe',
                           'avg_length_pipe','mini_distance_between_block',
                           'maxi_distance_between_block']
text_style = TextStyle(text_color=GREY,
                       font_size=10,
                       font_style='sans-serif')
surface_style = SurfaceStyle(color_fill=LIGHTGREY, opacity=0.3)
custom_tooltip = Tooltip(to_disp_attribute_names=to_disp_attribute_names,
                         surface_style=surface_style,
                         text_style=text_style,
                         tooltip_radius=10)
all_points = elements
plots = []
#ScatterPlot
plots.append(Scatter(tooltip=custom_tooltip,
                     to_disp_attribute_names=['min_length_pipe', 'name'],
                     elements=all_points))
plots.append(Scatter(tooltip=custom_tooltip,
                     to_disp_attribute_names=['mini_distance_between_block', 'name'],
                     elements=all_points))
plots.append(Scatter(tooltip=custom_tooltip,
                     to_disp_attribute_names=['avg_length_pipe', 'length_pipe'],
                     elements=all_points))
# ParallelPlot
plots.append(ParallelPlot(elements=all_points,
                          to_disp_attribute_names=to_disp_attribute_names))
multiplots = MultiplePlots(plots=plots, elements=all_points, 
                           initial_view_on=True)
from plot_data import plot_canvas
plot_canvas(plot_data_object=multiplots, canvas_id='canvas')

Leads to:
image

Intempestive alert on ScatterPlot opening

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?

When opening any ScatterPlot (since version >=0.6.0 I guess) an alert shows up and blocks loading. This looks like a simple warning so an alert seems a bit excessive, given the fact it shows up at each page reload

image

I suspect it to come from PlotScatter constructor, probably because mergeOn is True by default.

image

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

Open any WorkflowRun in platform-dev

  • What is the expected behavior?

This should be a simple warning or at least not block user handling

  • What is the motivation / use case for changing the behavior?

Better UX

  • Possible fixes

  • Please tell us about your environment:

    • branch: master
    • commit: 0.6.1
    • python version:

Parallel plot - rubberband

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?
    When we go to parallelplot rubberband, we can select an interval using percentage of available range.

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

  • What is the expected behavior?
    User would like to select precisely each interval instead of using percentage that is less accurate.

  • What is the motivation / use case for changing the behavior?
    User specification more accurate.

  • Possible fixes

  • Please tell us about your environment:

    • branch:
    • commit:
    • python version:

load_from_file() error - dessia_common v0.4.5

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?
    image

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Possible fixes

  • Please tell us about your environment:

    • branch:
    • commit:
    • python version:

Clear ParallelPlot's rubberband

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?

It looks like there is no way of directly clearing ParallelPlot's rubberband when clearing selection. Or, at least, we didn't find it

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

An issue has been opened a while ago on frontend repo, and we developped a work around to implement it.
A builtin feature would be really nice

Link to frontend repo issue :
https://gitea.dessia.tech/DessiA/frontend/issues/425#issuecomment-8787

  • Please tell us about your environment:

    • branch: master
    • commit: v0.8.4
    • python version: 3.9

Single selection doesn't index value right

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?

When selecting only one point, frontend's encounter an issue where the selection_change listener emit an empty array.
When selecting multiple point with the rubberband feature, it works well since several releases, though

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

Using frontend :
Open a WorkflowRun
log indices in selection_change listener
Click a point

  • What is the expected behavior?

We should listen to an array with one element OR the element should be added to the current selection

  • What is the motivation / use case for changing the behavior?

I think this is what is expected from an UX point of vue

  • Possible fixes

  • Please tell us about your environment:

    • branch: master
    • commit: 0.8.4
    • python version: 3.9

Bug: graph.py still uses attributes 'size', 'color_fill', etc.

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?
    "plot_data/graph.py", line 45, in _to_primitives
    prim = plot_data.Point2D(x, y, size=4, color_fill=color, [...])
    TypeError: init() got an unexpected keyword argument 'size'

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages
    Just launch any plot_data.graph.NetworkxGraph

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Possible fixes

  • Please tell us about your environment:

    • branch: master
    • commit:
    • python version:

PrimitiveGroup removes itself from MultiPlot when clicked or moved

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?

Whenever a PrimitiveGroup is added to a Multiplot by selecting objects in ScatterPlot, for instance, it looks like it gets removed if it is grabbed and moved around.

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

On demo platform :
Select a point. It uploads its displays.
Click _Order Plots
Click or move new PrimitiveGroup plot. It crashs the MultiPlot in a Michael Bay style. See error logs

image

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Possible fixes

It seems that the selection changes is triggered even if selection isn't changed. By adding a log to the event listener callback we can see that it is called whenever mouse is released.
These two behaviors could possibly be linked

  • Please tell us about your environment:

    • branch: master
    • commit: tag v0.4.8
    • python version: N/A

Use Point2D in PrimitiveGroup

It's can be interesting to use the Point2D in Primitive to have points in 2D visualization like we can have in mathplotlib (Exemple in picture)
Capture d’écran du 2021-08-31 19-16-04

Rotate plot_data.Text

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?

plot_data.Text is always parallel to the x axis

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

  • What is the expected behavior?

I'm looking for an option for plot_data.Text to be able to rotate it, with a certain angle, and not have it all the time parallel to the x axis. Like in this photo
photo

  • What is the motivation / use case for changing the behavior?

  • Possible fixes

  • Please tell us about your environment:

    • branch:
    • commit:
    • python version:

To keep family points when adding Scatterplot

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?

When user adds Scatterplot with two differents family describe, all points are in the same color and do not take into account theses families.

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

Add Scatterplot with family describe.

  • What is the expected behavior?
    The user expects to see points in its family color.

  • What is the motivation / use case for changing the behavior?
    It will allow a better identification of specific points

  • Possible fixes

  • Please tell us about your environment:

    • branch:
    • commit:
    • python version:

Remove focus from plot_data

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?

It's not really a bug but when you load an object in the platform you are directly redirected to the canvas

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

You only need to load an object on the platform to reproduce this issue

  • What is the expected behavior?

It is expected to don't have redirection from the library.
From what I saw from the code it was used to read keyboard inputs but it doesn't seem to change anything so it's seems fine to remove it (tried with ctrl + click on point)

  • What is the motivation / use case for changing the behavior?

  • Possible fixes

Just remove this line:

this.canvas.focus();

Update readme with new build

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?

It shows the old way of building dev version

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Possible fixes
    mention npm run dev, libdev and how to set template

  • Please tell us about your environment:

    • branch:
    • commit:
    • python version: 0.7.2

point family display in table doesn't work

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?
    When i click on 'Display points in table' for a family in 'Datasets', no points are available in the table

  • What is the expected behavior?
    Points appear in the table

  • Please tell us about your environment:
    platform-dev

New scatterplot doesn't have any attribute_name

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?

When you create a new scatterplot, then click on a point there is an error because there is no attribute_name, meaning that there is also no tooltip

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

Open an object with a multiplot
Create a new scatterplot
Click on any point of that scatterplot

  • What is the expected behavior?

New scatterplot should have tooltip too

  • Please tell us about your environment:

    • branch: fix/plot-data (in frontend)

Camembert diagrams

  • I'm submitting a ...
    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.

Implement piecharts

image

Consistent attributes

  • I'm submitting a ...

    • feature request
  • What is the current behavior?

Some classes have inconsistent attribute names such as to_disp_attributes (Parallel Plot) & to_disp_att_names (Scatter Plot) or elements (Scatter Plot / Parallel Plot) & points (Multiple Plot) which makes integration a trickier

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

  • What is the expected behavior?

These should be made consistent. For example, all classes should implements points or elements, but not both, etc...

  • What is the motivation / use case for changing the behavior?

This is in order to avoid a lot of checking on frontend side

  • Possible fixes

  • Please tell us about your environment:

    • branch: master
    • commit: v0.3.2
    • python version: 3.8

turn objects transparent

Sometimes there are plots in different planes that superpose each other, and it is often hard to figure out what is happening in the background plane.

What about creating a feature enabling the user to turn the object transparent when he wishes for, so he can have an idea if everything works fine back there?

image

ParallelPlot selection issue

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?
    image
    It doesn't select well (it works for other value)

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages
    Nothing special

  • What is the expected behavior?
    The well selection of this information in the parallel plot

  • What is the motivation / use case for changing the behavior?

  • Possible fixes

  • Please tell us about your environment:

    • branch: master
    • commit:
    • python version: 3.8.8

npm install not working

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?
    Tedlt
    image

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Possible fixes

  • Please tell us about your environment:

    • branch:
    • commit:
    • python version:

Plot_data html file saving in user-path-specified file

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?
    When a plot_data is created using command plot_canvas, the html file is openned in Web browser and saved in the computer Temp folder with no possibility to specify by the user on the path where the the file wil be saved.

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

  • What is the expected behavior?
    When command plot_canvas is called, it is possible fir the user to specify two attributes :

  • need_display : Bool -> specifiy if the window openned in Web browser is needed or not
  • html_saving_path : str -> specify the path where the html file is saved (by default it's the classical computer Temp file)
  • What is the motivation / use case for changing the behavior?
    For script use of plot_data

  • Possible fixes

  • Please tell us about your environment:

    • branch:
    • commit:
    • python version:

Disabling highlight option

It seems that for ~ 1000 rectangles (contours) highlight of these is very slow.
Maybe an option to disable it would increase perf

selectionchange event issue

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?

When you create a primitivegroupcontainer, then select multiples points using the selection tool the event is empty instead of returning the indexs of points

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

Go to the platform (platform-dev)
Open a workflow run object
Create a primitivegroupcontainer
log event.detail.selected_point_indices inside multi-plot.component.ts (line 124) of the frontend
without a primitivegroupcontainer it returns the index but it's not the case when one already exist

  • What is the expected behavior?

It should always return the indexs of points

  • What is the motivation / use case for changing the behavior?

To fix result component & addDisplay method

Adjusting contours sizes for PrimitiveGroupsContainer with large number of results

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?
    I am trying to plot some results with plot_data with:

  • 1 scatterplot with two important parameters
  • 1 primitivegroupscontainer plot where i represent all the contours for all the results I have (currently between 1 and 132 results)
    The corresponding html plot is attached to the ticket

But when the contours are plotted, the primitivegroups are placed function of the parameters specified in attributes x_variable and y_variable in the PrimitiveGroupsContainer (cf. picture attached from code). Thus, the PrimitiveGroupsContainer plotting windows adjusts function of the contours plotted.

So the question is :

  • is it possible to adjust (increase) the contours sizes so as to make the user reading easier
  • OR is it possible to make contours be closer from one another to limit the space occupied by the whole plot so as for the window to adjust on a smaller area ?

For information, modification of attribute "sizing" of PrimitiveGroupsContainer" does not seem not have any effect to solve the problem.

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Possible fixes

  • Please tell us about your environment:

    • branch: master
    • commit:
    • python version:

image

tmpicrty41u.zip

Implement Sankey Graphs

  • I'm submitting a ...
    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.

A nice new feature would be to be able to show Sankey diagrams. This is just an idea righ now, so a lot of elements are to be defined

First steps :

  • Find a dataset that could be generic/exhaustive for this
  • Define inputs (what are plotly and matplotlib doing ?)

An idea of an extreme complex graph :
image

One first constraints would be to be able to apply every plot-data handling on these elements (reorganize, move, etc...)

Some other elements to consider :
https://matplotlib.org/stable/api/sankey_api.html
https://fr.wikipedia.org/wiki/Diagramme_de_Sankey#:~:text=Un%20diagramme%20de%20Sankey%20ou,les%20flux%20%C3%A9nerg%C3%A9tiques%20de%20processus
https://plotly.com/python/

Highlight for wire

Wire is drown with open polygon. To see where the wire should end, it would be nice to have a highlight of wire

MultiPlot : Show full slider by default

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?

When selecting from a multiplot (and possibly just a ParallelPlot ?), sliders are not shown full by default which leads to this kind of situations :

image
image

Seven solutions are selected whereas it looks like none should be in range of all sliders. this is because the two righterns sliders haven't been used but still set a range from their min to max and allow solutions that are not shown included to actually be included.

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

This is not a bug, but I could reproduce locally as well. I can provide ways to reproduce if needed

  • What is the expected behavior?

There might be two :

  • Either we want to unselect all by default, and then after the first handling, just use what slider have been set (not preferred in my opinion)
  • Or we want to select all by default and show full sliders. I like this because it is a filters selection
  • What is the motivation / use case for changing the behavior?

Right behavior of platform and good UX

  • Possible fixes

  • Please tell us about your environment:

    • branch: master
    • commit: v0.5.9
    • python version: 3.9

disp attributes doesn't work when point are merged even if one point - local plot_data

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?

Correct display when point not merged, uncorrect when merged even if there is one point

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages
    Merged :
    image

Not merged:
image

  • What is the expected behavior?
    Not merged behavior when there is one point selected

  • What is the motivation / use case for changing the behavior?
    I think customers will not understand why information are not displayed

  • Possible fixes

  • Please tell us about your environment:

    • branch: local
    • commit: latest plot_data version
    • python version: 3.8

ordering a multi plot after deleting a plot

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?

When you have a multiplot, and you delete a plot you can no longer order the multiplot.
Example a multiplot with one scatterplot and one parallelplot, if we delete one, it's not possible to order the remaining one

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

Open an object
Delete a plot inside a multi plot
Try to order the plot

  • What is the expected behavior?

It should order the remaining plots

ScatterPlot-MultiSelection

  • I'm submitting a ...

    • [O] bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?
    When i select "Enable depency" and i click "Enable selection" on a ScatterPlot, the box doesn't select all point in it.

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

  • What is the expected behavior?
    The box should select all point in it.

  • What is the motivation / use case for changing the behavior?
    Enable depency allows users to see in another plot the same point but in different view.

  • Possible fixes

  • Please tell us about your environment:

    • branch: main
    • commit:
    • python version: 3.8.5

Tooltip font color inconsistency

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?

When you change the tooltip color font the information label isn't matching the color who was set

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

In frontend: open scatterplot settings, change tooltip color, the information label isn't maching the tooltip attribute color

  • What is the expected behavior?

Tooltip text should use the same color, or at least be configurable

chrome_n3OUkG4VsH

Simplify input data: to_disp_attribute_names

To discuss:

  • to_disp_attribute_names is an ugly name and should be optionnal? it is used in 2 ways: tooltip and axis. Maybe rename scatter x_axis='attribute1' and y_axis='attribute2'?

image

Adding 4 primitive groups to a container result in an infinite loop on the platform

  • I'm submitting a ...

    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.
  • What is the current behavior?

  • If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem Avoid reference to other packages

  • What is the expected behavior?

  • What is the motivation / use case for changing the behavior?

  • Possible fixes
    plot_data seems to be working correctly. And since the problem only occurs on the platform, a possible bug on frontend should be investigated.

  • Please tell us about your environment:

    • branch:
    • commit:
    • python version:

Heat Map

  • I'm submitting a ...
    • bug report
    • feature request
    • support request => Please do not submit support request here, see note at the top of this template.

We should implement heat maps as another type of plot for ScatterPlots in order to show point density

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.