beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2019-07-04T08:37:02Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/326[many] Gamification of the platform2019-07-04T08:37:02ZSébastien MARCEL[many] Gamification of the platformThis is for discussion later on.
We have been discussing the gamification of the platform to engage better the users by awarding them privileges. This is related to Activity page:
https://www.beat-eu.org/platform/user/smarcel/?tab=ac...This is for discussion later on.
We have been discussing the gamification of the platform to engage better the users by awarding them privileges. This is related to Activity page:
https://www.beat-eu.org/platform/user/smarcel/?tab=activity
I recommend this very nice MSc thesis "Gamification in a social system":
http://www.cs.rug.nl/~aiellom/tesi/blaauw.pdf
it describes various algorithms relying on graph -- and provides codes in appendix -- to model reputation with algorithms such PageRank and other. Another algorithm called LevelUp presents
principles to award badges and build a leaderboard.
The author is apparently a big fan of online games such as Call of Duty !
Here is also some interesting tips on Gamification in particular the tips 7, 8 and 9:
https://www.td.org/Publications/Blogs/Learning-Technologies-Blog/2014/02/10-Best-Practices-for-Implementing-Gamification
https://gitlab.idiap.ch/beat/beat.web/-/issues/325[experiments] Reproducibility chart2019-07-04T08:37:02ZAndré Anjos[experiments] Reproducibility chartAfter thinking about how reproducible an experiment in the platform really is, I think we can improve the experiment display a bit to include some sort of "reproducibility chart".
The idea behind this is to check, on a per-experiment ...After thinking about how reproducible an experiment in the platform really is, I think we can improve the experiment display a bit to include some sort of "reproducibility chart".
The idea behind this is to check, on a per-experiment basis and annotate, key points that may make the experiment irreproducible. Here are some key aspects
1. The database used by the experiment is deactivated due to the end of the license agreement between Idiap and the controller
2. The environment used by any of the blocks is not active anymore (outdated by another environment)
3. There are incompatible API changes that **may** affect reproducibility (for example, the changes pushed on September 2nd. removing the ``data_index`` and ``data_index_end`` attributes). This condition must be taken with care, as it would require an (human) in-depth analysis of all experiment algorithms for a thorough conclusion. What we can do though, is to setup a new table that lists incompatible API changes and dates. If the experiment finished after that date, then we can consider it is compatible. Otherwise, not. We keep this table updated in case of eventual non-compatible API modifications.https://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/319[reports] Visualization issues with locked reports2015-11-13T14:58:15ZTiago de Freitas Pereira[reports] Visualization issues with locked reportsI made a report and I locked it for an hypothetical publication.
When you try to access it via this link http://beatweb-staging/reports/909421704/ the plot labels are "undefined" no matter how many times you refresh the page. Furtherm...I made a report and I locked it for an hypothetical publication.
When you try to access it via this link http://beatweb-staging/reports/909421704/ the plot labels are "undefined" no matter how many times you refresh the page. Furthermore it is not possible to see the tables created for this report.
https://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 TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/316[reports] error to export a table2015-10-29T09:12:10ZSébastien MARCEL[reports] error to export a tableon beat staging I created a new report
http://beatweb-staging/reports/smarcel/fr-dct-ubm-gmm/
when trying to export the table it generates a link data:blob:http://beatweb-staging/1f829b44-7fa5-4165-b9f8-3f4039f61365 that my web brows...on beat staging I created a new report
http://beatweb-staging/reports/smarcel/fr-dct-ubm-gmm/
when trying to export the table it generates a link data:blob:http://beatweb-staging/1f829b44-7fa5-4165-b9f8-3f4039f61365 that my web browser (Safari) is not able to open.
Error message:
Safari ne parvient pas à ouvrir la page « data:blob:http://beatweb-staging/1f829b44-7fa5-4165-b9f8-3f4039f61365 » en raison de l’erreur « L’opération n’a pas pu s’achever. (kCFErrorDomainCFNetwork erreur -10). » (kCFErrorDomainCFNetwork:-10)
Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/315[reports] Float-point precision does not apply to "special" columns which are...2016-02-16T17:04:28ZAndré Anjos[reports] Float-point precision does not apply to "special" columns which are not analyzer outputsCan this be easily fixed?
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/f757c27dee559662a71491d076f904f2/image.png)
Can this be easily fixed?
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/f757c27dee559662a71491d076f904f2/image.png)
Open-source ReleaseFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/314Text on front-page and meta-data2015-10-28T12:19:43ZSébastien MARCELText on front-page and meta-data# On the BEAT front page the text is currently this one:
The BEAT platform provides easy online access to experimentation and testing in computational science. You define what data and modules you would like to use, we make sure the sys...# On the BEAT front page the text is currently this one:
The BEAT platform provides easy online access to experimentation and testing in computational science. You define what data and modules you would like to use, we make sure the system runs and provides you with a result. Data from different experiments can be easily compared and searched.
---
to boost the referencing of the BEAT platform I think it will be wise to take into account the vocabulary used in the new H2020 e-Infrastructure calls ( http://ec.europa.eu/research/participants/portal//desktop/en/opportunities/h2020/calls/h2020-einfra-2016-2017.html#c,topics=callIdentifier/t/H2020-EINFRA-2016-2017/1/1/1&callStatus/t/Forthcoming/1/1/0&callStatus/t/Open/1/1/0&callStatus/t/Closed/1/1/0&+identifier/desc ).
---
Therefore I suggest 2 things:
# add these keywords in the meta data of the front page
Keywords="open science","e-infrastructure","e-infrastructure platform","computing e-infrastructure","European Open Science Cloud for Research", "Data and Distributed Computing e-infrastructures for Open Science", "Platform-driven e-infrastructure innovation", "Data Preservation", "Data Access", "Open Access", "Privacy", "Confidentiality"
# replace the text on the front page by:
The BEAT platform is a European computing e-infrastructure for Open Science and propose a solution for open access, scientific information sharing and re-use including data and source code while protecting privacy and confidentiality.
It allows easy online access to experimentation and testing in computational science. You define what data and modules you would like to use, we make sure the system runs and provides you with a result. Data from different experiments can be easily compared and searched.
The platform also provides an attestation mechanism for your reports (scientific papers, technical documents or certifications).
André AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/313[search,report] Detection and displaying of results2019-07-04T08:37:02ZAndré Anjos[search,report] Detection and displaying of resultsThis ticket is to follow-up on a realization I had this morning looking at some of our stored searches.
In the "settings" field, I noticed that result fields supposed to be displayed are prepended by their analyzer (algorithm), as rep...This ticket is to follow-up on a realization I had this morning looking at some of our stored searches.
In the "settings" field, I noticed that result fields supposed to be displayed are prepended by their analyzer (algorithm), as reported by `beat.web.algorithms.Algorithm.fullname()`. This will not work if we're comparing experiments (with the same toolchain) with two or more analyzer outputs which happen to use the same algorithm. @philip.abbet: Am I overlooking something? Please fill-in in this case.
To improve on this we need to better define what we allow to be displayed (before we figure-out how to properly display it) and, only then, how it is going to be displayed and saved.
As of today, we have a couple of use-cases covered:
1. The user wants to compare experiments for which there is only one analyzer output using the same algorithm
2. The user wants to compare experiments with the same toolchain, for which there are matching algorithms on each analyzer block over all experiments.
So that these 2 cases are correctly displayed and stored, and because in case 2 the analysis block (on the toolchain) can use the same algorithm, it is not good to store search "settings" prefixing result names with the algorithm fullname, but rather with the block name. Right?
Philip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/312[teams] Team creation test is failing after use of "reverse"2015-10-26T10:01:31ZAndré Anjos[teams] Team creation test is failing after use of "reverse"Apparently, the patch on the team creation has a small problem. The team is created after the call to `reverse()`, which results in an error:
https://gitlab.idiap.ch/ci/projects/3/builds/40Apparently, the patch on the team creation has a small problem. The team is created after the call to `reverse()`, which results in an error:
https://gitlab.idiap.ch/ci/projects/3/builds/40Final DocumentationSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/311[experiments] utils.js: displayPlot is bogus after merge/unmerge patch2015-10-26T11:34:12ZAndré Anjos[experiments] utils.js: displayPlot is bogus after merge/unmerge patchWhen displaying the result of an experiment, the following may validate to undefined:
```javascript
(line 223) data_per_experiment.legend = data.legend.split("&")[i];
```
If we set an `if` clause around this statement, then final...When displaying the result of an experiment, the following may validate to undefined:
```javascript
(line 223) data_per_experiment.legend = data.legend.split("&")[i];
```
If we set an `if` clause around this statement, then finally the experiment result plot gets a 500 error.Final DocumentationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/310[documentation] Fixes2015-09-29T07:52:40ZAndré Anjos[documentation] FixesWe have, presently, objects for which documentation cannot be properly parsed (i.e., rendered in proper HTML via docutils), some as a result of #253. The solution in these cases, is to render a `<pre></pre>` formatted version of this doc...We have, presently, objects for which documentation cannot be properly parsed (i.e., rendered in proper HTML via docutils), some as a result of #253. The solution in these cases, is to render a `<pre></pre>` formatted version of this documentation. This strategy is current adopted in websites like PyPI. So,
1. If documentation can be parsed, render it properly via HTML
2. If documentation cannot be parsed, render it in HTML with `<pre></pre>`.
This may make the fork work again, if the documentation of forked objects is bogus as reported in the mailing list.BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/309[algorithms] Cannot fork shared algorithm2015-09-28T15:50:11ZAndré Anjos[algorithms] Cannot fork shared algorithmAn algorithm that is shared with me cannot be forked.
Try, for example, to hit the following URL:
https://www.beat-eu.org/platform/algorithms/fork/chichan/comp_histogram_similarity/13/
This algorithm is shared with "system/admin...An algorithm that is shared with me cannot be forked.
Try, for example, to hit the following URL:
https://www.beat-eu.org/platform/algorithms/fork/chichan/comp_histogram_similarity/13/
This algorithm is shared with "system/administrators", but cannot be forked. The platform sends a 404.BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/308[experiments] Cannot execute experiment with shared toolchain2015-09-26T17:54:34ZAndré Anjos[experiments] Cannot execute experiment with shared toolchainThe platform tells me the toolchain isn't public, but the toolchain is accessible to me.
2 issues:
1. It should not say "it isn't public", but "it isn't accessible"
2. The said toolchain is accessible to me (and to you as well).
...The platform tells me the toolchain isn't public, but the toolchain is accessible to me.
2 issues:
1. It should not say "it isn't public", but "it isn't accessible"
2. The said toolchain is accessible to me (and to you as well).
Check here by forking this ready to use experiment:
http://beatweb-staging/experiments/setup/chichan/chichan/full_mlbphs_projection/1/MLBPHLDA1/BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/307[teams] API does not return view url for team2015-09-26T17:51:41ZAndré Anjos[teams] API does not return view url for teamLike for the other objects, it would be nice that, upon the creation of a team, the API returned the view URL.Like for the other objects, it would be nice that, upon the creation of a team, the API returned the view URL.BTAS TutorialSamuel GAISTSamuel GAIST