Best practices for FEAT_DYNAMIC_REAL in DeepAR #1705
-
Hello, I have a question on FEAT_DYNAMIC_REAL. As per documentation and comments by folks including committers and my experience as well, we would need to have a known future values for any feature we use as part of the said field name. My questions are:
I really wished there was a Wiki on this repo where we could collate these best practices, it would definitely help out other folks. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi @vikasmalhotra08, Thank you for your interest in GluonTS. Imputing future The mean reason why there isn't a document that shows best practices in this case is that there is not really best practice for it (to the best of my knowledge). Currently, I'm also not quite sure that using I might be wrong here, of course :-). |
Beta Was this translation helpful? Give feedback.
Hi @vikasmalhotra08,
Thank you for your interest in GluonTS.
Imputing future
feat_dynamic_real
with mean values does not work very well in my experience. I think it is plausible that it works if you have a feature that does not change much in the prediction range.The mean reason why there isn't a document that shows best practices in this case is that there is not really best practice for it (to the best of my knowledge). Currently, I'm also not quite sure that using
feat_dynamic_real
with unknown values in the future is useful. In a way, you make your problem harder because now you have to solve multiple forecast problems (the forecast of your target plus the forecast of your features) …