[From nobody Wed Jul 15 11:55:14 2009
Return-Path: &lt;pymol-users-bounces@lists.sourceforge.net&gt;
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on
	nighthawk.chemicalconnection.dyndns.org
X-Spam-Level: *****
X-Spam-Status: No, score=5.1 required=8.0 tests=AWL,TVD_RCVD_IP,TVD_RCVD_IP4
	autolearn=disabled version=3.2.5
X-Flags: 0000
Delivered-To: GMX delivery to mbanck@gmx.net
Received: from 213.165.64.22 [213.165.64.22]
	by nighthawk.chemicalconnection.dyndns.org with POP3
	(fetchmail-6.3.9-rc2) for &lt;mbanck@localhost&gt; (single-drop);
	Thu, 18 Sep 2008 21:39:28 +0200 (CEST)
Received: (qmail invoked by alias); 18 Sep 2008 19:32:20 -0000
Received: from lists-outbound.sourceforge.net (EHLO
	lists-outbound.sourceforge.net) [66.35.250.225]
	by mx0.gmx.net (mx086) with SMTP; 18 Sep 2008 21:32:20 +0200
Received: from sc8-sf-list2-new.sourceforge.net
	(sc8-sf-list2-new-b.sourceforge.net [10.3.1.94])
	by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP
	id 71A04125CF; Thu, 18 Sep 2008 12:32:18 -0700 (PDT)
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]
	helo=mail.sourceforge.net)
	by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43)
	id 1KgPER-0001A6-Ea; Thu, 18 Sep 2008 12:32:03 -0700
Received: from [208.84.113.32] (helo=host-208.84.113.32.hosting4less.com)
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1KgPEd-0000eq-8d; Thu, 18 Sep 2008 12:32:16 -0700
Received: from parxp (ssf.delsci.net [66.134.243.26]) (authenticated bits=0)
	by apollo.hosting4less.com (8.13.1/8.13.1) with ESMTP id m8IJPVcU027196;
	Thu, 18 Sep 2008 12:25:36 -0700
Message-Id: &lt;200809181925.m8IJPVcU027196@apollo.hosting4less.com&gt;
From: &quot;DeLano Scientific&quot; &lt;delsci@delsci.info&gt;
To: &lt;pymol-users@lists.sourceforge.net&gt;
Date: Thu, 18 Sep 2008 12:32:07 -0700
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AckZvl4ZIVC664U4QmKc9ybfPAkR7AABVnzQ
In-Reply-To: &lt;BB3AE652-1F9D-4C66-98EA-163E98B6A25E@mac.com&gt;
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Cc: apbs-users@lists.sourceforge.net
Subject: [PyMOL] Plan for FreeMOL: APBS/PQR2PDB + MENGINE + MPEG movie creation
X-BeenThere: pymol-users@lists.sourceforge.net
X-Mailman-Version: 2.1.8
Precedence: list
List-Id: PyMOL Users Group &lt;pymol-users.lists.sourceforge.net&gt;
List-Unsubscribe: &lt;https://lists.sourceforge.net/lists/listinfo/pymol-users&gt;, 
	&lt;mailto:pymol-users-request@lists.sourceforge.net?subject=unsubscribe&gt;
List-Archive: &lt;http://sourceforge.net/mailarchive/forum.php?forum_name=pymol-users&gt;
List-Post: &lt;mailto:pymol-users@lists.sourceforge.net&gt;
List-Help: &lt;mailto:pymol-users-request@lists.sourceforge.net?subject=help&gt;
List-Subscribe: &lt;https://lists.sourceforge.net/lists/listinfo/pymol-users&gt;,
	&lt;mailto:pymol-users-request@lists.sourceforge.net?subject=subscribe&gt;
Content-Type: text/plain; charset=&quot;us-ascii&quot;
Content-Transfer-Encoding: 7bit
Sender: pymol-users-bounces@lists.sourceforge.net
Errors-To: pymol-users-bounces@lists.sourceforge.net
X-GMX-Antivirus: -1 (not scanned, may not use virus scanner)
X-GMX-Htest: 0.48
X-GMX-Antispam: 0 (Mail was not recognized as spam)
X-GMX-UID: ocW3CUs8fW4p7UkifWVoDgRmdmllcgXp


&gt; This might be a good reason to start moving towards distribution of
&gt; APBS and PDB2PQR with PyMOL! :)

Indeed, along those lines, here is the plan:

Starting with PyMOL 1.2, we will start distributing an accompanying
open-source compilation named FreeMOL, which includes several packages many
users would like to be able to call upon when using PyMOL.  They are:

(a) an electrostatics package (APBS / PDB2PQR of course).

(b) an MMFF forcefield &amp; minimizer (mengine) for small molecule building and
peptide modeling.

(C) an MPEG movie generator (mpeg_encode, most likely).

In each case, we are doing the upfront compilation, integration, and testing
to ensure that what ships actually interoperates reliably, on Mac, on
Windows, and on Linux.  With this effort, I am determined that we will get
to a point where all this stuff &quot;just works&quot; together without major issues.

Well.  That is the plan at least.  Nothing in software can ever be taken for
granted until it has shipped.  At present, we about two thirds of the way
there, so hopefully the rest will have come together before the end of the
year.  Betas will be out much sooner of course...

By the way, just to be absolutely crystal clear:  FreeMOL is and will remain
a 100% free-software  open-source project, distributed under full compliance
with each component's own open-source licensing terms.  As such, FreeMOL is
and must be kept well-separated from our closed-source PyMOL derivatives.  

Cheers,
Warren

PS. I suspect I am not the only one looking forward to the day when we stop
seeing all those repeated &quot;ObjectMapLoadDXFile-Error&quot;s clogging up the APBS
&amp; PyMOL mailing lists...

&gt; -----Original Message-----
&gt; From: pymol-users-bounces@lists.sourceforge.net [mailto:pymol-users-
&gt; bounces@lists.sourceforge.net] On Behalf Of Nathan Baker
&gt; Sent: Thursday, September 18, 2008 11:54 AM
&gt; To: DeLano Scientific
&gt; Cc: apbs-users@lists.sourceforge.net; gilles.truan@cgm.cnrs-gif.fr; pymol-
&gt; users@lists.sourceforge.net
&gt; Subject: Re: [PyMOL] [Apbs-users] Strange behaviour with APBS
&gt; 
&gt; Hi Warren --
&gt; 
&gt; &gt; Strictly speaking, the issue may be with PDB2PQR itself, not APBS.
&gt; &gt; Furthermore, we don't yet know whether a combined development
&gt; &gt; version of all
&gt; &gt; three packages would still reproduce the problem.
&gt; 
&gt; This might be a good reason to start moving towards distribution of
&gt; APBS and PDB2PQR with PyMOL! :)
&gt; 
&gt; &gt; As an aside, a good reason for PyMOL to see PQR files is for
&gt; &gt; diagnostic
&gt; &gt; visualization:  to enable the user to inspect and modify or
&gt; &gt; manipulate what
&gt; &gt; is being fed directly into APBS.
&gt; 
&gt; I agree completely.  However, I think we can remain flexible with the
&gt; PQR format while still allowing this.
&gt; 
&gt; &gt; PyMOL can read &amp; write PQR directly, though we may have issues reading
&gt; &gt; non-PDB-like PQR files.  I would generally agree that use of PDB2PQR
&gt; &gt; to
&gt; &gt; convert PDBs to PQRs is the preferred route, since PyMOL doesn't do
&gt; &gt; any
&gt; &gt; checking or optimization.
&gt; 
&gt; OK.
&gt; 
&gt; &gt; Anyway, based on reported symptoms alone, the problem appears to be
&gt; &gt; that
&gt; &gt; some component in the PyMOL-&gt;APBS pipeline assumes that the input
&gt; &gt; PDBs are
&gt; &gt; space-delimited rather than column-delimited.  This guess is based
&gt; &gt; on the
&gt; &gt; observation that a B-factor of 100 or greater eliminates the space
&gt; &gt; between
&gt; &gt; the occupany and the B factor in spec-compliant PDB files, and the
&gt; &gt; calculation fails.
&gt; 
&gt; This seems like a reasonable guess but I can't think of a component of
&gt; PDB2PQR that is sensitive to this.  Gilles, can you confirm that you
&gt; used PDB2PQR to generate the PQR file for your calculation?
&gt; 
&gt; Thanks,
&gt; 
&gt; Nathan
&gt; 



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
_______________________________________________
PyMOL-users mailing list
PyMOL-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pymol-users
]