Fix segmentation time pad test

[freemansw1]

Resolves #565 by removing the i_time line (which does not belong) from the feature detection call.

• 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?

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 64.86%. Comparing base (8639ece) to head (4c6cfa7).
⚠️ Report is 2 commits behind head on RC_v1.6.x.

Additional details and impacted files

@@            Coverage Diff             @@
##           RC_v1.6.x     #569   +/-   ##
==========================================
  Coverage      64.86%   64.86%           
==========================================
  Files             27       27           
  Lines           4047     4047           
==========================================
  Hits            2625     2625           
  Misses          1422     1422           

Flag	Coverage Δ
unittests	64.86% <ø> (ø)

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.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-actions]

Linting results by Pylint:

Your code has been rated at 8.36/10 (previous run: 8.36/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 main branch.
A decrease usually indicates your new code does not fully meet style guidelines or has potential errors.}

[fsenf]

correctly done, thanks

[fsenf]

@freemansw1 : please go ahead and merge