<div dir="ltr">I had this same question myself. Others can correct me or add to, but I believe the idea is as follows... Arrows allow you to separate the implementation of a particular algorithm from the top-level code that uses it. Thus, you can have an OCV arrow that does image filtering or some other library implementing the particular algorithm. However, for some simpler process functionality, it isn't worth the overhead of defining a vital algorithm and dispatching to an arrow. For example, <b>ocv/image_viewer_process</b> just displays an image to the screen. Though conceivably, a process could start life as a library-specific implementation but then later be broken out into vital::algorithm and arrow if there is a desire to use different libraries for that functionality.<br><br><div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 13, 2017 at 10:43 AM, Matt Phillips <span dir="ltr"><<a href="mailto:matt.phillips@kitware.com" target="_blank">matt.phillips@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Tbh what is the rationale for having ocv *processes*? Obviously, ocv algos, and crop_chips is one (arrows/ocv/crop_chips.cxx). I would have thought that Sprokit would abstract away from which particular vision library is being used to perform some functionality. <span class="gmail-HOEnZb"><font color="#888888"><div><br></div><div>Matt</div></font></span></div><div class="gmail-HOEnZb"><div class="gmail-h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 13, 2017 at 10:33 AM, Matt Brown <span dir="ltr"><<a href="mailto:matt.brown@kitware.com" target="_blank">matt.brown@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div>I think for now, I will just make my process an OCV process, even though it is only using OCV for the cropping aspect. Once we settle on a view/crop utility and it makes it way into master, which I think would be great, then I will move it back to a core process.<br><br></div>Thanks,<br></div>Matt<br></div><div class="gmail-m_-5606786602795338938HOEnZb"><div class="gmail-m_-5606786602795338938h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 13, 2017 at 9:27 AM, Matt Phillips <span dir="ltr"><<a href="mailto:matt.phillips@kitware.com" target="_blank">matt.phillips@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi, I've signed up for kwiver-users now, but as for this post which Aaron B. kindly forwarded, I'd say this sounds like Jon C.'s crop_chips/crop_detector functionality. I've written an example pipeline for it, and it all lives in Jon's repo atm afaik.</div><div><br></div><div><a href="https://github.com/Erotemic/kwiver/tree/dev/CropChipsPipeline" target="_blank">https://github.com/Erotemic/kw<wbr>iver/tree/dev/CropChipsPipelin<wbr>e</a><br></div><div><br></div><div>Matt</div><div><br></div><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Aaron Bray</b> <span dir="ltr"><<a href="mailto:aaron.bray@kitware.com" target="_blank">aaron.bray@kitware.com</a>></span><br>Date: Mon, Nov 13, 2017 at 9:15 AM<br>Subject: Fwd: [Kwiver-users] Window view of Vital image<br>To: Matt Phillips <<a href="mailto:matt.phillips@kitware.com" target="_blank">matt.phillips@kitware.com</a>><br><br><br><div dir="ltr"><div>Are you a member of kwiver-users?</div><div>If not, you should sign up here : <a href="https://public.kitware.com/mailman/listinfo/kwiver-announce" target="_blank">https://public.kitware.com/m<wbr>ailman/listinfo/kwiver-announc<wbr>e</a></div><div><br></div><div>This thread sounds like your guacamole arrow...</div><div><div class="gmail-m_-5606786602795338938m_4829002309342039542h5"><div><br></div><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Linus Sherrill</b> <span dir="ltr"><<a href="mailto:linus.sherrill@kitware.com" target="_blank">linus.sherrill@kitware.com</a>></span><br>Date: Mon, Nov 13, 2017 at 9:08 AM<br>Subject: Re: [Kwiver-users] Window view of Vital image<br>To: Matt Brown <<a href="mailto:matt.brown@kitware.com" target="_blank">matt.brown@kitware.com</a>><br>Cc: <a href="mailto:kwiver-users@public.kitware.com" target="_blank">kwiver-users@public.kitware.co<wbr>m</a><br><br><br><div dir="ltr">There has been some discussion about adding functionality to clip rectangles (bounding boxes) from images to yield another image (or image_container). If somebody is working on this, speak up :-)<div>In any event, this is best implemented as an operator on an image(or image_container) and not a member.</div><div><br></div><div>Thanks,</div><div>-Linus</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="gmail-m_-5606786602795338938m_4829002309342039542m_1117801992019261108gmail-m_-5132284457405075822gmail-h5">On Sun, Nov 12, 2017 at 9:16 PM, Matt Brown <span dir="ltr"><<a href="mailto:matt.brown@kitware.com" target="_blank">matt.brown@kitware.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="gmail-m_-5606786602795338938m_4829002309342039542m_1117801992019261108gmail-m_-5132284457405075822gmail-h5"><div dir="ltr"><div><div>Is there an easy way to create a view into a window of a Vital image akin to what you can do in OpenCV by applying a cv::Rect to a cv::Mat? I couldn't find any examples in the repo of this being done. I was looking into the 'image_of' class, and I could use that with the appropriate step sizes. But, it would be ideal if a vital::image or even better vital::image_container had this functionality built in.<br><br></div>Thanks,<br></div>Matt<br></div>
<br></div></div>______________________________<wbr>_________________<br>
Kwiver-users mailing list<br>
<a href="mailto:Kwiver-users@public.kitware.com" target="_blank">Kwiver-users@public.kitware.co<wbr>m</a><br>
<a href="http://public.kitware.com/mailman/listinfo/kwiver-users" rel="noreferrer" target="_blank">http://public.kitware.com/mail<wbr>man/listinfo/kwiver-users</a><br>
<br></blockquote></div><span class="gmail-m_-5606786602795338938m_4829002309342039542m_1117801992019261108gmail-HOEnZb"><font color="#888888"><span class="gmail-m_-5606786602795338938m_4829002309342039542m_1117801992019261108gmail-m_-5132284457405075822gmail-HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div class="gmail-m_-5606786602795338938m_4829002309342039542m_1117801992019261108gmail-m_-5132284457405075822gmail-m_-3252641207093460525gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><font color="#888888"><b>Linus Sherrill - </b></font><font color="#888888">Staff R&D Engineer<br></font><font color="#888888">Kitware, Inc.<br><a href="https://maps.google.com/?q=28+Corporate+Drive+Clifton+Park,+NY+12065&entry=gmail&source=g" target="_blank">28 Corporate Drive</a><br><a href="https://maps.google.com/?q=28+Corporate+Drive+Clifton+Park,+NY+12065&entry=gmail&source=g" target="_blank">Clifton Park, NY 12065</a>-8662<br>E: <a href="mailto:linus.sherrill@kitware.com" target="_blank">linus.sherrill@kitware.com</a><br>P: <a href="tel:(518)%20881-4400" value="+15188814400" target="_blank">518.881.4400</a><br></font></div></div></div></div></div>
</font></span></font></span></div><span class="gmail-m_-5606786602795338938m_4829002309342039542m_1117801992019261108gmail-HOEnZb"><font color="#888888">
<br>______________________________<wbr>_________________<br>
Kwiver-users mailing list<br>
<a href="mailto:Kwiver-users@public.kitware.com" target="_blank">Kwiver-users@public.kitware.co<wbr>m</a><br>
<a href="http://public.kitware.com/mailman/listinfo/kwiver-users" rel="noreferrer" target="_blank">http://public.kitware.com/mail<wbr>man/listinfo/kwiver-users</a><br>
<br></font></span></div><br></div></div></div>
</div><br></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div></div></div>