forecastscope
Finite-prefix forecasts, temporal combinations of reference experts, and sequence
diagnostics in a reusable Python library. The core requires NumPy. Diagnostic
implementations use optional scientific packages through forecastscope.diagnostics.
Release availability is recorded on PyPI and GitHub. Application adoption is a separate step. The extraction preserves numerical equations while adding strict public request and output validation, lint normalization and warnings for unavailable optional diagnostics. It makes no new forecast accuracy, calibration, chaos-identification or operational-performance claim.
import numpy as np
from forecastscope import combine, forecast
history = 20 + np.tile([1., 4., 2., 3.], 30)
columns = forecast("HoltWinters", history, seasonality=4, horizon=8)
allocation = combine("ValidationMix", history, seasonality=4, horizon=8)
print(columns.shape, allocation.weights, allocation.origins)
The caller supplies a contiguous observed history; raw arrays contain no timestamps, so contiguity itself is a caller precondition. Future targets belong to the caller's evaluation protocol. NaNs, infinite values, fractional horizons, invalid seasonal lags and unsupported probability grids are refused by the public entry points. The reference kernels preserve their documented short-history policies, including Holt fallback when additive seasonal smoothing lacks two cycles or has lag one. Combination experts can consequently coincide on a nonseasonal input. The five reference experts use approximate Gaussian residual intervals; ordered columns do not establish calibration. Temporal validation filters an outer-prefix-defined historical grid, and does not reconstruct the exact grid a historical service would have proposed at every earlier date.
The fixed contextual combination has an unfavorable comparison with its matching recency control in its original development study. Later validation-selected combinations have bounded point-score improvements on specified external collections, with stronger automatic-method and interval-score comparisons retained. The package does not turn those studies into a general superiority claim.
For diagnostics, install the diagnostics extra and import the topic module, for
example forecastscope.diagnostics.sequence.matrix_profile. Diagnostics describe
their supplied sequence and can be retrospective. They must not be computed on a
future block and then treated as prefix-only model-selection inputs.
The source origin and exact input hashes are recorded in docs/extraction-source.json. The originating software is MIT licensed; its copyright and licence remain in this repository. Application cases, generator seeds, source CSVs, artifact schemas, pipeline stages and web assets are outside this library. See the extraction boundary.
Metadata
Release files for forecastscope 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| forecastscope-0.1.0.tar.gz | 70.1 kB | With provenance | Details for forecastscope-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| forecastscope-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for forecastscope-0.1.0-py3-none-any.whl |
Total release size: 127.5 kB
Release files / forecastscope-0.1.0.tar.gz
| Download URL | forecastscope-0.1.0.tar.gz |
|---|---|
| Size | 70.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c7fd0ddc5e6f4b441bff2d649c9122589d133220c4cd95d9a63cbfac98dfdd66
|
|
BLAKE2b-256 checksum How to use checksums |
9212025eb2341b0d5b8689ebc0c7efad0f0b0954a1027d605dbeddee3bc1b34c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logRelease files / forecastscope-0.1.0-py3-none-any.whl
| Download URL | forecastscope-0.1.0-py3-none-any.whl |
|---|---|
| Size | 57.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1ad7ccd3c63edaa94c3ffb95f4c2ae06b682560cc65222b7ed76622c93b979b8
|
|
BLAKE2b-256 checksum How to use checksums |
21371a4dce6a1a3152c3f4a7afcfdc9bb314b628af2df19de71a90fcb58a9839
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logSecurity for forecastscope 0.1.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for forecastscope-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2026.
Transparency logA 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.