Skip to main content

fcst

Publish Tag to PyPI

Package repo on PyPI: fcst - PyPI

Installation

uv add fcst

Features

This package provides you with these sub-modules

  1. automation

    This automatically runs back-test, select the best models, and forecast for you. You can customise whether or not to run in parallel, how many top models to select, etc.

  2. forecasting

    This provides you with the basic functionality of fit() and predict(), given that you pass in the model.

  3. evaluation

    This provides you with back-test and model selection functionalities.

  4. preprocessing

    This allows you to prepare your dataframes, preprocess the time-series data, fill in the missing dates automatically.

  5. horizon

    This is an API for dealing with future horizon from sktime. But in some modules, it will also do this automatically.

  6. models

    Gives you the base models for you to work with. Provides you with the basic models, default (fallback) and zero predictor.

  7. metrics

    Our own implementation of forecasting performance metrics.

  8. common

    Other common functionalities, e.g., types.

Usage

Examples

In case you want to automate the whole process...

from fcst.automation import run_forecasting_automation
import pandas as pd


df_input = pd.read_csv("path-to-your/file.csv")

data_period_date = pd.Period("2025-02", freq="M")

# Can support multivariate forecasting
# Just pass in the config
multivar_config = MultiVarConfig(df_X_raw=df_X, feature_cols=["feature_1", "feature_2", "feature_3"])

results = run_forecasting_automation(
    df_raw=df_y,
    value_col="y",
    date_col="date",
    data_period_date=data_period_date,
    forecasting_periods=5,
    id_cols=["id"],
    multivar_config=multivar_config,
)

# Do something with the results
def format_and_upload_results(df_results):
    ...

There are main configs you can customise...

from fcst.common.configs import ForecastingConfig, BacktestingConfig

forecasting_config = ForecastingConfig(top_n=2)
backtesting_config = BacktestingConfig(backtesting_periods=3, eval_periods=4)


df_input = pd.read_csv("path-to-your/file.csv")

data_period_date = pd.Period("2025-02", freq="M")

results = run_forecasting_automation(
    df_raw=df_y,
    value_col="y",
    date_col="date",
    data_period_date=data_period_date,
    forecasting_periods=5,
    id_cols=["id"],
    forecasting_config=forecasting_config,
    backtesting_config=backtesting_config
)

# Do something with the results
def format_and_upload_results(df_results):
    ...

Other utilities for time-series

from fcst.preprocessing import prepare_timeseries


# Group time-series based on customer-product, then yields a generater of (id_, pd.Series)
timeseries = prepare_timeseries(
    df_raw=df_input,
    date_col="date",
    value_col="net_amount",
    data_period_date=data_period_date,
    id_cols=["customer_code", "product_code"],
    min_cap=0,
    freq="M",
    agg_method="sum",
    fillna=0,
)


# Returns the whole DataFrame as a time-series
timeseries = prepare_timeseries(
    df_raw=df_input,
    date_col="date",
    value_col="net_amount",
    data_period_date=data_period_date,
    id_cols=None,
    min_cap=0,
    freq="M",
    agg_method="sum",
    fillna=0,
)

More detailed usage

Automation

This automation sub-module runs cleaning, fill-in the missing dates, evaluation, model selection, forecasting and ensemble, everything automatically.

Preprocessing

This provides time-series preparation functions. The most complete function and does most of the heavy lifting is prepare_timeseries() function. You can import it from from fcst.preprocessing import prepare_timeseries. You can specify ID columns, date column, value column to forecast, the frequency, and much more. This function returns a dictionary where the keys are time-series IDs and the values are the corresponding time-series.

Models

By default the run_forecasting_automation() uses base_models from models. But you can define your own model(s) with fit() and predict() methods. You can get the base_models, fast_models, all_models, or multivar_models and put your own model(s) to the dictionary.

Metrics

By default, we use smape() for measuring accuracy (error) of forecasting models. We define our own as it handles when the forecast or actual values are 0. There are other metrics as well such as: - mape() - mae() - mse() - rmse()

Horizon

If you want to utilise the forecast horizons or get some future dates, this sub-module provides the basic functionalities. And this is the base of forecasting and evaluation functions.

Forecasting

In forecasting sub-module, you can use forecast or ensemble to forecast using one or more models.

Evaluation

The evaluation sub-module provides the back-testing and model selection functions. You can pass in a model dictionary to evaluate which models are suitable for each time-series.

Metadata

Release files for fcst 0.8.11

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for fcst 0.8.11
File Size Uploaded Provenance Actions
fcst-0.8.11.tar.gz 132.7 kB Without provenance Details for fcst-0.8.11.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for fcst 0.8.11
File Interpreter ABI Platform Actions
fcst-0.8.11-py3-none-any.whl Python 3 none any Details for fcst-0.8.11-py3-none-any.whl

Total release size: 161.6 kB

Release files / fcst-0.8.11.tar.gz

Download URL fcst-0.8.11.tar.gz
Size 132.7 kB
Tags Source
SHA-256 checksum
How to use checksums
87ca6346953308202c7a756946267cc08443625b2c71137488203755ae1a0ebb
BLAKE2b-256 checksum
How to use checksums
7aa07d5092ef101e520a1f41f564f9889c5dddd80657bd6e2b257296962212cf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.5.11

Release files / fcst-0.8.11-py3-none-any.whl

Download URL fcst-0.8.11-py3-none-any.whl
Size 28.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
148034bbf041ac5725a876ce7720449eea106d87be4bb263d3f28ba55699440c
BLAKE2b-256 checksum
How to use checksums
6f0025b2e643150deb9bb815c4aa6621ef5b5c0b9fcd0af2dbf219bcb9ba1f9c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.5.11

Security for fcst 0.8.11

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page