Fix processing cost calculator: the order of filter support

[stiepan]

Category:

Bug fix (non-breaking change which fixes an issue)

Description:

In the setup, the resize operator estimates the cost of running the resize with different orders of the resampled axes. It uses output, input sizes and the size of filters used along particular axes. However, it seems that the filters support size is unnecesarily reversed when passed to the best order calculator, which may result in sub-optimal performance in some cases.

Additional information:

Affected modules and functionalities:

The performance of the dali resize operator, esp. for downsampling with antialias on and filters with big radious.

Key points relevant for the review:

While the shapes and arguments come in a (D)HW (limited to spatial dims) layout, the SampleDesc keeps the extents in the WH(D) order. The filters are setup in the SetFilters method called a few lines above the fix. They are kept in the SampleDesc in the WH(D) order, same as the computed input (roi) and output shapes here.

Tests:

• Existing tests apply
• New tests added
  • Python tests
  • GTests
  • Benchmark
  • Other
• N/A

Checklist

Documentation

• Existing documentation applies
• Documentation updated
  • Docstring
  • Doxygen
  • RST
  • Jupyter
  • Other
• N/A

DALI team only

Requirements

• Implements new requirements
• Affects existing requirements
• N/A

REQ IDs: N/A

JIRA TASK: N/A

[stiepan]

!build

[dali-automaton]

CI MESSAGE: [9450865]: BUILD STARTED

[dali-automaton]

CI MESSAGE: [9450865]: BUILD FAILED

[dali-automaton]

CI MESSAGE: [9450865]: BUILD PASSED