Gamestudio Links
Zorro Links
Newest Posts
Trading Journey
by howardR. 04/24/24 20:04
M1 Oversampling
by Petra. 04/24/24 10:34
Zorro FIX plugin - Experimental
by flink. 04/21/24 07:12
Data from CSV not parsed correctly
by EternallyCurious. 04/20/24 21:39
Scripts not found
by juergen_wue. 04/20/24 18:51
zorro 64bit command line support
by 7th_zorro. 04/20/24 10:06
StartWeek not working as it should
by jcl. 04/20/24 08:38
folder management functions
by VoroneTZ. 04/17/24 06:52
AUM Magazine
Latest Screens
The Bible Game
A psychological thriller game
SHADOW (2014)
DEAD TASTE
Who's Online Now
2 registered members (AndrewAMD, howardR), 472 guests, and 7 spiders.
Key: Admin, Global Mod, Mod
Newest Members
Mega_Rod, EternallyCurious, howardR, 11honza11, ccorrea
19048 Registered Users
Previous Thread
Next Thread
Print Thread
Rate Thread
Page 1 of 4 1 2 3 4
Blame the manual #451111
04/28/15 18:13
04/28/15 18:13
Joined: Sep 2007
Posts: 101
Luxembourg
K
krial057 Offline OP
Member
krial057  Offline OP
Member
K

Joined: Sep 2007
Posts: 101
Luxembourg
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?

Re: Blame the manual [Re: krial057] #451166
04/29/15 14:49
04/29/15 14:49
Joined: Jul 2000
Posts: 27,982
Frankfurt
jcl Offline

Chief Engineer
jcl  Offline

Chief Engineer

Joined: Jul 2000
Posts: 27,982
Frankfurt
Thanks! Yes, please continue to post any mistakes that you find.

Re: Blame the manual [Re: jcl] #451212
04/30/15 06:06
04/30/15 06:06
Joined: Sep 2013
Posts: 504
California
G
GPEngine Offline
User
GPEngine  Offline
User
G

Joined: Sep 2013
Posts: 504
California
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.

Re: Blame the manual [Re: GPEngine] #451217
04/30/15 11:08
04/30/15 11:08
Joined: Jul 2000
Posts: 27,982
Frankfurt
jcl Offline

Chief Engineer
jcl  Offline

Chief Engineer

Joined: Jul 2000
Posts: 27,982
Frankfurt
How so?

Re: Blame the manual [Re: jcl] #451238
04/30/15 16:22
04/30/15 16:22
Joined: Sep 2013
Posts: 504
California
G
GPEngine Offline
User
GPEngine  Offline
User
G

Joined: Sep 2013
Posts: 504
California
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."

Re: Blame the manual [Re: GPEngine] #451239
04/30/15 16:28
04/30/15 16:28
Joined: Jul 2000
Posts: 27,982
Frankfurt
jcl Offline

Chief Engineer
jcl  Offline

Chief Engineer

Joined: Jul 2000
Posts: 27,982
Frankfurt
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.

Re: Blame the manual [Re: jcl] #451286
05/01/15 14:11
05/01/15 14:11
Joined: Jun 2013
Posts: 1,609
D
DdlV Offline
Serious User
DdlV  Offline
Serious User
D

Joined: Jun 2013
Posts: 1,609
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.

Re: Blame the manual [Re: DdlV] #451291
05/01/15 15:42
05/01/15 15:42
Joined: Sep 2013
Posts: 504
California
G
GPEngine Offline
User
GPEngine  Offline
User
G

Joined: Sep 2013
Posts: 504
California
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?

Re: Blame the manual [Re: GPEngine] #451310
05/02/15 02:43
05/02/15 02:43
Joined: Jun 2013
Posts: 1,609
D
DdlV Offline
Serious User
DdlV  Offline
Serious User
D

Joined: Jun 2013
Posts: 1,609
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>?

Re: Blame the manual [Re: DdlV] #451360
05/04/15 10:59
05/04/15 10:59
Joined: Jul 2000
Posts: 27,982
Frankfurt
jcl Offline

Chief Engineer
jcl  Offline

Chief Engineer

Joined: Jul 2000
Posts: 27,982
Frankfurt
It's the current balance and the value of the open trades - that was indeed missing in the manual.

Re: Blame the manual [Re: krial057] #451366
05/04/15 15:23
05/04/15 15:23
Joined: Nov 2013
Posts: 123
Mithrandir77 Offline
Member
Mithrandir77  Offline
Member

Joined: Nov 2013
Posts: 123
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.

Re: Blame the manual [Re: Mithrandir77] #451503
05/08/15 11:48
05/08/15 11:48
Joined: Jul 2000
Posts: 27,982
Frankfurt
jcl Offline

Chief Engineer
jcl  Offline

Chief Engineer

Joined: Jul 2000
Posts: 27,982
Frankfurt
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.

Re: Blame the manual [Re: jcl] #451727
05/18/15 06:48
05/18/15 06:48
Joined: Sep 2013
Posts: 504
California
G
GPEngine Offline
User
GPEngine  Offline
User
G

Joined: Sep 2013
Posts: 504
California
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

Re: Blame the manual [Re: GPEngine] #451732
05/18/15 15:35
05/18/15 15:35
Joined: Sep 2013
Posts: 504
California
G
GPEngine Offline
User
GPEngine  Offline
User
G

Joined: Sep 2013
Posts: 504
California
Hurst.

Re: Blame the manual [Re: GPEngine] #451812
05/22/15 08:34
05/22/15 08:34
Joined: Jul 2000
Posts: 27,982
Frankfurt
jcl Offline

Chief Engineer
jcl  Offline

Chief Engineer

Joined: Jul 2000
Posts: 27,982
Frankfurt
Thanks! Will be corrected.

Re: Blame the manual [Re: jcl] #452598
06/18/15 15:13
06/18/15 15:13
Joined: Sep 2013
Posts: 504
California
G
GPEngine Offline
User
GPEngine  Offline
User
G

Joined: Sep 2013
Posts: 504
California
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]?

Re: Blame the manual [Re: GPEngine] #452599
06/18/15 16:04
06/18/15 16:04
Joined: Jun 2013
Posts: 1,609
D
DdlV Offline
Serious User
DdlV  Offline
Serious User
D

Joined: Jun 2013
Posts: 1,609
Hi GPEngine. From my experience so far, a percentage.

HTH.

Re: Blame the manual [Re: DdlV] #452609
06/19/15 10:28
06/19/15 10:28
Joined: Jul 2000
Posts: 27,982
Frankfurt
jcl Offline

Chief Engineer
jcl  Offline

Chief Engineer

Joined: Jul 2000
Posts: 27,982
Frankfurt
Probably the "1" was misguiding, but any low number greater than zero would do here.

Re: Blame the manual [Re: jcl] #452615
06/19/15 12:51
06/19/15 12:51
Joined: Jun 2013
Posts: 1,609
D
DdlV Offline
Serious User
DdlV  Offline
Serious User
D

Joined: Jun 2013
Posts: 1,609
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

Re: Blame the manual [Re: DdlV] #452620
06/19/15 13:51
06/19/15 13:51
Joined: Jul 2000
Posts: 27,982
Frankfurt
jcl Offline

Chief Engineer
jcl  Offline

Chief Engineer

Joined: Jul 2000
Posts: 27,982
Frankfurt
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.

Re: Blame the manual [Re: jcl] #458561
03/20/16 23:02
03/20/16 23:02
Joined: Dec 2013
Posts: 568
Fuerth, DE
Sphin Offline
User
Sphin  Offline
User

Joined: Dec 2013
Posts: 568
Fuerth, DE
http://www.zorro-trader.com/manual/en/rbridge.htm:

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

Wouldn't it mean Rv instead of Rd?

Re: Blame the manual [Re: Sphin] #458603
03/22/16 04:09
03/22/16 04:09
Joined: Jun 2013
Posts: 1,609
D
DdlV Offline
Serious User
DdlV  Offline
Serious User
D

Joined: Jun 2013
Posts: 1,609
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.

Re: Blame the manual [Re: DdlV] #458637
03/22/16 16:19
03/22/16 16:19
Joined: Jul 2000
Posts: 27,982
Frankfurt
jcl Offline

Chief Engineer
jcl  Offline

Chief Engineer

Joined: Jul 2000
Posts: 27,982
Frankfurt
Thanks, the Rd was indeed wrong and I'll also make the updating more clear.

Re: Blame the manual [Re: jcl] #459381
05/12/16 21:24
05/12/16 21:24
Joined: Jun 2013
Posts: 1,609
D
DdlV Offline
Serious User
DdlV  Offline
Serious User
D

Joined: Jun 2013
Posts: 1,609
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.

Re: Blame the manual [Re: DdlV] #459431
05/18/16 12:30
05/18/16 12:30
Joined: Jun 2013
Posts: 1,609
D
DdlV Offline
Serious User
DdlV  Offline
Serious User
D

Joined: Jun 2013
Posts: 1,609
Hi jcl. The COMMA flag is missing from the Mode flags page.

Re: Blame the manual [Re: DdlV] #459437
05/19/16 11:13
05/19/16 11:13
Joined: Jul 2000
Posts: 27,982
Frankfurt
jcl Offline

Chief Engineer
jcl  Offline

Chief Engineer

Joined: Jul 2000
Posts: 27,982
Frankfurt
Not missing, but removed since it's a Zorro.ini parameter.

Re: Blame the manual [Re: jcl] #459438
05/19/16 13:29
05/19/16 13:29
Joined: Jun 2013
Posts: 1,609
D
DdlV Offline
Serious User
DdlV  Offline
Serious User
D

Joined: Jun 2013
Posts: 1,609
Then The Z Systems page should be updated to include it & the link on the Data Export / Import page should be updated. laugh

Re: Blame the manual [Re: DdlV] #462175
09/12/16 22:07
09/12/16 22:07
Joined: Aug 2016
Posts: 61
D
dr_panther Offline
Junior Member
dr_panther  Offline
Junior Member
D

Joined: Aug 2016
Posts: 61
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));
  	} 
}


Last edited by dr_panther; 09/12/16 22:15.
Re: Blame the manual [Re: dr_panther] #462194
09/13/16 14:24
09/13/16 14:24
Joined: Jul 2000
Posts: 27,982
Frankfurt
jcl Offline

Chief Engineer
jcl  Offline

Chief Engineer

Joined: Jul 2000
Posts: 27,982
Frankfurt
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.

Re: Blame the manual [Re: jcl] #462199
09/13/16 15:27
09/13/16 15:27
Joined: Aug 2016
Posts: 61
D
dr_panther Offline
Junior Member
dr_panther  Offline
Junior Member
D

Joined: Aug 2016
Posts: 61
that is correct now, thank you.

Re: Blame the manual [Re: dr_panther] #462730
10/23/16 13:54
10/23/16 13:54
Joined: Feb 2016
Posts: 15
Milan, Italy
F
fsgi Offline
Newbie
fsgi  Offline
Newbie
F

Joined: Feb 2016
Posts: 15
Milan, Italy
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.

Re: Blame the manual [Re: fsgi] #462743
10/24/16 14:48
10/24/16 14:48
Joined: Jul 2000
Posts: 27,982
Frankfurt
jcl Offline

Chief Engineer
jcl  Offline

Chief Engineer

Joined: Jul 2000
Posts: 27,982
Frankfurt
Thanks, this will be fixed.

Re: Blame the manual [Re: jcl] #462779
10/28/16 11:47
10/28/16 11:47
Joined: Aug 2016
Posts: 61
D
dr_panther Offline
Junior Member
dr_panther  Offline
Junior Member
D

Joined: Aug 2016
Posts: 61

Last edited by dr_panther; 10/28/16 13:11.
Re: Blame the manual [Re: dr_panther] #462820
10/30/16 18:39
10/30/16 18:39
Joined: Aug 2016
Posts: 61
D
dr_panther Offline
Junior Member
dr_panther  Offline
Junior Member
D

Joined: Aug 2016
Posts: 61
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

Re: Blame the manual [Re: dr_panther] #462822
10/30/16 21:57
10/30/16 21:57
Joined: Dec 2013
Posts: 568
Fuerth, DE
Sphin Offline
User
Sphin  Offline
User

Joined: Dec 2013
Posts: 568
Fuerth, DE
Workaround: if you click on the help-button of your Zorro the manual opens as a searchable windows help file.

Re: Blame the manual [Re: Sphin] #462835
10/31/16 11:10
10/31/16 11:10
Joined: Jul 2000
Posts: 27,982
Frankfurt
jcl Offline

Chief Engineer
jcl  Offline

Chief Engineer

Joined: Jul 2000
Posts: 27,982
Frankfurt
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.

Re: Blame the manual [Re: jcl] #462982
11/09/16 15:03
11/09/16 15:03
Joined: May 2016
Posts: 180
Prague
pcz Offline
Member
pcz  Offline
Member

Joined: May 2016
Posts: 180
Prague
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)

Re: Blame the manual [Re: pcz] #462995
11/10/16 09:20
11/10/16 09:20
Joined: Jul 2000
Posts: 27,982
Frankfurt
jcl Offline

Chief Engineer
jcl  Offline

Chief Engineer

Joined: Jul 2000
Posts: 27,982
Frankfurt
Thanks. This was due to options implementation and will be corrected for the release.

Re: Blame the manual [Re: jcl] #463064
11/12/16 20:05
11/12/16 20:05
Joined: Jun 2013
Posts: 1,609
D
DdlV Offline
Serious User
DdlV  Offline
Serious User
D

Joined: Jun 2013
Posts: 1,609
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.

Page 1 of 4 1 2 3 4

Moderated by  Petra 

Gamestudio download | chip programmers | Zorro platform | shop | Data Protection Policy

oP group Germany GmbH | Birkenstr. 25-27 | 63549 Ronneburg / Germany | info (at) opgroup.de

Powered by UBB.threads™ PHP Forum Software 7.7.1