pathview
1
0
Entering edit mode
Hilary Smith ▴ 70
@hilary-smith-5927
Last seen 10.3 years ago
Hi, I just started using pathview (great program!) and was wondering if there is a way to make the images in eps format vs the .png files that are produced, so that I can use the images for publication in journals requiring eps. I don't think a standard postscript command like I normally use in R would work here, because the figure generation automatically occurs when I use the ">pathview" command. At present I am using the Development version of the package (see below) because I have a "non-model" organism (mosquito, Anopheles), and it seems I need to use the latest/development version to use the Kegg gene IDs for my organism (e.g., "AgaP_AGAP005583"). I can re-save and thus convert the PNG image as EPS in ADOBE, but I am not sure if that'll decrease resolution relative to making the format in EPS in R originally. Thanks! > sessionInfo() R version 3.0.2 (2013-09-25) Platform: x86_64-apple-darwin10.8.0 (64-bit) locale: [1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8 attached base packages: [1] parallel stats graphics grDevices utils datasets methods [8] base other attached packages: [1] pathview_1.1.7 org.Hs.eg.db_2.10.1 RSQLite_0.11.4 [4] DBI_0.2-7 AnnotationDbi_1.23.25 Biobase_2.21.7 [7] BiocGenerics_0.7.5 KEGGgraph_1.17.0 graph_1.39.3 [10] XML_3.95-0.2 loaded via a namespace (and not attached): [1] Biostrings_2.29.19 digest_0.6.3 grid_3.0.2 httr_0.2 [5] IRanges_1.19.38 KEGGREST_1.1.1 png_0.1-6 RCurl_1.95-4.1 [9] Rgraphviz_2.5.4 stats4_3.0.2 stringr_0.6.2 tools_3.0.2 [13] XVector_0.1.4 -------------------------------------------------- Dr. Hilary April Smith Postdoctoral Research Associate University of Notre Dame Department of Biological Sciences 321 Galvin Life Sciences [[alternative HTML version deleted]]
Organism convert pathview Organism convert pathview • 2.0k views
ADD COMMENT
0
Entering edit mode
Luo Weijun ★ 1.6k
@luo-weijun-1783
Last seen 18 months ago
United States
Hi Hilary, It straightforward to include in pathview options to output the native kegg graphs in other format, like PDF or postscript. I originally had that in the early development phase of pathview. But I decided not to do that, because the file size of raster image format like PDF output from R is huge (> 10 times the size of PNG output), and without any gain of resolution. Note that pathview output resolution is limited by the source KEGG graphs (in PNG), which are usually not extremely high as they are raster image. Therefore it is better stick to PNG. I believe many journals are okay with PNG. You may always do the format conversion in adobe illustrator etc for pulication purpose. You are right you need to use the latest/development version to use the Kegg gene IDs for many minor species like in your case. If you need to do pathway analysis on your species, the latest gage package also has a new function kegg.gsets, to compile pathway gene set any of the 2300 KEGG species and KEGG Orthology (with species="ko"). HTH. Weijun On Tue Oct 1 Hilary Smith wrote: Hi, I just started using pathview (great program!) and was wondering if there is a way to make the images in eps format vs the .png files that are produced, so that I can use the images for publication in journals requiring eps. I don't think a standard postscript command like I normally use in R would work here, because the figure generation automatically occurs when I use the ">pathview" command. At present I am using the Development version of the package (see below) because I have a "non-model" organism (mosquito, Anopheles), and it seems I need to use the latest/development version to use the Kegg gene IDs for my organism (e.g., "AgaP_AGAP005583"). I can re-save and thus convert the PNG image as EPS in ADOBE, but I am not sure if that'll decrease resolution relative to making the format in EPS in R originally. Thanks!
ADD COMMENT

Login before adding your answer.

Traffic: 668 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6