Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
tomwer
tomwer
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 46
    • Issues 46
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • tomotools
  • tomwertomwer
  • Issues
  • #495

Closed
Open
Opened Oct 28, 2020 by payno@payno
  • Report abuse
  • New issue
Report abuse New issue

rework nexus-file management

We could create a cache or create modified nexus file at some processes. The 'first' / raw nexus file should stay 'untouched'. Then we should process on other files. One file per process ? For example modifying image_key(s) should be done in a separate file.

In this case we should also provide a widget for 'overwritting the nexus file' or 'dumping / copying' current nexus file. This is the same for tomwer_processes.h5. We could have several when there is some 'branch' fork. And we could have file to dump processes of one branch only.

Edited Nov 05, 2020 by payno
To upload designs, you'll need to enable LFS. More information
Assignee
Assign to
0.7
Milestone
0.7
Assign milestone
Time tracking
None
Due date
None
2
Labels
medium priority refactoring
Assign labels
  • View project labels
Reference: tomotools/tomwer#495