Blame the manual

Posted By: krial057

Blame the manual - 04/28/15 18:13

Hey jcl,

I just got started learning about automated trading. I used 3dgs and because it shares the same forum I got interested about it and started reading the manual. I think I found some mistakes in the manual and wanted to post them here(didn't know where else smirk )

In "Zorro and the Brokers" -> "Observing your VPS trade status" -> last point: "the public IP address of your server - for instance, bei entering 98.765.43.12\Z12.htm in your browser's address field." -> "bei" should be "by"

In "Workshop 4" -> After "We're now going to analyze the code line by line" you cite the code twice, but with other values than in the initial code. "vars Trend = series(LowPass(Price,1000));" should be "vars Trend = series(LowPass(Price,500));"

Otherwise a really nice manual! Really easy to understand even for people that never had something to do with trading(like me).

I'm currently playing around with the basics, hopefully I can develop some own strategies on my own in the near future laugh

kind regards,

Alain

P.S: should we all continue posting into this thread when finding other mistakes or will you create a new Forum like you did for the 3dgs community?
Posted By: jcl

Re: Blame the manual - 04/29/15 14:49

Thanks! Yes, please continue to post any mistakes that you find.
Posted By: GPEngine

Re: Blame the manual - 04/30/15 06:06

Please proofread this page http://zorro-trader.com/manual/en/stop.htm

It says
Quote:
Entry
Enter the trade only when the price reaches a certain value at the next bar (default = 0 = enter at market). The value can be given either directly as an Ask price, or as a distance to the current close price. A positive price or distance constitutes an entry stop, a negative price or distance an entry limit. An entry limit buys when the price is at or worse than the limit; it increases the profit of the trade as it buys at a better price. An entry stop buys when the price is at or better than the limit; it reduces the profit, but enters only when the price moved in favourable direction, and thus acts as an additional trade filter. If the entry price is not reached within the allowed time period (set through EntryTime), the trade is cancelled and a "Missed Entry" message is printed to the log file.

The emphasized fragments are opposite to statements of those that appear here and here.
Posted By: jcl

Re: Blame the manual - 04/30/15 11:08

How so?
Posted By: GPEngine

Re: Blame the manual - 04/30/15 16:22

For one thing,
You say "An entry limit buys when the price is at or worse than the limit"
They say "Limit Entry orders ... enter the market at a more favorable price."
Posted By: jcl

Re: Blame the manual - 04/30/15 16:28

Ah, I see. "Worse" means that the price went down when your trade needs it to rise. The other website describes the same price move as "favorable" because it happened when the trade was not yet entered. Both is not wrong, but indeed confusing and I'll try to make this more clear in the manual.
Posted By: DdlV

Re: Blame the manual - 05/01/15 14:11

Hi jcl. OK, I'll throw in a couple of minor things... laugh

On the Indicators page, TrueRange is out of alphabetical order. Also, the link to TrueRange in ATR seems to link to the description, not the header.

On the Trading page, the Progress Bar is described as "The left segment of the Progress Bar indicates the closed profit of the strategy since starting it, the right segment indicates the total profit or loss of all open trades (including phantom trades). When the right segment is green, your trades are in the profit zone; when the left segment is green, your account is in the profit zone. Otherwise the segment is red." A recent Demo strategy did 1 trade for $.64 profit. With that 1 trade closed and no open trades, the Progress Bar was left ~2/3 green and right ~1/3 red. Where did the red come from? With no open trades, shouldn't the right side have been 0, therefore non-existent, and hence the whole bar green?

Thanks.
Posted By: GPEngine

Re: Blame the manual - 05/01/15 15:42

Re: Entry
Some illustrations would really help here. There are at least 4 scenarios.
Entry is negative, next bar open is above |Entry|.
Entry is negative, next bar open is below |Entry|.
Entry is positive, next bar open is above |Entry|.
Entry is positive, next bar open is below |Entry|.

I have tried making zooming in to my plot. I have tried poring through the log. In complex cases, I have a hard time understanding what is happening, especially since in practice only entered trades are plotted. Missed entries, irrelevant stops, etc., are not plotted. Can you add visualizations at some level?
Posted By: DdlV

Re: Blame the manual - 05/02/15 02:43

Hi jcl. How about an update of the Testing page to reflect the current result window display: <nnn> <mmm> <www>/<lll>. What are the <nnn> and <mmm>?
Posted By: jcl

Re: Blame the manual - 05/04/15 10:59

It's the current balance and the value of the open trades - that was indeed missing in the manual.
Posted By: Mithrandir77

Re: Blame the manual - 05/04/15 15:23

Not sure if it is a mistake but in the manual it says for the DTREE method "The signals should be in the -100..100 range for best precision." , my question is, shouldn't it be the same for PERCEPTRON -and PATTERN maybe?- because according to what I read about neural networks, inputs should be normalized.
Posted By: jcl

Re: Blame the manual - 05/08/15 11:48

PERCEPTRON and PATTERN do not need normalized data. The perceptron is solved with a normal equation, not with gradient descent. Neural networks that use gradient descent or similar backprop algorithms would indeed require normalized, balanced data.
Posted By: GPEngine

Re: Blame the manual - 05/18/15 06:48

Thank you for carefully annotating many indicators with the warning, "The function internally creates series and thus must be called in a fixed order in the script." This helps me avoid Error 041: Inconsistent series calls.

Here are a few series-creating indicators/transformations which lack this annotation.

ZMA
RVI
Posted By: GPEngine

Re: Blame the manual - 05/18/15 15:35

Hurst.
Posted By: jcl

Re: Blame the manual - 05/22/15 08:34

Thanks! Will be corrected.
Posted By: GPEngine

Re: Blame the manual - 06/18/15 15:13

Quote:
TrailLock
'Locks' a percentage of the profit (default = 0 = no profit locking); has only an effect when Stop and Trail are set and the profit is above the trail distance. A stop loss is automatically placed at the given percentage of the current profit. Example: A long position is currently in profit by 10 pips. TrailLock = 80 would then place the stop loss at 8 pips above the entry price, thus locking 80% of the profit. TrailLock = 1 would set the stop loss at the entry price, i.e. at break even as soon as the profit reaches the Trail value. Using TrailLock is in most cases preferable to setting a profit target.
So, which is it? Is TrailLock supposed to be a percentage [0,100] or a fraction [0,1]?
Posted By: DdlV

Re: Blame the manual - 06/18/15 16:04

Hi GPEngine. From my experience so far, a percentage.

HTH.
Posted By: jcl

Re: Blame the manual - 06/19/15 10:28

Probably the "1" was misguiding, but any low number greater than zero would do here.
Posted By: DdlV

Re: Blame the manual - 06/19/15 12:51

Thanks jcl. This has spawned some other thoughts:

I gather, then, that 1 isn't specifically called out in the code - it's just that 1% (or other small %) of the profit normally calculates close enough to 0 that the result is the stop being at entry?

Is this also taking into account Spread, etc.? I.e., in the example of 10 pips, that's 10 pips after costs, yes? And the TrailLock stop is placed at entry+costs+8pips?

Also, is TrailLock a one-time thing or is it re-evaluated at every tick/bar? In the example, if profit subsequently increased to 20 pips, would the TrailLock stop be moved up to 16 pips?

Thanks.

P.S. - Does it work for TrailLock >100? Can I "lock" >100% of my profit?! laugh
Posted By: jcl

Re: Blame the manual - 06/19/15 13:51

Yes, it's 1% in the example, and spread is taken into account. Slippage not, as it is determined only in hindsight. TrailLock is re-evaluated at every tick, like all exit parameters.

As to locking more than 100% profit, well it is not easy, but we're working on it laugh.
Posted By: Sphin

Re: Blame the manual - 03/20/16 23:02

http://www.zorro-trader.com/manual/en/rbridge.htm:

Rd("rout",vecOut,5); // read it back

Wouldn't it mean Rv instead of Rd?
Posted By: DdlV

Re: Blame the manual - 03/22/16 04:09

The manual's Data Export / Import page says Assets.csv "is updated on every connection to the broker with the current parameters of all assets contained in the script". However, it appears Assets.csv is in fact not updated on connection to the broker, but rather when the script ends. For example, if you Trade a script, Assets.csv appears to be updated only when you Stop.
Posted By: jcl

Re: Blame the manual - 03/22/16 16:19

Thanks, the Rd was indeed wrong and I'll also make the updating more clear.
Posted By: DdlV

Re: Blame the manual - 05/12/16 21:24

Hi jcl. This is not the manual per se, but the Download page: The 2002-2008 History is needed for Z7, at least as of 1.44.
Posted By: DdlV

Re: Blame the manual - 05/18/16 12:30

Hi jcl. The COMMA flag is missing from the Mode flags page.
Posted By: jcl

Re: Blame the manual - 05/19/16 11:13

Not missing, but removed since it's a Zorro.ini parameter.
Posted By: DdlV

Re: Blame the manual - 05/19/16 13:29

Then The Z Systems page should be updated to include it & the link on the Data Export / Import page should be updated. laugh
Posted By: dr_panther

Re: Blame the manual - 09/12/16 22:07

The function dow states the days of the week are like that
Day of week of the given bar, MONDAY (1), TUESDAY (2) ... SUNDAY (7).

But actually the weeks starts with
SUNDAY(1), MONDAY(2)....

Code:
#include <profile.c>
 
function run()
{
	 
	set(LOGFILE);
	BarPeriod =5;
 
	static int cur_day = 0  ;
 	 
 	if ( ldow(ET,0) != cur_day){ 
	    cur_day = ldow(ET,0);
	 
 		print (TO_LOG,"ldow() %d", ldow(ET,0));
  	} 
}

Posted By: jcl

Re: Blame the manual - 09/13/16 14:24

This was in fact not a wrong manual, but a wrong time zone - the same bug that you already had in the dayHigh calculation. It is supposedly fixed in the latest Zorro 1.50.4.
Posted By: dr_panther

Re: Blame the manual - 09/13/16 15:27

that is correct now, thank you.
Posted By: fsgi

Re: Blame the manual - 10/23/16 13:54

Dear Zorro Team,

Please note that in the online manual the link to "putvar, getvar" is broken. It is even difficult to "guess" it.

Thank you

fs.
Posted By: jcl

Re: Blame the manual - 10/24/16 14:48

Thanks, this will be fixed.
Posted By: dr_panther

Re: Blame the manual - 10/28/16 11:47

also broken :
http://www.zorro-trader.com/manual/en/cdf.htm
http://www.zorro-trader.com/manual/en/window.htm
Posted By: dr_panther

Re: Blame the manual - 10/30/16 18:39

jcl, would it be a hard think for you to add a search function for the manual, I think a very simple google search should do it.

https://cse.google.com/cse/create/new
Posted By: Sphin

Re: Blame the manual - 10/30/16 21:57

Workaround: if you click on the help-button of your Zorro the manual opens as a searchable windows help file.
Posted By: jcl

Re: Blame the manual - 10/31/16 11:10

Use normally your own manual. The online manual is more intended for preview and beta testers. It changes often and the correctness of links is not guaranteed. Still, please post if you find a missing page that was not yet uploaded or updated.
Posted By: pcz

Re: Blame the manual - 11/09/16 15:03

In the offline version the Volatility function is described as taking 3 arguments while its definition is actually:
Code:
Volatility(vars Data, int TimePeriod): var


(Zorro 1.51)
Posted By: jcl

Re: Blame the manual - 11/10/16 09:20

Thanks. This was due to options implementation and will be corrected for the release.
Posted By: DdlV

Re: Blame the manual - 11/12/16 20:05

Hi jcl,

Have Tested 1.50 Z3 with default 50/10 to verify results vs. manual in preparation for implementing this weekend & have noticed a couple of discrepancies between the manual and my Test:

Avg trade duration: Manual says 2 weeks; my Test says 7 days = 1 week.

Profit factor: Manual says ~1.1%; my Test says 1.75.

All the other values seem to match OK.

Regards.
© 2024 lite-C Forums