Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
aeva
aeva
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 62
    • Issues 62
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • aeva
  • aevaaeva
  • Issues
  • #167

Closed
Open
Created Nov 24, 2020 by David Thompson@dcthompOwner

MED exporter integration

Currently, the MED export operation is not registered with the SMTK exporter operation-group. It should be, so that users can choose MED as a format for saving data.

In order to be a member of the smtk::operation::ExporterGroup, the operation must be modified to accept association to resources, not just models as it currently does.

Assignee
Assign to
aeva 2.0.1
Milestone
aeva 2.0.1 (Past due)
Assign milestone
Time tracking
None
Due date
None