beat.examples issueshttps://gitlab.idiap.ch/beat/beat.examples/-/issues2017-10-04T21:58:17Zhttps://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.examples/-/issues/5Installation of FRGC, GBU, LFW and NIST SRE2017-10-04T21:58:17ZAndré AnjosInstallation of FRGC, GBU, LFW and NIST SREA request to install the following databases on the platform.
These have to be "hidden" and usable only by us:
- [x] LFW
- [x] NIST SRE
These can be made public (we have authorizations for that):
- [x] FRGC
- [x] GBUA request to install the following databases on the platform.
These have to be "hidden" and usable only by us:
- [x] LFW
- [x] NIST SRE
These can be made public (we have authorizations for that):
- [x] FRGC
- [x] GBUTutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.examples/-/issues/6Database development is a pain2017-10-04T21:58:16ZAndré AnjosDatabase development is a painCurrently, developing a database for inclusion in the platform is a difficult task.
The user has to practically install a functional beat.web platform on his own machine to do it thoroughly:
1. Create the JSON and RST descriptions ...Currently, developing a database for inclusion in the platform is a difficult task.
The user has to practically install a functional beat.web platform on his own machine to do it thoroughly:
1. Create the JSON and RST descriptions of the database
2. Upload that into the beat.databases package and install the contribution
3. Create a toolchain that can use the database
4. Create a new configuration that uses the database
5. Download all pieces locally so that one can debug the toolchain and make sure all is working fine.
We should try to simplify this a bit.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.examples/-/issues/9Problems with SQLite2017-10-04T21:58:16ZTiago de Freitas PereiraProblems with SQLiteThis issue applies for database views that use xbob.dbs with SQLite.
After several fetches in the database (during the execution of the next method in the view), the SQLAlchemy raises the exception "Cannot operate on a closed database...This issue applies for database views that use xbob.dbs with SQLite.
After several fetches in the database (during the execution of the next method in the view), the SQLAlchemy raises the exception "Cannot operate on a closed database".
For some reason the connection with the database closes in the middle of the execution.
A workaround was done redefining (inside the view) the pool configuration to NullPool(http://docs.sqlalchemy.org/en/latest/core/pooling.html#sqlalchemy.pool.NullPool).
This works, but we have no clue what is going on.
This bug keeps track of this issue.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjos