Excessive status output

[goddard@…]

The following bug report has been submitted:
Platform:        Darwin-18.7.0-x86_64-i386-64bit
ChimeraX Version: 0.91 (2019-09-06)
Description
swapaa seems to send hundreds of status messages per second so they just are a blur on top of each other in the status line.  This unreadable status gives no indication what is going on, and may be slowing down the whole process since the OpenGL rendering to the status line is waiting for display vsync so can at most show 60 status messages per second without blocking.  The granularity of status messages should be chosen to get about 1 message per second.


Log:
UCSF ChimeraX version: 0.91 (2019-09-06)  
© 2016-2019 Regents of the University of California. All rights reserved.  
How to cite UCSF ChimeraX  

> open 6h6b format mmCIF fromDatabase pdb

6h6b title:  
Structure of alpha-synuclein fibrils [more info...]  
  
Chain information for 6h6b #1  
---  
Chain | Description  
A B C D E F G H I J | Alpha-synuclein  
  
  

> swapaa /A:53 GLU

Using Dunbrack library  
/A ALA 53: phi -136.3, psi 131.6 trans  
Applying GLU rotamer (chi angles: -63.7 -179.7 25.5) to /A GLU 53  

> swapaa /A:53 GLU

Using Dunbrack library  
/A GLU 53: phi -136.3, psi 131.6 trans  
Applying GLU rotamer (chi angles: -63.7 -179.7 25.5) to /A GLU 53  




OpenGL version: 4.1 ATI-2.11.20
OpenGL renderer: AMD Radeon Pro Vega 20 OpenGL Engine
OpenGL vendor: ATI Technologies Inc.

[Eric Pettersen]

Cut way back on the status message output by having swapaa silence the status output of the hbonds calls, with just one status message before and after all the calls.

[Eric Pettersen]

You were also right that the status messages were slowing things down. With status messages on the structure/residue you were using: chp criteria: 0.7 seconds, hcp criteria: 5.0 seconds. With reduced status messages: 0.3 and 1.1 seconds.