Hi Thomas,
I'm not sure I get it. Does that mean that `cmd.sync()` is actually not
doing anything at all if called outside of `cmd.do()`?
Cheers,
Lorenzo
Il giorno mer 18 dic 2019 alle ore 10:49 Thomas Holder <
thomas.hol...@schrodinger.com> ha scritto:
> Hi Lorenzo,
>
> Thanks for the script,
Hi Lorenzo,
Thanks for the script, and great that you could identify cmd.sync() as the
culprit. I looked at the code, cmd.do("cmd.sync()") literally blocks itself
until it times out after 1 second. cmd.do() puts commands in a queue, and
cmd.sync() tries to ensure that all queued commands have
After playing around with it a bit longer, it's clear that I misunderstood.
The issue was not with `cmd.alter` nor with `cmd.show_as`, but with
`cmd.sync`.
I was calling many times a smaller function that contained `cmd.sync()`,
which resulted - it seems - in all these calls piling up.
Still, I
OK thanks. I haven't seen such performance differences before and couldn't
reproduce it so far. Could you share your script (and data files if possible)
with me?
Thanks,
Thomas
> On Dec 16, 2019, at 5:42 PM, Lorenzo Gaifas wrote:
>
> Yes, it does. Both cases are with the GUI and ewual
Yes, it does. Both cases are with the GUI and ewual graphical
representation.
On Mon, Dec 16, 2019, 17:37 Thomas Holder
wrote:
> Hi Lorenzo,
>
> When you say "run from a python script", is that with the graphical GUI?
> That "instant update", does that include instant update of visual
>
Hi Lorenzo,
When you say "run from a python script", is that with the graphical GUI? That
"instant update", does that include instant update of visual representations?
Thanks,
Thomas
> On Dec 13, 2019, at 12:55 PM, Lorenzo Gaifas wrote:
>
> Dear Pymol users,
>
> I just discovered
Dear Pymol users,
I just discovered something I did not expect: the same python function can
have extremely different performance when called as a python function or
using the pymol api.
To be more specific: I have a function func that (among other things) uses
cmd.alter several times over a big
