Bucket of trades

[casebefx]

Hi !

I think there is some bug in Bucket of Trades.
I made strategy that opens trades on sum of lots bucket of trades. I have comments on the chart and I see value lots.
But on the begininng of strategy my comments shows value 2147483647 and strategy opens maximum lot for balance (for example 4.8 for 1000 USD). I think that default value for no existing bucket should be 0 no 2147483647.

I use strategy on offline chart (renko)

Could you check this option.

Best regards
Radek

[fxDreema]

I use 2147483647, also known as EMPTY_VALUE normally on purpose. The reason is that "Condition" does not pass if one of its sides equals to this value. This simplifies things. If you have "Condition" block and inside you have something (indicator, object...) that does not exists, then there is no reason for this block to pass. This is the idea. But maybe the idea is not very good for Buckets. Can you give me some small example (not your actual project, it contains many blocks and I'm lazy to investigate it) that shows your idea?

[casebefx]

Here is my strategy.

example:

if condition is true for BUY ,strategy should open 0.10 for BUY. But it opens 0.10 lot and big lot for maximum balance (for example 4.8 lots)
It shouldn't be becouse sell trade do not exist yet and bucket for red is zero.

https://fxdreema.com/shared/IIczjRcye

[fxDreema]

I don't know why people prefer to connect blocks like this. The idea of these "Bucket" blocks is to:

1. Select some group of trades. Because the term "Group" is used somewhere else, I decided to use the word "Bucket".
2. After you have those trades selected, get some value out of them - their profit, count, whatever.

And the idea is that 2) **must **happen after 1). But for some reason if there are blocks that must run in certain order, people don't connect them in any order. Insted, probably because it looks more pretty, they connect blocks in this parallel fashion. When blocks are connected like this, then their numbers matter and this is the problem.

I don't want to turn the value from EMPTY_VALUE to 0 only because of this example. As I said, there is a reason why I use EMPTY_VALUE. What I can do is to turn EMPTY_VALUE to the minimum lot size in the functions that calculate lot sized. Because 0 is nothing, but EMPTY_VALUE also represents nothingness, although it's value is a huge positive number