beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2015-09-04T08:55:36Zhttps://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/286Notification upon "New environment" or "New database version"2015-11-12T14:18:28ZAndré 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).Final DocumentationSamuel 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/284[reports] Plot URL not found2015-11-25T15:31:33ZAndré Anjos[reports] Plot URL not foundYet another place where we're missing the URL_PREFIX trick: http://beatweb-staging/reports/1164982793/, somehow.Yet another place where we're missing the URL_PREFIX trick: http://beatweb-staging/reports/1164982793/, somehow.Final DocumentationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/283[reports] Inconsistent behaviour with delete2019-07-04T08:37:02ZAndré Anjos[reports] Inconsistent behaviour with deleteWhen I delete an experiment from the report by clicking a button on the GUI, it immediately deletes the experiment from the report and saves it.
If I do the same with any other button on that GUI, I need to click on the "Save report" ...When I delete an experiment from the report by clicking a button on the GUI, it immediately deletes the experiment from the report and saves it.
If I do the same with any other button on that GUI, I need to click on the "Save report" button to get it saved. This is confusing.
We either have to go one way or the otherhttps://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/281[plotter] Parameters are not associated to Plotters2015-11-20T11:23:06ZAndré Anjos[plotter] Parameters are not associated to PlottersThey should, otherwise we'll see parameters sometimes related to specific plotters showing up everywhere.They should, otherwise we'll see parameters sometimes related to specific plotters showing up everywhere.Final DocumentationAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/280[reports] Expiration of reports2016-03-14T16:12:24ZAndré Anjos[reports] Expiration of reportsAs with attestations, reports should also expire, so the workflow for both of them is similar. Contrary to attestations, we should not simply delete expired reports, as users put effort and time tunning them. What we should do is to remo...As with attestations, reports should also expire, so the workflow for both of them is similar. Contrary to attestations, we should not simply delete expired reports, as users put effort and time tunning them. What we should do is to remove the lock and revert the report to an editable state again. At this point, we need to **make sure to reset the report number to a different one**, so that any links to it will now be broken.
This makes the work flow for both types of objects be the same while preserving reports.Flavio TARSETTIFlavio TARSETTIhttps://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/276[search] Plot template not showing up on search2016-04-04T14:37:02ZFlavio TARSETTI[search] Plot template not showing up on searchMissing the new feature "plot template selection" on searchMissing the new feature "plot template selection" on searchFlavio 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/274Sharing modal window does not update w.r.t. shared users/teams2015-11-20T11:24:26ZAndré AnjosSharing modal window does not update w.r.t. shared users/teamsIf a user shares a contribution with another user or a team, there is no way to see who the contribution is shared with (after the contribution page is reloaded).
It would be good if the sharing modal window was correctly pre-filled w...If a user shares a contribution with another user or a team, there is no way to see who the contribution is shared with (after the contribution page is reloaded).
It would be good if the sharing modal window was correctly pre-filled with the people/teams the contribution was shared with.Final DocumentationPhilip ABBETPhilip ABBEThttps://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 TARSETTI