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

Docker-in-Docker (DinD) capabilities of public runners deactivated. More info

  • np
  • nptoolnptool
  • Issues
  • #27

Closed
Open
Created Mar 28, 2017 by Adrien Matta@matta☠Owner

Issue in NPSimulation/Scorers/SiliconScorers.cc and .hh

Created by: malabi

An issue was recently reported to me regarding this scorer while used for a gamma-ray detection system, as it returned a wrong strip id assignment and wrong strip multiplicity.

The origin of this problem turned out to be the variable m_Index that is declared as a G4int in the header file but, as used in the cc file (line showed below), can take very large values.

m_Index = aStep->GetTrack()->GetTrackID() + m_DetectorNumber * 1e3 + m_StripLengthNumber * 1e6 + m_StripWidthNumber * 1e9;

The solution is to declare m_Index as a long integer with: int long or G4long.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking