Stefano Alberto Russo
Stefano Alberto Russo
Hi, commit 61d9845 introduced loguru, but it seems to me that right now it's just using Python root logger under the hood, as it might not be properly set up...
I am developing a Python [library](https://github.com/sarusso/Timeseria) for time series data analysis and I embedded a custom plotting engine with HTML and Javascript, based on [Dygraphs](https://dygraphs.com/). Last time I checked my...
Both in the Series/TimeSeries and in the transformations module. Plus check the "process" function and how it is used together with the "target" thing.
Both in Series/TimeSeries and in the operations module.
Indexes can be present, not present. If present, can have a value or a None. A time serie has a given index if it is present for (at least?) one...
E.g. `Forecaster(model_data_path)` but model data was dumped (saved) from a reconstructor, not a forecaster. Maybe just issue a warning?
To dig in: - `series.autodetected_sampling_interval` vs `series.resolution` vs `series.sampling_interval` - `plot(height)` vs `plot(max_y)` vs `plot(y_range)` Naming conventions at the moment: - **timestamp** (time stamp not present at all) - **timezone**...
Considerations: - Append results (unless we are before the first timeseries start point) - Handle missing slots until the requested end (end_dt), but it might clash with the idea of...