From matt.brown at kitware.com Thu Aug 24 14:16:56 2017 From: matt.brown at kitware.com (Matt Brown) Date: Thu, 24 Aug 2017 14:16:56 -0400 Subject: [Kwiver-users] Fwd: KWIVER FAQ In-Reply-To: References: Message-ID: I am a new user of Sprokit, and as such, I have been asking quite a few questions. I started a page on the KWIVER Github to start documenting these Q/A. I think this can be particularly useful in terms of indicating what is confusing to a completely new user and indicating areas where the documentation or the architecture may be inadequate. Please feel free to contribute. https://github.com/Kitware/kwiver/wiki/Frequently-Asked-Questions -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt.brown at kitware.com Thu Aug 24 20:41:38 2017 From: matt.brown at kitware.com (Matt Brown) Date: Thu, 24 Aug 2017 20:41:38 -0400 Subject: [Kwiver-users] KWIVER FAQ In-Reply-To: References: Message-ID: Per Matt Leotta's advice, I would like to use the kwiver-users mailing list for non-project-specific KWIVER discussions, but it is unclear to me whether all interested Kitwareans are subscribers there. So, if you are interested in KWIVER discussions, please subscribe: http://public.kitware.com/mailman/listinfo/kwiver-users On Thu, Aug 24, 2017 at 11:30 AM, Matt Brown wrote: > I am a new user of Sprokit, and as such, I have been asking quite a few > questions. I started a page on the KWIVER Github to start documenting these > Q/A. I think this can be particularly useful in terms of indicating what is > confusing to a completely new user and indicating areas where the > documentation or the architecture may be inadequate. Please feel free to > contribute. > > https://github.com/Kitware/kwiver/wiki/Frequently-Asked-Questions > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt.brown at kitware.com Thu Aug 24 21:45:16 2017 From: matt.brown at kitware.com (Matt Brown) Date: Thu, 24 Aug 2017 21:45:16 -0400 Subject: [Kwiver-users] KWIVER FAQ In-Reply-To: References: Message-ID: Sorry about that. Meant to send to vision-developers at kitware.com. On Thu, Aug 24, 2017 at 8:41 PM, Matt Brown wrote: > Per Matt Leotta's advice, I would like to use the kwiver-users mailing > list for non-project-specific KWIVER discussions, but it is unclear to me > whether all interested Kitwareans are subscribers there. So, if you are > interested in KWIVER discussions, please subscribe: > http://public.kitware.com/mailman/listinfo/kwiver-users > > On Thu, Aug 24, 2017 at 11:30 AM, Matt Brown > wrote: > >> I am a new user of Sprokit, and as such, I have been asking quite a few >> questions. I started a page on the KWIVER Github to start documenting these >> Q/A. I think this can be particularly useful in terms of indicating what is >> confusing to a completely new user and indicating areas where the >> documentation or the architecture may be inadequate. Please feel free to >> contribute. >> >> https://github.com/Kitware/kwiver/wiki/Frequently-Asked-Questions >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt.brown at kitware.com Fri Aug 25 12:21:54 2017 From: matt.brown at kitware.com (Matt Brown) Date: Fri, 25 Aug 2017 12:21:54 -0400 Subject: [Kwiver-users] Pipeline timing information Message-ID: I am using a Sprokit pipeline for a near-real-time application, and it is important to understand the latencies of the different processes. Is there any existing or in the works to provide pipeline profiling? I am currently just adding LOG_DEBUG messages with timing information. -------------- next part -------------- An HTML attachment was scrubbed... URL: From linus.sherrill at kitware.com Mon Aug 28 12:57:11 2017 From: linus.sherrill at kitware.com (Linus Sherrill) Date: Mon, 28 Aug 2017 12:57:11 -0400 Subject: [Kwiver-users] Pipeline timing information In-Reply-To: References: Message-ID: There is some emerging technology (read somewhat under used and under tested) that can instrument processes. The support is in current master branch, but there is a branch where I started adding the instrumentation calls. branch: dev/add-process-instrumentation Unfortunately the instrumentation is invasive and requires modification of the processes but the overhead is minimal if instrumentation is not enabled. Once the instrumentation calls are added, it can be activated on a per process basis via the process config in the pipe file. process my_process :: my_process_type _instrumentation:type = logger The above will enable the logger style instrumentation which generates a log message for each start_*_processing() and stop_*_processing() call. There is another one that uses RightTrack to generate execution time-lines for the processes, but that approach requires building an external package and other integration issues. This one has not been used is a while. On Fri, Aug 25, 2017 at 12:21 PM, Matt Brown wrote: > I am using a Sprokit pipeline for a near-real-time application, and it is > important to understand the latencies of the different processes. Is there > any existing or in the works to provide pipeline profiling? I am currently > just adding LOG_DEBUG messages with timing information. > > _______________________________________________ > Kwiver-users mailing list > Kwiver-users at public.kitware.com > http://public.kitware.com/mailman/listinfo/kwiver-users > > -- *Linus Sherrill - *Staff R&D Engineer Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065-8662 E: linus.sherrill at kitware.com P: 518.881.4400 -------------- next part -------------- An HTML attachment was scrubbed... URL: