Re: [scikit-learn] scikit-learn Digest, Vol 41, Issue 21

[Mike Smith]

Hi,

I have been scouring around everywhere to volunteer. I took a one month
python course from a training company that promised me a job in two months
but they're still working on it after 3. So I decide to volunteer. I'm
looking to use python with DS, ML, AI, etc, I love neural nets, then it hit
me that I get the scikit mailing list and opened it up and you guys are
talking about volunteers. I would love to volunteer for scikit. But I just
have one month training in python. I have prior experience with java and
javascript, some computer science education, How can I start volunteering?

On Mon, Aug 26, 2019 at 9:03 AM  wrote:

> Send scikit-learn mailing list submissions to
> scikit-learn@python.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.python.org/mailman/listinfo/scikit-learn
> or, via email, send a message with subject or body 'help' to
> scikit-learn-requ...@python.org
>
> You can reach the person managing the list at
> scikit-learn-ow...@python.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of scikit-learn digest..."
>
>
> Today's Topics:
>
>1. Re: Monthly meetings between core developers + "Hello World"
>   (Nicolas Hug)
>
>
> --
>
> Message: 1
> Date: Mon, 26 Aug 2019 08:54:21 -0400
> From: Nicolas Hug 
> To: scikit-learn@python.org
> Subject: Re: [scikit-learn] Monthly meetings between core developers +
> "Hello World"
> Message-ID: <136faf1a-5514-1c21-7514-0673b4ddd...@gmail.com>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> Meeting is in 5 minutes everyone! Prepare to be np.random.choice'd? :)
>
> https://appear.in/amueller
> <
> https://www.google.com/url?q=https://appear.in/amueller=D=1566914386036000=AOvVaw2rS1k5NlK35I-_dSoJLgt2
> >
>
>
> On 8/22/19 10:11 AM, Nicolas Hug wrote:
> >
> > Hi Everyone,
> >
> > Quick reminder that the next meeting is on Monday! *Please update your
> > cards on the project board* so we can all have a look before the
> week-end.
> >
> > We decided to go for a "scrum-like" approach this time: quickly go
> > through everyone's notes first, then discuss main issues.
> >
> > Anyone interested in hosting? I think we should have a new person each
> > time, or you'll soon be fed up with me. If nobody speaks up I'll
> > np.random.choice someone on Monday ;)
> >
> > 
> >
> > Time and date:
> >
> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2019=8=26=13=0=0=240=33=37=179
> >
> > Project board:
> > https://github.com/scikit-learn/scikit-learn/projects/15
> > <
> https://www.google.com/url?q=https://github.com/scikit-learn/scikit-learn/projects/15=D=1566914386036000=AOvVaw15duAHoylKYpdBsYgogoOQ
> >
> >
> > Meeting link: https://appear.in/amueller
> > <
> https://www.google.com/url?q=https://appear.in/amueller=D=1566914386036000=AOvVaw2rS1k5NlK35I-_dSoJLgt2
> >
> >
> >
> > See you on Monday!
> >
> > Nicolas
> >
> >
> > On 8/5/19 10:31 AM, Andreas Mueller wrote:
> >> As usual, I agree ;)
> >> I think it would be good to call out particularly important bugfixes
> >> so they get reviews.
> >> We might also want to think about how we can organize the issue
> >> tracker better.
> >>
> >> Having more full-time people on the project certainly means more
> >> activity but ideally we can use some of that time to make the issue
> >> tracker more organized.
> >>
> >>
> >> On 8/5/19 9:21 AM, Joel Nothman wrote:
> >>> Yay for technology!?Awesome to see you all and have some matters
> >>> clarified.
> >>>
> >>> Adrin is right that the issue tracker is increasingly overwhelming
> >>> (because there are more awesome people hired to work on the project,
> >>> more frequent sprints, etc). This meeting is a useful summary.
> >>>
> >>> The meeting mostly focussed on big features. We should be careful to
> >>> not leave behind important bugs fixes and work originating outside
> >>> the core devs.
> >>>
> >>> Despite that: Some of Guillaume's activities got cut off. I think it
> >>> would be great to progress both on stacking and resampling before
> >>> the next release.
> >>>
> >>> I also think these meeting

[scikit-learn] Forest Decision path

[Surya D]

Hello! I am Surya, a student of the machine learning world. I am currently
working on a project to obtain the values of nodes that are parents of the
leaf nodes in the decision path of each tree. I have seen stack overflow
and have tried out the solutions but for my project, it is not fast enough.
Is there any other way I can access the “values” in these parent nodes?


Regards
Surya Dheeshjith
___
scikit-learn mailing list
scikit-learn@python.org
https://mail.python.org/mailman/listinfo/scikit-learn

Re: [scikit-learn] Monthly meetings between core developers + "Hello World"

[Nicolas Hug]

Meeting is in 5 minutes everyone! Prepare to be np.random.choice'd  :)

https://appear.in/amueller 




On 8/22/19 10:11 AM, Nicolas Hug wrote:


Hi Everyone,

Quick reminder that the next meeting is on Monday! *Please update your 
cards on the project board* so we can all have a look before the week-end.


We decided to go for a "scrum-like" approach this time: quickly go 
through everyone's notes first, then discuss main issues.


Anyone interested in hosting? I think we should have a new person each 
time, or you'll soon be fed up with me. If nobody speaks up I'll 
np.random.choice someone on Monday ;)




Time and date: 
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2019=8=26=13=0=0=240=33=37=179


Project board: 
https://github.com/scikit-learn/scikit-learn/projects/15 



Meeting link: https://appear.in/amueller 




See you on Monday!

Nicolas


On 8/5/19 10:31 AM, Andreas Mueller wrote:

As usual, I agree ;)
I think it would be good to call out particularly important bugfixes 
so they get reviews.
We might also want to think about how we can organize the issue 
tracker better.


Having more full-time people on the project certainly means more 
activity but ideally we can use some of that time to make the issue 
tracker more organized.



On 8/5/19 9:21 AM, Joel Nothman wrote:
Yay for technology! Awesome to see you all and have some matters 
clarified.


Adrin is right that the issue tracker is increasingly overwhelming 
(because there are more awesome people hired to work on the project, 
more frequent sprints, etc). This meeting is a useful summary.


The meeting mostly focussed on big features. We should be careful to 
not leave behind important bugs fixes and work originating outside 
the core devs.


Despite that: Some of Guillaume's activities got cut off. I think it 
would be great to progress both on stacking and resampling before 
the next release.


I also think these meetings should, as a standing item, note the 
estimated upcoming release schedule, to help us remain aware of that 
cadence.


Good night!

J

___
scikit-learn mailing list
scikit-learn@python.org
https://mail.python.org/mailman/listinfo/scikit-learn



___
scikit-learn mailing list
scikit-learn@python.org
https://mail.python.org/mailman/listinfo/scikit-learn
___
scikit-learn mailing list
scikit-learn@python.org
https://mail.python.org/mailman/listinfo/scikit-learn