[reportlab-users] SVG export in comparison to PDF?

[Peter Cock]

On Fri, Aug 9, 2013 at 5:52 PM, Marc Tompkins <marc.tompkins at gmail.com> wrote:

> On Fri, Aug 9, 2013 at 8:32 AM, Ilya Flyamer <flyamer at gmail.com> wrote:

>>

>> I am using GenomeDiagram from BioPython, which is based on ReportLab to

>> generate pictures, to draw some graphs/maps on the genome. The data is in

>> general huge, so that export of a picture out into PDF file takes a few

>> minutes. But the problem is with export in SVG files: I waited over 40

>> minutes and it still hasn't finished writing to disk (BTW, the process was

>> using >1Gb of RAM, but only 1-2% of CPU - looks strange to me, is it?).

>> Is it an issue in ReportLab or a pure format structure issue?

>>

> Can you try it with a very small chunk of data?  I don't know BioPython or

> GenomeDiagram, but I presume that there must be some way to handle tiny

> snippets; in any case, does it successfully create an SVG when the dataset

> is not huge?


The size of the successful PDF file would be interesting as a rough
way to guess the complexity of your figure and how big the SVG
might be.

Have you run the Biopython unit tests, specifically file
Tests/test_GenomeDiagram.py which should produce some
sample PDF and SVG output in Tests/Graphics/ ?

Also what versions of Python, Biopython and ReportLab do you
have, and were there any issues installing the C bits of ReportLab?

Regards,

Peter