You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Where videoSource is a multi-port output, convertColor and resize are all 1-1 input-to-output setups that are clonable and videoSink is a parallel_k fan-in stage.
For some reason, when I run my application only videoSource, convertColor and videoSink are run in this configuration. If I use only convertColor or resize individually, they are each run but if I try to use any two together for the joined parallel kernel, only the first is run.
Am I using the incorrect syntax or missing something else?
The text was updated successfully, but these errors were encountered:
dkushner
changed the title
Skipping a single parallel kernel stage.
Only first of many parallel kernel stages is executed.
Jul 24, 2017
This is a bug....suspect it will be fixed in the dev branch, however, will add to queue for the mainline branch too. Is there any chance you could submit a test case for this one? Dropping code in the comment box or submitting a pull request to add the test case would be awesome.
I have a pipeline laid out something like this:
Where
videoSource
is a multi-port output,convertColor
andresize
are all 1-1 input-to-output setups that are clonable andvideoSink
is aparallel_k
fan-in stage.For some reason, when I run my application only
videoSource
,convertColor
andvideoSink
are run in this configuration. If I use onlyconvertColor
orresize
individually, they are each run but if I try to use any two together for the joined parallel kernel, only the first is run.Am I using the incorrect syntax or missing something else?
The text was updated successfully, but these errors were encountered: