bob.bio.base issueshttps://gitlab.idiap.ch/bob/bob.bio.base/-/issues2020-04-23T14:53:55Zhttps://gitlab.idiap.ch/bob/bob.bio.base/-/issues/90parallelizing the scoring step for each model.2020-04-23T14:53:55ZAmir MOHAMMADIparallelizing the scoring step for each model.I was wondering if it is possible to parallelize the score computation for one model.
As of now I think the `verify.py` script parallelizes the computations for each model but if one model has too many files, it is going to run in a sing...I was wondering if it is possible to parallelize the score computation for one model.
As of now I think the `verify.py` script parallelizes the computations for each model but if one model has too many files, it is going to run in a single process.https://gitlab.idiap.ch/bob/bob.bio.base/-/issues/50Why is the BioDatabase.model_ids_with_protocol function required?2018-06-03T12:14:15ZManuel Günthersiebenkopf@googlemail.comWhy is the BioDatabase.model_ids_with_protocol function required?I am trying to implement a new database interface for one of our local databases, which uses the `BioFileSet` interface. I have created a class derived from `BioDatabase`, and I am implementing the functions.
While implementing the data...I am trying to implement a new database interface for one of our local databases, which uses the `BioFileSet` interface. I have created a class derived from `BioDatabase`, and I am implementing the functions.
While implementing the database, I was stumbling upon a *pure virtual* function that I don't understand: `model_ids_with_protocol`. Why do I have to implement this function, and why can't I just simply implement the `model_ids` function?
When I see it correctly, the `model_ids_with_protocol` function is called from within `model_ids`: https://gitlab.idiap.ch/bob/bob.bio.base/blob/master/bob/bio/base/database/database.py#L378
passing a the member variable `self.protocol` as the protocol.
This is IMHO completely useless. The `self.protocol` is available in the derived class as well, and it can be used inside there, without needing to pass it as a parameter. The exact same is true for the functions `objects`: https://gitlab.idiap.ch/bob/bob.bio.base/blob/master/bob/bio/base/database/database.py#L381, `object_sets`: https://gitlab.idiap.ch/bob/bob.bio.base/blob/master/bob/bio/base/database/database.py#L565 and the `tmodel_ids_with_protocol`: https://gitlab.idiap.ch/bob/bob.bio.base/blob/master/bob/bio/base/database/database.py#L732
So, is there any reasoning behind having the `protocol` parameters in these functions, other than 'It has been that way in the bob.db.verification.database interface' (where it was required)?
@amohammadihttps://gitlab.idiap.ch/bob/bob.bio.base/-/issues/49dependency to gridtk2018-06-03T12:14:15ZManuel Günthersiebenkopf@googlemail.comdependency to gridtkI was wondering, why this package is now -- by default -- dependent on gridtk?
GridTK is not required to use this package -- not even to run the tests (there is an actual flag that tests if gridtk is installed and skips the tests that ...I was wondering, why this package is now -- by default -- dependent on gridtk?
GridTK is not required to use this package -- not even to run the tests (there is an actual flag that tests if gridtk is installed and skips the tests that require gridtk). I can understand that we have gridtk inside ``test_requirements.txt``, but bob.bio packages do not require gridtk to run (not even ``bob.bio.gmm``). I can understand that it is a nice addition to have, but I don't see, why this is a default requirement.