Menu

#12 TA_TRIMA

closed-fixed
None
9
2003-04-20
2003-03-10
Anonymous
No

I believe the inner or outer ranges from which separate
SMA's are calculated are incorrect resulting in out of
bounds read/write.

I ask for TRIMA(4665,4665,10...) and then internal to
TRIMA calls SMA(0,4661,...) for outer and SMA
(4660,4665,...) for inner. Perhaps there is some offset
missing in the outer (either the zero should be offset
upward or the 4661 downward).

Thanks,

Chris
crokusek@hotmail.com

Discussion

  • Mario Fortier

    Mario Fortier - 2003-03-11
    • priority: 5 --> 9
    • assigned_to: nobody --> fortier
     
  • Mario Fortier

    Mario Fortier - 2003-03-11

    Logged In: YES
    user_id=1123

    Thanks Chris.

    Yes, it is broken.

    I could fix it now, but instead I think I will revisit the whole
    algorithm. It is currently innefficient for user doing the
    calculation for one (or just a few) price bar.

    I should be able to provide a working implementation in CVS
    by March 17 (I have a busy week).

    Very good bug report, keep these coming !

    \Mario

    Side Note: I am surprise that my regression testing did not
    catch this. I will see to add a test for this...

     
  • Mario Fortier

    Mario Fortier - 2003-03-18

    Fix for this problem. This will be included in V0.0.8

     
  • Mario Fortier

    Mario Fortier - 2003-03-18
    • status: open --> open-fixed
     
  • Mario Fortier

    Mario Fortier - 2003-03-18

    Logged In: YES
    user_id=1123

    Please find attach a new TA_TRIMA.c file

    The Fix is also now check-in in CVS.

    The FIX will be part of release V0.0.8

    Thanks Chris.

     
  • Mario Fortier

    Mario Fortier - 2003-03-18

    Logged In: YES
    user_id=1123

    Please find attach a new TA_TRIMA.c file

    The Fix is also now check-in in CVS.

    The FIX will be part of release V0.0.8

    Thanks Chris.

     
  • Mario Fortier

    Mario Fortier - 2003-04-20
    • status: open-fixed --> closed-fixed
     

Log in to post a comment.