Updated WriteprintsAnalyzer documentation
Fixed a bug where classifiers wouldn't reset properly after switching
from WriteprintsAnalyzer to any other classifier. NOTE: This still does
not allow WriteprintsAnalyzer to be in the queue with any other
classifier. It just means that loading one queue, emptying it, and
building a new one works as it should even if one of those queues
includes the WriteprintsAnalyzer