<html><head></head><body><div>Hi everybody. <img src="cid:1495224770.19360.2.camel@yahoo.es" alt=":-D"></div><div><br></div><div>Well, i think here we are starting the "The Hopeless Machine Learning Team". <img src="cid:1495224770.19360.2.camel@yahoo.es" alt=":-D"> </div><div><br></div><div><b>It's a good news for all the community, we should celebrate. <img src="cid:1495224770.19360.2.camel@yahoo.es" alt=":-D"></b></div><div><b><br></b></div>I'm working on a series of studies to determine if SciLAB can meet the requirements for my job.<br><div>Unfortunately, this machine learning toolbox not fits in the requirements, so I can not help in a long way. However, perhaps I can do something, I will keep myself open. <img src="cid:1495224770.19360.2.camel@yahoo.es" alt=":-D"></div><div><b><br></b></div><div><b>A machine learning toolbox is very important, we need to do it. <img src="cid:1495224770.19360.1.camel@yahoo.es" alt=":-O"> </b></div><div><b><br></b></div><div>-- Amanda Osvaldo</div><div><b><br></b></div><div><br></div><div>On Fri, 2017-05-19 at 11:37 -0300, Caio Souza wrote:</div><blockquote type="cite"><div dir="ltr">Hi,<div><br></div><div>Thanks for input<br><div><br></div><div>We have both possibilities, from scratch or/and using a library, still an open topic.</div><div>For now either way we chose, I think we would be limited to a few GB's of data, but we can extend it later if we start with this idea in mind. IMHO making anything to work with hundreds of GB's of data could be alone another project :)</div><div><br></div><div>My idea is to have a scilab interface which is how it's organized and can be used/called, and how it works in the backend could be scilab code, C/C++ code or calling other libraries.</div><div><br></div><div><br></div><div><blockquote type="cite">Somebody have some idea how to handle this project in a software engineering perspective?<br>Just to ensure the tests and code quality.<br></blockquote></div><div><br></div><div>1) Define our interface (most important thing), here I think who uses most the feature should chose.</div><div>2) Start with simple algorithms, but working 100% inside our interface.</div><div>3) Demos, tests and documentation for everything</div><div>4) Repeat 2 and 3.</div><div><br></div><div>After doing 2 and 3 for the first time we will be able to advance faster.</div><div><br></div><div><br></div><div class="gmail_extra"><div class="gmail_quote"><blockquote type="cite">
Then from the Scilab programmers point of view, if we were using the JIMS or PIMS, at the ends the Scilab codes would be very much looks like Python or Java style, unless we wrote another macros to wrap all these into Scilab style. <br></blockquote><div> </div><div>Not sure what would be more convenient to users, but I would prefer to wrap everything inside scilab to make a simpler interface.</div><div><br></div><div><br></div><blockquote type="cite">So far I think the C/C++ API might be the most "seamless" integrated into Scilab, which we could utilizing parts of the C/C++ libraries while others work in Scilab<br></blockquote><div><br></div><div>If we have our own interface, using C/C++, Python or Java could make difference only in performance, but all those lib have their core in C/C++, so I would choose simplicity for now.</div><div><br></div><div> </div><blockquote type="cite">
Finally as for the GPU usage concern, using libs could have solve this depending on the lib being used.<br></blockquote><div><br></div><div>I see GPU support being an option after we have something solid working already on CPU.</div><div><br></div><div><br></div><div><br></div><div>Best,</div><div>Caio SOUZA</div></div></div></div></div>
<pre>_______________________________________________
dev mailing list
<a href="mailto:dev@lists.scilab.org">dev@lists.scilab.org</a>
<a href="http://lists.scilab.org/mailman/listinfo/dev">http://lists.scilab.org/mailman/listinfo/dev</a>
</pre></blockquote></body></html>