beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2015-09-07T11:45:17Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/290[reports] Cannot add symbols to experiment alias2015-09-07T11:45:17ZAndré Anjos[reports] Cannot add symbols to experiment aliasFor some reason, we cannot add symbols such as `+` to experiment aliases in reports. To be checked.For some reason, we cannot add symbols such as `+` to experiment aliases in reports. To be checked.BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/296[experiments] Despite atnt/2 shows on the experiment display, atnt/1 is still...2015-09-08T01:51:19ZAndré Anjos[experiments] Despite atnt/2 shows on the experiment display, atnt/1 is still chosenIf you fork this experiment:
https://www.beat-eu.org/platform/experiments/tutorial/tutorial/full_isv/2/atnt_isv_DCT12x8_100G_U50/
You'll see the datasets for ATNT/2 are chosen for you.
If you run it (the experiment will fail, bu...If you fork this experiment:
https://www.beat-eu.org/platform/experiments/tutorial/tutorial/full_isv/2/atnt_isv_DCT12x8_100G_U50/
You'll see the datasets for ATNT/2 are chosen for you.
If you run it (the experiment will fail, but no worries), you'll see that the toolchain shown on the bottom indicates that ATNT/1 datasets are still chosen in stead of what is displayed. Must be a bug.BTAS TutorialPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/293[algoritms] Cannot visualise differences between algorithms anymore2015-09-08T01:51:20ZAndré Anjos[algoritms] Cannot visualise differences between algorithms anymoreThe "history" page only displays the changes on the JSON, but no the change on the algorithm code itself!
Please! Can somebody look at this ASAP?The "history" page only displays the changes on the JSON, but no the change on the algorithm code itself!
Please! Can somebody look at this ASAP?BTAS TutorialPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/292Experiment cannot be deleted, despite not being attested2015-09-08T01:51:43ZAndré AnjosExperiment cannot be deleted, despite not being attestedThis experiment:
tpereira / tutorial / full_fisherface / 1 / PCA-200_LDA-49_periocular_mobio-male
Is shared with the team `system/administrators`, so all of us have access to it. It has no attestations attached to it. If the user (...This experiment:
tpereira / tutorial / full_fisherface / 1 / PCA-200_LDA-49_periocular_mobio-male
Is shared with the team `system/administrators`, so all of us have access to it. It has no attestations attached to it. If the user (tpereira) logs in and then tries to push the "Delete" button, which is enabled for this experiment, then it gets:
![Screen_Shot_2015-09-06_at_13.59.53](https://gitlab.idiap.ch/biometric/beat.web/uploads/03a58864d06bf881fa2851c6972fe31a/Screen_Shot_2015-09-06_at_13.59.53.png)
BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/291[experiments] Experiment was shared, together with toolchain, but configurato...2015-09-08T01:51:44ZAndré Anjos[experiments] Experiment was shared, together with toolchain, but configurator refuses to use itFor example, this experiment was shared with the team system/administrators:
https://www.beat-eu.org/platform/experiments/setup/chichan/chichan/full_mlbphs/1/MLBPH_comp7/
As you can see, if you try to fill-in the label and then pre...For example, this experiment was shared with the team system/administrators:
https://www.beat-eu.org/platform/experiments/setup/chichan/chichan/full_mlbphs/1/MLBPH_comp7/
As you can see, if you try to fill-in the label and then press the Go button, the configurator refuses to submit the experiment saying the toolchain is not public.
The expected behaviour is that it allows us to run the experiment, given the toolchain is also shared with us:
https://www.beat-eu.org/platform/admin/toolchains/toolchain/213/?_changelist_filters=q%3Dchichan
BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/295[reports] Delete button is still shown even if report is published2015-09-08T01:52:26ZAndré Anjos[reports] Delete button is still shown even if report is publishedHow to reproduce:
1. Create a report and publish it
2. Go back to the user page, to the relevant tab
3. The report published still has a "delete" button displayed (clicking it pops-up a box saying it is readonly).
Ideally, in thi...How to reproduce:
1. Create a report and publish it
2. Go back to the user page, to the relevant tab
3. The report published still has a "delete" button displayed (clicking it pops-up a box saying it is readonly).
Ideally, in this case, there should be no button.BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/294[reports] If the experiment is locked or published, then the experiment alias...2015-09-08T01:52:48ZAndré Anjos[reports] If the experiment is locked or published, then the experiment aliases are not properly displayed at user viewOn the user view, when the experiment is locked, the system shows the experiment names but not their aliases. It seems to work well for the "other's view" though.
On the user view, when the experiment is locked, the system shows the experiment names but not their aliases. It seems to work well for the "other's view" though.
BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/299[experiments] Cannot create experiment from toolchain2015-09-08T10:00:29ZAndré Anjos[experiments] Cannot create experiment from toolchainA JS error is produced. For example:
https://www.beat-eu.org/platform/experiments/setup/tutorial/eigenface/1/
Please! A fix!A JS error is produced. For example:
https://www.beat-eu.org/platform/experiments/setup/tutorial/eigenface/1/
Please! A fix!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 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/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/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/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/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/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/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/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/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/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 TARSETTI