beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2018-11-03T15:23:12Zhttps://gitlab.idiap.ch/beat/beat.core/-/issues/9Versionning support2018-11-03T15:23:12ZAndré AnjosVersionning supportAutomatic versionning suport should be implemented through out the platform. I'm putting this bug here, but surely this affects most packages in the project. I detail our existing workplan and some key behavioral aspects.
- Each objec...Automatic versionning suport should be implemented through out the platform. I'm putting this bug here, but surely this affects most packages in the project. I detail our existing workplan and some key behavioral aspects.
- Each object in the system (databases, toolchains, dataformats, algorithms, attached documentation strings, environments) should be version-able. Every time the user uploads or changes that object, the version number of that object is bumped.
- Each time a new version is entered, the user should be able to attach a version comment, which is independent from the object documentation itself.
- For the platform, the combination of the object name and the version determines the uniqueness of such object.
- The sharing, usage and tagging status of each unique object (name/version) should be tracked independently. This outdates the usage of "/private" paths which seems to be a bit confusing for some users.
- While visualizing the object, the user by defaults accesses the latest version to which it has access to. This should be made consistent through the platform.
- There is always an option to see/use an earlier version of an object, but that requires the user to specify it explicitly. For example, in the command-line utilities, a "--version=xxx" could be passed. On the web interface, the version of a certain object is chosen automatically as the latest, but a field allows the user to browse for an earlier version.Biometrics Center Kickoff Meeting and BEAT Reviewhttps://gitlab.idiap.ch/beat/beat.web/-/issues/2Login box <TAB> behavior is a bit unintuitive2014-09-22T09:01:35ZAndré AnjosLogin box <TAB> behavior is a bit unintuitiveToday, while trying to login, I realised that if a push TAB just after typing the password and then ENTER, I'd reset my password.
Maybe it would be better we move the "Password reset" link away from the login so people don't push it b...Today, while trying to login, I realised that if a push TAB just after typing the password and then ENTER, I'd reset my password.
Maybe it would be better we move the "Password reset" link away from the login so people don't push it by mistake. By "away" I mean both graphically and keyboard-wise.Biometrics Center Kickoff Meeting and BEAT ReviewAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/8Old scripts lingering at beat git2014-09-22T14:36:37ZAndré AnjosOld scripts lingering at beat gitI just realized that the following scripts are still available on `./bin`:
- generate_single_integers.py
- check_dataformat.py
- synchronize.py
- run_toolchain.py
- generate_integers_database.py
- check_toolchain.py
- display_da...I just realized that the following scripts are still available on `./bin`:
- generate_single_integers.py
- check_dataformat.py
- synchronize.py
- run_toolchain.py
- generate_integers_database.py
- check_toolchain.py
- display_data.py
If they are not useful anymore (i.e. have been integrated into the `beat` general command-line program), could you please remove them not to create any confusion?Biometrics Center Kickoff Meeting and BEAT ReviewAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/6Support for enumerations (migrated from github)2014-09-22T14:36:49ZAndré AnjosSupport for enumerations (migrated from github)I have not seen how to declare an enumeration. Is this possible at all? We do have use cases where we could benefit from this. E.g., client data migth belong to the "train", "devel" or "test" datasets. These could be implemented as enume...I have not seen how to declare an enumeration. Is this possible at all? We do have use cases where we could benefit from this. E.g., client data migth belong to the "train", "devel" or "test" datasets. These could be implemented as enumerations. Currently, in the UBM-GMM, I implement this field as an unchecked string.
Biometrics Center Kickoff Meeting and BEAT ReviewPhilip ABBETPhilip ABBEThttps://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.core/-/issues/22Analyzers with the same content but different versions share the same hash2017-08-06T11:17:04ZLaurent EL SHAFEYAnalyzers with the same content but different versions share the same hashIn our current design, analyzers with the same content but different versions share the same hash.
This is problematic, since the cache files for the analyzers include the 'algorithm_name/version' in their headers. Since they share th...In our current design, analyzers with the same content but different versions share the same hash.
This is problematic, since the cache files for the analyzers include the 'algorithm_name/version' in their headers. Since they share the same hash, loading a cache file for a requested 'algorithm_name/version1' may lead to loading a cache file with 'algorithm_name/version2' hardcoded in the header, which will fail, because of the 'dataformat validation'.
To avoid this problem, one possible solution is to change the way hash are generated for analyzer blocks.Second BEAT Reviewhttps://gitlab.idiap.ch/beat/beat.web/-/issues/81Tabbed scheduler page2014-11-24T12:54:34ZAndré AnjosTabbed scheduler pageCurrently, the scheduler information is just output in a single page. Following other functionality available in the web site, it would be nice to organize this information in a tabbed view.
The default tab to show would be a table, e...Currently, the scheduler information is just output in a single page. Following other functionality available in the web site, it would be nice to organize this information in a tabbed view.
The default tab to show would be a table, emitted by the scheduler with the current experiments running and their stats (top-like). The other tabs would concentrate information about the "workers" and "queues".Second BEAT Reviewhttps://gitlab.idiap.ch/beat/beat.web/-/issues/80validate_queue_environment() does not work well2014-11-21T11:50:14ZLaurent EL SHAFEYvalidate_queue_environment() does not work wellWhile performing some update on the database, we noticed that validate_queue_environment() was not validating a tuple (Queue, Env), which seemed to be correct. We have to investigate why.
https://gitlab.idiap.ch/biometric/beat.web/blo...While performing some update on the database, we noticed that validate_queue_environment() was not validating a tuple (Queue, Env), which seemed to be correct. We have to investigate why.
https://gitlab.idiap.ch/biometric/beat.web/blob/master/beat/web/experiments/models.py#L35Second BEAT Reviewhttps://gitlab.idiap.ch/beat/beat.web/-/issues/79Cancelled experiment page is wrong when no associated jobs was cancelled2014-11-20T14:49:24ZLaurent EL SHAFEYCancelled experiment page is wrong when no associated jobs was cancelledThe cancelled experiment page does not show any useful information, when the cancellation of this experiment does not involve the cancellation of a specific job. In this case, we get the configuration page for this experiment instead of ...The cancelled experiment page does not show any useful information, when the cancellation of this experiment does not involve the cancellation of a specific job. In this case, we get the configuration page for this experiment instead of a page indicated that the experiment has been cancelled.
I do not know the exact cause of the problem. I suspect that the lack of error message such as 'Job x was cancelled by an external user agent' leads to the problem.Second BEAT ReviewLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.web/-/issues/77Backend page time out since partitions are now -noac mounted2014-12-02T12:12:52ZLaurent EL SHAFEYBackend page time out since partitions are now -noac mountedThe backend page now seems to time out when e.g. a clean-up is performed.
This is caused by the use of the -noac NFS flag while mounting the partition on beatsched, which affects the filesystem performance.The backend page now seems to time out when e.g. a clean-up is performed.
This is caused by the use of the -noac NFS flag while mounting the partition on beatsched, which affects the filesystem performance.Second BEAT Reviewhttps://gitlab.idiap.ch/beat/beat.web/-/issues/74Error reading parameter for analysis block2014-11-21T12:02:48ZManuel GüntherError reading parameter for analysis blockI continue receiving "internal BEAT system error"s while trying to access a parameter in an analysis block. The relevant code is something like:
```python
## INPUTS
## scores: tutorial/probe_scores/1
## INPU...I continue receiving "internal BEAT system error"s while trying to access a parameter in an analysis block. The relevant code is something like:
```python
## INPUTS
## scores: tutorial/probe_scores/1
## INPUTS_END
## RESULTS
## ROC: beat/chart/1
## RESULTS_END
## PARAMETERS
## points: uint16 100
## PARAMETERS_END
import bob
class Algorithm:
def __init__(self):
self.positives = []
self.negatives = []
def setup(self, parameters):
self.points = parameters.get('points', 100)
return True
def process(self, inputs, output):
...
roc = bob.measure.roc(self.negatives, self.positives, self.points)
...
return True
```
(see https://www.beat-eu.org/platform/algorithms/siebenkopf/ROC/6, if you can). Second BEAT Reviewhttps://gitlab.idiap.ch/beat/beat.core/-/issues/20Reliability of data I/O2017-08-06T11:17:04ZAndré AnjosReliability of data I/OSimilarly to what we did for the indexes, we should also promote some check-summing capabilities for the data which is produced and consumed in our environments. I leave this open for discussion here.Similarly to what we did for the indexes, we should also promote some check-summing capabilities for the data which is produced and consumed in our environments. I leave this open for discussion here.Second BEAT ReviewLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.web/-/issues/73After sharing algorithm, page doesn't reload2014-11-11T12:37:11ZAndré AnjosAfter sharing algorithm, page doesn't reloadIn an algorithm page (maybe this also happens for other contributions), it would be handy that the sharing information (or the whole page) is reloaded after the user has shared the contribution, to show the change. This currently doesn't...In an algorithm page (maybe this also happens for other contributions), it would be handy that the sharing information (or the whole page) is reloaded after the user has shared the contribution, to show the change. This currently doesn't happen.Second BEAT ReviewPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/66Missing tab for attestations2014-11-19T11:56:48ZLaurent EL SHAFEYMissing tab for attestationsThere is currently no way for a user to list his attestations. It would be nice to have a tab showing them with their state (locked/unlocked, expiration time).There is currently no way for a user to list his attestations. It would be nice to have a tab showing them with their state (locked/unlocked, expiration time).Second BEAT ReviewPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/64Possibility to reset a failed experiment2014-12-02T11:54:03ZAndré AnjosPossibility to reset a failed experimentIt would be nice to be able to "reset" failed experiment, from the experiment result page. There are situations where you make wrong choices of parameters or queues for an experiment and you want to fix this - not fork the experiment. Fo...It would be nice to be able to "reset" failed experiment, from the experiment result page. There are situations where you make wrong choices of parameters or queues for an experiment and you want to fix this - not fork the experiment. For those situations, the user may reset the experiment, which would take him to the configuration page again.
The experiment model class in our Django app already supports the "reset()" functionality, which is successfuly used in the admin page already. This ticket is only about hooking in the possibility to reset from the result page itself.Second BEAT ReviewPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/61Missing "Environments" panel for the user2014-11-21T10:37:38ZAndré AnjosMissing "Environments" panel for the userWe miss a panel at the user dashboard allow the user to list existing software environments, queue configurations and number of slots available.
This web page should allow the user to visualize existing software environments and brows...We miss a panel at the user dashboard allow the user to list existing software environments, queue configurations and number of slots available.
This web page should allow the user to visualize existing software environments and browser user queues to view the number of slots available and queue properties.
Second BEAT ReviewPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/59 Cannot create new version of existing Toolchain2014-11-18T11:51:51ZAndré Anjos Cannot create new version of existing ToolchainI'm not able to create anymore a new version of existing (public) toolchains. This should be possible:
![Screenshot - 311014 - 10:16:56](https://gitlab.idiap.ch/uploads/biometric/beat.web/e1d46fe655/Screenshot_-_311014_-_10_16_56.png)...I'm not able to create anymore a new version of existing (public) toolchains. This should be possible:
![Screenshot - 311014 - 10:16:56](https://gitlab.idiap.ch/uploads/biometric/beat.web/e1d46fe655/Screenshot_-_311014_-_10_16_56.png)
Any ideas?Second BEAT ReviewPhilip ABBETPhilip ABBEThttps://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.web/-/issues/158The sentence "Public for specific users..." is not sensical2015-05-07T08:51:20ZAndré AnjosThe sentence "Public for specific users..." is not sensicalMaybe we could modify it to "Shared with specific users..." instead.Maybe we could modify it to "Shared with specific users..." instead.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/156Saved search is not displayed2015-05-07T10:08:10ZAndré AnjosSaved search is not displayedIf I click (from the user micro-site, Databases panel), on this query for the AT&T database:
https://www.beat-eu.org/platform/search/?query=db:atnt%20type:results
And I save this search, with its default name, and then I go back to...If I click (from the user micro-site, Databases panel), on this query for the AT&T database:
https://www.beat-eu.org/platform/search/?query=db:atnt%20type:results
And I save this search, with its default name, and then I go back to the micro-site, "Searches" panel and click on the saved search, I cannot see it properly.Tutorial for the FG2015 ConferenceFlavio TARSETTIFlavio TARSETTI