B &[¨_W~ã@s(ddlmZddlZGdd„deƒZdS)é)Ú BaseTraceTypeNcs¬eZdZdZdZddddddd d d d d ddddddddddddhZedd„ƒZejdd„ƒZedd„ƒZ e jdd„ƒZ ed d!„ƒZ e jd"d!„ƒZ ed#d$„ƒZ e jd%d$„ƒZ ed&d'„ƒZ e jd(d'„ƒZ ed)d*„ƒZ e jd+d*„ƒZ ed,d-„ƒZejd.d-„ƒZed/d0„ƒZejd1d0„ƒZed2d3„ƒZejd4d3„ƒZed5d6„ƒZejd7d6„ƒZed8d9„ƒZejd:d9„ƒZed;d<„ƒZejd=d<„ƒZed>d?„ƒZejd@d?„ƒZedAdB„ƒZejdCdB„ƒZedDdE„ƒZejdFdE„ƒZedGdH„ƒZejdIdH„ƒZedJdK„ƒZejdLdK„ƒZedMdN„ƒZejdOdN„ƒZedPdQ„ƒZejdRdQ„ƒZedSdT„ƒZejdUdT„ƒZedVdW„ƒZejdXdW„ƒZedYdZ„ƒZejd[dZ„ƒZed\d]„ƒZed^d_„ƒZdc‡fdadb„ Z ‡Z!S)dÚAreaÚÚareaÚ customdataÚ customdatasrcÚ hoverinfoÚ hoverinfosrcÚ hoverlabelÚidsÚidssrcÚ legendgroupÚmarkerÚmetaÚmetasrcÚnameÚopacityÚrÚrsrcÚ showlegendÚstreamÚtÚtsrcÚtypeÚuidÚ uirevisionÚvisiblecCs|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©)Úselfrrú;/tmp/pip-install-l29rncou/plotly/plotly/graph_objs/_area.pyr'szArea.customdatacCs ||d<dS)Nrr)rÚvalrrrr8scCs|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 rr)rrrrr>s zArea.customdatasrccCs ||d<dS)Nrr)rr rrrrMscCs|dS)a` Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired. The 'hoverinfo' property is a flaglist and may be specified as a string containing: - Any combination of ['x', 'y', 'z', 'text', 'name'] joined with '+' characters (e.g. 'x+y') OR exactly one of ['all', 'none', 'skip'] (e.g. 'skip') - A list or array of the above Returns ------- Any|numpy.ndarray rr)rrrrrSszArea.hoverinfocCs ||d<dS)Nrr)rr rrrrgscCs|dS)zý Sets the source reference on Chart Studio Cloud for hoverinfo . The 'hoverinfosrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str r r)rrrrr ms zArea.hoverinfosrccCs ||d<dS)Nr r)rr rrrr |scCs|dS)a* The 'hoverlabel' property is an instance of Hoverlabel that may be specified as: - An instance of :class:`plotly.graph_objs.area.Hoverlabel` - A dict of string/value properties that will be passed to the Hoverlabel constructor Supported dict properties: align Sets the horizontal alignment of the text content within hover label box. Has an effect only if the hover label text spans more two or more lines alignsrc Sets the source reference on Chart Studio Cloud for align . bgcolor Sets the background color of the hover labels for this trace bgcolorsrc Sets the source reference on Chart Studio Cloud for bgcolor . bordercolor Sets the border color of the hover labels for this trace. bordercolorsrc Sets the source reference on Chart Studio Cloud for bordercolor . font Sets the font used in hover labels. namelength Sets the default length (in number of characters) of the trace name in the hover labels for all traces. -1 shows the whole name regardless of length. 0-3 shows the first 0-3 characters, and an integer >3 will show the whole name if it is less than that many characters, but if it is longer, will truncate to `namelength - 3` characters and add an ellipsis. namelengthsrc Sets the source reference on Chart Studio Cloud for namelength . Returns ------- plotly.graph_objs.area.Hoverlabel r r)rrrrr ‚s3zArea.hoverlabelcCs ||d<dS)Nr r)rr rrrr ·scCs|dS)aq 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)rrrrr ½szArea.idscCs ||d<dS)Nr r)rr rrrr ÍscCs|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 r r)rrrrr Ós z Area.idssrccCs ||d<dS)Nr r)rr rrrr áscCs|dS)ak Sets the legend group for this trace. Traces 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)rrrrr çszArea.legendgroupcCs ||d<dS)Nr r)rr rrrr øscCs|dS)a“ The 'marker' property is an instance of Marker that may be specified as: - An instance of :class:`plotly.graph_objs.area.Marker` - A dict of string/value properties that will be passed to the Marker constructor Supported dict properties: color Area traces are deprecated! Please switch to the "barpolar" trace type. Sets themarkercolor. It accepts either a specific color or an array of numbers that are mapped to the colorscale relative to the max and min values of the array or relative to `marker.cmin` and `marker.cmax` if set. colorsrc Sets the source reference on Chart Studio Cloud for color . opacity Area traces are deprecated! Please switch to the "barpolar" trace type. Sets the marker opacity. opacitysrc Sets the source reference on Chart Studio Cloud for opacity . size Area traces are deprecated! Please switch to the "barpolar" trace type. Sets the marker size (in px). sizesrc Sets the source reference on Chart Studio Cloud for size . symbol Area traces are deprecated! Please switch to the "barpolar" trace type. Sets the marker symbol type. Adding 100 is equivalent to appending "-open" to a symbol name. Adding 200 is equivalent to appending "-dot" to a symbol name. Adding 300 is equivalent to appending "-open-dot" or "dot-open" to a symbol name. symbolsrc Sets the source reference on Chart Studio Cloud for symbol . Returns ------- plotly.graph_objs.area.Marker rr)rrrrrþs4z Area.markercCs ||d<dS)Nrr)rr rrrr4scCs|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)rrrrr:sz Area.metacCs ||d<dS)Nrr)rr rrrrPscCs|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)rrrrrVs z Area.metasrccCs ||d<dS)Nrr)rr rrrrdscCs|dS)a& Sets the trace name. The trace name appear 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)rrrrrjsz Area.namecCs ||d<dS)Nrr)rr rrrrzscCs|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)rrrrr€s z Area.opacitycCs ||d<dS)Nrr)rr rrrrŽscCs|dS)aQ Area traces are deprecated! Please switch to the "barpolar" trace type. Sets the radial coordinates for legacy polar chart only. The 'r' property is an array that may be specified as a tuple, list, numpy array, or pandas Series Returns ------- numpy.ndarray rr)rrrrr”szArea.rcCs ||d<dS)Nrr)rr rrrr¤scCs|dS)zå Sets the source reference on Chart Studio Cloud for r . The 'rsrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str rr)rrrrrªs z Area.rsrccCs ||d<dS)Nrr)rr rrrr¸scCs|dS)a 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 rr)rrrrr¾s zArea.showlegendcCs ||d<dS)Nrr)rr rrrrÍscCs|dS)as The 'stream' property is an instance of Stream that may be specified as: - An instance of :class:`plotly.graph_objs.area.Stream` - A dict of string/value properties that will be passed to the Stream constructor Supported dict properties: maxpoints Sets the maximum number of points to keep on the plots from an incoming stream. If `maxpoints` is set to 50, only the newest 50 points will be displayed on the plot. token The stream id number links a data trace on a plot with a stream. See https://chart- studio.plotly.com/settings for more details. Returns ------- plotly.graph_objs.area.Stream rr)rrrrrÓsz Area.streamcCs ||d<dS)Nrr)rr rrrrîscCs|dS)aR Area traces are deprecated! Please switch to the "barpolar" trace type. Sets the angular coordinates for legacy polar chart only. The 't' property is an array that may be specified as a tuple, list, numpy array, or pandas Series Returns ------- numpy.ndarray rr)rrrrrôszArea.tcCs ||d<dS)Nrr)rr rrrrscCs|dS)zå Sets the source reference on Chart Studio Cloud for t . The 'tsrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str rr)rrrrr s z Area.tsrccCs ||d<dS)Nrr)rr rrrrscCs|dS)aL 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 rr)rrrrrszArea.uidcCs ||d<dS)Nrr)rr rrrr.scCs|dS)aR 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 rr)rrrrr4szArea.uirevisioncCs ||d<dS)Nrr)rr rrrrOscCs|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)rrrrrUsz Area.visiblecCs ||d<dS)Nrr)rr rrrrfscCs |jdS)Nr)Ú_props)rrrrrlsz Area.typecCsdS)Na— customdata Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, "scatter" traces also appends customdata items in the markers DOM elements customdatasrc Sets the source reference on Chart Studio Cloud for customdata . hoverinfo Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired. hoverinfosrc Sets the source reference on Chart Studio Cloud for hoverinfo . hoverlabel :class:`plotly.graph_objects.area.Hoverlabel` instance or dict with compatible properties ids Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type. idssrc Sets the source reference on Chart Studio Cloud for ids . legendgroup Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items. marker :class:`plotly.graph_objects.area.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 appear as the legend item and on hover. opacity Sets the opacity of the trace. r Area traces are deprecated! Please switch to the "barpolar" trace type. Sets the radial coordinates for legacy polar chart only. rsrc Sets the source reference on Chart Studio Cloud for r . showlegend Determines whether or not an item corresponding to this trace is shown in the legend. stream :class:`plotly.graph_objects.area.Stream` instance or dict with compatible properties t Area traces are deprecated! Please switch to the "barpolar" trace type. Sets the angular coordinates for legacy polar chart only. tsrc Sets the source reference on Chart Studio Cloud for t . uid Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions. uirevision Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves. visible Determines whether or not this trace is visible. If "legendonly", the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible). r)rrrrÚ_prop_descriptionsrshzArea._prop_descriptionsNc sÎtt|ƒ d¡d|kr&|d|_dS|dkr4i}n4t||jƒrJ| ¡}nt|tƒr`t  |¡}nt dƒ‚|  dd¡|_ |  dd¡|_ |  d d¡}|dk rœ|n|}|dk r°||d <|  d d¡}|dk rÈ|n|}|dk rÜ||d <|  d d¡}|dk rô|n|}|dk r ||d <|  d d¡}|dk r$|n|}|dk r:||d <|  d d¡}|dk rT|n|}|dk rj||d <|  dd¡}|dk r„|n|}|dk rš||d<|  dd¡}|dk r´|n|}|dk rÊ||d<|  dd¡}| dk rä| n|}|dk rú||d<|  dd¡}| dk r| n|}|dk r*||d<|  dd¡}| dk rD| n|}|dk rZ||d<|  dd¡}| dk rt| n|}|dk rŠ||d<|  dd¡}| dk r¤| n|}|dk rº||d<|  dd¡}|dk rÔ|n|}|dk rê||d<|  dd¡}|dk r|n|}|dk r||d<|  dd¡}|dk r4|n|}|dk rJ||d<|  dd¡}|dk rd|n|}|dk rz||d<|  dd¡}|dk r”|n|}|dk rª||d<|  dd¡}|dk rÄ|n|}|dk rÚ||d<|  dd¡}|dk rô|n|}|dk r ||d<|  dd¡}|dk r$|n|}|dk r:||d<|  dd¡}|dk rT|n|}|dk rj||d<|  dd¡}|dk r„|n|}|dk rš||d<d|jd<|  dd¡|jft|f|ŽŽd|_ dS) a£ Construct a new Area object Parameters ---------- arg dict of properties compatible with this constructor or an instance of :class:`plotly.graph_objs.Area` customdata Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, "scatter" traces also appends customdata items in the markers DOM elements customdatasrc Sets the source reference on Chart Studio Cloud for customdata . hoverinfo Determines which trace information appear on hover. If `none` or `skip` are set, no information is displayed upon hovering. But, if `none` is set, click and hover events are still fired. hoverinfosrc Sets the source reference on Chart Studio Cloud for hoverinfo . hoverlabel :class:`plotly.graph_objects.area.Hoverlabel` instance or dict with compatible properties ids Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type. idssrc Sets the source reference on Chart Studio Cloud for ids . legendgroup Sets the legend group for this trace. Traces part of the same legend group hide/show at the same time when toggling legend items. marker :class:`plotly.graph_objects.area.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 appear as the legend item and on hover. opacity Sets the opacity of the trace. r Area traces are deprecated! Please switch to the "barpolar" trace type. Sets the radial coordinates for legacy polar chart only. rsrc Sets the source reference on Chart Studio Cloud for r . showlegend Determines whether or not an item corresponding to this trace is shown in the legend. stream :class:`plotly.graph_objects.area.Stream` instance or dict with compatible properties t Area traces are deprecated! Please switch to the "barpolar" trace type. Sets the angular coordinates for legacy polar chart only. tsrc Sets the source reference on Chart Studio Cloud for t . uid Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions. uirevision Controls persistence of some user-driven changes to the trace: `constraintrange` in `parcoords` traces, as well as some `editable: true` modifications such as `name` and `colorbar.title`. Defaults to `layout.uirevision`. Note that other user-driven trace attribute changes are controlled by `layout` attributes: `trace.visible` is controlled by `layout.legend.uirevision`, `selectedpoints` is controlled by `layout.selectionrevision`, and `colorbar.(x|y)` (accessible with `config: {editable: true}`) is controlled by `layout.editrevision`. Trace changes are tracked by `uid`, which only falls back on trace index if no `uid` is provided. So if your app can add/remove traces before the end of the `data` array, such that the same trace has a different index, you can still preserve user-driven changes if you give each trace a `uid` that stays with it as it moves. visible Determines whether or not this trace is visible. If "legendonly", the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible). Returns ------- Area rÚ_parentNzThe first argument to the plotly.graph_objs.Area constructor must be a dict or an instance of :class:`plotly.graph_objs.Area`Z skip_invalidFÚ _validateTrrrr r r r r rrrrrrrrrrrrrrr)ÚsuperrÚ__init__r#Ú isinstanceÚ __class__Zto_plotly_jsonÚdictÚ_copyÚcopyÚ ValueErrorÚpopZ _skip_invalidr$r!Z_process_kwargs)rÚargrrrr r r r r rrrrrrrrrrrrrrÚkwargsZ_v)r(rrr&ÜsÖ                                                 z Area.__init__)NNNNNNNNNNNNNNNNNNNNNNN)"Ú__name__Ú __module__Ú __qualname__Z_parent_path_strZ _path_strZ _valid_propsÚpropertyrÚsetterrrr r r r r rrrrrrrrrrrrrrrr"r&Ú __classcell__rr)r(rrs¼     5    6               lr)Zplotly.basedatatypesrZ_BaseTraceTyper+r*rrrrrÚs