The y-axis lost it's restriction in a previous version, I have fixed it so that the y-axis is fixed between 1e-1 and 1e8.
Types of changes
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Motivation and Context
This was causing issues for the qc7 team, the y-axis should have remained fixed.
How Has This Been Tested?
#!/usr/bin/env bash
#=========================================================================================
# Testing Suite for the Inflection Point finder ------------------------------------------
#=========================================================================================
echo "Welcome to Brendan's Testing Suite for the Inflection Point Finder"
echo "------------------------------------------------------------------------------------"
echo "This script executes a bunch of files known to cause issues for the inflection"
echo "point finder"
echo "------------------------------------------------------------------------------------"
echo "Did you remember to update??? With make pip and pip install rpm*.tar.gz?"
echo "File 1"
echo "This tests how the code handles a vfat with a bad vfat"
echo "Please make sure (2,5,4) is filled in your system_specfic_constants.py file"
# This file causes issues because of a zero slope issue
anaSBitThresh.py /data/bigdisk/GEM-Data-Taking/GE11_QC8//sbitRate/channelOR/2019.10.25.13.59/SBitRateData.root
echo "File 2"
echo "This tests how the code handles a detector with missing vfats"
echo "Please make sure (1,2,0) is filled in your system_specfic_constants.py file"
# This file is from the coffin where the detector is missing vfats
anaSBitThresh.py /data/bigdisk/GEM-Data-Taking/GE11_Integration//sbitRate/channelOR//2019.10.24.17.45/SBitRateData.root
Screenshots (if appropriate):
Checklist:
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
Description
The y-axis lost it's restriction in a previous version, I have fixed it so that the y-axis is fixed between 1e-1 and 1e8.
Types of changes
Motivation and Context
This was causing issues for the qc7 team, the y-axis should have remained fixed.
How Has This Been Tested?
Screenshots (if appropriate):
Checklist: