-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
5 changed files
with
33 additions
and
7 deletions.
There are no files selected for viewing
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
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
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
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
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
05f27f2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here's an initial stab at #5
A few things I'm unsure about:
ConformalModel <: MMI.Model
for which the compulsoryMMI.fit
andMMI.predict
will be implemented. Subtypes then only need to implement generic methods that are relevant to how exactly conformal prediction is implemented (like here). The idea is that this way the compulsory methods don't have to be defined each time for each different conformal predictor. The motivation is that this should make it easier for contributors to add new conformal predictors. With respect to fitting, this seems to be working well: I can wrap both theNaiveConformalRegressor
and theLABELConformalClassifier
as a machine and call thefit!
method on it. But perhaps what I have in mind is not a good idea.predict
method, because conformal predictions are interval-/set-valued. In other words, it isn't obvious how to produce predictionsyhat
in the conventional format (e.g.yhat
is a vector ofDistribution
in the case of classification). Not sure how/if these types of predictions can be used for tuning the conformal model. I can always just define a predict function that just calls the underlying model, much like I've done with thefit
method here, but then tuning does not actually address the "conformal" aspect of the predictions.Any guidance would be much appreciated @ablaom 🙏🏽