justinblaber / ncorr_2d_cpp Goto Github PK

I would like to be able to do DIC on in-memory images without having to write them to a file (they are not stored in a standard format). I'd be happy to implement the capability and submit a pull request.

Any suggestions on the approach?

One simple option would be to modify the Image2D class to handle both cases (filename, and Array2D, only one of which is valid at any given time.

Another option could be to make the Image2D class a superclass with subclasses for file input and array input.

A third option could be to make the existing Image2D class no longer "final" and make its methods virtual, so that a derived class could be externally defined. In this case the interface functions would need to become virtual methods (or thin layers over virtual methods) so that they will properly call the derived class's methods.

Thoughts?

I am coming at the following error. I am unable to get a fix for it. Kindly help. Thanks in advance.

`In file included from /home/beno/.local/src/ncorr_2D_cpp/build/../include/ncorr.h:12,

             from /home/beno/.local/src/ncorr_2D_cpp/src/ncorr.cpp:8:

/home/beno/.local/src/ncorr_2D_cpp/build/../include/Image2D.h:36:21: error: friend declaration of ‘void imshow(const ncorr::Image2D&, ncorr::Image2D::difference_type)’ specifies default arguments and isn’t a definition [-fpermissive]
36 | friend void imshow(const Image2D&, difference_type delay = -1);
| ^~~~~~

`

While manually/automatically installing mex cpp copmpiler, an error stating "Cannot open include file: 'ammintrin.h': No such file or directory" might pop up.
Then the ammintrin.h file could be downloaded from the website given below and it should be further placed in the directory stated in the error.
https://in.mathworks.com/matlabcentral/answers/90383-fix-problem-when-mex-cpp-file

I am trying to create a pure C++ version of a DIC application using ncorr coming from one running on Matlab. One parameter of the DIC analysis that does not seem to appear in the C++ version is the spacing between subregions.

How does it work in the C++ version? Does it have a default value? Or is it present under another name / type of configuration?