Intel® Integrated Performance Primitives
Deliberate problems developing high-performance vision, signal, security, and storage applications.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
6814 Discussions

watershed for float images

tld
Beginner
‎01-03-2007 01:33 PM
656 Views
I noticed that watershed segmentation (SegmentWatershed) for 8bit unsigned images has been implemented in IPP5.2 beta...

Are there any plans for a 32bit float version?

Happy New Year
Thomas Lund Dideriksen
0 Kudos

Link Copied

3 Replies
Vladimir_Dudnik
Employee
‎01-11-2007 08:56 PM
656 Views

Hi Thomas,

you can submit it as feature request through Intel Premier Support

Regards,
Vladimir

0 Kudos
Copy link
Intel_C_Intel
Employee
‎01-12-2007 10:48 AM
656 Views

Hi, Thomas,

Could you answer a question: the current watershed segmentation in IPPis done for 8u images and 8u markers. It means that only 255 different objects can be segmented. If more, marker values for some objects will be same. It is OK if objects with the same marker value are not adjacent. Is it important to guarantee arbitrary number of marker values ie 16u type for markers?

Please submit a request to premier

Thanks,

Alexander

0 Kudos
Copy link
tld
Beginner
‎01-12-2007 02:20 PM
656 Views
Hi Alexander

I posted a feature request via intel premier support.

Concerning your question:
I would definately prefer 16u markers.

Regards
Thomas
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.