forked from petersen-f/jaspPredictiveAnalytics
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes future prediction and other bugs #19
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- added error message when covariates but no training indicator was added - added periodical based prediction of no training indicator and no covariates are selected
- bma result object was indexed wrong and caused error - additionally prediction plot now possible with one model only
This commit is a bit large. But in summary the following things have been changed fixed: - warning of no training indicator is adjusted so that it doesn't show when verification only is selected - available models are not picked via R function anymore but instead through JS function -> this makes them appear immediately and fixed some bugs with them disappearing - fixed bug where BMA predictions were not plotted for forecast verification - added note to future predictionplot that warns user to select the proper period unit and frequency - fixed some qml dependencies for enabling future plots and bma - fixed bug where prophet was unable to detect weekly seasonality (i disabled it for some reason in the past)
fixes reporting mode message, depenencies and adds warning message for periodical prediction, removes non-working featEng options
petersen-f
commented
Nov 8, 2023
- previously the selected prediction models disappeared in-between saves and reopening of the jasp file - by calculating the available/possible models in an invisible availableVariableList, and then using this as a source for another variable list, the models stay selected - i also added months to the periodical prediction
- when training window/data has no variance, error is added as bsts and lmSpike package don't work then - added error when added lagged dependent variable values exceed training window - fixed error with evaluation plan function and plot slice order
vandenman
requested changes
Nov 30, 2023
@vandenman Thank you Don! I indeed found more examples where I did this wrong... But I fixed every gettext now. |
vandenman
approved these changes
Dec 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR mainly fixes the prediction and adds options to make sure user can always predict the future as well as minor bugs: