beat.core issueshttps://gitlab.idiap.ch/beat/beat.core/-/issues2017-08-06T11:17:03Zhttps://gitlab.idiap.ch/beat/beat.core/-/issues/31Experiment setup() does not handle properly blocks with multiple outputs2017-08-06T11:17:03ZLaurent EL SHAFEYExperiment setup() does not handle properly blocks with multiple outputsFollowing the major revamping of this package, blocks with multiple outputs are not handled in the right way.
In particular, the current implementation of the setup() method for Experiment assumes that a block has a single output (e.g. ...Following the major revamping of this package, blocks with multiple outputs are not handled in the right way.
In particular, the current implementation of the setup() method for Experiment assumes that a block has a single output (e.g. see https://gitlab.idiap.ch/biometric/beat.core/blob/v0.8.1/beat/core/experiment.py#L858).
I am unsure whether there are other implications in the code or not.Tutorial for the FG2015 ConferenceLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.core/-/issues/30beat db index improvements2017-08-06T11:17:03ZAndré Anjosbeat db index improvementsShould index all databases, if not specified which.
It should also support multiple databases to be indexed.Should index all databases, if not specified which.
It should also support multiple databases to be indexed.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/28No way to visualise (binary) cache data2017-08-06T11:17:03ZAndré AnjosNo way to visualise (binary) cache dataAfter our data re-structuring in this package, a useful feature was removed: the ability to write cache files as JSON text. Cache files are now written in binary format, which improves the calculation precision and translates to what hap...After our data re-structuring in this package, a useful feature was removed: the ability to write cache files as JSON text. Cache files are now written in binary format, which improves the calculation precision and translates to what happens inside the platform. It is also much faster.
A side effect was we lost the possibility to directly view cache files.
A command-line option/command at our `beat` swiss-army knife could allow us to recover this ability, by providing a "view" command that allows one to inspect the contents of binary cache files.
This bug will remain opened until this is fixed.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/27Downloading/Uploading of database declarations and views2017-08-06T11:17:03ZAndré AnjosDownloading/Uploading of database declarations and viewsOnce beat.web#86 is fixed, then we should implement the pull/push of database declarations via the command-line as well.Once beat.web#86 is fixed, then we should implement the pull/push of database declarations via the command-line as well.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/23beat * pull commands are extremely slow in certain cases2017-08-06T11:17:04ZAndré Anjosbeat * pull commands are extremely slow in certain casesI'm currently implementing some tests for the cmdline utilities. I'm noticing that pulling algorithms out of the platform gets extremely slow in some circumstances. Namely, when using the tool as user `tutorial`, but downloading stuff fr...I'm currently implementing some tests for the cmdline utilities. I'm noticing that pulling algorithms out of the platform gets extremely slow in some circumstances. Namely, when using the tool as user `tutorial`, but downloading stuff from user `tpereira`. What is special about this? Why is it so slow? To be checked.
The same behaviour **cannot** be observed downloading either `data formats` or `toolchains`. I wonder if there is a problem with the algorithm -> data format dependence.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/21Output method write() is not able to process beat.core.Data instances2017-08-06T11:17:04ZManuel GüntherOutput method write() is not able to process beat.core.Data instancesThe output method write() is currently not able to process beat.core.Data instances.
This means that when a complex data structure is read from the inputs and that this input has to be written in one of the outputs, the user currently...The output method write() is currently not able to process beat.core.Data instances.
This means that when a complex data structure is read from the inputs and that this input has to be written in one of the outputs, the user currently has to convert it into a JSON like python dictionary.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/19More robust JSON validation2017-08-06T11:17:04ZAndré AnjosMore robust JSON validationWe currently have in place a hand-crafted JSON validation strategy for the many JSON bits we manipulate inside the platform.
I propose we improve JSON validation by introducing [JSON schemas](http://json-schema.org/) for every piece o...We currently have in place a hand-crafted JSON validation strategy for the many JSON bits we manipulate inside the platform.
I propose we improve JSON validation by introducing [JSON schemas](http://json-schema.org/) for every piece of JSON we handle in the platform. There is a [Python package available on PyPI](https://pypi.python.org/pypi/jsonschema) that is compatible with draft-4 (the latest) of the specification.
Find [here](http://spacetelescope.github.io/understanding-json-schema/), a gentle introduction to JSON schemas.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/18beat experiment pull does not pull all dataformats and complains2017-08-06T11:17:04ZAndré Anjosbeat experiment pull does not pull all dataformats and complainsAfter changes with the version numbers, a simple `beat experiments pull` for a particular experiment does not pull all dataformats required by the experiment anymore. As a result, the experiment cannot be run immediately after.After changes with the version numbers, a simple `beat experiments pull` for a particular experiment does not pull all dataformats required by the experiment anymore. As a result, the experiment cannot be run immediately after.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/16beat experiment run does not use external environment2018-11-03T15:23:12ZAndré Anjosbeat experiment run does not use external environmentCurrently, the command to run experiments on the user machine does not rely on the same infrastructure used by the platform to run experiments.
It would be good these two things converged at a certain point.Currently, the command to run experiments on the user machine does not rely on the same infrastructure used by the platform to run experiments.
It would be good these two things converged at a certain point.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/13Input management2018-11-03T15:23:12ZAndré AnjosInput managementIt would be interesting to revisit input management on algorithms and analysis blocks and try to factor out code that is repeated everywhere into a simpler interface.
This bug shall be used to track advances on this field.It would be interesting to revisit input management on algorithms and analysis blocks and try to factor out code that is repeated everywhere into a simpler interface.
This bug shall be used to track advances on this field.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/12Object renaming2018-11-03T15:23:12ZAndré AnjosObject renamingIt should be possible to rename:
- [ ] algorithms
- [ ] dataformats
- [ ] toolchains
- [ ] experiments
The platform should handle renaming gracefully.It should be possible to rename:
- [ ] algorithms
- [ ] dataformats
- [ ] toolchains
- [ ] experiments
The platform should handle renaming gracefully.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/10Library support2018-11-03T15:23:12ZAndré AnjosLibrary supportA ticket for holding information on library support. Some aspects discussed over the last months:
- The easiest to start with would be: 1 library = 1 file, pretty much like algorithms.
- External (bigger packages) need to be installe...A ticket for holding information on library support. Some aspects discussed over the last months:
- The easiest to start with would be: 1 library = 1 file, pretty much like algorithms.
- External (bigger packages) need to be installed with the processing environment.
- Libraries should be version-nable such as algorithms.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/7Improvements to the beat command-line tool (migrated from github)2015-03-25T07:37:09ZAndré AnjosImprovements to the beat command-line tool (migrated from github)- [x] Pull a configuration
- [x] Push a configuration
- [x] Edition/Pull/Push of descriptions associated to different objects
- [x] Color configuration
- [x] Check of a toolchain `beat toolchain check ...`
- [x] Algorithm changes de...- [x] Pull a configuration
- [x] Push a configuration
- [x] Edition/Pull/Push of descriptions associated to different objects
- [x] Color configuration
- [x] Check of a toolchain `beat toolchain check ...`
- [x] Algorithm changes detection when running an experiment
- [x] Check user existence in commands like: `beat algorithms pull --user ADHDAHGDGAHSGHDAGHSDGH`. Presently, this is silently ignored.
- [x] While running locally, it would be nice that this package printed out more information about data input and output. It is currently very summarized.
Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/2Warning for unconnected/multiply connected blocks (migrated from github)2015-03-06T08:05:11ZAndré AnjosWarning for unconnected/multiply connected blocks (migrated from github)Along the same lines as #39, it would be convenient that both `check_toolchain.py` and `run_toolchain.py` would check for unconnected blocks and issue a **warning** in case one is detected. It would be an immense helper for debugging new...Along the same lines as #39, it would be convenient that both `check_toolchain.py` and `run_toolchain.py` would check for unconnected blocks and issue a **warning** in case one is detected. It would be an immense helper for debugging new toolchains.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/3Repeated connection is not detected on toolchain JSON (migrated from github)2015-03-06T08:04:27ZAndré AnjosRepeated connection is not detected on toolchain JSON (migrated from github)By mistake, I created a repeated connection from one block to another, on my list of connections. The platform has signaled the toolchain to be valid, but when running, the following error occurred:
```python
File "/remote/filer.gx...By mistake, I created a repeated connection from one block to another, on my list of connections. The platform has signaled the toolchain to be valid, but when running, the following error occurred:
```python
File "/remote/filer.gx/user.active/aanjos/work/projects/beat/beat/eggs/ipdb-0.7-py2.7.egg/ipdb/__main__.py", line 138, in main
pdb._runscript(mainpyfile)
File "/usr/lib/python2.7/pdb.py", line 1233, in _runscript
self.run(statement)
File "/usr/lib/python2.7/bdb.py", line 400, in run
exec cmd in globals, locals
File "<string>", line 1, in <module>
File "./bin/run_toolchain.py", line 3, in <module>
import sys
File "/remote/filer.gx/user.active/aanjos/work/projects/beat/beat/src/beat.core/beat/core/scripts/run_toolchain.py", line 186, in main
if isinstance(connection.output.block, Database):
AttributeError: 'NoneType' object has no attribute 'output'
Uncaught exception. Entering post mortem debugging
```
I guess that should be relatively easy to fix.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjos