Hi. 1) Does anyone know any formula which can calculate how a stock reacts over a period of time when the market is moving: - up - sideway (eg within +/-0.3%) - down ?? 2) Beta Formula I receive the following error - "Division by zero: 938" My formula is as follows: [code:1:079ceb090b] Period:=Input("Period:",1,9999,21); SecurityA:=Security("[i][color=blue]file_location[/color][/i]",C); ((Period * Sum(ROC(C,1,%) * ROC(SecurityA,1,%),Period))- (Sum(ROC(C,1,%),Period) * Sum(ROC(SecurityA,1,%),Period))) / ((Period * Sum(Pwr(ROC(SecurityA,1,%),2),Period)) - Pwr(Sum(ROC(SecurityA,1,%),Period),2)) [/code:1:079ceb090b] What's up? :evil: Thank you. :)

or even speed it up a little bit by reducing the number of computations.... --8<------------------------- prd:=Input("Period:",1,9999,21); thisSec:=ROC(C,1,%); SecA:=ROC(Security("file_location",C),1,%); num:=(prd*Sum(thisSec*SecA,prd)) - (Sum(thisSec,prd)*Sum(SecA,prd)); den:=Max(0.00001,(prd*Sum(Pwr(SecA,2),prd)) - Pwr(Sum(SecA,prd),2)); num/den; --8<------------------------- wabbit :D

Don't quote me on this, but I think you will find the error is caused when the chart is opened and the indicator applied, MS gets the values of the data from the open chart and the Security() values, but only for the dates that are common in both data sets. If you modify the dates then you are changing the relationship between the two data files, and I believe the only way to cure this is to either set the x-axis properties back to default , or close and re-open the chart. On the other hand, why are you changing the data periods?? If you know it causes a problem, then don't do it! BTW - after several attempts, I could only generate the error once! wabbit :D

They are not the same. :?: I have created these 2 indicators and plotted it on the same chart. The first one is a normal line which fluctuating up and down. The second one is just a line moving narrowly around 0. What's wrong? :|

Well in the first code, you have umpteen nested brackets..... rationalising them was always going to be fraut with danger! Re-count the brackets and group the operations that need to be grouped. Start with no brackets except around the functions that specifically require them.... and go from there. num:=prd*Sum(thisSec*SecA,prd) - Sum(thisSec,prd)*Sum(SecA,prd); den:=prd*Sum(Pwr(SecA,2),prd) - Pwr(Sum(SecA,prd),2); The order of operations is clearly spelled out in the MS Users Manual, so you don't a zillion brackets.... just read the notes and implement cleaner code. See if that helps. wabbit :D P.S. A couple of simple points have just been highlighted here: [list:06681b0ea3][*:06681b0ea3]NEVER accept anyone else's code unles you 100% understand every line of code. My repsonses were written a 04:30 as I couldn't sleep... and am very tired. Been working on the mean, median, moded thing all night..... for you. (How's the testing coming along? Haven't seen any results posted yet?) [*:06681b0ea3]You need to be able to resolve some of your own problems, without relying on everyone here. We are sharing a lot of information with you for free. We are not infallable, we sometimes make mistakes. You should have been in a position to sort this minor problem out for your self without having to post what I call a "sook" post! The proper thing to do would have been to to sort the problem out yourself, then post the correct version with a message saying, "Thankyou for your efforts, but you made a mistake. Here is the correct code." [*:06681b0ea3]the MS Users Manual, has been and always wil be the MS Bible [/soapbox][/list:u:06681b0ea3]

WW, did you try the code I posted for you? It should have resolved your original problem. As a good coding practice, you want to avoid extra spaces and braces when possible. You will quickly reach character limits otherwise. Brackets and parentheses are used to override the natural operator precedence. Non-judicious use serves no purpose and clutters up the code. Please read the forum rules thoroughly. It would be good for you to start with the general information outlined in the comprehensive User's Manual. When you get ready to start with the formulas, download the Formula Primer and work the solutions in it... a few times. Finally, check out the Training Videos that are available to you free here on the forum. As Wabbit stated, try to help yourself first. Then, when you need help, please adhere to the forum rules and you will find that responses flow pretty smoothly. Thanks, George

yes. I am unable to duplicate this error either on individual charts or those loaded on a preset template. Clearly, you are experiencing some difficulty based on your screen shots, but I could not do anything to upset the original Beta plot. I use 'Retain Scale' on the x-axis. Also, I prefer to use the Equis Beta formula which can be found on the main web site, or if you dig deep enough, you might uncover it here in the forum. It is here somewhere... Basically it involves dragging your index security price plot into an empty inner window of the security in which you are wishing to examine the Beta relationship. Then you drag the Beta indicator on top of that inner window index price line. The code is essentially the same, except that the external reference called by Security() is replaced with the INDICATOR reference. Maybe you can try that and see what happens. If that doesn't work for you, I'm stuck. HTH, George

WmWaster, The answer to this problem is obvious. If you had read the code for the Beta indicator, and taken the time to try and understand exactly what is going on with it (as I have suggested to you previously) then you will know the Beta will return a value of 1 when it is comparing the OHLCV data in the primary array to nothing. What this means is that you have not followed the instructions on how to plot this indicator correctly, and have not read the in the MS Users Manual about dealing with multiple plots on one chart, and referencing using the Indicator or 'P' functions. When you open a chart, this is the primary data source; when you drag another price data array onto the already open chart, this is a secondary data array. When you try to drag the Beta indicator from your indicator quicklist onto the chart, when the mouse initially enters the chart you will see the primary data becomes highlighted in pink (mauve?). If you drop the Beta indicator then, it will not be able to reference the secondary data and so will return a value of 1 for all time. Keep moving the mouse until it is over the secondary data; this data array will now highlight in pink. Now you can drop the Beta indicator and it will operate correctly. I point out to you again the necessity to fully understand the indicators which you are going to be using to trade, and the wealth of information contained in the MS Users Manual and the Equis Formula Primer. wabbit :D

Do the charts have more than minimum required amount of data loaded? ie 21 days? You have mentioned before that you often change the loaded dates? I never change mine and I never seem to have any troubles that you have. Loading the maximum amount of data will ensure that any exponential indicators are as accurate as possible, and will also give that wider 'global view' of the stock price. You can zoom in and out to DISPLAY different time intervals, but all of the data is loaded into memory and used in the computations. The maximum value is 65500 bars. In my default view I see one year of data. wabbit :D

Yes, it has more than 21 days loaded. Yes, the best workaround. :D What's the full forn of URSC? I couldn't find it in the Help file, nor the indicator drop-down list.