This message was deleted.
# neural-forecast
s
This message was deleted.
c
Hi @Chris Gervais! Yes, this is by design. All features should be pre-processed before passing them to the models. Can you provide more details on what issues do you have with the encoded features?
You can set scaler_type to None to remove scaling, to identify if this is the issue.
c
sure yah, so for example we're taking a column of data representing hour of day (1-24) and converting those to dummy variables via hot encoding. but in the example re: exogenous the variable
weekday
doesn't get hot encoded before passing it to the model
c
In this example we didn't one hot encoded the variable, but it should work (run) in both cases
c
circling back on this - it wasn't the encoding, we had gaps in our y values. but that brings me to another question - is it possible to create a future df that doesn't rely on "current" y values?
example: fitting to 2022 hourly data and using it to forecast Feb 9th 2023, without having access to y values from Jan 1 - Feb 8th 2023
moving this to general chat to avoid overthreading this haha sorry