rescalante-lilly / ruffus

Automatically exported from code.google.com/p/ruffus
MIT License
0 stars 0 forks source link

pipeline_printout_graph fails to generate figures for recent versions of Graphviz #64

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
When running the Ruffus on the same pipeline on two different systems, I am 
having issues generating the pipeline plots on the more up to date system.

Old system (works):

 dot - graphviz version 2.26.3 (20100126.1600)

New system (doesn't work):

 dot - graphviz version 2.36.0 (20140111.2315)

Both systems are running 64-bit linux with Python 2.7.6 and the latest stable 
version of Ruffus (2.2). It's possible that the differences are caused by 
something else besides the version of Graphviz, but since the generation fails 
without any errors (an empty image file is generated), I suspect the issue is 
due to differences in Graphviz.

Let me know if there is anything I can do to help further diagnose the issue.

Original issue reported on code.google.com by keith.hu...@gmail.com on 24 Mar 2014 at 5:25

GoogleCodeExporter commented 9 years ago
It appears that the latest version of dot is a bit stricter in its 
understanding of the dot language. The "margins" attribute of a node has to be 
specified a string not a pair of numbers...
This has been fixed in the ruffus git repository 
https://github.com/bunbun/ruffus
and will be part of the 2.4 release next week.

Thanks for finding this.

I have to say that install the latest version of graphviz on ubuntu has been a 
right pain, involving manually editing the dependencies inside the debian 
archive!!!

Leo

Original comment by bunbu...@gmail.com on 27 Mar 2014 at 7:18

GoogleCodeExporter commented 9 years ago
Thanks for the quick fix, Leo!

That's unfortunate about the upgrading pains. In the past when I ran Ubuntu, I 
found the 'apt-get build-dep xxx' command very helpful for testing new versions 
of software (it installs all of the known dependencies for compilation), but 
since the dependencies were appear to have changed, that probably would have 
failed as well.

Original comment by keith.hu...@gmail.com on 29 Mar 2014 at 12:13