beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2018-07-30T08:57:48Zhttps://gitlab.idiap.ch/beat/beat.core/-/issues/4Binary data format (migrated from github)2018-07-30T08:57:48ZAndré AnjosBinary data format (migrated from github)The current data format of choice uses the Python pickling system. This is highly subjective to the project module structure. I'm not sure it is a good idea to keep it hanging around for long.
Our group had a (very good) experience wi...The current data format of choice uses the Python pickling system. This is highly subjective to the project module structure. I'm not sure it is a good idea to keep it hanging around for long.
Our group had a (very good) experience with HDF5. This is a binary format that is quite flexible, fast to read, compact and universally compatible with all major software suites. I believe we should port the data format
system to use data instead of Python pickle.
To get started, I'd go for incorporating a dependence on the excellent python package `h5py`. It does already bring support for all Python/NumPy basic types and is extensible to different data types.
At this point, it would be also nice to introduce data versioning somewhere. Maybe on the "dataformat" descriptors (not sure).
> Note: Philip/François are not sure on HDF5. Before discarding it the possibility to use it, it would be interesting to
> understand why.
> Note: Another useful tool would be an automatic converter, that takes HDF5 files and transforms that into JSON
> descriptors of that format. One can convert HDF5 files to simple data descriptors and, from there, into BEAT's
> JSON format if necessary.
> Note: While debugging, it should be possible to inspect the cache. We currently have no tools to do so,
> but if we address this item with HDF5, then this should come for free.
Second BEAT ReviewLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.core/-/issues/3Repeated connection is not detected on toolchain JSON (migrated from github)2015-03-06T08:04:27ZAndré AnjosRepeated connection is not detected on toolchain JSON (migrated from github)By mistake, I created a repeated connection from one block to another, on my list of connections. The platform has signaled the toolchain to be valid, but when running, the following error occurred:
```python
File "/remote/filer.gx...By mistake, I created a repeated connection from one block to another, on my list of connections. The platform has signaled the toolchain to be valid, but when running, the following error occurred:
```python
File "/remote/filer.gx/user.active/aanjos/work/projects/beat/beat/eggs/ipdb-0.7-py2.7.egg/ipdb/__main__.py", line 138, in main
pdb._runscript(mainpyfile)
File "/usr/lib/python2.7/pdb.py", line 1233, in _runscript
self.run(statement)
File "/usr/lib/python2.7/bdb.py", line 400, in run
exec cmd in globals, locals
File "<string>", line 1, in <module>
File "./bin/run_toolchain.py", line 3, in <module>
import sys
File "/remote/filer.gx/user.active/aanjos/work/projects/beat/beat/src/beat.core/beat/core/scripts/run_toolchain.py", line 186, in main
if isinstance(connection.output.block, Database):
AttributeError: 'NoneType' object has no attribute 'output'
Uncaught exception. Entering post mortem debugging
```
I guess that should be relatively easy to fix.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/2Warning for unconnected/multiply connected blocks (migrated from github)2015-03-06T08:05:11ZAndré AnjosWarning for unconnected/multiply connected blocks (migrated from github)Along the same lines as #39, it would be convenient that both `check_toolchain.py` and `run_toolchain.py` would check for unconnected blocks and issue a **warning** in case one is detected. It would be an immense helper for debugging new...Along the same lines as #39, it would be convenient that both `check_toolchain.py` and `run_toolchain.py` would check for unconnected blocks and issue a **warning** in case one is detected. It would be an immense helper for debugging new toolchains.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/1createDataFromJSON() is failing with dataformats which are arrays of dictiona...2014-08-28T11:34:02ZLaurent EL SHAFEYcreateDataFromJSON() is failing with dataformats which are arrays of dictionaries of dictionariesIt seems that the method createDataFromJSON() from the DataFormatSerializer does not work well when we have a dataformat, which is a list of dictionaries of dictionaries.
E.g.:
```
{
"objs": [2,
{
"id": "int...It seems that the method createDataFromJSON() from the DataFormatSerializer does not work well when we have a dataformat, which is a list of dictionaries of dictionaries.
E.g.:
```
{
"objs": [2,
{
"id": "int32",
"coordinates": {"x": "int32",
"y": "int32"
}
}
]
}
```
In this case, the method returns None and the associated error string is:
Data instance has no attribute 'coordinates'
I've pushed a 'failing' unit test in the repository (b8d4d1bc3 and e489e67f5)https://gitlab.idiap.ch/beat/beat.examples/-/issues/3Databases have no version number2017-10-04T21:58:17ZLaurent EL SHAFEYDatabases have no version numberThe current databases (JSON declaration) have no version number. This should be integrated.The current databases (JSON declaration) have no version number. This should be integrated.Biometrics Center Kickoff Meeting and BEAT Reviewhttps://gitlab.idiap.ch/beat/beat.examples/-/issues/2Automation of database deployment2017-10-04T21:58:17ZLaurent EL SHAFEYAutomation of database deploymentThere is currently no easy way to deploy a new BEAT database into a running platform.
Several issues require addressing:
1. The JSON file describing the database view and the root URL needs to be copied and edited manually.
2. The...There is currently no easy way to deploy a new BEAT database into a running platform.
Several issues require addressing:
1. The JSON file describing the database view and the root URL needs to be copied and edited manually.
2. There is currently no script give a new database JSON file to automatically instantiate the database into the Django database.RP Conference, Darmstadt, DEhttps://gitlab.idiap.ch/beat/beat.examples/-/issues/1Remove dependence of beat.env.* to this package2017-10-04T21:58:17ZLaurent EL SHAFEYRemove dependence of beat.env.* to this packageThe existing environments currently depend on this package. This implies that adding a new database requires redeploying all existing environments. To remove the dependence of this package from beat.env.* requires a process separation fr...The existing environments currently depend on this package. This implies that adding a new database requires redeploying all existing environments. To remove the dependence of this package from beat.env.* requires a process separation from the data sources linked to databases to the data sinks used by the experiments.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/262Refresh editor data2020-06-03T12:08:33ZSamuel GAISTRefresh editor dataSummary
When creating a new asset, generally an algorithm or a data format, the other editors like the experiment editor do not currently expose them.
Steps to reproduce
Create a new data format, once done, edit an algorithm then sea...Summary
When creating a new asset, generally an algorithm or a data format, the other editors like the experiment editor do not currently expose them.
Steps to reproduce
Create a new data format, once done, edit an algorithm then search for the newly created data format. It currently is not listed.
What is the current bug behavior?
The new asset is not listed.
What is the expected correct behavior?
Newly created asset should be visible without a restart of the application.
Possible fixes
- Reload all the parts that exposes these information when switching to an editor
- Reload all the parts that exposes these information when there's a modificationSamuel GAISTSamuel GAIST