6Dhx.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"\S85r#S;U4S9jjr$S:r%U=r&$)<Tabletable>idsuidmetanametypecellsdomainheaderidssrclegendstreammetasrcvisible hoverinfo customdata hoverlabel legendrank uirevision columnorder columnwidth legendwidth hoverinfosrc customdatasrccolumnordersrccolumnwidthsrclegendgrouptitlec US$)a The 'cells' property is an instance of Cells that may be specified as: - An instance of :class:`plotly.graph_objs.table.Cells` - A dict of string/value properties that will be passed to the Cells constructor Returns ------- plotly.graph_objs.table.Cells rselfs J/var/www/html/env/lib/python3.13/site-packages/plotly/graph_objs/_table.pyr Table.cells)sG}c XS'g)Nrr$r&vals r'rr(8s W r)c US$)a^ Specifies the rendered order of the data columns; for example, a value `2` at position `0` means that column index `0` in the data will be rendered as the third column, as columns have an index base of zero. The 'columnorder' property is an array that may be specified as a tuple, list, numpy array, or pandas Series Returns ------- numpy.ndarray rr$r%s r'rTable.columnorder<sM""r)c XS'g)Nrr$r+s r'rr.M !]r)c US$)z Sets the source reference on Chart Studio Cloud for `columnorder`. The 'columnordersrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str r r$r%s r'r Table.columnordersrcQ$%%r)c XS'g)Nr r$r+s r'r r2` !$ r)c US$)a: The width of columns expressed as a ratio. Columns fill the available width in proportion of their specified column widths. The 'columnwidth' property is a number and may be specified as: - An int or float - A tuple, list, or one-dimensional numpy array of the above Returns ------- int|float|numpy.ndarray rr$r%s r'rTable.columnwidthdsM""r)c XS'g)Nrr$r+s r'rr7tr0r)c US$)z Sets the source reference on Chart Studio Cloud for `columnwidth`. The 'columnwidthsrc' property must be specified as a string or as a plotly.grid_objs.Column object Returns ------- str r!r$r%s r'r!Table.columnwidthsrcxr3r)c XS'g)Nr!r$r+s r'r!r:r5r)c 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 rr$r%s r'rTable.customdatasL!!r)c XS'g)Nrr$r+s r'rr=  \r)c 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 rr$r%s r'rTable.customdatasrcsO$$r)c XS'g)Nrr$r+s r'rrAs #_r)c US$)a  The 'domain' property is an instance of Domain that may be specified as: - An instance of :class:`plotly.graph_objs.table.Domain` - A dict of string/value properties that will be passed to the Domain constructor Returns ------- plotly.graph_objs.table.Domain rr$r%s r'r Table.domainH~r)c XS'g)Nrr$r+s r'rrD Xr)c US$)a  The 'header' property is an instance of Header that may be specified as: - An instance of :class:`plotly.graph_objs.table.Header` - A dict of string/value properties that will be passed to the Header constructor Returns ------- plotly.graph_objs.table.Header rr$r%s r'r Table.headerrEr)c XS'g)Nrr$r+s r'rrIrGr)c 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 ['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$r%s r'rTable.hoverinfos$K  r)c XS'g)Nrr$r+s r'rrLs [r)c 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 rr$r%s r'rTable.hoverinfosrcsN##r)c XS'g)Nrr$r+s r'rrOs "^r)c US$)a! The 'hoverlabel' property is an instance of Hoverlabel that may be specified as: - An instance of :class:`plotly.graph_objs.table.Hoverlabel` - A dict of string/value properties that will be passed to the Hoverlabel constructor Returns ------- plotly.graph_objs.table.Hoverlabel rr$r%s r'rTable.hoverlabelsL!!r)c XS'g)Nrr$r+s r'rrRr?r)c 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$r%s r'r Table.idsE{r)c XS'g)Nr r$r+s r'r rU' U r)c 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$r%s r'r Table.idssrc+sH~r)c XS'g)Nrr$r+s r'rrZ9rGr)c 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$r%s r'r Table.legend=s"H~r)c XS'g)Nrr$r+s r'rr]PrGr)c US$)a? The 'legendgrouptitle' property is an instance of Legendgrouptitle that may be specified as: - An instance of :class:`plotly.graph_objs.table.Legendgrouptitle` - A dict of string/value properties that will be passed to the Legendgrouptitle constructor Returns ------- plotly.graph_objs.table.Legendgrouptitle r"r$r%s r'r"Table.legendgrouptitleTs&''r)c XS'g)Nr"r$r+s r'r"r`cs #&  r)c 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 rr$r%s r'rTable.legendrankgs&L!!r)c XS'g)Nrr$r+s r'rrc|r?r)c 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 rr$r%s r'rTable.legendwidthsM""r)c XS'g)Nrr$r+s r'rrfr0r)c 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$r%s r'r Table.metas(F|r)c XS'g)Nr r$r+s r'r ri V r)c 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$r%s r'r Table.metasrcsIr)c XS'g)Nrr$r+s r'rrm Yr)c 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$r%s r'r Table.namesF|r)c XS'g)Nr r$r+s r'r rqrkr)c US$)a  The 'stream' property is an instance of Stream that may be specified as: - An instance of :class:`plotly.graph_objs.table.Stream` - A dict of string/value properties that will be passed to the Stream constructor Returns ------- plotly.graph_objs.table.Stream rr$r%s r'r Table.streamrEr)c XS'g)Nrr$r+s r'rrtrGr)c 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$r%s r'r Table.uidrVr)c XS'g)Nr r$r+s r'r rwrXr)c 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 rr$r%s r'rTable.uirevisions2L!!r)c XS'g)Nrr$r+s r'rrzr?r)c 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 rr$r%s r'r Table.visiblesIr)c XS'g)Nrr$r+s r'rr}*ror)c URS$)Nr )_propsr%s r'r Table.type.s{{6""r)cg)NaN cells :class:`plotly.graph_objects.table.Cells` instance or dict with compatible properties columnorder Specifies the rendered order of the data columns; for example, a value `2` at position `0` means that column index `0` in the data will be rendered as the third column, as columns have an index base of zero. columnordersrc Sets the source reference on Chart Studio Cloud for `columnorder`. columnwidth The width of columns expressed as a ratio. Columns fill the available width in proportion of their specified column widths. columnwidthsrc Sets the source reference on Chart Studio Cloud for `columnwidth`. 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`. domain :class:`plotly.graph_objects.table.Domain` instance or dict with compatible properties header :class:`plotly.graph_objects.table.Header` instance or dict with compatible properties 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.table.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`. 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. legendgrouptitle :class:`plotly.graph_objects.table.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. 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. stream :class:`plotly.graph_objects.table.Stream` 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. 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 r'_prop_descriptionsTable._prop_descriptions2s{ r)c >[TU]S5 SU;a USUlgUc0nOb[XR5(aUR 5nO7[U[ 5(a[R"U5nO [S5eURSS5Ul URSS5Ul 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 SURS"'URS"S5 UR"S#0[ U40UD6D6 SUl g)$a7 Construct a new Table object Table view for detailed data viewing. The data are arranged in a grid of rows and columns. Most styling can be specified for columns, rows or individual cells. Table is using a column- major order, ie. the grid is represented as a vector of column vectors. Parameters ---------- arg dict of properties compatible with this constructor or an instance of :class:`plotly.graph_objs.Table` cells :class:`plotly.graph_objects.table.Cells` instance or dict with compatible properties columnorder Specifies the rendered order of the data columns; for example, a value `2` at position `0` means that column index `0` in the data will be rendered as the third column, as columns have an index base of zero. columnordersrc Sets the source reference on Chart Studio Cloud for `columnorder`. columnwidth The width of columns expressed as a ratio. Columns fill the available width in proportion of their specified column widths. columnwidthsrc Sets the source reference on Chart Studio Cloud for `columnwidth`. 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`. domain :class:`plotly.graph_objects.table.Domain` instance or dict with compatible properties header :class:`plotly.graph_objects.table.Header` instance or dict with compatible properties 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.table.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`. 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. legendgrouptitle :class:`plotly.graph_objects.table.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. 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. stream :class:`plotly.graph_objects.table.Stream` 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. 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 ------- Table r_parentNzThe first argument to the plotly.graph_objs.Table constructor must be a dict or an instance of :class:`plotly.graph_objs.Table` skip_invalidF _validateTrrr rr!rrrrrrrr rrr"rrr rr rr rrr r$)super__init__r isinstance __class__to_plotly_jsondict_copycopy ValueErrorpop _skip_invalidr _set_propertyr_process_kwargs)r&argrrr rr!rrrrrrrr rrr"rrr rr rr rrkwargsrs r'rTable.__init__sV !  !),DL  ;C ^^ , ,$$&C T " "**S/C3 $ZZ>K6 7C/ =#; +SA =#; +SA <9 ?C? 8S1 8S1 ;7 >3= <9 5#+ 8S1 8S&1 -s4DE <j9 =#{; 63- 9c73 63- 8S&1 5#s+ <j9 9c73% F  3tC2623"r))rrr)NNNNNNNNNNNNNNNNNNNNNNNNNN)'__name__ __module__ __qualname____firstlineno___parent_path_str _path_str _valid_propspropertyrsetterrr rr!rrrrrrrr rrr"rrr rr rr rrr rr__static_attributes__ __classcell__)rs@r'rrsIL:   \\## "" & &%% # #"" & &%%"" !! % %$$   ]]   ]]!!&   $ $## " "!!   ZZ   ]]$ ]] ( (''""(!! # #""* [[   ^^   [[   ]]   ZZ""4!!  ^^##| | @     7^#^#r)r)plotly.basedatatypesr_BaseTraceTyperrrr$r)r'rsAG#NG#r)