Hello Clément, Thanks for your answer. I think it clarifies the situation somehow. I still don't get your point of not open-sourcing it and maintaining it "for free". I think it's the other way round: if you open-source it, it might happen that some members of the community contribute to extend it and maintain it "for free". >From the info you gave me, scicv should be avoided by any one not being that >particular client of your group. Moreover, scicv is adding noise and confusion to the atoms library.
Antoine Le Lundi, Mars 09, 2020 15:29 CET, Clément David <[email protected]> a écrit: About the feature set, I suggest you take a look at SIVP which is much more complete and target a wider audience. The available functions are the documented ones and we might add more if customers requested more. Currently, this toolbox is used by some customers and we only mapped the feature requested by them to have an associated minimal OpenCV build. It targets customers and we will probably not open-source it as we don’t want to maintain it “for free”. Again if you want to co-develop, take a look at SIVP ; Chin Luh did a good job and it is open-source ! Regards, Clément From: users <[email protected]> On Behalf Of Antoine Monmayrant Sent: Monday, March 9, 2020 2:34 PM To: Users mailing list for Scilab <[email protected]> Subject: Re: [Scilab-users] ?==?utf-8?q? Which module to use for hassle-free image processing with scilab ? Hello Clément, Thanks for your answer. It's still not clear to me whether I should use scicv or not. First, many features are missing and it's not clear to me how I can implement or discover them (hough transforms for example). Is there a list of the opencv functions that you expose through swig and the one that are not implemented? Also, I'm a bit surprised by your statement: Note: the code is not open-source but SWIG for Scilab and OpenCV are! Why is it not open-source? Is this some transient situation due to the way the code was developped (like for a client)? Do you plan to make it open source in the near future? For many reasons and lots of lessons learned the hard way, I don't feel like investing my time on non open-source software... Antoine Le Lundi, Mars 09, 2020 10:52 CET, Clément David <[email protected]> a écrit: Hello Antoine, > - scicv: installs without any issue and as reported by Samuel ( > http://forge.scilab.org/index.php/p/scicv/issues/1944/ > http://forge.scilab.org/index.php/p/scicv/issues/1946/ ), overwrites 'write' > and > 'read' which breaks many native functions in scilab together with other useful > modules (ie uman). This is a blocking issue that has not been fixed in the > past 6 > months. Moreover, many opencv functions are not available and it is not clear > how to access them. About sciCV, the idea was to use SWIG [1] and OpenCV [2] as an easy to use (and simple to develop) toolbox for manipulating images and videos using Scilab scripts. Here we don't have Scilab scripts at all, just a bunch of SWIG rules to generate the Scilab C gateways from the OpenCV C API. We have a focus on keeping the data in the OpenCV world and "accessing" them from Scilab. The two reported bugs have been fixed in 0.5 (sorry I did not close them) and the latest 0.6 version is built for Scilab 6.1.0 after a customer request. Note: the code is not open-source but SWIG for Scilab and OpenCV are! -- Clément _______________________________________________ users mailing list [email protected] http://lists.scilab.org/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.scilab.org/mailman/listinfo/users
