Fix decorator issues with 1.5.x branch

[freemansw1]

This PR fixes issues with the RC_v1.5.x branch caused by merging in #380.

• Have you followed our guidelines in CONTRIBUTING.md?
• Have you self-reviewed your code and corrected any misspellings?
• Have you written documentation that is easy to understand?
• Have you written descriptive commit messages?
• Have you added NumPy docstrings for newly added functions?
• Have you formatted your code using black?
• If you have introduced a new functionality, have you added adequate unit tests?
• Have all tests passed in your local clone?
• If you have introduced a new functionality, have you added an example notebook?
• Have you kept your pull request small and limited so that it is easy to review?
• Have the newest changes from this branch been merged?

[github-actions]

Linting results by Pylint:

Your code has been rated at 8.68/10 (previous run: 8.68/10, +0.00)
_{The linting score is an indicator that reflects how well your code version follows Pylint’s coding standards and quality metrics with respect to the RC_v1.5.x branch.
A decrease usually indicates your new code does not fully meet style guidelines or has potential errors.}

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 57.17%. Comparing base (df86e7f) to head (3bc47ca).
Report is 9 commits behind head on RC_v1.5.x.

Additional details and impacted files

@@              Coverage Diff              @@
##           RC_v1.5.x     #416      +/-   ##
=============================================
+ Coverage      57.00%   57.17%   +0.17%     
=============================================
  Files             20       20              
  Lines           3454     3482      +28     
=============================================
+ Hits            1969     1991      +22     
- Misses          1485     1491       +6     

Flag	Coverage Δ
unittests	57.17% <100.00%> (+0.17%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[fsenf]

Could you please provide a short statement why you are using parenthesis after decorator name? Do new style rules apply? Thanks!

[w-k-jones]

Could you please provide a short statement why you are using parenthesis after decorator name? Do new style rules apply? Thanks!

Sean's changes made in #380 allow us to provide keyword options to the decorators to change their behaviour. However, this requires the decorator to be called as a function even when no keywords are provided, hence the added parentheses here

[fsenf]

all is perfect. Please go ahead and merge!