pgfplots-features Mailing List for pgfplots (Page 6)
Brought to you by:
cfeuersaenger,
ludewich
This list is closed, nobody may subscribe to it.
2009 |
Jan
|
Feb
|
Mar
(20) |
Apr
(5) |
May
(7) |
Jun
(15) |
Jul
(15) |
Aug
(17) |
Sep
(22) |
Oct
(3) |
Nov
(8) |
Dec
(6) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2010 |
Jan
(22) |
Feb
(19) |
Mar
(14) |
Apr
(24) |
May
(18) |
Jun
(23) |
Jul
(18) |
Aug
(10) |
Sep
(33) |
Oct
(11) |
Nov
(12) |
Dec
|
2011 |
Jan
(16) |
Feb
(9) |
Mar
(10) |
Apr
(17) |
May
(2) |
Jun
(11) |
Jul
(29) |
Aug
(12) |
Sep
(20) |
Oct
(9) |
Nov
(8) |
Dec
(17) |
2012 |
Jan
(17) |
Feb
(6) |
Mar
(9) |
Apr
(8) |
May
(1) |
Jun
(3) |
Jul
(4) |
Aug
(15) |
Sep
(7) |
Oct
(9) |
Nov
(25) |
Dec
(2) |
2013 |
Jan
(7) |
Feb
|
Mar
(4) |
Apr
(1) |
May
(3) |
Jun
(15) |
Jul
(2) |
Aug
(2) |
Sep
(1) |
Oct
(4) |
Nov
|
Dec
(2) |
2014 |
Jan
(4) |
Feb
(1) |
Mar
(17) |
Apr
(6) |
May
|
Jun
(2) |
Jul
(6) |
Aug
(3) |
Sep
(3) |
Oct
(4) |
Nov
(4) |
Dec
(4) |
2015 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
(2) |
Sep
(4) |
Oct
(1) |
Nov
|
Dec
|
2016 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
(3) |
Nov
|
Dec
(1) |
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(9) |
Nov
(1) |
Dec
|
2019 |
Jan
(4) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Christian F. <cfe...@go...> - 2013-01-19 11:17:55
|
Hi Denis, I have applied your patch proposal. Thanks! Best regards Christian Am 16.01.2013 15:17, schrieb Denis Bitouzé: > Hi, > > AFAIK, usual warning messages provided by packages start by: > > Package<package name> Warning: > > Those provided by pgfplots start with an extra exclamation mark > (followed by a space): > > ! Package pgfplots Warning: > > Some TeX editors, for instance TeXstudio, parse the log file looking > for, I guess: > > <beginning of the line>Package<something> Warning: > > in order to filter warnings. > > Hence, instead of (cf. line 33 of pgfplotscore.code.tex): > > \def\pgfplots@warning#1{\pgfplots@message{! Package pgfplots Warning: > #1}}% > > what about a regular: > > \def\pgfplots@warning#1{\PackageWarning{pgfplots}{#1}{}}% > > as that's already the case for pgfplots errors: > > \def\pgfplots@error#1{\PackageError{pgfplots}{#1}{}}% > > Best regards. |
From: Christian F. <cfe...@go...> - 2013-01-19 11:11:35
|
Hi Neal, The inverse coord transformations accept log values for logarithmic axes, that is correct. In order to convert the number back to the correct number, you should use x coord inv trafo/.code={% \pgfplotscoordmath{x}{exp}{#1}% \show\pgfmathresult \expandafter\secondspp\expandafter{\pgfmathresult}} the "coordmath" stuff ensures a suitable precision and respects the correct log basis. It assigns the result to \pgfmathresult. Your \secondspp seems to overwrite \pgfmathresult, that's why I used the two \expandafter constructs to pass by value instead of by reference. PGFplots assumes that user-provided transformations fit into the axis, i.e. that the transformation "knows" that it is to be applied in a log context. Consequently, you'd need two transformations, one tailored for linear axes and one tailored for log axes. This could be done by means of styles. I hope this helps so far. Best regards Christian Am 16.01.2013 14:10, schrieb Neal H. Walfield: > Hi, > > I'm using x coord inv trafo/.code to transform seconds into more > (human) meaningful labels. For instance, my macro turns 7000 seconds > into '2h'. This works correctly for normal axes, however, if I use a > logarithmic axes, my macro is passed the exponent rather than the > value. How do I programmatically determine what I am being passed? > > A minimal example follows. > > Thanks for your help, > > Neal > > > \documentclass{article} > > \usepackage{tikz} > \usepackage{pgfplots} > > % number > % threshold > % divisor > % suffix > % else > \def\secondspphelper#1#2#3#4#5{% > \pgfmathfloatparsenumber{#1}% > \edef\num{\pgfmathresult}% > \pgfmathfloatparsenumber{#2}% > \edef\threshold{\pgfmathresult}% > \pgfmathfloatparsenumber{#3}% > \edef\divisor{\pgfmathresult}% > % > \pgfmathfloatlessthan{\num}{\threshold}% > \ifdim\pgfmathresult pt = 1 pt% > \pgfmathfloatdivide{\num}{\divisor}% > \pgfmathfloattofixed{\pgfmathresult}% > \pgfmathprintnumberto[/pgf/number format/precision=0]{\pgfmathresult}{\pgfmathresult}% > \edef\pgfmathresult{\pgfmathresult#4}% > \else% > #5% > \fi% > }% > > % Pretty print a number of seconds. > % Example: > % \secondspp{1000}\pgfmathresult == 17m > \def\secondspp#1{% > % Print as seconds for values up to 90 seconds. > \secondspphelper{#1}{90}{1}{s}{% > % Print as minutes for values up to 1 hour (= 3600 seconds) > \secondspphelper{#1}{3600}{60}{m}{% > % Print as hours for values up to 1 day (= 86400 seconds) > \secondspphelper{#1}{86400}{3600}{h}{% > % Print as days for up to 2 weeks (= 1209600 seconds) > \secondspphelper{#1}{1209600}{86400}{d}{% > % Print as weeks. > \secondspphelper{#1}{Inf}{604800}{w}{}% > }% > }% > }% > }% > } > > \begin{document} > > \def\xmin{1} > \def\xmax{10000} > > \begin{tikzpicture} > \begin{axis}[ > xticklabel={\tick}, > scaled x ticks=false, > plot coordinates/math parser=false, > x coord inv trafo/.code={\def\x{#1}\show\x\secondspp{#1}} > ] > \addplot[domain=\xmin:\xmax] plot expression {x}; > \end{axis} > \end{tikzpicture} > > \begin{tikzpicture} > \begin{loglogaxis}[ > xticklabel={\tick}, > scaled x ticks=false, > plot coordinates/math parser=false, > x coord inv trafo/.code={\def\x{#1}\show\x\secondspp{#1}} > ] > \addplot[domain=\xmin:\xmax] plot expression {x}; > \end{loglogaxis} > \end{tikzpicture} > > \end{document} > > > ------------------------------------------------------------------------------ > Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery > and much more. Keep your Java skills current with LearnJavaNow - > 200+ hours of step-by-step video tutorials by Java experts. > SALE $49.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122612 > _______________________________________________ > Pgfplots-features mailing list > Pgf...@li... > https://lists.sourceforge.net/lists/listinfo/pgfplots-features |
From: Denis B. <dbi...@wa...> - 2013-01-16 14:17:22
|
Hi, AFAIK, usual warning messages provided by packages start by: Package <package name> Warning: Those provided by pgfplots start with an extra exclamation mark (followed by a space): ! Package pgfplots Warning: Some TeX editors, for instance TeXstudio, parse the log file looking for, I guess: <beginning of the line>Package <something> Warning: in order to filter warnings. Hence, instead of (cf. line 33 of pgfplotscore.code.tex): \def\pgfplots@warning#1{\pgfplots@message{! Package pgfplots Warning: #1}}% what about a regular: \def\pgfplots@warning#1{\PackageWarning{pgfplots}{#1}{}}% as that's already the case for pgfplots errors: \def\pgfplots@error#1{\PackageError{pgfplots}{#1}{}}% Best regards. -- Denis |
From: Neal H. W. <ne...@wa...> - 2013-01-16 13:38:23
|
Hi, I'm using x coord inv trafo/.code to transform seconds into more (human) meaningful labels. For instance, my macro turns 7000 seconds into '2h'. This works correctly for normal axes, however, if I use a logarithmic axes, my macro is passed the exponent rather than the value. How do I programmatically determine what I am being passed? A minimal example follows. Thanks for your help, Neal \documentclass{article} \usepackage{tikz} \usepackage{pgfplots} % number % threshold % divisor % suffix % else \def\secondspphelper#1#2#3#4#5{% \pgfmathfloatparsenumber{#1}% \edef\num{\pgfmathresult}% \pgfmathfloatparsenumber{#2}% \edef\threshold{\pgfmathresult}% \pgfmathfloatparsenumber{#3}% \edef\divisor{\pgfmathresult}% % \pgfmathfloatlessthan{\num}{\threshold}% \ifdim\pgfmathresult pt = 1 pt% \pgfmathfloatdivide{\num}{\divisor}% \pgfmathfloattofixed{\pgfmathresult}% \pgfmathprintnumberto[/pgf/number format/precision=0]{\pgfmathresult}{\pgfmathresult}% \edef\pgfmathresult{\pgfmathresult#4}% \else% #5% \fi% }% % Pretty print a number of seconds. % Example: % \secondspp{1000}\pgfmathresult == 17m \def\secondspp#1{% % Print as seconds for values up to 90 seconds. \secondspphelper{#1}{90}{1}{s}{% % Print as minutes for values up to 1 hour (= 3600 seconds) \secondspphelper{#1}{3600}{60}{m}{% % Print as hours for values up to 1 day (= 86400 seconds) \secondspphelper{#1}{86400}{3600}{h}{% % Print as days for up to 2 weeks (= 1209600 seconds) \secondspphelper{#1}{1209600}{86400}{d}{% % Print as weeks. \secondspphelper{#1}{Inf}{604800}{w}{}% }% }% }% }% } \begin{document} \def\xmin{1} \def\xmax{10000} \begin{tikzpicture} \begin{axis}[ xticklabel={\tick}, scaled x ticks=false, plot coordinates/math parser=false, x coord inv trafo/.code={\def\x{#1}\show\x\secondspp{#1}} ] \addplot[domain=\xmin:\xmax] plot expression {x}; \end{axis} \end{tikzpicture} \begin{tikzpicture} \begin{loglogaxis}[ xticklabel={\tick}, scaled x ticks=false, plot coordinates/math parser=false, x coord inv trafo/.code={\def\x{#1}\show\x\secondspp{#1}} ] \addplot[domain=\xmin:\xmax] plot expression {x}; \end{loglogaxis} \end{tikzpicture} \end{document} |
From: Christian F. <cfe...@go...> - 2013-01-13 17:06:29
|
Dear Dr. Zolili Ndlela, this is a bug, probably in the viewers, see http://tex.stackexchange.com/questions/79931/does-the-pgfplots-manual-crash-your-preview-and-or-skim-app-on-osx I am unsure how to proceed here as I the success of acroread and all linux viewers in displaying that stuff indicates that it (the pgfplots.pdf) is correct. And I cannot really experiment since I do not have the viewers at hand (?). The solution for you would be to use acrobat reader to open the manual. I would have an idea how to change some shading drivers such that the pdf becomes simpler. Perhaps I can generate such a version and send it so you, if you are willing to experiment. Best regards Christian 2013/1/11 Ndlela, Zolili <zn...@sa...>: > Dr. Feuersanger : > > I have come across a problem which might "infect" your user documentation, > Manual for Package PGFPLOTS. > > Over the last few days I have tried, unsuccessfully, to compile a Ternary > plot from examples. [Note: i have been able to compile!] > > But when I sought help/explanation from the manual my pdf application > crashed consistently. The pdf file opened without problem, but when I > passed pg. 330 on the Oct. 26, 2012 document and pg 312 on the Nov 2011 the > pdf application hung, then crashed. > > I thought the problem was my pdf application (Preview), but when I tried > another app, (PDF PenPro) I got the same result. I'm using two different > machines, a newer MacBook Pro with Mac OS X Mountain Lion (10.8.2) and a > slightly older MacBook Pro with OS X Snow Leopard (10.6.8). > > I don't know if other users have experienced this problem or whether its > peculiar to my systems. If you have suggestions how I can open and read the > manuals, and compile a Ternary diagram, if would be grateful. > > Thank you, > > Dr. Zolili Ndlela > Department of Physics and Astronomy > CSU, Sacramento > > > p.s. I just tried Adobe Acrobat, and the document did not crash. Still, I am > puzzled. |
From: Christian F. <cfe...@go...> - 2012-12-25 16:50:52
|
Dear Nils Schuhardt, thanks for your request! Since it might be of interest to a larger audience, I cc'ed the pgfplots mailing list. The question was "How can I use a different marker size for the legend, assuming that my plot has a 'mark size=0.01mm' set?" . The answer is to rely on the style 'every legend image post' (or its equivalent short-cut key 'legend image post style'). Here is a suitable minimal example: \documentclass{article} \usepackage{pgfplots} \begin{document} \begin{tikzpicture} \begin{axis} \addplot+[ mark=+, blue, only marks, mark size={0.1mm}, legend image post style={mark size=1mm}, ] {x}; \addlegendentry{$x$} \end{axis} \end{tikzpicture} \end{document} I wish a merry christmas and a happy new year! Kind regards Christian Am 25.12.2012 16:27, schrieb Nils Schuhardt: > Hallo Herr Dr. Feuersänger, > > fröhliche Weihnachten erstmal. > Zu meinem Problem habe ich nichts in der Anleitung und im Internet > gefunden. Über > > \addplot+[mark=+, blue, only marks, mark size={0.01mm}] > table[header=false,x index=0,y index=3] {bilder/2012_12_11.csv}; > > stelle ich jeden Messwert einzeln dar und möchte nun den Marker vor > dem Legendeneintrag größer als 0.01 mm haben. Als Option in der > Axisumgebung und bei \addlegendentry hatte ich mit mark size={1mm} > leider keinen Erfolg. Verraten Sie mir bitte wo und wie ich die Marker > unabhängig voneinander dimensionieren kann. > > Mit freundlichem Gruß > Nils Schuhardt |
From: Christian F. <cfe...@go...> - 2012-12-01 08:29:10
|
Hi Aurélien, good that it works. You can try out how much impact the sampling density has. Best regards Christian Am 30.11.2012 23:56, schrieb aurelien coillet: > Hi Christian, > > Thanks, that works indeed! I should have tried a little bit harder, I > suppose. > > Regarding this huge number of points, it is actually needed: my data > consists in thousands of lines of various amplitude, and I want to be > able to distinguish one of these lines from its neighbour as well as > comprehend the global variation in amplitude. However, you're right > that it may be a pain for the user, and I will consider using an image > instead. Actually, that was my workaround, but I was not satisfied > with this. > > So thanks for your help and comments. > > Best regards, > > Aurélien > > > 2012/11/30 Christian Feuersaenger <cfe...@go... > <mailto:cfe...@go...>> > > Hi Aurélien, > > that is very strange, indeed. I can reproduce the problem with a file > named "Sinus" (without extension): lualatex fails whereas pdflatex > works. > > Seems as if they have different path resolution algorithms. > > However, it worked as soon as I introduced a file suffix: both > lualatex > and pdflatex find "Sinus.dat" . > > My suggestion is to go along that path. > > However, I would like to point out that 78000 points might be > essentially overkill - and I am not talking about the time that > pgfplots > takes (be it lualatex or pdflatex). If you have 78000 points, you blow > up the size of your .pdf file. In addition, displaying it will > take some > time. And: the user might not benefit at all unless you really > have high > frequencies! Are you sure that you need such a sampling density? > Often, > it is completely sufficient to have less samples for a .pdf document. > Note that if you generate some .png graphics containing JUST the plot, > you could use pgfplots to overlay an axis by means of its \addplot > graphics feature. That would have a smaller pdf. > > Best regards > > Christian > > Am 30.11.2012 19:19, schrieb aurelien coillet: > > Hi, > > > > I'd like to plot a large file (78000 points) with pgfplots, and it > > obviously fails with pdflatex. I tried to use lualatex instead, > but it > > does not seem to find my file... > > So I tried a very simple example : > > > > \documentclass{article} > > \usepackage[utf8]{luainputenc} > > \usepackage{pgfplots} > > \pgfplotsset{compat=1.7} > > > > \begin{document} > > > > \begin{tikzpicture} > > \begin{axis} > > \addplot file {Sinus}; > > \end{axis} > > \end{tikzpicture} > > > > \end{document} > > > > with the Sinus file (a small one, 100 points) starting with: > > > > 0.00000000e+00 0.00000000e+00 > > 2.02020202e-02 2.02006461e-02 > > 4.04040404e-02 4.03930481e-02 > > 6.06060606e-02 6.05689655e-02 > > 8.08080808e-02 8.07201641e-02 > > 1.01010101e-01 1.00838420e-01 > > > > and it fails with: > > > > ! Package pgfplots Error: sorry, plot file{Sinus} could not be > opened. > > > > Note that compiling this document with pdflatex works as intended. > > What am I doing wrong? I searched on google, but couldn't find > > anything... > > > > Thanks for your help! Regards, > > > > > > -- > > Aurélien Coillet > > > > > > > ------------------------------------------------------------------------------ > > Keep yourself connected to Go Parallel: > > TUNE You got it built. Now make it sing. Tune shows you how. > > http://goparallel.sourceforge.net > > > > > > _______________________________________________ > > Pgfplots-features mailing list > > Pgf...@li... > <mailto:Pgf...@li...> > > https://lists.sourceforge.net/lists/listinfo/pgfplots-features > > > ------------------------------------------------------------------------------ > Keep yourself connected to Go Parallel: > TUNE You got it built. Now make it sing. Tune shows you how. > http://goparallel.sourceforge.net > _______________________________________________ > Pgfplots-features mailing list > Pgf...@li... > <mailto:Pgf...@li...> > https://lists.sourceforge.net/lists/listinfo/pgfplots-features > > > > > -- > Aurélien Coillet > > > ------------------------------------------------------------------------------ > Keep yourself connected to Go Parallel: > TUNE You got it built. Now make it sing. Tune shows you how. > http://goparallel.sourceforge.net > > > _______________________________________________ > Pgfplots-features mailing list > Pgf...@li... > https://lists.sourceforge.net/lists/listinfo/pgfplots-features |
From: aurelien c. <aco...@gm...> - 2012-11-30 22:56:26
|
Hi Christian, Thanks, that works indeed! I should have tried a little bit harder, I suppose. Regarding this huge number of points, it is actually needed: my data consists in thousands of lines of various amplitude, and I want to be able to distinguish one of these lines from its neighbour as well as comprehend the global variation in amplitude. However, you're right that it may be a pain for the user, and I will consider using an image instead. Actually, that was my workaround, but I was not satisfied with this. So thanks for your help and comments. Best regards, Aurélien 2012/11/30 Christian Feuersaenger <cfe...@go...> > Hi Aurélien, > > that is very strange, indeed. I can reproduce the problem with a file > named "Sinus" (without extension): lualatex fails whereas pdflatex works. > > Seems as if they have different path resolution algorithms. > > However, it worked as soon as I introduced a file suffix: both lualatex > and pdflatex find "Sinus.dat" . > > My suggestion is to go along that path. > > However, I would like to point out that 78000 points might be > essentially overkill - and I am not talking about the time that pgfplots > takes (be it lualatex or pdflatex). If you have 78000 points, you blow > up the size of your .pdf file. In addition, displaying it will take some > time. And: the user might not benefit at all unless you really have high > frequencies! Are you sure that you need such a sampling density? Often, > it is completely sufficient to have less samples for a .pdf document. > Note that if you generate some .png graphics containing JUST the plot, > you could use pgfplots to overlay an axis by means of its \addplot > graphics feature. That would have a smaller pdf. > > Best regards > > Christian > > Am 30.11.2012 19:19, schrieb aurelien coillet: > > Hi, > > > > I'd like to plot a large file (78000 points) with pgfplots, and it > > obviously fails with pdflatex. I tried to use lualatex instead, but it > > does not seem to find my file... > > So I tried a very simple example : > > > > \documentclass{article} > > \usepackage[utf8]{luainputenc} > > \usepackage{pgfplots} > > \pgfplotsset{compat=1.7} > > > > \begin{document} > > > > \begin{tikzpicture} > > \begin{axis} > > \addplot file {Sinus}; > > \end{axis} > > \end{tikzpicture} > > > > \end{document} > > > > with the Sinus file (a small one, 100 points) starting with: > > > > 0.00000000e+00 0.00000000e+00 > > 2.02020202e-02 2.02006461e-02 > > 4.04040404e-02 4.03930481e-02 > > 6.06060606e-02 6.05689655e-02 > > 8.08080808e-02 8.07201641e-02 > > 1.01010101e-01 1.00838420e-01 > > > > and it fails with: > > > > ! Package pgfplots Error: sorry, plot file{Sinus} could not be opened. > > > > Note that compiling this document with pdflatex works as intended. > > What am I doing wrong? I searched on google, but couldn't find > > anything... > > > > Thanks for your help! Regards, > > > > > > -- > > Aurélien Coillet > > > > > > > ------------------------------------------------------------------------------ > > Keep yourself connected to Go Parallel: > > TUNE You got it built. Now make it sing. Tune shows you how. > > http://goparallel.sourceforge.net > > > > > > _______________________________________________ > > Pgfplots-features mailing list > > Pgf...@li... > > https://lists.sourceforge.net/lists/listinfo/pgfplots-features > > > > ------------------------------------------------------------------------------ > Keep yourself connected to Go Parallel: > TUNE You got it built. Now make it sing. Tune shows you how. > http://goparallel.sourceforge.net > _______________________________________________ > Pgfplots-features mailing list > Pgf...@li... > https://lists.sourceforge.net/lists/listinfo/pgfplots-features > -- Aurélien Coillet |
From: Christian F. <cfe...@go...> - 2012-11-30 22:23:07
|
Hi Aurélien, that is very strange, indeed. I can reproduce the problem with a file named "Sinus" (without extension): lualatex fails whereas pdflatex works. Seems as if they have different path resolution algorithms. However, it worked as soon as I introduced a file suffix: both lualatex and pdflatex find "Sinus.dat" . My suggestion is to go along that path. However, I would like to point out that 78000 points might be essentially overkill - and I am not talking about the time that pgfplots takes (be it lualatex or pdflatex). If you have 78000 points, you blow up the size of your .pdf file. In addition, displaying it will take some time. And: the user might not benefit at all unless you really have high frequencies! Are you sure that you need such a sampling density? Often, it is completely sufficient to have less samples for a .pdf document. Note that if you generate some .png graphics containing JUST the plot, you could use pgfplots to overlay an axis by means of its \addplot graphics feature. That would have a smaller pdf. Best regards Christian Am 30.11.2012 19:19, schrieb aurelien coillet: > Hi, > > I'd like to plot a large file (78000 points) with pgfplots, and it > obviously fails with pdflatex. I tried to use lualatex instead, but it > does not seem to find my file... > So I tried a very simple example : > > \documentclass{article} > \usepackage[utf8]{luainputenc} > \usepackage{pgfplots} > \pgfplotsset{compat=1.7} > > \begin{document} > > \begin{tikzpicture} > \begin{axis} > \addplot file {Sinus}; > \end{axis} > \end{tikzpicture} > > \end{document} > > with the Sinus file (a small one, 100 points) starting with: > > 0.00000000e+00 0.00000000e+00 > 2.02020202e-02 2.02006461e-02 > 4.04040404e-02 4.03930481e-02 > 6.06060606e-02 6.05689655e-02 > 8.08080808e-02 8.07201641e-02 > 1.01010101e-01 1.00838420e-01 > > and it fails with: > > ! Package pgfplots Error: sorry, plot file{Sinus} could not be opened. > > Note that compiling this document with pdflatex works as intended. > What am I doing wrong? I searched on google, but couldn't find > anything... > > Thanks for your help! Regards, > > > -- > Aurélien Coillet > > > ------------------------------------------------------------------------------ > Keep yourself connected to Go Parallel: > TUNE You got it built. Now make it sing. Tune shows you how. > http://goparallel.sourceforge.net > > > _______________________________________________ > Pgfplots-features mailing list > Pgf...@li... > https://lists.sourceforge.net/lists/listinfo/pgfplots-features |
From: aurelien c. <aco...@gm...> - 2012-11-30 18:19:41
|
Hi, I'd like to plot a large file (78000 points) with pgfplots, and it obviously fails with pdflatex. I tried to use lualatex instead, but it does not seem to find my file... So I tried a very simple example : \documentclass{article} \usepackage[utf8]{luainputenc} \usepackage{pgfplots} \pgfplotsset{compat=1.7} \begin{document} \begin{tikzpicture} \begin{axis} \addplot file {Sinus}; \end{axis} \end{tikzpicture} \end{document} with the Sinus file (a small one, 100 points) starting with: 0.00000000e+00 0.00000000e+00 2.02020202e-02 2.02006461e-02 4.04040404e-02 4.03930481e-02 6.06060606e-02 6.05689655e-02 8.08080808e-02 8.07201641e-02 1.01010101e-01 1.00838420e-01 and it fails with: ! Package pgfplots Error: sorry, plot file{Sinus} could not be opened. Note that compiling this document with pdflatex works as intended. What am I doing wrong? I searched on google, but couldn't find anything... Thanks for your help! Regards, -- Aurélien Coillet |
From: Christoph B. <chr...@we...> - 2012-11-28 18:45:30
|
Christoph Bier schrieb am 25.11.2012 20:35: > Christoph Bier schrieb am 25.11.2012 14:18: > > [...] > >> 4. How can I automatically adjust vertical spacing? Both plots in >> the MWE have the same height and width. But the second plot needed >> more space.---JFTR: I already asked a similar question here: >> http://tex.stackexchange.com/questions/84073/space-between-bars-height-and-width-of-the-plot > > I got a helpful answer by Jake: > > “By default, plots always take up the same amount of space (240pt by > 207pt). If you want the plots to adjust their height depending on > the number of bars, you can define the length of a unit in the y > direction, by setting y=0.5cm, for instance. If you then define the > bar width to be 0.4cm, there will be no overlap between the bars. > Since PGFPlots version 1.7 (I think), you can also define the extra > space at the top and bottom in absolute lengths (before that, you > could only specify it in data units).” > > Corresponding example can be found here: > http://tex.stackexchange.com/a/84192/10682 And another helpful answer by Christian be found here: http://tex.stackexchange.com/a/84520/10682 -- (La)TeX-FAQ: http://projekte.dante.de/DanteFAQ +++ Minimalbeispiel erstellen und Einführung in dctt: http://www.latex-einfuehrung.de/ +++ Veraltete Befehle, Pakete und andere Fehler: ftp://ftp.dante.de/tex-archive/info/l2tabu/german/l2tabu.pdf +++ Typografie-Regeln (1.7): http://bit.ly/typokurz-cb |
From: Christian F. <cfe...@go...> - 2012-11-28 13:09:18
|
Hi Denis, before you are frustrated, you should take a look at the hint given by Juernjakob - it seems to address exactly the requested use-case. Best regards Christian 2012/11/28 Denis Bitouzé <dbi...@wa...>: > Le mardi 27/11/12 à 21h48, > Christian Feuersaenger <cfe...@go...> a écrit : > >> Hi Denis, > > Hi Christian, > >> thanks for your request. > > You're welcome :) > >> The key question when we talk about plotting is: how large is the >> data range? The dateplot lib maps a complete date to some integer >> number. Unfortunately, the available precision is (appears to be) >> insufficient for seconds. > > Too bad! > >> However, if your data range is one or two days, > > At least in educational area, that's the case. > >> one could think about a different data transformation which "throws >> away" the month and year information and uses the full precision for >> the mapping. > > Yes, could be nice. > >> This, however, would need to be implemented as coordinate >> transformation. > > OK. > >> In other words: the answer to your question is: "Yes, if (a) your >> data range is small enough and (b) if someone implements it." > > Sigh... > > BTW, wouldn't be possible to delegate date time data handling to > gnuplot? AFAICS, it is not so bad for this task: as said p. 19 of > http://www.gnuplot.info/docs_4.6/gnuplot.pdf, "Gnuplot now > tracks time to millisecond precision" ;) > > Best regards. > -- > Denis > > ------------------------------------------------------------------------------ > Keep yourself connected to Go Parallel: > INSIGHTS What's next for parallel hardware, programming and related areas? > Interviews and blogs by thought leaders keep you ahead of the curve. > http://goparallel.sourceforge.net > _______________________________________________ > Pgfplots-features mailing list > Pgf...@li... > https://lists.sourceforge.net/lists/listinfo/pgfplots-features |
From: Denis B. <dbi...@wa...> - 2012-11-28 08:25:14
|
Le mardi 27/11/12 à 21h48, Christian Feuersaenger <cfe...@go...> a écrit : > Hi Denis, Hi Christian, > thanks for your request. You're welcome :) > The key question when we talk about plotting is: how large is the > data range? The dateplot lib maps a complete date to some integer > number. Unfortunately, the available precision is (appears to be) > insufficient for seconds. Too bad! > However, if your data range is one or two days, At least in educational area, that's the case. > one could think about a different data transformation which "throws > away" the month and year information and uses the full precision for > the mapping. Yes, could be nice. > This, however, would need to be implemented as coordinate > transformation. OK. > In other words: the answer to your question is: "Yes, if (a) your > data range is small enough and (b) if someone implements it." Sigh... BTW, wouldn't be possible to delegate date time data handling to gnuplot? AFAICS, it is not so bad for this task: as said p. 19 of http://www.gnuplot.info/docs_4.6/gnuplot.pdf, "Gnuplot now tracks time to millisecond precision" ;) Best regards. -- Denis |
From: Christian F. <cfe...@go...> - 2012-11-27 20:48:47
|
Hi Denis, thanks for your request. The key question when we talk about plotting is: how large is the data range? The dateplot lib maps a complete date to some integer number. Unfortunately, the available precision is (appears to be) insufficient for seconds. However, if your data range is one or two days, one could think about a different data transformation which "throws away" the month and year information and uses the full precision for the mapping. This, however, would need to be implemented as coordinate transformation. In other words: the answer to your question is: "Yes, if (a) your data range is small enough and (b) if someone implements it." Best regards Christian Am 26.11.2012 15:46, schrieb Denis Bitouzé: > Hello, > > in technological experiences, it is frequent to collect data every > second (or every 2 seconds, etc.) and that the data acquisition > softwares record the dates as absolute ones of the form: > > 2012-11-26 15:40:31 > 2012-11-26 15:40:32 > 2012-11-26 15:40:33 > etc. > > If I'm right, this format is currently unavailable (section "4.20.2 > Dates as Input Coordinates"). Would it be possible to make pgfplots > deals with dates as input coordinates with seconds? > > Thanks in anticipation. > > Best regards. |
From: Denis B. <dbi...@wa...> - 2012-11-26 14:47:12
|
Hello, in technological experiences, it is frequent to collect data every second (or every 2 seconds, etc.) and that the data acquisition softwares record the dates as absolute ones of the form: 2012-11-26 15:40:31 2012-11-26 15:40:32 2012-11-26 15:40:33 etc. If I'm right, this format is currently unavailable (section "4.20.2 Dates as Input Coordinates"). Would it be possible to make pgfplots deals with dates as input coordinates with seconds? Thanks in anticipation. Best regards. -- Denis |
From: Christian F. <cfe...@go...> - 2012-11-25 21:04:27
|
Hi Christoph, thanks for the note that you received a good answer at tex.sx ! Quite good, tex.sx has a higher visibility than this list. Best regards Christian Am 25.11.2012 20:35, schrieb Christoph Bier: > Christoph Bier schrieb am 25.11.2012 14:18: > > [...] > >> 4. How can I automatically adjust vertical spacing? Both plots in >> the MWE have the same height and width. But the second plot needed >> more space.---JFTR: I already asked a similar question here: >> http://tex.stackexchange.com/questions/84073/space-between-bars-height-and-width-of-the-plot > I got a helpful answer by Jake: > > “By default, plots always take up the same amount of space (240pt by > 207pt). If you want the plots to adjust their height depending on > the number of bars, you can define the length of a unit in the y > direction, by setting y=0.5cm, for instance. If you then define the > bar width to be 0.4cm, there will be no overlap between the bars. > Since PGFPlots version 1.7 (I think), you can also define the extra > space at the top and bottom in absolute lengths (before that, you > could only specify it in data units).” > > Corresponding example can be found here: > http://tex.stackexchange.com/a/84192/10682 > > [...] > > Best regards > Christoph |
From: Christoph B. <chr...@we...> - 2012-11-25 19:36:03
|
Christoph Bier schrieb am 25.11.2012 14:18: [...] > 4. How can I automatically adjust vertical spacing? Both plots in > the MWE have the same height and width. But the second plot needed > more space.---JFTR: I already asked a similar question here: > http://tex.stackexchange.com/questions/84073/space-between-bars-height-and-width-of-the-plot I got a helpful answer by Jake: “By default, plots always take up the same amount of space (240pt by 207pt). If you want the plots to adjust their height depending on the number of bars, you can define the length of a unit in the y direction, by setting y=0.5cm, for instance. If you then define the bar width to be 0.4cm, there will be no overlap between the bars. Since PGFPlots version 1.7 (I think), you can also define the extra space at the top and bottom in absolute lengths (before that, you could only specify it in data units).” Corresponding example can be found here: http://tex.stackexchange.com/a/84192/10682 [...] Best regards Christoph -- (La)TeX-FAQ: http://projekte.dante.de/DanteFAQ +++ Minimalbeispiel erstellen und Einführung in dctt: http://www.latex-einfuehrung.de/ +++ Veraltete Befehle, Pakete und andere Fehler: ftp://ftp.dante.de/tex-archive/info/l2tabu/german/l2tabu.pdf +++ Typografie-Regeln (1.7): http://bit.ly/typokurz-cb |
From: Christoph B. <chr...@we...> - 2012-11-25 13:46:30
|
Christoph Bier schrieb am 25.11.2012 14:18: [...] > 2. Can “symbolic y coords” automatically be filled with the content > of a table row? Forgot to mention: I already asked this question on de.comp.text.tex: <news:aha...@mi...> [...] Best Christoph -- (La)TeX-FAQ: http://projekte.dante.de/DanteFAQ +++ Minimalbeispiel erstellen und Einführung in dctt: http://www.latex-einfuehrung.de/ +++ Veraltete Befehle, Pakete und andere Fehler: ftp://ftp.dante.de/tex-archive/info/l2tabu/german/l2tabu.pdf +++ Typografie-Regeln (1.7): http://bit.ly/typokurz-cb |
From: Christoph B. <chr...@we...> - 2012-11-25 13:30:10
|
Hi, I have some questions on the layout of bar plots (xbar) I couldn't find a solution so far. Below follows a minimal working example (MWE). I have many data to plot which is why I'm looking for automated solutions. 1. How can I use comma in “symbolic y coords”? (second plot MWE: “Waschen, Reinigen” instead of “Waschen/Reinigen”) 2. Can “symbolic y coords” automatically be filled with the content of a table row? 3. I do not understand how “text width” in “yticklabel style” works. Increasing it shifts the whole plot to the right but it does not seem to increase the text width for the labels; at least there's a lot of white space on the left of the plot while there's enough text to fill the white space. 4. How can I automatically adjust vertical spacing? Both plots in the MWE have the same height and width. But the second plot needed more space.---JFTR: I already asked a similar question here: http://tex.stackexchange.com/questions/84073/space-between-bars-height-and-width-of-the-plot %Minimal working example: ---> \documentclass{article} \usepackage{% pgfplots% ,filecontents% ,fontspec% } \usepackage[ngerman]{babel} \begin{document} \begin{filecontents}{drei-balken.dat} 6, zu groß 59, genau passend 3, zu klein \end{filecontents} \begin{tikzpicture} \begin{axis}[% xbar, % symbolic y coords={zu groß,genau passend,zu klein},% ytick=data,% nodes near coords,% nodes near coords align={horizontal},% ] \addplot table[col sep=comma,header=false] {drei-balken.dat}; \end{axis} \end{tikzpicture} \begin{filecontents}{vierzehn-balken.dat} 57, Waschen/Reinigen 50, Obst abholen 47, Verteilen 44, Zerkleinern 43, Abfall entsorgen 38, Schälen 38, Arbeitsgeräte säubern 5, Sonstiges 2, Tisch decken 1, Waschen u. Zurückbringen d. Container 1, Mit zunehmendem Alter übernehmen die Kinder immer mehr Arbeitsschritte 1, Keine 1, Geschirr + Besteck holen 1, Dekoratives Anrichten \end{filecontents} \begin{tikzpicture} \begin{axis}[% xbar, % symbolic y coords={% Waschen/Reinigen,% Obst abholen,% Verteilen,% Zerkleinern,% Abfall entsorgen,% Schälen,% Arbeitsgeräte säubern,% Sonstiges,% Tisch decken,% Waschen u. Zurückbringen d. Container,% Mit zunehmendem Alter übernehmen die Kinder immer mehr Arbeitsschritte,% Keine,% Geschirr + Besteck holen,% Dekoratives Anrichten,% },% ytick=data,% yticklabel style={text width=7cm,align=right},% nodes near coords,% nodes near coords align={horizontal},% % y post scale=2.2 % schlechter Workaround, um die % Balken auseinanderzuziehen % bzw. auszurichten ] \addplot table[col sep=comma,header=false] {vierzehn-balken.dat}; \end{axis} \end{tikzpicture} \noindent x \hfill{} x \end{document} %<--- I use TL 2012 with lualatex. Best Regards Christoph -- (La)TeX-FAQ: http://projekte.dante.de/DanteFAQ +++ Minimalbeispiel erstellen und Einführung in dctt: http://www.latex-einfuehrung.de/ +++ Veraltete Befehle, Pakete und andere Fehler: ftp://ftp.dante.de/tex-archive/info/l2tabu/german/l2tabu.pdf +++ Typografie-Regeln (1.7): http://bit.ly/typokurz-cb |
From: Christian F. <cfe...@go...> - 2012-11-22 19:46:56
|
Hi Timo, thanks for your request about colorbars with log scale. This is an old(er) feature request for pgfplots: it does not handle log colorbars automatically. It is still possible, but it requires lots of manual tweaks and hints. More specifically, you have to 1. define the color data by taking the log of your data (point meta key). This is similar to your link. 2. in order to get log scale for the colorbar as such, you need to undo the log trafo of step (1.); otherwise pgfplots will take the log a second time. Here, "undo" means to define 'point meta min' and 'point meta max' for the colorbar manually. The open feature request is to let Pgfplots handle such a case automatically. You may want to wait until it has been addressed eventually. If you still want something which works right now, you have to proceed along the (admittadly tedious) step 1 and 2. Here is your example (I also attached the .tex file and the resulting .pdf): \documentclass{article} \usepackage{pgfplots} % for patch type=bilinear \usepgfplotslibrary{patchplots} \begin{document} \begin{tikzpicture} \begin{semilogyaxis}[ view={0}{90}, colorbar, colorbar style={ % unfortunately, pgfplots has no good support for log % colorbars. % You have to take logs manually from the color data (point % meta) - and then, you have to tell the colorbar the % original, non-log value. % % In your case, I had to retrieve it from the data file. ymode=log, point meta min=1, point meta max=62, }, ] \addplot3[surf,mesh/rows = 7, % this here tells pgfplots that the point meta is provided by the % table: point meta=explicit, % % ... this is just for fun... shader=interp, patch type=bilinear, ] table[ x=Kr, y=Kt, % this applies logs to the z column: meta expr=ln(\thisrow{ratio}), ] {simBiomass_out2.dat}; \end{semilogyaxis} \end{tikzpicture} \end{document} There are two key steps: the first is to apply the log to the color data. This is done by means of the combination "point meta=explicit" and "meta expr=ln(\thisrow{ratio})". This is sufficient in order to get a log scale for your color data - and the colorbar reflects this automatically (but its tick labels show the log values). The second step is to customize the colorbar axis such that it has log mode. This is done by means of the "colorbar style". Best regards Christian PS Note that I posted a copy of this mail to the pgfplots mailing list in order to help others with similar issues. Am 22.11.2012 10:23, schrieb Timo Maarleveld: > Hi Christian, > > I do have one more question regarding colorbars. > > I like to use a logarithmic scale for the colorbar. I looked on-line > for examples > (http://tex.stackexchange.com/questions/23750/log-color-bar-meta-data-in-pgfplot), > but I am not able to get it working. > > Can you have a look? > > Thanks, > > -- > Timo Maarleveld |
From: Christian F. <cfe...@go...> - 2012-11-22 08:08:08
|
Hi there, it might be that I misread the specification of \require - but perhaps you should ensure that the documentation of those LUA primitives is made precise and stresses that no file ending is allowed. I will update pgfplots accordingly. Unless I am mistaken, my Tests did not reveal any problems with lualatex. Best regards Christian Am 22.11.2012 00:34, schrieb Aditya Mahajan: > On Wed, 21 Nov 2012, Thomas Weißschuh wrote: > >> Hi, >> >> when using (latest) pgfplots with ConTeXt standalone the following error >> occurs in tex/generic/pgfplots/util/pgfplotsutil.code.tex:1979 : >> >> ! LuaTeX error <\directlua >:1: module 'pgfplots.lua' not found: >> >> This is the same exact message and error location as the bug reported >> by Aditya last month, but this time it's a different issue. >> It seems like the workaround for the previous bug shadowed this one. >> >> For the record: My version of pgfplot has the fix for the previous bug >> already included. >> >> Problem background: >> The lua function require() appends the .lua file extension to the module >> name. So require('pgfplots.lua') looks for the file pgfplots.lua.lua, >> which then fails. > > Strictly speaking, require("...") searches for both filename.lua and > filename.so. > > require("pgfplots.lua") searchs for the file "pgfplots/lua.lua" and > "pgfplots/lua.so" > >> There was a discussion [0] on the ConTeXt list in which Aditya >> mentions [1], >> that dofile('pgfplots.lua') may be the right function in this >> situtation. > > I looked into it more, and I think that the original patch my Thomas, > changing require"pgfplots.lua") to require("pgfplots"), is the only > method that will work with both LaTeX and ConTeXt. > > I suggested dofile(...) because the standard approach in ConTeXt is to > load lua files using > > dofile(resolvers.findfile("pgfplots.lua")) > > However resolvers.findfiles is not a luatex function; rather it is a > function defined by ConTeXt data-res.lua and replaces kpse.find_all. > resolvers.findfiles caches the result and offers some logging abilities. > > Since ConTeXt provides its own library for searching and loading > files, it disables the kpse library (it is debatable whether disabling > core luatex features is good idea or not, but that is OT here). So, > the natural option: > > dofile(kpse.find_all("pgfplots.lua")) > > will work in LaTeX but fail in ConTeXt. > > On the other hand, require("pgfplots") will work both in LaTeX and > ConTeXt. > > Aditya > > PS: I haven't tested the LaTeX part yet, because my distro's TL > package does not have pgfplots.lua as part of the pgfplots package. > > > ------------------------------------------------------------------------------ > Monitor your physical, virtual and cloud infrastructure from a single > web console. Get in-depth insight into apps, servers, databases, vmware, > SAP, cloud infrastructure, etc. Download 30-day Free Trial. > Pricing starts from $795 for 25 servers or applications! > http://p.sf.net/sfu/zoho_dev2dev_nov > > > _______________________________________________ > Pgfplots-features mailing list > Pgf...@li... > https://lists.sourceforge.net/lists/listinfo/pgfplots-features |
From: Aditya M. <ad...@um...> - 2012-11-21 23:34:56
|
On Wed, 21 Nov 2012, Thomas Weißschuh wrote: > Hi, > > when using (latest) pgfplots with ConTeXt standalone the following error > occurs in tex/generic/pgfplots/util/pgfplotsutil.code.tex:1979 : > > ! LuaTeX error <\directlua >:1: module 'pgfplots.lua' not found: > > This is the same exact message and error location as the bug reported > by Aditya last month, but this time it's a different issue. > It seems like the workaround for the previous bug shadowed this one. > > For the record: My version of pgfplot has the fix for the previous bug > already included. > > Problem background: > The lua function require() appends the .lua file extension to the module > name. So require('pgfplots.lua') looks for the file pgfplots.lua.lua, > which then fails. Strictly speaking, require("...") searches for both filename.lua and filename.so. require("pgfplots.lua") searchs for the file "pgfplots/lua.lua" and "pgfplots/lua.so" > There was a discussion [0] on the ConTeXt list in which Aditya mentions [1], > that dofile('pgfplots.lua') may be the right function in this situtation. I looked into it more, and I think that the original patch my Thomas, changing require"pgfplots.lua") to require("pgfplots"), is the only method that will work with both LaTeX and ConTeXt. I suggested dofile(...) because the standard approach in ConTeXt is to load lua files using dofile(resolvers.findfile("pgfplots.lua")) However resolvers.findfiles is not a luatex function; rather it is a function defined by ConTeXt data-res.lua and replaces kpse.find_all. resolvers.findfiles caches the result and offers some logging abilities. Since ConTeXt provides its own library for searching and loading files, it disables the kpse library (it is debatable whether disabling core luatex features is good idea or not, but that is OT here). So, the natural option: dofile(kpse.find_all("pgfplots.lua")) will work in LaTeX but fail in ConTeXt. On the other hand, require("pgfplots") will work both in LaTeX and ConTeXt. Aditya PS: I haven't tested the LaTeX part yet, because my distro's TL package does not have pgfplots.lua as part of the pgfplots package. |
From: Thomas W. <tho...@la...> - 2012-11-21 22:16:49
|
Hi, when using (latest) pgfplots with ConTeXt standalone the following error occurs in tex/generic/pgfplots/util/pgfplotsutil.code.tex:1979 : ! LuaTeX error <\directlua >:1: module 'pgfplots.lua' not found: This is the same exact message and error location as the bug reported by Aditya last month, but this time it's a different issue. It seems like the workaround for the previous bug shadowed this one. For the record: My version of pgfplot has the fix for the previous bug already included. Problem background: The lua function require() appends the .lua file extension to the module name. So require('pgfplots.lua') looks for the file pgfplots.lua.lua, which then fails. There was a discussion [0] on the ConTeXt list in which Aditya mentions [1], that dofile('pgfplots.lua') may be the right function in this situtation. Thanks for pgfplots and regards, Thomas [0] http://www.mail-archive.com/ntg...@nt.../msg66630.html [1] http://www.mail-archive.com/ntg...@nt.../msg66688.html |
From: Christian F. <cfe...@go...> - 2012-11-15 13:09:16
|
I Timo, so you want a common (!?) colorbar for all sixteen axes which is horizontally centered below the last row? my idea would be to adjust the width of the color bar (using 'colorbar style={width=10cm}' or even \linewidth or so) combined with the 'colorbar to name' feature (compare section Color Bars Outside Of an Axis in the manual). I took the freedom to post a copy of this reply to the pgfplots mailing list; perhaps it is of use for others as well. Best regards Christian Am 15.11.2012 14:02, schrieb Timo Maarleveld: > Hi Christian, > > I attached an example. > > I want something like this (numbers are figures): > > 1 2 3 4 > 5 6 7 8 > 9 10 11 12 > 11 12 13 16 > COLORBAR > > Thanks, > > Timo > > > > > On 15 November 2012 13:55, Christian Feuersaenger > <cfe...@go... <mailto:cfe...@go...>> > wrote: > > Hi Timo, > > I fear I did not quite understand what you are trying to achieve. > > A colorbar is something which is inherently associated with an > axis, not with a plot. > > What do you mean by "plot", by the way? One axis + 16 \addplot > commands? Or 16 axes, each with a single(?) \addplot? > > Could you provide a minimal example? > > Best regards > > Christian > > Am 15.11.2012 12:42, schrieb Timo Maarleveld: > > Hi Christian, > > I am using your pgfplots software, but I encountered a problem. > > I made 16 plots and I like to have 1 colorbar that strengthes > along all columns (horizontal) > or along all rows (vertical). I know how to create 1 colorbar > for each individual plot, but > that\'s not what I want. > > Thanks in advance. > > Timo > > > > -- > This message was sent to your SourceForge.net email alias via > the web mail form. You may reply to this message directly, or > via https://sourceforge.net/sendmessage.php?touser=3053199 > To update your email alias preferences, please visit > https://sourceforge.net/account > > > > > > -- > Timo Maarleveld |
From: Denis B. <dbi...@wa...> - 2012-11-14 21:16:54
|
Le mercredi 14/11/12 à 10h48, Christian Feuersaenger <cfe...@go...> a écrit : > > 2. the first addplot would be the left one and the second, the > > right one, > > I am unsure of whether that is a good idea. It would disallow > multiple plots for the left axis ... and even though it might help > half the students, it might confuse the other half. The association > of \addplot to axis must be made clear somehow; perhaps explicit. Of course you're right! Thanks. Best regards. -- Denis |