[FEAT] Automatic Statistical Forecasting

[AzulGarza]

Description

This PR adds the autoselect command to perform automatic statistical forecasting. The command fits a set of statistical models and evaluates them to select the best-performing model. Forecasts are generated using the best model.

• Summary of the change / bug fix.
• Link # issue, if applicable.
• Screenshot of the feature or the bug before/after fix, if applicable.
• Relevant motivation and context.
• List any dependencies that are required for this change.

How has this been tested?

• Please describe the tests that you ran to verify your changes.
• Provide instructions so we can reproduce.
• Please also list any relevant details for your test configuration.

• Make sure affected commands still run in terminal
• Ensure the SDK still works
• Check any related reports

Checklist:

• Update our Hugo documentation following these guidelines.
• Update our tests following these guidelines.
• Make sure you are following our CONTRIBUTING guidelines.
• If a feature was added make sure to add it to the corresponding scripts file.

Others

• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.

[martinb-ai]

@FedericoGarza This is quite cool! Thanks so much for this!

Thinking about user experience and look now:

• Could we maybe think of a better name for the command? autostatsforecast is not really descriptive. Especially when this is already the forecast menu and the command is under timeseries forecasting. This is doing a model selection for the users, so think about how you want to name that 😄
• make the command string shorter
• the description should be a little more summarized so it can fit on a single line: Here is how it looks on my pc at the moment.

Also somewhat unrelated: When I did not make a new env and just pulled changes to run I got the following:

This is completely resolved with creating an new env and updating all libs. I know many users do not update their lib every time they pull latest from the repo. Do you think we can add in a try catch on your imports to allow users to still run the menu in case they havent updated and give them a warning message to update their env for statsforecast dependancies?
Something to think about :)

Thanks so much for this! Looking forward to get this in the menu

[AzulGarza]

hey @martinb-bb! Thanks for reviewing the PR. I've updated the name of the command to beststatsmodel. I've also included the try-except behavior you proposed. Let me know what you think. Thank you! :)

[martinb-ai]

@FedericoGarza as discussed, changing beststatsmodel --> autoselect

Then ready to merge :)

[AzulGarza]

hey @martinb-bb! I've changed the name of the command to autoselect :)