Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.cmdline beat.cmdline
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 22
    • Issues 22
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.cmdlinebeat.cmdline
  • Issues
  • #23
Closed
Open
Issue created Apr 27, 2018 by Flavio TARSETTI@flavio.tarsettiDeveloper

[cache] experiments data does not contain all information such as "type" field

When the experiments is run locally, We have a major issue.

Why aren't the information saved the same way as in the API?

One of the most important information is missing in the cache.

I was expecting this as in the API:

"results": {
    "analysis": {
        "bar_plot": {
            "type": "plot/bar/1",
            "primary": false,
            "value": {
                "data": [
                    {
                        "y": [
                            0.0,
                            1.0,
                            2.0,

But I was able to get only this from the local cache:

"bar_plot": {
      "data": [ 
        {       
          "y": [
            0.0,
            1.0,
            2.0,
            3.0,

Where is the "type" field gone?

The type field is important as it indicates which plotter can handle this kind of data.

At present, I am working on plotting using data I get remotely from the experiment when hitting the API, but someone would want to be able to use experiments data he has ran locally and this is not possible at the moment due to the "cache" missing information. This is blocking for local plotting from locally ran experiments.

Assignee
Assign to
Time tracking