Mailman 3 June 2014 - SciPy-Dev

Announce: scikit-video
by Alexander Izvorski June 17, 2014

June 17, 2014

Hello, This is to announce the very early version of scikit-video, a collection of algorithms for all your video-processing needs :) Code: https://github.com/aizvorski/scikit-video Status: There is functional video reading code, which is close to a replacement for cv2.VideoCapture. Otherwise, mostly a placeholder. Motivation: This scikit is intended as a companion to scikit-image: the two are complementary and not competitive. What code is better in video than in image? Roughly, if the code *only* makes sense when applied to a sequence of images, then it may be better placed in scikit-video. An example of this would be temporal denoise. Other code which would make sense to have in here is code which is much more often seen or used in a video context, even though it may in principle be used for both images or video. An example of this would be the SSIM quality metric. It is a goal that scikit-image and scikit-video would "just work" together, for example you might read a video file using scikit-video, use a scikit-image filter on each frame and write out the filtered frames to another file. Roadmap: - Skeleton project from scikit-example - DONE - Video IO by wrapping ffmpeg/avconv - reading DONE, writing not yet - Video metrics - Unit tests and CI (beyond this point are just possible future directions) - (?) Pyramid motion estimation - (?) TLD algorithm (http://personal.ee.surrey.ac.uk/Personal/Z.Kalal/) - (?) 3D denoise - (?) OpenGL display and a mini video player - (?) Any existing off-the-shelf projects that would be good to merge into this I expect that if this gathers enough interest it will transition to a group-maintained project similar to skimage or sklearn. Your suggestions, ideas, and code are most welcome. Regards, Alex Izvorski

1 0

Re: [SciPy-Dev] [Numpy-discussion] Reporting a bug to Apple.
by Aron Ahmadia June 10, 2014

June 10, 2014

On Mon, Jun 9, 2014 at 8:52 PM, Sturla Molden <sturla.molden(a)gmail.com> wrote: > > If we report a segfault Apple will probably think we are to blame. 99.9 % > of bug reports come from idiots, and those who screen bug reports are > basically payed to hit the ignore button. Indeed, good luck on reporting > it. I've reported bugs to Apple and seen them fixed in major releases of the operating system (though not necessarily minor releases). Unless things have changed considerably since my last bug report, I don't think it's fair to characterize their quality assurance team this way, particularly without evidence to back up your point. A

1 0

Re: [SciPy-Dev] [Numpy-discussion] Reporting a bug to Apple.
by Matthew Brett June 10, 2014

June 10, 2014

Hi, On Tue, Jun 10, 2014 at 1:52 AM, Sturla Molden <sturla.molden(a)gmail.com> wrote: > Frédéric Bastien <nouiz(a)nouiz.org> wrote: > OSes >> Good luck, and if they act on this, I would be happy to know how you did. >> > > If we report a segfault Apple will probably think we are to blame. 99.9 % > of bug reports come from idiots, and those who screen bug reports are > basically payed to hit the ignore button. Indeed, good luck on reporting > it. > > I think in the short run we will be better off re-implementing cblas_sgemv > with cblas_sgemm on Apple OSes. Luckily the error in cblas_sgemv does not > silently produce garbage data but segfaults the process, so anyone affected > will see it. Would you consider doing a PR for that? I believe I can build a 32 / 64 bit numpy binary against ATLAS, but it's certainly much less straightforward. Cheers, Matthew

1 0

Reporting a bug to Apple.
by Charles R Harris June 10, 2014

June 10, 2014

Hi All, Julian has tracked down a bug in the Accelerate library in Maverick, details here <https://github.com/numpy/numpy/issues/4007#issuecomment-45541678>. Is there a registered Apple Developer here who can report the bug to Apple? TIA, Chuck

2 1

ANN: NumPy 1.9.0 beta release
by Julian Taylor June 8, 2014

June 8, 2014

Hello, I'm happy to announce the fist beta release of Numpy 1.9.0. 1.9.0 will be a new feature release supporting Python 2.6 - 2.7 and 3.2 - 3.4. Due to low demand windows binaries for the beta are only available for Python 2.7, 3.3 and 3.4. Please try it and report any issues to the numpy-discussion mailing list or on github. The 1.9 release will consists of mainly of many small improvements and bugfixes. The highlights are: * Addition of __numpy_ufunc__ to allow overriding ufuncs in ndarray subclasses. Please note that there are still some known issues with this mechanism which we hope to resolve before the final release (e.g. #4753) * Numerous performance improvements in various areas, most notably indexing and operations on small arrays are significantly faster. Indexing operations now also release the GIL. * Addition of nanmedian and nanpercentile rounds out the nanfunction set. The changes involve a lot of small changes that might affect some applications, please read the release notes for the full details on all changes: https://github.com/numpy/numpy/blob/maintenance/1.9.x/doc/release/1.9.0-not… Please also take special note of the future changes section which will apply to the following release 1.10.0 and make sure to check if your applications would be affected by them. Source tarballs, windows installers and release notes can be found at https://sourceforge.net/projects/numpy/files/NumPy/1.9.0b1 Cheers, Julian Taylor

1 0

scipy/io/idl.py usage permission by ITT Visual Information
by Julian Taylor June 3, 2014

June 3, 2014

hi, scipy/io/idl.py contains code to read Save/Restore files written by IDL. These files contain following header (e.g. scipy/io/tests/ data/*.sav): NOTICE: IDL Save/Restore files embody unpublished proprietary information about the IDL program. Reverse engineering of this file is therefore forbidden under the terms of the IDL End User License Agreement (IDL EULA). All IDL users are required to read and agree to the terms of the IDL EULA at the time that they install IDL. Software that reads or writes files in the IDL Save/Restore format must have a license from ITT Visual Information Solutions explicitly granting the right to do so. In this case, the license will be included with the software for your inspection. Please report software that does not have such a license to ITT Visual Information Solutions (info(a)ittvis.com). So without a license from ITT using this code is illegal (within jurisdiction where this notice is valid). Though the idl.py file implementing the io contains following lines: # This code was developed by with permission from ITT Visual Information # Systems. IDL(r) is a registered trademark of ITT Visual Information Systems, # Inc. for their Interactive Data Language software. This is a little vague but I couldn't find any more information in the source and the addition predates github move. Is there more details on this permission available? Does the permission grant all users of scipy the full unencumbered right to read and write Save/Restore files? Does this permission extend to third parties redistributing scipy, e.g. via linux distributions? As is the IDL code does most likely not comply with the Debian free software guidelines and all code related to it will have to be removed from the Debian package. Cheers, Julian Taylor

2 1