Skip to content

Adding table overview with frequency options, supersedes PR #1092 #1095

Open
yoselalberto wants to merge 21 commits into
Nixtla:mainfrom
yoselalberto:expand_pr_1009
Open

Adding table overview with frequency options, supersedes PR #1092 #1095
yoselalberto wants to merge 21 commits into
Nixtla:mainfrom
yoselalberto:expand_pr_1009

Conversation

@yoselalberto

@yoselalberto yoselalberto commented Feb 16, 2026

Copy link
Copy Markdown

Problem: the freq parameter in StatsForecast is critical, yet there is no reference table; I created a frequency reference table and I added it to the Getting Started guides for both Pandas and Polars; this PR hopes to reduce friction while using StatsForecast.

In addition, I am thinking about creating a post with a getting started guide with examples for various frequency options, and a section with troubleshooting guide for common frequency errors; what do you think about that @nasaul @MMenchero? are you willing to add a new post?

Supersedes PR #1092 by @W057; closes issues #996, and it is related to #986.

Notes: I updated the PR, integrating the latest changes in main; in addition, I updated datasetsforecasts install, now it is resolved from PyPI instead of git

W057 and others added 3 commits February 12, 2026 14:38
The documentation described freq as "a string indicating the frequency"
but it also accepts an integer for integer-indexed time series.

Closes Nixtla#986
@review-notebook-app

Copy link
Copy Markdown

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

@yoselalberto

yoselalberto commented Feb 16, 2026

Copy link
Copy Markdown
Author

below is an screenshot of the changes, they are almost identical in both Pandas and Polars:
image

@yoselalberto

yoselalberto commented Feb 16, 2026

Copy link
Copy Markdown
Author

I rendered the documents with the changes locally, everything seems to be fine:

@yoselalberto

Copy link
Copy Markdown
Author

I rendered the documents with the changes locally, below are screenshots, everything seems to be fine:
image
image

@codspeed-hq

codspeed-hq Bot commented Feb 19, 2026

Copy link
Copy Markdown

Merging this PR will not alter performance

✅ 6 untouched benchmarks


Comparing yoselalberto:expand_pr_1009 (37dd9b1) with main (65569e1)

Open in CodSpeed

@yoselalberto

Copy link
Copy Markdown
Author

Hello Nixtla, thanks for your attention; after examining the failed CI/CD jobs I added the following changes:

1.- build-docs job: I specified the full quarto version used to build the docs, as required

2.- test-m3-performance job: I pulled the latest version of datasetsforecast from github, which fixes the m3 downloading; and added local functions to calculate the losses, as those imported from from utilsforecast.losses were failing because they now expect dataframes instead of numpy.arrays

@yoselalberto

Copy link
Copy Markdown
Author

Hello Nixtla, good afternoon

I noticed that statsforecast was updated, I will incorporate the latests changes, and update the PR so that it integrates smoothly

@yoselalberto

Copy link
Copy Markdown
Author

I integrated the latest changes in main, now it should merge smoothly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants