It probably is a bug, but also there is no need to burn up memory with
set antialiasdisplay on
The image antialiasing is independent of the display antialiasing. I had
not problem with this:
$ load =7tim
select all
spacefill off
select not solvent
spacefill
color chain
reset;center {73.4425 41.286503 51.1565}; rotate z 102.41; rotate y 149.09;
rotate z -65.73;
select pgh
spacefill
color cpk
#set antialiasdisplay on
background white
$
INTRAMOLECULAR OXIDOREDUCTASE 23-APR-91 7TIM
STRUCTURE OF THE TRIOSEPHOSPHATE ISOMERASE-
PHOSPHOGLYCOLOHYDROXAMATE COMPLEX: AN ANALOGUE OF THE
INTERMEDIATE ON THE REACTION PATHWAY
4,033 atoms selected
3,786 atoms selected
20 atoms selected
$ write image 2000 1500 xxx.jpg
OK JPG 332995 C:/jmol-dev/workspace/Jmol/bobtest/xxx.jpg; quality=-1;
width=2000; height=1500
$
It's not a huge image -- no need for all that extra memory, I think. And
there's no need to change your frame size of Jmol itself. That's consuming
lots of memory itself. This even worked with 1G of memory:
$ write image 4000 3000 xxx2.jpg
OK JPG 885709 C:/jmol-dev/workspace/Jmol/bobtest/xxx2.jpg; quality=-1;
width=4000; height=3000
so you are way below the range of problems.
On Mon, Apr 2, 2012 at 3:51 PM, Eric Martz <[email protected]>wrote:
> I wanted to make large (hi-res) jpg images using Jmol 12.2.19
> application. I start it with
>
> java -Xmx1024m -jar ~/Downloads/jmol-app/jmol.jar
>
> on OS X to give Jmol 1 gig of memory.
>
> Here is my script:
>
> load =7tim
> select all
> spacefill off
> select not solvent
> spacefill
> color chain
>
> reset;center {73.4425 41.286503 51.1565}; rotate z 102.41; rotate y
> 149.09; rotate z -65.73;
>
> select pgh
> spacefill
> color cpk
>
> set antialiasdisplay on
> background white
>
>
> 1. My screen is 1440 x 900 pixels. Before saving the jpg, I use
> Jmol's Display, Resize menu to set Jmol to 2000 x 1500 pixels.
>
> First possible bug: Every time I do that, I get only the width reset.
> So if Jmol was 1024 x 765 pixels, and I request 2000 x 1500, I get
> 2000 x 765. On the second try, it always works, going to the
> requested 2000 x 1500. Of course I cannot see the entire image on my
> screen, but that is OK.
>
> 2. I was able to "write jpg xx.jpg" for a cartoon image, and for a
> wireframe image at 2000 x 1500 pixels. However, I was unable to write
> the jpg at that pixel size for a spacefill image (above script). The
> write completes, but the image is corrupted. This appears to me to be a
> bug.
>
> I also tried it at 1500 x 1000 pixels and also got a (different)
> corrupted image in the jpg file. Jmol's display flashes the corrupted
> image while it is writing, then returns to the true image after
> writing is completed.
>
> At 1024 x 765 pixels, I was able to save the image without any corruption.
>
> Thanks, Eric
>
>
>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> Jmol-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jmol-users
>
--
Robert M. Hanson
Professor of Chemistry
St. Olaf College
1520 St. Olaf Ave.
Northfield, MN 55057
http://www.stolaf.edu/people/hansonr
phone: 507-786-3107
If nature does not answer first what we want,
it is better to take what answer we get.
-- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users
