beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2016-02-16T13:05:27Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/346[many] request documentation button ?2016-02-16T13:05:27ZSébastien MARCEL[many] request documentation button ?In any documentation tab
Example:
http://beatweb-staging/experiments/aythamimm/aythamimm/atvs_keystroke_btas_benchmark/1/ATVS_keystroke_beckmark_btas2015/
what about having a button "Request documentation" to all objects on the pl...In any documentation tab
Example:
http://beatweb-staging/experiments/aythamimm/aythamimm/atvs_keystroke_btas_benchmark/1/ATVS_keystroke_beckmark_btas2015/
what about having a button "Request documentation" to all objects on the platform (expe/toolchains/algo/attestation) for a user to ask another one to document its stuff ?
In practice the other user will receive an email.
We can imagine to link this later to some rewarding mechanism with the gamification.
Open-source Releasehttps://gitlab.idiap.ch/beat/beat.web/-/issues/345[ui] More meaningful names for tabs on main page2015-12-01T14:21:54ZSébastien MARCEL[ui] More meaningful names for tabs on main pagehttp://beatweb-staging/events/smarcel/
Events -> Activity ?
this could be a place to put also later on a Leaderboard
System Objects -> Resources (Data and Computing)
For the others what about sticky to the Open Science terminol...http://beatweb-staging/events/smarcel/
Events -> Activity ?
this could be a place to put also later on a Leaderboard
System Objects -> Resources (Data and Computing)
For the others what about sticky to the Open Science terminology ( https://en.wikipedia.org/wiki/Open_science ) ?
Objects -> Open Source -- it might not be 100% correct if we accommodate binaries are some point !
Queries -> Open Access
Note that the Teams can me moved from Objects to Queries as it is a sharing feature.
My 2 cents
Final Documentationhttps://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/342[experiments] Blocks on result display are out of order2015-11-20T12:02:29ZAndré Anjos[experiments] Blocks on result display are out of order![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/59cf206f5c8587a9de80686b420c2114/image.png)
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/59cf206f5c8587a9de80686b420c2114/image.png)
André AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/341[ui] Replace on the frontpage the example toolchain by the public activity feed2016-03-16T12:01:27ZSébastien MARCEL[ui] Replace on the frontpage the example toolchain by the public activity feedhttp://beatweb-staginghttp://beatweb-stagingOpen-source Releasehttps://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/333Weir error message submitting a job2015-11-19T10:41:09ZSébastien MARCELWeir error message submitting a jobprepared an expe:
https://www.beat-eu.org/platform/experiments/setup/smarcel/tpereira/full_isv_multi/2/Perio_CPqD_T-MM_D-MM_T-MM_ISV-G512-U160/
pressed "GO" to submit then got the HTML error message in a pop-up:
--
<html>
<head><...prepared an expe:
https://www.beat-eu.org/platform/experiments/setup/smarcel/tpereira/full_isv_multi/2/Perio_CPqD_T-MM_D-MM_T-MM_ISV-G512-U160/
pressed "GO" to submit then got the HTML error message in a pop-up:
--
<html>
<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx/1.2.1</center>
</body>
</html>
--
then still on the expe page
https://www.beat-eu.org/platform/experiments/setup/smarcel/tpereira/full_isv_multi/2/Perio_CPqD_T-MM_D-MM_T-MM_ISV-G512-U160/
where I can press "GO" again
however the jobs seems running:
https://www.beat-eu.org/platform/experiments/smarcel/tpereira/full_isv_multi/2/Perio_BANCA_T-P_D-P_T-P_ISV-G512-U160/
so I didn't pressed "GO" again to avoid messing up
https://gitlab.idiap.ch/beat/beat.web/-/issues/332Search function not working in the "Searches" and "Attestations" tabs2015-11-19T10:40:04ZSushil BHATTACHARJEESearch function not working in the "Searches" and "Attestations" tabsHi,
the text-box for entering search terms under the tabs "Searches" and "Attestations"
does not seem to be active.
Also, there is no "Add" button in the Searches tab (to create new searches).
Hi,
the text-box for entering search terms under the tabs "Searches" and "Attestations"
does not seem to be active.
Also, there is no "Add" button in the Searches tab (to create new searches).
https://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/327Error message accessing a shared failed experiment2015-11-18T10:01:46ZSébastien MARCELError message accessing a shared failed experimentI tried to access this toolchain from Sushil:
https://www.beat-eu.org/platform/experiments/anjos/sbhatta/iqm-face-antispoofing-test/1/sushils-experiment-on-replay-db/
that I can see as failed in my list of experiments — likely becaus...I tried to access this toolchain from Sushil:
https://www.beat-eu.org/platform/experiments/anjos/sbhatta/iqm-face-antispoofing-test/1/sushils-experiment-on-replay-db/
that I can see as failed in my list of experiments — likely because it is share with me — but when I access it I have a pop-up error message « Toolchain not found »