The patch size is currently found automatically by testing various input sizes and seeing which ones cause a memory error.
This seems to be time consuming and slows the development cycle.
Suggested steps:
- Profile how long it currently takes to find the patch size.
- If it is considerable (more than a couple of seconds or so) then provide patch dimensions as input arguments.
The patch size is currently found automatically by testing various input sizes and seeing which ones cause a memory error.
This seems to be time consuming and slows the development cycle.
Suggested steps: