On Sat, Mar 18, 2017 at 8:41 AM, Chris Barker <chris.bar...@noaa.gov> wrote:
> On Fri, Mar 17, 2017 at 4:37 AM, Jaime Fernández del Río < > jaime.f...@gmail.com> wrote: > >> >> - many people that use numpy in their daily work don't know what >> strides are, this was a BIG surprise for me. >> >> I'm not surprised at all. To start with, the majority of users are self-taught programmers that never used something lower level than Python or Matlab. Even talking to them about memory layout presents challenges. > >> - >> >> Based on that experience, I was thinking that maybe a good topic for a >> workshop would be NumPy's memory model: views, reshaping, strides, some >> hints of buffering in the iterator... >> > This material has been used multiple times in EuroScipy tutorials and may be of use: http://www.scipy-lectures.org/advanced/advanced_numpy/index.html Ralf > I think this is a great idea. In fact, when I do an intro to numpy, I > spend a bit of time on those issues, 'cause I think it's key to "Getting" > numpy, and not something that people end up learning on their own from > tutorials, etc. However, in my case, I try to jam it into a low-level > intro, and I think that fails :-( > > So doing it on it's own with the assumption that participant already know > the basics of the high level python interface is a great idea. > > Maybe a "advanced" numpy tutorial for SciPy 2017 in Austin also??? > > Here is my last talk -- maybe it'll be helpful. > > http://uwpce-pythoncert.github.io/SystemDevelopment/scipy.html#scipy > > the strides stuff is covered in a notebook here: > > https://github.com/UWPCE-PythonCert/SystemDevelopment/ > blob/master/Examples/numpy/stride_tricks.ipynb > > other notebooks here: > > https://github.com/UWPCE-PythonCert/SystemDevelopment/ > tree/master/Examples/numpy > > and the source for the whole thing is here: > > https://github.com/UWPCE-PythonCert/SystemDevelopment/ > blob/master/slides_sources/source/scipy.rst > > > All licensed under: Creative Commons Attribution-ShareAlike -- so please > use anything you find useful. > > -CHB > > > > And Julian's temporary work lends itself to a very nice talk, more on >> Python internals than on NumPy, but it's a very cool subject nonetheless. >> >> So my thinking is that I am going to propose those two, as a workshop and >> a talk. Thoughts? >> >> Jaime >> >> On Thu, Mar 9, 2017 at 8:29 PM, Sebastian Berg < >> sebast...@sipsolutions.net> wrote: >> >>> On Thu, 2017-03-09 at 15:45 +0100, Jaime Fernández del Río wrote: >>> > There will be a PyData conference in Barcelona this May: >>> > >>> > http://pydata.org/barcelona2017/ >>> > >>> > I am planning on attending, and was thinking of maybe proposing to >>> > organize a numpy-themed workshop or tutorial. >>> > >>> > My personal inclination would be to look at some advanced topic that >>> > I know well, like writing gufuncs in Cython, but wouldn't mind doing >>> > a more run of the mill thing. Anyone has any thoughts or experiences >>> > on what has worked well in similar situations? Any specific topic you >>> > always wanted to attend a workshop on, but were afraid to ask? >>> > >>> > Alternatively, or on top of the workshop, I could propose to do a >>> > talk: talking last year at PyData Madrid about the new indexing was a >>> > lot of fun! Thing is, I have been quite disconnected from the project >>> > this past year, and can't really think of any worthwhile topic. Is >>> > there any message that we as a project would like to get out to the >>> > larger community? >>> > >>> >>> Francesc already pointed out the temporary optimization. From what I >>> remember, my personal highlight would probably be Pauli's work on the >>> memory overlap detection. Though both are rather passive improvements I >>> guess (you don't really have to learn them to use them), its very cool! >>> And if its about highlighting new stuff, these can probably easily fill >>> a talk. >>> >>> > And if you are planning on attending, please give me a shout. >>> > >>> >>> Barcelona :). Maybe I should think about it, but probably not. >>> >>> >>> > Thanks, >>> > >>> > Jaime >>> > >>> > -- >>> > (\__/) >>> > ( O.o) >>> > ( > <) Este es Conejo. Copia a Conejo en tu firma y ayúdale en sus >>> > planes de dominación mundial. >>> > _______________________________________________ >>> > NumPy-Discussion mailing list >>> > NumPy-Discussion@scipy.org >>> > https://mail.scipy.org/mailman/listinfo/numpy-discussion >>> _______________________________________________ >>> NumPy-Discussion mailing list >>> NumPy-Discussion@scipy.org >>> https://mail.scipy.org/mailman/listinfo/numpy-discussion >>> >>> >> >> >> -- >> (\__/) >> ( O.o) >> ( > <) Este es Conejo. Copia a Conejo en tu firma y ayúdale en sus planes >> de dominación mundial. >> >> _______________________________________________ >> NumPy-Discussion mailing list >> NumPy-Discussion@scipy.org >> https://mail.scipy.org/mailman/listinfo/numpy-discussion >> >> > > > -- > > Christopher Barker, Ph.D. > Oceanographer > > Emergency Response Division > NOAA/NOS/OR&R (206) 526-6959 voice > 7600 Sand Point Way NE (206) 526-6329 fax > Seattle, WA 98115 (206) 526-6317 main reception > > chris.bar...@noaa.gov > > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > https://mail.scipy.org/mailman/listinfo/numpy-discussion > >
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpy-discussion
