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

RE: Quote Plus evaluation on Metastock list



PureBytes Links

Trading Reference Links

Alain,

how bout sharing the source code.

Sean

> -----Original Message-----
> From: owner-metastock@xxxxxxxxxxxxx
> [mailto:owner-metastock@xxxxxxxxxxxxx]On Behalf Of Alain JOSSART
> Sent: Saturday, November 07, 1998 1:10 AM
> To: Gary Lyben
> Cc: metastock@xxxxxxxxxxxxxxxxxx
> Subject: Quote Plus evaluation on Metastock list
>
>
>
> Gary,
>
> Sorry and apologies about this mistake.
>
> I had decided to address the list first because QP2 data service is quite
> familiar for the members and it was hence a good place to confirm/deny my
> tentative analysis before signaling a problem to Quote Plus. The 'suspect
> record' definition was extensive for the reason Alain Jossart was not sure
> himself about the check.
>
> It's a mistake because I should have integrated that the DLL
> could possibly
> offer a different data view than the user's view from QP charting program,
> Metastock or Quote Plus Virtual, ie that list members could possibly not
> sort my confusion anyway. This was not impolite in the intention, I do
> apologize if the contents was ambiguous.
>
> I will continue the analysis with Quote Plus privately from this
> point. Let
> just say that (1) a first batch of "errors" disappeared after handling of
> holidays but I had already corrected this point, (2) the huge majority of
> "errors" is zero volume, which corresponds indeed first (in
> importance)  to
> a data vendor convention and second to a real problem, ie that it's not a
> rare case that QP data does show zero volume (ie no trading) when
> Equis/i-Soft does show V>O and correct OHLC, (3) invalid OHLC errors are
> present, altough certainly not more than from Momentum or Equis data CD,
> and (4) some 0 date records were really detected by the DLL, the case
> (security) I verified more toroughly showed no 0
> Date records via QP Virtual/Metastock, however the QP charting module does
> display 0 records (ie that apparently not traded days where stored as
> date=OHLCV=0 instead of propagating the last traded close with 0 volume).
> My 'suspect record' definition must be corrected further also : some
> indices in daily stocks database do not contain Open or/and High/Low data.
>
> Anyway, let's sort all this privately and send a deny/confirmation report
> to the list later as applicable.
> Sorry again for the public mistake. Alain.
>