Sets the source reference on Chart Studio Cloud for  family .

Sets the source reference on Chart Studio Cloud for  size .

Sets the source reference on Chart Studio Cloud for  color .

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

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.

Sets the source reference on Chart Studio Cloud for  bgcolor .

Sets the source reference on Chart Studio Cloud for  bordercolor .

Sets the source reference on Chart Studio Cloud for  align .

Sets the source reference on Chart Studio Cloud for  namelength .

The stream id number links a data trace on a plot with a stream. See https://chart-studio.plotly.com/settings for more details.

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.

An array of operations that manipulate the trace data, for example filtering or sorting the data arrays.

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.