Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
nptool nptool
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • 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
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • np
  • nptoolnptool
  • Issues
  • #50

Closed
Open
Created Jan 17, 2018 by Adrien Matta@matta☠Owner

Excitation-Energy Randomisation and Event Rate dropping

Created by: padsley

When I try to run NPTool using a histogram for excitation energy, I find that it tends to run very slowly, and gets slower in contrast to the very similar code for the random angle generation.

Has anyone else seen this happening with NPTOOL or another GEANT4 simulation? I'm presently running valgrind to try to work out if and when a memory leak is occurring but there's nothing obvious leaping out at me at the moment.

So... my query is: "Has anyone else seen this behaviour?" If you haven't ever tried using an Ex histogram input rather than one set value for Ex in the input file, could you try and let me know if it's got this same behaviour of the event rate dropping fairly quickly?

Thanks.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking