Hi,

By tweaking the projection matrix, we can divide a big scene into
several sub-images and render them separately. Thus, we can reduce
the memory consumption. I think this is scriptable, although I
don't have time to implement myself.

 > I was wondering if the developers have come across this upper limit too?
 > I have a 2400 dpi printer, so I want to go with the highest dpi possible
 > for the best quality.

"2400 dpi" for a printer does not have the same meaning as 2400
dpi (or better, ppi, pixel per inch) for a screen.
Printers use many dots to represent an image pixel.
Did you take that into the account? Probably you don't need 2400 dpi
or 1200 dpi.

https://en.wikipedia.org/wiki/Dots_per_inch#/media/File:DPI_and_PPI.png

Best regards,

Takanori Nakane

Am 2016年05月10日 um 09:34 schrieb Stephen Kerry:
> Thank you for trying this out on a workstation with 128 GB and then 256
> GB of RAM. It is much appreciated as I do not have easy access to that
> kind of computational power. The fact that you also get these segfaults
> with all of your RAM, suggests that this might be a PyMOL limitation,
> rather than a hardware issue.
>
> I have come to the conclusion that it is impossible to ray trace an
> image with an output resolution greater than 45 megapixels (7500 x
> 6000). Halving the dpi from 1200 to 600 gives a 11.25 megapixel (3750 x
> 3000) resolution.
>
> I was wondering if the developers have come across this upper limit too?
> I have a 2400 dpi printer, so I want to go with the highest dpi possible
> for the best quality.
>
> ------------------------------------------------------------------------
> *From:* David Hall <li...@cowsandmilk.net>
> *Sent:* 06 May 2016 19:17:38
> *To:* Stephen Kerry
> *Cc:* pymol-users@lists.sourceforge.net
> *Subject:* Re: [PyMOL] High Resolution Ray Tracing
> Feel free to send me the files off list.
>
> -David Hall
>
>> On May 6, 2016, at 1:54 PM, Stephen Kerry <stephen.kerr...@outlook.com
>> <mailto:stephen.kerr...@outlook.com>> wrote:
>>
>> Dear All,
>>
>> I have a protein complex scene that I need to create a large, high
>> resolution (1200 dpi) ray traced image of, but am unable to do so as I
>> always run out of memory at the end of the ray tracing process, with
>> the following error:
>>
>> python2.7(972,0x7fff7397f300) malloc: ***
>> mach_vm_map(size=18446744068907188224) failed (error code=3)
>> *** error: can't allocate region
>> *** set a breakpoint in malloc_error_break to debug
>>
>> This is with PyMOL 1.81 from Fink on OSX 10.10 with
>> ani7-4790Kprocessor and 32 GB of DDR3. Python2.7 expands up to 15 GB
>> of RAM, with more than twice this reserved for virtual memory, but no
>> swap is actually used.
>>
>> Decreasing hash_max just increases the ray tracing time until the
>> error at the end. Sometimes PyMOL will be terminated with this error,
>> whilst at other times a transparent PNG is all that is produced.
>>
>> Is there a way to force PyMOL to use virtual memory to avoid these
>> errors/crashes at the expense of processing time?
>>
>> If not, is there anyone who has PyMOL 1.8x installed on a system with
>> 64 GB or more RAM, who would be able to render this ray traced image
>> if I send the, the .pse file and .pml script off list? Takes about 10
>> mins to process.
>>
>> Cheers,
>>
>> Stephen
>>
>> ------------------------------------------------------------------------------
>> Find and fix application performance issues faster with Applications
>> Manager
>> Applications Manager provides deep performance insights into multiple
>> tiers of
>> your business applications. It resolves application problems quickly and
>> reduces your MTTR. Get your free trial!
>> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z_______________________________________________
>> PyMOL-users mailing list (PyMOL-users@lists.sourceforge.net
>> <mailto:PyMOL-users@lists.sourceforge.net>)
>> Info Page:https://lists.sourceforge.net/lists/listinfo/pymol-users
>> Archives:http://www.mail-archive.com/pymol-users@lists.sourceforge.net
>
>
>
> ------------------------------------------------------------------------------
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
>
>
>
> _______________________________________________
> PyMOL-users mailing list (PyMOL-users@lists.sourceforge.net)
> Info Page: https://lists.sourceforge.net/lists/listinfo/pymol-users
> Archives: http://www.mail-archive.com/pymol-users@lists.sourceforge.net
>

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
PyMOL-users mailing list (PyMOL-users@lists.sourceforge.net)
Info Page: https://lists.sourceforge.net/lists/listinfo/pymol-users
Archives: http://www.mail-archive.com/pymol-users@lists.sourceforge.net

Reply via email to