Using complex indicators like the RMO on one minute charts is likely
to cause problems. It's caused by a conflict between the tick data
stream and the computer having to coordinate calculations and graph
display. All of those have to be insync or MS stutters for a second
and freezes up. MS just doesn't recover well when any data flow in any
pipe gets out of sequence.
Prev's on intraday charts can be a major problem and really magnify
the situation I just mentioned. I only use formula's with Prev's on
the longer time frames like daily or hourly charts. It's not that your
computer is slow. It's that there's too much data swapping from the
processor, hard disc and RAM that has to take place in coordination
with the inflow of tick data. You can see this if you open symbols
that have a lot of tick data versus a really low volume symbol.
It gets very complicated and expensive to overcome some of the
challenges of coordinating all of the various MS functions.
Here are a few things you can do. Increase the size of RAM to 4 GBs,
if you're running Vista and at least 2 GBs if you're running XP. 4 GBs
helps on XP but only marginally. MS does a lot of data swapping in and
out of memory.
Install an Intel x-25 160 GB solid state drive. MS is read write
intensive. Hard disc response time is critical to match up in inputs
and outputs. You won't believe how fast your system goes with the
Intel Drive in it. Once a defrag logic is worked out by Intel, I'm
going to put two of them into the computer I run MS on. (You can also
create a RAM drive if you can put 8 GBs on your motherboard. MS will
load into the RAM drive daily when you start it up, and it will fly
like you won't believe.) MS hammers your hard drives. Solid state
drives are more durable. The issue with small packet sizes and
defragging needs to be solved before I'll use MS on them daily,
however. MS creates a lot of small files and rewrites them constantly.
Turn off the accelerator mode on your video card if it has an
accelerator mode. (some do some don't)
Test MS with virus protection turned on and off and firewall
protection turned on and off. Those two things cause a lot of
problems. And test with both of them turned off at the same time.
Some video card bios cause problems with MS. That's a tough one to
track down, but MS has clashes with video memory sometimes. Things
like double buffering and full screen anti-aliasing can trip up MS
also. Since MS is a 2D program, RAM memory size is more important than
the memory on the video card. I find that MS works better with older
simpler video cards. (I do too!)
Often the management of memory becomes a factor as more charts are
opened and closed.
Other issues like the flow of data from your ISP. ISP's have data
glitches all the time but they happen so fast they don't generally
catch our attention. Every now and again those disruptions can cause
MS to make a misstep from which it can't recover.
MS is an old program. It needs a complete rewrite to make it more
compatible with today's technologies, but that's not likely to happen.
Instead we'll get more band aid features slapped on to it.
I think you can probably figure out a way to make money with other
indicators on a one minute chart. I keep my one minute charts really
simple. Tradestation is a bit better at handling these kinds of
problems, so it depends on what kind of program you want to work with
while trading.
Good luck Rvalue1!
Super
--- In equismetastock@ yahoogroups. com, "rvalue1" <rvalue1@xxx > wrote:
>
> I was using the RMO expert yesterday on a 1' chart and it seems to
> freeze up doing its calculation. The blue-red bars became black with
> no signals. When I tried changing the expert, I saw that Metastock
> was frrozen up and not responding.
> Has anyone had this problem with the RMO? My laptop is 1 1/2 years
> old and is not too outdated. Appreciate the input.
> For now, I have canned using the RMO and switched to a look alike
> that works fine.
>
> Rvalue1
> --- In equismetastock@ yahoogroups. com, pumrysh <no_reply@> wrote:
> >
> > Joo,
> >
> > I've taken the liberty of changing the message subject.
> >
> > Thanks for the indicator! From a lanquage standpoint this is
> > definately shorter. The limitation problem still exist though. If
> we
> > were to try a recursion period of m25 or there about metastock
> would
> > politely tell us that we had exceeded the number of allowable
> > variables.
> >
> > It would be great if we could set the lookback periods for the
> simple
> > and recursive moving averages by simply using an input statement.
> >
> >
> > Preston
> >
> >
> >
> > --- In equismetastock@ yahoogroups. com, joo seng <jooseng6@> wrote:
> > >
> > > Preston,
> > >
> > > This is my ver of the RMO Osc:
> > >
> > > m1:=mov(c,2, s);
> > > m2:=mov(m1,2, s);
> > > m3:=mov(m2,2, s);
> > > m4:=mov(m3,2, s);
> > > m5:=mov(m4,2, s);
> > > m6:=mov(m5,2, s);
> > > m7:=mov(m6,2, s);
> > > m8:=mov(m7,2, s);
> > > m9:=mov(m8,2, s);
> > > m10:=mov(m9, 2,s);
> > >
> > > mm:=(m1+m2+m3+ m4+m5+m6+ m7+m8+m9+ m10)/10;
> > >
> > > ST1:=100 *(c-mm)/max( hhv(c,10) -llv(c,10) ,0.000001) ;
> > >
> > > RMO:=Mov(ST1, 81,E);
> > > RMO;
> > >
> > > --- On Sat, 28/2/09, pumrysh <no_reply@xxxxxxxxxx s.com> wrote:
> > > From: pumrysh <no_reply@xxxxxxxxxx s.com>
> > > Subject: [EquisMetaStock Group] Re: RSI Calculation
> > > To: equismetastock@ yahoogroups. com
> > > Date: Saturday, 28 February, 2009, 4:56 AM
> > >
> > >
> > > Joo,
> > >
> > >
> > > Just noticed that I had written recussion... .that should have
> been
> > >
> > > recursion.
> > >
> > >
> > >
> > > Thus far we have:
> > >
> > >
> > >
> > > (Mov(C,2,S)+
> > >
> > > Mov(Mov(C,2, S),2,S)+
> > >
> > > Mov(Mov(Mov( C,2,S),2, S),2,S)+
> > >
> > > Mov(Mov(Mov( Mov(C,2,S) ,2,S),2,S) ,2,S)+
> > >
> > > Mov(Mov(Mov( Mov(Mov(C, 2,S),2,S) ,2,S),2,S) ,2,S)+
> > >
> > > Mov(Mov(Mov( Mov(Mov(Mov( C,2,S),2, S),2,S),2, S),2,S),2, S)+
> > >
> > > Mov(Mov(Mov( Mov(Mov(Mov( Mov
> > (C,2,S) ,2,S),2,S) ,2,S),2,S) ,2,S),2,S) +
> > >
> > > Mov(Mov(Mov( Mov(Mov(Mov( Mov(Mov
> > >
> > > (C,2,S),2,S) ,2,S),2,S) ,2,S),2,S) ,2,S),2,S) +
> > >
> > > Mov(Mov(Mov( Mov(Mov(Mov( Mov(Mov(Mov
> > >
> > > (C,2,S),2,S) ,2,S),2,S) ,2,S),2,S) ,2,S),2,S) ,2,\
> > >
> > > S)+
> > >
> > > Mov(Mov(Mov( Mov(Mov(Mov( Mov(Mov(Mov( Mov
> > >
> > > (C,2,S),2,S) ,2,S),2,S) ,2,S),2,S) ,2,S),2,S\
> > >
> > > ),2,S),2,S)) /10;
> > >
> > >
> > >
> > > can be written down in the following analytical form:
> > >
> > >
> > >
> > > (C*1023+Ref( C,-1)*2036+ Ref(C,-2) *1981+
> > >
> > > Ref(C,-3)*1816+ Ref(C,-4) *1486+Ref( C,-5)*1024+
> > >
> > > Ref(C,-6)*562+ Ref(C,-7) *232+Ref( C,-8)*67+
> > >
> > > Ref(C,-9)*12+ Ref(C,-10) )/10240
> > >
> > >
> > >
> > > What I would like to be able to do is simplify these formulas.
> Both
> > >
> > > are hardwired and in order to change them it requires that the
> code
> > >
> > > be rewritten. I also want to input the variables for the simple
> > >
> > > moving average and the recursive moving average.
> > >
> > >
> > >
> > > Preston
> > >
> > >
> > >
> > > --- In equismetastock@ yahoogroups. com, joo seng <jooseng6@ .>
> > wrote:
> > >
> > > >
> > >
> > > > Hi Preston,
> > >
> > > > Do you means you want to vary the no. of times of the mov of
> mov?
> > >
> > > >
> > >
> >
>