Tams

you know it is OT... why don't you start a new thread ? have you tried the search button !?!?

you can start with a book... there are a few on the market that teaches you the basic mechanics and methods. what platform you are using? (don't tell me, let me guess... it is MT4)

there is a method to everything...

For TradeStation, get the ebook EasyLanguage Essentials Programmers Guide (free) read up on Look-Inside-Bar-Back-testing (LIBB). For MultiCharts, use Backtesting Precision. (same function as LIBB) You are back testing on 60 min bars, and using a finer resolution (e.g. 1 tick data) as back testing precision.

arh... that's very good description.

don't jump into coding yet... you are a long way from ready. 1. Loops is easy... it is not rocket science...you just need to read the manual. 2. The problem at hand is NOT about programming in EasyLanugage... The problem is: how do you think through your logic: i.e. writing out your thoughts... a. describe what you want to do... and b .describe HOW you are going about to get want you want. c. the first set step in getting what you want is to give the computer what it needs... can you list out the items the computer need in order to do your calculation? hint: you don't need a loop, and I am not talking about array, and your description so far is incomplete...

your picture is not showing. you can load the picture directly to TradersLaboratory. Just click the Manage Attachments button under the Advanced reply window.

Array would be easiest method... that is, if you have overcame the Array hurdle. ;-)> here's some array help http://www.traderslaboratory.com/forums/f56/array-easylanguage-5785.html

I love diving in Malaysia. I love hiking the KK, golfing everywhere, food from the street vendors. (not all the food tho, you know which ones I mean, LOL) Maylaysia has the land that Singapore does not have. Maylaysia has the natural resources that Singapore does not have. Malaysia even managed to secure some hi-tech manufacturing investments, but I don't think Malaysia ever aspired to be a financial center. p.s. very soon, everybody will be in the Royal family.

you can create a counter to count the bars, so that you can reference it later.

Crisis is Opportunity just don't make yourself other's opportunity

thanks for the video

here's another version of the Ergodic indicator this one uses the exponential moving average http://www.traderslaboratory.com/forums/f46/ergodic-1161.html

What is your chart resolution? are you looking at volume at each 5 min block? or volume since the market opening?

you have to use lines and arrows and annotations on the chart to illustrate your thoughts... nobody on a public forum is going to spend the trouble to marry your incoherent ramblings to your convoluted chart. ... and to guess if this is what you meant, or to assume if that is what you want. p.s. also... when thinking about your logics, get into the habit of writing one line at a time... one thought per line, one action per line, one phrase per line, and start a new line for every sentence...

You are welcome... You can also check out this variation. It is on Stochastic... the idea can be applied to RSI, or any oscillating indicator. Tidal Wave http://www.traderslaboratory.com/forums/f46/tidal-wave-5666.html 156

TSI (True Strength Index) is include in this indicator. To enable TSI, go to Format Study and change the "ShowTSI" from false to true. As highlighted in Bill Blau's book Momentum, Direction and Divergence, the True Strength Index (TSI) is a double smoothed momentum indicator: Through the use of two sequential moving averages, the TSI yields "low lag, smooth curves which also show trending characteristics of price." .

Ergodic (Double Weighted) Based on a concept by William Blau as described in his book Momentum, Direction, and Divergence the Ergodic Oscillator (EO) is a double smoothed index with a signal line. The Ergodic is intended to act like a stochastic indicator without the "compression" often seen with stochastics at extremes. As a result, the Ergodic helps to register long trends in prices. Note: This EasyLanguage indicator was written in MultiCharts. I have not tested it in other compatible programs. Please refer to your users manual for importation instructions. Ergodic Double Weighted.txt ERG_Double_Weighted_(MultiCharts).pla

I would suggest you to draw a flow chart to illustrate your logic. the branches should include ALL THE PERMUTATIONS.

yes indeed. may I extend it to... It's what you don't know you don't know, that'll hurt you!

I have reformatted your code... I didn't change the code, only the formatting. You see, you have lots of conditional logic in your code. Many of the logics are nested... ie, there are multiple layers of IF condition1=true THEN do-this ELSE do-that... When you have a lot of code, the logic is easy to get lost in the "spaghetti". Formatting (indentation) of the code helps you to visualize your logic flow. Formatting has no effect on the computing process, this is strictly for human consumption. Here's the formated code: [LegacyColorValue = false]; { ************************************************** ******************* MACD-BB MACD Bolinger Banded Last Updated 8/30/2007 Added Up/Down Color to MACD ************************************************** *********************} Input: Use.XAvg(False), PlotCross(True), FastMA( 5), {12 default} SlowMA( 13), { 26 default} price( myprice), PlotBBands(true), SDev( 1.5), { 1.5 default} PlotBBAvg(false), BBavg( 10), { 10 default} Plot0Line(true), UpColor(cyan), UpAbove(darkgreen), DnColor(Magenta), DnBelow(darkred), Shadow(Yellow), Expanding(Green); Vars: BWI(0); value1 = MACD(price,FastMA,SlowMA); value2 = BollingerBand(MACD(price,FastMA,SlowMA),BBavg,SDev); //Upper Band value3 = BollingerBand(MACD(price,FastMA,SlowMA),BBavg,-SDev) ; //Lower Band // Band Width Indicator if Use.XAvg then value5 = XAverage(value1,BBavg) else Value5 = averagefc(value1,BBavg) ; {value5 = Average(value1,BBavg) ; } if value1 > value1[1] and value1 > value2 then begin // Plot1[1](Plot1[1],"MACD",UpAbove); Plot1(value1,"MACD",UpAbove); end else begin if value1 > value1[1] then begin // Plot1[1](Plot1[1],"MACD",UpColor); Plot1(value1,"MACD",UpColor); end else begin if value1 < value1[1] and value1 < value3 then begin // Plot1[1](Plot1[1],"MACD",DnBelow); Plot1(value1,"MACD",DnBelow); end else begin if value1 < value1[1] then begin // Plot1[1](Plot1[1],"MACD",DnColor); Plot1(value1,"MACD",DnColor); end; end; end; end; if Plot0Line = true then begin if value1 < 0 then SetPlotColor(2,Red) else SetPlotColor(2,Blue); Plot2(0,"ZeroLine"); end; if PlotBBands = true then begin //////// If Value5>Value5[1] then SetPlotColor[1](3,Expanding); If Value5>Value5[1] then SetPlotColor[1](4,Expanding); /////// plot3(value2,"bband+"); plot4(value3,"bband-"); end; if PlotBBAvg = true then begin Plot5(value5,"avg"); end; Plot6(value1,"MDShadow"); If PlotCross then begin If Value1[1]<0 and Value1>0 then Plot7(Value1,"CrossUp") else NoPlot(7); If Value1[1]>0 and Value1<0 then Plot8(Value1,"CrossDn") else NoPlot(8); end; here's an illustration of how the formatting helps you see the grouping of logics. Different people may format their codes different ways; there is no right or wrong way to format the code, the only purpose is to help you visualize the logic. .

on suggestion: do not use generic variable names. ie. Value1, Value2, etc., create a custom variable name that makes sense... so that you know what kind of data you are working with. when your code gets lengthy... you will loose track of which is what. when you come back to the code 3 months from now... you will have to STUDY the code to figure out which is what. bugs are to be avoided at all cost... this is the first step.

you have to be MORE specific... a lot more specific (this is to reflect the clarity of your thinking) what color you are looking at ? (what is the plot # ?) what color it should be? and WHY ? WHY and WHY ? what causes it to change? how many ways does it supposed to change? (# of options/permutations) which section of the code that is supposed to paint the color? can you articulate the logic in English/pseudo-code ? (in one-line-per-logic format?) if you can write them out one thought at a time... you will easily see where it went astray.

LOL... what does "but they do not look quite right" mean? let me guess... the pink should be lime green?

[ame=http://www.youtube.com/watch?v=TM-G0bkl8MQ]YouTube - That don't make no sense[/ame]