Re: amber-developers: retired namelist vars

From: Robert Duke <rduke.email.unc.edu>
Date: Tue, 17 Feb 2004 16:15:22 -0700

Scott -
PMEMD already does this. I have based retirement status on sander8 as of
about a week ago
- Regards - Bob
----- Original Message -----
From: "Scott Brozell" <sbrozell.scripps.edu>
To: <amber-developers.scripps.edu>
Sent: Tuesday, February 17, 2004 6:04 PM
Subject: Re: amber-developers: retired namelist vars


> Hi,
>
> I don't have time to include amber 6 -> 7.
> This should be done incrementally as a normal practice
> of development, not in batch.
> Here is a procedure I suggest: when a namelist variable is
> retired it is removed from all files except that which reads
> its namelist. it is made local to the appropriate subroutine
> in that file and given the initial value RETIRED_INPUT_OPTION;
> then after the namelist is read a warning is emitted if the
> value has changed.
> idxm and ischrgd are examples.
>
> Scott
>
> On Fri, 13 Feb 2004, Viktor Hornak wrote:
>
> > Scott Brozell wrote:
> >
> > >I have added a new Appendix for Retired Namelist Variables.
> > >So far only dxm and ischrgd appear.
> > >Usage of these variables is detected and a warning is emitted.
> > >
> > >What other input options have been removed ?
> > >
> > How about adding also variables retired from amber6 -> amber7? Many
> > people may still have inputs from amber6 and if they want to make a
> > transition to amber8, it might help...
> >
> > Just a thought,
> > -Viktor
> >
>
>
Received on Wed Apr 05 2006 - 23:50:05 PDT
Custom Search