Include an adoption notice in the deprecation warning?
On Sun, Dec 1, 2013 at 12:49 AM, Gael Varoquaux <
[email protected]> wrote:
> Our poor homeless HMMs. Nobody wants them :)
>
> G
>
>
> --
> Rapidly troub
Our poor homeless HMMs. Nobody wants them :)
G
--
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. Wi
On 11/30/2013 01:53 PM, Lars Buitinck wrote:
> 2013/11/30 Vlad Niculae :
>> seqlearn uses a different API on purpose though (one big ndarray),
>> whereas pystruct uses lists of arrays but is only focused on
>> max-margin learning :)
> And seqlearn only does supervised learning.
>
as does pystruct ;
2013/11/30 Vlad Niculae :
> seqlearn uses a different API on purpose though (one big ndarray),
> whereas pystruct uses lists of arrays but is only focused on
> max-margin learning :)
And seqlearn only does supervised learning.
--
seqlearn uses a different API on purpose though (one big ndarray),
whereas pystruct uses lists of arrays but is only focused on
max-margin learning :)
On Sat, Nov 30, 2013 at 12:38 PM, Gael Varoquaux
wrote:
> +1 on the whole thread.
>
> I was hoping that Lars's seqlearn could be a home for poor H
+1 on the whole thread.
I was hoping that Lars's seqlearn could be a home for poor HMMs.
--
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how applicat
> I guess remove means deprecate, right?
> I am +1 but we should definitely find a place for the code. Worse case
> it will be a repo with containing just the HMM.
My thoughts exactly; my impression is that people do find the code
useful and it's reasonably readable. It should definitely go into
On 11/30/2013 12:23 PM, Lars Buitinck wrote:
> 2013/11/30 Kyle Kastner :
>> Does anyone have a consolidated list of API issues with HMM? I have been
>> working with them recently and would be willing to try and work it into
>> better shape, unless core devs would rather have it removed.
> The API o
2013/11/30 Kyle Kastner :
> Does anyone have a consolidated list of API issues with HMM? I have been
> working with them recently and would be willing to try and work it into
> better shape, unless core devs would rather have it removed.
The API of the HMMs is fundamentally different from all othe
Hi Florian,
The documentation should be more explicit. What you missed was that:
preprocessor : callable or None (default)
Override the preprocessing (string transformation) stage while
preserving the tokenizing and n-grams generation steps.
means setting this parameter will
10 matches
Mail list logo
