beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2015-11-10T11:58:55Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/221Few algorithms do directly use data_index attributes2015-11-10T11:58:55ZLaurent EL SHAFEYFew algorithms do directly use data_index attributesFew algorithms on the platform do directly use data_index{,_end} attributes of the inputs.
The I/O uses the SynchronizationListener class to ensure that outputs are always synchronized with the main input channel.
Therefore, the use of...Few algorithms on the platform do directly use data_index{,_end} attributes of the inputs.
The I/O uses the SynchronizationListener class to ensure that outputs are always synchronized with the main input channel.
Therefore, the use of these attributes in the algorithm side should not be neither required nor allowed.
See the following issue for more details: https://gitlab.idiap.ch/biometric/beat.examples/issues/11
Final Documentationhttps://gitlab.idiap.ch/beat/beat.web/-/issues/227E-mail notification when experiment done2015-11-05T08:39:39ZAndré AnjosE-mail notification when experiment doneIt would be an useful feature a check box on the experiment submission page allowing the user to be notified when that experiment is done. We already have the user e-mail in hand.It would be an useful feature a check box on the experiment submission page allowing the user to be notified when that experiment is done. We already have the user e-mail in hand.Final Documentationhttps://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/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/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/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/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/186Reports: Export to CSV, LaTeX, PNG2015-10-26T08:34:28ZPhilip ABBETReports: Export to CSV, LaTeX, PNGDepends on #185
In a Locked Report, the table generated should be exportable in LaTeX or CSV mode, so that a user can adapt it to its own publication.
At minimum: CSV + PNG
Depends on #185
In a Locked Report, the table generated should be exportable in LaTeX or CSV mode, so that a user can adapt it to its own publication.
At minimum: CSV + PNG
Final DocumentationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/184Reports: Report page editor2015-10-02T15:47:34ZPhilip ABBETReports: Report page editorDepends on #183
The Report page should allow the user to display features of the
experiment. Preferably, it should be made flexible enough so that new
conditions can be added in a relatively easy way (i.e., w/o necessarily
requiring a ...Depends on #183
The Report page should allow the user to display features of the
experiment. Preferably, it should be made flexible enough so that new
conditions can be added in a relatively easy way (i.e., w/o necessarily
requiring a modification of large parts of the system). At first, apart
from what is already displayable at Search results, these are the other
conditions we'd thought are necessary. We've organized it in "Columns" of
interest, which can be mixed and matched upon user configuration.
- [x] Column "block computing time": Displays the computing time of a given block. Requires all experiments have a block with a given name
- [x] Column "total experiment time": Displays the total computing time for an experiment
- [x] Column "parameter value": Displays a parameter value in an algorithm for all experiments. Requires all experiments have an algorithm with a given value. If the algorithm has two values, displays a comma-separated list of values for each of those parameters.
- [x] Column "results": Displays any valid analyzer result.
- [x] Column "user label": Allows the user to define a label of its own for a given experiment.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 GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/303[api] Sharing of algorithm does not consider attached libraries2015-09-17T15:15:58ZAndré Anjos[api] Sharing of algorithm does not consider attached librariesAs of today, algorithm sharing only considers the used data formats, but not used libraries. We should change in such a way that it does.
Furthermore, libraries can also use libraries, so sharing a library should also affect libraries...As of today, algorithm sharing only considers the used data formats, but not used libraries. We should change in such a way that it does.
Furthermore, libraries can also use libraries, so sharing a library should also affect libraries that are needed by that library.BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/302[api] Creation of an object does not return its final full name2015-09-17T15:15:58ZAndré Anjos[api] Creation of an object does not return its final full nameI just realised that, when we create a new object, the API only returns an empty message with a 200 status code. It is not possible to be assertive about the full name the object will take on the other side. That would imply, at least, i...I just realised that, when we create a new object, the API only returns an empty message with a 200 status code. It is not possible to be assertive about the full name the object will take on the other side. That would imply, at least, in 2 API calls (one for `check_name` before the post), and hope for the best on the naming, including bumped version numbers accounting.
Ideally, the API should return the full name of the created object so that the client knows what is its final name. As a plus, it could also return the "view" URL, allowing the client to redirect to the final view of the just created object. As it can be expected, calculating the final view URL from javascript is not an easy task and may imply in too much hard-coding (as it is already). A change in the Django URLs and we're off into re-writing everything again.
In summary, all create APIs, new versions, forks, etc should return the final object created full name + at least the view URL of the object.BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/304[plotter/report] legend not taken into account for single experiment2015-09-16T12:22:21ZFlavio TARSETTI[plotter/report] legend not taken into account for single experimentLegend option is not taken into account for single experiment in report.
Could you please fix that as it's blocking my part please.
Thanks.Legend option is not taken into account for single experiment in report.
Could you please fix that as it's blocking my part please.
Thanks.André AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/301[backend] Queues are not exclusive to a set of users2015-09-13T22:23:48ZAndré Anjos[backend] Queues are not exclusive to a set of usersInstead, environments are. This is a bit odd, since the queue is the element that represents concrete hardware resources. We must change this ASAP as to support custom queue management.Instead, environments are. This is a bit odd, since the queue is the element that represents concrete hardware resources. We must change this ASAP as to support custom queue management.BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/300[algorithms] Cannot fork shared algorithm2015-09-09T13:34:40ZAndré Anjos[algorithms] Cannot fork shared algorithmThis seems to work on publicly shared algorithms, but not team-shared ones.
For example: https://www.beat-eu.org/platform/algorithms/chichan/comp_histogram_similarity/8/
Is shared with system/administrators (which is all of us) and...This seems to work on publicly shared algorithms, but not team-shared ones.
For example: https://www.beat-eu.org/platform/algorithms/chichan/comp_histogram_similarity/8/
Is shared with system/administrators (which is all of us) and forking it hits a 404 on:
https://www.beat-eu.org/platform/api/v1/algorithms/chichan/comp_histogram_similarity/1/?fields=html_description,description,short_description
As you can see on the algorithm description at the Django admin interface, the algorithm is properly shared, so the forking should work:
https://www.beat-eu.org/platform/admin/algorithms/algorithm/665/?_changelist_filters=q%3Dchichan
My guess is that there is an issue somewhere in rest framework end point concerning team sharing.BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/297[experiments] Configurator gets confused if the user selects a new algorithm ...2015-09-08T10:43:10ZAndré Anjos[experiments] Configurator gets confused if the user selects a new algorithm for blockIf I fork the experiment: https://www.beat-eu.org/platform/experiments/tutorial/tutorial/full_lbphs/1/atnt-lbphs-para/, and then replace the algorithm in a block with a decollapsed parameter set, the platform tells me that the parameters...If I fork the experiment: https://www.beat-eu.org/platform/experiments/tutorial/tutorial/full_lbphs/1/atnt-lbphs-para/, and then replace the algorithm in a block with a decollapsed parameter set, the platform tells me that the parameters are `undefined`. I'm not sure this problem is related to the fact there are two blocks with similar version lurking around or it is just the swap that confuses the configurator, when it a set of parameters preset.
Anyways, the expected behaviour would be, to preserve all possible parameters that make sense in the new settings, from the old one.
![Screen_Shot_2015-09-08_at_03.56.42](https://gitlab.idiap.ch/biometric/beat.web/uploads/884213b3a8ec182293c79350704754a3/Screen_Shot_2015-09-08_at_03.56.42.png)BTAS TutorialPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/298[experiments] I can now delete experiments with attestations!2015-09-08T10:33:59ZAndré Anjos[experiments] I can now delete experiments with attestations!This is a critical one!
https://www.beat-eu.org/platform/experiments/tutorial/tutorial/eigenface_with_preprocessing/1/eigenface-with-preproc-15/
@samuel.gaist, can you please have a look? Thanks, AThis is a critical one!
https://www.beat-eu.org/platform/experiments/tutorial/tutorial/eigenface_with_preprocessing/1/eigenface-with-preproc-15/
@samuel.gaist, can you please have a look? Thanks, ABTAS TutorialSamuel GAISTSamuel GAIST