mirror of
https://github.com/aykhans/AzSuicideDataVisualization.git
synced 2025-07-01 06:07:47 +00:00
first commit
This commit is contained in:
Ayxan
322
.venv/Lib/site-packages/plotly/validators/_scatter3d.py
Normal file
322
.venv/Lib/site-packages/plotly/validators/_scatter3d.py
Normal file
@ -0,0 +1,322 @@
|
||||
import _plotly_utils.basevalidators
|
||||
|
||||
|
||||
class Scatter3DValidator(_plotly_utils.basevalidators.CompoundValidator):
|
||||
def __init__(self, plotly_name="scatter3d", parent_name="", **kwargs):
|
||||
super(Scatter3DValidator, self).__init__(
|
||||
plotly_name=plotly_name,
|
||||
parent_name=parent_name,
|
||||
data_class_str=kwargs.pop("data_class_str", "Scatter3d"),
|
||||
data_docs=kwargs.pop(
|
||||
"data_docs",
|
||||
"""
|
||||
connectgaps
|
||||
Determines whether or not gaps (i.e. {nan} or
|
||||
missing values) in the provided data arrays are
|
||||
connected.
|
||||
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`.
|
||||
error_x
|
||||
:class:`plotly.graph_objects.scatter3d.ErrorX`
|
||||
instance or dict with compatible properties
|
||||
error_y
|
||||
:class:`plotly.graph_objects.scatter3d.ErrorY`
|
||||
instance or dict with compatible properties
|
||||
error_z
|
||||
:class:`plotly.graph_objects.scatter3d.ErrorZ`
|
||||
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.scatter3d.Hoverlab
|
||||
el` 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/tre
|
||||
e/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.
|
||||
Anything contained in tag `<extra>` is
|
||||
displayed in the secondary box, for example
|
||||
"<extra>{fullData.name}</extra>". To hide the
|
||||
secondary box completely, use an empty tag
|
||||
`<extra></extra>`.
|
||||
hovertemplatesrc
|
||||
Sets the source reference on Chart Studio Cloud
|
||||
for `hovertemplate`.
|
||||
hovertext
|
||||
Sets text elements associated with each (x,y,z)
|
||||
triplet. If a single string, the same string
|
||||
appears over all the data points. If an array
|
||||
of string, the items are mapped in order to the
|
||||
this trace's (x,y,z) coordinates. 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`.
|
||||
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.
|
||||
legendgrouptitle
|
||||
:class:`plotly.graph_objects.scatter3d.Legendgr
|
||||
ouptitle` 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.
|
||||
line
|
||||
:class:`plotly.graph_objects.scatter3d.Line`
|
||||
instance or dict with compatible properties
|
||||
marker
|
||||
:class:`plotly.graph_objects.scatter3d.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`.
|
||||
mode
|
||||
Determines the drawing mode for this scatter
|
||||
trace. If the provided `mode` includes "text"
|
||||
then the `text` elements appear at the
|
||||
coordinates. Otherwise, the `text` elements
|
||||
appear on hover. If there are less than 20
|
||||
points and the trace is not stacked then the
|
||||
default is "lines+markers". Otherwise, "lines".
|
||||
name
|
||||
Sets the trace name. The trace name appear as
|
||||
the legend item and on hover.
|
||||
opacity
|
||||
Sets the opacity of the trace.
|
||||
projection
|
||||
:class:`plotly.graph_objects.scatter3d.Projecti
|
||||
on` instance or dict with compatible properties
|
||||
scene
|
||||
Sets a reference between this trace's 3D
|
||||
coordinate system and a 3D scene. If "scene"
|
||||
(the default value), the (x,y,z) coordinates
|
||||
refer to `layout.scene`. If "scene2", the
|
||||
(x,y,z) coordinates refer to `layout.scene2`,
|
||||
and so on.
|
||||
showlegend
|
||||
Determines whether or not an item corresponding
|
||||
to this trace is shown in the legend.
|
||||
stream
|
||||
:class:`plotly.graph_objects.scatter3d.Stream`
|
||||
instance or dict with compatible properties
|
||||
surfaceaxis
|
||||
If "-1", the scatter points are not fill with a
|
||||
surface If 0, 1, 2, the scatter points are
|
||||
filled with a Delaunay surface about the x, y,
|
||||
z respectively.
|
||||
surfacecolor
|
||||
Sets the surface fill color.
|
||||
text
|
||||
Sets text elements associated with each (x,y,z)
|
||||
triplet. If a single string, the same string
|
||||
appears over all the data points. If an array
|
||||
of string, the items are mapped in order to the
|
||||
this trace's (x,y,z) coordinates. If trace
|
||||
`hoverinfo` contains a "text" flag and
|
||||
"hovertext" is not set, these elements will be
|
||||
seen in the hover labels.
|
||||
textfont
|
||||
:class:`plotly.graph_objects.scatter3d.Textfont
|
||||
` instance or dict with compatible properties
|
||||
textposition
|
||||
Sets the positions of the `text` elements with
|
||||
respects to the (x,y) coordinates.
|
||||
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-fo
|
||||
rmat/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.
|
||||
texttemplatesrc
|
||||
Sets the source reference on Chart Studio Cloud
|
||||
for `texttemplate`.
|
||||
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).
|
||||
x
|
||||
Sets the x coordinates.
|
||||
xcalendar
|
||||
Sets the calendar system to use with `x` date
|
||||
data.
|
||||
xhoverformat
|
||||
Sets the hover text formatting rulefor `x`
|
||||
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. And for dates see:
|
||||
https://github.com/d3/d3-time-
|
||||
format/tree/v2.2.3#locale_format. We add two
|
||||
items to d3's date formatter: "%h" for half of
|
||||
the year as a decimal number as well as "%{n}f"
|
||||
for fractional seconds with n digits. For
|
||||
example, *2016-10-13 09:15:23.456* with
|
||||
tickformat "%H~%M~%S.%2f" would display
|
||||
*09~15~23.46*By default the values are
|
||||
formatted using `xaxis.hoverformat`.
|
||||
xsrc
|
||||
Sets the source reference on Chart Studio Cloud
|
||||
for `x`.
|
||||
y
|
||||
Sets the y coordinates.
|
||||
ycalendar
|
||||
Sets the calendar system to use with `y` date
|
||||
data.
|
||||
yhoverformat
|
||||
Sets the hover text formatting rulefor `y`
|
||||
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. And for dates see:
|
||||
https://github.com/d3/d3-time-
|
||||
format/tree/v2.2.3#locale_format. We add two
|
||||
items to d3's date formatter: "%h" for half of
|
||||
the year as a decimal number as well as "%{n}f"
|
||||
for fractional seconds with n digits. For
|
||||
example, *2016-10-13 09:15:23.456* with
|
||||
tickformat "%H~%M~%S.%2f" would display
|
||||
*09~15~23.46*By default the values are
|
||||
formatted using `yaxis.hoverformat`.
|
||||
ysrc
|
||||
Sets the source reference on Chart Studio Cloud
|
||||
for `y`.
|
||||
z
|
||||
Sets the z coordinates.
|
||||
zcalendar
|
||||
Sets the calendar system to use with `z` date
|
||||
data.
|
||||
zhoverformat
|
||||
Sets the hover text formatting rulefor `z`
|
||||
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. And for dates see:
|
||||
https://github.com/d3/d3-time-
|
||||
format/tree/v2.2.3#locale_format. We add two
|
||||
items to d3's date formatter: "%h" for half of
|
||||
the year as a decimal number as well as "%{n}f"
|
||||
for fractional seconds with n digits. For
|
||||
example, *2016-10-13 09:15:23.456* with
|
||||
tickformat "%H~%M~%S.%2f" would display
|
||||
*09~15~23.46*By default the values are
|
||||
formatted using `zaxis.hoverformat`.
|
||||
zsrc
|
||||
Sets the source reference on Chart Studio Cloud
|
||||
for `z`.
|
||||
""",
|
||||
),
|
||||
**kwargs,
|
||||
)
|
||||
Reference in New Issue
Block a user