Dears,

please help me to fix following trouble:
- the attached strategy should produce max one pending position per bar
- but it produces another pending order once the previous pending order becomes executed

Appreciate,
Antony

Hi,

It does so cause you said so !

Here is the guilty:


Once the pending order is executed it switches from the status "pending" to "executed" literally from "opened" state to "filled" thus no-more considered as a Pending order but as open position.
To apply your condition, you should use "All position" instead of pending Position and you'll have that done.

Cheers

Well, that is right, but we need NOT to be limited by amount of opened (filled) positions.
Sorry, I did not mentioned that before

Let me clarify:
- Pending positions considers only orders in placed status
- Open positions handles Filled orders
- All positions handles both: PENDING + OPENED <=> Placed and filled

When a position is CLOSED then the amount gets reset and the flow will go through.

.. but there can be more than one position opened (filled)
- so the new pending order will not be opened
- even it should be opened based on entry conditions
- thus the flow does not get through
- because allPositions will be greater or equal to ONE

Am I right?

Yes, this is right.


Is this is a new assumption to be considered into your strategy ?

Could you please provide a full description ?

Lets put it this way:

- the attached strategy produces entry signals based on simple condition (anytime indicator crossess xy = place pending order)
- so there can be unlimited amount of filled positions

to avoid that, the filter is:
- place only ONE pending order per candle
- also, each placed pending order has its expiration (the same time period as the timeFrame)

Again, big thanks

from your first post the problem is:


and the solution is:


Then the use of the filter with pending is okay !! once the pending order is filled and a new candle starts (meeting the entry conditions) an new order is placed.
I can't see where is the problem here ..sorry

please specify what is the proper OutputValues in your example
https://www.dukascopy.com/vfhelper/arti ... _locale=EN

???

Thanks!

Hi,

Get time unit is a block used to retrieve date and time data from a given input, the input should be indeed defined as time & Date type. In the setting area, you can select the data that you want to retrieve and the variable type is defined by default as integer but you can still use "Double" if needed.
I cannot guess what is expected from the strategy to do, I need a thorough description so that I can help you to do achieve your idea in a simple way.
I don't understand the use of Ontick start while I can see that you trade on hourly basis.
Let's start from the attached version, I've added a couple of filters in the beginning as the strategy was generating an error in your previous example. The error comes from the fact that an output is used in an IF block while it did not get attributed with a value yet.

PS: Your latest post is almost treating the same matter, let's sort this out first
Thanks

Hi Amine,

sorry for the potential duplicity of discussed problem. I was getting lost, that is why tried to put it all together and made a new topic. It looks as a good refresh to me.

Appreciate your long explanation, before I get through that, I tried your attached SellSide_V1.vfs, but it is not producing any pending order at all (on historical testing). It should be, right?

Antony

My suggestion is this:

- as far as this topic is more theoretic from my side, lets end up the discussion over here and move to topic called PENDING ORDER EXPIRATION TROUBLE II, because that is exactly the real case I need to figure out

What do you think?