This repository has been archived by the owner on Jan 31, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 29
Feature/ge21compatibility #287
Merged
mexanick
merged 17 commits into
cms-gem-daq-project:generic-amc-RPC-v3-short-term
from
mexanick:feature/ge21compatibility
Jul 8, 2019
Merged
Changes from 15 commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
30b4fb9
Changing NGBT in hw_constants, adding additional debug info
mexanick 2770c29
Fixing gemType propagation to HwAMC from HwOH
mexanick 4681866
Revert "Fixing gemType propagation to HwAMC from HwOH"
mexanick fdf2853
Fixing gemType propagation to HwAMC from HwOH
mexanick 9bca633
Fixing hardcoded NVFATs
mexanick edf11e5
Fixing GBT scan
mexanick e37907d
Trying another phase
mexanick 391ceef
adding default phases for GE2/1 from Evaldas's tests
mexanick 7b0c892
Implementing Brian's comments
mexanick 564a503
Reverting for the moment self.NVFAT where it is undefined
mexanick 3ced528
Fixing getVFATChipIDs call
mexanick de8d628
Fixing getVFATChipIDs call
mexanick 38b6672
Fixing compatibility with new xhal APIs
mexanick da5761d
Fixing broadcastRead
mexanick 8d1c662
Fixing doc
mexanick a5999e0
Fixing nVFAT typos
mexanick 8b022ff
Switching NVFAT to nVFATs
mexanick File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we won't have a situation where
detType
has a different number of VFATs correct?e.g. {M1,...,M8} all have 12 VFATs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also in
HwOptohybrid
this isself.nVFATs
vs.self.NVFAT
.Should we keep both these data members...in retrospect probably the better way to go would have been to have:
HwOptohybrid
inherit fromHwAMC
andHwVFAT
inherit fromHwOptohybrid
. Then all thisparentX
crap which is, admittedly, messy could disappear. Although whether that type of change is appropriate for this PR (or ever given this is #legacy) is unclear. Alas...my programming skills have improved since the original design...There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would caution against making API changes at this point, since this legacy stuff is supposed to be frozen anyway...
We will have to potentially think of how to map this in the updated API, where currently there is not going to be a
HwVFAT
, though it could be added if deemed absolutely critical (would just have to think of how best to do so...)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed. For this PR then I would suggest we keep both data members but just standardized the data member name in both classes for QOL; so it should be either
self.NVFAT
orself.nVFATs
with a slight preference forself.nVFATs
simply because it pre-dates this PR inHwOptohybrid
.