You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if an analyzer requires input from more than one previous analyzer, the workflow requires multiple calls to get_data(). For example, interval n-grams go like this:
Considering how common this type of workflow is, this is really more complicated than it should be. Worse, it really isn't obvious why this is the case. IndexedPiece objects should be able to do this multiplexing by themselves, as in this example:
Wow. It's so much simpler! Please develop this on a feature branch, since I'm hoping to keep master stable in preparation for the formal release of VIS 2.0.
The text was updated successfully, but these errors were encountered:
Currently, if an analyzer requires input from more than one previous analyzer, the workflow requires multiple calls to get_data(). For example, interval n-grams go like this:
Considering how common this type of workflow is, this is really more complicated than it should be. Worse, it really isn't obvious why this is the case. IndexedPiece objects should be able to do this multiplexing by themselves, as in this example:
Wow. It's so much simpler! Please develop this on a feature branch, since I'm hoping to keep master stable in preparation for the formal release of VIS 2.0.
The text was updated successfully, but these errors were encountered: