beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2018-04-16T15:20:12Zhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/81Make exp using Tensorflow/PyTorch to use a DNN for M-NIST digit classification2018-04-16T15:20:12ZJaden DIEFENBAUGHMake exp using Tensorflow/PyTorch to use a DNN for M-NIST digit classificationSame as other conversion tasks, but this time doing something much differentSame as other conversion tasks, but this time doing something much differenthttps://gitlab.idiap.ch/beat/beat.editor/-/issues/80Convert a DCT-GMM-based face verification Bob experiment to BEAT2018-05-15T09:52:23ZJaden DIEFENBAUGHConvert a DCT-GMM-based face verification Bob experiment to BEATAfter #58, try to use the same toolchain (maybe the same database?) to implement a similar but different experiementAfter #58, try to use the same toolchain (maybe the same database?) to implement a similar but different experiementhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/78algs by default should not be analyzers2018-03-29T08:19:55ZJaden DIEFENBAUGHalgs by default should not be analyzershttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/19Fetch environment data from beat.web instances2018-04-13T12:39:53ZJaden DIEFENBAUGHFetch environment data from beat.web instances...using the `/api/v1/backend/environments/` endpoint.
Not sure how this would be stored...probably just dump the JSON in an `environments.json` file in the `.beat` user folder.
Needed for the June 2018 release!...using the `/api/v1/backend/environments/` endpoint.
Not sure how this would be stored...probably just dump the JSON in an `environments.json` file in the `.beat` user folder.
Needed for the June 2018 release!https://gitlab.idiap.ch/beat/beat.web/-/issues/495Expose more info about the available environments from the REST API2020-03-30T15:38:45ZJaden DIEFENBAUGHExpose more info about the available environments from the REST APIRight now we get something like this:
```json
[
{
"name": "Cxx backend",
"queues": {
"queue": {
"memory_limit": 1985,
"nb_slots": 0,
"max_slots_per_user": 8,
"nb_cores_per_slot": 1,
...Right now we get something like this:
```json
[
{
"name": "Cxx backend",
"queues": {
"queue": {
"memory_limit": 1985,
"nb_slots": 0,
"max_slots_per_user": 8,
"nb_cores_per_slot": 1,
"time_limit": 1440
}
},
"accessibility": "public",
"languages": [
"cxx"
],
"version": "1.1.0",
"short_description": "C++ backend"
},
{
"name": "Python 2.7",
"queues": {
"queue": {
"memory_limit": 1985,
"nb_slots": 0,
"max_slots_per_user": 8,
"nb_cores_per_slot": 1,
"time_limit": 1440
}
},
"accessibility": "public",
"languages": [
"python"
],
"version": "1.2.0",
"short_description": "Local python interpreter"
}
]
```
We need to add a "modules" field to the environments that lists packages & versions that are available. It would look something like this:
```json
[
...
{
"name": "Python 2.7",
...
"packages": {
"alabaster": "0.7.10",
"Babel": "2.4.0",
...
},
"version": "1.2.0",
"short_description": "Local python interpreter"
}
]
```
This is needed for the June 2018 deliverable!https://gitlab.idiap.ch/beat/beat.editor/-/issues/76TODOs for June Deliverable2018-05-30T14:08:33ZJaden DIEFENBAUGHTODOs for June DeliverableMilestones:
| Date | Milestone |
| :--- | :-------- |
| 07.06 | Tutorial date |
| 28.05 | VM ready for tutorial (production) |
| 28.05 | Deployable system / All software is released (tagged) for HES-SO tutorial |
| 21.05 | Fix bugs & re...Milestones:
| Date | Milestone |
| :--- | :-------- |
| 07.06 | Tutorial date |
| 28.05 | VM ready for tutorial (production) |
| 28.05 | Deployable system / All software is released (tagged) for HES-SO tutorial |
| 21.05 | Fix bugs & rewrite tutorial |
| 09.05 | Tutorial at Idiap with Conda packages (beta) |
| 07.05 | First version of deployable system based on Conda (all packages) |
| 23.04 | Feature freeze |
| 04.04 | Encode DCT-GMM-based Face verification (#80) |
| 28.03 | Encode AT&T-based Eigenfaces (from bob.bio.base) (#58) |https://gitlab.idiap.ch/beat/beat.editor/-/issues/75replace import statements in templates with note on how imports in algs/dbs/l...2018-04-09T08:44:12ZJaden DIEFENBAUGHreplace import statements in templates with note on how imports in algs/dbs/libs workhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/72Better cache access & visualization2018-06-11T07:59:40ZJaden DIEFENBAUGHBetter cache access & visualizationIdeas:
- Programmatic access of cache (for instance, loading into jupiter notebooks)
- visualization (seeing images and such in cache & seeing what caches are doing)Ideas:
- Programmatic access of cache (for instance, loading into jupiter notebooks)
- visualization (seeing images and such in cache & seeing what caches are doing)https://gitlab.idiap.ch/beat/beat.editor/-/issues/71Plot generation in beat.cmdline (tracking issue for beat.cmdline#16)2018-05-22T14:53:53ZJaden DIEFENBAUGHPlot generation in beat.cmdline (tracking issue for beat.cmdline#16)This is a tracking issue for beat.cmdline#16 so I can have it in my issues board.This is a tracking issue for beat.cmdline#16 so I can have it in my issues board.https://gitlab.idiap.ch/beat/beat.editor/-/issues/70Tutorial via driver.js2019-01-28T04:36:43ZJaden DIEFENBAUGHTutorial via driver.jsThere's a JS tool that's been thrown into popularity for providing a simple way to provide user tutorials: https://github.com/kamranahmedse/driver.js . *Might* be worthwhile to look intoThere's a JS tool that's been thrown into popularity for providing a simple way to provide user tutorials: https://github.com/kamranahmedse/driver.js . *Might* be worthwhile to look intohttps://gitlab.idiap.ch/beat/beat.editor/-/issues/69Cross-indexing/cross-references2020-02-12T12:15:02ZJaden DIEFENBAUGHCross-indexing/cross-referencesSee where objects are being usedSee where objects are being usedhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/68Deep fuzzy search2020-02-12T12:14:55ZJaden DIEFENBAUGHDeep fuzzy searchA non-essential addendum to #67 - allows for fuzzy-searching inside actual objects (such as searching for dataformat field names/values)A non-essential addendum to #67 - allows for fuzzy-searching inside actual objects (such as searching for dataformat field names/values)https://gitlab.idiap.ch/beat/beat.editor/-/issues/67Fuzzy search box2018-03-16T15:03:16ZJaden DIEFENBAUGHFuzzy search boxSearch through names/descriptionsSearch through names/descriptionshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/66Upgrade to webpack 42018-03-08T15:55:25ZJaden DIEFENBAUGHUpgrade to webpack 4I've put this off long enough, waiting for everything to stabilize. There's apparently huge build performance gains as well as better default settings for the complicated stuff, so I should do this soonish.I've put this off long enough, waiting for everything to stabilize. There's apparently huge build performance gains as well as better default settings for the complicated stuff, so I should do this soonish.https://gitlab.idiap.ch/beat/beat.core/-/issues/47Changing database schema to allow empty `parameters` object2018-09-18T17:27:09ZJaden DIEFENBAUGHChanging database schema to allow empty `parameters` objectIn the [db JSON schema](https://gitlab.idiap.ch/beat/beat.core/blob/a8871304860b9e7c87f3b7ec08c0b308ccd0908a/beat/core/schema/database/1.json#L93), it specifies that a set's `parameters` object must have at least one entry in it. I'd lik...In the [db JSON schema](https://gitlab.idiap.ch/beat/beat.core/blob/a8871304860b9e7c87f3b7ec08c0b308ccd0908a/beat/core/schema/database/1.json#L93), it specifies that a set's `parameters` object must have at least one entry in it. I'd like to remove the `minProperties` restriction to allow this field to exist without having any entries in it.
Now that local editing is becoming a thing, people have access to the JSON metadata files. Having these fields exist even if they're empty allows the user to see these fields when they browse the metadata.
It also makes sense from a parsing POV, since having fields exist even when they're empty makes the data transformation easier, as well as allowing us to define a "skeleton" for these metadata objects.
@samuel.gaist would this change be viable?https://gitlab.idiap.ch/beat/beat.cmdline/-/issues/16Add experiment results plot generation command2018-05-15T13:54:56ZJaden DIEFENBAUGHAdd experiment results plot generation commandI don't see a way to generate~visualize results from successfully-ran experiments outside of pushing the experiment to a `beat.web` installation. This feature seems practically necessary for a easy development cycle.
Maybe add a sub-com...I don't see a way to generate~visualize results from successfully-ran experiments outside of pushing the experiment to a `beat.web` installation. This feature seems practically necessary for a easy development cycle.
Maybe add a sub-command to the experiments or plotters command groups?Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/63Safely create/cast objects using the respective editor's `getValidObject` func2018-03-09T15:40:14ZJaden DIEFENBAUGHSafely create/cast objects using the respective editor's `getValidObject` funcInspired by all the work I have to do to handle malformed objects.
Instead of trusting the objects, use the editor getObject funcs to cast objs in `selectors.jsx`.Inspired by all the work I have to do to handle malformed objects.
Instead of trusting the objects, use the editor getObject funcs to cast objs in `selectors.jsx`.https://gitlab.idiap.ch/beat/beat.editor/-/issues/61Clone files as well as json metadata2018-03-09T16:33:15ZJaden DIEFENBAUGHClone files as well as json metadatahttps://gitlab.idiap.ch/beat/beat.editor/-/issues/58Convert a Bob biometrics experiment to BEAT2018-05-22T14:53:51ZJaden DIEFENBAUGHConvert a Bob biometrics experiment to BEATAfter #54, convert a biometrics experiment (see https://www.idiap.ch/software/bob/docs/bob/bob.bio.base/master/struct_bio_rec_sys.html) to BEATAfter #54, convert a biometrics experiment (see https://www.idiap.ch/software/bob/docs/bob/bob.bio.base/master/struct_bio_rec_sys.html) to BEATStuff before worrying about deploymenthttps://gitlab.idiap.ch/beat/beat.editor/-/issues/57"potentially unsaved changes" remark2018-03-20T15:27:38ZJaden DIEFENBAUGH"potentially unsaved changes" remarkActually checking if the server element is different than the local element is too expensive. Just have a flag "potential_changes_made" that turns on when the user edits something, and turns off when they save/write to serverActually checking if the server element is different than the local element is too expensive. Just have a flag "potential_changes_made" that turns on when the user edits something, and turns off when they save/write to server