On Mar 5, 2011, at 2:13 PM, Jörn Kottmann wrote: > I actually tried to ask how you would do that. I don't think it is super > simple. Can you please shortly > explain what you have in mind?
From the looks of it, we'd just need to return the bestSequence object (or some larger containing object) out to the user and not use it (or other pieces that may change) as a member variable. Granted, I'm still learning the code, so I likely am misreading some things. From the looks of it, though, simply changing the tag method to return the bestSequence would let the user make the appropriate calls to best outcome and to get the probabilities (or the probs() method could take in the bestSequence object if you wanted to keep that convenience) I suppose I should just work up a patch, it would be a lot easier than discussing it in the abstract. >> My bigger question is what is the cost of creating the objects that wrap the >> models? > Do you mean the POSModel? Do you think its too slow ? I don't think it makes > a big difference > compared to the way it was done until 1.5. Model loading time is also not a > problem for > most of our users, because it is only done once on start up. Is it an issue > for you when model > loading takes a few seconds? Right, the model loading time is likely not an issue in most cases since that is a one time thing, I'm asking about the heaviness of the objects that take in the model. I suppose the POSTaggerME is an example (it does look like it is pretty lightweight construction-wise.) I guess I can just take them one case at a time. -Grant
