Stochastic K and D lines

• 05/05/2018 at 11:17 AM #69818
  Juan Salas

  Hi all,

  I have some problem coding the stochastic. I have set the Stochastic to (79,3,4) in the indicators section, but when it come to coding only shows two parameters: Stochastic [79,3]. I would like to create a condition when %K crosses over %D or viceversa, but I don’t see it.

  I have reviewed the library in search of similar strategies with stochastic but nothing so far.

  Any suggestions?

  Thanks so much in advance.

  Juan

  

  Juan Salas

  Participant

  Topics: 39

  Replies: 246

  Been thanked: 63 times
  05/05/2018 at 12:35 PM #69827
  Juan Salas

  I think i got it. I found an old result from Nicolas in the Forums.

  K = stochastic[14,3] D = average[4](K) RETURN K, D

  1 2 3 4

  K = stochastic[14,3] D = average[4](K)   RETURN K, D

  Thanks anyway,

  Juan

  

  Juan Salas

  Participant

  Topics: 39

  Replies: 246

  Been thanked: 63 times
  02/24/2019 at 11:34 PM #92211
  tdisciplinet

  Did you manage to write the correct screener code for the stochastic crossover?

   

  If you did would you be able share it please?

   

  Thank you

  

  tdisciplinet

  Participant

  Topics: 1

  Replies: 1

  Been thanked: 0 times
  02/25/2019 at 1:27 AM #92218
  robertogozzi

  tdisciplinet wrote:

  Did you manage to write the correct screener code for the stochastic crossover?
  If you did would you be able share it please?
  Thank you

  Juan Salas‘s code is correct, to code a crossing just write:

  Croosover/under

  CrossOver = K crosses over D CrossUnder = K crosses under D

  1 2	CrossOver  = K crosses over D CrossUnder = K crosses under D

  If you search in the library for a Stochastic screener you’ll find some.

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 17826

  Been thanked: 4461 times
  02/25/2019 at 10:54 AM #92235
  Juan Salas

  tdisciplinet wrote:

  Did you manage to write the correct screener code for the stochastic crossover?

  If you did would you be able share it please?

  Thank you

  Hi, disciplinet,

  Roberto is right. I am sending you a piece of code similar to what Roberto sent:

  // Indicators /////////////////////// stoch76K= Stochastic[76,3] long50=stoch76K crosses over 50 // Entrada en largo normal al cruzar al alza 50 long80=stoch76K crosses over 80 // Reentrada en largo en >80 short50=stoch76K crosses under 50 // Entrada en corto normal al cruzar a la baja 50 short20=stoch76K crosses under 20 // Reentrada en corto en <20 // Estocastico lento D76 = average[4](stoch76K) // D stoch76K= Stochastic[76,3] // K crucelentoalza=stoch76K crosses over D76 crucelentobaja=stoch76K crosses under D76 // Estocastico rapido D8 = average[3](stoch8K) // D stoch8K= Stochastic[8,3] // K crucerapidoalza=stoch8K crosses over D8 crucerapidobaja=stoch8K crosses under D8

  1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

  // Indicators /////////////////////// stoch76K= Stochastic[76,3] long50=stoch76K crosses over 50 // Entrada en largo normal al cruzar al alza 50 long80=stoch76K crosses over 80 // Reentrada en largo en >80 short50=stoch76K crosses under 50 // Entrada en corto normal al cruzar a la baja 50 short20=stoch76K crosses under 20 // Reentrada en corto en <20   // Estocastico lento D76 = average[4](stoch76K) // D stoch76K= Stochastic[76,3] // K crucelentoalza=stoch76K crosses over D76 crucelentobaja=stoch76K crosses under D76   // Estocastico rapido D8 = average[3](stoch8K) // D stoch8K= Stochastic[8,3] // K crucerapidoalza=stoch8K crosses over D8 crucerapidobaja=stoch8K crosses under D8

  I hope it can help you

  1 user thanked author for this post.

  robertogozzi

  

  Juan Salas

  Participant

  Topics: 39

  Replies: 246

  Been thanked: 63 times
  09/24/2019 at 5:57 PM #108375
  s00071609

  I am have this code for stochastic in hourly TF. Pro Order should be placing order when, %K is above the %D (ie. %K>%D) and value of %D should be 32 and 75 before an order is placed. This is a bullish condition

  But I have multiple orders being placed even when stochastic is bearish. All conditions should be true to open a buy position ie c2 and c3 and c4 should all be true..

  Why is this dependency occurring with Pro Order Tests?

   

  I have attached an image that clearly shows the stochastic does not meet the conditions.

  timeframe(1 Hour, updateonclose) indicator3 = Stochastic[5,3](close) indicator4 = Average[3](indicator3) c2 = (indicator3[3] > indicator4) indicator5 = Average[3](Stochastic[5,3](close)) c3 = (indicator5 > 32) indicator6 = Average[3](Stochastic[5,3](close)) c4 = (indicator5 < 75)

  1 2 3 4 5 6 7 8

  timeframe(1 Hour, updateonclose) indicator3 = Stochastic[5,3](close) indicator4 = Average[3](indicator3) c2 = (indicator3[3] > indicator4) indicator5 = Average[3](Stochastic[5,3](close)) c3 = (indicator5 > 32) indicator6 = Average[3](Stochastic[5,3](close)) c4 = (indicator5 < 75)

  

  s00071609

  Participant

  Topics: 9

  Replies: 133

  Been thanked: 16 times
  09/24/2019 at 6:22 PM #108377
  robertogozzi

  Why line 4 refers to the 3rd previous candle?

  This could be the logical error.

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 17826

  Been thanked: 4461 times
  09/24/2019 at 6:41 PM #108380
  s00071609

  Ok thanks for pointing that out – that was an error. I corrected it, it improved by removing some of these orders, but there are still some that should not be there.

   

  If you see the screenshot below, 2 orders are placed in same area, the first one is placed when the stochastic is clearly bearish.

  How can i fix this? I want it to place orders when stochastic is bullish only.

  timeframe(1 Hour, updateonclose) indicator3 = Stochastic[5,3](close) indicator4 = Average[3](indicator3) c2 = (indicator3 > indicator4) indicator5 = Average[3](Stochastic[5,3](close)) c3 = (indicator5 > 25) indicator6 = Average[3](Stochastic[5,3](close)) c4 = (indicator6 < 35)

  1 2 3 4 5 6 7 8

  timeframe(1 Hour, updateonclose) indicator3 = Stochastic[5,3](close) indicator4 = Average[3](indicator3) c2 = (indicator3 > indicator4) indicator5 = Average[3](Stochastic[5,3](close)) c3 = (indicator5 > 25) indicator6 = Average[3](Stochastic[5,3](close)) c4 = (indicator6 < 35)

   

  

  s00071609

  Participant

  Topics: 9

  Replies: 133

  Been thanked: 16 times
  09/24/2019 at 7:04 PM #108382
  robertogozzi

  Without the complete code it is impossible to tell, it is likely conditions are not linked with AND.

  Or if you use a smaller default TF a trade could be entered while conditions have changed because variables are updated only when the 1-hour bar closes.

  If you need further help you should post your code to enable readers to replicate your trades, also specifying instrument and default TF used.

   

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 17826

  Been thanked: 4461 times
  09/24/2019 at 8:12 PM #108386
  s00071609

  Here is the code, its daily and hourly TF being used,

  // Definition of code parameters DEFPARAM CumulateOrders = False // Cumulating positions deactivated // Conditions to enter long positions timeframe(Daily) indicator1 = Stochastic[5,3] indicator2 = Average[3](indicator1) indicator0 = Average[3](Stochastic[5,3]) c1 = (indicator1 > indicator2) c0 = (indicator0 < 70) timeframe(1 Hour, updateonclose) indicator3 = Stochastic[5,3](close) indicator4 = Average[3](indicator3) c2 = (indicator3 > indicator4) indicator5 = Average[3](Stochastic[5,3](close)) c3 = (indicator5 > 10) indicator6 = Average[3](Stochastic[5,3](close)) c4 = (indicator6 < 40) LL = lowest[6](low) - 2*pointsize SL = close [0] - LL //BARHIGH = High REM Money Management Capital = 5000 Risk = 0.01 //Stoploss = 5 //StopLoss = abs((BARHIGH - SL)/pointvalue) // Could be our variable X REM Calculate contracts equity = Capital + StrategyProfit maxrisk = round(equity*Risk) PositionSize = abs(((maxrisk/SL)/PointValue)*pipsize) IF c0 AND c1 AND c2 AND c3 AND c4 THEN Buy Positionsize CONTRACT AT MARKET set stop Loss SL Set target profit SL*6 ENDIF

  1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41

  // Definition of code parameters DEFPARAM CumulateOrders = False // Cumulating positions deactivated   // Conditions to enter long positions timeframe(Daily) indicator1 = Stochastic[5,3] indicator2 = Average[3](indicator1) indicator0 = Average[3](Stochastic[5,3]) c1 = (indicator1 > indicator2) c0 = (indicator0 < 70)     timeframe(1 Hour, updateonclose) indicator3 = Stochastic[5,3](close) indicator4 = Average[3](indicator3) c2 = (indicator3 > indicator4) indicator5 = Average[3](Stochastic[5,3](close)) c3 = (indicator5 > 10) indicator6 = Average[3](Stochastic[5,3](close)) c4 = (indicator6 < 40) LL = lowest[6](low) - 2*pointsize SL = close [0] - LL //BARHIGH = High   REM Money Management Capital = 5000 Risk = 0.01 //Stoploss = 5 //StopLoss = abs((BARHIGH - SL)/pointvalue) // Could be our variable X REM Calculate contracts equity = Capital + StrategyProfit maxrisk = round(equity*Risk) PositionSize = abs(((maxrisk/SL)/PointValue)*pipsize)     IF c0 AND c1 AND c2 AND c3 AND c4 THEN Buy Positionsize CONTRACT AT MARKET set stop Loss SL Set target profit SL*6 ENDIF

   

  

  s00071609

  Participant

  Topics: 9

  Replies: 133

  Been thanked: 16 times
  09/24/2019 at 9:04 PM #108390
  robertogozzi

  What TF did you take that pic from?

  When you look at the daily chart keep in mind that previous daily bars only show the pic at closing time, while you did not use updateonclose thus at runtime values can be differrnt from hour to hour.

   

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 17826

  Been thanked: 4461 times
  09/24/2019 at 9:09 PM #108391
  s00071609

  I took that snap shot in Hourly TF. Daily TF seems to be working fine

  Even if daily is not using update on close, hourly conditions should still be respected isn’t it?

  

  s00071609

  Participant

  Topics: 9

  Replies: 133

  Been thanked: 16 times
  09/24/2019 at 9:23 PM #108392
  robertogozzi

  What time and instrument were those wrong trades?

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 17826

  Been thanked: 4461 times
  09/24/2019 at 9:28 PM #108393
  s00071609

  20 Aug to 31 Aug – Instrument is Spot Gold

  

  s00071609

  Participant

  Topics: 9

  Replies: 133

  Been thanked: 16 times
  09/24/2019 at 11:29 PM #108402
  robertogozzi

  For Spot GOLD I have no trades opened from Aug.20th through Aug 31st.

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 17826

  Been thanked: 4461 times
• Author
  Posts