bob issueshttps://gitlab.idiap.ch/groups/bob/-/issues2024-01-08T13:58:44Zhttps://gitlab.idiap.ch/bob/bob.pipelines/-/issues/21Who is Mario?2024-01-08T13:58:44ZTiago de Freitas PereiraWho is Mario?There are several places in the code where we alias `bob.pipelines` as Mario.
Well, it was a good joke at the beginning but now we need to think if we want to keep this.There are several places in the code where we alias `bob.pipelines` as Mario.
Well, it was a good joke at the beginning but now we need to think if we want to keep this.Tiago de Freitas PereiraTiago de Freitas Pereirahttps://gitlab.idiap.ch/bob/bob.devtools/-/issues/60Mac builds take more than 2 hours to finish2020-11-04T17:16:13ZAmir MOHAMMADIMac builds take more than 2 hours to finishThere is something wrong with our mac builds. They take a long time to finish. I increased the timeout from 1h to 2h but they are still failing, e.g.: https://gitlab.idiap.ch/bob/bob.devtools/-/jobs/215023There is something wrong with our mac builds. They take a long time to finish. I increased the timeout from 1h to 2h but they are still failing, e.g.: https://gitlab.idiap.ch/bob/bob.devtools/-/jobs/215023https://gitlab.idiap.ch/bob/bob.chapter.FRICE/-/issues/2Package is not working in Python 3 and with current Bob version2020-10-30T11:54:12ZManuel Günthersiebenkopf@googlemail.comPackage is not working in Python 3 and with current Bob versionIt has been a while that this package was uploaded, and Bob has changed in the meantime. Additionally, there are some parts that are incompatible with Python 3 (e.g., the `StringIO` works differently in Python 3).It has been a while that this package was uploaded, and Bob has changed in the meantime. Additionally, there are some parts that are incompatible with Python 3 (e.g., the `StringIO` works differently in Python 3).Manuel Günthersiebenkopf@googlemail.comManuel Günthersiebenkopf@googlemail.comhttps://gitlab.idiap.ch/bob/bob.ip.stereo/-/issues/4pybind11 is not a runtime dependency2021-01-26T16:05:29ZAmir MOHAMMADIpybind11 is not a runtime dependencyFrom what I have seen, e.g. https://github.com/pybind/python_example/blob/master/conda.recipe/meta.yaml, pybind11 is only a build time requirement and not a run time requirement. However, pybind11 is listed in the run section of the cond...From what I have seen, e.g. https://github.com/pybind/python_example/blob/master/conda.recipe/meta.yaml, pybind11 is only a build time requirement and not a run time requirement. However, pybind11 is listed in the run section of the conda recipe of this package as well.
Is this necessary? Can we remove it?Vincent POLLETVincent POLLEThttps://gitlab.idiap.ch/bob/bob.devtools/-/issues/59Invalid syntax in bootstrap.py2020-10-20T08:30:46ZSamuel GAISTInvalid syntax in bootstrap.pyCurrently [line 341 of boostrap.py](https://gitlab.idiap.ch/bob/bob.devtools/-/blob/master/bob/devtools/bootstrap.py#L341) which is:
`f"{'public' if public else 'private'}/{'stable' if stable else 'beta'}"`
Triggers invalid syntax on a...Currently [line 341 of boostrap.py](https://gitlab.idiap.ch/bob/bob.devtools/-/blob/master/bob/devtools/bootstrap.py#L341) which is:
`f"{'public' if public else 'private'}/{'stable' if stable else 'beta'}"`
Triggers invalid syntax on all build runs of the beat packages.
This is valid Python 3.6 code however, until all CI Linux runners are updated to Buster, it cannot be used.
The bootstrap process runs using the system Python which is currently Python 3.5 on the Linux nodes.Amir MOHAMMADIAmir MOHAMMADIhttps://gitlab.idiap.ch/bob/bob.bio.base/-/issues/141New pipeline for biometric template protection (BTP)2021-06-02T10:22:23ZHatef OTROSHINew pipeline for biometric template protection (BTP)Hi,
After the last Bob meeting last week, I was wondering if we could develop a new pipeline for biometric template protection (BTP) schemes. For a better understanding of the concept of BTP, I have reviewed it hereunder:
- **Review to...Hi,
After the last Bob meeting last week, I was wondering if we could develop a new pipeline for biometric template protection (BTP) schemes. For a better understanding of the concept of BTP, I have reviewed it hereunder:
- **Review to Biometric Systems**
As you know, each biometric recognition system has some main parts:
1) Feature extraction,
2) System Database (to store biometric features during enrollment),
3) Matching, and Scoring.
- **Motivation to BTP:**
A very crucial concern is that if the biometric templates which are stored at the system's database are compromised, it can cause crucial challenges for the user's privacy:
- the attacker can use the unprotected templates and impersonate to hack the recognition system.
- more important: since biometric data are unique if (unprotected) biometric features are compromised, they can not be revoked! Therefore, the attacker can use the person's biometric features to attack any other biometric systems.
- **How do BTP schemes work in general?**
To explain the process in general without going into details, BTP schemes aim to generate protected templates, and then make the recognition according to the protected templates. A very simple setup can be a transformation after the feature extraction stage to generate protected templates and also new algorithms for comparing and matching.
Considering different setup of the biometric recognition systems secured with BTP schemes, it can be useful to create and develop a new pipeline in Bob for such systems, e.g., in [bob.bio.btp](https://gitlab.idiap.ch/bob/bob.bio.btp).
@vkrivokuca @tiago.pereiraHatef OTROSHIHatef OTROSHIhttps://gitlab.idiap.ch/bob/bob.bio.base/-/issues/140Dask client is created by user but stopped by vanilla-biometrics2020-12-07T13:25:43ZLaurent COLBOISDask client is created by user but stopped by vanilla-biometricsHello,
Currently to use vanilla-biometrics one has to provide an already instantiated Dask client, which is closed by the vanilla-biometrics script at the end of the run.
This gives the false impression that one can instantiate a Dask cl...Hello,
Currently to use vanilla-biometrics one has to provide an already instantiated Dask client, which is closed by the vanilla-biometrics script at the end of the run.
This gives the false impression that one can instantiate a Dask client in a Python script, and then use it for several successive vanilla-biometrics experiment, which is not the case.
Should maybe the opening/closing of the Dask client be entirely handled either by the user, or by the vanilla-biometrics script ? In the latter case I guess some configuration dict for the client could be passed instead when calling vanilla-biometrics.
@ydayerhttps://gitlab.idiap.ch/bob/bob.bio.vein/-/issues/22PC feature extractor2020-11-03T16:03:18ZHatef OTROSHIPC feature extractorHi there,
I tried to use PC feature extractor, but the code is not working for me. In particular, there is a function `ut_gauss()` which is used but it seems it is not been defined or imported. See for example [L46](https://gitlab.idiap...Hi there,
I tried to use PC feature extractor, but the code is not working for me. In particular, there is a function `ut_gauss()` which is used but it seems it is not been defined or imported. See for example [L46](https://gitlab.idiap.ch/bob/bob.bio.vein/-/blob/master/bob/bio/vein/extractor/PrincipalCurvature.py#L46) or [L47](https://gitlab.idiap.ch/bob/bob.bio.vein/-/blob/master/bob/bio/vein/extractor/PrincipalCurvature.py#L47) . I was wondering if anyone can has any experience with it and can help.
Best,
Hatefhttps://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/-/issues/263Bob 8.0.02020-10-06T06:13:03ZTiago de Freitas PereiraBob 8.0.0Hi guys,
I just pinned all bob packages on Friday and during the weekend (nightlies were green before this).
However, I can't release the bob meta-package for some unreadable set of conda conflicts
https://gitlab.idiap.ch/bob/bob/-/jo...Hi guys,
I just pinned all bob packages on Friday and during the weekend (nightlies were green before this).
However, I can't release the bob meta-package for some unreadable set of conda conflicts
https://gitlab.idiap.ch/bob/bob/-/jobs/212111
I would appreciate some insights on this
Thankshttps://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.measure/-/issues/63bob measure pure python2021-06-10T11:11:12ZTiago de Freitas Pereirabob measure pure pythonHi @bob,
Following our renovation efforts for Bob, shall we make an effort to port this package to be pure python?
The benefits would be:
- Pure python is more convenient (no platform-dependent) than having a compiled one
- More read...Hi @bob,
Following our renovation efforts for Bob, shall we make an effort to port this package to be pure python?
The benefits would be:
- Pure python is more convenient (no platform-dependent) than having a compiled one
- More readable code. Hence, more people would be willing to contribute
- We would get rid of a blitz dependency (that will die at some point)
The drawbacks:
- We would lose the C++ API (does anyone need that?)
- Extra work
Follow bellow all the functions that would need to be ported.
- bob::measure::farfrr
- bob::measure::precision_recall
- bob::measure::f_score
- bob::measure::correctlyClassifiedPositives
- bob::measure::correctlyClassifiedNegatives
- bob::measure::minimizingThreshold
- bob::measure::eerThreshold
- bob::measure::eerRocch
- bob::measure::minWeightedErrorRateThreshold
- bob::measure::minHterThreshold
- bob::measure::farThreshold
- bob::measure::frrThreshold
- bob::measure::log_values
- bob::measure::meaningfulThresholds(
- bob::measure::roc
- bob::measure::precision_recall_curve
- bob::measure::rocc
- hbob::measure::rocch2eer
- bob::measure::roc_for_far
- bob::measure::ppndf
- bob::measure::det
- bob::measure::epc
Thankshttps://gitlab.idiap.ch/bob/bob.measure/-/issues/62Visualization in a plot with several curves2020-08-07T08:20:18ZHatef OTROSHIVisualization in a plot with several curvesHi,
I was trying to plot ROC curves of several models with `bob bio roc`. Since there are many curves in a plot, it is hard to understand each one and distinguish them. Below, you can find a sample of such plot:
![magma](/uploads/dc3090...Hi,
I was trying to plot ROC curves of several models with `bob bio roc`. Since there are many curves in a plot, it is hard to understand each one and distinguish them. Below, you can find a sample of such plot:
![magma](/uploads/dc30907b6bc6a3cbbf6c4a13e2d4f08a/magma.png)
I was wondering how I can achieve a better visualization. If we use `--line-styles` option in `bob bio roc` we will have a result as below which is still not clear:
![magma_line](/uploads/6b9e27f89c35dd54c946a0fd5ba48290/magma_line.png)
I was searching if I could find a better color map and change the color map of `matplotlib`. Inspired by [this plot](https://stackoverflow.com/a/35971096), I changed the color map by replacing [this line](https://gitlab.idiap.ch/bob/bob.measure/-/blob/master/bob/measure/utils.py#L141) in `bob.measure` with `cmap = pyplot.cm.get_cmap(name='gist_ncar')`- only changing the color map. Here is the result:
![gist_ncar](/uploads/fb6e7a5b3a442c1c355e6b92ded0cef8/gist_ncar.png)
And if I use `--line-styles` option as well, it results the following plot while the above plot is still more clear:
![gist_ncar_line](/uploads/988767d0c726939fad088b31e7c0ead4/gist_ncar_line.png)https://gitlab.idiap.ch/bob/bob.ip.stereo/-/issues/2In painting has different output based on computer OS2020-08-03T14:03:02ZVincent POLLETIn painting has different output based on computer OSJob [#204940](https://gitlab.idiap.ch/bob/bob.ip.stereo/-/jobs/204940) failed for aa03ba735badaad5f13e062e5074584b66fadf34:
When the `StereoParameter` has `inpaint = True` like [here](https://gitlab.idiap.ch/bob/bob.ip.stereo/-/blob/deb...Job [#204940](https://gitlab.idiap.ch/bob/bob.ip.stereo/-/jobs/204940) failed for aa03ba735badaad5f13e062e5074584b66fadf34:
When the `StereoParameter` has `inpaint = True` like [here](https://gitlab.idiap.ch/bob/bob.ip.stereo/-/blob/debug_inpaint/bob/ip/stereo/test/test.py#L49), the disparity is modified [here](https://gitlab.idiap.ch/bob/bob.ip.stereo/-/blob/master/bob/ip/stereo/stereo.py#L93) and the output of `cv.inpaint` is a little bit different depending on the OS the code is running on. The differences must be amplified later on because the final output image has pixels with rather different values, even though the images look very similar. This makes the test fail on mac runners in the CI.
@dgeissbuhler Did you observe this kind of behaviour from opencv function before ? Can we use another inpainting method ?
The versions of opencv are the same on Linux and Mac ; could the difference could come from the underlying algebra librairies ?
## Opencv version sur linux et mac
| | | |
|---|---|---|
libopencv | 3.4.2 | hb342d67_1 | defaults
opencv | 3.4.2 | py37h6fd60c2_1 | defaults
py-opencv | 3.4.2 | py37hb342d67_1 | defaults
# Output on linux
![rep_color_mac_lin_disparity](/uploads/6670692ca814ebc831f0c949d6f9e6bb/rep_color_mac_lin_disparity.png)
# Output on mac
![rep_color_mac_mac_disparity](/uploads/0d5f4c571914453921453c8d7d7815d1/rep_color_mac_mac_disparity.png)
# Difference between linux and mac
![output_diff](/uploads/0324b25dad47d75c5c0757e78aa53d55/output_diff.png)
[disparity_linux.npy](/uploads/26fb411a4ff963564ee35a3fbfa77456/disparity_lin.npy)
[disparity_mac.npy](/uploads/269cd455bb62c71cd45cd2b0c7a1ed01/disparity_mac.npy)
[output_linux.npy](/uploads/dc0d3aae2f5a1b23544d04d047c29a71/rep_color_mac_lin_disparity.npy)
[output_map.npy](/uploads/4a67dd48afdc1b20a8fa939fdb7a32e5/rep_color_mac_mac_disparity.npy)Vincent POLLETVincent POLLEThttps://gitlab.idiap.ch/bob/bob.devtools/-/issues/57noarch packages are built and uploaded twice2020-07-30T13:25:21ZAmir MOHAMMADInoarch packages are built and uploaded twiceSee: https://gitlab.idiap.ch/bob/bob.devtools/-/jobs/204868
noarch packages are built in both linux and mac and the resulting packages are uploaded twice.See: https://gitlab.idiap.ch/bob/bob.devtools/-/jobs/204868
noarch packages are built in both linux and mac and the resulting packages are uploaded twice.Amir MOHAMMADIAmir MOHAMMADIhttps://gitlab.idiap.ch/bob/docs/-/issues/8docs requires changes here to build bob.ip.binseg properly2020-07-24T14:16:43ZAmir MOHAMMADIdocs requires changes here to build bob.ip.binseg properlySee https://gitlab.idiap.ch/bob/docs/-/jobs/204340
- There are `_templates` and `_static` folders in bob.ip.binseg
- There are these warnings:
```
bob.ip.binseg/doc/cli.rst:13: WARNING: Unknown directive type "command-output"
```See https://gitlab.idiap.ch/bob/docs/-/jobs/204340
- There are `_templates` and `_static` folders in bob.ip.binseg
- There are these warnings:
```
bob.ip.binseg/doc/cli.rst:13: WARNING: Unknown directive type "command-output"
```André AnjosAndré Anjoshttps://gitlab.idiap.ch/bob/bob.devtools/-/issues/56python-gitlab in our beta channel2020-07-29T14:07:11ZAmir MOHAMMADIpython-gitlab in our beta channelI don't know why but somehow we have the `python-gitlab` package in our beta channel:
![image](/uploads/677dd62b2f514d899aa579754c3544b3/image.png)
from https://www.idiap.ch/software/bob/conda/label/beta/linux-64/?C=N;O=AI don't know why but somehow we have the `python-gitlab` package in our beta channel:
![image](/uploads/677dd62b2f514d899aa579754c3544b3/image.png)
from https://www.idiap.ch/software/bob/conda/label/beta/linux-64/?C=N;O=AAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/bob/bob.io.stream/-/issues/3warp transform changes dtype2020-08-07T08:33:14ZVincent POLLETwarp transform changes dtypeUsing the `warp` transform changes the dtype of the data to `float64`
In particular, it happens during the `warp` stream `process_frame` [function](https://gitlab.idiap.ch/bob/bob.io.stream/-/blob/unit_tests/bob/io/stream/stream.py#L435...Using the `warp` transform changes the dtype of the data to `float64`
In particular, it happens during the `warp` stream `process_frame` [function](https://gitlab.idiap.ch/bob/bob.io.stream/-/blob/unit_tests/bob/io/stream/stream.py#L435)
This happens even though `preserve_range=True` is passed to `sk-image.transform.warp`, which should preserve it according to the [doc](https://scikit-image.org/docs/dev/api/skimage.transform.html?highlight=warp#warp).
@dgeissbuhler Do you have an idea why this is happening ?
Minimal example (unit_test branch):
```python
import bob.io.stream
import numpy as np
from pkg_resources import resource_filename
f = bob.io.stream.StreamFile(
"test/data/input_example.h5",
"config/idiap_face_streams.json",
resource_filename("bob.ip.stereo", "config/idiap_face_calibration.json"),
)
color = f.stream("color")
warp_color = color.warp(color)
print(color[0].dtype)
print(warp_color[0].dtype)
```
Output:
`uint8`
`float64`
ThanksVincent POLLETVincent POLLEThttps://gitlab.idiap.ch/bob/bob.ip.qualitymeasure/-/issues/5Move bob.io packages to optional or test dependencies2020-07-13T10:11:53ZAmir MOHAMMADIMove bob.io packages to optional or test dependenciesRight now installing bob.ip.qualitymeasure also install bob.io.video and bob.io.image. This is a shame because those packages are not necessarily required for this package to function.Right now installing bob.ip.qualitymeasure also install bob.io.video and bob.io.image. This is a shame because those packages are not necessarily required for this package to function.Amir MOHAMMADIAmir MOHAMMADIhttps://gitlab.idiap.ch/bob/bob.bio.vein/-/issues/20UTFVP database2020-07-16T09:39:19ZHatef OTROSHIUTFVP databaseHi there,
I want to make some experiments using `utfvp` database which is available in `bob.bio.vein` by using the following script:
```
from bob.bio.vein.configurations.utfvp import database
```
However, I can not use `eval` and `world`...Hi there,
I want to make some experiments using `utfvp` database which is available in `bob.bio.vein` by using the following script:
```
from bob.bio.vein.configurations.utfvp import database
```
However, I can not use `eval` and `world` groups for evaluation using `verify.py`.
- when using `eval` group, it can not be found
- when using `world` group, it can calculate the scores but `scores-world` file is empty.
Does anyone have any idea how I should fix these issues?