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
  • #56
Closed
Open
Issue created Oct 30, 2019 by Niklas Uwe Langner@niklas.langnerOwner

Consistency of the 'charge' value after simulation

When simulating with simulations.ObservedBound and setting the charge to a constant value (like 2), the "charge" value of the resulting CosmicRaysSets is only the set integer. When using a setup of multiple charges (like "mixed"), the "charge" value is an array containing the individual charge of each cosmic ray. I think it would be better if the output was consistent (always the individual value of each cosmic ray) so that the same code can work when only changing the charge composition without the need to check the type of the "charge" value each time.

Assignee
Assign to
Time tracking