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
The Performance Counter variables tracking the number of produced items (nproduced, avg_nproduced, and var_nproduced)
only account for the return value of the block's work function.
It doesn't account for situations where produce(port, num) is called inside of that work function.
This means that, in this case, the reported nproduced stat is incorrect.
In the most extreme case, where a block only advertises its produced items through calls to produce(), the perf counter stats stay at 0.
What happened?
The Performance Counter variables tracking the number of produced items (
nproduced
,avg_nproduced
, andvar_nproduced
)only account for the return value of the block's work function.
It doesn't account for situations where
produce(port, num)
is called inside of that work function.This means that, in this case, the reported nproduced stat is incorrect.
In the most extreme case, where a block only advertises its produced items through calls to
produce()
, the perf counter stats stay at 0.gnuradio/gnuradio-runtime/lib/block_detail.cc
Lines 303 to 306 in 58725d5
System Information
OS: Linux Mint 21.3
GR Installation Method: Conda
GNU Radio Version
3.10 (maint-3.10)
Specific Version
3.10.9.2
Steps to Reproduce the Problem
The issue can be seen from even a simple embedded python block.
Just replace the return value in the default work function by consume and produce calls:
And insert it in whatever flowgraph.
Running gr-ctrlport-monitor, you can see
nproduced
,avg_nproduced
, andvar_nproduced
at 0 for that block.Relevant log output
No response
The text was updated successfully, but these errors were encountered: