Open malenov opened 12 months ago
Thank you, @malenov, for presenting the current issues with wmc_tool. We are looking forward to your contribution. The next ITU-T SG12 meeting will be around April next year; this gives us some time to prepare for the next revision of the STL.
So far all known problems and issues were fixed. Here's an excerpt of the changelog:
-f FRAME_PER_SECONDS
command-line option allowing the user to choose the number of frames per second (default is still 50.0)push_wmops()
was called twice when WMOPS_DETAILS
was activated#define WMC_TOOL_SKIP
is not paired with #undef WMC_TOOL_SKIP
The following new features (functionality) were added:
.csv
filemem_analysis.py
for graphical analysis and profiling of dynamic memory alloations based on the generated .csv
file The new version of the WMC tool is v1.5
@ludomal, shall I create a changelog.txt
file with the description of the above modifications or describe them in the README.MD
file?
I've just created the file HISTORY.md containing the history of modifications to the WMC tool.
Dear all,
during the development of the 3GPP IVAS codec a couple of issues and potential improvements were identified in the
wmc_tool
, for example:update_wmops()
.csv
fileExporting the detailed per-frame and per-block memory consumption to an external file allows for running external statistical analysis tools such as Python pandas.
I will provide an update of the
wmc_tool
addressing all the above issues.