Re: [AMBER] How to avoid tleap error *** Error: tl_getline(): not interactive, use stdio.

From: Niel Henriksen <niel.henriksen.utah.edu>
Date: Mon, 10 Jun 2013 19:13:22 +0000

If you leave "quit" out of your tleap input file AND redirect the output, it will give that error.

----- tleap.in -----
source leaprc.ff12SB
m=sequence {G5 A C C3}
saveamberparm m test.topo test.crds
---------------------

> tleap -s -f tleap.in > tleap.out
*** Error: tl_getline(): not interactive, use stdio.


Including the "quit" command at the end of the input file fixes the problem.
FYI, I am using an up-to-date/patched Amber12/AmberTools13 on RedHat 5.8, compiled with Intel v.12.1.3.293.

--Niel

________________________________________
From: David A Case [case.biomaps.rutgers.edu]
Sent: Monday, June 10, 2013 12:53 PM
To: AMBER Mailing List
Subject: Re: [AMBER] How to avoid tleap error *** Error: tl_getline(): not interactive, use stdio.

On Mon, Jun 10, 2013, ET wrote:

> if I use the command:
>
> tleap -f myScript.tleap,
>
> I always get this error.

I can't reproduce this. What version of AmberTools do you have? Which
OS/compiler?

I *do* get the error if I type "tleap < script.in". Workaround is to use the
"-f" flag.

...dac


_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber

_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Mon Jun 10 2013 - 12:30:02 PDT
Custom Search