bob issueshttps://gitlab.idiap.ch/groups/bob/-/issues2020-10-12T14:19:51Zhttps://gitlab.idiap.ch/bob/bob.pipelines/-/issues/19Dask Client as python resources2020-10-12T14:19:51ZTiago de Freitas PereiraDask Client as python resourcesWe should put the Dask Clients from here: https://gitlab.idiap.ch/bob/bob.pipelines/-/tree/master/bob/pipelines/config/distributed
as python resources.We should put the Dask Clients from here: https://gitlab.idiap.ch/bob/bob.pipelines/-/tree/master/bob/pipelines/config/distributed
as python resources.Bob 9.0.0Yannick DAYERYannick DAYERhttps://gitlab.idiap.ch/bob/bob.pipelines/-/issues/20Problem while using `sge_default` dask client2020-10-12T11:25:50ZVictor BROSProblem while using `sge_default` dask clientFOr some reason `bob.pipelines.distributed.sge.SGEIdiapJob` is requiring a class variable `config_name`.
I've patched myself to make it work, but this needs a proper fix
```
bob@2020-10-09 14:36:37,427 -- DEBUG: Logging of the `bob' log...FOr some reason `bob.pipelines.distributed.sge.SGEIdiapJob` is requiring a class variable `config_name`.
I've patched myself to make it work, but this needs a proper fix
```
bob@2020-10-09 14:36:37,427 -- DEBUG: Logging of the `bob' logger was set to 3
bob.extension.config@2020-10-09 14:36:37,430 -- DEBUG: Loading configuration file `./experiments/vera-finger/veradb.py'...
bob.extension.config@2020-10-09 14:36:38,765 -- DEBUG: Loading configuration file `./experiments/vera-finger/vera_miura.py'...
bob.bio.base@2020-10-09 14:36:39,001 -- INFO: Using `bob.bio.base` legacy algorithm <class 'bob.bio.vein.algorithm.MiuraMatch'>(ch=80, cw=90, multiple_model_scoring='average', multiple_probe_scoring='average')
bob.extension.config@2020-10-09 14:36:39,002 -- DEBUG: Loading configuration file `./src/bob.pipelines/bob/pipelines/config/distributed/sge_default.py'...
tornado.application - ERROR - Exception in callback functools.partial(<bound method IOLoop._discard_future_result of <tornado.platform.asyncio.AsyncIOLoop object at 0x7f92cb83db50>>, <Task finished coro=<SpecCluster._correct_state_internal() done, defined at /remote/idiap.svm/temp.biometric01/vbros/bob_vein/bob.bio.vein/eggs/distributed-2.30.0-py3.7.egg/distributed/deploy/spec.py:320> exception=ValueError("The class <class 'bob.pipelines.distributed.sge.SGEIdiapJob'> is required to have a 'config_name' class variable.\nIf you have created this class, please add a 'config_name' class variable.\nIf not this may be a bug, feel free to create an issue at: https://github.com/dask/dask-jobqueue/issues/new")>)
Traceback (most recent call last):
File "/idiap/temp/vbros/miniconda3/envs/bob.bio.vein/lib/python3.7/site-packages/tornado/ioloop.py", line 743, in _run_callback
ret = callback()
File "/idiap/temp/vbros/miniconda3/envs/bob.bio.vein/lib/python3.7/site-packages/tornado/ioloop.py", line 767, in _discard_future_result
future.result()
File "/remote/idiap.svm/temp.biometric01/vbros/bob_vein/bob.bio.vein/eggs/distributed-2.30.0-py3.7.egg/distributed/deploy/spec.py", line 348, in _correct_state_internal
worker = cls(self.scheduler.address, **opts)
File "/remote/idiap.svm/temp.biometric01/vbros/bob_vein/bob.bio.vein/src/bob.pipelines/bob/pipelines/distributed/sge.py", line 56, in __init__
super().__init__(*args, config_name=config_name, death_timeout=10000, **kwargs)
File "/remote/idiap.svm/temp.biometric01/vbros/bob_vein/bob.bio.vein/eggs/dask_jobqueue-0.7.1-py3.7.egg/dask_jobqueue/core.py", line 156, in __init__
default_config_name = self.default_config_name()
File "/remote/idiap.svm/temp.biometric01/vbros/bob_vein/bob.bio.vein/eggs/dask_jobqueue-0.7.1-py3.7.egg/dask_jobqueue/core.py", line 260, in default_config_name
"https://github.com/dask/dask-jobqueue/issues/new".format(cls)
ValueError: The class <class 'bob.pipelines.distributed.sge.SGEIdiapJob'> is required to have a 'config_name' class variable.
```Bob 9.0.0Tiago de Freitas PereiraTiago de Freitas Pereirahttps://gitlab.idiap.ch/bob/bob.ip.stereo/-/issues/3Wrong speckleWindowSize value2020-10-12T07:19:21ZVincent POLLETWrong speckleWindowSize valueLooks like speckleWindowSize gets assigned the wrong value [here](https://gitlab.idiap.ch/bob/bob.ip.stereo/-/blob/master/bob/ip/stereo/stereo.py#L67)
Shouldn't it be
``` python
speckleWindowSize = stereo_parameters.speckle_window_size...Looks like speckleWindowSize gets assigned the wrong value [here](https://gitlab.idiap.ch/bob/bob.ip.stereo/-/blob/master/bob/ip/stereo/stereo.py#L67)
Shouldn't it be
``` python
speckleWindowSize = stereo_parameters.speckle_window_size
```
?David GEISSBUHLERDavid GEISSBUHLERhttps://gitlab.idiap.ch/bob/bob.pad.base/-/issues/32Follow-up from "Scikit wrapper"2020-10-08T11:47:12ZAmir MOHAMMADIFollow-up from "Scikit wrapper"The following discussion from !64 should be addressed:
- [ ] @amohammadi started a [discussion](https://gitlab.idiap.ch/bob/bob.pad.base/merge_requests/64#note_49055): (+1 comment)
> You have to use `tempfile`The following discussion from !64 should be addressed:
- [ ] @amohammadi started a [discussion](https://gitlab.idiap.ch/bob/bob.pad.base/merge_requests/64#note_49055): (+1 comment)
> You have to use `tempfile`Bob 9.0.0Anjith GEORGEanjith.george@idiap.chAnjith GEORGEanjith.george@idiap.chhttps://gitlab.idiap.ch/bob/bob.pad.base/-/issues/34TEMPORARY Detach from bob.bio.base2020-10-08T11:42:46ZTiago de Freitas PereiraTEMPORARY Detach from bob.bio.baseHi guys,
We are about to have a beta release of `bob.bio.base` and `bob.bio.face`.
Thanks to @ydayer, we'll have a very nice user-guide for both very soon.
The future `bob.bio.base` is very different from the current one (I'll let you ...Hi guys,
We are about to have a beta release of `bob.bio.base` and `bob.bio.face`.
Thanks to @ydayer, we'll have a very nice user-guide for both very soon.
The future `bob.bio.base` is very different from the current one (I'll let you dig here https://gitlab.idiap.ch/bob/bob.bio.base/-/tree/dask-pipelines and here https://gitlab.idiap.ch/bob/bob.pipelines) and this will impact a lot the current version of this package. That's why this issue.
Until we have this package ported to use `bob.pipelines`, I would like to move the content from the current `bob.bio.base` to a module in this package, hence, we can have a beta version of the new `bob.bio.base` without breaking this one.
What do you think?Bob 9.0.0https://gitlab.idiap.ch/bob/bob.learn.mlp/-/issues/4superfluous 'batch_size' parameter?2020-10-08T08:12:49ZAndré Anjossuperfluous 'batch_size' parameter?*Created by: siebenkopf*
I recently tried to use the ``bob.learn.mlp.RProp`` class to train a neural network. I came across the ``batch_size`` parameter that I need to set in the constructor (as well as in all other Trainer constructors...*Created by: siebenkopf*
I recently tried to use the ``bob.learn.mlp.RProp`` class to train a neural network. I came across the ``batch_size`` parameter that I need to set in the constructor (as well as in all other Trainer constructors). In the documentation, it is not clear, how to select a proper value, so I used 1 (for stochastic training).
Anyways, afterwards I wanted to train a network with several input values, which I had put into a list. However, when I called the ``train`` method, I got the error message:
```
RuntimeError: array dimensions do not match 1 != 1031
```
where 1031 is the number of training examples. So, I had a look into the code, and I found that the ``batch_size`` parameter has to match the number of training samples.
Now, my question is, why do we need to specify something obvious? Can't the code just assume that the ``batch_size`` is the same as the number of inputs?
The only place, where the code actually relies on the ``batch_size`` is during the initialization of the trainer, which resizes some buffers according to the number of training data (see: https://github.com/bioidiap/bob.learn.mlp/blob/master/bob/learn/mlp/cxx/trainer.cpp#L221) . Can't we simply resize these buffers, when we know the number of data? This would enable us to remove this superfluous parameter from the Trainer constructors...https://gitlab.idiap.ch/bob/bob.learn.libsvm/-/issues/11Trained machine shape different from input shape2020-10-08T08:11:45ZGuillaume HEUSCHTrained machine shape different from input shapeHi,
When using ``bob.learn.libsvm`` in my own project (through ``bob.pad.face``). I sometimes got the following error:
```bash
RuntimeError: 2D `input' array should have 86 columns, matching `bob.learn.libsvm.Machine' input size, not 9...Hi,
When using ``bob.learn.libsvm`` in my own project (through ``bob.pad.face``). I sometimes got the following error:
```bash
RuntimeError: 2D `input' array should have 86 columns, matching `bob.learn.libsvm.Machine' input size, not 96
```
So basically the trained machine input size does not correspond to the feature size, which is quite odd ...
A first issue (https://gitlab.idiap.ch/bob/bob.pad.base/issues/19) was open there by myself, but I guess that here is more appropriate.
Also, I tracked down the error in the C++ code, and it happens here:
https://gitlab.idiap.ch/bob/bob.learn.libsvm/blob/master/bob/learn/libsvm/machine.cpp#L543
@andre.anjos any idea on this one ?
ThanksGuillaume HEUSCHGuillaume HEUSCHhttps://gitlab.idiap.ch/bob/bob.io.matlab/-/issues/3Old-Style C++ documentation and missing BOB_TRY2020-10-08T08:10:59ZManuel Günthersiebenkopf@googlemail.comOld-Style C++ documentation and missing BOB_TRYIn the C++ code of this module, the documentation does not rely on the `bob::extension` documentation classes. Furthermore, `bob.io.matlab.read_varnames` will crash on exceptions, as they are not caught:
https://gitlab.idiap.ch/bob/bob....In the C++ code of this module, the documentation does not rely on the `bob::extension` documentation classes. Furthermore, `bob.io.matlab.read_varnames` will crash on exceptions, as they are not caught:
https://gitlab.idiap.ch/bob/bob.io.matlab/blob/master/bob/io/matlab/main.cpp#L29
* [ ] Update documentation to use the `bob::extension` documentation classes
* [ ] Use `BOB_TRY` and `BOB_CATCH_FUNCTION` to catch exceptions in the binding codehttps://gitlab.idiap.ch/bob/bob.pad.face/-/issues/36Issue with docs2020-10-08T08:05:10ZAnjith GEORGEanjith.george@idiap.chIssue with docsThe docs says there is a script `evaluate.py`, which I couldnt find.
`https://gitlab.idiap.ch/bob/bob.pad.face/-/blob/master/doc/baselines.rst#L122`The docs says there is a script `evaluate.py`, which I couldnt find.
`https://gitlab.idiap.ch/bob/bob.pad.face/-/blob/master/doc/baselines.rst#L122`Anjith GEORGEanjith.george@idiap.chAnjith GEORGEanjith.george@idiap.chhttps://gitlab.idiap.ch/bob/bob.bio.face/-/issues/36outdated `baselines.py` script remained in setup.py2020-10-08T07:25:59ZManuel Günthersiebenkopf@googlemail.comoutdated `baselines.py` script remained in setup.pySee here: https://gitlab.idiap.ch/bob/bob.bio.face/-/blob/117ed4a764bac88c9e0d3c5b27c8c36d5cf87a61/setup.py#L106
When running `baselines.py`, I get the following error:
```
$ baselines.py -h
...
ModuleNotFoundError: No module named 'bob...See here: https://gitlab.idiap.ch/bob/bob.bio.face/-/blob/117ed4a764bac88c9e0d3c5b27c8c36d5cf87a61/setup.py#L106
When running `baselines.py`, I get the following error:
```
$ baselines.py -h
...
ModuleNotFoundError: No module named 'bob.bio.face.script.baselines'
```Bob 9.0.0https://gitlab.idiap.ch/bob/bob.bio.spear/-/issues/34Remove traces of evaluate.py2020-10-08T07:16:31ZTiago de Freitas PereiraRemove traces of evaluate.pyBefore the new release of Bob we should remove traces of `evaluate.py` in the documentation and in the baselines script.
Furthermore, we should test this baseline script.
Who is currently working with speaker recognition here?
Maybe @am...Before the new release of Bob we should remove traces of `evaluate.py` in the documentation and in the baselines script.
Furthermore, we should test this baseline script.
Who is currently working with speaker recognition here?
Maybe @amohammadi, @ssarfjoo ?
Related to https://gitlab.idiap.ch/bob/bob/issues/255https://gitlab.idiap.ch/bob/bob.bio.spear/-/issues/33The baselines need to be ported to bob.bio.baseline format2020-10-08T07:16:22ZAmir MOHAMMADIThe baselines need to be ported to bob.bio.baseline formatAlso, I noticed that in bob.bio.spear not only preprocessors are changed but hyper parameters of algorithms are also changed for each database and baseline combination. See for example: https://www.idiap.ch/software/bob/docs/bob/bob.bio....Also, I noticed that in bob.bio.spear not only preprocessors are changed but hyper parameters of algorithms are also changed for each database and baseline combination. See for example: https://www.idiap.ch/software/bob/docs/bob/bob.bio.spear/v3.2.0/baselines.html#voxforge-datasethttps://gitlab.idiap.ch/bob/bob.bio.spear/-/issues/32The link to the nist sre database is old in the documentation2020-10-08T07:15:37ZAmir MOHAMMADIThe link to the nist sre database is old in the documentationSaeed SARFJOOSaeed SARFJOOhttps://gitlab.idiap.ch/bob/bob.bio.spear/-/issues/29README has broken links2020-10-08T07:15:30ZAndré AnjosREADME has broken linksFor some reason, the README.rst file in the root of this package has not yet caught up with our new standards (see: https://gitlab.idiap.ch/bob/bob.admin/tree/master/templates). As a consequence, the PyPI page has a link to an outdated d...For some reason, the README.rst file in the root of this package has not yet caught up with our new standards (see: https://gitlab.idiap.ch/bob/bob.admin/tree/master/templates). As a consequence, the PyPI page has a link to an outdated doc tree.Pavel KORSHUNOVPavel KORSHUNOVhttps://gitlab.idiap.ch/bob/bob.bio.spear/-/issues/25code starts with ./bin/2020-10-08T07:15:23ZAlain KOMATYcode starts with ./bin/bob.bio.spear/bob/bio/spear/script/baselines.py
```
line 94: script = './bin/verify_gmm.py'
line 118: ... setup['script'] = './bin/verify.py'
line 223: base_command = ['./bin/evaluate.py', ...
```bob.bio.spear/bob/bio/spear/script/baselines.py
```
line 94: script = './bin/verify_gmm.py'
line 118: ... setup['script'] = './bin/verify.py'
line 223: base_command = ['./bin/evaluate.py', ...
```May 2017 Hackathonhttps://gitlab.idiap.ch/bob/bob.bio.spear/-/issues/24Add more info on the latest handcrafted features with usage examples2020-10-08T07:15:14ZPavel KORSHUNOVAdd more info on the latest handcrafted features with usage examplesNew features include more customizable MFCC, SCFC, RFCC, SCMC, SSFC, and LFCC.New features include more customizable MFCC, SCFC, RFCC, SCMC, SSFC, and LFCC.May 2017 HackathonPavel KORSHUNOVPavel KORSHUNOV2017-05-09https://gitlab.idiap.ch/bob/bob.bio.spear/-/issues/22Using super() for base class function calls2020-10-08T07:15:02ZManuel Günthersiebenkopf@googlemail.comUsing super() for base class function callsAfter bob.bio.base#64 is merged, we can go ahead and use `super()` to call base class functionality here, too. This mainly should affect constructor calls.After bob.bio.base#64 is merged, we can go ahead and use `super()` to call base class functionality here, too. This mainly should affect constructor calls.May 2017 Hackathonhttps://gitlab.idiap.ch/bob/bob.bio.spear/-/issues/20Results with new version are worse than those in the documentation2020-10-08T07:14:53ZAlain KOMATYResults with new version are worse than those in the documentationRunning spear now gives results slightly different than those in the documentation (https://pythonhosted.org/bob.bio.spear/baselines.html)
```
DEV: EER = 1.89%
EVAL: HTER = 1.56%
```
I re-ran two baseline experiments:
```
./bin/verify.py...Running spear now gives results slightly different than those in the documentation (https://pythonhosted.org/bob.bio.spear/baselines.html)
```
DEV: EER = 1.89%
EVAL: HTER = 1.56%
```
I re-ran two baseline experiments:
```
./bin/verify.py -g 'demanding' -d voxforge -p energy-2gauss -e mfcc-60 -a gmm-voxforge -s ubm_gmm_google_groups --groups {dev,eval}
./bin/verify_gmm.py -d voxforge -p energy-2gauss -e mfcc-60 -a gmm-voxforge -s ubm_gmm_sge --groups {dev,eval} -g 'demanding' -vvv
```
And getting the following results:
```
DEV: EER = 1.981%
EVAL: HTER = 2.074%
```Alain KOMATYAlain KOMATYhttps://gitlab.idiap.ch/bob/bob.bio.spear/-/issues/16bob.bio.spear.extractor.Cepstral() should not ask features_mask as a paramete...2020-10-08T07:14:36ZPavel KORSHUNOVbob.bio.spear.extractor.Cepstral() should not ask features_mask as a parameter but compute it insideConstructor bob.bio.spear.extractor.Cepstral() should compute features_mask based on n_ceps, with_delta, and with_delta_delta parameters instead of asking the caller to provide it.Constructor bob.bio.spear.extractor.Cepstral() should compute features_mask based on n_ceps, with_delta, and with_delta_delta parameters instead of asking the caller to provide it.Pavel KORSHUNOVPavel KORSHUNOVhttps://gitlab.idiap.ch/bob/bob.bio.spear/-/issues/4Using stereo wave files fails2020-10-08T07:14:21ZAndré AnjosUsing stereo wave files fails*Created by: 1kastner*
First of all great thanks for this existing project. I just tried out some of the features at https://github.com/1kastner/SpeakerRecognition and it worked very nicely. The only thing which bothered me was that I t...*Created by: 1kastner*
First of all great thanks for this existing project. I just tried out some of the features at https://github.com/1kastner/SpeakerRecognition and it worked very nicely. The only thing which bothered me was that I tried to use a stereo file and the error message was quite confusing because it was related to the structure of the numpy array. What would rather follow your conventions: throw an exception with an appropriate error message or just use either left or right and provide the user with a warning? I think making shure the data is valid should be part of the base processing.