[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Question on calculation



PureBytes Links

Trading Reference Links

ALL suggestions from all of our users are recorded in a database.  When we
begin defining the functional requirements for new versions of our products,
all suggestions are reviewed.  During the review process, all suggestions
that are asking for changes in the same area of code are grouped together.

Each suggestion is evaluated by asking the following types of questions:
	How many users have asked for this enhancement?
	How many of our users (novice through expert) will benefit from the
change?
	Will this new feature cause interest in our product from potential
users who have never bought our product before?
	Are there any negative impacts to our users (novice through expert)
if we make the change?
	How well does the new feature fit into the existing or planned
MetaStock look and feel?
	How long will it take to write the code to implement the suggestion?
	Do we have the programming resources available to implement this
change when combined with other desired changed?
	Will the code change be stable or will it tend to cause bugs?
	Can the resources on an average users computer handle this change?
	Can we make the new feature easy to use (novice through expert)?

There are other issues that are discussed during this evaluation phase and I
have paraphrased the questions themselves.  Each suggestion is weighed
against all others according to the above criteria.  From this comparison,
several enhancements are identified for implementation in an upcoming
release.

All suggestions are evaluated this scheme.  The method used to give us these
suggestions (telephone, email, fax, letter) has no impact on the chance that
one suggestion will be evaluated any differently than another.  In fact the
best way to submit a suggestion that accurately conveys the details of what
a user wants, is to send an email to suggestions@xxxxxxxxxx

Ken Hunt
Programming Manager
Equis International



-----Original Message-----
From: Michel Amelinckx [mailto:Michel.Amelinckx@xxxxxxxxxx]
Sent: Thursday, July 20, 2000 9:00 AM
To: metastock@xxxxxxxxxxxxx
Subject: RE: Question on calculation


Could you explain to us a little HOW you evaluate feature enhancements and
on what basis that you decide to add which future enhancement.

> -----Original Message-----
> From: owner-metastock@xxxxxxxxxxxxx
> [mailto:owner-metastock@xxxxxxxxxxxxx]On Behalf Of PD Manager
> Sent: woensdag 19 juli 2000 23:51
> To: 'metastock@xxxxxxxxxxxxx'
> Subject: RE: Question on calculation
>
>
> The MSX capability was added strictly to enhance the calculation of
> indicators only.  Your request to enter and exit on stop
> price are issues
> that involve the system test module only.  MSX does not
> address specific
> system tester capabilities beyond those that can be addressed
> by improved
> indicator calculations.
>
> I know that there have been numerous requests for changes and
> enhancements
> to the system tester module.  This feature of MetaStock is
> long overdue for
> an overhaul.  As I stated in earlier postings, we are
> currently evaluating
> enhancements to this capability.  At this time I am unable to
> tell anyone
> exactly when these enhancements will be available.
>
> Ken Hunt
> Programming Manager
> Equis International
>
>
>
> -----Original Message-----
> From: Yngvi Hardarson [mailto:hardy@xxxxxxxxxxxxx]
> Sent: Wednesday, July 19, 2000 11:45 AM
> To: metastock@xxxxxxxxxxxxx
> Subject: RE: Question on calculation
>
>
> Ken!
>
> Can the MSX be used to program STOP entries and exits where
> the stop price
> is based on a formula?
>
> This is a feature I find quite seriously lacking in
> MetaStock. Actually most
> of the formulas needed
> could be programmed using the current formula language but
> the facility is
> lacking. I have put this
> forth as a request to Equis Suggestions on several occacions.
> I'm sure many
> other users of the
> application agree. This task can be quite easily accomlished in
> TradeStation.
>
> Regards,
> Yngvi
> hardy@xxxxxxxxxxxxx
>
> -----Original Message-----
> From: owner-metastock@xxxxxxxxxxxxx
> [mailto:owner-metastock@xxxxxxxxxxxxx]On Behalf Of PD Manager
> Sent: Wednesday, July 19, 2000 14:47
> To: 'metastock@xxxxxxxxxxxxx'
> Subject: RE: Question on calculation
>
>
> The MSX capability was added to the MetaStock formula
> language for just such
> a purpose.  The built-in formula language in MetaStock was
> designed to make
> it easy for simple calculations to be quickly and easily
> coded.  Because of
> this, many complex calculations are extremely difficult or absolutely
> impossible to code in the formula language.
>
> Without the addition of MSX, it was virtually impossible for
> us to add the
> capabilities to the formula language that were demanded by
> our power users,
> while preserving the simplicity and ease of use for our less
> experienced
> users.  While some of our users have been asking for
> traditional programming
> structures to be added to our formula language (loops, array
> indexing, etc)
> most of our users have no concept of these programming techniques.
>
> MSX adds the ability for users, who may have a programming
> background, to
> write virtually any complex indicator calculation.  When a
> user creates an
> MSX DLL, it actually allows them to add new functions to the MetaStock
> formula language itself.  This means that once written, an
> MSX function can
> be used in a custom indicator, system test, exploration or
> expert.  These
> new functions can also be easily shared with other users by
> simple transfer
> of the MSX DLL.  Once the DLL appears on the other users
> machine, the new
> functions are automatically added to the formula language for
> that machine.
>
> MSX indicators are also extremely fast to calculate.
>
> Ken Hunt
> Programming Manager
> Equis International
>
>
>
> -----Original Message-----
> From: Michel Amelinckx [mailto:Michel.Amelinckx@xxxxxxxxxx]
> Sent: Wednesday, July 19, 2000 5:11 AM
> To: metastock@xxxxxxxxxxxxx
> Subject: RE: Question on calculation
>
>
> Guy,
> Why don't you get MSX, then you can make the add on your self.
> I don't think it is too complicated if you know C or C++
> Pascal , Power
> Basic.
>
>
>
> > -----Original Message-----
> > From: owner-metastock@xxxxxxxxxxxxx
> > [mailto:owner-metastock@xxxxxxxxxxxxx]On Behalf Of Guy Tann
> > Sent: woensdag 19 juli 2000 1:19
> > To: Metastock User Group
> > Subject: Question on calculation
> >
> >
> > List,
> >
> > Well I'm in the process of trying to move our Intermediate
> > Term Signals into
> > MetaStock and need a little help.
> >
> > First, here are a few of my assumptions I made after
> > reviewing the latest
> > manual (v7.01).
> >
> > 1. Variables go away after each day (we're EOD traders, so
> > daily is our time
> > frame).
> > 2. The only way you can reference a prior day's value is by
> > using PREV or by
> > plotting the indicator and using the "P" Data Array Identifier.
> > 3. The only way to reference the previous 20 values of an
> > indicator is by
> > using the "P" Data Array Identifier.
> > 4. Plotting of indicators is irrelevant for our system, so I'm only
> > interested in a programming solution.
> >
> > Questions:
> >
> > 1. Is there any way to build an array or list of variables
> > that you can
> > programmatically control?  For instance, I want to maintain
> > the last 20
> > values of a specific indicator and keep them for use on the
> > next day.  At
> > then end of each days processing, I would move X17 to X18,
> > thereby dropping
> > the previous X18.  X16 to X17, etc., thereby getting ready
> > for the next days
> > result, which I would store in X.
> > 2. Is there any way that I can maintain multiple PREV values for an
> > indicator?  What about PREV -1 and PREV -2?
> >
> > In our Intermediate Term System, we have an indicator we
> > calculate whereby
> > we maintain the last 18 results, always keeping the last 18
> > values available
> > to us for calculations.  We use the first 6 for a short-term
> > indicator, the
> > second six for an intermediate-term indicator and the final
> six for a
> > long-term indicator.
> >
> > I'm trying to avoid having to do much additional programming
> > outside of
> > MetaStock, if possible, so I would appreciate any assistance.
> >  Does anyone
> > know of an add-in that's available that would provide array or table
> > capabilities to MetaStock?
> >
> > Thanks for any help.
> >
> > Guy
> >
> > Paranoia...you only have to be right once to make it all worthwhile!
> >
> >
> >
>