Found 7 results for Metastock 9.1. Full version downloads available, all hosted on high speed servers! Download servers online: 7.
Chris Errors are reported when daily signals are plotted on daily charts and weekly signals are plotted on weekly charts, etc. O1:=ExtFml('TMW.WeeklyLocalize',0); H1:=ExtFml('TMW.WeeklyLocalize',1); L1:=ExtFml('TMW.WeeklyLocalize',2); C1:=ExtFml('TMW.WeeklyLocalize',3); O1;H1;L1;C1; This plots 4 horizontal lines of 0, 1, 2, and 3 on a daily chart. O1:=ExtFml('TMW.Weekly',0); H1:=ExtFml('TMW.Weekly',1); L1:=ExtFml('TMW.Weekly',2); C1:=ExtFml('TMW.Weekly',3); O1;H1;L1;C1; The first indicator plots future values for Monday to Thursday, which is interesting visually, and virtually impossible to do in MFL, but not particularly practical in terms of testing systems. My assumption was that the first example would give TRUE weekly values on EOD charts (on and after the Friday Bar). I'm not sure if I should be a little annoyed or very flattered that you seem to have picked up some ideas from the website (and also Jose's websitesite) and decided to improve upon them. First there was an equity indicator following in the footsteps of Trade Equity, and now, longer timeframe and compressed timeframe indicators.
If these bring benefits for MetaStock users then I'm all for them, so keep up the good work, but the job is far from complete yet. Roy PS I haven't looked at your equity indicator yet, but I do want to give it the 'once over' when I have time. I’m proud to present you a unique collection of Multitimeframe Functions for MetaStock. Any process that has already been coded in MetaStock Formula Language (MSFL), by definition cannot be considered unique. 5) Create Daily Data for a Data Array ExtFml( 'TMW.DailyCreate', Number) 6) Create weekly Data for a Data Array ExtFml( 'TMW.WeeklyCreate', Number) 7) Create monthly Data for a Data Array ExtFml( 'TMW.MonthylyCreate', Number) These functions don't work in my copy of MetaStock Pro v8.01 code:1:7d711fd212Plots the Calendar Week on a chart (ISO Standard) 1) ExtFml( 'TMW.CW')/code:1:7d711fd212 This is plotting an erroneous week count in some years, e.g.: 2004: starts the week count at 2 instead of 1. 1996/2001/2002: counts the last week in that year as week 1, instead of 53 (some years have an additional partial week). 1998: starts the week count at 53, then lags behind 1 week for the rest of the year.
Compare the DLL's plot to an accurate indicator using plain MSFL. These functions plot OHLC values before they actually become available.
Using hindsight in this function means that these values will shift in real time, and will also produce unrealistic expectations when backtesting. Refer to the ZigZag function for more on dynamic/hindsight plots. Also compare the DLL's weekly function to an accurate using plain MSFL.
This last point illustrates the danger in the inherent lack of transparency in external formulae - it's not easy to be sure that the function is not using hindsight in its internal process. My current algorithms work this way (simple description): Example for lower time frame Daily und higher time frame weekly.
I compress the lower time frame to the weekly time frame. This means, one Week is represented by only one Data Point. So, if you choose the Close data array, the weekly data array is only represented by one close data point. The plot on the chart is 100% identical to a line chart, but the corresponding dates are totally different, because it's plotted on a daily chart.
One Daily bar = one Weekly data point. The localize functions works in the opposite way: Every bar on a daily chart has multiple identical weekly plots. One week (normally 5 bars) = one (identical) Weekly data point.
My plan is to create a totally flexible multiple Timeframe Indicator, where you can enter any number. The lower time frame is multiplied by this value. So if you like, you can easily look at a 1min, a 37min and an 89 min chart in one window. I’m currently working on a concept, but it’s a little bit tricky.
The creation is not the problem, but the localization is difficult, because on Intraday data there’s no clear reference point where to start or to stop, the holiday and weekend Problem, Maybe for FOREX it’s no so tricky, if I start every trading week on Sunday 22:00 and ends it on Friday 23:00 and ignores all holidays. Maybe you have another idea or concept. By the way, the inspiration for these Indicators comes from PPP, which I've bought some years ago and like very much. @MSST, You should neither be annoyed or shattered.
Not knowing me under my username means not, that I’m a MetaStock newbie. I use MS for more than 7 years and I think, there's not so much, I can’t realize with the common Formula language of MS. You (not personally) are well known to me and I sent many of my customers to your Internet Site and/or recommend reading your newsletter to them. I worked with “your” weekly Indictors and I spent a lot of time with the Trade Equity set and I like both tools very much. One reason for writing the Equity function and the weekly Indicators was that I spent uncountable hours on workshops to explain these Indictors to my customers. The reason for this is that the usage is too complicated for the “normal” user.
“My” Equity function is fast and very simple to use, you enter some parameters in one Dialog and you can get a lot of System Information and a plot of the equity on a chart. The function is not ready, it’s a first try. Characteristic numbers can be added or removed, the layout can be changed.
The only thing I need is the input of some users. If you want to have another output, other System characteristic numbers or anything else, you can tell me and I try to implement this. The DLL is a private project of my own and there’s no plan to sell or distribute the DLL in a commercial form. I don’t want to steel you any customer and as I told in another thread: I’ve no problems in sharing my code, if the equity function is ready.
My only intention is to give MS users a simple method to get some information on a Trading System and a plot of the equity. If they need a sophisticated test of a System they shall you the Enhanced System tester, TradeSim or what ever they want. Unique is the compressed Monthly/Weekly/Daily on a lower Timeframe, no other software I knew, has this feature.
The Calendar function now is correct, thanks for the hint. Errors are human; please remember of your various versions of tools, which had in the first version some errors. The current plot of my Indictors has nothing to do with hindsight’s; they represent the actual value of the chosen higher Timeframe. If you look today at a Weekly Chart, you can not say, this is not a correct chart. But you’re right: Every signal on every Timeframe is only valid, after the bar has ended. In my next version I implement the ability to choose a delay, so when using the indictor in a System Test, it generates only a signal on the last day of the week.
Chris3105 Thank you for the detailed response. However, you haven't speciffied if your DLL will support Higher Time Frame Indicators from MS or, alterantively, from other DLL's. A correct plot for a higher time frame indicator I believe it requires to compute/return its function's output from the higher time frame data array to the current time frame and only once for every N bars in the current time frame (where N is the Time Factor multiplier).
The Applications Windows X force keygen for autocad 2012 64 bit. Download Xforce Keygen 64-bit do i need abbyy finereader 90. Free download xforce keygen autocad 2012 64. 3ds max 2010 64 bit xforce keygen. Only xforce keygen 3ds max. Autodesk 3ds Max 2012 and.
PP+ is doing just that, but I don't know anything about the algorithm. I believe that is not even required to re-implement/re-calculate the indicators values in your DLL but to pass instead the price data array values from the higher time frame to the external DLL function that was called from the custom indicator in MS at a N times slower pace. (pls see the 'Correct' and the 'Wrong' examples from my previous reply). From this perspective, PP+ looks to work almost OK, but from some tests I've ran with TDataCreate/TDataLocalize looks there are some discontinuities for these functions output (see the file 'PPPTFPlots.doc' from the 'ADSI Users = Stimulus Files' post). (Looks there is a problem exactly with the 'Localize' function because the biggest discontinuities are showing always between 00:44:00 AM and 1:34:00 AM on EACH Monday, every week!) I hope your implementation will be better than PP+ TDataCreate/TDataLocalize. Regarding FOREX trading week, it starts on [email protected]:00PM and ends on [email protected] 5:00 PM. I wish you good luck, patience and success to finish this promising DLL.
Regards Guara. Not knowing me under my username means not, that I’m a MetaStock newbie. So, why hide your real name/details? color=green:b17980dd67 The current plot of my Indictors has nothing to do with hindsight’s;/color Weekly values are plotted by this dll in retrospect on daily charts, before they become available in real-time (i.e. Friday's Close on previous MonThu).
This is process is called 'hindsight'. color=green:b17980dd67 In my next version I implement the ability to choose a delay/color It would be better if there was no hindsight to delay in the first place. Overall, I think that this multi-timeframe external toolkit has a lot of potential, as long as you are prepared to support it.
Don't be afraid to display some of your details (name/website) - it will add credibility to this useful tool. After some very hard days with MSX here's the newest version of Multiple Time functions. Hello, here's the latest version and I say, the results are (on my PC) very great. To get these good results, I had to create the logic and algorithms for the Flex Function totally new. My frustration while testing these functions was unbelievable.
New/modified functions: ExtFml( 'TMW.FlexCreate', Data Array, Price Field 0(Open) 1(High) 2(Low) 3(Close), Multiplier for Timeframe, Delay: 0=Dynamic, 1=Delay) This function has four input Parameters: 1) Data Array: Open, High, Low, Close or a function 2) Price Field (Number): 0 = Open, 1= High, 2= Low, 3 = Close 3) Multiplier for Timeframe (Number) 4) (Number) Last bar Dynamic = 0, Last bar Delay = 1 By using this function on Daily and Intraday (no Tick) Bar, the data are compressed by the factor Multiplier, by using the function on a Tick Chart, the Multiplier is a factor for minutes. Examples: Simple Close of a two Bar Close Create:=ExtFml( 'TMW.FlexCreate', C, 3,2,0); Create 20 Bar exp. Moving Average of a two Bar Close Create:=ExtFml( 'TMW.FlexCreate', C, 3,2,0); Mov(Create,20,E) ExtFml( 'TMW.FlexLocalize', Flex Array, Multiplier for Timeframe) This function has two input Parameters: 1) Flex Array: Result of the TMW.FlexCreate 2) Multiplier: Must be exact the same value as in TMW.FlexCreate. Soft verdict vergessen rarity. Examples: Create and Plot a two Bar Close Create:=ExtFml( 'TMW.FlexCreate', C, 3,2,0); Localize:= ExtFml( 'TMW.FlexLocalize', Create, 2); Localize Use with external Function Create:=ExtFml( 'TMW.FlexCreate', C, 3,2,0); Localize:=ExtFml( 'TMW.FlexLocalize', Create, 2); ASI:=ExtFml( 'ASI.sma', Localize, 9); ASI Restriction/Limits: You can create on a intraday/daily Char any period, where: (Intervall. Multiplier ).
@guarariua, one addition to my previous post. The result of the TMW ASI Chart on a 10 Min Chart of Microsoft was 25.37045, the result of the PP Excample was 25.36695.
To find out, which value is correct, we apply the ASI Indicator directly on the calculated higher Time Frame. In my excample I choose a 10 Min Chart of Microsoft, the TMW has a Multiplier of 4 Original Chart has to be a 40 minute Chart.
Now use the original MS Chart in a 40 Min display and create a new Indicator: ASI:=ExtFml( 'ASI.SMA', C, 20); ASI You see: TMW calculation has exact the same value as the original Chart. And the best thing is, you can use a strategic delay with the TMW functions:D Hope, your glad now:wink: Chris. Chris Everything works fine now.
I have followed exactly your exmaple from Dec-6th from ASI.SMA that was a typo: FlexLocalize MUST be the last called function, in order for the plot to be correct. I have used also much more complex indicators (i.e. Adaptive Fisher Transform, that uses the CyberCycle Period from ADSI package) to see how your Flex function perform. The results are quite similar with PP+, althou I found that PP+ are closer to the original indicator in the higher time frame. The FlexLocalize values for a TimeFactor=4 on a 15min chart vs. The same indicator in a 1hr chart).
The highest diference I saw was arround 0.32 for an indicator range of +/-5 and many time the diference in value compared with PP+ was at the 3rd decimal. Seems to me that your algorithm is more dynamic vs.
PP+ and generating slightly higher values. Anyway, your efforts are very commendable and the Flex functions are quite good. Would be a good idea to provide a little bit more detailed explanation about their use.
I.E for FlexCreate/FlexLocalize: - The 1st step is to 'Create' the Price values in the higher time frame (OHLC) - Use any kind of indicator/external function that uses ONLY the values of the price created in the step above. 'Localize' the indicator output and plot it in the current time frame.
Thanks again for this great utility Chris, and keep up with the good work!
FileFortune.com is a new file sharing web service which gives you access to literally hundreds of thousands of direct downloads including software, games, movies, tv shows, mp3 albums, ebooks and more! Our downloads database is updated daily to provide the latest download releases on offer. To celebrate our launch we are offering unlimited full download access for $3.99/mo! This is a limited offer and will soon expire and revert back to the normal member price. We now have 154,836 downloads in the member section.
Take the FileFortune now for more detailed information!