beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2015-11-20T11:48:42Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/344[attestations] Show all existing attestations on user page2015-11-20T11:48:42ZAndré Anjos[attestations] Show all existing attestations on user pagePresently, only user attestations are displayed. This is not true any longer for all other contribution types.Presently, only user attestations are displayed. This is not true any longer for all other contribution types.Final DocumentationAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/343[experiments] Cancel page refresh if not on "Result Display" mode2015-12-10T14:50:41ZAndré Anjos[experiments] Cancel page refresh if not on "Result Display" modeOtherwise user changes may be forgotten.Otherwise user changes may be forgotten.Final DocumentationAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/340[search] Leader board notification2015-12-04T11:05:23ZAndré Anjos[search] Leader board notificationThis is an idea to implement leader boards in the platform re-using the search app.
1. Implement a new attribute to the `Search` model called `experiments`, pointing to the current set of experiments which are the result of a search. ...This is an idea to implement leader boards in the platform re-using the search app.
1. Implement a new attribute to the `Search` model called `experiments`, pointing to the current set of experiments which are the result of a search. N.B.: This field is not used to display the search results, which still relies on the code available at the app. It is only used for the Leader Board feature. This feature is switchable with a simple checkbox and, `Search.experiments` is not visible otherwise to the user.
2. For every `Search` with `experiments` set, perform the following via a cronjob (once every 4 hours?):
1. Re-run the search
2. Check if the new set of experiments is the same as before
3. If it changed, report this via e-mail (and on the actstream?) of the owner, indicating the old and new lists (relative differences may be displayed). The e-mail contains a link to the original search
4. If (3) was fullfilled, for each user that has an experiment on the search AND access to the search, report the relative displacement of the user experiment's position.Final Documentationhttps://gitlab.idiap.ch/beat/beat.web/-/issues/339[experiments] Re-running reset experiments generates invalid results2015-12-01T14:22:44ZAndré Anjos[experiments] Re-running reset experiments generates invalid resultsResult screen after re-running an experiment that was reset:
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/891489c5dc0a7469fc52924195060fe3/image.png)
Result screen after re-running an experiment that was reset:
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/891489c5dc0a7469fc52924195060fe3/image.png)
Final DocumentationAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/338[multiple] History viewer rows are out of place after new design merger2015-12-15T14:43:01ZAndré Anjos[multiple] History viewer rows are out of place after new design mergerAfter our new design merger, we now have a history viewer in which rows are out of order.
@philip.abbet: could you please have a look at this and try to understand the reason of this misplacement? (Likely a change from my side, but I'...After our new design merger, we now have a history viewer in which rows are out of order.
@philip.abbet: could you please have a look at this and try to understand the reason of this misplacement? (Likely a change from my side, but I'm not sure where that would be.)Final DocumentationPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/337[reports] button settings and delete visible in edition mode via number access2015-11-20T08:37:27ZFlavio TARSETTI[reports] button settings and delete visible in edition mode via number accessThis should be removedThis should be removedFinal DocumentationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/336[activities] Cannot restore activities2016-01-04T16:55:55ZAndré Anjos[activities] Cannot restore activitiesAs of today, the restore of actions from the app actstream is broken. The reason is our backup/restore functionality depends on apps fixture dumping using natural keys instead of database identifiers. We cannot guarantee that the restore...As of today, the restore of actions from the app actstream is broken. The reason is our backup/restore functionality depends on apps fixture dumping using natural keys instead of database identifiers. We cannot guarantee that the restored objects will have exactly the same PKs all the time.
The app `actstream` does not use natural keys for fields such as `actor_object_id`, and `target_object_id` so, when restoring, it relies on the exact usage of a given PK and it gets lost. This may cause degradation on the admin page:
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/f3932cdfa57bdd5970e174fda11adfa5/image.png)
Or more severe errors on the front page:
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/1e6ac66e02c523c1044af39e15d36969/image.png)
@samuel.gaist: Suggestions on how to proceed?Final DocumentationSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/335[reports] Display bug in Report2015-11-19T15:41:27ZSushil BHATTACHARJEE[reports] Display bug in ReportPlease refer to the following report:
https://www.beat-eu.org/platform/reports/990149671/
The table in the report, comparing two experiments, displays the statistics for only
one experiment. The values for the other experiment are n...Please refer to the following report:
https://www.beat-eu.org/platform/reports/990149671/
The table in the report, comparing two experiments, displays the statistics for only
one experiment. The values for the other experiment are not visible.Final DocumentationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/334[commands] Backup and Restore are broken2015-12-15T11:30:57ZAndré Anjos[commands] Backup and Restore are brokenFollowing changes in "AccountSettings" and "ActStream", we can back-up but cannot re-store anymore from these backups. This makes moving data pretty hard, so it is a critical problem.Following changes in "AccountSettings" and "ActStream", we can back-up but cannot re-store anymore from these backups. This makes moving data pretty hard, so it is a critical problem.Final Documentationhttps://gitlab.idiap.ch/beat/beat.web/-/issues/331[toolchain] Editor has problems adjusting location of "synchronization" modal...2015-12-17T15:17:39ZAndré Anjos[toolchain] Editor has problems adjusting location of "synchronization" modal on zoomed toolchainsIf the toolchain editor zooms too much, it has problems calculating where to pop-up the synchronization modal window.
Example:
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/d829732a27cd13301a29637a602b94a6/image.png)
If the toolchain editor zooms too much, it has problems calculating where to pop-up the synchronization modal window.
Example:
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/d829732a27cd13301a29637a602b94a6/image.png)
Final DocumentationPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/330[reports] tables are not dynamic anymore after a settings change2015-11-18T16:12:12ZFlavio TARSETTI[reports] tables are not dynamic anymore after a settings changeThis appeared after migration to new designThis appeared after migration to new designFinal DocumentationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/329[experiments] Sharing not working properly with experiment containing private...2016-01-11T13:24:11ZAndré Anjos[experiments] Sharing not working properly with experiment containing private objectsFor some reason, I'm getting a bogus answer when trying to share an experiment with a single user.
The experiment is private and uses algorithms which are privately shared by some other people. So, I guess I should not be able to comp...For some reason, I'm getting a bogus answer when trying to share an experiment with a single user.
The experiment is private and uses algorithms which are privately shared by some other people. So, I guess I should not be able to complete the action (that bit is correct). The issue is that I'm not informed this, but rather a bogus screen:
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/4c8254b116df20c2b0e5008572c3b75c/image.png)
The underlying reason is that some of the components this experiment depends on are privately shared.
Looking at our swagger interface and trying to hit it with the sharing request, I see what is the issue:
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/3b20019240542bdaec954298a0ac70b0/image.png)
This should be correctly reported back to the user instead of the screen I got above.Final DocumentationPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/328[reports] experiments not shown to owner for public reports2015-11-18T10:22:21ZFlavio TARSETTI[reports] experiments not shown to owner for public reportsThis bug has come with the new_design mergeThis bug has come with the new_design mergeFinal DocumentationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/324[notifications] Automatic email received twice ?2015-11-16T11:47:43ZSébastien MARCEL[notifications] Automatic email received twice ?I received this email twice for "Experiment failed"
```text
The experiment smarcel/tpereira/full_isv_multi/2/btas2015_face-periocular_cpqd-smartphone-male_det-rr failed to execute properly.
You can see detailed output here: /platf...I received this email twice for "Experiment failed"
```text
The experiment smarcel/tpereira/full_isv_multi/2/btas2015_face-periocular_cpqd-smartphone-male_det-rr failed to execute properly.
You can see detailed output here: /platform/experiments/smarcel/tpereira/full_isv_multi/2/btas2015_face-periocular_cpqd-smartphone-male_det-rr/
```
it happened also for an "Experiment done":
```
The experiment smarcel/siebenkopf/FaceRec-WithOut-Training/2/face-GGG-GBU-ugly-rr finished successfully.
You can see detailed results here: /platform/experiments/smarcel/siebenkopf/FaceRec-WithOut-Training/2/face-GGG-GBU-ugly-rr/
```
Final DocumentationSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/323[attestations] Automatic email for attestation expiration2015-11-16T10:43:39ZSébastien MARCEL[attestations] Automatic email for attestation expirationLocked attestations have an expiration date:
https://www.beat-eu.org/platform/attestations/809977024/
it will be nice to received a reminder email to inform the user that expiration date is approaching !
also what happens if the e...Locked attestations have an expiration date:
https://www.beat-eu.org/platform/attestations/809977024/
it will be nice to received a reminder email to inform the user that expiration date is approaching !
also what happens if the expiration date is passed ?
Final DocumentationSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/322Error: end_data_index=inputs['probe_id'].data_index_end2015-11-14T16:43:18ZSébastien MARCELError: end_data_index=inputs['probe_id'].data_index_endI tried to re-run an attested toolchain from Tiago on the new version of Scientific Python 2.7 (0.0.4) — that was attested on 0.0.3
https://www.beat-eu.org/platform/experiments/smarcel/tpereira/full_isv/2/btas2015_face_mobio-female_de...I tried to re-run an attested toolchain from Tiago on the new version of Scientific Python 2.7 (0.0.4) — that was attested on 0.0.3
https://www.beat-eu.org/platform/experiments/smarcel/tpereira/full_isv/2/btas2015_face_mobio-female_det/
and I got an error
Errors
Block:
scoring_dev
Algorithm:
tpereira/isv_scoring/3
Details:
Process 0: File "tpereira/isv_scoring/3.py", line 108, in process
end_data_index=inputs['probe_id'].data_index_end
AttributeError: Input instance has no attribute 'data_index_end
Process 1: File "tpereira/isv_scoring/3.py", line 108, in process
end_data_index=inputs['probe_id'].data_index_end
AttributeError: Input instance has no attribute 'data_index_end
Process 2: File "tpereira/isv_scoring/3.py", line 108, in process
end_data_index=inputs['probe_id'].data_index_end
AttributeError: Input instance has no attribute 'data_index_end
Process 3: File "tpereira/isv_scoring/3.py", line 108, in process
end_data_index=inputs['probe_id'].data_index_end
AttributeError: Input instance has no attribute 'data_index_end
it looks like the same bug I obtained for another toolchain that I forked from Tiago and that was working before:
https://www.beat-eu.org/platform/experiments/smarcel/tpereira/full_isv_multi/2/btas2015_face-periocular_cpqd-smartphone-male_det-rr/
Errors
Block:
isv_offset_probe_test_2
Algorithm:
tpereira/isv_offset/3
Details:
Block was cancelled by an external agent.
Block:
scoring_dev_2
Algorithm:
tpereira/isv_scoring/3
Details:
Process 0: File "tpereira/isv_scoring/3.py", line 108, in process
end_data_index=inputs['probe_id'].data_index_end
AttributeError: Input instance has no attribute ‘data_index_end
Final Documentationhttps://gitlab.idiap.ch/beat/beat.web/-/issues/321[notification] Quirks2015-11-13T15:49:38ZAndré Anjos[notification] QuirksFor some reason, the following is happening (staging):
1) I get "failed" e-mail notifications for cached (successful) experiments. How to reproduce: fork a successful experiment, run it, wait for the e-mail.
2) I don't get an e-mai...For some reason, the following is happening (staging):
1) I get "failed" e-mail notifications for cached (successful) experiments. How to reproduce: fork a successful experiment, run it, wait for the e-mail.
2) I don't get an e-mail for experiments that execute, but fail.Final DocumentationSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/320[reports] Problem with the precision and labels update2015-11-23T06:57:26ZTiago de Freitas Pereira[reports] Problem with the precision and labels updateWhen you have an empty report and starts to work on it, the events that need a refresh, such as, the precision update, the experiment labels and so on do not work. These things only start to work smoothly when you refresh the page.
St...When you have an empty report and starts to work on it, the events that need a refresh, such as, the precision update, the experiment labels and so on do not work. These things only start to work smoothly when you refresh the page.
Steps to reproduce the issue:
- Create a new report;
- Add some experiments on it;
- Open the report;
- Add a table;
- Change the floating point precision (this will not work);
- Refresh the page (F5)
- Change the floating point precision (Now starts to work properly);
Final DocumentationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/318[toolchains] Editor gets really small if object is documented2015-10-29T17:50:31ZAndré Anjos[toolchains] Editor gets really small if object is documentedFor example, try to fork:
http://beatweb-staging/toolchains/anjos/livdet-lda/1/
Result screen:
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/8197663fad88091908b40b09dc31380b/image.png)
For example, try to fork:
http://beatweb-staging/toolchains/anjos/livdet-lda/1/
Result screen:
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/8197663fad88091908b40b09dc31380b/image.png)
Final DocumentationPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/317[reports] adding measure type (%, time) in tables2015-12-03T12:43:37ZSébastien MARCEL[reports] adding measure type (%, time) in tablesAdding on the first row of table the measure type (%, time, ...) for each columns would be beneficial:
E.g in http://beatweb-staging/reports/smarcel/fr-dct-ubm-gmm/ (% and time in seconds ?).
Adding on the first row of table the measure type (%, time, ...) for each columns would be beneficial:
E.g in http://beatweb-staging/reports/smarcel/fr-dct-ubm-gmm/ (% and time in seconds ?).
Final DocumentationFlavio TARSETTIFlavio TARSETTI