platform icon indicating copy to clipboard operation
platform copied to clipboard

HOBBIT benchmarking platform

Results 100 platform issues
Sort by recently updated
recently updated
newest added

It should be possible to schedule the closing of a challenge.

type: enhancement
component: UI
priority: low
component: controller
component: core-lib
component: ontology

### User story Users who inspect experiment results may want to know which version of the HOBBIT platform experiment were run on. ### Solution Store versions of all components and...

type: enhancement
component: UI
priority: high
component: controller
component: ontology

### User story Benchmarks and systems need versioning so you can use a specific version for an experiment and also have experiment results grouped by version. It will also allow...

component: UI
priority: high
type: discussion
component: controller
component: ontology

### User story It would be useful to allow benchmarks (and maybe systems) to generate any kind of artifacts (files) to be stored and be accessible later. One example where...

type: enhancement
component: ontology

In some cases, [like here](http://master.project-hobbit.eu/#/challenges/http%3A%2F%2Fw3id.org%2Fhobbit%2Fchallenges%238bd4f77f-ec7c-4e73-8048-c986fbbdce7c/experiments?task-id=http%3A%2F%2Fw3id.org%2Fhobbit%2Fchallenges%238bd4f77f-ec7c-4e73-8048-c986fbbdce7c_task2 ), the result pages show errors such as ```The experiment took too much time.``` The timeout value should be indicated (i.e. was it 5 minutes,...

type: enhancement
component: UI
priority: low
component: controller
component: ontology

Parameters and KPIs can be tricky to display there but at least it can display whether experiment was successful or not. - [ ] whether experiment was successful - [...

type: enhancement
component: UI

### User story Users want to see some statistics on KPIs when viewing several experiments together, like - expected value - standard deviation - ... ### Solution Display it in...

type: enhancement
component: UI

For example this log: > Some problem occurred! > at org.mypackage... > at abc.def.... logstash will break this log into three messages, each containing one line of the original log....

type: enhancement
priority: critical

### User story When viewing details of several experiments at once, it should be easier to see if experiments shared any parameters or KPI values. ### Solution By default, merge...

type: enhancement
component: UI

### User story When viewing experiment details, I want to see how many other experiments used the same parameters and be able to browse them. ### Solution Add a link...

type: enhancement
component: UI
priority: low