Ask Your Question

Revision history [back]

need collaborative effort

i want to see collaborative power of forum users.

i think documentation needs some corrections and make up like cv::merge ( related issue : 5111 )

we can do some corrections collaboratively.

I suggest a working model like the steps below.

  • declaration of the need ( as i did )
  • someone make an initial PR ( i think we can encourage unexperienced users to do initial PR )
  • we suggest additional corrections or ideas by comments on PR

i hope i will get response and we make contributions together. also waiting your opinions.

need collaborative effort

i want to see collaborative power of forum users.

i think documentation needs some corrections and make up like cv::merge ( related issue : 5111 )

we can do some corrections collaboratively.

I suggest a working model like the steps below.

  • declaration of the need ( as i did )
  • someone make an initial PR ( i think we can encourage unexperienced users to do initial PR )
  • we suggest additional corrections or ideas by comments on PR
  • at the and we will confirm PR image description by this way we will make merging job easier to core developer

i hope i will get response and we make contributions together. also waiting your opinions.

need collaborative effort

i want to see collaborative power of forum users.

i think documentation needs some corrections and make up like cv::merge ( related issue : 5111 )

we can do some corrections collaboratively.

I suggest a working model like the steps below.

  • declaration of the need ( as i did )
  • someone make an initial PR ( i think we can encourage unexperienced users to do initial PR )
  • we suggest additional corrections or ideas by comments on PR
  • at the and we will confirm the PR image descriptionimage description by this way we will make merging job easier to core developer

i hope i will get response and we make contributions together. also waiting your opinions.

need collaborative effort

i want to see collaborative power of forum users.

i think documentation needs some corrections and make up like cv::merge ( related issue : 5111 )

we can do some corrections collaboratively.

I suggest a working model like the steps below.

  • declaration of the need ( as i did )
  • someone make an initial PR ( i think we can encourage unexperienced inexperienced users to do initial PR )
  • we suggest additional corrections or ideas by comments on PR
  • at the and we will confirm the PR image description by this way we will make merging job easier to core developer

i hope i will get response and we make contributions together. also waiting your opinions.

need collaborative effort

i want to see collaborative power of forum users.

i think documentation needs some corrections and make up like cv::merge ( related issue : 5111 )

we can do some corrections collaboratively.

I suggest a working model like the steps below.

  • declaration of the need ( as i did )
  • someone make an initial PR ( i think we can encourage inexperienced users to do initial PR )
  • we suggest additional corrections or ideas by comments on PR
  • at the and we will confirm the PR image description by this way we will make merging job easier to core developer

i hope i will get response and we make contributions together. also waiting your opinions.

EDIT : I think my question needs a small explanation about the correction need of the function cv::merge.

for example i made bold where i think to be corrected: ( but i am sure there is more)

Creates one multi-channel array out of several single-channel ones.

The function merge merges several arrays to make a single multi-channel array. That is, each element of the output array will be a concatenation of the elements of the input arrays, where elements of i-th input array are treated as mv[i].channels()-element vectors

The function cv::split does the reverse operation. If you need to shuffle channels in some other advanced way, use cv::mixChannels

need collaborative effort

i want to see collaborative power of forum users.

i think documentation needs some corrections and make up like cv::merge ( related issue : 5111 )

we can do some corrections collaboratively.

I suggest a working model like the steps below.

  • declaration of the need ( as i did )
  • someone make an initial PR ( i think we can encourage inexperienced users to do initial PR )
  • we suggest additional corrections or ideas by comments on PR
  • at the and we will confirm the PR image description by this way we will make merging job easier to core developer

i hope i will get response and we make contributions together. also waiting your opinions.

EDIT : I think my question needs a small explanation about the correction need of the function cv::merge.

for example i made bold where i think to be corrected: ( but i am sure there is more)

Creates one multi-channel array out of several single-channel ones.

The function merge merges several arrays to make a single multi-channel array. That is, each element of the output array will be a concatenation of the elements of the input arrays, where elements of i-th input array are treated as mv[i].channels()-element vectors

The function cv::split does the reverse operation. If you need to shuffle channels in some other advanced way, use cv::mixChannels

Parameters

mv input array of matrices to be merged; all the matrices in mv must have the same size and the same depth.

count number of input matrices when mv is a plain C array; it must be greater than zero.

dst output array of the same size and the same depth as mv[0]; The number of channels will be the total number of channels in the matrix array. ( i think The number of channels will be given value by count)

need collaborative effort

i want to see collaborative power of forum users.

i think documentation needs some corrections and make up like cv::merge ( related issue : 5111 )

we can do some corrections collaboratively.

I suggest a working model like the steps below.

  • declaration of the need ( as i did )
  • someone make an initial PR ( i think we can encourage inexperienced users to do initial PR )
  • we suggest additional corrections or ideas by comments on PR
  • at the and we will confirm the PR image description by this way we will make merging job easier to core developer

i hope i will get response and we make contributions together. also waiting your opinions.

EDIT : I think my question needs a small explanation about the correction need of the function cv::merge.

for example i made bold where i think to it might be corrected:

Creates one multi-channel array out of several single-channel ones.

The function merge merges several arrays to make a single multi-channel array. That is, each element of the output array will be a concatenation of the elements of the input arrays, where elements of i-th input array are treated as mv[i].channels()-element vectors

The function cv::split does the reverse operation. If you need to shuffle channels in some other advanced way, use cv::mixChannels

Parameters

mv input array of matrices to be merged; all the matrices in mv must have the same size and the same depth.

count number of input matrices when mv is a plain C array; it must be greater than zero.

dst output array of the same size and the same depth as mv[0]; The number of channels will be the total number of channels in the matrix array. ( i think The number of channels will be given value by count)

need collaborative effort

i want to see collaborative power of forum users.

i think documentation needs some corrections and make up like cv::merge ( related issue : 5111 )

we can do some corrections collaboratively.

I suggest a working model like the steps below.

  • declaration of the need ( as i did )
  • someone make an initial PR ( i think we can encourage inexperienced users to do initial PR )
  • we suggest additional corrections or ideas by comments on PR
  • at the and we will confirm the PR image description by this way we will make merging job easier to core developer

i hope i will get response and we make contributions together. also waiting your opinions.

EDIT : I think my question needs a small explanation about the correction need of the function cv::merge.

for example i made bold where i think it might be corrected:

Creates one multi-channel array out of several single-channel ones.

The function merge merges several arrays to make a single multi-channel array. That is, each element of the output array will be a concatenation of the elements of the input arrays, where elements of i-th input array are treated as mv[i].channels()-element vectors

The function cv::split does the reverse operation. If you need to shuffle channels in some other advanced way, use cv::mixChannels

Parameters

mv input array of matrices to be merged; all the matrices in mv must have the same size and the same depth.

count number of input matrices when mv is a plain C array; it must be greater than zero.

dst output array of the same size and the same depth as mv[0]; The number of channels will be the total number of channels in the matrix array. ( i think The number of channels will be given value by count)

here you can find the header file to be corrected

need collaborative effort

i want to see collaborative power of forum users.

i think documentation needs some corrections and make up like cv::merge ( related issue : 5111 )

we can do some corrections collaboratively.

I suggest a working model like the steps below.

  • declaration of the need ( as i did )
  • someone make an initial PR ( i think we can encourage inexperienced users to do initial PR )
  • we suggest additional corrections or ideas by comments on PR
  • at the and we will confirm the PR image description by this way we will make merging job easier to core developer

i hope i will get response and we make contributions together. also waiting your opinions.

EDIT : I think my question needs a small explanation about the correction need of the function cv::merge.

for example i made bold where i think it might be corrected:

Creates one multi-channel array out of several single-channel ones.

The function merge merges several arrays to make a single multi-channel array. That is, each element of the output array will be a concatenation of the elements of the input arrays, where elements of i-th input array are treated as mv[i].channels()-element vectors

The function cv::split does the reverse operation. If you need to shuffle channels in some other advanced way, use cv::mixChannels

Parameters

mv input array of matrices to be merged; all the matrices in mv must have the same size and the same depth.

count number of input matrices when mv is a plain C array; it must be greater than zero.

dst output array of the same size and the same depth as mv[0]; The number of channels will be the total number of channels in the matrix array. ( i think The number of channels will be given value by count)

here you can find the header file to be corrected