You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The results of the forecasting simulations are shown from many different perspectives. This is a screenshot of the "fixed horizon perspective":
However, those simulation results are not saved in the workspace. It is not saved for efficiency reasons, so technically this is not a bug. Although the nowcasting plug-in makes it straightforward to simulate real-time forecasts over a period of time, it could take hours if the evaluation sample is large and the model parameters are re-estimated many times. Thus, it would be very convenient that users would be able to save the results of a simulation in the workspace. This would also simplify the comparison of results accross different models models, which could be all saved in the same workspace.
Three possible solutions:
Store all the information in the workspace
Store in the workspace only the parameters resulting from each recursive estimation
Store the necesary information outside the workspace and load it only when requested by the user
The text was updated successfully, but these errors were encountered:
The results of the forecasting simulations are shown from many different perspectives. This is a screenshot of the "fixed horizon perspective":
However, those simulation results are not saved in the workspace. It is not saved for efficiency reasons, so technically this is not a bug. Although the nowcasting plug-in makes it straightforward to simulate real-time forecasts over a period of time, it could take hours if the evaluation sample is large and the model parameters are re-estimated many times. Thus, it would be very convenient that users would be able to save the results of a simulation in the workspace. This would also simplify the comparison of results accross different models models, which could be all saved in the same workspace.
Three possible solutions:
The text was updated successfully, but these errors were encountered: