Skip to content

Difference between default moving average declared in .fit() and find_start cause problem #29

Description

@kmc026

Moving average declared in the .fit() : 1 #fit(...moving_average=1,...)
Moving average declared in find_start : 6 #find_start(...ma_window=6)

Compile rate when using .fit (Moving average 1 ) onto a data size of 653 :
318/653 (49%)
Compile rate when using find_start (Moving average 6 ), find_end_baseline, SARIMAX_predictor, calc_resid onto a filtered data size of 537 :
514/537 (96%)

Note: .fit and au3_functions yield different results because of differences between moving averages

Suggestion: change default moving average value
Suggestion 2: warnings to remind users to change input parameters including the start andend dates, or ma when code does not compile

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions