Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
I
id06workflow
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 12
    • Issues 12
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • payno
  • id06workflow
  • Issues
  • #3

Closed
Open
Opened Oct 15, 2018 by payno@payno
  • Report abuse
  • New issue
Report abuse New issue

Save experiement

Experiment with result and raw data should be saved (into an .h5 file for example).

This is why an addOperation should be added to the Experiment class. This would add to the stack of operation a name and the set of parameters used for this operation:

  • roi selection
  • noise removal ... This would be called before the 'send' of the orange processing ? Or exported in the processing (would be better I guess if we want to remove the orange part one day. So this way can be an update operation).
To upload designs, you'll need to enable LFS. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
1
Labels
new process
Assign labels
  • View project labels
Reference: payno/id06workflow#3