"Phoenix - FAQ, Stable, User support -Read Post #1" - Page 3

cdysthe · #21 (**permalink**) 11-23-2006, 03:21 PM

Quote:

Originally Posted by Ducati

My optimization is not working. I have followed the directions, and it looks like it is optimizing wih with 10/10 in the corner, and it takes longer than normal, but the optimization graph and results are always blank. Am I missing something?

I have noticed this if I try to optimize to many parameters at the same time. I take a few related ones, do those, then save. Then another few, and so on.

Ducati · #22 (**permalink**) 11-23-2006, 03:29 PM

Quote:

Originally Posted by cdysthe

I have noticed this if I try to optimize to many parameters at the same time. I take a few related ones, do those, then save. Then another few, and so on.

I just tried two and same results.

Also, I backtested on Alpari and on FXDD both with Alparis data and I get totally different results with the same settings. This is so frustrating.

Wackena · #23 (**permalink**) 11-23-2006, 03:29 PM

Quote:

Originally Posted by Ducati

My optimization is not working. I have followed the directions, and it looks like it is optimizing wih with 10/10 in the corner, and it takes longer than normal, but the optimization graph and results are always blank. Am I missing something?

Ducati,
No results means the settings you tested produced no orders or no profits. If you look in Journal, you see that the 10 scans were discarded.

Make sure you have UsePrefs=false and values in all required variable inputs in Experts Properties. Then check mark in box before variable name and values in start, step, end of each variable you want to optimize.

Wackiena

Wackena

Ducati · #24 (**permalink**) 11-23-2006, 03:47 PM

It was having too many consecutive wins according to the journals. The Optimization inputs were all selected. Thanks guys.

Ducati · #25 (**permalink**) 11-23-2006, 03:51 PM

Oh, nope. Still not working. Says all have been discarded as insignificant. WTF?

Edit: Ok, I seem to have some parameters work and others not. This program to so quirky.

Anyone know why I have majorly different results on backtesting from different brokers, but with the same data?

francoc30 · #26 (**permalink**) 11-24-2006, 04:05 AM

I am back testing v5.6.04 on 4 pairs. There are tons of "orderModify error #130" The EA ran to the end of the test period uninterrpted. Not sure what caused this #130 error. Anyone figured this out?
Francoc30

bertbin · #27 (**permalink**) 11-24-2006, 12:17 PM

Quote:

Originally Posted by francoc30

I am back testing v5.6.04 on 4 pairs. There are tons of "orderModify error #130" The EA ran to the end of the test period uninterrpted. Not sure what caused this #130 error. Anyone figured this out?
Francoc30

Had same "problem"... Asked two days ago... Nobody answer me... Perhaps nobody knows and nobody cares...

Seems that all our "Big Thinkers" are sleeeeeeeeeping after this big rally day..

Well It's seems that New Digital is our Administrator... Good.

NEW DIGITAL can you answer that ???

Thanks a lot and nice WE

bertbin · #28 (**permalink**) 11-25-2006, 12:20 AM

AAAAAAAAAAAAHHHHHHHHHHHHHHHHHHH

Somebody knows something about "Error130 " ????????????????

Thanks !

daraknor · #29 (**permalink**) 11-25-2006, 01:25 AM

Error 130 is an attempt to set the stoploss too close to the current price. I the code changes are in dialog on the programming forum, I will release them this weekend. Mode1 should not have this error, since it isn't moving the SL around.

francoc30 · #30 (**permalink**) 11-25-2006, 11:17 AM

Thanks, Daraknor. Good to know you are taking care of the house.
Francoc30

Quote:

Originally Posted by daraknor

Error 130 is an attempt to set the stoploss too close to the current price. I the code changes are in dialog on the programming forum, I will release them this weekend. Mode1 should not have this error, since it isn't moving the SL around.