I commented out the source statement but am still getting an error on this. Here is the output and test.log is attached.<br><br>C:\tmp2\tikzDevice\inst\tests>findstr source testRTikZDevice.R<br># source('testXeLaTeX.R')<br>
<br>C:\tmp2\tikzDevice\inst\tests>Rscript testRTikZDevice.R --output=output > test.l<br>og<br>Loading required package: filehash<br>Loading required package: methods<br>filehash: Simple key-value database (2.0-1 2008-12-19)<br>
tikzDevice: A Device for R Graphics Output in PGF/TikZ Format (v0.4.8)<br>Checking for a LaTeX compiler...<br><br><br>A working LaTeX compiler was found in:<br> The PATH using the command latex<br><br>Global option tikzLatex set to:<br>
C:\PROGRA~1\MIKTEX~1.7\miktex\bin\latex.exe<br><br>MiKTeX-pdfTeX 2.7.2808 (1.40.4) (MiKTeX 2.7)<br>Copyright (C) 1982 D. E. Knuth, (C) 1996-2006 Han The Thanh<br>TeX is a trademark of the American Mathematical Society.<br>
<br><br>Error in getMetricsFromLatex(TeXMetrics) :<br> ******** There was a problem calculating string metrics,<br> ******** likely there was a problem with your custom packages.<br> ******** See the LaTeX log file above for details.<br>
Calls: system.time ... localTitle -> title -> <Anonymous> -> getMetricsFromLatex<br><br>Execution halted<br><br><br><div class="gmail_quote">On Fri, Dec 4, 2009 at 2:50 PM, Cameron Bracken <span dir="ltr"><<a href="mailto:cameron.bracken@gmail.com">cameron.bracken@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">That problem is from the XeLaTeX test, which has been segfaulting for<br>
a while, I don't know why. Apologies for the lack of instructions.<br>
The rest of the tests should work if you comment out the line<br>
<br>
source('testXeLaTeX.R')<br>
<br>
near the top of testRTikZDevice.R. Then you can either run the script<br>
run-tests.sh (which builds and installs the package) or do what you<br>
did before (it is better to redirect the output to another directory)<br>
<br>
mkdir output<br>
Rscript testRTikZDevice.R --output-prefix=output<br>
<br>
If you want to investigate the speedup from global string width<br>
caching put a line like<br>
<br>
options(tikzMetricsDictionary = "/Users/cameron/.tikzMetricsDictionary")<br>
<br>
In your .Rprofile file. The first run will be slow then subsequent<br>
runs will be much faster. For example on my system without using<br>
global string width caching:<br>
<br>
Running Test 01 ... Done, took 4.455 seconds.<br>
Compiling Test 01 ... Done, took 0.423 seconds.<br>
Running Test 02 ... Done, took 1.145 seconds.<br>
Compiling Test 02 ... Done, took 0.419 seconds.<br>
Running Test 03 ... Done, took 6.042 seconds.<br>
Compiling Test 03 ... Done, took 0.542 seconds.<br>
Running Test 04 ... Done, took 6.719 seconds.<br>
Compiling Test 04 ... Done, took 0.586 seconds.<br>
Running Test 05 ... Done, took 11.283 seconds.<br>
Compiling Test 05 ... Done, took 0.676 seconds.<br>
Running Test 06 ... Done, took 0.391 seconds.<br>
Compiling Test 06 ... Done, took 0.449 seconds.<br>
Running Test 07 ... Done, took 0.365 seconds.<br>
Compiling Test 07 ... Done, took 0.423 seconds.<br>
Running Test 08 ... Done, took 0.355 seconds.<br>
Compiling Test 08 ... Done, took 0.405 seconds.<br>
Running Test 09 ... Done, took 0.394 seconds.<br>
Compiling Test 09 ... Done, took 0.399 seconds.<br>
Running Test 10 ... Done, took 0.364 seconds.<br>
Compiling Test 10 ... Done, took 0.411 seconds.<br>
Running Test 11 ... Done, took 0.364 seconds.<br>
Compiling Test 11 ... Done, took 0.422 seconds.<br>
Running Test 12 ... Done, took 0.376 seconds.<br>
Compiling Test 12 ... Done, took 0.401 seconds.<br>
Running Test 13 ... Done, took 0.376 seconds.<br>
Compiling Test 13 ... Done, took 0.568 seconds.<br>
Running Test 14 ... Done, took 0.381 seconds.<br>
Compiling Test 14 ... Done, took 1.995 seconds.<br>
Running Test 15 ... Done, took 23.414 seconds.<br>
Compiling Test 15 ... Done, took 3.241 seconds.<br>
Running Test 16 ... Done, took 27.007 seconds.<br>
Compiling Test 16 ... Done, took 0.779 seconds.<br>
Running Test 17 ... Done, took 2.648 seconds.<br>
Compiling Test 17 ... Done, took 0.415 seconds.<br>
Running Test 18 ... Done, took 2.183 seconds.<br>
Compiling Test 18 ... Done, took 3.592 seconds.<br>
Running Test 19 ... Done, took 17.97 seconds.<br>
Compiling Test 19 ... Done, took 2.409 seconds.<br>
<br>
and with caching<br>
<br>
Running Test 01 ... Done, took 0.085 seconds.<br>
Compiling Test 01 ... Done, took 0.428 seconds.<br>
Running Test 02 ... Done, took 0.031 seconds.<br>
Compiling Test 02 ... Done, took 0.439 seconds.<br>
Running Test 03 ... Done, took 0.198 seconds.<br>
Compiling Test 03 ... Done, took 0.529 seconds.<br>
Running Test 04 ... Done, took 0.254 seconds.<br>
Compiling Test 04 ... Done, took 0.556 seconds.<br>
Running Test 05 ... Done, took 0.353 seconds.<br>
Compiling Test 05 ... Done, took 0.66 seconds.<br>
Running Test 06 ... Done, took 0.021 seconds.<br>
Compiling Test 06 ... Done, took 0.45 seconds.<br>
Running Test 07 ... Done, took 0.013 seconds.<br>
Compiling Test 07 ... Done, took 0.426 seconds.<br>
Running Test 08 ... Done, took 0.014 seconds.<br>
Compiling Test 08 ... Done, took 0.393 seconds.<br>
Running Test 09 ... Done, took 0.012 seconds.<br>
Compiling Test 09 ... Done, took 0.403 seconds.<br>
Running Test 10 ... Done, took 0.028 seconds.<br>
Compiling Test 10 ... Done, took 0.463 seconds.<br>
Running Test 11 ... Done, took 0.015 seconds.<br>
Compiling Test 11 ... Done, took 0.415 seconds.<br>
Running Test 12 ... Done, took 0.021 seconds.<br>
Compiling Test 12 ... Done, took 0.408 seconds.<br>
Running Test 13 ... Done, took 0.014 seconds.<br>
Compiling Test 13 ... Done, took 0.544 seconds.<br>
Running Test 14 ... Done, took 0.022 seconds.<br>
Compiling Test 14 ... Done, took 1.86 seconds.<br>
Running Test 15 ... Done, took 1.484 seconds.<br>
Compiling Test 15 ... Done, took 3.33 seconds.<br>
Running Test 16 ... Done, took 2.988 seconds.<br>
Compiling Test 16 ... Done, took 0.779 seconds.<br>
Running Test 17 ... Done, took 0.111 seconds.<br>
Compiling Test 17 ... Done, took 0.437 seconds.<br>
Running Test 18 ... Done, took 0.096 seconds.<br>
Compiling Test 18 ... Done, took 3.585 seconds.<br>
Running Test 19 ... Done, took 11.742 seconds.<br>
Compiling Test 19 ... Done, took 2.293 seconds.<br>
<br>
The last thing you can do if you really want to get into it is turn on<br>
the debugging switch in tikzDevice.c by changing the line<br>
<br>
#define DEBUG FALSE<br>
<br>
near the top of the file to<br>
<br>
#define DEBUG TRUE<br>
<br>
Then recompiling and installing the package. After this running the<br>
test will show the number of times string width was calculated or<br>
looked up which will give you some idea of where the speedup is coming<br>
from.<br>
<br>
-Cameron<br>
<br>
<br>
<br>
On Fri, Dec 4, 2009 at 5:12 AM, Gabor Grothendieck<br>
<div><div></div><div class="h5"><<a href="mailto:ggrothendieck@gmail.com">ggrothendieck@gmail.com</a>> wrote:<br>
><br>
> Thanks. When I try to run the test it fails. This is the stderr output is shown below and test.log is attached. I am on Windows Vista and am running R 2.10.0.<br>
><br>
> ---<br>
><br>
> C:\tmp2\tikzDevice\inst\tests>Rscript testRTikZDevice.R --output=output > test.l<br>
> og<br>
> Loading required package: filehash<br>
> Loading required package: methods<br>
> filehash: Simple key-value database (2.0-1 2008-12-19)<br>
> tikzDevice: A Device for R Graphics Output in PGF/TikZ Format (v0.4.8)<br>
> Checking for a LaTeX compiler...<br>
><br>
><br>
> A working LaTeX compiler was found in:<br>
> The PATH using the command latex<br>
><br>
> Global option tikzLatex set to:<br>
> C:\PROGRA~1\MIKTEX~1.7\miktex\bin\latex.exe<br>
><br>
> MiKTeX-pdfTeX 2.7.2808 (1.40.4) (MiKTeX 2.7)<br>
> Copyright (C) 1982 D. E. Knuth, (C) 1996-2006 Han The Thanh<br>
> TeX is a trademark of the American Mathematical Society.<br>
><br>
><br>
> Error in getMetricsFromLatex(TeXMetrics) :<br>
> ******** There was a problem calculating string metrics,<br>
> ******** likely there was a problem with your custom packages.<br>
> ******** See the LaTeX log file above for details.<br>
> Calls: source ... Axis.default -> axis -> <Anonymous> -> getMetricsFromLatex<br>
> Execution halted<br>
><br>
> ---<br>
><br>
> On Wed, Dec 2, 2009 at 8:23 PM, Cameron Bracken <<a href="mailto:cameron.bracken@gmail.com">cameron.bracken@gmail.com</a>> wrote:<br>
>><br>
>> Not quite sure what you mean by relative speed, but yes there is a test suite that times some output. The suite is in the inst/tests directory of the source code. A vast majority of the time is taken by calculating string widths. The performance gain from caching metrics calculations is very noticable, somtimes up to 90% when lots of strings are involved. Does this answer your question?<br>
>><br>
>> -Cameron<br>
>><br>
>> On Dec 2, 2009, at 6:10 PM, Gabor Grothendieck <<a href="mailto:ggrothendieck@gmail.com">ggrothendieck@gmail.com</a>> wrote:<br>
>><br>
>>> Are there any performance benchmarks for tikzdevice? Is the relative speed noticeable?<br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> Tikzdevice-bugs mailing list<br>
>>> <a href="mailto:Tikzdevice-bugs@lists.r-forge.r-project.org">Tikzdevice-bugs@lists.r-forge.r-project.org</a><br>
>>> <a href="https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/tikzdevice-bugs" target="_blank">https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/tikzdevice-bugs</a><br>
><br>
</div></div></blockquote></div><br>