Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • astrotools astrotools
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • astroastro
  • astrotoolsastrotools
  • Issues
  • #54
Closed
Open
Issue created Oct 16, 2019 by Teresa Karolin Bister@teresa.bister🤛🏻Owner1 of 3 checklist items completed1/3 checklist items

Effective storing and calling of directions

  • Internal conversion of vecs to x, y, z in order to efficiently store inside shape_array? -> better smaller size than fast calling of vecs?
  • remove convert_all in simulations
  • raise Warning only if someone stores different info in a similar direction key, no warning for same info (enables faster calling)
  • How to treat pixels regarding the conversion?
Edited Oct 17, 2019 by Marcus Wirtz
Assignee
Assign to
Time tracking