I believe all the developers (not just image and vision) are
working on their topics for weeks, months or even years before the
release of a module to public. It is good that we have atoms
portal so that we could know who else working on the same fields
and exchange ideas from there.
As for the aim for the modules, I believe all the modules should
have the same ultimate aim: to make a good image processing and
computer vision tools for Scilab, and possibly, replace Matlab. :)
From my opinion, the crash of the function name are quite common,
for example, imshow in sip using scilab graphic, using tcl/tk in
sivp, using both in IPCV, and using OpenCV highgui in sciCV. It
depends on how the developers want it to be. For the moment, I
disable the atomsAutoload for both modules and load it manually
whenever I need to avoid this problem.
As for the combine effort, what I could say is everything is
possible with OpenSource. Someday, somehow, Scilab image
processing and computer vision shall be taking over Matlab for
On 25/4/2017 9:44 PM, Philipp Mühlmann wrote:
am I to wrong to ask if the aim for IPCV and sciCV is
Both toolboxes are quite welcome, but some confusion
might occur if both toolboxes are installed.
In fact, some functions are already named the same...e.g.:
imread in sciCV can have flags, in IPCV it can not.
...just to mention.
I am about to ask, if it wouldn't make sence to combine the
efforts, and create only one powerful toolbox enabling openCV
functionality to Scilab.
but...maybe there are good reasons for not doing so...