bob issueshttps://gitlab.idiap.ch/groups/bob/-/issues2016-08-04T09:29:22Zhttps://gitlab.idiap.ch/bob/bob/-/issues/81bob.measure.far_threshold missing tests2016-08-04T09:29:22ZAndré Anjosbob.measure.far_threshold missing tests*Created by: anjos*
Hello,
I noticed you placed a function for computing the threshold given a certain FAR at `bob.measure`. This method is very useful, but it was wrongly coded w.r.t. the default arguments. I have fixed this on commit...*Created by: anjos*
Hello,
I noticed you placed a function for computing the threshold given a certain FAR at `bob.measure`. This method is very useful, but it was wrongly coded w.r.t. the default arguments. I have fixed this on commit 5644f048642ec97cb05781180790ba66f1c3371f. I have also taken the opportunity to improve on the documentation for each input variable.
I noticed there are no tests for this method. Could you please implement them?v1.1https://gitlab.idiap.ch/bob/bob/-/issues/80Logging system configuration in Python does not work as expected2016-08-04T09:29:20ZAndré AnjosLogging system configuration in Python does not work as expected*Created by: anjos*
If you use, from a C++ piece of code:
```C++
bob::core::info << "test" << std::endl;
```
This message is still logged after:
```python
import bob
```
Something is not quite right with the logging system settings.*Created by: anjos*
If you use, from a C++ piece of code:
```C++
bob::core::info << "test" << std::endl;
```
This message is still logged after:
```python
import bob
```
Something is not quite right with the logging system settings.v1.1https://gitlab.idiap.ch/bob/bob/-/issues/78Ffmpeg on Ubuntu 12.04 generates a memory leak2016-08-04T09:29:16ZAndré AnjosFfmpeg on Ubuntu 12.04 generates a memory leak*Created by: anjos*
Download and/or compile the latest version of Bob on Ubuntu-12.04, with stock dependencies.
Execute the following script to see the leak:
```python
for in in range(100):
v = bob.io.VideoReader('/path/to/a/file.m...*Created by: anjos*
Download and/or compile the latest version of Bob on Ubuntu-12.04, with stock dependencies.
Execute the following script to see the leak:
```python
for in in range(100):
v = bob.io.VideoReader('/path/to/a/file.mov')
for frame in v:
x = bob.ip.rgb_to_gray(frame) #just use frame
```
The leak consumes the available memory pretty fast.v1.1https://gitlab.idiap.ch/bob/bob/-/issues/75IP module consolidation2016-08-04T09:29:09ZAndré AnjosIP module consolidation*Created by: laurentes*
As discussed on the mailing list previously, there is a need to consolidate some parts of the code. In particular, the Image Processing module (IP) is one of the largest one and contains many algorithm ports from...*Created by: laurentes*
As discussed on the mailing list previously, there is a need to consolidate some parts of the code. In particular, the Image Processing module (IP) is one of the largest one and contains many algorithm ports from late torch5spro and others.
I've started this consolidation procedure. However, this is quite a large work.
This ticket aims at tracking the consolidation procedure of this IP module, with remarks and TODOs. Feel free to add your feature request.v1.1https://gitlab.idiap.ch/bob/bob/-/issues/72Gaussian filter is using Variance/2 instead of Variance2016-08-04T09:29:05ZAndré AnjosGaussian filter is using Variance/2 instead of Variance*Created by: laurentes*
There is an invalid parametrization in the Gaussian filter of the IP module. A factor 1/2 is missing is the argument of the exponential, which means that the variance given as a parameter of the filter correspond...*Created by: laurentes*
There is an invalid parametrization in the Gaussian filter of the IP module. A factor 1/2 is missing is the argument of the exponential, which means that the variance given as a parameter of the filter corresponds to the variance/2.
This can be easily fixed, but the main issue is that this class is used by the TanTriggs preprocessing. This means that if the fix is applied, the user SHOULD divide the provided variance by 2 to keep getting the same results. Therefore, I don't know what would be the most suitable option.v1.1https://gitlab.idiap.ch/bob/bob/-/issues/68FIR database lacks proper documentation2016-08-04T09:29:03ZAndré AnjosFIR database lacks proper documentation*Created by: anjos*
It would be nice to have some more documentation explaining what is the FIR database in the Bob release (I wonder if we did it right to include it in the 1.0 release...) and where to download it if it is available. O...*Created by: anjos*
It would be nice to have some more documentation explaining what is the FIR database in the Bob release (I wonder if we did it right to include it in the 1.0 release...) and where to download it if it is available. Otherwise, some mentioning of Idiap internal use would be nice.v1.1https://gitlab.idiap.ch/bob/bob/-/issues/66cxx/ip/test/geomnorm.cc is not working2016-08-04T09:28:58ZAndré Anjoscxx/ip/test/geomnorm.cc is not working*Created by: siebenkopf*
I just detected that the C++ ip::GeomNorm test is disabled by documenting its inclusion in the CMakeLists.txt. I tried to simply enable the test, but it doesn't compile.
It would be nice, if either this test wo...*Created by: siebenkopf*
I just detected that the C++ ip::GeomNorm test is disabled by documenting its inclusion in the CMakeLists.txt. I tried to simply enable the test, but it doesn't compile.
It would be nice, if either this test would be corrected or removed. Since it has Laurent's name in it, I assign it to him :)
Cheers,
Manuelv1.1https://gitlab.idiap.ch/bob/bob/-/issues/64ImageMagick 6.7.8 write/read issue on OSX2016-08-04T09:28:56ZAndré AnjosImageMagick 6.7.8 write/read issue on OSX*Created by: anjos*
Not sure this is related to OSX or ImageMagick 6.7.8. I just reported the problem to the ImageMagick developers:
http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=21362*Created by: anjos*
Not sure this is related to OSX or ImageMagick 6.7.8. I just reported the problem to the ImageMagick developers:
http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=21362v1.1https://gitlab.idiap.ch/bob/bob/-/issues/62Test python/io/lib/test/file.py overwrites files from distribution2016-08-04T09:28:54ZAndré AnjosTest python/io/lib/test/file.py overwrites files from distribution*Created by: tiagofrepereira2012*
This test seems to be overwriting files in the distribution directories. This should be re-done so that it creates a temporary directory and write files there. If something goes wrong with saving, then ...*Created by: tiagofrepereira2012*
This test seems to be overwriting files in the distribution directories. This should be re-done so that it creates a temporary directory and write files there. If something goes wrong with saving, then this will modify the core files.v1.1https://gitlab.idiap.ch/bob/bob/-/issues/59ImageMagick 6.7.7 issues on OSX (MacPorts)2016-08-04T09:28:50ZAndré AnjosImageMagick 6.7.7 issues on OSX (MacPorts)*Created by: anjos*
We just found out that the version of ImageMagick currently shipped with MacPorts (6.7.7) presents a runtime problem related to https://bugs.archlinux.org/task/30122?project=1&openedfrom=-1+week. Until that gets upgr...*Created by: anjos*
We just found out that the version of ImageMagick currently shipped with MacPorts (6.7.7) presents a runtime problem related to https://bugs.archlinux.org/task/30122?project=1&openedfrom=-1+week. Until that gets upgraded in MacPorts, avoid using that version. If you upgraded and things became unstable, downgrade with the following recipe:
```sh
$ wget --no-check-certificate https://trac.macports.org/export/93199/trunk/dports/graphics/ImageMagick/Portfile
$ sudo port uninstall ImageMagick
$ sudo port install
```
6.7.6 and 6.7.7 are API and ABI compatible. You **don't** need to recompile your build of Bob after downgrading or upgrading.v1.1https://gitlab.idiap.ch/bob/bob/-/issues/58OpenCV 2.4.x has problems with pkg-config2016-08-04T09:28:48ZAndré AnjosOpenCV 2.4.x has problems with pkg-config*Created by: anjos*
The following bug in the OpenCV tracker affects us (at least our OSX builds with MacPorts): http://code.opencv.org/issues/1925. Avoid upgrading to OpenCV 2.4.x until that is fixed. The last know version to work prope...*Created by: anjos*
The following bug in the OpenCV tracker affects us (at least our OSX builds with MacPorts): http://code.opencv.org/issues/1925. Avoid upgrading to OpenCV 2.4.x until that is fixed. The last know version to work properly is 2.3.1a.
Here is a recipe to revert your Mac Ports installation to OpenCV 2.3.1a in case you need it:
```sh
$ wget --no-check-certificate https://trac.macports.org/export/90303/trunk/dports/graphics/opencv/Portfile https://trac.macports.org/export/90303/trunk/dports/graphics/opencv/files/patch-CMakeLists.txt.diff https://trac.macports.org/export/90303/trunk/dports/graphics/opencv/files/patch-install_name.diff https://trac.macports.org/export/90303/trunk/dports/graphics/opencv/files/patch-pch-CMakeLists.txt.diff
$ mkdir files
$ mv patch-*.diff files
$ sudo port install
```v1.1https://gitlab.idiap.ch/bob/bob/-/issues/54LBPTopOperator is untested and seems to be buggy2016-08-04T09:28:38ZAndré AnjosLBPTopOperator is untested and seems to be buggy*Created by: laurentes*
The current LBPTopOperator implementation is a port of some older torch5spro code. Unfortunately, it suffers from the following problems (non-exhaustive list):
- No unit test!
- Does not seem to work!
- Poor pyth...*Created by: laurentes*
The current LBPTopOperator implementation is a port of some older torch5spro code. Unfortunately, it suffers from the following problems (non-exhaustive list):
- No unit test!
- Does not seem to work!
- Poor python bindings (no helper functions to get information about the expected size of the output)
- Generic C++ core exceptions rather than specialized ones
- Few check on the input/output array size are performed
This requires some serious revision.v1.1https://gitlab.idiap.ch/bob/bob/-/issues/52IP Block - Get output shape - Two different functions for similar purpose2016-08-04T09:28:34ZAndré AnjosIP Block - Get output shape - Two different functions for similar purpose*Created by: laurentes*
I've just noticed that there are two different functions for similar purpose in the IP block decomposition code. To get the expected number of blocks given an input array and some parameters, both `getBlockShape(...*Created by: laurentes*
I've just noticed that there are two different functions for similar purpose in the IP block decomposition code. To get the expected number of blocks given an input array and some parameters, both `getBlockShape()` and `getNBlocks()` could be used.
For the next release, we should remove one of them and update the bits which rely on these functions accordingly (at the C++ level, `DCTFeatures` and `LBPHSFeatures`).v1.1https://gitlab.idiap.ch/bob/bob/-/issues/51Search Engine Optimisation, and consolidation of links2016-08-04T09:28:32ZAndré AnjosSearch Engine Optimisation, and consolidation of links*Created by: Waldo000000*
Googling for Bob returns poor results. e.g.
* Searching for "bob toolbox" or "bob toolkit" or "bob library" or "bob signal processing" all fail to return a link to http://idiap.github.com/bob/ on the first ...*Created by: Waldo000000*
Googling for Bob returns poor results. e.g.
* Searching for "bob toolbox" or "bob toolkit" or "bob library" or "bob signal processing" all fail to return a link to http://idiap.github.com/bob/ on the first page of results.
* Searching for "bob idiap" returns a link to the github page (https://github.com/idiap/bob), not the home page, as first result.
* Searching for "bob biometrics" returns the correct link but only at 5th position
* Searching for "bob machine learning" has the link in 2nd position
To address this issue, we should follow relevant instructions in Google's Webmaster Tools, for example:
* [Webmaster Guidelines](http://support.google.com/webmasters/bin/answer.py?hl=en&answer=35769)
* [Search Engine Optimization (SEO)](http://support.google.com/webmasters/bin/answer.py?hl=en&answer=35291)
Finally, we need to decide whether the advertised home page of Bob is http://idiap.github.com/bob/ (as was noted in the recent announcement emails) or http://www.idiap.ch/software/bob. There is currently a link at the top of https://github.com/idiap/bob that points to http://www.idiap.ch/software/bob that redirects to http://idiap.github.com/bob/. So anyone who "bookmarks" the Bob homepage right now is bookmarking http://idiap.github.com/bob/. If we are happy with that URL, we should edit the link on https://github.com/idiap/bob accordingly. Making this choice of a single homepage URL may in turn help us to improve search results.v1.1https://gitlab.idiap.ch/bob/bob/-/issues/46SVD segfaults (BLAS function) on Ubuntu 32 bits when using blitz 0.10 hg2016-08-04T09:28:23ZAndré AnjosSVD segfaults (BLAS function) on Ubuntu 32 bits when using blitz 0.10 hg*Created by: laurentes*
We have noticed that the SVD was crashing on Ubuntu 32 bits, when using the latest release of blitz++ from mercurial. Strangely, this only happens with this particular combination of platform and blitz version, a...*Created by: laurentes*
We have noticed that the SVD was crashing on Ubuntu 32 bits, when using the latest release of blitz++ from mercurial. Strangely, this only happens with this particular combination of platform and blitz version, and hence no problem is encountered when using 64 bits versions of Ubuntu or the latest but old 0.9 release of blitz++, even when using valgrind.
The crash is caused by a segmentation fault, and gdb reports the following:
```
Program received signal SIGSEGV, Segmentation fault.
0xb6e4f19b in ATL_dgemvT_a1_x1_b0_y1 () from /usr/lib/libblas.so.3gf
```
There are many tickets for other libraries using BLAS which report similar problem with this particular function, but none of them really explain the cause of the problem. This might be related to some data alignment issue.
[NumPy/SciPy](http://projects.scipy.org/numpy/ticket/551)
[gnome-mousetrap](https://bugs.launchpad.net/ubuntu/+source/gnome-mousetrap/+bug/732927)
[OpenCV1](https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/684302)
[OpenCV2](http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610400)
The workaround that we have currently chosen is to copy the data of the blitz::Array's to/from C-style arrays, only for the linux 32 bits implementation of the SVD.v1.1https://gitlab.idiap.ch/bob/bob/-/issues/42No range check of std::vector in DEBUG mode2016-08-04T09:28:13ZAndré AnjosNo range check of std::vector in DEBUG mode*Created by: siebenkopf*
In the current version of Bob, there is no range check on the std::vector::operator [] and no sanity checks for std::...iterator's. Unfortunately, the proposed method for GnuCC, i.e., adding the compiler flag "-...*Created by: siebenkopf*
In the current version of Bob, there is no range check on the std::vector::operator [] and no sanity checks for std::...iterator's. Unfortunately, the proposed method for GnuCC, i.e., adding the compiler flag "-D_GLIBCXX_DEBUG" interferes with:
+ some functionalities of Boost, like the boost::program_options
+ also Boost.Python seems to be affected
+ the -DBZ_DEBUG flag to enable range checking in blitz::Arrays also seems to affect this (not sure)
by adding C++ linking errors.
The proposed solutions on the internet suggest to compile boost (and blitz) with the -D_GLIBCXX_DEBUG. Unfortunately, this would require to ship the compiled versions of boost (and blitz) with Bob.
A workaround for at least the indexing check would be to used the std:: vector::at(i) function instead, which does the range checking. Unfortunately, the range check is not disabled in release mode. This could be solved by:
#ifndef DEBUG
#define at(x) operator[](x)
#endif
(another solution I found in the net), but this of course would influence ALL at() functions...
Another workaround (which we had in our old software system) is to use our own derived class from the std::vector that actually does the range check (only in debug mode) and calls the operator::[] of the std::vector. Unfortunately, this is very ugly since it requires to re-write (at least) all constructors of the std::vector.v1.1https://gitlab.idiap.ch/bob/bob/-/issues/39FisherLDATrainer does not have a zscore_convert option2016-08-04T09:28:06ZAndré AnjosFisherLDATrainer does not have a zscore_convert option*Created by: ivana7c*
In contrast to SVDPCATrainer, the FisherLDATrainer does not have the zscore_convert option. It would be nice to add this option for consistency.*Created by: ivana7c*
In contrast to SVDPCATrainer, the FisherLDATrainer does not have the zscore_convert option. It would be nice to add this option for consistency.v1.1https://gitlab.idiap.ch/bob/bob/-/issues/44Exception Raising with HDF5-related file manipulation ends in segfault2016-08-04T09:28:17ZAndré AnjosException Raising with HDF5-related file manipulation ends in segfault*Created by: anjos*
This example will trigger it:
```python
import bob
f = bob.io.HDF5File('test.hdf5', 't')
f.set('bla', 3)
del f
m = bob.machine.LinearMachine(3,3)
# saving on read-only file, exception is raised and then Pyth...*Created by: anjos*
This example will trigger it:
```python
import bob
f = bob.io.HDF5File('test.hdf5', 't')
f.set('bla', 3)
del f
m = bob.machine.LinearMachine(3,3)
# saving on read-only file, exception is raised and then Python segfaults on exit()
m.save(bob.io.HDF5File('test.hdf5'))
```v1.0https://gitlab.idiap.ch/bob/bob/-/issues/40Unit test for SIFT features extraction based on VLFeat fails on Ubuntu 12.04 ...2016-08-04T09:28:08ZAndré AnjosUnit test for SIFT features extraction based on VLFeat fails on Ubuntu 12.04 32bits*Created by: laurentes*
There is currently an issue with the test of the *SIFT* features under *Ubuntu 12.04 32 bits*. For unknown reason, the *SIFT* descriptors computed by *Ubuntu 12.04 32 bits* are different from the reference one ge...*Created by: laurentes*
There is currently an issue with the test of the *SIFT* features under *Ubuntu 12.04 32 bits*. For unknown reason, the *SIFT* descriptors computed by *Ubuntu 12.04 32 bits* are different from the reference one generated with *Ubuntu 10.04 32 bits*. This happens despite the fact that we are using the exact same version of *VLFeat 0.9.14* (last release), and that *VLFeat* has almost no external dependence:
```
$ ldd /usr/lib/libvl.so
linux-gate.so.1 => (0x00b52000)
libm.so.6 => /lib/tls/i686/cmov/libm.so.6 (0x00412000)
libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0x0073c000)
libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0x00174000)
/lib/ld-linux.so.2 (0x00b8b000)
```
Tracking the problem, it likely originates from the keypoint detection, as there is no such an issue with the *Dense SIFT* features, which also relies on *VLFeat*. I guess that some of them are slightly below the threshold to be considered as keypoints on 12.04 but slightly above on 10.04. This is particularly annoying as this then shift the whole keypoints, making the comparison of the descriptors tough.
There are three possible options:
- Remove the test, considering that this is a VLFeat issue
- Add additional references and checking that one of them matches the values generated
- Add a more clever test. which will allow some keypoints more (or less), and able to still match the descriptors in such a situation.
Personally, I will go for the first one.v1.0https://gitlab.idiap.ch/bob/bob/-/issues/38VLFeat is not detected despite installation2016-08-04T09:28:03ZAndré AnjosVLFeat is not detected despite installation*Created by: anjos*
From my understanding of the cmake file, we should see a printout when VLFeat is detected on the system:
```
Found VLFeat: /usr/lib/libvlfeat.so
```
But we don't seem to see this line ever. Could you make sur...*Created by: anjos*
From my understanding of the cmake file, we should see a printout when VLFeat is detected on the system:
```
Found VLFeat: /usr/lib/libvlfeat.so
```
But we don't seem to see this line ever. Could you make sure that it is properly detected and reported?v1.0