-Phd6ddlmZddlZGddeZdS)) 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 drfdq Z?xZ@S)sPiepie>6idsuidholemetanamepullsorttexttypetitledlabeldomainidssrclabel0labelslegendmarkerstreamvaluesmetasrcopacitypullsrctextsrcvisiblerotationtextfonttextinfo direction hoverinfo hovertext labelssrc valuessrc automargin customdata hoverlabel legendrank scalegroup showlegend uirevision legendgroup legendwidth hoverinfosrc hovertextsrc textposition texttemplate customdatasrc hovertemplateinsidetextfontoutsidetextfonttextpositionsrctexttemplatesrchovertemplatesrclegendgrouptitleinsidetextorientationc|dS)z Determines whether outside text labels can push the margins. The 'automargin' property must be specified as a bool (either True, or False) Returns ------- bool r(selfs V/var/www/html/test/jupyter/venv/lib/python3.11/site-packages/plotly/graph_objs/_pie.pyr(zPie.automarginEsL!!c||d<dS)Nr(r?rAvals rBr(zPie.automarginS \rCc|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)zPie.customdataWL!!rCc||d<dS)Nr)r?rEs rBr)zPie.customdatahrGrCc|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 rBr5zPie.customdatasrclsO$$rCc||d<dS)Nr5r?rEs rBr5zPie.customdatasrc{ #_rCc|dS)aC Specifies the direction at which succeeding sectors follow one another. The 'direction' property is an enumeration that may be specified as: - One of the following enumeration values: ['clockwise', 'counterclockwise'] Returns ------- Any r#r?r@s rBr#z Pie.directionsK  rCc||d<dS)Nr#r?rEs rBr#z Pie.direction[rCc|dS)z Sets the label step. See `label0` for more info. The 'dlabel' property is a number and may be specified as: - An int or float Returns ------- int|float rr?r@s rBrz Pie.dlabelH~rCc||d<dS)Nrr?rEs rBrz Pie.dlabelXrCc|dS)aQ The 'domain' property is an instance of Domain that may be specified as: - An instance of :class:`plotly.graph_objs.pie.Domain` - A dict of string/value properties that will be passed to the Domain constructor Returns ------- plotly.graph_objs.pie.Domain rr?r@s rBrz Pie.domainH~rCc||d<dS)Nrr?rEs rBrz Pie.domainrTrCc|dS)a Sets the fraction of the radius to cut out of the pie. Use this to make a donut chart. The 'hole' property is a number and may be specified as: - An int or float in the interval [0, 1] Returns ------- int|float r r?r@s rBr zPie.holeF|rCc||d<dS)Nr r?rEs rBr zPie.holeV rCc|dS)aq 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 ['label', 'text', 'value', 'percent', 'name'] joined with '+' characters (e.g. 'label+text') 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$z Pie.hoverinfo$K  rCc||d<dS)Nr$r?rEs rBr$z Pie.hoverinforPrCc|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 rBr1zPie.hoverinfosrcN##rCc||d<dS)Nr1r?rEs rBr1zPie.hoverinfosrc"^rCc|dS)ae The 'hoverlabel' property is an instance of Hoverlabel that may be specified as: - An instance of :class:`plotly.graph_objs.pie.Hoverlabel` - A dict of string/value properties that will be passed to the Hoverlabel constructor Returns ------- plotly.graph_objs.pie.Hoverlabel r*r?r@s rBr*zPie.hoverlabelL!!rCc||d<dS)Nr*r?rEs rBr*zPie.hoverlabelrGrCc|dS)a 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. 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, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Finally, the template string has access to variables `label`, `color`, `value`, `percent` and `text`. 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 rBr6zPie.hovertemplate sLO$$rCc||d<dS)Nr6r?rEs rBr6zPie.hovertemplate1rMrCc|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;zPie.hovertemplatesrc5&''rCc||d<dS)Nr;r?rEs rBr;zPie.hovertemplatesrcD#&    rCc|dS)aG Sets hover text elements associated with each sector. If a single string, the same string appears for all data points. If an array of string, the items are mapped in order of this trace's sectors. 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%z Pie.hovertextHr]rCc||d<dS)Nr%r?rEs rBr%z Pie.hovertext\rPrCc|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 rBr2zPie.hovertextsrc`r`rCc||d<dS)Nr2r?rEs rBr2zPie.hovertextsrcorbrCc|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 rr?r@s rBrzPie.idssE{rCc||d<dS)Nrr?rEs rBrzPie.idsU rCc|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 rBrz Pie.idssrcrRrCc||d<dS)Nrr?rEs rBrz Pie.idssrcrTrCc|dS)a Sets the font used for `textinfo` lying inside the sector. The 'insidetextfont' property is an instance of Insidetextfont that may be specified as: - An instance of :class:`plotly.graph_objs.pie.Insidetextfont` - A dict of string/value properties that will be passed to the Insidetextfont constructor Returns ------- plotly.graph_objs.pie.Insidetextfont r7r?r@s rBr7zPie.insidetextfonts$%%rCc||d<dS)Nr7r?rEs rBr7zPie.insidetextfonts!$ rCc|dS)a Controls the orientation of the text inside chart sectors. When set to "auto", text may be oriented in any direction in order to be as big as possible in the middle of a sector. The "horizontal" option orients text to be parallel with the bottom of the chart, and may make text smaller in order to achieve that goal. The "radial" option orients text along the radius of the sector. The "tangential" option orients text perpendicular to the radius of the sector. The 'insidetextorientation' property is an enumeration that may be specified as: - One of the following enumeration values: ['horizontal', 'radial', 'tangential', 'auto'] Returns ------- Any r=r?r@s rBr=zPie.insidetextorientations(+,,rCc||d<dS)Nr=r?rEs rBr=zPie.insidetextorientations(+ $%%%rCc|dS)a9 Alternate to `labels`. Builds a numeric set of labels. Use with `dlabel` where `label0` is the starting label and `dlabel` the step. The 'label0' property is a number and may be specified as: - An int or float Returns ------- int|float rr?r@s rBrz Pie.label0sH~rCc||d<dS)Nrr?rEs rBrz Pie.label0rTrCc|dS)a Sets the sector labels. If `labels` entries are duplicated, we sum associated `values` or simply count occurrences if `values` is not provided. For other array attributes (including color) we use the first non-empty entry among all occurrences of the label. The 'labels' property is an array that may be specified as a tuple, list, numpy array, or pandas Series Returns ------- numpy.ndarray rr?r@s rBrz Pie.labelss H~rCc||d<dS)Nrr?rEs rBrz Pie.labelsrTrCc|dS)z Sets the source reference on Chart Studio Cloud for `labels`. The 'labelssrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str r&r?r@s rBr&z Pie.labelssrcK  rCc||d<dS)Nr&r?rEs rBr&z Pie.labelssrcrPrCc|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 rBrz Pie.legends"H~rCc||d<dS)Nrr?rEs rBrz Pie.legendrTrCc|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/zPie.legendgroupsM""rCc||d<dS)Nr/r?rEs rBr/zPie.legendgroup,!]rCc|dS)a The 'legendgrouptitle' property is an instance of Legendgrouptitle that may be specified as: - An instance of :class:`plotly.graph_objs.pie.Legendgrouptitle` - A dict of string/value properties that will be passed to the Legendgrouptitle constructor Returns ------- plotly.graph_objs.pie.Legendgrouptitle r<r?r@s rBr<zPie.legendgrouptitle0rirCc||d<dS)Nr<r?rEs rBr<zPie.legendgrouptitle?rkrCc|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+zPie.legendrankCs&L!!rCc||d<dS)Nr+r?rEs rBr+zPie.legendrankXrGrCc|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 rBr0zPie.legendwidth\sM""rCc||d<dS)Nr0r?rEs rBr0zPie.legendwidthkrrCc|dS)aQ The 'marker' property is an instance of Marker that may be specified as: - An instance of :class:`plotly.graph_objs.pie.Marker` - A dict of string/value properties that will be passed to the Marker constructor Returns ------- plotly.graph_objs.pie.Marker rr?r@s rBrz Pie.markerorVrCc||d<dS)Nrr?rEs rBrz Pie.marker~rTrCc|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 r?r@s rBr zPie.metas(F|rCc||d<dS)Nr r?rEs rBr zPie.metar[rCc|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 rBrz Pie.metasrcIrCc||d<dS)Nrr?rEs rBrz Pie.metasrcYrCc|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 r r?r@s rBr zPie.namesF|rCc||d<dS)Nr r?rEs rBr zPie.namer[rCc|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 rBrz Pie.opacityrrCc||d<dS)Nrr?rEs rBrz Pie.opacityrrCc|dS)a Sets the font used for `textinfo` lying outside the sector. The 'outsidetextfont' property is an instance of Outsidetextfont that may be specified as: - An instance of :class:`plotly.graph_objs.pie.Outsidetextfont` - A dict of string/value properties that will be passed to the Outsidetextfont constructor Returns ------- plotly.graph_objs.pie.Outsidetextfont r8r?r@s rBr8zPie.outsidetextfonts%&&rCc||d<dS)Nr8r?rEs rBr8zPie.outsidetextfont"% rCc|dS)a Sets the fraction of larger radius to pull the sectors out from the center. This can be a constant to pull all slices apart from each other equally or an array to highlight one or more slices. The 'pull' property is a number and may be specified as: - An int or float in the interval [0, 1] - A tuple, list, or one-dimensional numpy array of the above Returns ------- int|float|numpy.ndarray r r?r@s rBr zPie.pull F|rCc||d<dS)Nr r?rEs rBr zPie.pullr[rCc|dS)z Sets the source reference on Chart Studio Cloud for `pull`. The 'pullsrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str rr?r@s rBrz Pie.pullsrcrrCc||d<dS)Nrr?rEs rBrz Pie.pullsrc rrCc|dS)a Instead of the first slice starting at 12 o'clock, rotate to some other angle. The 'rotation' property is a angle (in degrees) that may be specified as a number between -180 and 180. Numeric values outside this range are converted to the equivalent value (e.g. 270 is converted to -90). Returns ------- int|float r r?r@s rBr z Pie.rotationJrCc||d<dS)Nr r?rEs rBr z Pie.rotation"ZrCc|dS)a If there are multiple pie charts that should be sized according to their totals, link them by providing a non-empty group id here shared by every trace in the same group. The 'scalegroup' 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,zPie.scalegroup&rIrCc||d<dS)Nr,r?rEs rBr,zPie.scalegroup7rGrCc|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-zPie.showlegend;rdrCc||d<dS)Nr-r?rEs rBr-zPie.showlegendJrGrCc|dS)z Determines whether or not the sectors are reordered from largest to smallest. The 'sort' property must be specified as a bool (either True, or False) Returns ------- bool rr?r@s rBrzPie.sortNrYrCc||d<dS)Nrr?rEs rBrzPie.sort]r[rCc|dS)aQ The 'stream' property is an instance of Stream that may be specified as: - An instance of :class:`plotly.graph_objs.pie.Stream` - A dict of string/value properties that will be passed to the Stream constructor Returns ------- plotly.graph_objs.pie.Stream rr?r@s rBrz Pie.streamarVrCc||d<dS)Nrr?rEs rBrz Pie.streamprTrCc|dS)a Sets text elements associated with each sector. If trace `textinfo` contains a "text" flag, these elements will be seen on the chart. 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 an array that may be specified as a tuple, list, numpy array, or pandas Series Returns ------- numpy.ndarray rr?r@s rBrzPie.texttrrCc||d<dS)Nrr?rEs rBrzPie.textr[rCc|dS)a Sets the font used for `textinfo`. The 'textfont' property is an instance of Textfont that may be specified as: - An instance of :class:`plotly.graph_objs.pie.Textfont` - A dict of string/value properties that will be passed to the Textfont constructor Returns ------- plotly.graph_objs.pie.Textfont r!r?r@s rBr!z Pie.textfontrrCc||d<dS)Nr!r?rEs rBr!z Pie.textfontrrCc|dS)a Determines which trace information appear on the graph. The 'textinfo' property is a flaglist and may be specified as a string containing: - Any combination of ['label', 'text', 'value', 'percent'] joined with '+' characters (e.g. 'label+text') OR exactly one of ['none'] (e.g. 'none') Returns ------- Any r"r?r@s rBr"z Pie.textinforrCc||d<dS)Nr"r?rEs rBr"z Pie.textinforrCc|dS)ay Specifies the location of the `textinfo`. The 'textposition' property is an enumeration that may be specified as: - One of the following enumeration values: ['inside', 'outside', 'auto', 'none'] - A tuple, list, or one-dimensional numpy array of the above Returns ------- Any|numpy.ndarray r3r?r@s rBr3zPie.textpositionsN##rCc||d<dS)Nr3r?rEs rBr3zPie.textpositionrbrCc|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 r9r?r@s rBr9zPie.textpositionsrc%&&rCc||d<dS)Nr9r?rEs rBr9zPie.textpositionsrcrrCc|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 rr?r@s rBrz Pie.textsrcrrCc||d<dS)Nrr?rEs rBrz Pie.textsrcrrCc|dS)a Template string used for rendering the information text that appear 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. Every attributes that can be specified per- point (the ones that are `arrayOk: true`) are available. Finally, the template string has access to variables `label`, `color`, `value`, `percent` 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 rBr4zPie.texttemplates6N##rCc||d<dS)Nr4r?rEs rBr4zPie.texttemplate rbrCc|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 r:r?r@s rBr:zPie.texttemplatesrcrrCc||d<dS)Nr:r?rEs rBr:zPie.texttemplatesrcrrCc|dS)aL The 'title' property is an instance of Title that may be specified as: - An instance of :class:`plotly.graph_objs.pie.Title` - A dict of string/value properties that will be passed to the Title constructor Returns ------- plotly.graph_objs.pie.Title rr?r@s rBrz Pie.title!sG}rCc||d<dS)Nrr?rEs rBrz Pie.title0sW rCc|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 zPie.uid4rqrCc||d<dS)Nr r?rEs rBr zPie.uidDrsrCc|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.zPie.uirevisionHs2L!!rCc||d<dS)Nr.r?rEs rBr.zPie.uirevisioncrGrCc|dS)a Sets the values of the sectors. If omitted, we count occurrences of each label. The 'values' property is an array that may be specified as a tuple, list, numpy array, or pandas Series Returns ------- numpy.ndarray rr?r@s rBrz Pie.valuesgrVrCc||d<dS)Nrr?rEs rBrz Pie.valuesvrTrCc|dS)z Sets the source reference on Chart Studio Cloud for `values`. The 'valuessrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str r'r?r@s rBr'z Pie.valuessrczrrCc||d<dS)Nr'r?rEs rBr'z Pie.valuessrcrPrCc|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 rr?r@s rBrz Pie.visiblesIrCc||d<dS)Nrr?rEs rBrz Pie.visiblerrCc|jdS)Nr)_propsr@s rBrzPie.types{6""rCcdS)Na32 automargin Determines whether outside text labels can push the margins. 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`. direction Specifies the direction at which succeeding sectors follow one another. dlabel Sets the label step. See `label0` for more info. domain :class:`plotly.graph_objects.pie.Domain` instance or dict with compatible properties hole Sets the fraction of the radius to cut out of the pie. Use this to make a donut chart. 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.pie.Hoverlabel` instance or dict with compatible properties 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. 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, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Finally, the template string has access to variables `label`, `color`, `value`, `percent` and `text`. Anything contained in tag `` is displayed in the secondary box, for example "{fullData.name}". To hide the secondary box completely, use an empty tag ``. hovertemplatesrc Sets the source reference on Chart Studio Cloud for `hovertemplate`. hovertext Sets hover text elements associated with each sector. If a single string, the same string appears for all data points. If an array of string, the items are mapped in order of this trace's sectors. 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`. insidetextfont Sets the font used for `textinfo` lying inside the sector. insidetextorientation Controls the orientation of the text inside chart sectors. When set to "auto", text may be oriented in any direction in order to be as big as possible in the middle of a sector. The "horizontal" option orients text to be parallel with the bottom of the chart, and may make text smaller in order to achieve that goal. The "radial" option orients text along the radius of the sector. The "tangential" option orients text perpendicular to the radius of the sector. label0 Alternate to `labels`. Builds a numeric set of labels. Use with `dlabel` where `label0` is the starting label and `dlabel` the step. labels Sets the sector labels. If `labels` entries are duplicated, we sum associated `values` or simply count occurrences if `values` is not provided. For other array attributes (including color) we use the first non-empty entry among all occurrences of the label. labelssrc Sets the source reference on Chart Studio Cloud for `labels`. 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.pie.Legendgrouptitle` 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.pie.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. outsidetextfont Sets the font used for `textinfo` lying outside the sector. pull Sets the fraction of larger radius to pull the sectors out from the center. This can be a constant to pull all slices apart from each other equally or an array to highlight one or more slices. pullsrc Sets the source reference on Chart Studio Cloud for `pull`. rotation Instead of the first slice starting at 12 o'clock, rotate to some other angle. scalegroup If there are multiple pie charts that should be sized according to their totals, link them by providing a non-empty group id here shared by every trace in the same group. showlegend Determines whether or not an item corresponding to this trace is shown in the legend. sort Determines whether or not the sectors are reordered from largest to smallest. stream :class:`plotly.graph_objects.pie.Stream` instance or dict with compatible properties text Sets text elements associated with each sector. If trace `textinfo` contains a "text" flag, these elements will be seen on the chart. If trace `hoverinfo` contains a "text" flag and "hovertext" is not set, these elements will be seen in the hover labels. textfont Sets the font used for `textinfo`. textinfo Determines which trace information appear on the graph. textposition Specifies the location of the `textinfo`. 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 appear 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. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Finally, the template string has access to variables `label`, `color`, `value`, `percent` and `text`. texttemplatesrc Sets the source reference on Chart Studio Cloud for `texttemplate`. title :class:`plotly.graph_objects.pie.Title` instance or dict with compatible properties 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. values Sets the values of the sectors. If omitted, we count occurrences of each label. valuessrc Sets the source reference on Chart Studio Cloud for `values`. 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_descriptionszPie._prop_descriptionssG G rCNc7 tdd|7vr|7d|_dS|i}nct||jr|}n9t|t rtj|}ntd|7 dd|_ |7 dd|_ | d ||| d ||| d ||| d ||| d ||| d||| d||| d|| | d|| | d|| | d|| | d|| | d||| d||| d||| d||| d||| d||| d||| d||| d||| d||| d||| d ||| d!||| d"||| d#||| d$||| d%||| d&||| d'|| | d(||!| d)||"| d*||#| d+||$| d,||%| d-||&| d.||'| d/||(| d0||)| d1||*| d2||+| d3||,| d4||-| d5||.| d6||/| d7||0| d8||1| d9||2| d:||3| d;||4| d<||5| d=||6d|jd><| d>d|jd?it |fi|7d|_ dS)@a3 Construct a new Pie object A data visualized by the sectors of the pie is set in `values`. The sector labels are set in `labels`. The sector colors are set in `marker.colors` Parameters ---------- arg dict of properties compatible with this constructor or an instance of :class:`plotly.graph_objs.Pie` automargin Determines whether outside text labels can push the margins. 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`. direction Specifies the direction at which succeeding sectors follow one another. dlabel Sets the label step. See `label0` for more info. domain :class:`plotly.graph_objects.pie.Domain` instance or dict with compatible properties hole Sets the fraction of the radius to cut out of the pie. Use this to make a donut chart. 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.pie.Hoverlabel` instance or dict with compatible properties 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. 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, every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Finally, the template string has access to variables `label`, `color`, `value`, `percent` and `text`. Anything contained in tag `` is displayed in the secondary box, for example "{fullData.name}". To hide the secondary box completely, use an empty tag ``. hovertemplatesrc Sets the source reference on Chart Studio Cloud for `hovertemplate`. hovertext Sets hover text elements associated with each sector. If a single string, the same string appears for all data points. If an array of string, the items are mapped in order of this trace's sectors. 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`. insidetextfont Sets the font used for `textinfo` lying inside the sector. insidetextorientation Controls the orientation of the text inside chart sectors. When set to "auto", text may be oriented in any direction in order to be as big as possible in the middle of a sector. The "horizontal" option orients text to be parallel with the bottom of the chart, and may make text smaller in order to achieve that goal. The "radial" option orients text along the radius of the sector. The "tangential" option orients text perpendicular to the radius of the sector. label0 Alternate to `labels`. Builds a numeric set of labels. Use with `dlabel` where `label0` is the starting label and `dlabel` the step. labels Sets the sector labels. If `labels` entries are duplicated, we sum associated `values` or simply count occurrences if `values` is not provided. For other array attributes (including color) we use the first non-empty entry among all occurrences of the label. labelssrc Sets the source reference on Chart Studio Cloud for `labels`. 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.pie.Legendgrouptitle` 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.pie.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. outsidetextfont Sets the font used for `textinfo` lying outside the sector. pull Sets the fraction of larger radius to pull the sectors out from the center. This can be a constant to pull all slices apart from each other equally or an array to highlight one or more slices. pullsrc Sets the source reference on Chart Studio Cloud for `pull`. rotation Instead of the first slice starting at 12 o'clock, rotate to some other angle. scalegroup If there are multiple pie charts that should be sized according to their totals, link them by providing a non-empty group id here shared by every trace in the same group. showlegend Determines whether or not an item corresponding to this trace is shown in the legend. sort Determines whether or not the sectors are reordered from largest to smallest. stream :class:`plotly.graph_objects.pie.Stream` instance or dict with compatible properties text Sets text elements associated with each sector. If trace `textinfo` contains a "text" flag, these elements will be seen on the chart. If trace `hoverinfo` contains a "text" flag and "hovertext" is not set, these elements will be seen in the hover labels. textfont Sets the font used for `textinfo`. textinfo Determines which trace information appear on the graph. textposition Specifies the location of the `textinfo`. 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 appear 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. Every attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Finally, the template string has access to variables `label`, `color`, `value`, `percent` and `text`. texttemplatesrc Sets the source reference on Chart Studio Cloud for `texttemplate`. title :class:`plotly.graph_objects.pie.Title` instance or dict with compatible properties 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. values Sets the values of the sectors. If omitted, we count occurrences of each label. valuessrc Sets the source reference on Chart Studio Cloud for `values`. 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 ------- Pie r_parentNz{The first argument to the plotly.graph_objs.Pie constructor must be a dict or an instance of :class:`plotly.graph_objs.Pie` skip_invalidF _validateTr(r)r5r#rrr r$r1r*r6r;r%r2rrr7r=rrr&rr/r<r+r0rr rr rr8r rr r,r-rrrr!r"r3r9rr4r:rr r.rr'rrr?)super__init__r isinstance __class__to_plotly_jsondict_copycopy ValueErrorpop _skip_invalidr _set_propertyr_process_kwargs)9rAargr(r)r5r#rrr r$r1r*r6r;r%r2rrr7r=rrr&rr/r<r+r0rr rr rr8r rr r,r-rrrr!r"r3r9rr4r:rr r.rr'rkwargsrs9 rBrz Pie.__init__s+b    !),DL F ;CC T^ , , $$&&CC T " " *S//CC1 $ZZ>>K66 <j999 <j999 ?C??? ;Y777 8S&111 8S&111 63--- ;Y777 >3 === <j999 ?C??? -s4DEEE ;Y777 >3 === 5#s+++ 8S&111 +S.AAA 2C9NOOO 8S&111 8S&111 ;Y777 8S&111 =#{;;; -s4DEEE <j999 =#{;;; 8S&111 63--- 9c7333 63--- 9c7333 ,c?CCC 63--- 9c7333 :sH555 <j999 <j999 63--- 8S&111 63--- :sH555 :sH555 >3 === ,c?CCC 9c7333 >3 === ,c?CCC 7C/// 5#s+++ <j999 8S&111 ;Y777 9c7333# F 33tC22622333"rC)6NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN)A__name__ __module__ __qualname___parent_path_str _path_str _valid_propspropertyr(setterr)r5r#rrr r$r1r*r6r;r%r2rrr7r=rrr&rr/r<r+r0rr rr rr8r rr r,r-rrrr!r"r3r9rr4r:rr r.rr'rrrr __classcell__)rs@rBrrs I777Lr " "X "!!!""X" !!! % %X %$$$ ! !X !     X  ]]  X  ]]  X  [[!!X!&    $ $X $### " "X "!!!%%%%X%%N$$$ ( (X ('''!!X!&    $ $X $###  X  ZZ  X  ]]&&X& %%%--X-*!,,"!,  X  ]]X" ]] ! !X !   X$ ]]##X# """ ( (X ('''""X"(!!! # #X #"""  X  ]]X* [[  X  ^^  X  [[  X  ^^''X' &&&X" [[  X  ^^  X __""X" !!! " "X "!!!  X  [[  X  ]]X" [[  X __  X __ $ $X $### ' 'X '&&&  X  ^^$$X$8### ' 'X '&&&  X  \\  X  ZZ""X"4!!!  X  ]] ! !X !   X  ^^##X#H H XH X   "      o`#`#`#`#`#`#`#`#`#`#rCr)plotly.basedatatypesr_BaseTraceTyperrrr?rCrBrsdA@@@@@H#H#H#H#H#.H#H#H#H#H#rC