Chart-Plotly
view release on metacpan or search on metacpan
lib/Chart/Plotly/Trace/Bar.pm view on Meta::CPAN
documentation =>
"Alternate to `x`. Builds a linear space of x coordinates. Use with `dx` where `x0` is the starting coordinate and `dx` the step.",
);
has xaxis => (
is => "rw",
documentation =>
"Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.",
);
has xcalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `x` date data.",
);
has xhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has xperiod => (
lib/Chart/Plotly/Trace/Bar.pm view on Meta::CPAN
documentation =>
"Alternate to `y`. Builds a linear space of y coordinates. Use with `dy` where `y0` is the starting coordinate and `dy` the step.",
);
has yaxis => (
is => "rw",
documentation =>
"Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.",
);
has ycalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `y` date data.",
);
has yhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has yperiod => (
lib/Chart/Plotly/Trace/Bar.pm view on Meta::CPAN
Sets the x coordinates.
=item * x0
Alternate to `x`. Builds a linear space of x coordinates. Use with `dx` where `x0` is the starting coordinate and `dx` the step.
=item * xaxis
Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.
=item * xcalendar
Sets the calendar system to use with `x` date data.
=item * 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...
=item * xperiod
Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *n* on the x axis. Special values in the form of *n* could be used to declare the number of months. In this case `n` must be a positive integer.
=item * xperiod0
lib/Chart/Plotly/Trace/Bar.pm view on Meta::CPAN
Sets the y coordinates.
=item * y0
Alternate to `y`. Builds a linear space of y coordinates. Use with `dy` where `y0` is the starting coordinate and `dy` the step.
=item * yaxis
Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.
=item * ycalendar
Sets the calendar system to use with `y` date data.
=item * 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...
=item * yperiod
Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *n* on the y axis. Special values in the form of *n* could be used to declare the number of months. In this case `n` must be a positive integer.
=item * yperiod0
lib/Chart/Plotly/Trace/Box.pm view on Meta::CPAN
documentation =>
"Sets the x coordinate for single-box traces or the starting coordinate for multi-box traces set using q1/median/q3. See overview for more info.",
);
has xaxis => (
is => "rw",
documentation =>
"Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.",
);
has xcalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `x` date data.",
);
has xhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has xperiod => (
lib/Chart/Plotly/Trace/Box.pm view on Meta::CPAN
documentation =>
"Sets the y coordinate for single-box traces or the starting coordinate for multi-box traces set using q1/median/q3. See overview for more info.",
);
has yaxis => (
is => "rw",
documentation =>
"Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.",
);
has ycalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `y` date data.",
);
has yhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has yperiod => (
lib/Chart/Plotly/Trace/Box.pm view on Meta::CPAN
Sets the x sample data or coordinates. See overview for more info.
=item * x0
Sets the x coordinate for single-box traces or the starting coordinate for multi-box traces set using q1/median/q3. See overview for more info.
=item * xaxis
Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.
=item * xcalendar
Sets the calendar system to use with `x` date data.
=item * 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...
=item * xperiod
Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *n* on the x axis. Special values in the form of *n* could be used to declare the number of months. In this case `n` must be a positive integer.
=item * xperiod0
lib/Chart/Plotly/Trace/Box.pm view on Meta::CPAN
Sets the y sample data or coordinates. See overview for more info.
=item * y0
Sets the y coordinate for single-box traces or the starting coordinate for multi-box traces set using q1/median/q3. See overview for more info.
=item * yaxis
Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.
=item * ycalendar
Sets the calendar system to use with `y` date data.
=item * 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...
=item * yperiod
Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *n* on the y axis. Special values in the form of *n* could be used to declare the number of months. In this case `n` must be a positive integer.
=item * yperiod0
lib/Chart/Plotly/Trace/Candlestick.pm view on Meta::CPAN
isa => "ArrayRef|PDL",
documentation => "Sets the x coordinates. If absent, linear coordinate will be generated.",
);
has xaxis => (
is => "rw",
documentation =>
"Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.",
);
has xcalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `x` date data.",
);
has xhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has xperiod => (
lib/Chart/Plotly/Trace/Candlestick.pm view on Meta::CPAN
Sets the width of the whiskers relative to the box' width. For example, with 1, the whiskers are as wide as the box(es).
=item * x
Sets the x coordinates. If absent, linear coordinate will be generated.
=item * xaxis
Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.
=item * xcalendar
Sets the calendar system to use with `x` date data.
=item * 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...
=item * xperiod
Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *n* on the x axis. Special values in the form of *n* could be used to declare the number of months. In this case `n` must be a positive integer.
=item * xperiod0
lib/Chart/Plotly/Trace/Contour.pm view on Meta::CPAN
documentation =>
"Alternate to `x`. Builds a linear space of x coordinates. Use with `dx` where `x0` is the starting coordinate and `dx` the step.",
);
has xaxis => (
is => "rw",
documentation =>
"Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.",
);
has xcalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `x` date data.",
);
has xhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has xperiod => (
lib/Chart/Plotly/Trace/Contour.pm view on Meta::CPAN
documentation =>
"Alternate to `y`. Builds a linear space of y coordinates. Use with `dy` where `y0` is the starting coordinate and `dy` the step.",
);
has yaxis => (
is => "rw",
documentation =>
"Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.",
);
has ycalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `y` date data.",
);
has yhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has yperiod => (
lib/Chart/Plotly/Trace/Contour.pm view on Meta::CPAN
Sets the x coordinates.
=item * x0
Alternate to `x`. Builds a linear space of x coordinates. Use with `dx` where `x0` is the starting coordinate and `dx` the step.
=item * xaxis
Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.
=item * xcalendar
Sets the calendar system to use with `x` date data.
=item * 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...
=item * xperiod
Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *n* on the x axis. Special values in the form of *n* could be used to declare the number of months. In this case `n` must be a positive integer.
=item * xperiod0
lib/Chart/Plotly/Trace/Contour.pm view on Meta::CPAN
Sets the y coordinates.
=item * y0
Alternate to `y`. Builds a linear space of y coordinates. Use with `dy` where `y0` is the starting coordinate and `dy` the step.
=item * yaxis
Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.
=item * ycalendar
Sets the calendar system to use with `y` date data.
=item * 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...
=item * yperiod
Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *n* on the y axis. Special values in the form of *n* could be used to declare the number of months. In this case `n` must be a positive integer.
=item * yperiod0
lib/Chart/Plotly/Trace/Heatmap.pm view on Meta::CPAN
documentation =>
"Alternate to `x`. Builds a linear space of x coordinates. Use with `dx` where `x0` is the starting coordinate and `dx` the step.",
);
has xaxis => (
is => "rw",
documentation =>
"Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.",
);
has xcalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `x` date data.",
);
has xgap => ( is => "rw",
isa => "Num",
documentation => "Sets the horizontal gap (in pixels) between bricks.",
);
has xhoverformat => (
is => "rw",
isa => "Str",
lib/Chart/Plotly/Trace/Heatmap.pm view on Meta::CPAN
documentation =>
"Alternate to `y`. Builds a linear space of y coordinates. Use with `dy` where `y0` is the starting coordinate and `dy` the step.",
);
has yaxis => (
is => "rw",
documentation =>
"Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.",
);
has ycalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `y` date data.",
);
has ygap => ( is => "rw",
isa => "Num",
documentation => "Sets the vertical gap (in pixels) between bricks.",
);
has yhoverformat => (
is => "rw",
isa => "Str",
lib/Chart/Plotly/Trace/Heatmap.pm view on Meta::CPAN
Sets the x coordinates.
=item * x0
Alternate to `x`. Builds a linear space of x coordinates. Use with `dx` where `x0` is the starting coordinate and `dx` the step.
=item * xaxis
Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.
=item * xcalendar
Sets the calendar system to use with `x` date data.
=item * xgap
Sets the horizontal gap (in pixels) between bricks.
=item * 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...
=item * xperiod
lib/Chart/Plotly/Trace/Heatmap.pm view on Meta::CPAN
Sets the y coordinates.
=item * y0
Alternate to `y`. Builds a linear space of y coordinates. Use with `dy` where `y0` is the starting coordinate and `dy` the step.
=item * yaxis
Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.
=item * ycalendar
Sets the calendar system to use with `y` date data.
=item * ygap
Sets the vertical gap (in pixels) between bricks.
=item * 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...
=item * yperiod
lib/Chart/Plotly/Trace/Histogram.pm view on Meta::CPAN
has xaxis => (
is => "rw",
documentation =>
"Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.",
);
has xbins => ( is => "rw",
isa => "Maybe[HashRef]|Chart::Plotly::Trace::Histogram::Xbins", );
has xcalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `x` date data.",
);
has xhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has xsrc => ( is => "rw",
lib/Chart/Plotly/Trace/Histogram.pm view on Meta::CPAN
has yaxis => (
is => "rw",
documentation =>
"Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.",
);
has ybins => ( is => "rw",
isa => "Maybe[HashRef]|Chart::Plotly::Trace::Histogram::Ybins", );
has ycalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `y` date data.",
);
has yhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has ysrc => ( is => "rw",
lib/Chart/Plotly/Trace/Histogram.pm view on Meta::CPAN
=item * x
Sets the sample data to be binned on the x axis.
=item * xaxis
Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.
=item * xbins
=item * xcalendar
Sets the calendar system to use with `x` date data.
=item * 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...
=item * xsrc
Sets the source reference on Chart Studio Cloud for `x`.
=item * y
Sets the sample data to be binned on the y axis.
=item * yaxis
Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.
=item * ybins
=item * ycalendar
Sets the calendar system to use with `y` date data.
=item * 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...
=item * ysrc
Sets the source reference on Chart Studio Cloud for `y`.
=back
lib/Chart/Plotly/Trace/Histogram2d.pm view on Meta::CPAN
has xbingroup => (
is => "rw",
isa => "Str",
documentation =>
"Set a group of histogram traces which will have compatible x-bin settings. Using `xbingroup`, histogram2d and histogram2dcontour traces (on axes of the same axis type) can have compatible x-bin settings. Note that the same `xbingroup` value c...
);
has xbins => ( is => "rw",
isa => "Maybe[HashRef]|Chart::Plotly::Trace::Histogram2d::Xbins", );
has xcalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `x` date data.",
);
has xgap => ( is => "rw",
isa => "Num",
documentation => "Sets the horizontal gap (in pixels) between bricks.",
);
has xhoverformat => (
is => "rw",
isa => "Str",
lib/Chart/Plotly/Trace/Histogram2d.pm view on Meta::CPAN
has ybingroup => (
is => "rw",
isa => "Str",
documentation =>
"Set a group of histogram traces which will have compatible y-bin settings. Using `ybingroup`, histogram2d and histogram2dcontour traces (on axes of the same axis type) can have compatible y-bin settings. Note that the same `ybingroup` value c...
);
has ybins => ( is => "rw",
isa => "Maybe[HashRef]|Chart::Plotly::Trace::Histogram2d::Ybins", );
has ycalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `y` date data.",
);
has ygap => ( is => "rw",
isa => "Num",
documentation => "Sets the vertical gap (in pixels) between bricks.",
);
has yhoverformat => (
is => "rw",
isa => "Str",
lib/Chart/Plotly/Trace/Histogram2d.pm view on Meta::CPAN
=item * xaxis
Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.
=item * xbingroup
Set a group of histogram traces which will have compatible x-bin settings. Using `xbingroup`, histogram2d and histogram2dcontour traces (on axes of the same axis type) can have compatible x-bin settings. Note that the same `xbingroup` value can be u...
=item * xbins
=item * xcalendar
Sets the calendar system to use with `x` date data.
=item * xgap
Sets the horizontal gap (in pixels) between bricks.
=item * 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...
=item * xsrc
lib/Chart/Plotly/Trace/Histogram2d.pm view on Meta::CPAN
=item * yaxis
Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.
=item * ybingroup
Set a group of histogram traces which will have compatible y-bin settings. Using `ybingroup`, histogram2d and histogram2dcontour traces (on axes of the same axis type) can have compatible y-bin settings. Note that the same `ybingroup` value can be u...
=item * ybins
=item * ycalendar
Sets the calendar system to use with `y` date data.
=item * ygap
Sets the vertical gap (in pixels) between bricks.
=item * 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...
=item * ysrc
lib/Chart/Plotly/Trace/Histogram2dcontour.pm view on Meta::CPAN
has xbingroup => (
is => "rw",
isa => "Str",
documentation =>
"Set a group of histogram traces which will have compatible x-bin settings. Using `xbingroup`, histogram2d and histogram2dcontour traces (on axes of the same axis type) can have compatible x-bin settings. Note that the same `xbingroup` value c...
);
has xbins => ( is => "rw",
isa => "Maybe[HashRef]|Chart::Plotly::Trace::Histogram2dcontour::Xbins", );
has xcalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `x` date data.",
);
has xhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has xsrc => ( is => "rw",
lib/Chart/Plotly/Trace/Histogram2dcontour.pm view on Meta::CPAN
has ybingroup => (
is => "rw",
isa => "Str",
documentation =>
"Set a group of histogram traces which will have compatible y-bin settings. Using `ybingroup`, histogram2d and histogram2dcontour traces (on axes of the same axis type) can have compatible y-bin settings. Note that the same `ybingroup` value c...
);
has ybins => ( is => "rw",
isa => "Maybe[HashRef]|Chart::Plotly::Trace::Histogram2dcontour::Ybins", );
has ycalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `y` date data.",
);
has yhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has ysrc => ( is => "rw",
lib/Chart/Plotly/Trace/Histogram2dcontour.pm view on Meta::CPAN
=item * xaxis
Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.
=item * xbingroup
Set a group of histogram traces which will have compatible x-bin settings. Using `xbingroup`, histogram2d and histogram2dcontour traces (on axes of the same axis type) can have compatible x-bin settings. Note that the same `xbingroup` value can be u...
=item * xbins
=item * xcalendar
Sets the calendar system to use with `x` date data.
=item * 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...
=item * xsrc
Sets the source reference on Chart Studio Cloud for `x`.
=item * y
lib/Chart/Plotly/Trace/Histogram2dcontour.pm view on Meta::CPAN
=item * yaxis
Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.
=item * ybingroup
Set a group of histogram traces which will have compatible y-bin settings. Using `ybingroup`, histogram2d and histogram2dcontour traces (on axes of the same axis type) can have compatible y-bin settings. Note that the same `ybingroup` value can be u...
=item * ybins
=item * ycalendar
Sets the calendar system to use with `y` date data.
=item * 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...
=item * ysrc
Sets the source reference on Chart Studio Cloud for `y`.
=item * z
lib/Chart/Plotly/Trace/Mesh3d.pm view on Meta::CPAN
"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).",
);
has x => (
is => "rw",
isa => "ArrayRef|PDL",
documentation =>
"Sets the X coordinates of the vertices. The nth element of vectors `x`, `y` and `z` jointly represent the X, Y and Z coordinates of the nth vertex.",
);
has xcalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `x` date data.",
);
has xhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has xsrc => ( is => "rw",
lib/Chart/Plotly/Trace/Mesh3d.pm view on Meta::CPAN
documentation => "Sets the source reference on Chart Studio Cloud for `x`.",
);
has y => (
is => "rw",
isa => "ArrayRef|PDL",
documentation =>
"Sets the Y coordinates of the vertices. The nth element of vectors `x`, `y` and `z` jointly represent the X, Y and Z coordinates of the nth vertex.",
);
has ycalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `y` date data.",
);
has yhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has ysrc => ( is => "rw",
lib/Chart/Plotly/Trace/Mesh3d.pm view on Meta::CPAN
documentation => "Sets the source reference on Chart Studio Cloud for `y`.",
);
has z => (
is => "rw",
isa => "ArrayRef|PDL",
documentation =>
"Sets the Z coordinates of the vertices. The nth element of vectors `x`, `y` and `z` jointly represent the X, Y and Z coordinates of the nth vertex.",
);
has zcalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `z` date data.",
);
has zhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has zsrc => ( is => "rw",
lib/Chart/Plotly/Trace/Mesh3d.pm view on Meta::CPAN
Sets the source reference on Chart Studio Cloud for `vertexcolor`.
=item * 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).
=item * x
Sets the X coordinates of the vertices. The nth element of vectors `x`, `y` and `z` jointly represent the X, Y and Z coordinates of the nth vertex.
=item * xcalendar
Sets the calendar system to use with `x` date data.
=item * 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...
=item * xsrc
Sets the source reference on Chart Studio Cloud for `x`.
=item * y
Sets the Y coordinates of the vertices. The nth element of vectors `x`, `y` and `z` jointly represent the X, Y and Z coordinates of the nth vertex.
=item * ycalendar
Sets the calendar system to use with `y` date data.
=item * 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...
=item * ysrc
Sets the source reference on Chart Studio Cloud for `y`.
=item * z
Sets the Z coordinates of the vertices. The nth element of vectors `x`, `y` and `z` jointly represent the X, Y and Z coordinates of the nth vertex.
=item * zcalendar
Sets the calendar system to use with `z` date data.
=item * 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...
=item * zsrc
Sets the source reference on Chart Studio Cloud for `z`.
=back
lib/Chart/Plotly/Trace/Ohlc.pm view on Meta::CPAN
isa => "ArrayRef|PDL",
documentation => "Sets the x coordinates. If absent, linear coordinate will be generated.",
);
has xaxis => (
is => "rw",
documentation =>
"Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.",
);
has xcalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `x` date data.",
);
has xhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has xperiod => (
lib/Chart/Plotly/Trace/Ohlc.pm view on Meta::CPAN
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).
=item * x
Sets the x coordinates. If absent, linear coordinate will be generated.
=item * xaxis
Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.
=item * xcalendar
Sets the calendar system to use with `x` date data.
=item * 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...
=item * xperiod
Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *n* on the x axis. Special values in the form of *n* could be used to declare the number of months. In this case `n` must be a positive integer.
=item * xperiod0
lib/Chart/Plotly/Trace/Scatter.pm view on Meta::CPAN
documentation =>
"Alternate to `x`. Builds a linear space of x coordinates. Use with `dx` where `x0` is the starting coordinate and `dx` the step.",
);
has xaxis => (
is => "rw",
documentation =>
"Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.",
);
has xcalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `x` date data.",
);
has xhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has xperiod => (
lib/Chart/Plotly/Trace/Scatter.pm view on Meta::CPAN
documentation =>
"Alternate to `y`. Builds a linear space of y coordinates. Use with `dy` where `y0` is the starting coordinate and `dy` the step.",
);
has yaxis => (
is => "rw",
documentation =>
"Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.",
);
has ycalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `y` date data.",
);
has yhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has yperiod => (
lib/Chart/Plotly/Trace/Scatter.pm view on Meta::CPAN
Sets the x coordinates.
=item * x0
Alternate to `x`. Builds a linear space of x coordinates. Use with `dx` where `x0` is the starting coordinate and `dx` the step.
=item * xaxis
Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.
=item * xcalendar
Sets the calendar system to use with `x` date data.
=item * 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...
=item * xperiod
Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *n* on the x axis. Special values in the form of *n* could be used to declare the number of months. In this case `n` must be a positive integer.
=item * xperiod0
lib/Chart/Plotly/Trace/Scatter.pm view on Meta::CPAN
Sets the y coordinates.
=item * y0
Alternate to `y`. Builds a linear space of y coordinates. Use with `dy` where `y0` is the starting coordinate and `dy` the step.
=item * yaxis
Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.
=item * ycalendar
Sets the calendar system to use with `y` date data.
=item * 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...
=item * yperiod
Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *n* on the y axis. Special values in the form of *n* could be used to declare the number of months. In this case `n` must be a positive integer.
=item * yperiod0
lib/Chart/Plotly/Trace/Scatter3d.pm view on Meta::CPAN
is => "rw",
documentation =>
"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).",
);
has x => ( is => "rw",
isa => "ArrayRef|PDL",
documentation => "Sets the x coordinates.",
);
has xcalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `x` date data.",
);
has xhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has xsrc => ( is => "rw",
isa => "Str",
documentation => "Sets the source reference on Chart Studio Cloud for `x`.",
);
has y => ( is => "rw",
isa => "ArrayRef|PDL",
documentation => "Sets the y coordinates.",
);
has ycalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `y` date data.",
);
has yhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has ysrc => ( is => "rw",
isa => "Str",
documentation => "Sets the source reference on Chart Studio Cloud for `y`.",
);
has z => ( is => "rw",
isa => "ArrayRef|PDL",
documentation => "Sets the z coordinates.",
);
has zcalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `z` date data.",
);
has zhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has zsrc => ( is => "rw",
lib/Chart/Plotly/Trace/Scatter3d.pm view on Meta::CPAN
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 t...
=item * 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).
=item * x
Sets the x coordinates.
=item * xcalendar
Sets the calendar system to use with `x` date data.
=item * 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...
=item * xsrc
Sets the source reference on Chart Studio Cloud for `x`.
=item * y
Sets the y coordinates.
=item * ycalendar
Sets the calendar system to use with `y` date data.
=item * 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...
=item * ysrc
Sets the source reference on Chart Studio Cloud for `y`.
=item * z
Sets the z coordinates.
=item * zcalendar
Sets the calendar system to use with `z` date data.
=item * 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...
=item * zsrc
Sets the source reference on Chart Studio Cloud for `z`.
=back
lib/Chart/Plotly/Trace/Scattergl.pm view on Meta::CPAN
documentation =>
"Alternate to `x`. Builds a linear space of x coordinates. Use with `dx` where `x0` is the starting coordinate and `dx` the step.",
);
has xaxis => (
is => "rw",
documentation =>
"Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.",
);
has xcalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `x` date data.",
);
has xhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has xperiod => (
lib/Chart/Plotly/Trace/Scattergl.pm view on Meta::CPAN
documentation =>
"Alternate to `y`. Builds a linear space of y coordinates. Use with `dy` where `y0` is the starting coordinate and `dy` the step.",
);
has yaxis => (
is => "rw",
documentation =>
"Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.",
);
has ycalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `y` date data.",
);
has yhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has yperiod => (
lib/Chart/Plotly/Trace/Scattergl.pm view on Meta::CPAN
Sets the x coordinates.
=item * x0
Alternate to `x`. Builds a linear space of x coordinates. Use with `dx` where `x0` is the starting coordinate and `dx` the step.
=item * xaxis
Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.
=item * xcalendar
Sets the calendar system to use with `x` date data.
=item * 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...
=item * xperiod
Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *n* on the x axis. Special values in the form of *n* could be used to declare the number of months. In this case `n` must be a positive integer.
=item * xperiod0
lib/Chart/Plotly/Trace/Scattergl.pm view on Meta::CPAN
Sets the y coordinates.
=item * y0
Alternate to `y`. Builds a linear space of y coordinates. Use with `dy` where `y0` is the starting coordinate and `dy` the step.
=item * yaxis
Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.
=item * ycalendar
Sets the calendar system to use with `y` date data.
=item * 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...
=item * yperiod
Only relevant when the axis `type` is *date*. Sets the period positioning in milliseconds or *n* on the y axis. Special values in the form of *n* could be used to declare the number of months. In this case `n` must be a positive integer.
=item * yperiod0
lib/Chart/Plotly/Trace/Surface.pm view on Meta::CPAN
is => "rw",
documentation =>
"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).",
);
has x => ( is => "rw",
isa => "ArrayRef|PDL",
documentation => "Sets the x coordinates.",
);
has xcalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `x` date data.",
);
has xhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has xsrc => ( is => "rw",
isa => "Str",
documentation => "Sets the source reference on Chart Studio Cloud for `x`.",
);
has y => ( is => "rw",
isa => "ArrayRef|PDL",
documentation => "Sets the y coordinates.",
);
has ycalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `y` date data.",
);
has yhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has ysrc => ( is => "rw",
isa => "Str",
documentation => "Sets the source reference on Chart Studio Cloud for `y`.",
);
has z => ( is => "rw",
isa => "ArrayRef|PDL",
documentation => "Sets the z coordinates.",
);
has zcalendar => ( is => "rw",
isa => enum(
[ "chinese", "coptic", "discworld", "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
"julian", "mayan", "nanakshahi", "nepali", "persian", "taiwan", "thai", "ummalqura"
]
),
documentation => "Sets the calendar system to use with `z` date data.",
);
has zhoverformat => (
is => "rw",
isa => "Str",
documentation =>
"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...
);
has zsrc => ( is => "rw",
lib/Chart/Plotly/Trace/Surface.pm view on Meta::CPAN
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 t...
=item * 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).
=item * x
Sets the x coordinates.
=item * xcalendar
Sets the calendar system to use with `x` date data.
=item * 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...
=item * xsrc
Sets the source reference on Chart Studio Cloud for `x`.
=item * y
Sets the y coordinates.
=item * ycalendar
Sets the calendar system to use with `y` date data.
=item * 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...
=item * ysrc
Sets the source reference on Chart Studio Cloud for `y`.
=item * z
Sets the z coordinates.
=item * zcalendar
Sets the calendar system to use with `z` date data.
=item * 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...
=item * zsrc
Sets the source reference on Chart Studio Cloud for `z`.
=back
share/plotly.js/plotly.min.js view on Meta::CPAN
/**
* plotly.js v2.14.0
* Copyright 2012-2022, Plotly, Inc.
* All rights reserved.
* Licensed under the MIT license
*/
!function(t){if("object"==typeof exports&&"undefined"!=typeof module)module.exports=t();else if("function"==typeof define&&define.amd)define([],t);else{("undefined"!=typeof window?window:"undefined"!=typeof global?global:"undefined"!=typeof self?self...
/*!
* The buffer module from node.js, for the browser.
*
* @author Feross Aboukhadijeh <feross@feross.org> <http://feross.org>
* @license MIT
*/function i(t,e){if(t===e)return 0;for(var r=t.length,n=e.length,i=0,a=Math.min(r,n);i<a;++i)if(t[i]!==e[i]){r=t[i],n=e[i];break}return r<n?-1:n<r?1:0}function a(t){return r.Buffer&&"function"==typeof r.Buffer.isBuffer?r.Buffer.isBuffer(t):!(null==...
/*!
* The buffer module from node.js, for the browser.
*
* @author Feross Aboukhadijeh <https://feross.org>
share/plotly.js/plotly.min.js view on Meta::CPAN
object-assign
(c) Sindre Sorhus
@license MIT
*/
"use strict";var n=Object.getOwnPropertySymbols,i=Object.prototype.hasOwnProperty,a=Object.prototype.propertyIsEnumerable;function o(t){if(null==t)throw new TypeError("Object.assign cannot be called with null or undefined");return Object(t)}e.exports...
/*
* @copyright 2016 Sean Connelly (@voidqk), http://syntheti.cc
* @license MIT
* @preserve Project Home: https://github.com/voidqk/polybooljs
*/
var n,i=t("./lib/build-log"),a=t("./lib/epsilon"),o=t("./lib/intersecter"),s=t("./lib/segment-chainer"),l=t("./lib/segment-selector"),c=t("./lib/geojson"),u=!1,f=a();function h(t,e,r){var i=n.segments(t),a=n.segments(e),o=r(n.combine(i,a));return n.p...
/*!
* The buffer module from node.js, for the browser.
*
* @author Feross Aboukhadijeh <https://feross.org>
* @license MIT
*/
"use strict";var e=t("base64-js"),n=t("ieee754");r.Buffer=a,r.SlowBuffer=function(t){+t!=t&&(t=0);return a.alloc(+t)},r.INSPECT_MAX_BYTES=50;function i(t){if(t>2147483647)throw new RangeError('The value "'+t+'" is invalid for option "size"');var e=ne...
/*!
* Determine if an object is a Buffer
*
( run in 0.320 second using v1.01-cache-2.11-cpan-5dc5da66d9d )