From priimak at gmail.com Thu May 2 22:16:33 2019 From: priimak at gmail.com (Dmitri Priimak) Date: Thu, 2 May 2019 19:16:33 -0700 Subject: [Matplotlib-devel] Internals of smooth plotting in matplotlib Message-ID: Hi All. I am writing plotting library in Scala (https://github.com/priimak/splot https://splot-web.github.io/) but I am having difficulty doing smooth plotting when I have a lot of data points. Consider a following use case. Let say along the x-axis I have array of points from 0 to 0.3 with step 0.001 and on y-axis each corresponding point is computed from some function, let say sin(x). Now I want to plot smooth plot using these points. If I just plot corresponding pixels I might have wholes in the image if I zoom in, so that it is not good. If I just poly line (there is such function in java Graphics2D object) based on these points I have another problem. I have to convert each point into onscreen pixel coordinates (I can use floor(..) or rounding to the nearest int when doing it). And that results in jagged step like line that you can see here https://i.imgur.com/t26WDut.png That does not happen in matplotlib when let say using fig.plot(...) function. Output is always smooth which is what I want as well. Is there a particular place in code where I can see how that is done? -- Dmitri Priimak -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Sun May 5 22:52:37 2019 From: tcaswell at gmail.com (Thomas Caswell) Date: Sun, 5 May 2019 22:52:37 -0400 Subject: [Matplotlib-devel] REL: Matplotilb v3.1.0rc2 Message-ID: Folks, Just tagged rc2 which has a hand full of critical fixes - un-deprecated MaxNLocator default_params (this broke down-stream packages) - reverted un-intentional change to install the tests by default - fix saving non FuncAnimation animations - many documentation fixes - fixed bug in zorder of errorbars on barplots - fix bug that caused ticks to disappear in interactive use Will push to pypi as soon as all of the wheels are ready. Tom -- Thomas Caswell tcaswell at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.barker at noaa.gov Mon May 6 13:10:32 2019 From: chris.barker at noaa.gov (Chris Barker - NOAA Federal) Date: Mon, 6 May 2019 17:10:32 +0000 Subject: [Matplotlib-devel] Internals of smooth plotting in matplotlib In-Reply-To: References: Message-ID: Now I want to plot smooth plot using these points. If I just plot corresponding pixels I might have wholes in the image if I zoom in, You really don?t want to do that. so that it is not good. If I just poly line (there is such function in java Graphics2D object) based on these points I have another problem. I have to convert each point into onscreen pixel coordinates (I can use floor(..) I would use round(), but still, drawing in pixel coordinates will result in somewhat jagged lines. The way around that is to use ?antialiased? drawing. I would be shocked if there wasn?t a Java lib for that. Most MPL back-ends use the antigrain library (AGG) which is s particularly good renderer, but any antialiasing renderer should be pretty good. You also mention zooming ? make sure you zoom before converting to pixel coords as well. HTH, -CHB or rounding to the nearest int when doing it). And that results in jagged step like line that you can see here https://i.imgur.com/t26WDut.png That does not happen in matplotlib when let say using fig.plot(...) function. Output is always smooth which is what I want as well. Is there a particular place in code where I can see how that is done? -- Dmitri Priimak _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel at python.org https://mail.python.org/mailman/listinfo/matplotlib-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From priimak at gmail.com Mon May 6 13:17:08 2019 From: priimak at gmail.com (Dmitri Priimak) Date: Mon, 6 May 2019 10:17:08 -0700 Subject: [Matplotlib-devel] Internals of smooth plotting in matplotlib In-Reply-To: References: Message-ID: On Mon, May 6, 2019 at 10:10 AM Chris Barker - NOAA Federal < chris.barker at noaa.gov> wrote: > Now I want to plot smooth plot using these points. If I just plot > corresponding pixels I might have wholes in the image if I zoom in, > > > You really don?t want to do that. > > so that it is not good. If I just poly line (there is such function in > java Graphics2D object) based on these points I have another problem. I > have to convert each point into onscreen pixel coordinates (I can use > floor(..) > > > I would use round(), but still, drawing in pixel coordinates will result > in somewhat jagged lines. > > The way around that is to use ?antialiased? drawing. I would be shocked if > there wasn?t a Java lib for that. > There is but it does not seem to work very well. Certainly not as good as AGG back end. > Most MPL back-ends use the antigrain library (AGG) which is s particularly > good renderer, but any antialiasing renderer should be pretty good. > I see that now. I don't really want to depend on AGG. Perhaps I can re-implement it in Java/Scala. > > You also mention zooming ? make sure you zoom before converting to pixel > coords as well. > Yes, I am doing just that. > HTH, > > -CHB > > > > or rounding to the nearest int when doing it). And that results in jagged > step like line that you can see here > > https://i.imgur.com/t26WDut.png > > That does not happen in matplotlib when let say using fig.plot(...) > function. Output is always smooth which is what I want as well. Is there a > particular place in code where I can see how that is done? > > -- > Dmitri Priimak > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.barker at noaa.gov Mon May 6 21:06:09 2019 From: chris.barker at noaa.gov (Chris Barker - NOAA Federal) Date: Mon, 6 May 2019 21:06:09 -0400 Subject: [Matplotlib-devel] Internals of smooth plotting in matplotlib In-Reply-To: References: Message-ID: > There is but it does not seem to work very well. Certainly not as good as AGG back end. Part of the problem may be that you have to specify coordinates in integers, forcing a rounding even before you draw. One kludgy option is to draw at double resolution, and then rescale the image. > I see that now. I don't really want to depend on AGG. Perhaps I can re-implement it in Java/Scala. I?d look for s better Java rendering lib... -CHB From nelle.varoquaux at gmail.com Wed May 8 14:11:13 2019 From: nelle.varoquaux at gmail.com (Nelle Varoquaux) Date: Wed, 8 May 2019 11:11:13 -0700 Subject: [Matplotlib-devel] REL: Matplotilb v3.1.0rc2 In-Reply-To: References: Message-ID: Thanks! On Sun, 5 May 2019 at 19:52, Thomas Caswell wrote: > Folks, > > Just tagged rc2 which has a hand full of critical fixes > > - un-deprecated MaxNLocator default_params (this broke down-stream > packages) > - reverted un-intentional change to install the tests by default > - fix saving non FuncAnimation animations > - many documentation fixes > - fixed bug in zorder of errorbars on barplots > - fix bug that caused ticks to disappear in interactive use > > Will push to pypi as soon as all of the wheels are ready. > > Tom > > -- > Thomas Caswell > tcaswell at gmail.com > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From johann.arnold at siemens.com Fri May 10 04:49:56 2019 From: johann.arnold at siemens.com (Arnold, Johann) Date: Fri, 10 May 2019 08:49:56 +0000 Subject: [Matplotlib-devel] Matplotlib 2.2.2 - unclear license conditions for _png.cpp Message-ID: <617F0F9AC717D841BF586C83D0DE265E2FC2BF1E@DENBGAT9EJ5MSX.ww902.siemens.net> Dear Matplotlib developers, For one of our products we want to use Matplotlib 2.2.2. In order to distribute our product in a license compliant way we check the licenses of all OSS source code we are using. We do this on an file by file basis. For the file _png.cpp we have not been able to determine license situation. In file header we found the following text: // this code is heavily adapted from the paint license, which is in 4. // the file paint.license (BSD compatible) included in this 5. // distribution. TODO, add license file to MANIFEST.in and CVS 6. 7. /* For linux, png.h must be imported before Python.h because 8. png.h needs to be the one to define setjmp. 9. Undefining _POSIX_C_SOURCE and _XOPEN_SOURCE stops a couple 10. of harmless warnings. We could not find the file "paint.license", i.e. we do not know the correct license for _png.cpp. Can you please help us in order to get the correct license for _png.cpp Thanks a lot in advance and kind regards Johann Arnold Siemens AG Digital Industries Process Automation Software House Nbg DI PA CI R&D 3 Gleiwitzer Str. 555 90475 N?rnberg, Deutschland Tel.: +49 911 895-3162 Fax: +49 911 895-4010 mailto:johann.arnold at siemens.com www.siemens.com/ingenuityforlife [www.siemens.com/ingenuityforlife] Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Jim Hagemann Snabe; Vorstand: Joe Kaeser, Vorsitzender; Roland Busch, Lisa Davis, Klaus Helmrich, Janina Kugel, Cedrik Neike, Michael Sen, Ralf P. Thomas; Sitz der Gesellschaft: Berlin und M?nchen, Deutschland; Registergericht: Berlin Charlottenburg, HRB 12300, M?nchen, HRB 6684; WEEE-Reg.-Nr. DE 23691322 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 3536 bytes Desc: image001.gif URL: From story645 at gmail.com Mon May 13 16:54:29 2019 From: story645 at gmail.com (Hannah) Date: Mon, 13 May 2019 16:54:29 -0400 Subject: [Matplotlib-devel] Documentation Summit Message-ID: The Matplotlib development team is planning a 2 day documentation sprint / summit in Denver for late summer 2019 and have some travel funds. If you are interested in attending (either in person or calling in) please fill out http://bit.ly/docsum19 The purpose of this summit is to: - write a work-plan for 9-12 months of work for a technical writer - including rough outlines, deliverable, and milestones - write a budget (technical writer + core dev time to manage / review) - write short grant to submit to foundations (4-6 pages, ~100k) To achieve these goals, the summit participants will identify problems with the Matplotlib documentation, including: - it is too big to effectively use (over 3k pages of content) - it is incomplete (many methods lack sufficient API documentation and examples) - there is no consistent voice through out the documentation - there is no clear path through the docs - the same content is serving many different audiences - existing users looking for API docs - new-to-python users looking for a "quick start" - new-to-programming/viz, but domain experts - new-to-visualization users starting from scratch - two main audiences: - scientists/user - trying to solve a specific problem as quickly as possible - developer writing visualization apps/ software - looking for detailed API docs and internal logic The participants will then develop a work plan for addressing these issues by hiring a technical writer with a mandate to: - audit and sort the existing documentation - potentially into tutorial, reference, topic and how-to guides - ensure complete coverage of API docs - de-duplicate the examples and tutorials - sort out what the per-requisites are and link appropriately - develop curated "paths" through examples / API doc - develop "quick reference" sheets - develop a template for domain specific intro material - implement several of these? - develop coding and documentation style guides - identify missing tutorials - scrape stackoverflow and otherwise engage with the community to determine what is missing and other such tasks. The technical writer will be expected to work with the developers to cover knowledge gaps. Please reply to this email with questions, comments, complaints, and suggestion and please fill out http://bit.ly/docsum19 if you are interested in attending remotely or in person. Thanks, Hannah -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Fri May 17 22:13:47 2019 From: tcaswell at gmail.com (Thomas Caswell) Date: Fri, 17 May 2019 22:13:47 -0400 Subject: [Matplotlib-devel] REL: v3.1.0 Message-ID: Folks, I (finally) tagged 3.1! Will announce do user list when wheels are built and up. A big thank you to every one on who worked on this! I am particularly thankful to David Stansby and Hannah Aizenman did much of the work colating the API and whats new documentation. Tom -- Thomas Caswell tcaswell at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From nelle.varoquaux at gmail.com Sat May 18 11:14:10 2019 From: nelle.varoquaux at gmail.com (Nelle Varoquaux) Date: Sat, 18 May 2019 08:14:10 -0700 Subject: [Matplotlib-devel] REL: v3.1.0 In-Reply-To: References: Message-ID: Thank you so much, Tom! N On Fri, May 17, 2019, 7:14 PM Thomas Caswell wrote: > Folks, > > I (finally) tagged 3.1! > > Will announce do user list when wheels are built and up. > > A big thank you to every one on who worked on this! I am particularly > thankful to David Stansby and Hannah Aizenman did much of the work colating > the API and whats new documentation. > > Tom > > -- > Thomas Caswell > tcaswell at gmail.com > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Sat May 18 15:25:32 2019 From: tcaswell at gmail.com (Thomas Caswell) Date: Sat, 18 May 2019 15:25:32 -0400 Subject: [Matplotlib-devel] REL: Matplotlib 3.1.0 Message-ID: Folks, We are happy to announce the release of Matplotlib 3.1! Matplotlib 3.1 supports Python 3.6+. Highlights of this release include: - A helper method for scatter legends - Secondary axis support (ex, degrees and radians) - A concise date formatter - No longer requires a framework build of Python to use OSX backend - Major and minor ticks will no longer collide by default - A progress callback for animations - mplot3D is always registered - deprecated mlab functions have been removed - Many function calls have become stricter about invalid or ignored input For the full details see - whats new: https://matplotlib.org/users/whats_new.html - API changes: https://matplotlib.org/api/api_changes.html A big thank you to everyone who worked on this release including the 151 people contributed code [1] and the many more who reported issues. We are planning to have Matplotlib 3.2 released in September/October and Matplotlib 2.2.5 (the final release of the 2.2.x LTS series) in December. Tom [1] https://matplotlib.org/users/github_stats.html -- Thomas Caswell tcaswell at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Sat May 18 18:44:34 2019 From: tcaswell at gmail.com (Thomas Caswell) Date: Sat, 18 May 2019 18:44:34 -0400 Subject: [Matplotlib-devel] pydata events Message-ID: Folks, There are a number of pydata events coming up around the world ( https://pydata.org/events/ ). If you are interested in presenting a talk / tutorial or leading a sprint at any of the events please let me know and we can work with NumFOCUS to get it set up. Tom -- Thomas Caswell tcaswell at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Sat May 18 20:25:32 2019 From: tcaswell at gmail.com (Thomas Caswell) Date: Sat, 18 May 2019 20:25:32 -0400 Subject: [Matplotlib-devel] LTGM github app Message-ID: Folks, I just installed the LGTM github app (moving us from the previous web-hook based version). I'm sorry if this is causing anyone else to get ~30 emails from them about the initial ingesting of each of our repositories. Tom -- Thomas Caswell tcaswell at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Fri May 24 12:04:47 2019 From: tcaswell at gmail.com (Thomas Caswell) Date: Fri, 24 May 2019 12:04:47 -0400 Subject: [Matplotlib-devel] Matplotlib 3.1.1 plans Message-ID: Folks, We have a couple of major regressions in 3.1, to that end we are planning to do a 3.1.1 relatively soon (May 31 is the goal). Paul Ivanov has agreed to be the release manager for 3.1.1 Tom -- Thomas Caswell tcaswell at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Thu May 30 14:06:51 2019 From: tcaswell at gmail.com (Thomas Caswell) Date: Thu, 30 May 2019 14:06:51 -0400 Subject: [Matplotlib-devel] Weekly call moved Message-ID: Folks, Through NumFOCUS we now have access to a zoom account which we can use for our weekly meetings. Hopefully we will have less issues with this than we have been having with hangouts. As a reminder they are from 1500-1600 US Eastern (15:00-04) every Monday if you are interested please join! If people want to join, but this time / day does not work for you we can move it. The time can probably only move an hour or two either way (we need to get both Hawaii (UTC-10) and Central European Summer time (UTC+2) on the call) It seems to not be able to set up an infinity repeating meeting so this one is for 20 occurrences. Tom ---- Thomas Caswell is inviting you to a scheduled Zoom meeting. Topic: Matplotlib Weekly call Time: Jun 3, 2019 3:00 PM Eastern Time (US and Canada) Every week on Mon, 20 occurrence(s) Please download and import the following iCalendar (.ics) files to your calendar system. Weekly: https://zoom.us/meeting/384435716/ics?icsToken=5790d101e3242759366e1b5f95ff5cb48468283f349c357c2c0e1438757bde31 Join Zoom Meeting https://zoom.us/j/384435716 One tap mobile +16468769923,,384435716# US (New York) +16699006833,,384435716# US (San Jose) Dial by your location +1 646 876 9923 US (New York) +1 669 900 6833 US (San Jose) +44 203 695 0088 United Kingdom +44 203 966 3809 United Kingdom +44 203 051 2874 United Kingdom +49 30 5679 5800 Germany +49 69 8088 3899 Germany +49 30 3080 6188 Germany +33 1 8288 0188 France +33 7 5678 4048 France +1 647 558 0588 Canada Meeting ID: 384 435 716 Find your local number: https://zoom.us/u/abafL44FHD -- Thomas Caswell tcaswell at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: