*L i.ddlmZddlZGddeZy)) BaseTraceTypeNceZdZdZdZhdZedZejdZedZ 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"ed9Z# d;fd: Z$xZ%S)<Sankeysankey>idsuidlinkmetanamenodetypedomainidssrclegendstreammetasrcvisibletextfont hoverinfo customdata hoverlabel legendrank uirevision arrangement legendwidth orientation valueformat valuesuffix customdatasrcselectedpointslegendgrouptitlec |dS)a If value is `snap` (the default), the node arrangement is assisted by automatic snapping of elements to preserve space between nodes specified via `nodepad`. If value is `perpendicular`, the nodes can only move along a line perpendicular to the flow. If value is `freeform`, the nodes can freely move on the plane. If value is `fixed`, the nodes are stationary. The 'arrangement' property is an enumeration that may be specified as: - One of the following enumeration values: ['snap', 'perpendicular', 'freeform', 'fixed'] Returns ------- Any rselfs _/mnt/ssd/data/python-lab/Trading/venv/lib/python3.12/site-packages/plotly/graph_objs/_sankey.pyrzSankey.arrangement)s&M""c||d<y)Nrr$r&vals r'rzSankey.arrangement> !]r(c |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 rr$r%s r'rzSankey.customdataBsL!!r(c||d<y)Nrr$r*s r'rzSankey.customdataS  \r(c |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 r r$r%s r'r zSankey.customdatasrcWsO$$r(c||d<y)Nr r$r*s r'r zSankey.customdatasrcfs #_r(c |dS)aW The 'domain' property is an instance of Domain that may be specified as: - An instance of :class:`plotly.graph_objs.sankey.Domain` - A dict of string/value properties that will be passed to the Domain constructor Returns ------- plotly.graph_objs.sankey.Domain rr$r%s r'rz Sankey.domainjH~r(c||d<y)Nrr$r*s r'rz Sankey.domainy Xr(c |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. Note that this attribute is superseded by `node.hoverinfo` and `node.hoverinfo` for nodes and links respectively. The 'hoverinfo' property is a flaglist and may be specified as a string containing: - Any combination of [] joined with '+' characters (e.g. '') OR exactly one of ['all', 'none', 'skip'] (e.g. 'skip') Returns ------- Any rr$r%s r'rzSankey.hoverinfo}s&K  r(c||d<y)Nrr$r*s r'rzSankey.hoverinfos [r(c |dS)ak The 'hoverlabel' property is an instance of Hoverlabel that may be specified as: - An instance of :class:`plotly.graph_objs.sankey.Hoverlabel` - A dict of string/value properties that will be passed to the Hoverlabel constructor Returns ------- plotly.graph_objs.sankey.Hoverlabel rr$r%s r'rzSankey.hoverlabelsL!!r(c||d<y)Nrr$r*s r'rzSankey.hoverlabelr/r(c |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 r'rz Sankey.idsE{r(c||d<y)Nrr$r*s r'rz Sankey.ids U r(c |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 r'rz Sankey.idssrcsH~r(c||d<y)Nrr$r*s r'rz Sankey.idssrcr5r(c |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 r'rz Sankey.legends"H~r(c||d<y)Nrr$r*s r'rz Sankey.legendr5r(c |dS)a The 'legendgrouptitle' property is an instance of Legendgrouptitle that may be specified as: - An instance of :class:`plotly.graph_objs.sankey.Legendgrouptitle` - A dict of string/value properties that will be passed to the Legendgrouptitle constructor Returns ------- plotly.graph_objs.sankey.Legendgrouptitle r"r$r%s r'r"zSankey.legendgrouptitles&''r(c||d<y)Nr"r$r*s r'r"zSankey.legendgrouptitles #&  r(c |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 rr$r%s r'rzSankey.legendranks&L!!r(c||d<y)Nrr$r*s r'rzSankey.legendrankr/r(c |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 rr$r%s r'rzSankey.legendwidthM""r(c||d<y)Nrr$r*s r'rzSankey.legendwidth!r,r(c |dS)at The links of the Sankey plot. The 'link' property is an instance of Link that may be specified as: - An instance of :class:`plotly.graph_objs.sankey.Link` - A dict of string/value properties that will be passed to the Link constructor Returns ------- plotly.graph_objs.sankey.Link r r$r%s r'r z Sankey.link%F|r(c||d<y)Nr r$r*s r'r z Sankey.link6 V r(c |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 r'r z Sankey.meta:s(F|r(c||d<y)Nr r$r*s r'r z Sankey.metaPrLr(c |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 r'rzSankey.metasrcTsIr(c||d<y)Nrr$r*s r'rzSankey.metasrcb Yr(c |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 r'r z Sankey.namefsF|r(c||d<y)Nr r$r*s r'r z Sankey.namevrLr(c |dS)at The nodes of the Sankey plot. The 'node' property is an instance of Node that may be specified as: - An instance of :class:`plotly.graph_objs.sankey.Node` - A dict of string/value properties that will be passed to the Node constructor Returns ------- plotly.graph_objs.sankey.Node r r$r%s r'r z Sankey.nodezrJr(c||d<y)Nr r$r*s r'r z Sankey.noderLr(c |dS)a  Sets the orientation of the Sankey diagram. The 'orientation' property is an enumeration that may be specified as: - One of the following enumeration values: ['v', 'h'] Returns ------- Any rr$r%s r'rzSankey.orientationrGr(c||d<y)Nrr$r*s r'rzSankey.orientationr,r(c |dS)a Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect. The 'selectedpoints' property accepts values of any type Returns ------- Any r!r$r%s r'r!zSankey.selectedpointss $%%r(c||d<y)Nr!r$r*s r'r!zSankey.selectedpointss !$ r(c |dS)aW The 'stream' property is an instance of Stream that may be specified as: - An instance of :class:`plotly.graph_objs.sankey.Stream` - A dict of string/value properties that will be passed to the Stream constructor Returns ------- plotly.graph_objs.sankey.Stream rr$r%s r'rz Sankey.streamr3r(c||d<y)Nrr$r*s r'rz Sankey.streamr5r(c |dS)a Sets the font for node labels The 'textfont' property is an instance of Textfont that may be specified as: - An instance of :class:`plotly.graph_objs.sankey.Textfont` - A dict of string/value properties that will be passed to the Textfont constructor Returns ------- plotly.graph_objs.sankey.Textfont rr$r%s r'rzSankey.textfontsJr(c||d<y)Nrr$r*s r'rzSankey.textfonts Zr(c |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 r'r z Sankey.uidr;r(c||d<y)Nr r$r*s r'r z Sankey.uidr=r(c |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 rr$r%s r'rzSankey.uirevisions2L!!r(c||d<y)Nrr$r*s r'rzSankey.uirevisionr/r(c |dS)a Sets the value formatting rule using d3 formatting mini- languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. The 'valueformat' property is a string and must be specified as: - A string - A number that will be converted to a string Returns ------- str rr$r%s r'rzSankey.valueformats M""r(c||d<y)Nrr$r*s r'rzSankey.valueformat%r,r(c |dS)aL Adds a unit to follow the value in the hover tooltip. Add a space if a separation is necessary from the value. The 'valuesuffix' property is a string and must be specified as: - A string - A number that will be converted to a string Returns ------- str rr$r%s r'rzSankey.valuesuffix)sM""r(c||d<y)Nrr$r*s r'rzSankey.valuesuffix9r,r(c |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 r'rzSankey.visible=sIr(c||d<y)Nrr$r*s r'rzSankey.visibleNrQr(c |jdS)Nr)_propsr%s r'rz Sankey.typeRs{{6""r(cy)Na arrangement If value is `snap` (the default), the node arrangement is assisted by automatic snapping of elements to preserve space between nodes specified via `nodepad`. If value is `perpendicular`, the nodes can only move along a line perpendicular to the flow. If value is `freeform`, the nodes can freely move on the plane. If value is `fixed`, the nodes are stationary. 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.sankey.Domain` 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. Note that this attribute is superseded by `node.hoverinfo` and `node.hoverinfo` for nodes and links respectively. hoverlabel :class:`plotly.graph_objects.sankey.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.sankey.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. link The links of the Sankey plot. 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. node The nodes of the Sankey plot. orientation Sets the orientation of the Sankey diagram. selectedpoints Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect. stream :class:`plotly.graph_objects.sankey.Stream` instance or dict with compatible properties textfont Sets the font for node labels 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. valueformat Sets the value formatting rule using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. valuesuffix Adds a unit to follow the value in the hover tooltip. Add a space if a separation is necessary from the value. 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_descriptionszSankey._prop_descriptionsVsE r(c t|dd|vr |d|_y|i}nXt||jr|j }n1t|t rtj|}n td|jdd|_ |jdd|_ |jd |||jd |||jd |||jd |||jd |||jd|||jd|||jd|| |jd|| |jd|| |jd|| |jd|| |jd|||jd|||jd|||jd|||jd|||jd|||jd|||jd|||jd|||jd|||jd|||jd |||jd!|||jd"||d|jd#<|jd#d|jd$it |fi|d|_ y)%a Construct a new Sankey object Sankey plots for network flow data analysis. The nodes are specified in `nodes` and the links between sources and targets in `links`. The colors are set in `nodes[i].color` and `links[i].color`, otherwise defaults are used. Parameters ---------- arg dict of properties compatible with this constructor or an instance of :class:`plotly.graph_objs.Sankey` arrangement If value is `snap` (the default), the node arrangement is assisted by automatic snapping of elements to preserve space between nodes specified via `nodepad`. If value is `perpendicular`, the nodes can only move along a line perpendicular to the flow. If value is `freeform`, the nodes can freely move on the plane. If value is `fixed`, the nodes are stationary. 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.sankey.Domain` 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. Note that this attribute is superseded by `node.hoverinfo` and `node.hoverinfo` for nodes and links respectively. hoverlabel :class:`plotly.graph_objects.sankey.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.sankey.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. link The links of the Sankey plot. 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. node The nodes of the Sankey plot. orientation Sets the orientation of the Sankey diagram. selectedpoints Array containing integer indices of selected points. Has an effect only for traces that support selections. Note that an empty array means an empty selection where the `unselected` are turned on for all points, whereas, any other non-array values means no selection all where the `selected` and `unselected` styles have no effect. stream :class:`plotly.graph_objects.sankey.Stream` instance or dict with compatible properties textfont Sets the font for node labels 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. valueformat Sets the value formatting rule using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. valuesuffix Adds a unit to follow the value in the hover tooltip. Add a space if a separation is necessary from the value. 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 ------- Sankey r_parentNzThe first argument to the plotly.graph_objs.Sankey constructor must be a dict or an instance of :class:`plotly.graph_objs.Sankey` skip_invalidF _validateTrrr rrrrrrr"rrr r rr r rr!rrr rrrrrr$)super__init__rm isinstance __class__to_plotly_jsondict_copycopy ValueErrorpop _skip_invalidro _set_propertyri_process_kwargs)r&argrrr rrrrrrr"rrr r rr r rr!rrr rrrrkwargsrss r'rqzSankey.__init__sj "  !),DL  ;C T^^ ,$$&C T "**S/C45 5 $ZZ>K6 =#{; <j9 ?C? 8S&1 ;Y7 <j9 5#s+ 8S&1 8S&1 -s4DE <j9 =#{; 63- 63- 9c73 63- 63- =#{; +S.A 8S&1 :sH5 5#s+ <j9 =#{; =#{; 9c73& F 3tC2623"r()NNNNNNNNNNNNNNNNNNNNNNNNNNN)&__name__ __module__ __qualname___parent_path_str _path_str _valid_propspropertyrsetterrr rrrrrrr"rrr r rr r rr!rrr rrrrrrkrq __classcell__)rss@r'rrs1IL<##("""" !! % %$$   ]]!!(   " "!!   ZZ   ]]$ ]] ( (''""(!! # #""  [[* [[   ^^   [[  [[ # #""&&"%%   ]]  __   ZZ""4!!##""" # #""  ^^##F F T       9g#g#r(r)plotly.basedatatypesr_BaseTraceTyperwrvrr$r(r'rsA~#^~#r(