paanoik@seznam.cz
22 Nov 2020, 02:10

RE:

Hi,

I don't get what do you mean, example what you want to achieve could help. Position can obviously has only one TP level. If it hit the level, position is closed. If you want tu change TP value, you can use method

ModifyPosition(position, SL, TP)

T.

paanoik@seznam.cz
21 Nov 2020, 12:51

yep, same here, already running optimization was working overnight, but since this morning, I can only run bots on active symbols (e.g. cryptos)

paanoik@seznam.cz
13 Jan 2018, 20:53

I think it has it's space here, as there are people who tests long term possitions (like days/weeks). In this case tick testing doesn't make any sense as it will only slow it down.

paanoik@seznam.cz
03 Jan 2018, 13:02

Thank you for feedback.

Is there any workaround for this? As margin differs for symbols, I would like to get leverage runtime calculate required margin and check available equity. However, I can see only Symbol.PreciseLeverage property which doesn't seem to be what I'm looking for.

T.

paanoik@seznam.cz
13 Dec 2017, 16:39

Hi Andrey,

1) Well, I must admit that every time I've change ticks to m1 in settings, I've ignored new spread part inputs .. shame on me. Will look into this more deeply. However, as I've quickchecked .. spread is dynamic and changes between 1 to 5 pips so static value cause m1 backtesting useless.

2) I did .. however as I didn't change default (1.00) spread, it works with same "invalid way" .. actually my discovery was like ... wth, did I really made 100K out of 1K in a year? Let optimize it and find nicer parameters .. ok, not 100K but 13M. :)

Anyway .. thanks for your feedback. This helped me a lot.

T.

paanoik@seznam.cz
13 Dec 2017, 16:20

OK, thank you.

I'll run analysis on history data and create some hardcoded trade hours based on this. Should be easy. I was just curious if not missing something.

T.