Stoploss not put in place

• 12/29/2023 at 4:20 PM #225817
  ashehzi

  Thanks @GraHal.

  I can give it a try by removing NOT LONGONMARKET/SHORTONMARKET/ONMARKET to see the behaviour as I don’t take more than one trade at a time on this system. I’ve already in place Defparam CumulateOrders = False.

  @PeterSt, sure, I’ve attached with all columns included. The issue is not that. You can clearly see 3 rows for 1h algo and 2 rows for 30mins. The issue I was explaining earlier was that not all stops and limits are being placed. I cannot go lower than 30 mins timeframe for this algo because of limitation of 10k for PRELOADBARS. I would 15m action with PRELOADBARS supporting 20/30k but it is what it is. I understand more PRELOADBARS means bigger memory footprint for the program on PRT servers but why not? I wonder what was the other logic to limit PRELOADBARS to 10k.

  1 user thanked author for this post.

  GraHal

  

  ashehzi

  Participant

  Topics: 29

  Replies: 88

  Been thanked: 9 times
  12/30/2023 at 11:24 AM #225821
  JS

  You say you can’t take a higher time frame than 30 minutes with the maximum PreLoadBars (10,000)…

  So, you use an algo/indicator that looks back about 1 year (10,000*30min) in history…?

  

  JS

  Participant

  Topics: 26

  Replies: 1704

  Been thanked: 769 times
  12/30/2023 at 3:58 PM #225826
  ashehzi

  Yes it is quite obvious. Different algos different methods, some run on short tf, some on higher. If you want to use higher timeframe averages or similar, then you need longer time frame data. Lesser trades but greater reward.

  

  ashehzi

  Participant

  Topics: 29

  Replies: 88

  Been thanked: 9 times
  12/30/2023 at 5:17 PM #225829
  JS

  Yes, that’s clear… only an Average[10000](Close) (or similar) on a 30 minute time frame is a bit more unusual…but indeed possible…

  

  JS

  Participant

  Topics: 26

  Replies: 1704

  Been thanked: 769 times
  01/04/2024 at 8:55 PM #225969
  ashehzi

  For the initial issue of no stop loss / target profit set, I think I might have found the issue.

  IF NOT LONGONMARKET AND LongCondition THEN BUY 1.0 CONTRACTS AT myLevel limit SET TARGET PLOSS lossDistance SET TARGET PPROFIT profDistance ENDIF

  1 2 3 4 5

  IF NOT LONGONMARKET AND LongCondition THEN BUY 1.0 CONTRACTS AT myLevel limit SET TARGET PLOSS lossDistance SET TARGET PPROFIT profDistance ENDIF

  For the algo using above code, I’ve following setting in place:

  1. Max Position: 1 Amount/Pt
  2. Guaranteed stop: No
  3. Readjust stops: Yes

  In my open positions window, I noticed the following (see attached):

  Under limit, it was showing Caution symbol and related info was:

  1. Current Position: 1
  2. Total qty of targets: -2
  3. Total qty of stop loss: 0

  The total quantity of your target orders exceeds your position if executed, these orders could lead to opening a new position n opposite direction.

  Now, I am wondering, if I change “SET TARGET PLOSS lossDistance” to “SET STOP PLOSS lossDistance”, will it resolve the issue completely? What am I missing here?

   

   

  

  ashehzi

  Participant

  Topics: 29

  Replies: 88

  Been thanked: 9 times
  01/04/2024 at 9:09 PM #225972
  GraHal

  Wim wrote:

  But those who are nevertheless tempted to use a set target loss statement, should NEVER launch it simultaneously with the order entry (buy, sellshort), be it at market or pending. This one is meant to be launched once in real trouble, when loss is already BIGGER than the distance supplied with the set target loss.

  ashehzi you are doing what it says NOT to do in bold in above text.

  ashehzi wrote:

  if I change “SET TARGET PLOSS lossDistance” to “SET STOP PLOSS lossDistance”, will it resolve the issue completely?

  Yes try above and let us know.

  1 user thanked author for this post.

  ashehzi

  

  GraHal

  Participant

  Topics: 211

  Replies: 8775

  Been thanked: 2180 times
  01/04/2024 at 11:25 PM #225974
  ashehzi

  Yes that is old code and was still running on one of the demos, found the issue and thought to share for the benefit of others. I’ve mostly changed the code to set stop.

  1 user thanked author for this post.

  GraHal

  

  ashehzi

  Participant

  Topics: 29

  Replies: 88

  Been thanked: 9 times
• Author
  Posts