-
Notifications
You must be signed in to change notification settings - Fork 2
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
InterpretationEngine v0.1.0 #6
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
Plan is to merge this and continue refining documentation, examples, vignettes in another PR for actual v0.1 release. Everything changed in this PR is backward compatible based on my testing. |
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 is draft PR for a v0.1.0 release of InterpretationEngine. With these additions it will be at least theoretically possible to fully evaluate primary rules provided input property data are available.
initRuleset()
now links hedge and operator functions to nodes of the rule setCVIRLinear()
fix for certain specifications of linear function, update example.NULL_NOT_RATED()
hedge function usesNaN
to represent "Not rated"interpret()
method for a data.tree ruleset using either data.frame or SpatRaster input for property dataTODO:
interpret()
propdata needs to be handled