OR || usage

[Aussiemike]

Hi,

Trying to use || (OR) like this. Can I (syntax? it errors like this) or do i need separate arguments for each?

if ((Open[0] || Low[0] || Close[0]) >= MAX(High, 3)[0])

Cheers

[BigWaveDave]

Looks ok to me. What's the context and what's the error?

[Aussiemike]

Strategy\FullBollRSITrail.cs Operator '||' cannot be applied to operands of type 'double' and 'double' CS0019 - click for info 245 12


Cheers

[Aussiemike]

on a related part i've got it working as 3 separate conditions, but i've realised on testing the output i need to use barsarray on the highs...but cant get that working.

If you do have a knack for syntax would probably benefit more from that as not sure of an easy way around. This is under Barsinprogress ==1, and i want the last three highs to be on barsinprogress ==0

Cheers

if (Open[0] >= MAX(High, 3)[0]
|| High[0] >= MAX(High, 3)[0]
|| Close[0] >= MAX(High, 3)[0])

[Aussiemike]

Tried

if (Open[0] <= MIN(Lows, 3)[0][0]
|| Low[0] <= MIN(Lows, 3)[0][0]
|| Close[0] <= MIN(Lows, 3)[0][0]


actually just got that working...

if (Open[0] <= MIN(Lows[0], 3)[0]
|| Low[0] <= MIN(Lows[0], 3)[0]
|| Close[0] <= MIN(Lows[0], 3)[0])

If you have an answer on the OR question it would be nice to know, although i believe i have my solution.

Cheers

[koganam]

Tried

if (Open[0] <= MIN(Lows, 3)[0][0]
|| Low[0] <= MIN(Lows, 3)[0][0]
|| Close[0] <= MIN(Lows, 3)[0][0]


actually just got that working...

if (Open[0] <= MIN(Lows[0], 3)[0]
|| Low[0] <= MIN(Lows[0], 3)[0]
|| Close[0] <= MIN(Lows[0], 3)[0])

If you have an answer on the OR question it would be nice to know, although i believe i have my solution.

Cheers

Your final solution is correct. Your initial code will not run, as Open[0] et.c., are not logical constructs; they are simply data points.

[marcow]

If you have an answer on the OR question it would be nice to know, although i believe i have my solution.

Hi,

Trying to use || (OR) like this. Can I (syntax? it errors like this) or do i need separate arguments for each?

if ((Open[0] || Low[0] || Close[0]) >= MAX(High, 3)[0])

Cheers

the output of each condition separated by the "||" signs should be a boolean, and not a double value like Open[0], Low[0] or Close[0]. So the if statement above should be
if ( Open[0]>= MAX(High, 3)[0] || Low[0] >= MAX(High, 3)[0] || Close[0] >= MAX(High, 3)[0] )

[sledge]

If you really want to simplify...

If ( Math.Min ( Math.Min ( Open[0], Low[0]) , Close[0]) <= MIN(Lows[0], 3)[0])
{
MakeMegaBucks2()...
}

**please don't throw me under the bus if this doesn't work... I haven't tested any of this... thanks

http://msdn.microsoft.com/en-us/library/aa340213(v=vs.71).aspx

Tried

if (Open[0] <= MIN(Lows, 3)[0][0]
|| Low[0] <= MIN(Lows, 3)[0][0]
|| Close[0] <= MIN(Lows, 3)[0][0]


actually just got that working...

if (Open[0] <= MIN(Lows[0], 3)[0]
|| Low[0] <= MIN(Lows[0], 3)[0]
|| Close[0] <= MIN(Lows[0], 3)[0])

If you have an answer on the OR question it would be nice to know, although i believe i have my solution.

Cheers

[marcow]

good idea Sledge to use the Math.Min method

[koganam]

If you really want to simplify...

If ( Math.Min ( Math.Min ( Open[0], Low[0]) , Close[0]) <= MIN(Lows[0], 3)[0])
{
MakeMegaBucks2()...
}

**please don't throw me under the bus if this doesn't work... I haven't tested any of this... thanks

http://msdn.microsoft.com/en-us/libr...(v=vs.71).aspx

Which tells me now that it is all redundant anyway. the Low[0] is ALWAYS the minimum value, so no need to even bother with the other checks if you are checking for the low value against another value.

[marcow]

ooops,

I guess we were focussing to much on the boolean logic in the condition without looking at what's going on. Let's say in our discussion we treated close[0],low[0],open[0] as random variables.

Nice call Koganam !

[Aussiemike]

Cheers...it has made me notice something.

The use of the other values Open and Close is simply to ensure i get the first or nearest strike.

While the low would indeed meet the criteria the Open might as well, and i'd rather hit that for accuracy (as much as can be without tick data.

Close is useless though i believe as this can only hit if the Low does, and after it, so thanks for making me look at this again i'll remove that.

I have Open and High for Highs now, and Open and Low for Lows...

Cheers

Cheers