[6g6ddlmZddlZGddeZdS)) BaseTraceTypeNceZdZdZdZhdZedZejdZedZ e jdZ edZ e jd Z ed Z e jd Z ed Z e jd Z edZ e jdZ edZejdZedZejdZedZejdZedZejdZedZejdZedZejdZedZejdZedZejdZed Zejd!Zed"Zejd#Zed$Zejd%Zed&Zejd'Zed(Zejd)Zed*Zejd+Zed,Zejd-Zed.Zejd/Zed0Zejd1Zed2Zejd3Zed4Z e jd5Z ed6Z!e!jd7Z!ed8Z"e"jd9Z"ed:Z#e#jd;Z#ed<Z$e$jd=Z$ed>Z%e%jd?Z%ed@Z&e&jdAZ&edBZ'e'jdCZ'edDZ(e(jdEZ(edFZ)e)jdGZ)edHZ*e*jdIZ*edJZ+e+jdKZ+edLZ,e,jdMZ,edNZ-e-jdOZ-edPZ.edQZ/ dTfdS Z0xZ1S)U Pointcloud pointcloud>'xyxyidsuidmetanametexttypexsrcysrcxaxisxysrcyaxisidssrclegendmarkerstreamindicesmetasrcopacitytextsrcvisiblexboundsybounds hoverinfo customdata hoverlabel indicessrc legendrank showlegend uirevision xboundssrc yboundssrc legendgroup legendwidth hoverinfosrc customdatasrclegendgrouptitlec|dS)a Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, "scatter" traces also appends customdata items in the markers DOM elements The 'customdata' property is an array that may be specified as a tuple, list, numpy array, or pandas Series Returns ------- numpy.ndarray r"selfs \/var/www/surfInsights/venv3-11/lib/python3.11/site-packages/plotly/graph_objs/_pointcloud.pyr"zPointcloud.customdata7sL!!c||d<dS)Nr"r0r2vals r3r"zPointcloud.customdataH \r4c|dS)z Sets the source reference on Chart Studio Cloud for `customdata`. The 'customdatasrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str r-r0r1s r3r-zPointcloud.customdatasrcNsO$$r4c||d<dS)Nr-r0r6s r3r-zPointcloud.customdatasrc]s #_r4c|dS)a\ Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired. The 'hoverinfo' property is a flaglist and may be specified as a string containing: - Any combination of ['x', 'y', 'z', 'text', 'name'] joined with '+' characters (e.g. 'x+y') OR exactly one of ['all', 'none', 'skip'] (e.g. 'skip') - A list or array of the above Returns ------- Any|numpy.ndarray r!r0r1s r3r!zPointcloud.hoverinfocs$K  r4c||d<dS)Nr!r0r6s r3r!zPointcloud.hoverinfows[r4c|dS)z Sets the source reference on Chart Studio Cloud for `hoverinfo`. The 'hoverinfosrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str r,r0r1s r3r,zPointcloud.hoverinfosrc}sN##r4c||d<dS)Nr,r0r6s r3r,zPointcloud.hoverinfosrcs"^r4c|dS)a" The 'hoverlabel' property is an instance of Hoverlabel that may be specified as: - An instance of :class:`plotly.graph_objs.pointcloud.Hoverlabel` - A dict of string/value properties that will be passed to the Hoverlabel constructor Supported dict properties: align Sets the horizontal alignment of the text content within hover label box. Has an effect only if the hover label text spans more two or more lines alignsrc Sets the source reference on Chart Studio Cloud for `align`. bgcolor Sets the background color of the hover labels for this trace bgcolorsrc Sets the source reference on Chart Studio Cloud for `bgcolor`. bordercolor Sets the border color of the hover labels for this trace. bordercolorsrc Sets the source reference on Chart Studio Cloud for `bordercolor`. font Sets the font used in hover labels. namelength Sets the default length (in number of characters) of the trace name in the hover labels for all traces. -1 shows the whole name regardless of length. 0-3 shows the first 0-3 characters, and an integer >3 will show the whole name if it is less than that many characters, but if it is longer, will truncate to `namelength - 3` characters and add an ellipsis. namelengthsrc Sets the source reference on Chart Studio Cloud for `namelength`. Returns ------- plotly.graph_objs.pointcloud.Hoverlabel r#r0r1s r3r#zPointcloud.hoverlabelsfL!!r4c||d<dS)Nr#r0r6s r3r#zPointcloud.hoverlabelr8r4c|dS)am Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type. The 'ids' property is an array that may be specified as a tuple, list, numpy array, or pandas Series Returns ------- numpy.ndarray r r0r1s r3r zPointcloud.idsE{r4c||d<dS)Nr r0r6s r3r zPointcloud.idsU r4c|dS)z Sets the source reference on Chart Studio Cloud for `ids`. The 'idssrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str rr0r1s r3rzPointcloud.idssrcsH~r4c||d<dS)Nrr0r6s r3rzPointcloud.idssrcXr4c|dS)a A sequential value, 0..n, supply it to avoid creating this array inside plotting. If specified, it must be a typed `Int32Array` array. Its length must be equal to or greater than the number of points. For the best performance and memory use, create one large `indices` typed array that is guaranteed to be at least as long as the largest number of points during use, and reuse it on each `Plotly.restyle()` call. The 'indices' property is an array that may be specified as a tuple, list, numpy array, or pandas Series Returns ------- numpy.ndarray rr0r1s r3rzPointcloud.indicess$Ir4c||d<dS)Nrr0r6s r3rzPointcloud.indices Yr4c|dS)z Sets the source reference on Chart Studio Cloud for `indices`. The 'indicessrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str r$r0r1s r3r$zPointcloud.indicessrcL!!r4c||d<dS)Nr$r0r6s r3r$zPointcloud.indicessrcr8r4c|dS)a/ Sets the reference to a legend to show this trace in. References to these legends are "legend", "legend2", "legend3", etc. Settings for these legends are set in the layout, under `layout.legend`, `layout.legend2`, etc. The 'legend' property is an identifier of a particular subplot, of type 'legend', that may be specified as the string 'legend' optionally followed by an integer >= 1 (e.g. 'legend', 'legend1', 'legend2', 'legend3', etc.) Returns ------- str rr0r1s r3rzPointcloud.legend%s"H~r4c||d<dS)Nrr0r6s r3rzPointcloud.legend8rGr4c|dS)ar Sets the legend group for this trace. Traces and shapes part of the same legend group hide/show at the same time when toggling legend items. The 'legendgroup' property is a string and must be specified as: - A string - A number that will be converted to a string Returns ------- str r*r0r1s r3r*zPointcloud.legendgroup>sM""r4c||d<dS)Nr*r0r6s r3r*zPointcloud.legendgroupO!]r4c|dS)aU The 'legendgrouptitle' property is an instance of Legendgrouptitle that may be specified as: - An instance of :class:`plotly.graph_objs.pointcloud.Legendgrouptitle` - A dict of string/value properties that will be passed to the Legendgrouptitle constructor Supported dict properties: font Sets this legend group's title font. text Sets the title of the legend group. Returns ------- plotly.graph_objs.pointcloud.Legendgrouptitle r.r0r1s r3r.zPointcloud.legendgrouptitleUs(&''r4c||d<dS)Nr.r0r6s r3r.zPointcloud.legendgrouptitleks#&    r4c|dS)a Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with "reversed" `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items. When having unranked or equal rank items shapes would be displayed after traces i.e. according to their order in data and layout. The 'legendrank' property is a number and may be specified as: - An int or float Returns ------- int|float r%r0r1s r3r%zPointcloud.legendrankqs&L!!r4c||d<dS)Nr%r0r6s r3r%zPointcloud.legendrankr8r4c|dS)a  Sets the width (in px or fraction) of the legend for this trace. The 'legendwidth' property is a number and may be specified as: - An int or float in the interval [0, inf] Returns ------- int|float r+r0r1s r3r+zPointcloud.legendwidthsM""r4c||d<dS)Nr+r0r6s r3r+zPointcloud.legendwidthrRr4c|dS)a% The 'marker' property is an instance of Marker that may be specified as: - An instance of :class:`plotly.graph_objs.pointcloud.Marker` - A dict of string/value properties that will be passed to the Marker constructor Supported dict properties: blend Determines if colors are blended together for a translucency effect in case `opacity` is specified as a value less then `1`. Setting `blend` to `true` reduces zoom/pan speed if used with large numbers of points. border :class:`plotly.graph_objects.pointcloud.marker. Border` instance or dict with compatible properties color Sets the marker fill color. It accepts a specific color. If the color is not fully opaque and there are hundreds of thousands of points, it may cause slower zooming and panning. opacity Sets the marker opacity. The default value is `1` (fully opaque). If the markers are not fully opaque and there are hundreds of thousands of points, it may cause slower zooming and panning. Opacity fades the color even if `blend` is left on `false` even if there is no translucency effect in that case. sizemax Sets the maximum size (in px) of the rendered marker points. Effective when the `pointcloud` shows only few points. sizemin Sets the minimum size (in px) of the rendered marker points, effective when the `pointcloud` shows a million or more points. Returns ------- plotly.graph_objs.pointcloud.Marker rr0r1s r3rzPointcloud.markers`H~r4c||d<dS)Nrr0r6s r3rzPointcloud.markerrGr4c|dS)a Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index. The 'meta' property accepts values of any type Returns ------- Any|numpy.ndarray r r0r1s r3r zPointcloud.metas(F|r4c||d<dS)Nr r0r6s r3r zPointcloud.metaV r4c|dS)z Sets the source reference on Chart Studio Cloud for `meta`. The 'metasrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str rr0r1s r3rzPointcloud.metasrcIr4c||d<dS)Nrr0r6s r3rzPointcloud.metasrcrJr4c|dS)a# Sets the trace name. The trace name appears as the legend item and on hover. The 'name' property is a string and must be specified as: - A string - A number that will be converted to a string Returns ------- str rr0r1s r3rzPointcloud.name sF|r4c||d<dS)Nrr0r6s r3rzPointcloud.namer]r4c|dS)z Sets the opacity of the trace. The 'opacity' property is a number and may be specified as: - An int or float in the interval [0, 1] Returns ------- int|float rr0r1s r3rzPointcloud.opacityr_r4c||d<dS)Nrr0r6s r3rzPointcloud.opacity-rJr4c|dS)z Determines whether or not an item corresponding to this trace is shown in the legend. The 'showlegend' property must be specified as a bool (either True, or False) Returns ------- bool r&r0r1s r3r&zPointcloud.showlegend3sL!!r4c||d<dS)Nr&r0r6s r3r&zPointcloud.showlegendBr8r4c|dS)ak The 'stream' property is an instance of Stream that may be specified as: - An instance of :class:`plotly.graph_objs.pointcloud.Stream` - A dict of string/value properties that will be passed to the Stream constructor Supported dict properties: maxpoints Sets the maximum number of points to keep on the plots from an incoming stream. If `maxpoints` is set to 50, only the newest 50 points will be displayed on the plot. token The stream id number links a data trace on a plot with a stream. See https://chart- studio.plotly.com/settings for more details. Returns ------- plotly.graph_objs.pointcloud.Stream rr0r1s r3rzPointcloud.streamHs2H~r4c||d<dS)Nrr0r6s r3rzPointcloud.streamcrGr4c|dS)a Sets text elements associated with each (x,y) pair. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. If trace `hoverinfo` contains a "text" flag and "hovertext" is not set, these elements will be seen in the hover labels. The 'text' property is a string and must be specified as: - A string - A number that will be converted to a string - A tuple, list, or one-dimensional numpy array of the above Returns ------- str|numpy.ndarray rr0r1s r3rzPointcloud.textis&F|r4c||d<dS)Nrr0r6s r3rzPointcloud.text~r]r4c|dS)z Sets the source reference on Chart Studio Cloud for `text`. The 'textsrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str rr0r1s r3rzPointcloud.textsrcr_r4c||d<dS)Nrr0r6s r3rzPointcloud.textsrcrJr4c|dS)aH Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions. The 'uid' property is a string and must be specified as: - A string - A number that will be converted to a string Returns ------- str r r0r1s r3r zPointcloud.uidrBr4c||d<dS)Nr r0r6s r3r zPointcloud.uidrDr4c|dS)aN Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves. The 'uirevision' property accepts values of any type Returns ------- Any r'r0r1s r3r'zPointcloud.uirevisions2L!!r4c||d<dS)Nr'r0r6s r3r'zPointcloud.uirevisionr8r4c|dS)a Determines whether or not this trace is visible. If "legendonly", the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible). The 'visible' property is an enumeration that may be specified as: - One of the following enumeration values: [True, False, 'legendonly'] Returns ------- Any rr0r1s r3rzPointcloud.visiblesIr4c||d<dS)Nrr0r6s r3rzPointcloud.visiblerJr4c|dS)z Sets the x coordinates. The 'x' property is an array that may be specified as a tuple, list, numpy array, or pandas Series Returns ------- numpy.ndarray rr0r1s r3rz Pointcloud.xCyr4c||d<dS)Nrr0r6s r3rz Pointcloud.xS r4c|dS)a  Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If "x" (the default value), the x coordinates refer to `layout.xaxis`. If "x2", the x coordinates refer to `layout.xaxis2`, and so on. The 'xaxis' property is an identifier of a particular subplot, of type 'x', that may be specified as the string 'x' optionally followed by an integer >= 1 (e.g. 'x', 'x1', 'x2', 'x3', etc.) Returns ------- str rr0r1s r3rzPointcloud.xaxis"G}r4c||d<dS)Nrr0r6s r3rzPointcloud.xaxis W r4c|dS)a} Specify `xbounds` in the shape of `[xMin, xMax] to avoid looping through the `xy` typed array. Use it in conjunction with `xy` and `ybounds` for the performance benefits. The 'xbounds' property is an array that may be specified as a tuple, list, numpy array, or pandas Series Returns ------- numpy.ndarray rr0r1s r3rzPointcloud.xboundsIr4c||d<dS)Nrr0r6s r3rzPointcloud.xbounds#rJr4c|dS)z Sets the source reference on Chart Studio Cloud for `xbounds`. The 'xboundssrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str r(r0r1s r3r(zPointcloud.xboundssrc)rLr4c||d<dS)Nr(r0r6s r3r(zPointcloud.xboundssrc7r8r4c|dS)z Sets the source reference on Chart Studio Cloud for `x`. The 'xsrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str rr0r1s r3rzPointcloud.xsrc=F|r4c||d<dS)Nrr0r6s r3rzPointcloud.xsrcKr]r4c|dS)a Faster alternative to specifying `x` and `y` separately. If supplied, it must be a typed `Float32Array` array that represents points such that `xy[i * 2] = x[i]` and `xy[i * 2 + 1] = y[i]` The 'xy' property is an array that may be specified as a tuple, list, numpy array, or pandas Series Returns ------- numpy.ndarray r r0r1s r3r z Pointcloud.xyQsDzr4c||d<dS)Nr r0r6s r3r z Pointcloud.xybsT r4c|dS)z Sets the source reference on Chart Studio Cloud for `xy`. The 'xysrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str rr0r1s r3rzPointcloud.xysrchsG}r4c||d<dS)Nrr0r6s r3rzPointcloud.xysrcvrzr4c|dS)z Sets the y coordinates. The 'y' property is an array that may be specified as a tuple, list, numpy array, or pandas Series Returns ------- numpy.ndarray r r0r1s r3r z Pointcloud.y|rtr4c||d<dS)Nr r0r6s r3r z Pointcloud.yrvr4c|dS)a  Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If "y" (the default value), the y coordinates refer to `layout.yaxis`. If "y2", the y coordinates refer to `layout.yaxis2`, and so on. The 'yaxis' property is an identifier of a particular subplot, of type 'y', that may be specified as the string 'y' optionally followed by an integer >= 1 (e.g. 'y', 'y1', 'y2', 'y3', etc.) Returns ------- str rr0r1s r3rzPointcloud.yaxisrxr4c||d<dS)Nrr0r6s r3rzPointcloud.yaxisrzr4c|dS)a} Specify `ybounds` in the shape of `[yMin, yMax] to avoid looping through the `xy` typed array. Use it in conjunction with `xy` and `xbounds` for the performance benefits. The 'ybounds' property is an array that may be specified as a tuple, list, numpy array, or pandas Series Returns ------- numpy.ndarray r r0r1s r3r zPointcloud.yboundsr|r4c||d<dS)Nr r0r6s r3r zPointcloud.yboundsrJr4c|dS)z Sets the source reference on Chart Studio Cloud for `ybounds`. The 'yboundssrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str r)r0r1s r3r)zPointcloud.yboundssrcrLr4c||d<dS)Nr)r0r6s r3r)zPointcloud.yboundssrcr8r4c|dS)z Sets the source reference on Chart Studio Cloud for `y`. The 'ysrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str rr0r1s r3rzPointcloud.ysrcrr4c||d<dS)Nrr0r6s r3rzPointcloud.ysrcr]r4c|jdS)Nr)_propsr1s r3rzPointcloud.types{6""r4cdS)Na ! customdata Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, "scatter" traces also appends customdata items in the markers DOM elements customdatasrc Sets the source reference on Chart Studio Cloud for `customdata`. hoverinfo Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired. hoverinfosrc Sets the source reference on Chart Studio Cloud for `hoverinfo`. hoverlabel :class:`plotly.graph_objects.pointcloud.Hoverlabel` instance or dict with compatible properties ids Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type. idssrc Sets the source reference on Chart Studio Cloud for `ids`. indices A sequential value, 0..n, supply it to avoid creating this array inside plotting. If specified, it must be a typed `Int32Array` array. Its length must be equal to or greater than the number of points. For the best performance and memory use, create one large `indices` typed array that is guaranteed to be at least as long as the largest number of points during use, and reuse it on each `Plotly.restyle()` call. indicessrc Sets the source reference on Chart Studio Cloud for `indices`. legend Sets the reference to a legend to show this trace in. References to these legends are "legend", "legend2", "legend3", etc. Settings for these legends are set in the layout, under `layout.legend`, `layout.legend2`, etc. legendgroup Sets the legend group for this trace. Traces and shapes part of the same legend group hide/show at the same time when toggling legend items. legendgrouptitle :class:`plotly.graph_objects.pointcloud.Legendgrouptitl e` instance or dict with compatible properties legendrank Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with "reversed" `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items. When having unranked or equal rank items shapes would be displayed after traces i.e. according to their order in data and layout. legendwidth Sets the width (in px or fraction) of the legend for this trace. marker :class:`plotly.graph_objects.pointcloud.Marker` instance or dict with compatible properties meta Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index. metasrc Sets the source reference on Chart Studio Cloud for `meta`. name Sets the trace name. The trace name appears as the legend item and on hover. opacity Sets the opacity of the trace. showlegend Determines whether or not an item corresponding to this trace is shown in the legend. stream :class:`plotly.graph_objects.pointcloud.Stream` instance or dict with compatible properties text Sets text elements associated with each (x,y) pair. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. If trace `hoverinfo` contains a "text" flag and "hovertext" is not set, these elements will be seen in the hover labels. textsrc Sets the source reference on Chart Studio Cloud for `text`. uid Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions. uirevision Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves. visible Determines whether or not this trace is visible. If "legendonly", the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible). x Sets the x coordinates. xaxis Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If "x" (the default value), the x coordinates refer to `layout.xaxis`. If "x2", the x coordinates refer to `layout.xaxis2`, and so on. xbounds Specify `xbounds` in the shape of `[xMin, xMax] to avoid looping through the `xy` typed array. Use it in conjunction with `xy` and `ybounds` for the performance benefits. xboundssrc Sets the source reference on Chart Studio Cloud for `xbounds`. xsrc Sets the source reference on Chart Studio Cloud for `x`. xy Faster alternative to specifying `x` and `y` separately. If supplied, it must be a typed `Float32Array` array that represents points such that `xy[i * 2] = x[i]` and `xy[i * 2 + 1] = y[i]` xysrc Sets the source reference on Chart Studio Cloud for `xy`. y Sets the y coordinates. yaxis Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If "y" (the default value), the y coordinates refer to `layout.yaxis`. If "y2", the y coordinates refer to `layout.yaxis2`, and so on. ybounds Specify `ybounds` in the shape of `[yMin, yMax] to avoid looping through the `xy` typed array. Use it in conjunction with `xy` and `xbounds` for the performance benefits. yboundssrc Sets the source reference on Chart Studio Cloud for `ybounds`. ysrc Sets the source reference on Chart Studio Cloud for `y`. r0r1s r3_prop_descriptionszPointcloud._prop_descriptionssr r r4Nc( tt|dd|(vr|(d|_dS|i}nct ||jr|}n9t |trtj |}ntd|( dd|_ |( dd|_ | d d})||n|)})|)|)|d <| d d})||n|)})|)|)|d <| d d})||n|)})|)|)|d <| d d})||n|)})|)|)|d <| d d})||n|)})|)|)|d <| dd})||n|)})|)|)|d<| dd})||n|)})|)|)|d<| dd})| | n|)})|)|)|d<| dd})| | n|)})|)|)|d<| dd})| | n|)})|)|)|d<| dd})| | n|)})|)|)|d<| dd})| | n|)})|)|)|d<| dd})||n|)})|)|)|d<| dd})||n|)})|)|)|d<| dd})||n|)})|)|)|d<| dd})||n|)})|)|)|d<| dd})||n|)})|)|)|d<| dd})||n|)})|)|)|d<| dd})||n|)})|)|)|d<| dd})||n|)})|)|)|d<| dd})||n|)})|)|)|d<| dd})||n|)})|)|)|d<| dd})||n|)})|)|)|d<| d d})||n|)})|)|)|d <| d!d})||n|)})|)|)|d!<| d"d})||n|)})|)|)|d"<| d#d})||n|)})|)|)|d#<| d$d})||n|)})|)|)|d$<| d%d})||n|)})|)|)|d%<| d&d})||n|)})|)|)|d&<| d'd})| | n|)})|)|)|d'<| d(d})|!|!n|)})|)|)|d(<| d)d})|"|"n|)})|)|)|d)<| d*d})|#|#n|)})|)|)|d*<| d+d})|$|$n|)})|)|)|d+<| d,d})|%|%n|)})|)|)|d,<| d-d})|&|&n|)})|)|)|d-<| d.d})|'|'n|)})|)|)|d.<d|jd/<| d/d|jd0it|fi|(d|_ dS)1a" Construct a new Pointcloud object "pointcloud" trace is deprecated! Please consider switching to the "scattergl" trace type. The data visualized as a point cloud set in `x` and `y` using the WebGl plotting engine. Parameters ---------- arg dict of properties compatible with this constructor or an instance of :class:`plotly.graph_objs.Pointcloud` customdata Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, "scatter" traces also appends customdata items in the markers DOM elements customdatasrc Sets the source reference on Chart Studio Cloud for `customdata`. hoverinfo Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired. hoverinfosrc Sets the source reference on Chart Studio Cloud for `hoverinfo`. hoverlabel :class:`plotly.graph_objects.pointcloud.Hoverlabel` instance or dict with compatible properties ids Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type. idssrc Sets the source reference on Chart Studio Cloud for `ids`. indices A sequential value, 0..n, supply it to avoid creating this array inside plotting. If specified, it must be a typed `Int32Array` array. Its length must be equal to or greater than the number of points. For the best performance and memory use, create one large `indices` typed array that is guaranteed to be at least as long as the largest number of points during use, and reuse it on each `Plotly.restyle()` call. indicessrc Sets the source reference on Chart Studio Cloud for `indices`. legend Sets the reference to a legend to show this trace in. References to these legends are "legend", "legend2", "legend3", etc. Settings for these legends are set in the layout, under `layout.legend`, `layout.legend2`, etc. legendgroup Sets the legend group for this trace. Traces and shapes part of the same legend group hide/show at the same time when toggling legend items. legendgrouptitle :class:`plotly.graph_objects.pointcloud.Legendgrouptitl e` instance or dict with compatible properties legendrank Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with "reversed" `legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items. When having unranked or equal rank items shapes would be displayed after traces i.e. according to their order in data and layout. legendwidth Sets the width (in px or fraction) of the legend for this trace. marker :class:`plotly.graph_objects.pointcloud.Marker` instance or dict with compatible properties meta Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace `name`, graph, axis and colorbar `title.text`, annotation `text` `rangeselector`, `updatemenues` and `sliders` `label` text all support `meta`. To access the trace `meta` values in an attribute in the same trace, simply use `%{meta[i]}` where `i` is the index or key of the `meta` item in question. To access trace `meta` in layout attributes, use `%{data[n[.meta[i]}` where `i` is the index or key of the `meta` and `n` is the trace index. metasrc Sets the source reference on Chart Studio Cloud for `meta`. name Sets the trace name. The trace name appears as the legend item and on hover. opacity Sets the opacity of the trace. showlegend Determines whether or not an item corresponding to this trace is shown in the legend. stream :class:`plotly.graph_objects.pointcloud.Stream` instance or dict with compatible properties text Sets text elements associated with each (x,y) pair. If a single string, the same string appears over all the data points. If an array of string, the items are mapped in order to the this trace's (x,y) coordinates. If trace `hoverinfo` contains a "text" flag and "hovertext" is not set, these elements will be seen in the hover labels. textsrc Sets the source reference on Chart Studio Cloud for `text`. uid Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions. uirevision Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves. visible Determines whether or not this trace is visible. If "legendonly", the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible). x Sets the x coordinates. xaxis Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If "x" (the default value), the x coordinates refer to `layout.xaxis`. If "x2", the x coordinates refer to `layout.xaxis2`, and so on. xbounds Specify `xbounds` in the shape of `[xMin, xMax] to avoid looping through the `xy` typed array. Use it in conjunction with `xy` and `ybounds` for the performance benefits. xboundssrc Sets the source reference on Chart Studio Cloud for `xbounds`. xsrc Sets the source reference on Chart Studio Cloud for `x`. xy Faster alternative to specifying `x` and `y` separately. If supplied, it must be a typed `Float32Array` array that represents points such that `xy[i * 2] = x[i]` and `xy[i * 2 + 1] = y[i]` xysrc Sets the source reference on Chart Studio Cloud for `xy`. y Sets the y coordinates. yaxis Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If "y" (the default value), the y coordinates refer to `layout.yaxis`. If "y2", the y coordinates refer to `layout.yaxis2`, and so on. ybounds Specify `ybounds` in the shape of `[yMin, yMax] to avoid looping through the `xy` typed array. Use it in conjunction with `xy` and `xbounds` for the performance benefits. yboundssrc Sets the source reference on Chart Studio Cloud for `ybounds`. ysrc Sets the source reference on Chart Studio Cloud for `y`. Returns ------- Pointcloud r_parentNzThe first argument to the plotly.graph_objs.Pointcloud constructor must be a dict or an instance of :class:`plotly.graph_objs.Pointcloud` skip_invalidF _validateTr"r-r!r,r#r rrr$rr*r.r%r+rr rrrr&rrrr r'rrrrr(rr rr rr r)rrr0)superr__init__r isinstance __class__to_plotly_jsondict_copycopy ValueErrorpop _skip_invalidrr_process_kwargs)+r2argr"r-r!r,r#r rrr$rr*r.r%r+rr rrrr&rrrr r'rrrrr(rr rr rr r)rkwargs_vrs+ r3rzPointcloud.__init__s@Z j$((666   !),DL F ;CC T^ , , $$&&CC T " " *S//CC8 $ZZ>>K66WW\4 ( (%1ZZr >!#D  WW_d + ++7]]R >$&D ! WW[$ ' '#/YYR > "D  WW^T * *)5\\2 >#%D WW\4 ( (%1ZZr >!#D  WWUD ! !OSS >DK WWXt $ $)VVr >DN WWY % %+WW > DO WW\4 ( (%1ZZr >!#D  WWXt $ $)VVr >DN WW]D ) )'3[[ >"$D  WW' . .!1!=  2 >')D# $ WW\4 ( (%1ZZr >!#D  WW]D ) )'3[[ >"$D  WWXt $ $)VVr >DN WWVT " "%TT2 >DL WWY % %+WW > DO WWVT " "%TT2 >DL WWY % %+WW > DO WW\4 ( (%1ZZr >!#D  WWXt $ $)VVr >DN WWVT " "%TT2 >DL WWY % %+WW > DO WWUD ! !OSS >DK WW\4 ( (%1ZZr >!#D  WWY % %+WW > DO WWS$  -QQR >DI WWWd # #'UUR >DM WWY % %+WW > DO WW\4 ( (%1ZZr >!#D  WWVT " "%TT2 >DL WWT4 >RRr >DJ WWWd # #'UUR >DM WWS$  -QQR >DI WWWd # #'UUR >DM WWY % %+WW > DO WW\4 ( (%1ZZr >!#D  WWVT " "%TT2 >DL + F  33tC22622333#r4)'NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN)2__name__ __module__ __qualname___parent_path_str _path_str _valid_propspropertyr"setterr-r!r,r#r rrr$rr*r.r%r+rr rrrr&rrrr r'rrrrr(rr rr rr r)rrrr __classcell__)rs@r3rrs I(((LX""X" !!!  % %X %$$$ !!X!&    $ $X $### 2"2"X2"h!!!   X  ZZ   X  ]] X& ^^  " "X "!!! X$ ]] ##X# """ ((X(*''' ""X"(!!!  # #X #""" //X/b ]] X* [[   X  ^^   X  [[   X  ^^  " "X "!!! X4 ]] X( [[   X  ^^   X  ZZ ""X"4!!! X  ^^   X XX X$ \\   X  ^^  " "X "!!!   X  [[ X YY   X  \\   X XX X$ \\   X  ^^  " "X "!!!   X  [[ ##X# s s Xs n           Qo#o#o#o#o#o#o#o#o#o#r4r)plotly.basedatatypesr_BaseTraceTyperrrr0r4r3rsa@@@@@@M#M#M#M#M#M#M#M#M#M#r4