Skip to content
This repository has been archived by the owner on Jan 31, 2022. It is now read-only.

GE2/1 compatibility and elimination of GE1/1-specific hardcoded constants #131

Open
1 of 2 tasks
mexanick opened this issue Jun 13, 2019 · 0 comments
Open
1 of 2 tasks

Comments

@mexanick
Copy link
Contributor

Brief summary of issue

Current version of the code suffers from various GEM detector type specific constants being hardcoded and can't be used in a straightforward manner with the GE2/1

Types of issue

  • Bug report (report an issue with the code)
  • Feature request (request for change which adds functionality)

Expected Behavior

The software should work in the very same manner between GE1/1 and GE2/1

Current Behavior

Currently some of the methods are still working, but wasting the memory assuming GE1/1 electronics layout, others simply does not work properly due to mapping differences.

Your Environment

  • Version used: tip of develop
  • Shell used: bash
  • Setup: GE2/1 integration stand
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants