@phcerdan I just posted a possible implementation of ConstantBoundaryImageNeighborhoodPixelAccessPolicy, which has the same functionality of the policy classes we have been discussing here in July… but this one does allow specifying the constant value at run-time: WIP: Added policy for constant NeighborhoodRange values outside image
While I think it’s fully functional already, I just marked it WIP, because I don’t know if it has priority for the release of ITK 5.0. What do you think?
Eventually it could replace existing use cases of the old itk::ConstantBoundaryCondition, and possibly yield a performance improvement…