Error indicator negative entry or zero parameter

Tanou · Wed, 10 Mar 2021 08:32:02 +0000

Hello everyone! 😀 I hope you are well! I launched live a code yesterday and today it has been stopped with the message ” indicator negative entry or zero parameter” and I can’t find why and where could be the error… Could someone give me a hint? Thanks! 😀 //------------------------------------------------------------------------- // Code principal : PP4H V1 //------------------------------------------------------------------------- // Définition des paramètres du code // Cumul des positions désactivé DEFPARAM CumulateOrders = False DEFPARAM PRELOADBARS = 100000000 //************************************************************************ //Horaires de trading // Annule tous les ordres en attente et ferme toutes les positions à 0:00, puis empêche toute création d'ordre avant l'heure "FLATBEFORE". DEFPARAM FLATBEFORE = 090000 // Annule tous les ordres en attente et ferme toutes les positions à l'heure "FLATAFTER" DEFPARAM FLATAFTER = 173000 // Empêche le système de placer des ordres pour entrer sur le marché ou augmenter la taille d'une position avant l'heure spécifiée noEntryBeforeTime = 090500 timeEnterBefore = time >= noEntryBeforeTime // Empêche le système de placer des ordres pour entrer sur le marché ou augmenter la taille d'une position après l'heure spécifiée noEntryAfterTime = 125000 timeEnterAfter = time < noEntryAfterTime // Empêche le système de placer de nouveaux ordres sur les jours de la semaine spécifiés daysForbiddenEntry = OpenDayOfWeek = 5 OR OpenDayOfWeek = 0 //************************************************************************ // Calcul Points Pivots 4h Int = (OpenTime[1] < 010000 AND OpenTime > 010000) OR (OpenTime[1] < 050000 AND OpenTime > 050000) OR (OpenTime[1] < 090000 AND OpenTime > 090000) OR (OpenTime[1] < 130000 AND OpenTime > 130000) OR (OpenTime[1] < 170000 AND OpenTime > 170000) OR (OpenTime[1] < 210000 AND OpenTime > 210000) OR (Openday <> Openday[1] AND DayOfWeek < DayOfWeek[1]) IF (OpenTime Mod 40000 = 10000) OR Int THEN myLastHigh = myHigh myLastLow = myLow myLastClose = Close[1] myHigh = High myLow = Low Premierpassage=0 DebutOpen = Barindex ELSE myHigh = Max(myHigh, High) myLow = Min(myLow, Low) ENDIF PP = (myLastHigh + myLastLow + myLastClose) / 3 hh = highest[85](high) ll = lowest[85](low) if (hh-ll)<20 then Rang = 0 else Rang = 1 Endif BarresDepuisOpen = Barindex - DebutOpen HighSinceOpen = highest[BarresDepuisOpen](high) LowSinceOpen = lowest[BarresDepuisOpen](low) DiffHighSinceOpen = HighSinceOpen - pp DiffLowSinceOpen = pp - LowSinceOpen If DiffHighSinceOpen>25 or DiffLowSinceOpen>25 then Rang2 = 1 else Rang2 = 0 Endif // Conditions pour ouvrir une position acheteuse c1 = (close[1] CROSSES UNDER pp) IF c1 AND timeEnterBefore AND timeEnterAfter AND Premierpassage=0 AND not daysForbiddenEntry and Rang and Rang2 THEN BUY 1 CONTRACT AT MARKET Premierpassage=1 SET STOP pLOSS 60 ENDIF // Conditions pour ouvrir une position en vente à découvert c2 = (close[1] CROSSES OVER pp) IF c2 AND timeEnterBefore AND timeEnterAfter AND Premierpassage=0 AND not daysForbiddenEntry and Rang and Rang2 THEN SELLSHORT 1 CONTRACT AT MARKET Premierpassage=1 SET STOP pLOSS 50 ENDIF If time>=090500 and time<=125000 then If Premierpassage=0 and c1 or c2 then Premierpassage=1 endif Endif //************************************************************************ //trailing stop function trailingstartL = 21 //LONG trailing will start @trailinstart points profit trailingstartS = 21 //SHORT trailing will start @trailinstart points profit trailingstep = 11 //trailing step to move the "stoploss" breakeven = 0 //Activate or not the Brakeven breakevenlevel = 15 //Level of activation of the breakeven PointsToKeepBreakeven = 1 //reset the stoploss value IF NOT ONMARKET THEN newSL=0 BreakevenStop=0 ENDIF //manage long positions IF LONGONMARKET THEN //first move (breakeven) If Breakeven and BreakevenStop=0 then IF close-tradeprice(1)>=breakevenlevel*pipsize THEN BreakevenStop = tradeprice(1) + PointsToKeepBreakeven Endif Endif //first move trailing stop IF newSL=0 AND close-tradeprice(1)>=trailingstartL*pipsize THEN newSL = tradeprice(1)+trailingstep*pipsize ENDIF //next moves IF newSL>0 AND close-newSL>=trailingstep*pipsize THEN newSL = newSL+trailingstep*pipsize ENDIF ENDIF //manage short positions IF SHORTONMARKET THEN //first move (breakeven) If Breakeven and BreakevenStop=0 then IF tradeprice(1)-close>=breakevenlevel*pipsize THEN BreakevenStop = tradeprice(1) - PointsToKeepBreakeven Endif Endif //first move trailing stop IF newSL=0 AND tradeprice(1)-close>=trailingstartS*pipsize THEN newSL = tradeprice(1)-trailingstep*pipsize ENDIF //next moves IF newSL>0 AND newSL-close>=trailingstep*pipsize THEN newSL = newSL-trailingstep*pipsize ENDIF ENDIF //stop order to exit the positions with trailing stop IF newSL>0 THEN SELL AT newSL STOP EXITSHORT AT newSL STOP ENDIF //stop order to exit the positions with breakeven IF BreakevenStop>0 THEN SELL AT BreakevenStop STOP EXITSHORT AT BreakevenStop STOP ENDIF //************************************************************************

This topic has 17 replies, 4 voices, and was last updated 1 year ago by robertogozzi.

Viewing 3 posts - 16 through 18 (of 18 total)

← 1 2

09/03/2023 at 8:55 PM #220276

Hi,

True, there are differences, but these can possibly be overcome…

I myself am always struggling with dates and times and have experienced several times that unexpected situations occur…

When next Monday everything has to change to a new day, new week and a new month, I would be more surprised if you didn’t get an error message…

I made this proposal because this way is more “robust” and should not depend on 1 bar…

Participant

Topics: 27

Replies: 1810

Been thanked: 882 times

09/04/2023 at 8:05 AM #220290

jmf125

Not too sure how you can overcome the differences between <> and crosses over – under but in any cases the cause of the problem isn’t there.
As expected the system stopped this morning.

jmf125

Participant

Topics: 8

Replies: 111

Been thanked: 14 times

09/06/2023 at 9:25 AM #220394

robertogozzi

The line with the CROSSOVERS shows potential sources of error as the system has to compare the two prior values against the current value of PP.

You can replace the crossover with:

// c1 = (close[1] CROSSES UNDER pp)        //perhaps  c1 = (close[1] CROSSES UNDER pp[1])   ????

// replacement for the CROSSOVER (crossing under in this case)
c2 = (close[2] > pp) AND (close[1] < pp)

// c1 = (close[1] CROSSES UNDER pp) //perhaps c1 = (close[1] CROSSES UNDER pp[1]) ????

// replacement for the CROSSOVER (crossing under in this case)

c2 = (close[2] > pp) AND (close[1] < pp)

I can’t actually know what you want to achieve, but if you simply need to check that there’s been a crossover the prior candle, you could replace the line c1 = (close[1] CROSSES UNDER pp) with:

c1 = (close CROSSES UNDER pp)
// then you can refer to c1[1] to know whether a crossover occurred the prior candle)

1 2	c1 = (close CROSSES UNDER pp) // then you can refer to c1[1] to know whether a crossover occurred the prior candle)

robertogozzi

Moderator

Topics: 69

Replies: 17275

Been thanked: 4124 times

Author

Posts

Viewing 3 posts - 16 through 18 (of 18 total)

← 1 2

Find exclusive trading pro-tools on