*L i.ddlmZddlZGddeZy)) BaseTraceTypeNc eZdZdZdZhdZedZejdZedZ 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.e.jdQZ.edRZ/e/jdSZ/edTZ0e0jdUZ0edVZ1e1jdWZ1edXZ2e2jdYZ2edZZ3e3jd[Z3ed\Z4e4jd]Z4ed^Z5e5jd_Z5ed`Z6e6jdaZ6edbZ7e7jdcZ7eddZ8e8jdeZ8edfZ9e9jdgZ9edhZ:e:jdiZ:edjZ;e;jdkZ;edlZ dqfdp Z?xZ@S)rScatterternaryscatterternary>6abcidssumuidasrcbsrccsrcfilllinemetamodenametexttypeidssrclegendmarkerstreamhoveronmetasrcopacitysubplottextsrcvisibleselectedtextfont fillcolor hoverinfo hovertext cliponaxis customdata hoverlabel legendrank showlegend uirevision unselected connectgaps legendgroup legendwidth hoverinfosrc hovertextsrc textposition texttemplate customdatasrc hovertemplateselectedpointstextpositionsrctexttemplatesrchovertemplatesrclegendgrouptitletexttemplatefallbackhovertemplatefallbackc |dS)a Sets the quantity of component `a` in each data point. If `a`, `b`, and `c` are all provided, they need not be normalized, only the relative values matter. If only two arrays are provided they must be normalized to match `ternary.sum`. The 'a' property is an array that may be specified as a tuple, list, numpy array, or pandas Series Returns ------- numpy.ndarray rselfs g/mnt/ssd/data/python-lab/Trading/venv/lib/python3.12/site-packages/plotly/graph_objs/_scatterternary.pyrzScatterternary.aDCyc||d<y)Nrr?rAvals rBrzScatterternary.aU S rDc |dS)z Sets the source reference on Chart Studio Cloud for `a`. The 'asrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str rr?r@s rBrzScatterternary.asrcYF|rDc||d<y)Nrr?rFs rBrzScatterternary.asrcg V rDc |dS)a Sets the quantity of component `a` in each data point. If `a`, `b`, and `c` are all provided, they need not be normalized, only the relative values matter. If only two arrays are provided they must be normalized to match `ternary.sum`. The 'b' property is an array that may be specified as a tuple, list, numpy array, or pandas Series Returns ------- numpy.ndarray r r?r@s rBr zScatterternary.bkrCrDc||d<y)Nr r?rFs rBr zScatterternary.b|rHrDc |dS)z Sets the source reference on Chart Studio Cloud for `b`. The 'bsrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str rr?r@s rBrzScatterternary.bsrcrJrDc||d<y)Nrr?rFs rBrzScatterternary.bsrcrLrDc |dS)a Sets the quantity of component `a` in each data point. If `a`, `b`, and `c` are all provided, they need not be normalized, only the relative values matter. If only two arrays are provided they must be normalized to match `ternary.sum`. The 'c' property is an array that may be specified as a tuple, list, numpy array, or pandas Series Returns ------- numpy.ndarray r r?r@s rBr zScatterternary.crCrDc||d<y)Nr r?rFs rBr zScatterternary.crHrDc |dS)a Determines whether or not markers and text nodes are clipped about the subplot axes. To show markers and text nodes above axis lines and tick labels, make sure to set `xaxis.layer` and `yaxis.layer` to *below traces*. The 'cliponaxis' property must be specified as a bool (either True, or False) Returns ------- bool r'r?r@s rBr'zScatterternary.cliponaxisL!!rDc||d<y)Nr'r?rFs rBr'zScatterternary.cliponaxis  \rDc |dS)a Determines whether or not gaps (i.e. {nan} or missing values) in the provided data arrays are connected. The 'connectgaps' property must be specified as a bool (either True, or False) Returns ------- bool r.r?r@s rBr.zScatterternary.connectgapsM""rDc||d<y)Nr.r?rFs rBr.zScatterternary.connectgaps !]rDc |dS)z Sets the source reference on Chart Studio Cloud for `c`. The 'csrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str rr?r@s rBrzScatterternary.csrcrJrDc||d<y)Nrr?rFs rBrzScatterternary.csrcrLrDc |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(r?r@s rBr(zScatterternary.customdatarTrDc||d<y)Nr(r?rFs rBr(zScatterternary.customdatarVrDc |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 r5r?r@s rBr5zScatterternary.customdatasrcsO$$rDc||d<y)Nr5r?rFs rBr5zScatterternary.customdatasrc #_rDc |dS)a Sets the area to fill with a solid color. Use with `fillcolor` if not "none". scatterternary has a subset of the options available to scatter. "toself" connects the endpoints of the trace (or each segment of the trace if it has gaps) into a closed shape. "tonext" fills the space between two traces if one completely encloses the other (eg consecutive contour lines), and behaves like "toself" if there is no trace before it. "tonext" should not be used if one trace does not enclose the other. The 'fill' property is an enumeration that may be specified as: - One of the following enumeration values: ['none', 'toself', 'tonext'] Returns ------- Any rr?r@s rBrzScatterternary.fill s*F|rDc||d<y)Nrr?rFs rBrzScatterternary.fill rLrDc |dS)aC Sets the fill color. Defaults to a half-transparent variant of the line color, marker color, or marker line color, whichever is available. The 'fillcolor' property is a color and may be specified as: - A hex string (e.g. '#ff0000') - An rgb/rgba string (e.g. 'rgb(255,0,0)') - An hsl/hsla string (e.g. 'hsl(0,100%,50%)') - An hsv/hsva string (e.g. 'hsv(0,100%,100%)') - A named CSS color: see https://plotly.com/python/css-colors/ for a list Returns ------- str r$r?r@s rBr$zScatterternary.fillcolor$$K  rDc||d<y)Nr$r?rFs rBr$zScatterternary.fillcolor8 [rDc |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 ['a', 'b', 'c', 'text', 'name'] joined with '+' characters (e.g. 'a+b') OR exactly one of ['all', 'none', 'skip'] (e.g. 'skip') - A list or array of the above Returns ------- Any|numpy.ndarray r%r?r@s rBr%zScatterternary.hoverinfo<rerDc||d<y)Nr%r?rFs rBr%zScatterternary.hoverinfoPrgrDc |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 r1r?r@s rBr1zScatterternary.hoverinfosrcTN##rDc||d<y)Nr1r?rFs rBr1zScatterternary.hoverinfosrcc "^rDc |dS)a{ The 'hoverlabel' property is an instance of Hoverlabel that may be specified as: - An instance of :class:`plotly.graph_objs.scatterternary.Hoverlabel` - A dict of string/value properties that will be passed to the Hoverlabel constructor Returns ------- plotly.graph_objs.scatterternary.Hoverlabel r)r?r@s rBr)zScatterternary.hoverlabelgL!!rDc||d<y)Nr)r?rFs rBr)zScatterternary.hoverlabelvrVrDc |dS)a Do the hover effects highlight individual points (markers or line points) or do they highlight filled regions? If the fill is "toself" or "tonext" and there are no markers or text, then the default is "fills", otherwise it is "points". The 'hoveron' property is a flaglist and may be specified as a string containing: - Any combination of ['points', 'fills'] joined with '+' characters (e.g. 'points+fills') Returns ------- Any rr?r@s rBrzScatterternary.hoveronz"IrDc||d<y)Nrr?rFs rBrzScatterternary.hoveron YrDc |dS)aK Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, "xother" will be added to those with different x positions from the first point. An underscore before or after "(x|y)other" will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time- format/tree/v2.2.3#locale_format for details on the date formatting syntax. Variables that can't be found will be replaced with the specifier. For example, a template of "data: %{x}, %{y}" will result in a value of "data: 1, %{y}" if x is 1 and y is missing. Variables with an undefined value will be replaced with the fallback value. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event- data. Additionally, all attributes that can be specified per- point (the ones that are `arrayOk: true`) are available. Anything contained in tag `` is displayed in the secondary box, for example `%{fullData.name}`. To hide the secondary box completely, use an empty tag ``. The 'hovertemplate' 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 r6r?r@s rBr6zScatterternary.hovertemplatesRO$$rDc||d<y)Nr6r?rFs rBr6zScatterternary.hovertemplaterarDc |dS)aS Fallback string that's displayed when a variable referenced in a template is missing. If the boolean value 'false' is passed in, the specifier with the missing variable will be displayed. The 'hovertemplatefallback' property accepts values of any type Returns ------- Any r=r?r@s rBr=z$Scatterternary.hovertemplatefallbacks+,,rDc||d<y)Nr=r?rFs rBr=z$Scatterternary.hovertemplatefallbacks (+ $%rDc |dS)a Sets the source reference on Chart Studio Cloud for `hovertemplate`. The 'hovertemplatesrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str r:r?r@s rBr:zScatterternary.hovertemplatesrc&''rDc||d<y)Nr:r?rFs rBr:zScatterternary.hovertemplatesrc #&  rDc |dS)a^ Sets hover text elements associated with each (a,b,c) point. If a single string, the same string appears over all the data points. If an array of strings, the items are mapped in order to the the data points in (a,b,c). To be seen, trace `hoverinfo` must contain a "text" flag. The 'hovertext' 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 r&r?r@s rBr&zScatterternary.hovertextrerDc||d<y)Nr&r?rFs rBr&zScatterternary.hovertextrgrDc |dS)z Sets the source reference on Chart Studio Cloud for `hovertext`. The 'hovertextsrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str r2r?r@s rBr2zScatterternary.hovertextsrcrkrDc||d<y)Nr2r?rFs rBr2zScatterternary.hovertextsrc rmrDc |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 r?r@s rBr zScatterternary.idsE{rDc||d<y)Nr r?rFs rBr zScatterternary.ids! U rDc |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 rr?r@s rBrzScatterternary.idssrc%sH~rDc||d<y)Nrr?rFs rBrzScatterternary.idssrc3 XrDc |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 rr?r@s rBrzScatterternary.legend7s"H~rDc||d<y)Nrr?rFs rBrzScatterternary.legendJrrDc |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/r?r@s rBr/zScatterternary.legendgroupNsM""rDc||d<y)Nr/r?rFs rBr/zScatterternary.legendgroup_rZrDc |dS)a The 'legendgrouptitle' property is an instance of Legendgrouptitle that may be specified as: - An instance of :class:`plotly.graph_objs.scatterternary.Legendgrouptitle` - A dict of string/value properties that will be passed to the Legendgrouptitle constructor Returns ------- plotly.graph_objs.scatterternary.Legendgrouptitle r;r?r@s rBr;zScatterternary.legendgrouptitlecrzrDc||d<y)Nr;r?rFs rBr;zScatterternary.legendgrouptitlerr|rDc |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*r?r@s rBr*zScatterternary.legendrankvs&L!!rDc||d<y)Nr*r?rFs rBr*zScatterternary.legendrankrVrDc |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 r0r?r@s rBr0zScatterternary.legendwidthrXrDc||d<y)Nr0r?rFs rBr0zScatterternary.legendwidthrZrDc |dS)a] The 'line' property is an instance of Line that may be specified as: - An instance of :class:`plotly.graph_objs.scatterternary.Line` - A dict of string/value properties that will be passed to the Line constructor Returns ------- plotly.graph_objs.scatterternary.Line rr?r@s rBrzScatterternary.linesF|rDc||d<y)Nrr?rFs rBrzScatterternary.linerLrDc |dS)ag The 'marker' property is an instance of Marker that may be specified as: - An instance of :class:`plotly.graph_objs.scatterternary.Marker` - A dict of string/value properties that will be passed to the Marker constructor Returns ------- plotly.graph_objs.scatterternary.Marker rr?r@s rBrzScatterternary.markerH~rDc||d<y)Nrr?rFs rBrzScatterternary.markerrrDc |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 rr?r@s rBrzScatterternary.meta(F|rDc||d<y)Nrr?rFs rBrzScatterternary.metarLrDc |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 rr?r@s rBrzScatterternary.metasrcIrDc||d<y)Nrr?rFs rBrzScatterternary.metasrcrtrDc |dS)a Determines the drawing mode for this scatter trace. If the provided `mode` includes "text" then the `text` elements appear at the coordinates. Otherwise, the `text` elements appear on hover. If there are less than 20 points and the trace is not stacked then the default is "lines+markers". Otherwise, "lines". The 'mode' property is a flaglist and may be specified as a string containing: - Any combination of ['lines', 'markers', 'text'] joined with '+' characters (e.g. 'lines+markers') OR exactly one of ['none'] (e.g. 'none') Returns ------- Any rr?r@s rBrzScatterternary.moderrDc||d<y)Nrr?rFs rBrzScatterternary.mode rLrDc |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 rr?r@s rBrzScatterternary.namesF|rDc||d<y)Nrr?rFs rBrzScatterternary.namerLrDc |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 rr?r@s rBrzScatterternary.opacity"rrDc||d<y)Nrr?rFs rBrzScatterternary.opacity0rtrDc |dS)aq The 'selected' property is an instance of Selected that may be specified as: - An instance of :class:`plotly.graph_objs.scatterternary.Selected` - A dict of string/value properties that will be passed to the Selected constructor Returns ------- plotly.graph_objs.scatterternary.Selected r"r?r@s rBr"zScatterternary.selected4sJrDc||d<y)Nr"r?rFs rBr"zScatterternary.selectedC ZrDc |dS)a Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect. The 'selectedpoints' property accepts values of any type Returns ------- Any r7r?r@s rBr7zScatterternary.selectedpointsGs $%%rDc||d<y)Nr7r?rFs rBr7zScatterternary.selectedpointsYs !$ rDc |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+r?r@s rBr+zScatterternary.showlegend]rorDc||d<y)Nr+r?rFs rBr+zScatterternary.showlegendlrVrDc |dS)ag The 'stream' property is an instance of Stream that may be specified as: - An instance of :class:`plotly.graph_objs.scatterternary.Stream` - A dict of string/value properties that will be passed to the Stream constructor Returns ------- plotly.graph_objs.scatterternary.Stream rr?r@s rBrzScatterternary.streamprrDc||d<y)Nrr?rFs rBrzScatterternary.streamrrDc |dS)a. Sets a reference between this trace's data coordinates and a ternary subplot. If "ternary" (the default value), the data refer to `layout.ternary`. If "ternary2", the data refer to `layout.ternary2`, and so on. The 'subplot' property is an identifier of a particular subplot, of type 'ternary', that may be specified as the string 'ternary' optionally followed by an integer >= 1 (e.g. 'ternary', 'ternary1', 'ternary2', 'ternary3', etc.) Returns ------- str rr?r@s rBrzScatterternary.subplotrrrDc||d<y)Nrr?rFs rBrzScatterternary.subplotrtrDc |dS)a The number each triplet should sum to, if only two of `a`, `b`, and `c` are provided. This overrides `ternary.sum` to normalize this specific trace, but does not affect the values displayed on the axes. 0 (or missing) means to use ternary.sum The 'sum' property is a number and may be specified as: - An int or float in the interval [0, inf] Returns ------- int|float r r?r@s rBr zScatterternary.sums E{rDc||d<y)Nr r?rFs rBr zScatterternary.sumrrDc |dS)a Sets text elements associated with each (a,b,c) point. If a single string, the same string appears over all the data points. If an array of strings, the items are mapped in order to the the data points in (a,b,c). 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 rr?r@s rBrzScatterternary.texts&F|rDc||d<y)Nrr?rFs rBrzScatterternary.textrLrDc |dS)a Sets the text font. The 'textfont' property is an instance of Textfont that may be specified as: - An instance of :class:`plotly.graph_objs.scatterternary.Textfont` - A dict of string/value properties that will be passed to the Textfont constructor Returns ------- plotly.graph_objs.scatterternary.Textfont r#r?r@s rBr#zScatterternary.textfontsJrDc||d<y)Nr#r?rFs rBr#zScatterternary.textfontrrDc |dS)a+ Sets the positions of the `text` elements with respects to the (x,y) coordinates. The 'textposition' property is an enumeration that may be specified as: - One of the following enumeration values: ['top left', 'top center', 'top right', 'middle left', 'middle center', 'middle right', 'bottom left', 'bottom center', 'bottom right'] - A tuple, list, or one-dimensional numpy array of the above Returns ------- Any|numpy.ndarray r3r?r@s rBr3zScatterternary.textpositions"N##rDc||d<y)Nr3r?rFs rBr3zScatterternary.textpositionrmrDc |dS)z Sets the source reference on Chart Studio Cloud for `textposition`. The 'textpositionsrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str r8r?r@s rBr8zScatterternary.textpositionsrc%&&rDc||d<y)Nr8r?rFs rBr8zScatterternary.textpositionsrc "% rDc |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 r r?r@s rBr zScatterternary.textsrcrrDc||d<y)Nr r?rFs rBr zScatterternary.textsrcrtrDc |dS)a Template string used for rendering the information text that appears on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time- format/tree/v2.2.3#locale_format for details on the date formatting syntax. Variables that can't be found will be replaced with the specifier. For example, a template of "data: %{x}, %{y}" will result in a value of "data: 1, %{y}" if x is 1 and y is missing. Variables with an undefined value will be replaced with the fallback value. All attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Finally, the template string has access to variables `a`, `b`, `c` and `text`. The 'texttemplate' 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 r4r?r@s rBr4zScatterternary.texttemplates>N##rDc||d<y)Nr4r?rFs rBr4zScatterternary.texttemplate;rmrDc |dS)aR Fallback string that's displayed when a variable referenced in a template is missing. If the boolean value 'false' is passed in, the specifier with the missing variable will be displayed. The 'texttemplatefallback' property accepts values of any type Returns ------- Any r<r?r@s rBr<z#Scatterternary.texttemplatefallback?s*++rDc||d<y)Nr<r?rFs rBr<z#Scatterternary.texttemplatefallbackNs '* #$rDc |dS)z Sets the source reference on Chart Studio Cloud for `texttemplate`. The 'texttemplatesrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str r9r?r@s rBr9zScatterternary.texttemplatesrcRrrDc||d<y)Nr9r?rFs rBr9zScatterternary.texttemplatesrcarrDc |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 r?r@s rBr zScatterternary.uiderrDc||d<y)Nr r?rFs rBr zScatterternary.uidurrDc |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,r?r@s rBr,zScatterternary.uirevisionys2L!!rDc||d<y)Nr,r?rFs rBr,zScatterternary.uirevisionrVrDc |dS)a{ The 'unselected' property is an instance of Unselected that may be specified as: - An instance of :class:`plotly.graph_objs.scatterternary.Unselected` - A dict of string/value properties that will be passed to the Unselected constructor Returns ------- plotly.graph_objs.scatterternary.Unselected r-r?r@s rBr-zScatterternary.unselectedrorDc||d<y)Nr-r?rFs rBr-zScatterternary.unselectedrVrDc |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 r!r?r@s rBr!zScatterternary.visiblesIrDc||d<y)Nr!r?rFs rBr!zScatterternary.visiblertrDc |jdS)Nr)_propsr@s rBrzScatterternary.types{{6""rDcy)Na< a Sets the quantity of component `a` in each data point. If `a`, `b`, and `c` are all provided, they need not be normalized, only the relative values matter. If only two arrays are provided they must be normalized to match `ternary.sum`. asrc Sets the source reference on Chart Studio Cloud for `a`. b Sets the quantity of component `a` in each data point. If `a`, `b`, and `c` are all provided, they need not be normalized, only the relative values matter. If only two arrays are provided they must be normalized to match `ternary.sum`. bsrc Sets the source reference on Chart Studio Cloud for `b`. c Sets the quantity of component `a` in each data point. If `a`, `b`, and `c` are all provided, they need not be normalized, only the relative values matter. If only two arrays are provided they must be normalized to match `ternary.sum`. cliponaxis Determines whether or not markers and text nodes are clipped about the subplot axes. To show markers and text nodes above axis lines and tick labels, make sure to set `xaxis.layer` and `yaxis.layer` to *below traces*. connectgaps Determines whether or not gaps (i.e. {nan} or missing values) in the provided data arrays are connected. csrc Sets the source reference on Chart Studio Cloud for `c`. 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`. fill Sets the area to fill with a solid color. Use with `fillcolor` if not "none". scatterternary has a subset of the options available to scatter. "toself" connects the endpoints of the trace (or each segment of the trace if it has gaps) into a closed shape. "tonext" fills the space between two traces if one completely encloses the other (eg consecutive contour lines), and behaves like "toself" if there is no trace before it. "tonext" should not be used if one trace does not enclose the other. fillcolor Sets the fill color. Defaults to a half-transparent variant of the line color, marker color, or marker line color, whichever is available. 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.scatterternary.Hoverlabel` instance or dict with compatible properties hoveron Do the hover effects highlight individual points (markers or line points) or do they highlight filled regions? If the fill is "toself" or "tonext" and there are no markers or text, then the default is "fills", otherwise it is "points". hovertemplate Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, "xother" will be added to those with different x positions from the first point. An underscore before or after "(x|y)other" will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time- format/tree/v2.2.3#locale_format for details on the date formatting syntax. Variables that can't be found will be replaced with the specifier. For example, a template of "data: %{x}, %{y}" will result in a value of "data: 1, %{y}" if x is 1 and y is missing. Variables with an undefined value will be replaced with the fallback value. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event- data. Additionally, all attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `` is displayed in the secondary box, for example `%{fullData.name}`. To hide the secondary box completely, use an empty tag ``. hovertemplatefallback Fallback string that's displayed when a variable referenced in a template is missing. If the boolean value 'false' is passed in, the specifier with the missing variable will be displayed. hovertemplatesrc Sets the source reference on Chart Studio Cloud for `hovertemplate`. hovertext Sets hover text elements associated with each (a,b,c) point. If a single string, the same string appears over all the data points. If an array of strings, the items are mapped in order to the the data points in (a,b,c). To be seen, trace `hoverinfo` must contain a "text" flag. hovertextsrc Sets the source reference on Chart Studio Cloud for `hovertext`. 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`. 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.scatterternary.Legendgroup title` 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. line :class:`plotly.graph_objects.scatterternary.Line` instance or dict with compatible properties marker :class:`plotly.graph_objects.scatterternary.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`. mode Determines the drawing mode for this scatter trace. If the provided `mode` includes "text" then the `text` elements appear at the coordinates. Otherwise, the `text` elements appear on hover. If there are less than 20 points and the trace is not stacked then the default is "lines+markers". Otherwise, "lines". name Sets the trace name. The trace name appears as the legend item and on hover. opacity Sets the opacity of the trace. selected :class:`plotly.graph_objects.scatterternary.Selected` instance or dict with compatible properties selectedpoints Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect. showlegend Determines whether or not an item corresponding to this trace is shown in the legend. stream :class:`plotly.graph_objects.scatterternary.Stream` instance or dict with compatible properties subplot Sets a reference between this trace's data coordinates and a ternary subplot. If "ternary" (the default value), the data refer to `layout.ternary`. If "ternary2", the data refer to `layout.ternary2`, and so on. sum The number each triplet should sum to, if only two of `a`, `b`, and `c` are provided. This overrides `ternary.sum` to normalize this specific trace, but does not affect the values displayed on the axes. 0 (or missing) means to use ternary.sum text Sets text elements associated with each (a,b,c) point. If a single string, the same string appears over all the data points. If an array of strings, the items are mapped in order to the the data points in (a,b,c). If trace `hoverinfo` contains a "text" flag and "hovertext" is not set, these elements will be seen in the hover labels. textfont Sets the text font. textposition Sets the positions of the `text` elements with respects to the (x,y) coordinates. textpositionsrc Sets the source reference on Chart Studio Cloud for `textposition`. textsrc Sets the source reference on Chart Studio Cloud for `text`. texttemplate Template string used for rendering the information text that appears on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time- format/tree/v2.2.3#locale_format for details on the date formatting syntax. Variables that can't be found will be replaced with the specifier. For example, a template of "data: %{x}, %{y}" will result in a value of "data: 1, %{y}" if x is 1 and y is missing. Variables with an undefined value will be replaced with the fallback value. All attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Finally, the template string has access to variables `a`, `b`, `c` and `text`. texttemplatefallback Fallback string that's displayed when a variable referenced in a template is missing. If the boolean value 'false' is passed in, the specifier with the missing variable will be displayed. texttemplatesrc Sets the source reference on Chart Studio Cloud for `texttemplate`. 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. unselected :class:`plotly.graph_objects.scatterternary.Unselected` instance or dict with compatible properties 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). r?r@s rB_prop_descriptionsz!Scatterternary._prop_descriptionssp rDc7 t8|dd|7vr |7d|_y|i}nXt||jr|j }n1t|t rtj|}n td|7jdd|_ |7jdd|_ |jd |||jd |||jd |||jd |||jd |||jd|||jd|||jd|| |jd|| |jd|| |jd|| |jd|| |jd|||jd|||jd|||jd|||jd|||jd|||jd|||jd|||jd|||jd|||jd|||jd |||jd!|||jd"|||jd#|||jd$|||jd%|||jd&|||jd'|| |jd(||!|jd)||"|jd*||#|jd+||$|jd,||%|jd-||&|jd.||'|jd/||(|jd0||)|jd1||*|jd2||+|jd3||,|jd4||-|jd5||.|jd6||/|jd7||0|jd8||1|jd9||2|jd:||3|jd;||4|jd<||5|jd=||6d|jd><|jd>d|jd?it |fi|7d|_ y)@af> Construct a new Scatterternary object Provides similar functionality to the "scatter" type but on a ternary phase diagram. The data is provided by at least two arrays out of `a`, `b`, `c` triplets. Parameters ---------- arg dict of properties compatible with this constructor or an instance of :class:`plotly.graph_objs.Scatterternary` a Sets the quantity of component `a` in each data point. If `a`, `b`, and `c` are all provided, they need not be normalized, only the relative values matter. If only two arrays are provided they must be normalized to match `ternary.sum`. asrc Sets the source reference on Chart Studio Cloud for `a`. b Sets the quantity of component `a` in each data point. If `a`, `b`, and `c` are all provided, they need not be normalized, only the relative values matter. If only two arrays are provided they must be normalized to match `ternary.sum`. bsrc Sets the source reference on Chart Studio Cloud for `b`. c Sets the quantity of component `a` in each data point. If `a`, `b`, and `c` are all provided, they need not be normalized, only the relative values matter. If only two arrays are provided they must be normalized to match `ternary.sum`. cliponaxis Determines whether or not markers and text nodes are clipped about the subplot axes. To show markers and text nodes above axis lines and tick labels, make sure to set `xaxis.layer` and `yaxis.layer` to *below traces*. connectgaps Determines whether or not gaps (i.e. {nan} or missing values) in the provided data arrays are connected. csrc Sets the source reference on Chart Studio Cloud for `c`. 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`. fill Sets the area to fill with a solid color. Use with `fillcolor` if not "none". scatterternary has a subset of the options available to scatter. "toself" connects the endpoints of the trace (or each segment of the trace if it has gaps) into a closed shape. "tonext" fills the space between two traces if one completely encloses the other (eg consecutive contour lines), and behaves like "toself" if there is no trace before it. "tonext" should not be used if one trace does not enclose the other. fillcolor Sets the fill color. Defaults to a half-transparent variant of the line color, marker color, or marker line color, whichever is available. 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.scatterternary.Hoverlabel` instance or dict with compatible properties hoveron Do the hover effects highlight individual points (markers or line points) or do they highlight filled regions? If the fill is "toself" or "tonext" and there are no markers or text, then the default is "fills", otherwise it is "points". hovertemplate Template string used for rendering the information that appear on hover box. Note that this will override `hoverinfo`. Variables are inserted using %{variable}, for example "y: %{y}" as well as %{xother}, {%_xother}, {%_xother_}, {%xother_}. When showing info for several points, "xother" will be added to those with different x positions from the first point. An underscore before or after "(x|y)other" will add a space on that side, only when this field is shown. Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time- format/tree/v2.2.3#locale_format for details on the date formatting syntax. Variables that can't be found will be replaced with the specifier. For example, a template of "data: %{x}, %{y}" will result in a value of "data: 1, %{y}" if x is 1 and y is missing. Variables with an undefined value will be replaced with the fallback value. The variables available in `hovertemplate` are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event- data. Additionally, all attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Anything contained in tag `` is displayed in the secondary box, for example `%{fullData.name}`. To hide the secondary box completely, use an empty tag ``. hovertemplatefallback Fallback string that's displayed when a variable referenced in a template is missing. If the boolean value 'false' is passed in, the specifier with the missing variable will be displayed. hovertemplatesrc Sets the source reference on Chart Studio Cloud for `hovertemplate`. hovertext Sets hover text elements associated with each (a,b,c) point. If a single string, the same string appears over all the data points. If an array of strings, the items are mapped in order to the the data points in (a,b,c). To be seen, trace `hoverinfo` must contain a "text" flag. hovertextsrc Sets the source reference on Chart Studio Cloud for `hovertext`. 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`. 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.scatterternary.Legendgroup title` 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. line :class:`plotly.graph_objects.scatterternary.Line` instance or dict with compatible properties marker :class:`plotly.graph_objects.scatterternary.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`. mode Determines the drawing mode for this scatter trace. If the provided `mode` includes "text" then the `text` elements appear at the coordinates. Otherwise, the `text` elements appear on hover. If there are less than 20 points and the trace is not stacked then the default is "lines+markers". Otherwise, "lines". name Sets the trace name. The trace name appears as the legend item and on hover. opacity Sets the opacity of the trace. selected :class:`plotly.graph_objects.scatterternary.Selected` instance or dict with compatible properties selectedpoints Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect. showlegend Determines whether or not an item corresponding to this trace is shown in the legend. stream :class:`plotly.graph_objects.scatterternary.Stream` instance or dict with compatible properties subplot Sets a reference between this trace's data coordinates and a ternary subplot. If "ternary" (the default value), the data refer to `layout.ternary`. If "ternary2", the data refer to `layout.ternary2`, and so on. sum The number each triplet should sum to, if only two of `a`, `b`, and `c` are provided. This overrides `ternary.sum` to normalize this specific trace, but does not affect the values displayed on the axes. 0 (or missing) means to use ternary.sum text Sets text elements associated with each (a,b,c) point. If a single string, the same string appears over all the data points. If an array of strings, the items are mapped in order to the the data points in (a,b,c). If trace `hoverinfo` contains a "text" flag and "hovertext" is not set, these elements will be seen in the hover labels. textfont Sets the text font. textposition Sets the positions of the `text` elements with respects to the (x,y) coordinates. textpositionsrc Sets the source reference on Chart Studio Cloud for `textposition`. textsrc Sets the source reference on Chart Studio Cloud for `text`. texttemplate Template string used for rendering the information text that appears on points. Note that this will override `textinfo`. Variables are inserted using %{variable}, for example "y: %{y}". Numbers are formatted using d3-format's syntax %{variable:d3-format}, for example "Price: %{y:$.2f}". https://github.com/d3/d3-format/tree/v1.4.5#d3-format for details on the formatting syntax. Dates are formatted using d3-time-format's syntax %{variable|d3-time-format}, for example "Day: %{2019-01-01|%A}". https://github.com/d3/d3-time- format/tree/v2.2.3#locale_format for details on the date formatting syntax. Variables that can't be found will be replaced with the specifier. For example, a template of "data: %{x}, %{y}" will result in a value of "data: 1, %{y}" if x is 1 and y is missing. Variables with an undefined value will be replaced with the fallback value. All attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Finally, the template string has access to variables `a`, `b`, `c` and `text`. texttemplatefallback Fallback string that's displayed when a variable referenced in a template is missing. If the boolean value 'false' is passed in, the specifier with the missing variable will be displayed. texttemplatesrc Sets the source reference on Chart Studio Cloud for `texttemplate`. 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. unselected :class:`plotly.graph_objects.scatterternary.Unselected` instance or dict with compatible properties 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). Returns ------- Scatterternary r_parentNzThe first argument to the plotly.graph_objs.Scatterternary constructor must be a dict or an instance of :class:`plotly.graph_objs.Scatterternary` skip_invalidF _validateTrrr rr r'r.rr(r5rr$r%r1r)rr6r=r:r&r2r rrr/r;r*r0rrrrrrrr"r7r+rrr rr#r3r8r r4r<r9r r,r-r!rr?)super__init__r isinstance __class__to_plotly_jsondict_copycopy ValueErrorpop _skip_invalidr _set_propertyr_process_kwargs)9rAargrrr rr r'r.rr(r5rr$r%r1r)rr6r=r:r&r2r rrr/r;r*r0rrrrrrrr"r7r+rrr rr#r3r8r r4r<r9r r,r-r!kwargsrs9 rBrzScatterternary.__init__sv )*  !),DL  ;C T^^ ,$$&C T "**S/C<= = $ZZ>K6 3Q' 63- 3Q' 63- 3Q' <j9 =#{; 63- <j9 ?C? 63- ;Y7 ;Y7 >3 = <j9 9c73 ?C? 2C9NO -s4DE ;Y7 >3 = 5#s+ 8S&1 8S&1 =#{; -s4DE <j9 =#{; 63- 8S&1 63- 9c73 63- 63- 9c73 :sH5 +S.A <j9 8S&1 9c73 5#s+ 63- :sH5 >3 = ,c?C 9c73 >3 = 138LM ,c?C 5#s+ <j9 <j9 9c73. F 3tC2623"rD)6NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN)A__name__ __module__ __qualname___parent_path_str _path_str _valid_propspropertyrsetterrr rr r'r.rr(r5rr$r%r1r)rr6r=r:r&r2r rrr/r;r*r0rrrrrrrr"r7r+rrr rr#r3r8r r4r<r9r r,r-r!rrr __classcell__)rs@rBrrsD  I7Lr XX   [[ XX   [[ XX"" !! # #""   [["" !! % %$$, [[!!&  !!&   $ $## " "!!$ ^^(%(%T$$ - -!!,", ( (''!!&   $ $##   ZZ   ]]$ ]]## "" ( (''""(!! # #""   [[   ]]* [[   ^^* [[   [[   ^^    __&&"%% " "!!   ]]$ ^^" ZZ( [[  __$$$## ' '&&   ^^$$@## , ,  +!+ ' '&&   ZZ""4!! " "!!  ^^##q q j        "       ! oH#H#rDr)plotly.basedatatypesr_BaseTraceTyperrrr?rDrBrsAx#^x#rD