| | 1 | == July 7, 2009 == |
| | 2 | '''Attendees''': Conrad, Elaine, Greg, Eric, TomG, Scooter, TomF |
| | 3 | |
| | 4 | === Action Items === |
| | 5 | * TBD |
| | 6 | |
| | 7 | === Items === |
| | 8 | 1. Trac reports |
| | 9 | - After some discussion, it was agreed that people should assign milestones when possible and to elevate priorities of bug reports that should be addressed promptly. Trac reports with above-normal priorities will be reviewed at each Chimera meeting. |
| | 10 | 1. Chimera 1.4 release schedule |
| | 11 | - TomF needs to demonstrate Chimera in August. Rather than making a snapshot, everyone agreed that using the daily build for demo and saying that the features will be available in an upcoming release is acceptable. |
| | 12 | 1. Chris Schafmeister tools |
| | 13 | - Chris has C++ code that "implements the Amber/Gadd force field, automatic type assignment, automatic parameter assignment, very fast geometry optimization and conformational searching." He is interested in having the code working/distributed with Chimera. If we are interested, Chris has volunteered to take the first step of making his code Python accessible to Chimera and to provide some glue code for linking data structures; the follow-up of creating Chimera user interfaces can be split between the groups. TomG and Conrad were concerned that this may be a significant undertaking. Eric pointed out that Chris is motivated to make this work since his group uses these tools and may be valuable collaborators with biological projects. Scooter and TomG agreed that the potential return is work serious investigation and that we should work with Chris on the integration. |
| | 14 | 1. Pov-Ray defaults |
| | 15 | - Eric pointed out that increasing the antialias threshold significantly reduces computation time while image quality only degrades slightly. Everyone agreed that it should be increased to 1.0 by default for performance and users can lower it for higher quality. |
| | 16 | 1. '''Meeting adjourned''' |