bob issueshttps://gitlab.idiap.ch/groups/bob/-/issues2021-02-05T18:32:43Zhttps://gitlab.idiap.ch/bob/bob.bio.face/-/issues/40Convention when feeding data to an annotator2021-02-05T18:32:43ZLaurent COLBOISConvention when feeding data to an annotatorHi, I have some trouble using face annotators, and I think the issue is caused by some inconsistency between feeding a batch of images vs a single image when calling the annotator. More precisely :
+ The FaceCrop [sends a **single image*...Hi, I have some trouble using face annotators, and I think the issue is caused by some inconsistency between feeding a batch of images vs a single image when calling the annotator. More precisely :
+ The FaceCrop [sends a **single image** to the annotator](https://gitlab.idiap.ch/bob/bob.bio.face/-/blob/master/bob/bio/face/preprocessor/FaceCrop.py#L349), and [expects to receive a **single dictionary of annotations**](https://gitlab.idiap.ch/bob/bob.bio.face/-/blob/master/bob/bio/face/preprocessor/FaceCrop.py#L299)
+ While (from my understanding)
the [Base annotator](https://gitlab.idiap.ch/bob/bob.bio.face/-/blob/master/bob/bio/face/annotator/Base.py#L5) expects a **list of images** and returns a **list of annotations dictionaries** (one dictionary per provided image).
I should be able to propose an easy fix, but which is the correct expected behavior ?
ping @ydayer @tiago.pereiraLaurent COLBOISLaurent COLBOIShttps://gitlab.idiap.ch/bob/bob/-/issues/266Bob 9.0.0rc12021-07-07T07:34:13ZTiago de Freitas PereiraBob 9.0.0rc1Hi guys,
Since we are in a consistent sequence of green nightlies, I think we can safely have a release candidate of Bob with the new stuff.
I would like to pin everything on `bob.nightlies` as `rc1` and release it on our stable channe...Hi guys,
Since we are in a consistent sequence of green nightlies, I think we can safely have a release candidate of Bob with the new stuff.
I would like to pin everything on `bob.nightlies` as `rc1` and release it on our stable channel.
I would appreciate your input on it.
ThanksBob 9.0.0https://gitlab.idiap.ch/bob/bob.devtools/-/issues/70Removing `llvm-tools` from build dependencies in `bdt create` is undesirable2021-10-29T15:34:56ZAndré AnjosRemoving `llvm-tools` from build dependencies in `bdt create` is undesirableThis was done to overcome another issue regarding `llvm-tools` and its dependence to `libllvm10`.
One of the (build) packages we depend on wants to have `libllvm10=10.0.0`, but "llvm-tools" requires `libllvm10=10.0.1`. This creates a c...This was done to overcome another issue regarding `llvm-tools` and its dependence to `libllvm10`.
One of the (build) packages we depend on wants to have `libllvm10=10.0.0`, but "llvm-tools" requires `libllvm10=10.0.1`. This creates a conflict. Build requirements from our packages will end-up bringing in the requirement for "llvm-tools".
To test this, on a macOS system, try the following:
```sh
$ conda create --dry-run --name xxx --override-channels --channel=http://www.idiap.ch/software/bob/conda/label/beta --channel=http://www.idiap.ch/software/bob/conda --channel=defaults --dry-run 'bob-devel=2021.01.28.*' clang llvm-tools
```
The problem is, possibly, that our own bob-devel brings in dependencies that make the above build tools conflict. Removing any of the 3 packages listed above from the command-line makes the command-line work again. Once that command (or a variant with a newer version of bob-devel) works, the problem is fixed and a patch is no longer required.André AnjosAndré Anjoshttps://gitlab.idiap.ch/bob/bob.devtools/-/issues/69Pin of `smmap<4` is undesirable2021-04-10T11:28:22ZAndré AnjosPin of `smmap<4` is undesirableThis pin was put in place to fix a dependency issue with package `gitdb`, which we don't provide, but depend on.
This can be undone when this (https://github.com/ContinuumIO/anaconda-issues/issues/12255) is fixed.
To undo this work, ju...This pin was put in place to fix a dependency issue with package `gitdb`, which we don't provide, but depend on.
This can be undone when this (https://github.com/ContinuumIO/anaconda-issues/issues/12255) is fixed.
To undo this work, just revert !205.André AnjosAndré Anjoshttps://gitlab.idiap.ch/bob/bob.pad.face/-/issues/39User Guide and Documentation2021-02-15T12:53:56ZTiago de Freitas PereiraUser Guide and DocumentationHi @ydayer,
Could you please do a "pass" in the documentation of this package, to remove traces from `spoof.py`?
ThanksHi @ydayer,
Could you please do a "pass" in the documentation of this package, to remove traces from `spoof.py`?
ThanksBob 9.0.0https://gitlab.idiap.ch/bob/nightlies/-/issues/59Nightlies MacOS SegFault2021-01-22T07:05:43ZTiago de Freitas PereiraNightlies MacOS SegFaultWith this MR https://gitlab.idiap.ch/bob/bob.devtools/-/merge_requests/203 the Seg.fault was solved for individual packages.
However, the problem still remains with nightly builds.
https://gitlab.idiap.ch/bob/nightlies/-/jobs/221664
Lo...With this MR https://gitlab.idiap.ch/bob/bob.devtools/-/merge_requests/203 the Seg.fault was solved for individual packages.
However, the problem still remains with nightly builds.
https://gitlab.idiap.ch/bob/nightlies/-/jobs/221664
Looking at the logs there are still some references pointing to 10.9 `sdk`.
```
creating build/temp.macosx-10.9-x86_64-3.7/bob/blitz
x86_64-apple-darwin13.4.0-clang -fno-strict-aliasing -Wsign-compare -Wunreachable-code -DNDEBUG -fwrapv -O3 -Wall -march=core2 -mtune=haswell -mssse3 -ftree-vectorize -fPIC -fPIE -fstack-protector-strong -O3 -pipe -fdebug-prefix-map=${SRC_DIR}=/usr/local/src/conda/${PKG_NAME}-${PKG_VERSION} -fdebug-prefix-map=$PREFIX=/usr/local/src/conda-prefix -flto -Wl,-export_dynamic -march=core2 -mtune=haswell -mssse3 -ftree-vectorize -fPIC -fPIE -fstack-protector-strong -O3 -march=core2 -mtune=haswell -mssse3 -ftree-vectorize -fPIC -fPIE -fstack-protector-strong -O2 -pipe -isystem $PREFIX/include -fdebug-prefix-map=$SRC_DIR=/usr/local/src/conda/bob.blitz-2.0.23b0 -fdebug-prefix-map=$PREFIX=/usr/local/src/conda-prefix -D_FORTIFY_SOURCE=2 -mmacosx-version-min=10.9 -isystem $PREFIX/include -Wno-strict-aliasing -DBOB_EXT_MODULE_PREFIX="bob.blitz" -DBOB_EXT_MODULE_NAME="version" -DBOB_EXT_ENTRY_NAME=PyInit_version -DBOB_EXT_MODULE_VERSION="2.0.23b0" -DHAVE_BOOST=1 -DHAVE_BLITZ=1 -DPY_ARRAY_UNIQUE_SYMBOL=BOB_BLITZ_NUMPY_C_API -DNO_IMPORT_ARRAY=1 -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -I/Users/gitlab/builds/b6d3167a/0/bob/nightlies/src/bob/bob.blitz/bob/blitz/include -I$PREFIX/lib/python3.7/site-packages/bob/extension/include -I$PREFIX/include/python3.7m -c bob/blitz/version.cpp -o build/temp.macosx-10.9-x86_64-3.7/bob/blitz/version.o -mmacosx-version-min=10.10 -isysroot /opt/MacOSX10.10.sdk -march=core2 -mtune=haswell -mssse3 -ftree-vectorize -fPIC -fPIE -fstack-protector-strong -O2 -pipe -stdlib=libc++ -fvisibility-inlines-hidden -std=c++14 -fmessage-length=0 -fdebug-prefix-map=$SRC_DIR=/usr/local/src/conda/bob.blitz-2.0.23b0 -fdebug-prefix-map=$PREFIX=/usr/local/src/conda-prefix -Wno-#warnings -pthread -isystem $PREFIX/lib/python3.7/site-packages/numpy/core/include -isystem $PREFIX/include
```
or
```
+CPPFLAGS=-D_FORTIFY_SOURCE=2 -mmacosx-version-min=10.9 -isystem $PREFIX/include
```
I don't know if these lines have a major impact. However, I don't know where the 10.9 come from.https://gitlab.idiap.ch/bob/bob.devtools/-/issues/68CI is not working2021-01-19T10:54:42ZTiago de Freitas PereiraCI is not workingFrom today, builds are not working.
https://gitlab.idiap.ch/bob/bob.buildout/-/jobs/221383
What happened with `conda-build`?
Thanks
```
------------------------------------------------------------------------------------------------...From today, builds are not working.
https://gitlab.idiap.ch/bob/bob.buildout/-/jobs/221383
What happened with `conda-build`?
Thanks
```
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
TOTAL 862 649 25%
Coverage HTML written to dir /scratch/builds/bob/bob.buildout/conda/../sphinx/coverage
Coverage XML written to file /scratch/builds/bob/bob.buildout/conda/../coverage.xml
============================== 8 passed in 0.90s ===============================
+ conda inspect linkages -p /scratch/builds/bob/bob.buildout/miniconda/conda-bld/bob.buildout_1610543493742/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pla bob.buildout
Traceback (most recent call last):
File "/scratch/builds/bob/bob.buildout/miniconda/bin/conda-inspect", line 7, in <module>
from conda_build.cli.main_inspect import main
ModuleNotFoundError: No module named 'conda_build'
Tests failed for bob.buildout-2.2.6b0-py37ha12b548_43.conda - moving package to /scratch/builds/bob/bob.buildout/miniconda/conda-bld/broken
TESTS FAILED: bob.buildout-2.2.6b0-py37ha12b548_43.conda
Uploading artifacts for failed job
00:01
Uploading artifacts...
coverage.xml: found 1 matching files and directories
Uploading artifacts as "cobertura" to coordinator... ok id=221383 responseStatus=201 Created token=cHw11iVi
Cleaning up file based variables
00:02
ERROR: Job failed: exit code 1
```https://gitlab.idiap.ch/bob/bob.devtools/-/issues/67Moving from macOS 10.13 to a newer version2021-01-05T14:37:42ZAndré AnjosMoving from macOS 10.13 to a newer versionWhile trying to upgrade some packages on the mac ci (black tower), I got this message today:
```
Warning: You are using macOS 10.13.
We (and Apple) do not provide support for this old version.
You will encounter build failures with some...While trying to upgrade some packages on the mac ci (black tower), I got this message today:
```
Warning: You are using macOS 10.13.
We (and Apple) do not provide support for this old version.
You will encounter build failures with some formulae.
Please create pull requests instead of asking for help on Homebrew's GitHub,
Twitter or any other official channels. You are responsible for resolving
any issues you experience while you are running this
old version.
```
We need to consider an OS upgrade for both machines. This should be OK as we will still be able to compile for an older version of macOS as we currently do.
I propose we bump the OS *directly* to version 10.15 (Catalina).André AnjosAndré Anjoshttps://gitlab.idiap.ch/bob/bob.devtools/-/issues/66Location of miniconda install script2021-01-08T14:37:57ZVincent POLLETLocation of miniconda install scriptI am getting a 302 error when running [bootstrap.py](https://gitlab.idiap.ch/bob/bob.devtools/-/blob/master/bob/devtools/bootstrap.py), in the [request](https://gitlab.idiap.ch/bob/bob.devtools/-/blob/master/bob/devtools/bootstrap.py#L24...I am getting a 302 error when running [bootstrap.py](https://gitlab.idiap.ch/bob/bob.devtools/-/blob/master/bob/devtools/bootstrap.py), in the [request](https://gitlab.idiap.ch/bob/bob.devtools/-/blob/master/bob/devtools/bootstrap.py#L241) for the miniconda install script.
The url of the request is `http://www.idiap.ch/miniconda/Miniconda3-py37_4.8.2-Linux-x86_64.sh` and the url of the re-direction is the same, but https instead of http. However, I get a 404 at the https url. Is the ressource missing or am I doing something wrong ?
For context, I am trying to find out why the [build of the opencv package in bob/conda](https://gitlab.idiap.ch/bob/conda/-/jobs/220377) is failing in the CI, but working fine locally. So I am trying to run the build steps of [base-build.yaml](https://gitlab.idiap.ch/bob/bob.devtools/-/blob/master/bob/devtools/data/gitlab-ci/base-build.yaml) in a docker with the c3i-linux-64 image.https://gitlab.idiap.ch/bob/bob.bio.face/-/issues/39[LGBPHS] wrong tempfiles path when running on the grid2020-12-22T17:20:39ZLaurent COLBOIS[LGBPHS] wrong tempfiles path when running on the gridHi,
I have an issue when running the LGBPHS baseline, e.g.
```bob bio vanilla-biometrics pipeline mobio-male lgbphs -vv -l sge```
where it fails with the following traceback :
<details><summary> Click to see traceback </summary>
```
...Hi,
I have an issue when running the LGBPHS baseline, e.g.
```bob bio vanilla-biometrics pipeline mobio-male lgbphs -vv -l sge```
where it fails with the following traceback :
<details><summary> Click to see traceback </summary>
```
Traceback (most recent call last):
File "./bin/bob", line 47, in <module>
sys.exit(bob.extension.scripts.main_cli())
File "/idiap/temp/lcolbois/miniconda3/envs/bob_tf2/lib/python3.7/site-packages/click/core.py", line 829, in __call__
return self.main(*args, **kwargs)
File "/idiap/temp/lcolbois/miniconda3/envs/bob_tf2/lib/python3.7/site-packages/click/core.py", line 782, in main
rv = self.invoke(ctx)
File "/idiap/temp/lcolbois/miniconda3/envs/bob_tf2/lib/python3.7/site-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/idiap/temp/lcolbois/miniconda3/envs/bob_tf2/lib/python3.7/site-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/idiap/temp/lcolbois/miniconda3/envs/bob_tf2/lib/python3.7/site-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/idiap/temp/lcolbois/miniconda3/envs/bob_tf2/lib/python3.7/site-packages/click/core.py", line 1066, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/idiap/temp/lcolbois/miniconda3/envs/bob_tf2/lib/python3.7/site-packages/click/core.py", line 610, in invoke
return callback(*args, **kwargs)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/src/bob.bio.base/bob/bio/base/script/vanilla_biometrics.py", line 215, in vanilla_biometrics
**kwargs,
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/src/bob.bio.base/bob/bio/base/pipelines/vanilla_biometrics/vanilla_biometrics.py", line 143, in execute_vanilla_biometrics
_ = compute_scores(post_processed_scores, dask_client)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/src/bob.bio.base/bob/bio/base/pipelines/vanilla_biometrics/vanilla_biometrics.py", line 23, in compute_scores
result = result.compute(scheduler=dask_client)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/eggs/dask-2.30.0-py3.7.egg/dask/base.py", line 167, in compute
(result,) = compute(self, traverse=False, **kwargs)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/eggs/dask-2.30.0-py3.7.egg/dask/base.py", line 452, in compute
results = schedule(dsk, keys, **kwargs)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/eggs/distributed-2.30.1-py3.7.egg/distributed/client.py", line 2725, in get
results = self.gather(packed, asynchronous=asynchronous, direct=direct)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/eggs/distributed-2.30.1-py3.7.egg/distributed/client.py", line 1992, in gather
asynchronous=asynchronous,
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/eggs/distributed-2.30.1-py3.7.egg/distributed/client.py", line 833, in sync
self.loop, func, *args, callback_timeout=callback_timeout, **kwargs
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/eggs/distributed-2.30.1-py3.7.egg/distributed/utils.py", line 340, in sync
raise exc.with_traceback(tb)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/eggs/distributed-2.30.1-py3.7.egg/distributed/utils.py", line 324, in f
result[0] = yield future
File "/idiap/temp/lcolbois/miniconda3/envs/bob_tf2/lib/python3.7/site-packages/tornado/gen.py", line 735, in run
value = future.result()
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/eggs/distributed-2.30.1-py3.7.egg/distributed/client.py", line 1851, in _gather
raise exception.with_traceback(traceback)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/src/bob.bio.base/bob/bio/base/pipelines/vanilla_biometrics/pipelines.py", line 175, in write_scores
return self.score_writer.write(scores)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/src/bob.bio.base/bob/bio/base/pipelines/vanilla_biometrics/score_writers.py", line 56, in write
return _write(probe_sampleset)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/src/bob.bio.base/bob/bio/base/pipelines/vanilla_biometrics/score_writers.py", line 35, in _write
if isinstance(probe[0], DelayedSample):
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/src/bob.pipelines/bob/pipelines/sample.py", line 165, in __getitem__
return self.samples.__getitem__(item)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/src/bob.pipelines/bob/pipelines/sample.py", line 187, in samples
return self._load()
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/src/bob.bio.base/bob/bio/base/pipelines/vanilla_biometrics/legacy.py", line 364, in _load
return joblib.load("/tmp/" + path)
File "/remote/idiap.svm/temp.biometric03/lcolbois/bob.bio.face/eggs/joblib-0.17.0-py3.7.egg/joblib/numpy_pickle.py", line 577, in load
with open(filename, 'rb') as f:
FileNotFoundError: [Errno 2] No such file or directory: '/tmp//tmp/tmp1dt8ulg0/scores/uman/m103/02_mobile/m103_02_f12_i0_0uman/m103/01_mobile/m103_01_p01_i0_0_uman/m104/01_mobile/m104_01_p01_i0_0_uman/m106/01_mobile/m106_01_p01_i0_0.joblib'
```
</details>
Looks like there is an error when computing the path of some temporary files. Note that the issue:
+ Is specific to LGBPHS (Gabor graph for example works flawlessly)
+ Does not happen when running in local
+ Does not happen when using checkpointing (`-c`)
I am unsure how to start tracking down the root cause.
ping @tiago.pereira @ydayerhttps://gitlab.idiap.ch/bob/bob.bio.base/-/issues/151verify.py --create-configuration-file crashes for local file2021-05-19T17:10:10ZManuel Günthersiebenkopf@googlemail.comverify.py --create-configuration-file crashes for local fileWhen running
```
verify.py --create-configuration-file config.py
```
this crashes with the error:
```
File "miniconda/envs/bob/bin/verify.py", line 11, in <module>
sys.exit(main())
File "miniconda/envs/bob/lib/python3.7/site-p...When running
```
verify.py --create-configuration-file config.py
```
this crashes with the error:
```
File "miniconda/envs/bob/bin/verify.py", line 11, in <module>
sys.exit(main())
File "miniconda/envs/bob/lib/python3.7/site-packages/bob/bio/base/script/verify.py", line 432, in main
args = parse_arguments(command_line_parameters)
File "miniconda/envs/bob/lib/python3.7/site-packages/bob/bio/base/script/verify.py", line 34, in parse_arguments
skips = ['preprocessing', 'extractor-training', 'extraction', 'projector-training', 'projection', 'enroller-training', 'enrollment', 'score-computation', 'concatenation', 'calibration'])
File "miniconda/envs/bob/lib/python3.7/site-packages/bob/bio/base/tools/command_line.py", line 425, in initialize
args = parse_config_file(parsers, args, args_dictionary, keywords, skips)
File "miniconda/envs/bob/lib/python3.7/site-packages/bob/bio/base/tools/command_line.py", line 284, in parse_config_file
create_configuration_file(parsers, args)
File "miniconda/envs/bob/lib/python3.7/site-packages/bob/bio/base/tools/command_line.py", line 578, in create_configuration_file
bob.io.base.create_directories_safe(os.path.dirname(args.create_configuration_file))
File "miniconda/envs/bob/lib/python3.7/site-packages/numpy/lib/utils.py", line 100, in newfunc
return func(*args, **kwds)
File "miniconda/envs/bob/lib/python3.7/site-packages/bob/io/base/__init__.py", line 104, in create_directories_safe
os.makedirs(directory, exist_ok=True)
File "miniconda/envs/bob/lib/python3.7/os.py", line 223, in makedirs
mkdir(name, mode)
FileNotFoundError: [Errno 2] No such file or directory: ''
```
The issue is that `bob.io.base.create_directories_safe(os.path.dirname(args.create_configuration_file))` is called without checking whether `os.path.dirname(args.create_configuration_file)` isn't empty.
There are two solutions to this issue:
1. We add this check here.
2. We correct this in `bob.io.base.create_directories_safe` and just skip empty strings.
Which option would you prefer?https://gitlab.idiap.ch/bob/bob.devtools/-/issues/64Use pytorch model-zoo style file uploads for `bdt dav upload`2021-03-23T14:45:30ZAndré AnjosUse pytorch model-zoo style file uploads for `bdt dav upload`As discussed during the Bob meeting yesterday afternoon, it would be nice to have an option in the `upload` command for `bdt dav` that would handle filename hashing automatically, à là pytorch's model zoo implementation (https://pytorch....As discussed during the Bob meeting yesterday afternoon, it would be nice to have an option in the `upload` command for `bdt dav` that would handle filename hashing automatically, à là pytorch's model zoo implementation (https://pytorch.org/docs/stable/model_zoo.html). This procedure would have to take a file and ensure it is uploaded to the destination URL with a slightly modified name:
```
if name is file.ext and url is http://example.com/dir/
file is uploaded as http://example.com/dir/file-deadbeef.ext
where `deadbeaf` is the first 8 characters of the original file's sha256 sum.
```
Similarly, an option in bob/bob.extension's `get_data` should be able to handle automatic hash checking, if the user specifies the said option, or automatically, based on the filename (e.g. via regular expression matching).
This mechanism provides a way to handle file versions and automatic checking for the completeness of existing cached downloads.Amir MOHAMMADIAmir MOHAMMADIhttps://gitlab.idiap.ch/bob/bob/-/issues/265Several tests failing on bob/bob2020-12-18T12:35:36ZTiago de Freitas PereiraSeveral tests failing on bob/bobSome nosetests are failing one bob/bob
https://gitlab.idiap.ch/bob/nightlies/-/jobs/220347Some nosetests are failing one bob/bob
https://gitlab.idiap.ch/bob/nightlies/-/jobs/220347Bob 9.0.0https://gitlab.idiap.ch/bob/bob/-/issues/264[black]2022-05-10T09:48:44ZTiago de Freitas Pereira[black]I would like to `[black]` all packages inside of `bob.nightlies`, so we have standard formating.
Any objection?
ping @amohammadi @ydayer @andre.anjosI would like to `[black]` all packages inside of `bob.nightlies`, so we have standard formating.
Any objection?
ping @amohammadi @ydayer @andre.anjosBob 9.0.0https://gitlab.idiap.ch/bob/bob.pipelines/-/issues/30CSVBaseSampleLoader does not support delayed metadata2020-12-13T11:51:16ZAmir MOHAMMADICSVBaseSampleLoader does not support delayed metadataSince DelayedSample supports delayed metadata as well, I think it's a good idea that CSVBaseSampleLoader delays the metadata loading as well.
This is really important as when we query the database, we may want to load the annotations in ...Since DelayedSample supports delayed metadata as well, I think it's a good idea that CSVBaseSampleLoader delays the metadata loading as well.
This is really important as when we query the database, we may want to load the annotations in a delayed manner because they might not exist and annotaitons might not be used. see https://gitlab.idiap.ch/bob/bob.pipelines/-/blob/e2459dc5784045261ccc25df204a852bb527239e/bob/pipelines/datasets/sample_loaders.py#L60Bob 9.0.0Tiago de Freitas PereiraTiago de Freitas Pereirahttps://gitlab.idiap.ch/bob/bob.pad.base/-/issues/37Follow-up from "[dask] Make vanilla-pad work properlly with dask"2022-06-02T15:48:19ZAmir MOHAMMADIFollow-up from "[dask] Make vanilla-pad work properlly with dask"The following discussion from !81 should be addressed:
- [ ] @amohammadi started a [discussion](https://gitlab.idiap.ch/bob/bob.pad.base/-/merge_requests/81#note_59236):
> This should be `ToDaskBag` no? Anyhow I prefer if this was...The following discussion from !81 should be addressed:
- [ ] @amohammadi started a [discussion](https://gitlab.idiap.ch/bob/bob.pad.base/-/merge_requests/81#note_59236):
> This should be `ToDaskBag` no? Anyhow I prefer if this was actually a click option.Bob 9.0.0Tiago de Freitas PereiraTiago de Freitas Pereirahttps://gitlab.idiap.ch/bob/bob.pad.base/-/issues/36One-Shot vulnerability analysis2021-06-16T09:05:39ZTiago de Freitas PereiraOne-Shot vulnerability analysisHi,
Today the workflow to do vulnerability analysis is:
1. To have a database with two protocols, one licit (zero-effort impostors vs bonafides) and one called spoof (presentation attacks vs bonafides).
2. run `bob bio pipelines vanill...Hi,
Today the workflow to do vulnerability analysis is:
1. To have a database with two protocols, one licit (zero-effort impostors vs bonafides) and one called spoof (presentation attacks vs bonafides).
2. run `bob bio pipelines vanilla-biometrics licit....`
3. run `bob bio pipelines vanilla-biometrics spoof....`
4. run `bob pad vulnerability .... {licit,spoof}/scores-{dev,eval}`
I understand the reasons why this was made like this, but now with `bob bio pipelines vanilla-biometrics --write-metadata ....` we can have score files where metadata is available:
```
probe_key,probe_path,probe_reference_id,bio_ref_path,bio_ref_reference_id,is_bonafide,score
devel/real/client003_session01_webcam_authenticate_adverse_1,devel/real/client003_session01_webcam_authenticate_adverse_1,3,3,3,1,0.9919710755348206
```
Therefore, we can afford to have one protocol containing both `zero-effort impostors` and `presentation attack` probes, and the job of the tools inside of `bob pad vulnerability` would take care of selecting these two types of probes and do the correct analysis.
I think this is wiser.
What do you think @amohammadi @ydayer?
ThanksBob 9.0.0Yannick DAYERYannick DAYERhttps://gitlab.idiap.ch/bob/bob.pad.base/-/issues/35Follow-up from "Dask pipelines Improvements"2020-12-09T10:24:37ZTiago de Freitas PereiraFollow-up from "Dask pipelines Improvements"The following discussion from !78 should be addressed:
- [ ] @tiago.pereira started a [discussion](https://gitlab.idiap.ch/bob/bob.pad.base/-/merge_requests/78#note_59143):
> Hi,
>
> Would be nice to have this functionali...The following discussion from !78 should be addressed:
- [ ] @tiago.pereira started a [discussion](https://gitlab.idiap.ch/bob/bob.pad.base/-/merge_requests/78#note_59143):
> Hi,
>
> Would be nice to have this functionality on `bob.pipelines`
Would be nice to have a functionality that saves the pipeline steps in a `.txt` file for the record.https://gitlab.idiap.ch/bob/bob.bio.face/-/issues/38Follow-up from "Sample Loaders able to handle certain type of annotations..."2020-12-15T17:44:30ZTiago de Freitas PereiraFollow-up from "Sample Loaders able to handle certain type of annotations..."The following discussion from !81 should be addressed:
- [ ] @amohammadi started a [discussion](https://gitlab.idiap.ch/bob/bob.bio.face/-/merge_requests/81#note_59087):
> you can remove this now.
I need to do some minor clean-up...The following discussion from !81 should be addressed:
- [ ] @amohammadi started a [discussion](https://gitlab.idiap.ch/bob/bob.bio.face/-/merge_requests/81#note_59087):
> you can remove this now.
I need to do some minor clean-up on MEDS dataset.Tiago de Freitas PereiraTiago de Freitas Pereirahttps://gitlab.idiap.ch/bob/bob.db.oulunpu/-/issues/4Nightlies stuck on this one2021-04-12T10:05:55ZTiago de Freitas PereiraNightlies stuck on this oneHi guys,
We need to make this package compatible with the new `bob.bio.video` to get this green.Hi guys,
We need to make this package compatible with the new `bob.bio.video` to get this green.Bob 9.0.0Amir MOHAMMADIAmir MOHAMMADI