There are times where scaling the data is not desired. This addresses this problem in the different instrument functions that had previously had scaling hard-coded in.
Type of change
Please delete options that are not relevant.
New feature (non-breaking change which adds functionality)
This change requires a documentation update
How Has This Been Tested?
Created new unit tests, ran functions with new functionality.
Test Configuration:
Operating system: OS X Big Sur
Version number: Python 3.9, 3.8
Any details about your local setup that are relevant
Checklist:
[x] Make sure you are merging into the develop (not main) branch
[x] My commits are formatted appropriately (following the SciPy/NumPy style)
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] Add a note to Changelog.rst, summarising the changes
Coverage increased (+13.6%) to 94.037% when pulling 5d0673bbc7b8fc50653f21bad48aabe78e5ce6b1 on no_auroral_scaling into c2f41824a4e3fb5f0b6efe475b7534d152763881 on develop.
Description
There are times where scaling the data is not desired. This addresses this problem in the different
instrument
functions that had previously had scaling hard-coded in.Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Created new unit tests, ran functions with new functionality.
Test Configuration:
Checklist:
develop
(notmain
) branchChangelog.rst
, summarising the changesAUTHORS.rst