Mailman 3 May 2019 - SciPy-User

How to display a RGB image (MFISH)?
by jp April 3, 2023

April 3, 2023

Hi, I have written a script to try to combine five images into a three channels RGB images<http://dip4fish.blogspot.com/2011/05/trying-to-combine-mfish-images-into-rg…> . The resulting RGB image looks like a grey scale image instead of a color one. I have three np.array Rnorm, Gnorm, Bnorm which are copied into a rgb array: *rgb = np.zeros((shape[0],shape[1],3),dtype=float) mxr=np.max(R) mxg=np.max(G) mxb=np.max(B) Rnorm=np.uint8((255*(R/mxr)))Gnorm=np.uint8((255*(R/mxg)))Bnorm=np.uint8((255*(R/mxb)))#copy each RGB component in an RGB array rgb[:,:,0]=Rnorm rgb[:,:,1]=Gnorm rgb[:,:,2]=Bnorm* *pylab.subplot(224, aspect='equal',frameon=False, xticks=[], yticks=[]) pylab.imshow(rgb) pylab.show()* Any advice? Thank you Jean-Patrick

3 4

Invitation to connect on LinkedIn
by Jelle Feringa via LinkedIn July 28, 2022

July 28, 2022

LinkedIn ------------ Jelle Feringa requested to add you as a connection on LinkedIn: ------------------------------------------ Jose, I'd like to add you to my professional network on LinkedIn. - Jelle Accept invitation from Jelle Feringa http://www.linkedin.com/e/-3wy1w2-gpkzwpgn-5n/Q6WKH0LACopGJkAw_6fSqajo6R7VM… View invitation from Jelle Feringa http://www.linkedin.com/e/-3wy1w2-gpkzwpgn-5n/Q6WKH0LACopGJkAw_6fSqajo6R7VM… ------------------------------------------ DID YOU KNOW your LinkedIn profile helps you control your public image when people search for you? Setting your profile as public means your LinkedIn profile will come up when people enter your name in leading search engines. Take control of your image! http://www.linkedin.com/e/-3wy1w2-gpkzwpgn-5n/ewp/inv-22/ -- (c) 2011, LinkedIn Corporation

2 1

Help required regding Eigenvectors
by Sudheer Phani March 14, 2022

March 14, 2022

Hello All, I have been encountering some strange problems with the calculation of eigen vectors using python. The problem is with the sign of the eigen vectors calculated. On Very few occasions the eigen vectors calculated using python have an opposite sign than the actual eigenvectors, though the magnitude is correct. Can any one of you plz help me in this regard and suggest me some solution if you have encoutered similar problems . Any help in this regd is appreciated Thanks in Advace regds Sudheer

5 5

PyCM 2.2 released : A general benchmark based comparison of classification models
by Sepand Haghighi May 31, 2019

May 31, 2019

Hi folks Recently we have released new version of PyCM, library for confusion matrix statistical analysis. I thought you might find it interesting. http://www.pycm.ir https://github.com/sepandhaghighi/pycm Changelog : - Negative likelihood ratio interpretation (NLRI) added - Cramer's benchmark (SOA5) added - Matthews correlation coefficient interpretation (MCCI) added #204 - Matthews's benchmark (SOA6) added #204 - F1 macro added - F1 micro added - Accuracy macro added #205 - Compare class score calculation modified - Parameters recommendation for multi-class dataset modified - Parameters recommendation for imbalance dataset modified - README.md modified - Document modified - Logo updated Best RegardsSepand Haghighi

1 0

NumPy 1.16.4 released.
by Charles R Harris May 28, 2019

May 28, 2019

Charles R Harris <charlesr.harris(a)gmail.com> Apr 21, 2019, 8:39 PM to numpy-discussion, SciPy, SciPy-User, bcc: python-announce-list Hi All, On behalf of the NumPy team I am pleased to announce the release of NumPy 1.16.4 which contains several fixes for newly reported bugs. The Python versions supported in this release are 2.7 and 3.5-3.7. Downstream developers building this release should use Cython >= 0.29.2 and, if using OpenBLAS, OpenBLAS > v0.3.7. Wheels for this release can be downloaded from PyPI <https://pypi.org/project/numpy/1.16.4/>, source archives and release notes are available from Github <https://github.com/numpy/numpy/releases/tag/v1.16.4>. If you are installing using pip, you may encounter a problem with older installed versions of NumPy that pip did not delete becoming mixed with the current version, resulting in an ``ImportError``. That problem is particularly common on Debian derived distributions due to a modified pip. The fix is to make sure all previous NumPy versions installed by pip have been removed. See #12736 <https://github.com/numpy/numpy/issues/12736> for discussion of the issue. *Contributors* A total of 10 people contributed to this release. People with a "+" by their names contributed a patch for the first time. - Charles Harris - Eric Wieser - Dennis Zollo + - Hunter Damron + - Jingbei Li + - Kevin Sheppard - Matti Picus - Nicola Soranzo + - Sebastian Berg - Tyler Reddy *Pull requests merged* A total of 16 pull requests were merged for this release. - gh-13392: BUG: Some PyPy versions lack PyStructSequence_InitType2. - gh-13394: MAINT, DEP: Fix deprecated ``assertEquals()`` - gh-13396: BUG: Fix structured_to_unstructured on single-field types (backport) - gh-13549: BLD: Make CI pass again with pytest 4.5 - gh-13552: TST: Register markers in conftest.py. - gh-13559: BUG: Removes ValueError for empty kwargs in arraymultiter_new - gh-13560: BUG: Add TypeError to accepted exceptions in crackfortran. - gh-13561: BUG: Handle subarrays in descr_to_dtype - gh-13562: BUG: Protect generators from log(0.0) - gh-13563: BUG: Always return views from structured_to_unstructured when... - gh-13564: BUG: Catch stderr when checking compiler version - gh-13565: BUG: longdouble(int) does not work - gh-13587: BUG: distutils/system_info.py fix missing subprocess import (#13523) - gh-13620: BUG,DEP: Fix writeable flag setting for arrays without base - gh-13641: MAINT: Prepare for the 1.16.4 release. - gh-13644: BUG: special case object arrays when printing rel-, abs-error Cheers, Charles Harris

1 0

[ANN] SolarUtils-0.3 released - wrappers for NREL SOLPOS and SPECTRL2 algorithms
by Mark Mikofski May 23, 2019

May 23, 2019

This update adds two convenience functions: 1. get_solposAM(location, datetimes, weather) - returns solar positions and airmass for arbitrary sequence of datetime vectors [year, month, day, hour, minute second]. 2. get_solpos8760(location, year, weather) - returns 8760 annyual hourly solar position and airmass for given year. For example: >>> location = [35.56836, -119.2022, -8.0]>>> datetimes = [... (datetime.datetime(2013, 1, 1, 0, 0, 0)... + datetime.timedelta(hours=h)).timetuple()[:6]... for h in range(1000)]>>> weather = [1015.62055, 40.0]>>> angles, airmass = get_solposAM(location, datetimes, weather) For more info, please see: - docs: https://sunpower.github.io/SolarUtils/ - repo: https://github.com/SunPower/SolarUtils - pypi: https://pypi.org/project/SolarUtils/ Thanks! -- Mark Mikofski, PhD (2005) *Fiat Lux*

1 0

Re: [SciPy-User] [Numpy-discussion] GSoD - Technical Writter
by Chris Barker - NOAA Federal May 22, 2019

May 22, 2019

> a responsive web page may not be an absolute requirement, but still it may be nice to be able to read the docs from a tablet or smartphone. Unfortunately I am not familiar yet with Sphinx, but I hope that it can be integrated with Jekyll or Hugo, and then one of their templates can be used. Sphinx is powerful, featurefull, and the standard doc system for Python. Let’s just stick with that. But there are a LOT of themes available for Sphinx— I’m sure there are responsive ones out there that could be used or adapted. http://www.sphinx-doc.org/en/stable/theming.html You might check out the bootstrap theme: https://github.com/ryan-roemer/sphinx-bootstrap-theme -CHB About the content of the User Guide etc. I don't see any obvious improvement that is needed (maybe because I have not read them yet). One thing that may help is making the code examples interactive, so that the readers can play with them and see how the results change. For example this may be useful: https://github.com/RunestoneInteractive/RunestoneComponents The two changes that I have suggested above seem more like engineering work (for improving the documentation infrastructure), than documentation work. For making a content that can be easily grasped by the beginners, I think that it should be presented as a series of problems and their solutions. In other words don't show the users the features and their details, but ask them to solve a simple problem, and then show them how to solve it with NumPy/SciPy and its features. This would make it more attractive because people usually don't like to read manuals from beginning to the end. This is a job that can be done by the teachers for their students, having in mind the level of their students and what they actually want them to learn. I have noticed that there are already some lectures, or books, or tutorials like this. This is a creative work, with a specific target audience in mind, so I can't pretend that I can possibly do something useful about this in a short time (2-3 months). But of course the links to the existing resources can be made more visible and reachable from the main page of the website. Best regards, Dashamir _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion(a)python.org https://mail.python.org/mailman/listinfo/numpy-discussion

3 2

Main Site Design Questions
by Christina Lee May 20, 2019

May 20, 2019

As both people are realizing scipy.org needs a design overhaul and discussing doing so, I'd like to start a discussion clarifying aspects of SciPy that would drive design choices. These might seem like annoying and weird questions to someone used to a different type of thinking, but this is still problem-solving. The code itself gets more useful if there is a lower barrier to entry. * How should the typical user* feel* about SciPy? What gut-level impression should the website leave? How do you* feel* about SciPy? For example: reliable, dependable, cutting-edge, fast, novel, exciting, ... These will influence aspects like colors, fonts, images, spacings, etc. * What is the most important thing for a user to do? Fairly certain the answer to this question is "Install". * What is the most important thing for someone to learn about SciPy? Assume they know absolutely nothing and you have 10 seconds to catch their interest. * You have more than 10 seconds: Anything really cool about SciPy? Done anything amazing with it? Any cool plots? * Do we have information about both the typical SciPy user, and the typical person visiting the website? If most people have barely touched Python the first time the come across SciPy.org, that changes presentation and wording. Happy Sunday, Christina Lee

5 4

Re: [SciPy-User] GSoD - Technical Writter
by Ralf Gommers May 18, 2019

May 18, 2019

On Fri, May 17, 2019 at 6:57 PM Dashamir Hoxha <dashohoxha(a)gmail.com> wrote: > On Fri, May 17, 2019 at 2:54 PM Ralf Gommers <ralf.gommers(a)gmail.com> > wrote: > >> Hi Dashamir, >> >> Thank you for your email and interest in NumPy and SciPy. I'm excited >> about this program and opportunity to work with a technical writer. Please >> rest assured that we do not assume or expect you to be familiar with the >> project already. The scipy.stats idea we included in case someone would be >> familiar with it and wanted to work at the individual module level. >> Personally I think the most important and impactful thing though is to >> shape the structure of our documentation content. For that it's not >> necessarily an advantage to know numpy or scipy well - fresh eyes can be >> helpful. And in general, I'd say we have lots of people that can provide >> pieces of content; the ability to create the right framework/structure to >> effectively place and solicit that content is what we habe been missing. >> > >> If you look at the NumPy and SciPy documentation, you will see that the >> reference guides (which are aimed at experienced users) are very large. The >> user guides (for beginning users) and the overall structuring could really >> benefit from a good technical writer. >> > > Thanks for your encouraging message, Ralf. > > Something that I can notice immediately is that the interface of the docs > looks a bit outdated and maybe it can benefit from an update (or replacing > it with another template), in order to make it a bit more responsive. It is > true that when you program you usually work on a big screen, so a > responsive web page may not be an absolute requirement, but still it may be > nice to be able to read the docs from a tablet or smartphone. > Unfortunately I am not familiar yet with Sphinx, but I hope that it can be > integrated with Jekyll or Hugo, and then one of their templates can be used. > You're right, the interface is a little outdated. Docs will have to stay in Sphinx (that's really the only choice for reST docs for a large Python package), however the top level websites (scipy.org, docs.scipy.org) could be moved to Jekyll or Hugo for a more modern look - this will actually be beneficial. > About the content of the User Guide etc. I don't see any obvious > improvement that is needed (maybe because I have not read them yet). One > thing that may help is making the code examples interactive, so that the > readers can play with them and see how the results change. For example this > may be useful: https://github.com/RunestoneInteractive/RunestoneComponents > I'd really like to stay with a static site, so that's unfortunately not the best option. It looks cool, but RunestoneServer requires a server - maintenance cost wise that's a showstopper. > The two changes that I have suggested above seem more like engineering > work (for improving the documentation infrastructure), than documentation > work. For making a content that can be easily grasped by the beginners, I > think that it should be presented as a series of problems and their > solutions. In other words don't show the users the features and their > details, but ask them to solve a simple problem, and then show them how to > solve it with NumPy/SciPy and its features. This would make it more > attractive because people usually don't like to read manuals from beginning > to the end. This is a job that can be done by the teachers for their > students, having in mind the level of their students and what they actually > want them to learn. I have noticed that there are already some lectures, or > books, or tutorials like this. This is a creative work, with a specific > target audience in mind, so I can't pretend that I can possibly do > something useful about this in a short time (2-3 months). But of course the > links to the existing resources can be made more visible and reachable from > the main page of the website. > Yes, there's https://scipy-lectures.org/ for example. Guiding users effectively to all existing resources will be a major step forward. Cheers, Ralf

2 3

[ANN] PVMismatch v4.1: Python tools for photovoltaic IV curve modeling
by Mark Mikofski May 17, 2019

May 17, 2019

PVMismatch-4.1 has been released Release Notes: https://github.com/SunPower/PVMismatch/releases/tag/v4.1 PyPI: https://pypi.org/project/pvmismatch/ Docs: https://sunpower.github.io/PVMismatch/ GitHub: https://github.com/SunPower/PVMismatch -- Mark Mikofski, PhD (2005) *Fiat Lux*

1 0