@@ -84,11 +84,13 @@ appear as an input to training but not to prediction.
84
84
## Data interfaces
85
85
86
86
Algorithms are free to consume data in any format. However, a method called [ ` obs ` ] (@ref
87
- data_interface) (read as "observations") gives users and meta-algorithms access to an
88
- algorithm-specific representation of input data, which is also guaranteed to implement a
89
- standard interface for accessing individual observations, unless the algorithm explicitly
90
- opts out. Moreover, the ` fit ` and ` predict ` methods will also be able to consume these
91
- alternative data representations, for performance benefits in some situations.
87
+ data_interface) (read as "observations") gives developers the option of providing a
88
+ separate data front end for their algorithms. In this case ` obs ` gives users and
89
+ meta-algorithms access to an algorithm-specific representation of input data, which is
90
+ also guaranteed to implement a standard interface for accessing individual observations,
91
+ unless the algorithm explicitly opts out. Moreover, the ` fit ` and ` predict ` methods will
92
+ also be able to consume these alternative data representations, for performance benefits
93
+ in some situations.
92
94
93
95
The fallback data interface is the [ MLUtils.jl] ( https://github.com/JuliaML/MLUtils.jl )
94
96
` getobs/numobs ` interface, here tagged as [ ` LearnAPI.RandomAccess() ` ] ( @ref ) , and if the
@@ -97,6 +99,9 @@ then overloading `obs` is completely optional. Plain iteration interfaces, with
97
99
knowledge of the number of observations, can also be specified, to support, e.g., data
98
100
loaders reading images from disk.
99
101
102
+ Some canned data front ends are provided by the
103
+ [ LearnDataFrontEnds.jl] ( https://juliaai.github.io/LearnAPI.jl/stable/ ) package.
104
+
100
105
## Learning more
101
106
102
107
- [ Anatomy of an Implementation] ( @ref ) : informal introduction to the main actors in a new
0 commit comments