| ▲ | Show HN: Python SDK – forecasting with foundation time-series and tabular models(github.com) |
| 33 points by ChernovAndrei 5 days ago | 11 comments |
| We’ve built a Python SDK for running inference on foundation models designed for time-series and tabular data. They are new SOTA models for time-series and tabular tasks and work out of the box. They do not require model training or feature engineering. The link to the GitHub repository is:
https://github.com/S-FM/faim-python-client |
|
| ▲ | smallnix 9 minutes ago | parent | next [-] |
| Before picking this I would benchmark on my existing data using e.g. https://unit8co.github.io/darts/index.html#regression-models |
|
| ▲ | bvan an hour ago | parent | prev | next [-] |
| Isn’t this the ultimate black box? If a forecasting system is a black box, then you have no chance of understanding why its performance might deteriorate. Once that happens it essentially becomes a digital paper-weight. |
|
| ▲ | srean 4 hours ago | parent | prev | next [-] |
| I will always advise "start simple" https://news.ycombinator.com/item?id=46055919 |
| |
| ▲ | anshumankmr 2 hours ago | parent [-] | | >We have successfully replaced thousands of complicated deep net time series based anomaly detectors at a FANG with statistical (nonparametric, semiparametric) process control ones. They use 3 to 4 orders lower number of trained parameters and have just enough complexity that a team of 3 or four can handle several thousands of such streams. Could you explain how ? Cause I am working on this essentially right now and it seems management is wanting to go the way of Deep NNs for our customers. | | |
| ▲ | srean 36 minutes ago | parent [-] | | Without knowing details it's very hard to give specific recommendations. However if you follow that thread you will see folks have commented on what has worked for them. In general I would recommend get Hyndman's (free) book on forecasting. That will definitely get you upto speed. https://news.ycombinator.com/item?id=46058611 Wishing you the best. If it's the case that you will ship the code over client's fence and be done with it, that is, no commitments regarding maintenance, then I will say do what the management wants. If you will continue to remain responsible for the ongoing performance of the tool then you will be better if choosing a model you understand. |
|
|
|
| ▲ | SubiculumCode 11 hours ago | parent | prev | next [-] |
| I do not understand how time series can be forecast without training on data from a relevant domain. Like, would these be able to predict EEG/fMRI timeseries? |
| |
| ▲ | armcat 7 hours ago | parent [-] | | The promise is similar to LLMs, if you pretrain on sufficiently large timeseries datasets with sufficiently large variance/characteristics, that you will be able to transfer the model to a completely different use case that exhibits somewhat similar characteristics (in latent space). But it’s always good to check what kind of data the model was trained on, eg Chronos 2.0 training data is described in Appendix A Table 6 here: https://arxiv.org/pdf/2510.15821 |
|
|
| ▲ | kavalg 2 hours ago | parent | prev | next [-] |
| It looks like this is an SaaS with an open source client only right? |
|
| ▲ | clickety_clack 4 hours ago | parent | prev | next [-] |
| If these worked we would have heard a lot more about them. |
|
| ▲ | anshumankmr 2 hours ago | parent | prev | next [-] |
| How does next-token prediction work for time series data? |
|
| ▲ | BobSonOfBob 7 hours ago | parent | prev [-] |
| Would be good if the site had a couple of case studies |
