You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/** Sets the quantity of component `a` in each data point. If `a`, `b`, and `c` are all provided, they need not be normalized, only the relative values matter. If only two arrays are provided they must be normalized to match `ternary<i>.sum`. */
9729
+
a?: Datum[] | Datum[][] | TypedArray;
9730
+
/** Sets the quantity of component `a` in each data point. If `a`, `b`, and `c` are all provided, they need not be normalized, only the relative values matter. If only two arrays are provided they must be normalized to match `ternary<i>.sum`. */
9731
+
b?: Datum[] | Datum[][] | TypedArray;
9732
+
/** Sets the quantity of component `a` in each data point. If `a`, `b`, and `c` are all provided, they need not be normalized, only the relative values matter. If only two arrays are provided they must be normalized to match `ternary<i>.sum`. */
9733
+
c?: Datum[] | Datum[][] | TypedArray;
9734
+
/**
9735
+
* Determines whether or not gaps (i.e. {nan} or missing values) in the provided data arrays are connected.
9736
+
* @default false
9737
+
*/
9738
+
connectgaps?: boolean;
9739
+
/** 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 */
9740
+
customdata?: Datum[] | Datum[][] | TypedArray;
9741
+
/**
9742
+
* Sets the area to fill with a solid color. Use with `fillcolor` if not *none*. scatterternary has a subset of the options available to scatter. *toself* connects the endpoints of the trace (or each segment of the trace if it has gaps) into a closed shape. *tonext* fills the space between two traces if one completely encloses the other (eg consecutive contour lines), and behaves like *toself* if there is no trace before it. *tonext* should not be used if one trace does not enclose the other.
9743
+
* @default 'none'
9744
+
*/
9745
+
fill?: 'none' | 'toself' | 'tonext';
9746
+
/** Sets the fill color. Defaults to a half-transparent variant of the line color, marker color, or marker line color, whichever is available. */
9747
+
fillcolor?: Color;
9748
+
/**
9749
+
* Determines what trace information appears 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.
/** 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. Variables that can't be found will be replaced with the specifier. For example, a template of "data: %{x}, %{y}" will result in a value of "data: 1, %{y}" if x is 1 and y is missing. Variables with an undefined value will be replaced with the fallback value. 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, all 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>`. */
9755
+
hovertemplate?: string | string[];
9756
+
/**
9757
+
* Fallback string that's displayed when a variable referenced in a template is missing. If the boolean value 'false' is passed in, the specifier with the missing variable will be displayed.
9758
+
* @default '-'
9759
+
*/
9760
+
hovertemplatefallback?: any;
9761
+
/** Sets hover text elements associated with each (a,b,c) point. If a single string, the same string appears over all the data points. If an array of strings, the items are mapped in order to the data points in (a,b,c). To be seen, trace `hoverinfo` must contain a *text* flag. */
9762
+
hovertext?: string | string[];
9763
+
/** 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. */
9764
+
ids?: Datum[] | Datum[][] | TypedArray;
9765
+
/**
9766
+
* 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.
9767
+
* @default 'legend'
9768
+
*/
9769
+
legend?: string;
9770
+
/** 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. */
9771
+
legendgroup?: string;
9772
+
legendgrouptitle?: LegendGroupTitle;
9773
+
/**
9774
+
* 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.
9775
+
* @default 1000
9776
+
*/
9777
+
legendrank?: number;
9778
+
/**
9779
+
* Sets the width (in px or fraction) of the legend for this trace.
9780
+
* Minimum: 0
9781
+
*/
9782
+
legendwidth?: number;
9783
+
line?: {
9784
+
/** Sets the line color. */
9785
+
color?: Color;
9786
+
/**
9787
+
* Sets the style of the lines.
9788
+
* @default 'solid'
9789
+
*/
9790
+
dash?: Dash;
9791
+
/**
9792
+
* Sets the line width (in px).
9793
+
* @default 2
9794
+
* Minimum: 0
9795
+
*/
9796
+
width?: number;
9797
+
};
9798
+
marker?: _internal.Marker;
9799
+
/** 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. */
9800
+
meta?: any;
9801
+
/**
9802
+
* 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*.
/** Sets the trace name. The trace name appears as the legend item and on hover. */
9807
+
name?: string;
9808
+
/**
9809
+
* Sets the opacity of the trace.
9810
+
* @default 1
9811
+
* Range: [0, 1]
9812
+
*/
9813
+
opacity?: number;
9814
+
selected?: {
9815
+
marker?: {
9816
+
/** Sets the marker color of selected points. */
9817
+
color?: Color;
9818
+
/**
9819
+
* Sets the marker opacity of selected points.
9820
+
* Range: [0, 1]
9821
+
*/
9822
+
opacity?: number;
9823
+
/**
9824
+
* Sets the marker size of selected points.
9825
+
* Minimum: 0
9826
+
*/
9827
+
size?: number;
9828
+
};
9829
+
textfont?: Font;
9830
+
};
9831
+
/** 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. */
9832
+
selectedpoints?: any;
9833
+
/**
9834
+
* Determines whether or not an item corresponding to this trace is shown in the legend.
9835
+
* @default true
9836
+
*/
9837
+
showlegend?: boolean;
9838
+
/**
9839
+
* Sets a reference between this trace's data coordinates and a ternary subplot. If *ternary* (the default value), the data refer to `layout.ternary`. If *ternary2*, the data refer to `layout.ternary2`, and so on.
9840
+
* @default 'ternary'
9841
+
*/
9842
+
subplot?: string;
9843
+
/**
9844
+
* The number each triplet should sum to, if only two of `a`, `b`, and `c` are provided. This overrides `ternary<i>.sum` to normalize this specific trace, but does not affect the values displayed on the axes. 0 (or missing) means to use ternary<i>.sum
9845
+
* @default 0
9846
+
* Minimum: 0
9847
+
*/
9848
+
sum?: number;
9849
+
/** Sets text elements associated with each (a,b,c) point. If a single string, the same string appears over all the data points. If an array of strings, the items are mapped in order to the data points in (a,b,c). If trace `hoverinfo` contains a *text* flag and *hovertext* is not set, these elements will be seen in the hover labels. */
9850
+
text?: string | string[];
9851
+
/** Sets the text font. */
9852
+
textfont?: {
9853
+
color?: Color | Color[];
9854
+
/** HTML font family - the typeface that will be applied by the web browser. The web browser can only apply a font if it is available on the system where it runs. Provide multiple font families, separated by commas, to indicate the order in which to apply fonts if they aren't available. */
9855
+
family?: string | string[];
9856
+
/**
9857
+
* Minimum: 1
9858
+
*/
9859
+
size?: number | number[];
9860
+
/**
9861
+
* Sets whether a font should be styled with a normal or italic face from its family.
/** Template string used for rendering the information text that appears 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. Variables that can't be found will be replaced with the specifier. For example, a template of "data: %{x}, %{y}" will result in a value of "data: 1, %{y}" if x is 1 and y is missing. Variables with an undefined value will be replaced with the fallback value. All attributes that can be specified per-point (the ones that are `arrayOk: true`) are available. Finally, the template string has access to variables `a`, `b`, `c` and `text`. */
9882
+
texttemplate?: string | string[];
9883
+
/**
9884
+
* Fallback string that's displayed when a variable referenced in a template is missing. If the boolean value 'false' is passed in, the specifier with the missing variable will be displayed.
9885
+
* @default '-'
9886
+
*/
9887
+
texttemplatefallback?: any;
9888
+
type?: 'scatterternarygl';
9889
+
/** Assign an id to this trace, Use this to provide object constancy between traces during animations and transitions. */
9890
+
uid?: string;
9891
+
/** 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. */
9892
+
uirevision?: any;
9893
+
unselected?: {
9894
+
marker?: {
9895
+
/** Sets the marker color of unselected points, applied only when a selection exists. */
9896
+
color?: Color;
9897
+
/**
9898
+
* Sets the marker opacity of unselected points, applied only when a selection exists.
9899
+
* Range: [0, 1]
9900
+
*/
9901
+
opacity?: number;
9902
+
/**
9903
+
* Sets the marker size of unselected points, applied only when a selection exists.
9904
+
* Minimum: 0
9905
+
*/
9906
+
size?: number;
9907
+
};
9908
+
textfont?: Font;
9909
+
};
9910
+
/**
9911
+
* 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).
9912
+
* @default true
9913
+
*/
9914
+
visible?: true | false | 'legendonly';
9915
+
}
9916
+
9727
9917
export interface SplomData {
9728
9918
/** 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 */
0 commit comments