beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2015-09-08T01:52:26Zhttps://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/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/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/289Notification upon "New environment" or "New database version"2015-09-04T08:55:36ZAndré AnjosNotification upon "New environment" or "New database version"To include in the feature list for the notification framework (besides #230 and #227):
- If a new database version is released by the system administrators, it should signal a search for all experiments using the previous version and ...To include in the feature list for the notification framework (besides #230 and #227):
- If a new database version is released by the system administrators, it should signal a search for all experiments using the previous version and notify the relevant user a newer version of the database is available (with a link to the new database page).
- If a new version of an environment is released, then we should do the same, i.e., scan all experiments that use that environment and notify users of the new environment (with a link to the new environment description).BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/288Notification upon "New environment" or "New database version"2015-09-04T08:55:37ZAndré AnjosNotification upon "New environment" or "New database version"To include in the feature list for the notification framework (besides #230 and #227):
- If a new database version is released by the system administrators, it should signal a search for all experiments using the previous version and ...To include in the feature list for the notification framework (besides #230 and #227):
- If a new database version is released by the system administrators, it should signal a search for all experiments using the previous version and notify the relevant user a newer version of the database is available (with a link to the new database page).
- If a new version of an environment is released, then we should do the same, i.e., scan all experiments that use that environment and notify users of the new environment (with a link to the new environment description).BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/287Notification upon "New environment" or "New database version"2015-09-04T08:55:37ZAndré AnjosNotification upon "New environment" or "New database version"To include in the feature list for the notification framework (besides #230 and #227):
- If a new database version is released by the system administrators, it should signal a search for all experiments using the previous version and ...To include in the feature list for the notification framework (besides #230 and #227):
- If a new database version is released by the system administrators, it should signal a search for all experiments using the previous version and notify the relevant user a newer version of the database is available (with a link to the new database page).
- If a new version of an environment is released, then we should do the same, i.e., scan all experiments that use that environment and notify users of the new environment (with a link to the new environment description).BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/285[experiments] Multiple database versions are shown at the configurator2015-09-04T14:56:11ZAndré Anjos[experiments] Multiple database versions are shown at the configuratorWe have just inserted a new database version for AT&T, called ``atnt/2``. The insertion works fine and the database listing flawlessly.
Meanwhile, when configuring experiments, both database versions are still display whereas only the...We have just inserted a new database version for AT&T, called ``atnt/2``. The insertion works fine and the database listing flawlessly.
Meanwhile, when configuring experiments, both database versions are still display whereas only the latest one should be.
Ideally, we need this fixed for the tutorial. @philip.abbet: Do you think you can have a look at this ASAP? (thanks!)BTAS TutorialPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/282[search] Bigger plots screw-up search page2015-09-02T11:33:09ZAndré Anjos[search] Bigger plots screw-up search pageExample:
https://www.beat-eu.org/platform/search/?query=type:results%20tc:tutorial/eigenface_with_preprocessing/1%20db:atnt/1.idiap%20analyzer:tutorial/postperf_iso/1
And then, enable a "roc" plot. This is related to the fixes on t...Example:
https://www.beat-eu.org/platform/search/?query=type:results%20tc:tutorial/eigenface_with_preprocessing/1%20db:atnt/1.idiap%20analyzer:tutorial/postperf_iso/1
And then, enable a "roc" plot. This is related to the fixes on the merge request !69.BTAS TutorialPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/279[Plotter] Setting alias fails to be set properly on plotted graphs2015-09-03T03:54:08ZFlavio TARSETTI[Plotter] Setting alias fails to be set properly on plotted graphsSome issues with the plotter when an alias is set:
- Plotter library needs to be changed from label to legend
- Some refactoring of the graphic names need to be done (when for example 2 experiments are shown as 4 plots with different n...Some issues with the plotter when an alias is set:
- Plotter library needs to be changed from label to legend
- Some refactoring of the graphic names need to be done (when for example 2 experiments are shown as 4 plots with different names)BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/278[swagger] Is currently broken2015-09-01T17:03:51ZAndré Anjos[swagger] Is currently brokenIt complains it cannot visit one of the required web pages. Hitting on it, for example:
http://beatweb-staging/docs/api-docs/api/v1/reports
Shows:
![Screen_Shot_2015-09-01_at_15.45.20](https://gitlab.idiap.ch/biometric/beat.web/...It complains it cannot visit one of the required web pages. Hitting on it, for example:
http://beatweb-staging/docs/api-docs/api/v1/reports
Shows:
![Screen_Shot_2015-09-01_at_15.45.20](https://gitlab.idiap.ch/biometric/beat.web/uploads/5d088ce45de4107fa8e309ba2deaa1e0/Screen_Shot_2015-09-01_at_15.45.20.png)
BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/277[plot] image size are enforced to 300/4002015-09-02T08:34:02ZFlavio TARSETTI[plot] image size are enforced to 300/400This doesn't let us change the height/width of a plot through a plot templateThis doesn't let us change the height/width of a plot through a plot templateBTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/275Cannot delete public contribution2015-08-31T14:14:35ZAndré AnjosCannot delete public contributionAn API call to:
DELETE /api/v1/toolchains/tutorial/bla/2/
Gets me a 403 error and a message saying the toolchain is being used. I'm sure it is not. I've reproduced this on the staging system and on my local machine.
Something is...An API call to:
DELETE /api/v1/toolchains/tutorial/bla/2/
Gets me a 403 error and a message saying the toolchain is being used. I'm sure it is not. I've reproduced this on the staging system and on my local machine.
Something is not being calculated right under the API.
How to:
1. Create a new toolchain and make it public
2. Try to delete it
The system says it can't, because it's being used (while it's not). It should allow me to delete this contribution. This should be valid for all **unused** contributions independent of their sharing level.BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/273500 error when accessing queue permissions2015-08-27T14:43:10ZAndré Anjos500 error when accessing queue permissionsJust hit: http://beatweb-staging/admin/backend/queue/5/permissions/Just hit: http://beatweb-staging/admin/backend/queue/5/permissions/BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/272[reports] missing ability to delete report items2015-08-27T14:43:53ZFlavio TARSETTI[reports] missing ability to delete report itemsHaving the possibilty to delete a table or plot would be goodHaving the possibilty to delete a table or plot would be goodBTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/271If algorithm sharing state is "usable" (i.e. executable-only by others), then...2015-08-28T12:46:51ZAndré AnjosIf algorithm sharing state is "usable" (i.e. executable-only by others), then it should not be forkable on the UIIn the staging, system, the algorithm "AntonioCandia/hist/1" is usable by all, but not readable. So, a fork button should **not** appear on its list line.
Furthermore, clicking on the said button will generate a 404, since the user h...In the staging, system, the algorithm "AntonioCandia/hist/1" is usable by all, but not readable. So, a fork button should **not** appear on its list line.
Furthermore, clicking on the said button will generate a 404, since the user has no access to the algorithm code.BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/270[reports] Cannot cooperatively create a report2015-08-21T15:19:25ZAndré Anjos[reports] Cannot cooperatively create a reportBecause reports can't be shared today, it is not possible to write a joint publication using the platform w/o a very cumbersome workflow. Like searches, reports should also be shareable.
What would take it for this to be done?Because reports can't be shared today, it is not possible to write a joint publication using the platform w/o a very cumbersome workflow. Like searches, reports should also be shareable.
What would take it for this to be done?BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/269[reports] No way to remove an experiment from a report2015-08-27T14:43:49ZAndré Anjos[reports] No way to remove an experiment from a reportThis was originally reported by @tiago.pereira on a mail to beat-devel, but that is really necessary. Since we're not dealing with a search here, but with an add-as-you-go system, being able to remove something wrongly inserted is a must.This was originally reported by @tiago.pereira on a mail to beat-devel, but that is really necessary. Since we're not dealing with a search here, but with an add-as-you-go system, being able to remove something wrongly inserted is a must.BTAS TutorialFlavio TARSETTIFlavio TARSETTI