bob issueshttps://gitlab.idiap.ch/groups/bob/-/issues2022-05-16T14:42:09Zhttps://gitlab.idiap.ch/bob/bob.db.verafinger/-/issues/2DEPRECATION. Question2022-05-16T14:42:09ZTiago de Freitas PereiraDEPRECATION. QuestionHi @bob, sorry for the spam, but this is needed.
With our new efforts to put this new pipeline mechanism in place, shall we deprecate this package?
Who is against it?
ThanksHi @bob, sorry for the spam, but this is needed.
With our new efforts to put this new pipeline mechanism in place, shall we deprecate this package?
Who is against it?
ThanksBob 9.0.0https://gitlab.idiap.ch/bob/bob.db.banca/-/issues/3DEPRECATION. Question2020-11-02T14:14:09ZTiago de Freitas PereiraDEPRECATION. QuestionHi @bob, sorry for the spam, but this is needed.
With our new efforts to put this new pipeline mechanism in place, shall we deprecate this package?
Who is against it?
ThanksHi @bob, sorry for the spam, but this is needed.
With our new efforts to put this new pipeline mechanism in place, shall we deprecate this package?
Who is against it?
ThanksBob 9.0.0https://gitlab.idiap.ch/bob/bob.bio.spear/-/issues/36DEPRECATION. Question2020-11-12T08:48:27ZTiago de Freitas PereiraDEPRECATION. Question@bob,
With our new efforts to put this new pipeline mechanism in place, shall we deprecate this package?
Who is against it?
Thanks@bob,
With our new efforts to put this new pipeline mechanism in place, shall we deprecate this package?
Who is against it?
ThanksBob 9.0.0https://gitlab.idiap.ch/bob/bob/-/issues/261Possible changing plan2020-12-15T08:35:24ZTiago de Freitas PereiraPossible changing planI will keep this issue opened to keep track of a possible changing plan for Bob.
For the moment, follow below possible candidates that we could archive.
We have 116 packages in total,
- [ ] bob.buildout
- [ ] bob.extension
- [ ] bob.bl...I will keep this issue opened to keep track of a possible changing plan for Bob.
For the moment, follow below possible candidates that we could archive.
We have 116 packages in total,
- [ ] bob.buildout
- [ ] bob.extension
- [ ] bob.blitz
- [ ] bob.core
- [ ] bob.io.base
- [ ] bob.math
- [ ] bob.measure
- [ ] bob.io.image
- [ ] bob.db.base
- [ ] bob.io.video
- [x] bob.io.matlab
- [ ] bob.io.audio
- [ ] bob.sp
- [ ] bob.ap
- [ ] bob.ip.base
- [ ] bob.ip.color
- [x] bob.ip.draw
- [ ] bob.ip.gabor
- [ ] bob.learn.activation
- [x] bob.learn.libsvm
- [ ] bob.learn.linear
- [x] bob.learn.mlp
- [x] bob.learn.boosting
- [ ] bob.db.iris
- [ ] bob.learn.em
- [x] bob.db.wine
- [ ] bob.db.mnist
- [ ] bob.db.atnt
- [ ] bob.ip.facedetect
- [x] bob.ip.optflow.hornschunck
- [x] bob.ip.optflow.liu
- [x] bob.ip.flandmark
- [ ] gridtk
- [ ] bob.ip.qualitymeasure
- [ ] bob.ip.skincolorfilter
- [x] bob.ip.facelandmarks
- [x] bob.ip.dlib
- [ ] bob.db.arface
- [ ] bob.db.asvspoof
- [ ] bob.db.asvspoof2017
- [ ] bob.db.atvskeystroke
- [x] bob.db.avspoof
- [x] bob.db.banca
- [x] bob.db.biosecure
- [x] bob.db.biosecurid.face
- [ ] bob.db.casia_fasd
- [x] bob.db.casme2
- [x] bob.db.caspeal
- [x] bob.db.cohface
- [x] bob.db.frgc
- [ ] bob.db.gbu
- [x] bob.db.hci_tagging
- [x] bob.db.ijba
- [ ] bob.db.ijbc
- [ ] bob.db.kboc16
- [ ] bob.db.lfw
- [ ] bob.db.livdet2013
- [ ] bob.db.mobio
- [x] bob.db.msu_mfsd_mod
- [ ] bob.db.multipie
- [x] bob.db.nist_sre12
- [ ] bob.db.putvein
- [ ] bob.db.replay
- [ ] bob.db.replaymobile
- [x] bob.db.scface
- [ ] bob.db.utfvp
- [ ] bob.db.verafinger
- [ ] bob.db.fv3d
- [ ] bob.db.hkpu
- [ ] bob.db.thufvdt
- [ ] bob.db.mmcbnu6k
- [ ] bob.db.hmtvein
- [ ] bob.db.voicepa
- [x] bob.db.xm2vts
- [ ] bob.db.youtube
- [x] bob.db.pericrosseye
- [ ] bob.db.maskattack
- [ ] bob.db.casiasurf
- [ ] bob.db.fargo
- [ ] bob.bio.base
- [ ] bob.bio.gmm
- [ ] bob.bio.face
- [x] bob.bio.spear
- [ ] bob.bio.video
- [ ] bob.bio.vein
- [ ] bob.db.voxforge
- [x] bob.rppg.base
- [ ] bob.pad.base
- [ ] bob.pad.face
- [x] bob.pad.voice
- [x] bob.pad.vein
- [ ] bob.fusion.base
- [ ] bob.db.oulunpu
- [ ] bob.db.uvad
- [ ] bob.db.swan
- [ ] bob.db.cuhk_cufs
- [ ] bob.db.cbsr_nir_vis_2
- [ ] bob.db.nivl
- [ ] bob.db.pola_thermal
- [ ] bob.db.cuhk_cufsf
- [ ] bob.db.ldhf
- [ ] bob.ip.tensorflow_extractor
- [ ] bob.learn.tensorflow
- [ ] bob.learn.pytorch
- [x] bob.bio.face_ongoing
- [ ] bob.bio.htface
- [ ] bob.db.drive
- [ ] bob.db.stare
- [ ] bob.db.chasedb1
- [ ] bob.db.iostar
- [ ] bob.db.hrf
- [ ] bob.db.rimoner3
- [ ] bob.db.drionsdb
- [ ] bob.db.refuge
- [ ] bob.db.drishtigs1
- [ ] bob.ip.binsegBob 9.0.0https://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.bio.base/-/issues/130Functions in submodule `load` cannot handle identities or labels with spaces ...2021-05-19T17:10:47ZAndré AnjosFunctions in submodule `load` cannot handle identities or labels with spaces on themThe following score file, for example, cannot be correctly loaded:
```text
id1 id1 name with spaces 1.0
id1 id2 another name with spaces 0.0
```
Inside the submodule `load.py` in this package, we use `csv.read` to read the file content...The following score file, for example, cannot be correctly loaded:
```text
id1 id1 name with spaces 1.0
id1 id2 another name with spaces 0.0
```
Inside the submodule `load.py` in this package, we use `csv.read` to read the file contents. Therefore, I was expecting the following change to work properly:
```text
id1 id1 "name with spaces" 1.0
id1 id2 "another name with spaces" 0.0
```
However, that does not work either because of the way `_estimate_score_file_format()` works - i.e., by using another function to figure out the number of columns than `csv.read`.
If you have suggestions on how to correctly handle this, they are welcome!Bob 9.0.0https://gitlab.idiap.ch/bob/bob.pad.base/-/issues/27Problem importing `evaluate.py`2021-03-26T09:48:58ZManuel Günthersiebenkopf@googlemail.comProblem importing `evaluate.py`I am not sure if this is a real bug or if I do not understand some implicitly happening things with the new way of handling the evaluation via `bob pad ...`.
As reported in https://groups.google.com/d/msg/bob-devel/5KpSh0SId34/wGa6MEwoA...I am not sure if this is a real bug or if I do not understand some implicitly happening things with the new way of handling the evaluation via `bob pad ...`.
As reported in https://groups.google.com/d/msg/bob-devel/5KpSh0SId34/wGa6MEwoAQAJ
there seems to be an issue with importing things in: https://gitlab.idiap.ch/bob/bob.pad.base/blob/f322e5d09d4844a0abf2ebb7acf24f06ea31eb68/bob/pad/base/script/evaluate.py#L8
I cannot see any of these imports being in the same directory as the `evaluate.py`, so I don't think that importing `evaluate.py` would work in any circumstance.Bob 9.0.0Yannick DAYERYannick DAYERhttps://gitlab.idiap.ch/bob/bob/-/issues/255Remove traces of evaluate.py and other old plotting scripts2020-12-15T08:44:53ZAmir MOHAMMADIRemove traces of evaluate.py and other old plotting scriptsOnce the plotting scripts are implemented in Bob, it's a good idea to remove traces of them in the documentation too.
For example, bob.pad.face still points to evaluate.py in its documentation.Once the plotting scripts are implemented in Bob, it's a good idea to remove traces of them in the documentation too.
For example, bob.pad.face still points to evaluate.py in its documentation.Bob 9.0.0https://gitlab.idiap.ch/bob/bob.bio.base/-/issues/107Replace the bob_bio_database to our nice Global Configuration System2020-10-16T14:48:41ZTiago de Freitas PereiraReplace the bob_bio_database to our nice Global Configuration SystemHi,
Since we have this very elegant way to define system global parameters in bob.extension (https://www.idiap.ch/software/bob/docs/bob/bob.extension/stable/rc.html), I think it's time to use this solution instead of `bob_bio_databases....Hi,
Since we have this very elegant way to define system global parameters in bob.extension (https://www.idiap.ch/software/bob/docs/bob/bob.extension/stable/rc.html), I think it's time to use this solution instead of `bob_bio_databases.txt` https://www.idiap.ch/software/bob/docs/bob/bob.bio.base/stable/installation.html?highlight=bob_bio_databases#databases
Basically we would replace this:
```
atnt_directory = "[YOUR_ATNT_DIRECTORY]"
database = AtntBioDatabase(
original_directory=atnt_directory,
original_extension=".pgm",
)
```
to this
```
from bob.extension import rc
database = AtntBioDatabase(
original_directory=rc['bob.db.atnt.directory'],
original_extension=".pgm",
)
```
We would need to update the following packages:
- [ ] bob.bio.base
- [ ] bob.bio.face
- [ ] bob.bio.vein
- [ ] bob.bio.spear
What do you think?
CheersBob 9.0.0https://gitlab.idiap.ch/bob/bob.bio.base/-/issues/106Using Bob as a library: Don't force HDF5 serialization2020-10-16T14:49:57ZJaden DIEFENBAUGHUsing Bob as a library: Don't force HDF5 serializationThere are many, many places in `bob.bio.base` & the associated ecosystem where it is assumed the user wants to serialize information to an HDF5 file (for example, [`bob.bio.base.PCA`'s `train_projector()`](https://www.idiap.ch/software/b...There are many, many places in `bob.bio.base` & the associated ecosystem where it is assumed the user wants to serialize information to an HDF5 file (for example, [`bob.bio.base.PCA`'s `train_projector()`](https://www.idiap.ch/software/bob/docs/bob/bob.bio.base/master/_modules/bob/bio/base/algorithm/PCA.html#PCA.train_projector) always writes to an HDF5 file). This is an issue when using Bob tools in different use-cases & environments, as there's no guarantee that a user wants to write to an HDF5 file. Sometimes the user _can't_ write to files, such as in BEAT, which is the specific use-case that concerns me.
(Disk) serialization should at least be opt-in, and the data that was previously saved to disk by default should be returned by the function instead. For the above PCA example, this would change `train_projector()` to return the variances by default, and optionally write them to disk. Changes like this is the bare minimum needed to use these Bob tools in BEAT.
Honestly, though, serialization endpoints (disk, network, whatever) in general should be separated from individual Bob tools. A preprocessor/extractor/algorithm/whatever should have a method for general serialization as well as a method for rehydrating the instance using this data (this is already present in many places, but is just hard-coded to write to an HDF5 file). Some `bob.serialization` package could handle writing this data to disks/caches/networks/whatever.
What does everyone think?Bob 9.0.0https://gitlab.idiap.ch/bob/bob.db.base/-/issues/22Loading data from databases with minimal parameters provided2021-06-24T12:54:01ZAmir MOHAMMADILoading data from databases with minimal parameters providedAs of now it seems that we do not have a single way to load a sample in our databases.
The old db's load like this:
```python
db = Database(original_directory='/some/path')
sample = db.objects()[0]
data = sample.load(db.original_directo...As of now it seems that we do not have a single way to load a sample in our databases.
The old db's load like this:
```python
db = Database(original_directory='/some/path')
sample = db.objects()[0]
data = sample.load(db.original_directory, db.original_extension)
```
The current guide advices this:
```python
db = Database(original_directory='/some/path')
sample = db.objects()[0]
data = sample.load()
```
but this requires changes in all db interfaces because it suggests that each db sample object will carry a reference to `original_directory`.
I suggest we do like this:
```python
db = Database(original_directory='/some/path')
sample = db.objects()[0]
data = db.load(sample)
```
This is similar in how annotations are returned in high-level interfaces and hides away the fact that the database is a file-based one.
It can be easily implemented for all current databases that we have like this:
```python
class bob.db.base.Database:
def load(self, file):
return file.load(self.original_directory, self.original_extension)
```
What do you think?Bob 9.0.0https://gitlab.idiap.ch/bob/bob.bio.base/-/issues/100Correctly protecting strings with spaces in score files2021-05-19T17:11:09ZAndré AnjosCorrectly protecting strings with spaces in score filesCurrently, this package does not protect strings when they are written to score files. That means `evaluate.py` cannot do its job in score files with spaces on identities or labels such as the one described in bob/bob.measure#36.
Since ...Currently, this package does not protect strings when they are written to score files. That means `evaluate.py` cannot do its job in score files with spaces on identities or labels such as the one described in bob/bob.measure#36.
Since `bob.measure.load` uses `csv.read` to load score files (please confirm), the robust way to handle this could be like this:
1. Fix bob/bob.measure#36
2. In this package, protect strings dumped during scoring in case they have spaces, using a `"` (double-quotes) delimiterBob 9.0.0https://gitlab.idiap.ch/bob/bob.db.base/-/issues/21The file-based databases should not have an option of original_extension2021-06-24T12:53:33ZAmir MOHAMMADIThe file-based databases should not have an option of original_extension@andre.anjos raised this issue yesterday. Since the discussions we do offline tend to get lost and ignored, I am opening an issue for it here.@andre.anjos raised this issue yesterday. Since the discussions we do offline tend to get lost and ignored, I am opening an issue for it here.Bob 9.0.0https://gitlab.idiap.ch/bob/bob.bio.face/-/issues/26Use the new sequential preprocessors and annotators API here2020-11-05T14:30:04ZAmir MOHAMMADIUse the new sequential preprocessors and annotators API hereNow that we have an implementation of the [Sequential Preprocessor](https://www.idiap.ch/software/bob/docs/bob/bob.bio.base/master/implemented.html#bob.bio.base.preprocessor.SequentialPreprocessor), it makes sense to take some of the pre...Now that we have an implementation of the [Sequential Preprocessor](https://www.idiap.ch/software/bob/docs/bob/bob.bio.base/master/implemented.html#bob.bio.base.preprocessor.SequentialPreprocessor), it makes sense to take some of the preprocessors here and implement them using that.
Also, some preprocessors like FaceDetect could take advantage of our new annotators API.Bob 9.0.0Amir MOHAMMADIAmir MOHAMMADIhttps://gitlab.idiap.ch/bob/bob.bio.spear/-/issues/26Re-enable bob.db.mobio tests2018-04-16T14:59:56ZAmir MOHAMMADIRe-enable bob.db.mobio tests@pkorshunov I don't think disabling a test so that you can release is a good idea.
Here is the commit that just went silently in the master
https://gitlab.idiap.ch/bob/bob.bio.spear/commit/ca993a954968231c214730ce730defc7239ded3d@pkorshunov I don't think disabling a test so that you can release is a good idea.
Here is the commit that just went silently in the master
https://gitlab.idiap.ch/bob/bob.bio.spear/commit/ca993a954968231c214730ce730defc7239ded3dBob 2.7.x releasePavel KORSHUNOVPavel KORSHUNOVhttps://gitlab.idiap.ch/bob/bob.extension/-/issues/37naming convention for scripts generated on extensions2017-08-11T22:23:17ZAndré Anjosnaming convention for scripts generated on extensionsAs the number of packages grow, the probabily of scripts with the same name will also increase. In order to support a structured development, we need to come out with a method for naming scripts in packages so multiple packages can be in...As the number of packages grow, the probabily of scripts with the same name will also increase. In order to support a structured development, we need to come out with a method for naming scripts in packages so multiple packages can be installed in the same code base.Bob 2.7.x releaseGuillaume HEUSCHGuillaume HEUSCHhttps://gitlab.idiap.ch/bob/bob.learn.libsvm/-/issues/9SVM in sequence segmenation fault2017-10-21T19:07:03ZTiago de Freitas PereiraSVM in sequence segmenation faultWhen you try to train several SVMs in sequence we have segmentation fault.
Follow a code that reproduces the issue (2 SVMs in sequence):
```
import bob.learn.libsvm
import numpy
numpy.random.seed(10)
for i in range(2):
pos = numpy....When you try to train several SVMs in sequence we have segmentation fault.
Follow a code that reproduces the issue (2 SVMs in sequence):
```
import bob.learn.libsvm
import numpy
numpy.random.seed(10)
for i in range(2):
pos = numpy.random.normal(0., 1, size=(100, 2))
neg = numpy.random.normal(1., 1, size=(100, 2))
data = [pos, neg]
trainer = bob.learn.libsvm.Trainer()
trainer.kernel_type = 'LINEAR'
trainer.cost = 1
trainer.train(data)
```
However, if you free the data variables in the end of loop for, everything runs fine
```
import bob.learn.libsvm
import numpy
numpy.random.seed(10)
for i in range(2):
pos = numpy.random.normal(0., 1, size=(100, 2))
neg = numpy.random.normal(1., 1, size=(100, 2))
data = [pos, neg]
trainer = bob.learn.libsvm.Trainer()
trainer.kernel_type = 'LINEAR'
trainer.cost = 1
trainer.train(data)
del data
del pos
del neg
```
I'm still debugging, but it seems that the issue is somewhere here in the bindings (https://gitlab.idiap.ch/bob/bob.learn.libsvm/blob/master/bob/learn/libsvm/trainer.cpp#L616)Bob 2.7.x releaseTiago de Freitas PereiraTiago de Freitas Pereirahttps://gitlab.idiap.ch/bob/nightlies/-/issues/25Timeout2017-10-04T19:42:19ZTiago de Freitas PereiraTimeoutHey,
Every night is the same, our nightlies are failing because of some time out.
The majority of the occurences are with `bob.db.mnist`. Look the logs bellow.
I know that we cannot host the raw data ourselves, but can we do it just f...Hey,
Every night is the same, our nightlies are failing because of some time out.
The majority of the occurences are with `bob.db.mnist`. Look the logs bellow.
I know that we cannot host the raw data ourselves, but can we do it just for internal connections?
This will mitigate the failures.
- https://gitlab.idiap.ch/bob/bob.nightlies/builds/49615
- https://gitlab.idiap.ch/bob/bob.nightlies/builds/49614
- https://gitlab.idiap.ch/bob/bob.nightlies/builds/49619
- https://gitlab.idiap.ch/bob/bob.nightlies/builds/49618
ThanksBob 2.7.x releaseAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/bob/bob.bio.base/-/issues/73Incorporate a general overview of biometric verification and illustrate biome...2017-08-07T13:07:35ZVedrana KRIVOKUCAIncorporate a general overview of biometric verification and illustrate biometric verification experiment flow in bob.bio.base docA general overview of the structure of a typical biometric verification system should be added as introductory material inside the bob.bio.base documentation on running biometric recognition experiments.
Also, there should be some dia...A general overview of the structure of a typical biometric verification system should be added as introductory material inside the bob.bio.base documentation on running biometric recognition experiments.
Also, there should be some diagrams (+ accompanying explanations) to facilitate better understanding of the biometric verification experiment flow in bob.bio.base.
After much deliberation, I also believe we should be using the word "verification" instead of the more general word "recognition", simply because our main script is called verify.py (not recognise.py or identify.py).May 2017 HackathonManuel Günthersiebenkopf@googlemail.comManuel Günthersiebenkopf@googlemail.comhttps://gitlab.idiap.ch/bob/bob.db.base/-/issues/16It seems latest changes to bob.db.base breaks bob.pad.base (at least)2017-09-30T18:11:14ZPavel KORSHUNOVIt seems latest changes to bob.db.base breaks bob.pad.base (at least)See build here:https://gitlab.idiap.ch/bob/bob.pad.base/builds/61260
It is possible that bob.bio.base would be broken too
```
ERROR: test01_database (bob.pad.base.test.test_databases.DummyDatabaseSqlTest)
------------------------...See build here:https://gitlab.idiap.ch/bob/bob.pad.base/builds/61260
It is possible that bob.bio.base would be broken too
```
ERROR: test01_database (bob.pad.base.test.test_databases.DummyDatabaseSqlTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/gitlab-runner/builds/0d638152/0/bob/bob.pad.base/build-prefix/lib/python2.7/site-packages/bob/pad/base/test/test_databases.py", line 48, in test01_database
assert db.original_file_name(file) == "original/directory/test/path.orig"
File "/home/gitlab-runner/builds/0d638152/0/bob/bob.pad.base/build-prefix/lib/python2.7/site-packages/bob/db/base/database.py", line 230, in original_file_name
"The original_directory and/or the original_extension were not specified in the constructor.")
ValueError: The original_directory and/or the original_extension were not specified in the constructor.
```May 2017 HackathonAmir MOHAMMADIAmir MOHAMMADI