[Possible] Bug Report: Differences between Parallel and Series SBIT Rate Scans

[bdorney]

Brief summary of issue

Types of issue

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

Expected Behavior

The two scans should give the same value of rate vs. scan register (bandwidth considerations not accounted for).

Current Behavior

As shown:

http://cmsonline.cern.ch/cms-elog/1028798

The series and the parallel sbit scans produce different results

Steps to Reproduce (for bugs)

1. Execute: sbitThreshScanParallel.py --shelf=3 -s5 -g0 --vfatmask=0x30 --scanmin=0 --scanmax=256 --stepSize=1
2. Execute: sbitThreshScanSeries.py --shelf=3 -s5 -g0 --vfatmask=0xfffffe --scanmin=0 --scanmax=254 --stepSize=1 --time=1000
3. Analyze the two differtent outputs and compare VFAT0

Possible Solution (for bugs)

The case is the following:

1. There is a bug in the CTP7 FW v3.3.6,
2. There is a bug in the OH FW v3.0.9.A, or
3. There is a bug in sbitRateScanParallelLocal(...) or the corresponding python script sbitThreshScanParallel.py

I will investigate item 3 and update the community.

Context (for feature requests)

Wrong set point

Your Environment

• Version used: 2236dc2
• Shell used: /bin/zsh

[bdorney]

Oops this probably should have gone in ctp7_modules