Thanks for the trick.
This sounds like a good method, in general.
I will do this when I finish debugging my code
and start to work on many files.
I was just curious if we can do this in a program.
Perhaps this is actually a Python problem,
not a Pymol specific problem.
> Message: 3
> From: Nathaniel Echols <nat@...>
> Subject: Re: [PyMOL] Suppress some output
> > Is there a way to keep my program 'quiet',
> > or I can customize the output message myself?
> Depending on your OS and shell, something like this may work:
> denethor:~ > /usr/local/pymol/pymol.com >/dev/null 2>/dev/null
> This works under Bash in any modern Linux distribution, from what I've
> seen. I suspect it would work on Irix too (still using Bash). I've had
> the exact same problem- mainly with util.rainbow().
In the on-line help (of `iterate_state'), I found examples that
one can iterate through atoms and obtain their x value.
But I tried on my local installations (both Win and Linux),
an error was there when I tried to access 'x' value, for example.
But I can access other properties like partial charge, etc.
Is there an exaust list of atom properties that I can obtain
Or is there a way to know what properties are there
in a python class?
Thanks for your help in advance.
Even better: try the "feedback" command:
Will suppress most of PyMOL's normal chatter.
Warren L. DeLano, Ph.D.
Sunesis Pharmaceuticals, Inc.
341 Oyster Point Blvd.
S. San Francisco, CA 94080
> -----Original Message-----
> From: kkliang@... [mailto:kkliang@...]
> Sent: Monday, July 29, 2002 10:23 PM
> To: pymol-users@...
> Subject: [PyMOL] Suppress some output
> Dear Pymolers,
> Well I asked about the possibility of supressing some output
> from pymol earlier.
> I'm so happy that I found something important.
> In my case, what bothered me is that I have to do a lot of
> selections and analyze the selected residues.
> There are roughly 10,000 selection for each pdb file that I analyze.
> That is crazily slow if there is always a
> "Selection: xxxx" output for each selection I make.
> But today I decided to dig in the code and found that
> there are two undocumented arguments to "selection"...
> def select(name,selection=3D"",quiet=3D0,show=3D0):
> I tried the combinations of the use of them and found that
> the selection operation will be quiet if we just set quiet=3D1.
> However, the value of show has no effect in my tests.
> I will try to dig out more cases like this if I run into
> other routines which also output to console too often.
> But you who have your own problem may try to find out
> if there is such option in the routine you want to use.