From: JC Gumbart (gumbart_at_ks.uiuc.edu)
Date: Mon Dec 20 2010 - 18:11:08 CST
I can't reproduce that exact error, even using 2.7b3. One thing I will point out though is that some of the keywords you use in the abf block don't belong there, but rather in the colvar block.
Hopefully someone else has some insight.
On Dec 20, 2010, at 4:10 PM, Alex Liu wrote:
> I have attached the configuration files.
> Thanks for your help.
> From: JC Gumbart <gumbart_at_ks.uiuc.edu>
> To: Alex Liu <liu.alex77_at_yahoo.com>
> Cc: namd-l_at_ks.uiuc.edu
> Sent: Mon, December 20, 2010 4:37:54 PM
> Subject: Re: namd-l: ABF on NAMD 2.7b3
> Please also copy your configuration file(s), so we can determine if there is a mistake there. The error message suggests you left a necessary input field blank.
> On Dec 20, 2010, at 3:03 PM, Alex Liu wrote:
>> Dear NAMD users,
>> I am using NAMD 2.7b3 to run ABF. After running I get an error as below:
>> colvars: Initializing a new collective variable.
>> colvars: # name = ProjectionZ
>> colvars: Initializing a new "distance projection on an axis" component.
>> colvars: # componentCoeff = 1 [default]
>> colvars: # componentExp = 1 [default]
>> colvars: Initializing atom group "main".
>> colvars: Error: keyword "" is not supported, or not recognized in this context.
>> colvars: If this error message is unclear, try recompile with -DCOLVARS_DEBUG.
>> FATAL ERROR: Error in the collective variables module: exiting.
>> ------------- Processor 0 Exiting: Called CmiAbort ------------
>> Reason: FATAL ERROR: Error in the collective variables module: exiting.
>> Can you please help me? I am using NAMD on super computers. Is there something wrong with compiling NAMD by them?
This archive was generated by hypermail 2.1.6 : Wed Feb 29 2012 - 15:54:53 CST