matplotlib-cpp VS vnlog

The library (matplotlibcpp) on GitHub

I am aware of this excellent matplotlib C++ wrapper. Are there any C/C++ tools similar to scipy.signals? I currently use the python tools to generate header files and can translate algorithms to C++, but I would like a more direct well to develop in C++.

I want to plot graphs in C++ with matplotlib-cpp (https://github.com/lava/matplotlib-cpp). But I dont know how to install it in Visual Studio. I followed the instruction on website. But I got Errors like 'Python.h not found' ...

If you want it to be as simple as possible I’d recommend this matplotlib wrapper

THere is also this one, which is header only, so it's much simpler to install https://github.com/lava/matplotlib-cpp

There's actually a wrapper for matplotlib for cpp https://github.com/lava/matplotlib-cpp, so it's more or less doing exactly what you asked. Cpp doing all the heavy lifting, then matplotlib making the graphs.

There's matplotlib-cpp if you want to use the same kind of interface as with python.

or https://github.com/lava/matplotlib-cpp

well I usually use Python's matplotlib to do the plottings. It was the easiest I think. Before that, I attempted this library, which is a somewhat wrapper for C++: https://github.com/lava/matplotlib-cpp

Since you mentioned it, there is a wrapper for matplotlib: https://github.com/lava/matplotlib-cpp

For simple analyses (i.e. what most people do most of the time) doing this on the commandline gets you there faster. I use vnlog (https://github.com/dkogan/vnlog/). By the time you fired up your editor to write your Python code, I already have analyses and plots ready.

Alternative very appropriate for some uses cases: `vnl-join` from the vnlog toolkit (https://github.com/dkogan/vnlog). Uses the `join` tool from coreutils (works well, has been around forever), and `vnlog` for nice column labelling

There's also https://github.com/dkogan/vnlog/ which is a wrapper around the existing coreutils, so all the options work, and there's nothing to learn

And to improve the ergonomics, the vnlog wrappers are available to operate on field names, while retaining the internals of the core tools:

  https://github.com/dkogan/vnlog/

I sorta, kinda agree. Tools written in AWK (and friends) are indeed somewhat unmaintainable, but they're really close to being just right for a LOT of applications. The vnlog toolkit (https://github.com/dkogan/vnlog) adds just a little bit of syntactic sugar to the usual commandline tools to make processing scripts robust and easy to read and write. This was not my intent initially, but I now do most of my data processing with the shell and vnl-wrapped awk (and sort and join, ...) It's really nice. If you write stuff in awk, you should check it out. (Disclaimer: I'm the author)