System Tester Suggestions

[kdennis <Keith.Dennis@xxxxxxx>]

Equis:

 1) I suspect that the first thing that would have to done to be able
    to implemented or accommodate any of these great suggestions you are
    receiving, would be to do a file structure overhaul of your strange
    data format.  Since this overhaul is long overdue anyway, why not
    just do it and move on to bigger and better things.  Then you could
    use a more up-to-date, state-of-the-art, and standard file structure.
    How about a relational database structure of some sort?  This would
    be a big improvement to all your products.  Think of all the outside
    programming language capabilities that would instantly become 
    available.  Programmers the world over currently working with 
    relational database structures would be capable of supporting and 
    creating custom system designs right away for the new Metastock.  
    
 2) You need to add Global parameter access and update capabilities.

 3) You need to add the ability to use callable global routines that can
    return values, flags, or whatever we want for code reuse abilities.
    Perhaps the possibility of compiled and store modules to be executed
    by the system tester/experts/explorations/indicators/etc., instead of 
    executing code in line as it is today.  Yes, I know that there is the
    FML(" ") writing function available, but it is just not the same.   

 4) You need to add the ability to enter and exit a trade on the same day.

 5) You need to add the ability to scale in and out of a position.  What
    I mean is the ability to trigger multiple buy signals without having
    to always sell in matched pairs, as it is now.  Something like  
    buy-buy-buy-buy-buy-sell-sell-sell.  Not as it is today:  buy-sell-
    buy-sell-buy-sell. 

 6) We need to ability to system test multiple securities at one time.

 7) You need to go to a more robust programmable language environment.

 8) You need to speed up this testing process and make it more efficient.
    Probably means accessing the disk less often.  Maybe read at the start
    of the test and then write out the results at the end.  No need to 
    access the data for every security we are processing.  Read all the 
    records into storage and access them there.  Most computers are loaded
    with memory these days.  Let's use it !!!      

 9) The system test output needs to be store on disk for later retrieval and
    viewing.  You would need to figure out a way to store these report 
    files in a generation naming convention of some sort to allow viewing at
    a later time.  

Thanks,
Keith
                         
----------------------------------------------------------------------------
       
Date: Tue, 19 Jan 1999 09:43 -0700 (MST)
From: Equis Support <support@xxxxxxxxx>
To: "'metastock@xxxxxxxxxxxxx'" <metastock@xxxxxxxxxxxxx>
Sender: owner-metastock@xxxxxxxxxxxxx
Reply-To: metastock@xxxxxxxxxxxxx
Subject: MetaStock System Testing capabilities

            In the interest of improving the system testing
capabilities in MetaStock, we are asking for your input.  We have many
suggestions which we are currently evaluating, but would like as much
feedback as possible.  So please send us your opinions on what you would
like the System Tester to have or do or what you wouldn't like it to
have or do.  Please be as detailed as possible.

            We will evaluate all the suggestions we receive
and see if we can incorporate them into future versions.  Please
understand that not every suggestion can be used.  However, we feel it
is important for us to receive all types of comments.  

            Please send all suggestions to
mailto:suggestions@xxxxxxxxx with "System Tester Suggestions" in the
subject line.

            Thanks for your help!

            Allan McNichol
            Equis International, Inc