r11424 r11439 2 2 Channels and Tokens 3 3 ################### 4 4 5 5 Our data sampler widget was, regarding the channels, rather simple 6 6 and linear: the widget was designed to receive the token from one … … 55 55 Notice that everything is pretty much the same as it was with 56 56 widgets from previous lessons, the only difference being 57 :obj:`Multiple + Default` as the last value in the list that defines 58 the :obj:`Learner` channel. This :obj:`Multiple + Default` says 57 ` as the last value in the list that defines 58 the :obj:`Learner` channel. This ` says 59 59 that this is a multi-input channel and is the default input for its type. 60 60 If it would be unspecified then by default value of 61 :obj:`Single + NonDefault` would be used. That would mean that the 61 ` would be used. That would mean that the 62 62 widget can receive the input only from one widget and is not the default input 63 63 channel for its type (more on default channels later). … … 147 147 scoring functions from stats. I rather like 148 148 the easy by which new scoring functions are added to the widget, since 149 all that is needed is the augmenting the list 149 all that is needed is the augmenting the list:: 150 150 151 151 self.scoring = [("Classification Accuracy", orngStat.CA), … … 234 234 That is, the :obj:`Train Data` channel is a single-token 235 235 channel which is a default one (third parameter). Note that the flags can 236 be added (or OR-d) together so :obj:`Default + Multiple` is a valid flag. 236 be added (or OR-d) together so ` is a valid flag. 237 237 To test how this works, connect a file widget to a learning curve widget and 238 238 - nothing will really happen:
Note: See TracChangeset for help on using the changeset viewer.