Interaction between “nan” data, unbounded coords, and stack plots
I have noticed a strange interaction since the last update of my Miktex packages that I cannot explain. Perhaps someone knows about it here. Here is an MWE
documentclass{article}
usepackage{tikz,pgfplots}
begin{document}
begin{tikzpicture}
begin{axis}[unbounded coords=jump, stack plots=y]
addplot[fill=gray, draw=black] table{123.tsv}
closedcycle;
addplot[fill=none, draw=black] table{123.tsv}
closedcycle;
end{axis}
end{tikzpicture}
end{document}
my data looks like this
1 nan
1.2 0.2
0.9 0.1
running the above produce the error: Undefined control sequence. [closedcycle;]
The error goes away if I do either of the following three things:
take out
unbounded coords=jump: nothing changes visibly, but no errortake out
stack plots=y: plot looks obviously differenttake out the
nan-line in the data: nothing changes visibly, but no error
I do not want to do either of these things (data and tikzpicture is supposed to be created by matlab2tikz who I cannot tell to not produce this) and the picture drawn under the errors looks good to me.
However, I have this error now (and only since the last update of my packages). Does anyone have an idea why it produces this error, why it wasn't produced before, and how to get around it?
What I tried:
adding
pgfplotsset{compat=x.x}: does not helptaking away the
closedcycle: produces undefined control sequenceaddplot
tikz-pgf pgfplots
edited Feb 7 at 5:56
Stefan Pinnow
19.8k83276
asked Feb 6 at 11:21
johaschnjohaschn
966
add a comment |
I have noticed a strange interaction since the last update of my Miktex packages that I cannot explain. Perhaps someone knows about it here. Here is an MWE
documentclass{article}
usepackage{tikz,pgfplots}
begin{document}
begin{tikzpicture}
begin{axis}[unbounded coords=jump, stack plots=y]
addplot[fill=gray, draw=black] table{123.tsv}
closedcycle;
addplot[fill=none, draw=black] table{123.tsv}
closedcycle;
end{axis}
end{tikzpicture}
end{document}
my data looks like this
1 nan
1.2 0.2
0.9 0.1
running the above produce the error: Undefined control sequence. [closedcycle;]
The error goes away if I do either of the following three things:
take out
unbounded coords=jump: nothing changes visibly, but no errortake out
stack plots=y: plot looks obviously differenttake out the
nan-line in the data: nothing changes visibly, but no error
I do not want to do either of these things (data and tikzpicture is supposed to be created by matlab2tikz who I cannot tell to not produce this) and the picture drawn under the errors looks good to me.
However, I have this error now (and only since the last update of my packages). Does anyone have an idea why it produces this error, why it wasn't produced before, and how to get around it?
What I tried:
adding
pgfplotsset{compat=x.x}: does not helptaking away the
closedcycle: produces undefined control sequenceaddplot
tikz-pgf pgfplots
edited Feb 7 at 5:56
Stefan Pinnow
19.8k83276
asked Feb 6 at 11:21
johaschnjohaschn
966
1
Make a bug report, pgf/tikz changed and now something is undefined ...
– Ulrike Fischer
Feb 6 at 11:49
bug report created: sourceforge.net/p/pgf/bugs/512
– johaschn
Feb 6 at 13:42
add a comment |
I have noticed a strange interaction since the last update of my Miktex packages that I cannot explain. Perhaps someone knows about it here. Here is an MWE
documentclass{article}
usepackage{tikz,pgfplots}
begin{document}
begin{tikzpicture}
begin{axis}[unbounded coords=jump, stack plots=y]
addplot[fill=gray, draw=black] table{123.tsv}
closedcycle;
addplot[fill=none, draw=black] table{123.tsv}
closedcycle;
end{axis}
end{tikzpicture}
end{document}
my data looks like this
1 nan
1.2 0.2
0.9 0.1
running the above produce the error: Undefined control sequence. [closedcycle;]
The error goes away if I do either of the following three things:
take out
unbounded coords=jump: nothing changes visibly, but no errortake out
stack plots=y: plot looks obviously differenttake out the
nan-line in the data: nothing changes visibly, but no error
I do not want to do either of these things (data and tikzpicture is supposed to be created by matlab2tikz who I cannot tell to not produce this) and the picture drawn under the errors looks good to me.
However, I have this error now (and only since the last update of my packages). Does anyone have an idea why it produces this error, why it wasn't produced before, and how to get around it?
What I tried:
adding
pgfplotsset{compat=x.x}: does not helptaking away the
closedcycle: produces undefined control sequenceaddplot
tikz-pgf pgfplots
edited Feb 7 at 5:56
Stefan Pinnow
19.8k83276
asked Feb 6 at 11:21
johaschnjohaschn
966
I have noticed a strange interaction since the last update of my Miktex packages that I cannot explain. Perhaps someone knows about it here. Here is an MWE
documentclass{article}
usepackage{tikz,pgfplots}
begin{document}
begin{tikzpicture}
begin{axis}[unbounded coords=jump, stack plots=y]
addplot[fill=gray, draw=black] table{123.tsv}
closedcycle;
addplot[fill=none, draw=black] table{123.tsv}
closedcycle;
end{axis}
end{tikzpicture}
end{document}
my data looks like this
1 nan
1.2 0.2
0.9 0.1
running the above produce the error: Undefined control sequence. [closedcycle;]
The error goes away if I do either of the following three things:
take out
unbounded coords=jump: nothing changes visibly, but no errortake out
stack plots=y: plot looks obviously differenttake out the
nan-line in the data: nothing changes visibly, but no error
I do not want to do either of these things (data and tikzpicture is supposed to be created by matlab2tikz who I cannot tell to not produce this) and the picture drawn under the errors looks good to me.
However, I have this error now (and only since the last update of my packages). Does anyone have an idea why it produces this error, why it wasn't produced before, and how to get around it?
What I tried:
adding
pgfplotsset{compat=x.x}: does not helptaking away the
closedcycle: produces undefined control sequenceaddplot
tikz-pgf pgfplots
tikz-pgf pgfplots
edited Feb 7 at 5:56
Stefan Pinnow
19.8k83276
asked Feb 6 at 11:21
johaschnjohaschn
966
edited Feb 7 at 5:56
Stefan Pinnow
19.8k83276
asked Feb 6 at 11:21
johaschnjohaschn
966
edited Feb 7 at 5:56
Stefan Pinnow
19.8k83276
edited Feb 7 at 5:56
Stefan Pinnow
19.8k83276
edited Feb 7 at 5:56
Stefan Pinnow
19.8k83276
19.8k83276
asked Feb 6 at 11:21
johaschnjohaschn
966
asked Feb 6 at 11:21
johaschnjohaschn
966
asked Feb 6 at 11:21
johaschnjohaschn
966
966
1
Make a bug report, pgf/tikz changed and now something is undefined ...
– Ulrike Fischer
Feb 6 at 11:49
bug report created: sourceforge.net/p/pgf/bugs/512
– johaschn
Feb 6 at 13:42
add a comment |
1
Make a bug report, pgf/tikz changed and now something is undefined ...
– Ulrike Fischer
Feb 6 at 11:49
bug report created: sourceforge.net/p/pgf/bugs/512
– johaschn
Feb 6 at 13:42
1
1
Make a bug report, pgf/tikz changed and now something is undefined ...
– Ulrike Fischer
Feb 6 at 11:49
Make a bug report, pgf/tikz changed and now something is undefined ...
– Ulrike Fischer
Feb 6 at 11:49
bug report created: sourceforge.net/p/pgf/bugs/512
– johaschn
Feb 6 at 13:42
bug report created: sourceforge.net/p/pgf/bugs/512
– johaschn
Feb 6 at 13:42
add a comment |
1 Answer
1
active
oldest
votes
This might be a bug in pgfplots rather than PGF, which only surfaced now due to changes in PGF, because if I simply define the undefined control sequence, it works as expected.
documentclass{article}
usepackage{tikz,pgfplots}
makeatletter
defpgfplots@stacked@diff{}
makeatother
begin{document}
begin{tikzpicture}
begin{axis}[unbounded coords=jump, stack plots=y]
addplot[fill=gray, draw=black] table{123.tsv}
closedcycle;
addplot[fill=none, draw=black] table{123.tsv}
closedcycle;
end{axis}
end{tikzpicture}
end{document}
answered Feb 6 at 23:09
Henri MenkeHenri Menke
73.9k8162274
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f473608%2finteraction-between-nan-data-unbounded-coords-and-stack-plots%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This might be a bug in pgfplots rather than PGF, which only surfaced now due to changes in PGF, because if I simply define the undefined control sequence, it works as expected.
documentclass{article}
usepackage{tikz,pgfplots}
makeatletter
defpgfplots@stacked@diff{}
makeatother
begin{document}
begin{tikzpicture}
begin{axis}[unbounded coords=jump, stack plots=y]
addplot[fill=gray, draw=black] table{123.tsv}
closedcycle;
addplot[fill=none, draw=black] table{123.tsv}
closedcycle;
end{axis}
end{tikzpicture}
end{document}
answered Feb 6 at 23:09
Henri MenkeHenri Menke
73.9k8162274
add a comment |
This might be a bug in pgfplots rather than PGF, which only surfaced now due to changes in PGF, because if I simply define the undefined control sequence, it works as expected.
documentclass{article}
usepackage{tikz,pgfplots}
makeatletter
defpgfplots@stacked@diff{}
makeatother
begin{document}
begin{tikzpicture}
begin{axis}[unbounded coords=jump, stack plots=y]
addplot[fill=gray, draw=black] table{123.tsv}
closedcycle;
addplot[fill=none, draw=black] table{123.tsv}
closedcycle;
end{axis}
end{tikzpicture}
end{document}
answered Feb 6 at 23:09
Henri MenkeHenri Menke
73.9k8162274
add a comment |
This might be a bug in pgfplots rather than PGF, which only surfaced now due to changes in PGF, because if I simply define the undefined control sequence, it works as expected.
documentclass{article}
usepackage{tikz,pgfplots}
makeatletter
defpgfplots@stacked@diff{}
makeatother
begin{document}
begin{tikzpicture}
begin{axis}[unbounded coords=jump, stack plots=y]
addplot[fill=gray, draw=black] table{123.tsv}
closedcycle;
addplot[fill=none, draw=black] table{123.tsv}
closedcycle;
end{axis}
end{tikzpicture}
end{document}
answered Feb 6 at 23:09
Henri MenkeHenri Menke
73.9k8162274
This might be a bug in pgfplots rather than PGF, which only surfaced now due to changes in PGF, because if I simply define the undefined control sequence, it works as expected.
documentclass{article}
usepackage{tikz,pgfplots}
makeatletter
defpgfplots@stacked@diff{}
makeatother
begin{document}
begin{tikzpicture}
begin{axis}[unbounded coords=jump, stack plots=y]
addplot[fill=gray, draw=black] table{123.tsv}
closedcycle;
addplot[fill=none, draw=black] table{123.tsv}
closedcycle;
end{axis}
end{tikzpicture}
end{document}
answered Feb 6 at 23:09
Henri MenkeHenri Menke
73.9k8162274
answered Feb 6 at 23:09
Henri MenkeHenri Menke
73.9k8162274
answered Feb 6 at 23:09
Henri MenkeHenri Menke
73.9k8162274
answered Feb 6 at 23:09
Henri MenkeHenri Menke
73.9k8162274
73.9k8162274
add a comment |
add a comment |
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f473608%2finteraction-between-nan-data-unbounded-coords-and-stack-plots%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Make a bug report, pgf/tikz changed and now something is undefined ...
– Ulrike Fischer
Feb 6 at 11:49
bug report created: sourceforge.net/p/pgf/bugs/512
– johaschn
Feb 6 at 13:42