6Dhd.SSKJr SSKr"SS\5rg)) BaseTraceTypeNc ^\rSrSrSrSr1Skr\S5r\RS5r\S5r \ RS5r \S 5r \ RS 5r \S 5r \ RS 5r \S 5r \ RS5r \S5r\RS5r\S5r\RS5r\S5r\RS5r\S5r\RS5r\S5r\RS5r\S5r\RS5r\S5r\RS5r\S5r\RS5r\S5r\RS 5r\S!5r\RS"5r\S#5r\RS$5r\S%5r\RS&5r\S'5r\RS(5r\S)5r\RS*5r\S+5r\RS,5r\S-5r\RS.5r\S/5r\RS05r\S15r\RS25r\S35r \ RS45r \S55r!\!RS65r!\S75r"\"RS85r"\S95r#\#RS:5r#\S;5r$\$RS<5r$\S=5r%\%RS>5r%\S?5r&\&RS@5r&\SA5r'\'RSB5r'\SC5r(\(RSD5r(\SE5r)\)RSF5r)\SG5r*\*RSH5r*\SI5r+\+RSJ5r+\SK5r,\,RSL5r,\SM5r-\-RSN5r-\SO5r.\.RSP5r.\SQ5r/\/RSR5r/\SS5r0\0RST5r0\SU5r1\1RSV5r1\SW5r2\2RSX5r2\SY5r3\3RSZ5r3\S[5r4\4RS\5r4\S]5r5\5RS^5r5\S_5r6\6RS`5r6\Sa5r7\7RSb5r7\Sc5r8\8RSd5r8\Se5r9\9RSf5r9\Sg5r:\:RSh5r:\Si5r;\;RSj5r;\Sk5r<\\Sp5r?SsU4Sqjjr@SrrAU=rB$)tPiepie>6idsuidholemetanamepullsorttexttypetitledlabeldomainidssrclabel0labelslegendmarkerstreamvaluesmetasrcopacitypullsrctextsrcvisiblerotationtextfonttextinfo direction hoverinfo hovertext labelssrc valuessrc automargin customdata hoverlabel legendrank scalegroup showlegend uirevision legendgroup legendwidth hoverinfosrc hovertextsrc textposition texttemplate customdatasrc hovertemplateinsidetextfontoutsidetextfonttextpositionsrctexttemplatesrchovertemplatesrclegendgrouptitleinsidetextorientationc US$)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 H/var/www/html/env/lib/python3.13/site-packages/plotly/graph_objs/_pie.pyr)Pie.automarginEsL!!c XS'g)Nr)r@rBvals rCr)rDS  \rEc US$)aJ 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@rAs rCr*Pie.customdataWL!!rEc XS'g)Nr*r@rGs rCr*rKhrIrEc US$)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 r6r@rAs rCr6Pie.customdatasrclsO$$rEc XS'g)Nr6r@rGs rCr6rO{ #_rEc US$)z 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@rAs rCr$ Pie.directionsK  rEc XS'g)Nr$r@rGs rCr$rS [rEc US$)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@rAs rCr Pie.dlabelH~rEc XS'g)Nrr@rGs rCrrW XrEc US$)a  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@rAs rCr Pie.domainH~rEc XS'g)Nrr@rGs rCrr\rZrEc US$)z 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@rAs rCr Pie.holeF|rEc XS'g)Nr r@rGs rCr r` V rEc US$)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 ['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@rAs rCr% Pie.hoverinfo$K  rEc XS'g)Nr%r@rGs rCr%rerUrEc US$)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 r2r@rAs rCr2Pie.hoverinfosrcN##rEc XS'g)Nr2r@rGs rCr2ri "^rEc US$)a 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@rAs rCr+Pie.hoverlabelL!!rEc XS'g)Nr+r@rGs rCr+rnrIrEc US$)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 r7r@rAs rCr7Pie.hovertemplate sLO$$rEc XS'g)Nr7r@rGs rCr7rr1rQrEc US$)z 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@rAs rCr<Pie.hovertemplatesrc5&''rEc XS'g)Nr<r@rGs rCr<ruD #&  rEc US$)a 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@rAs rCr& Pie.hovertextHrfrEc XS'g)Nr&r@rGs rCr&rz\rUrEc US$)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 r3r@rAs rCr3Pie.hovertextsrc`rjrEc XS'g)Nr3r@rGs rCr3r}orlrEc US$)a% 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@rAs rCr Pie.idssE{rEc XS'g)Nr r@rGs rCr r U rEc US$)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@rAs rCr Pie.idssrcrXrEc XS'g)Nrr@rGs rCrrrZrEc US$)am 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 r8r@rAs rCr8Pie.insidetextfonts$%%rEc XS'g)Nr8r@rGs rCr8rs !$ rEc US$)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@rAs rCr>Pie.insidetextorientations(+,,rEc XS'g)Nr>r@rGs rCr>rs (+ $%rEc US$)z 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@rAs rCr Pie.label0sH~rEc XS'g)Nrr@rGs rCrrrZrEc US$)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@rAs rCr Pie.labelss H~rEc XS'g)Nrr@rGs rCrrrZrEc US$)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@rAs rCr' Pie.labelssrcK  rEc XS'g)Nr'r@rGs rCr'rrUrEc US$)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@rAs rCr Pie.legends"H~rEc XS'g)Nrr@rGs rCrrrZrEc US$)a" 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 r0r@rAs rCr0Pie.legendgroupsM""rEc XS'g)Nr0r@rGs rCr0r, !]rEc US$)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@rAs rCr=Pie.legendgrouptitle0rvrEc XS'g)Nr=r@rGs rCr=r?rxrEc US$)aZ 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@rAs rCr,Pie.legendrankCs&L!!rEc XS'g)Nr,r@rGs rCr,rXrIrEc US$)z 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 r1r@rAs rCr1Pie.legendwidth\sM""rEc XS'g)Nr1r@rGs rCr1rkrrEc US$)a  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@rAs rCr Pie.markeror]rEc XS'g)Nrr@rGs rCrr~rZrEc US$)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@rAs rCr Pie.metas(F|rEc XS'g)Nr r@rGs rCr rrcrEc US$)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@rAs rCr Pie.metasrcIrEc XS'g)Nrr@rGs rCrr YrEc US$)z 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@rAs rCr Pie.namesF|rEc XS'g)Nr r@rGs rCr rrcrEc US$)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@rAs rCr Pie.opacityrrEc XS'g)Nrr@rGs rCrrrrEc US$)as 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 r9r@rAs rCr9Pie.outsidetextfonts%&&rEc XS'g)Nr9r@rGs rCr9r "% rEc US$)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 rr@rAs rCrPie.pull F|rEc XS'g)Nrr@rGs rCrrrcrEc US$)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@rAs rCr Pie.pullsrcrrEc XS'g)Nrr@rGs rCrr rrEc US$)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@rAs rCr! Pie.rotationJrEc XS'g)Nr!r@rGs rCr!r" ZrEc US$)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@rAs rCr-Pie.scalegroup&rLrEc XS'g)Nr-r@rGs rCr-r7rIrEc US$)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@rAs rCr.Pie.showlegend;rorEc XS'g)Nr.r@rGs rCr.rJrIrEc US$)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@rAs rCrPie.sortNrarEc XS'g)Nrr@rGs rCrr]rcrEc US$)a  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@rAs rCr Pie.streamar]rEc XS'g)Nrr@rGs rCrrprZrEc US$)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@rAs rCrPie.texttrrEc XS'g)Nrr@rGs rCrrrcrEc US$)a7 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@rAs rCr" Pie.textfontrrEc XS'g)Nr"r@rGs rCr"rrrEc US$)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@rAs rCr# Pie.textinforrEc XS'g)Nr#r@rGs rCr#rrrEc US$)a1 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 r4r@rAs rCr4Pie.textpositionsN##rEc XS'g)Nr4r@rGs rCr4rrlrEc US$)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 r:r@rAs rCr:Pie.textpositionsrc%&&rEc XS'g)Nr:r@rGs rCr:rrrEc US$)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@rAs rCr Pie.textsrcrrEc XS'g)Nrr@rGs rCrrrrEc US$)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 r5r@rAs rCr5Pie.texttemplates6N##rEc XS'g)Nr5r@rGs rCr5r rlrEc US$)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@rAs rCr;Pie.texttemplatesrcrrEc XS'g)Nr;r@rGs rCr;rrrEc US$)a 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@rAs rCr Pie.title!sG}rEc XS'g)Nrr@rGs rCrr0s W rEc US$)a 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@rAs rCr Pie.uid4rrEc XS'g)Nr r@rGs rCr rDrrEc US$)a 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@rAs rCr/Pie.uirevisionHs2L!!rEc XS'g)Nr/r@rGs rCr/rcrIrEc US$)z 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@rAs rCr Pie.valuesgr]rEc XS'g)Nrr@rGs rCrrvrZrEc US$)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@rAs rCr( Pie.valuessrczrrEc XS'g)Nr(r@rGs rCr(rrUrEc US$)aS 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@rAs rCr Pie.visiblesIrEc XS'g)Nr r@rGs rCr rrrEc URS$)Nr)_propsrAs rCrPie.types{{6""rEcg)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@rAs rC_prop_descriptionsPie._prop_descriptionssG rEc7 >[T8U]S5 SU7;a U7SUlgUc0nOb[XR5(aUR 5nO7[U[ 5(a[R"U5nO [S5eU7RSS5Ul U7RSS5Ul URS X5 URS X5 URS X5 URS X5 URS X5 URSX5 URSX5 URSX5 URSX5 URSX5 URSX5 URSX5 URSX5 URSX5 URSUU5 URSUU5 URSUU5 URSUU5 URSUU5 URSUU5 URSUU5 URSUU5 URSUU5 URS UU5 URS!UU5 URS"UU5 URS#UU5 URS$UU5 URS%UU5 URS&UU5 URS'UU 5 URS(UU!5 URS)UU"5 URS*UU#5 URS+UU$5 URS,UU%5 URS-UU&5 URS.UU'5 URS/UU(5 URS0UU)5 URS1UU*5 URS2UU+5 URS3UU,5 URS4UU-5 URS5UU.5 URS6UU/5 URS7UU05 URS8UU15 URS9UU25 URS:UU35 URS;UU45 URS'URS>S5 UR"S?0[ U40U7D6D6 SUl g)@aI+ 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*r6r$rrr r%r2r+r7r<r&r3r rr8r>rrr'rr0r=r,r1rr rr rr9rrr!r-r.rrrr"r#r4r:rr5r;rr r/rr(r rr@)super__init__r isinstance __class__to_plotly_jsondict_copycopy ValueErrorpop _skip_invalidr _set_propertyr_process_kwargs)9rBargr)r*r6r$rrr r%r2r+r7r<r&r3r rr8r>rrr'rr0r=r,r1rr rr rr9rrr!r-r.rrrr"r#r4r:rr5r;rr r/rr(r kwargsr s9 rCr  Pie.__init__sb   !),DL  ;C ^^ , ,$$&C T " "**S/C1 $ZZ>K6 <9 <9 ?C? ;7 8S1 8S1 63- ;7 >3= <9 ?C? -sE ;7 >3= 5#s+ 8S&1 +S.A 2C9NO 8S&1 8S&1 ;Y7 8S&1 =#{; -s4DE <j9 =#{; 8S&1 63- 9c73 63- 9c73 ,c?C 63- 9c73 :sH5 <j9 <j9 63- 8S&1 63- :sH5 :sH5 >3 = ,c?C 9c73 >3 = ,c?C 7C/ 5#s+ <j9 8S&1 ;Y7 9c73# F  3tC2623"rE)rrr)6NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN)C__name__ __module__ __qualname____firstlineno___parent_path_str _path_str _valid_propspropertyr)setterr*r6r$rrr r%r2r+r7r<r&r3r rr8r>rrr'rr0r=r,r1rr rr rr9rrr!r-r.rrrr"r#r4r:rr5r;rr r/rr(r rrr __static_attributes__ __classcell__)r s@rCrrsE I7Lr " "!!"" !! % %$$ ! !     ]]   ]]   [[!!&   $ $## " "!!%%%%N$$ ( (''!!&   $ $##   ZZ   ]]&& %%--*!!,",   ]]" ]] ! !  $ ]]## "" ( (''""(!! # #""   ]]* [[   ^^   [[   ^^'' &&" [[   ^^  __"" !! " "!!   [[   ]]" [[  __  __ $ $## ' '&&   ^^$$8## ' '&&   \\   ZZ""4!!   ]] ! !    ^^##H H X   "      o`#`#rEr)plotly.basedatatypesr_BaseTraceTyperrrr@rErCr&sAH#.H#rE