Support Board
Date/Time: Sat, 15 Mar 2025 04:01:32 +0000
Moving avarage shows differently .
View Count: 383
[2022-07-02 21:47:38] |
bala - Posts: 74 |
I am using Sierra charts standard technical studies- 'Simple Moving avarage' for a period of 200 ( 16 tick chart) (ref: SierraChartStudies_64.scsf_MovingAverageSimple - this uses call 'sc.SimpleMovAvg(sc.BaseDataIn[Input_Data.GetInputDataIndex()], Subgraph_Avg, Input_Length.GetInt());'). I make a custom study using 'sc.MovingAverage(sc.BaseDataIn[Input_Data.GetInputDataIndex()], MV200,MOVAVGTYPE_SIMPLE, MVLR_Length.GetInt());' The standard technical charts studies are very different on the screen compared to the custom study. I would expect them to be the same! I experimented a standard 'Moving Average Crossover' with 200 and 10 ( SierraChartStudies_64.scsf_MovingAverageCrossover) - Now the MA for 200 is similar to mine. Observation: ' sc.SimpleMovAvg(sc.BaseDataIn[Input_Data.GetInputDataIndex()], Subgraph_Avg, Input_Length.GetInt()); ' and 'sc.MovingAverage(sc.BaseDataIn[Input_Data.GetInputDataIndex()], Subgraph_Avg,MOVAVGTYPE_SIMPLE, Input_Length.GetInt());' produce very different results for 200 periods. ( they are close for period for 7) Thanks |
[2022-07-04 18:58:47] |
|
The same internal core calculation function is used in both cases. We do not observe any difference: https://www.sierrachart.com/image.php?Image=1656961079364.png There must be something wrong with your method of analyzing this. Check the underlying data in the chart. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2022-07-04 18:59:14
|
To post a message in this thread, you need to log in with your Sierra Chart account: