Sorry, I think I had a corrupted .pm somewhere, no more problems after and rm -R and cvs update...
--- En date de : Ven 4.7.08, Weigert, Thomas <weigert
AT
mst.edu> a écrit :
De: Weigert, Thomas <weigert
AT
mst.edu>
Objet: RE: [GT] Input validation in Tools.pm
À: sam_backtester
AT
yahoo.fr, devel
AT
geniustrader.org
Date: Vendredi 4 Juillet 2008, 22h40
Can you be more specific about how these are broken? Are they “broken”
only when using short timeframes? By the way, the option is –timeframe, not –time.
Thanks, th.
From: sam
[mailto:sam_backtester
AT
yahoo.fr]
Sent: Friday, July 04, 2008 11:47 AM
To: devel
AT
geniustrader.org
Subject: Re: [GT] Input validation in Tools.pm
|
Hi all.
Joao, are you able to do the same test with display_indicator.pl with I:STO
and with I:LinearRegression please ?
For me these two indicators are broken...
-------
./display_indicator.pl -time 1min --full I:STO 02052006|more
Calculating indicator %K Fast[5] ...
-------
Thx.
--- En date de : Ven 4.7.08, João Costa <joaocosta
AT
zonalivre.org>
a écrit :
De: João Costa
<joaocosta
AT
zonalivre.org>
Objet: Re: [GT] Input validation in Tools.pm
À: devel
AT
geniustrader.org
Date: Vendredi 4 Juillet 2008, 1h02
You need to put something in DB::timeframes_available
which GT won't recognize to reproduce this.
Try :
-------------------------------------------------------------------
DB::timeframes_available 30sec,day
-------------------------------------------------------------------
Then ask for some intraday data larger than 30 seconds, ie:
-------------------------------------------------------------------
display_indicator.pl --timeframe=hour I:Prices EURUSD
-------------------------------------------------------------------
All my patch does is to make sure that the timeframe names the user created
in the config file are valid,
and if they are not, give the user a list of possible valid names.
I'm using the code in trunk, not any of the exp branches.
|
Envoyé
avec Yahoo!
Mail.
Une boite mail plus intelligente.
|