From contact at pierre-vuillemin.fr Fri May 5 15:59:04 2017 From: contact at pierre-vuillemin.fr (Pierre Vuillemin) Date: Fri, 05 May 2017 15:59:04 +0200 Subject: [Scilab-Dev] Trying to update help_from_sci Message-ID: Hi all, I am currently trying to update the routine "help_from_sci" so that it works both with head comments written with // and with /* ... */. I was wondering if there was a (quick) way to display the resulting xml file with the Scilab style to check whether the xml that has been built is right? Regards, Pierre From Clement.David at esi-group.com Wed May 10 12:13:12 2017 From: Clement.David at esi-group.com (=?utf-8?B?Q2zDqW1lbnQgRGF2aWQ=?=) Date: Wed, 10 May 2017 10:13:12 +0000 Subject: [Scilab-Dev] Trying to update help_from_sci In-Reply-To: References: Message-ID: <1494411191.6500.20.camel@esi-group.com> Hello Pierre, Currently the easiest way is to put the resulting xml file as an exemple of an empty toolbox and build/load this toolbox to check for the rendering. HTML files can also be used as an easy content to check using a standard web browser (eg. without loading the toolbox). See xmltoweb() to generate it. AFAIK Samuel usually commit updated help files using the pdf format produced by xmltopdf(). As this PDF backend is not the main one, I tend to prefer the HTML ones but PDF might be a good alternative. -- Cl?ment Le vendredi 05 mai 2017 ? 15:59 +0200, Pierre Vuillemin a ?crit?: > Hi all, > > I am currently trying to update the routine "help_from_sci" so that it? > works both with head comments written with // and with /* ... */. > > I was wondering if there was a (quick) way to display the resulting xml? > file with the Scilab style to check whether the xml that has been built? > is right? > > Regards, > > Pierre > _______________________________________________ > dev mailing list > dev at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/dev From sgougeon at free.fr Wed May 10 12:33:38 2017 From: sgougeon at free.fr (sgougeon at free.fr) Date: Wed, 10 May 2017 12:33:38 +0200 (CEST) Subject: [Scilab-Dev] Trying to update help_from_sci In-Reply-To: <1494411191.6500.20.camel@esi-group.com> Message-ID: <1682080502.3871446.1494412418793.JavaMail.root@zimbra75-e12.priv.proxad.net> Hello, >De: "Cl?ment David" > >Hello Pierre, > >Currently the easiest way is to put the resulting xml file as an exemple of an empty toolbox and >build/load this toolbox to check for the rendering. > >HTML files can also be used as an easy content to check using a standard web browser (eg. without >loading the toolbox). See xmltoweb() to generate it. > >AFAIK Samuel usually commit updated help files using the pdf format produced by xmltopdf(). As this >PDF backend is not the main one, I tend to prefer the HTML ones but PDF might be a good alternative. AFAIRemember, xmltopdf() has some issue, so i use now PDF Creator applied the HTML. To illustrate the whole page setting and rendering, PDF does not need to be zipped, whereas HTML needs it to include css dependencies etc. Anyway, the rendering of the HTML (zipped in the .jar) through the Scilab helpbrowser is limited wrt the true HTML as it appears in web browsers: Many attributes or style values are well built but are not rendered... But this is another thread. Regards Samuel From contact at pierre-vuillemin.fr Wed May 10 15:01:11 2017 From: contact at pierre-vuillemin.fr (Pierre Vuillemin) Date: Wed, 10 May 2017 15:01:11 +0200 Subject: [Scilab-Dev] Trying to update help_from_sci In-Reply-To: <1682080502.3871446.1494412418793.JavaMail.root@zimbra75-e12.priv.proxad.net> References: <1682080502.3871446.1494412418793.JavaMail.root@zimbra75-e12.priv.proxad.net> Message-ID: Thanks for the answers and the hints, I have finally managed to do what I wanted using xmltojar and add_help_chapter. The xml file generated with help_from_sci seems to have some quirk, is there a reference page concerning the xml that should be produced? The main reference I have found is this page [1] but I don't know if it is still up to date. Besides, I am thinking about extending the features of the routine so that is supports some flavour of markdown (or similar stuff like Matlab's publishing features [2]). Has there already been some reflection in that direction? Regards, Pierre Le 10.05.2017 12:33, sgougeon at free.fr a ?crit : > Hello, > >> De: "Cl?ment David" >> >> Hello Pierre, >> >> Currently the easiest way is to put the resulting xml file as an exemple of an empty toolbox and >> build/load this toolbox to check for the rendering. >> >> HTML files can also be used as an easy content to check using a standard web browser (eg. without >> loading the toolbox). See xmltoweb() to generate it. >> >> AFAIK Samuel usually commit updated help files using the pdf format produced by xmltopdf(). As this >> PDF backend is not the main one, I tend to prefer the HTML ones but PDF might be a good alternative. > > AFAIRemember, xmltopdf() has some issue, so i use now PDF Creator > applied the HTML. > To illustrate the whole page setting and rendering, PDF does not need > to be zipped, > whereas HTML needs it to include css dependencies etc. > > Anyway, the rendering of the HTML (zipped in the .jar) through the > Scilab helpbrowser > is limited wrt the true HTML as it appears in web browsers: Many > attributes or style > values are well built but are not rendered... But this is another thread. > > Regards > Samuel > > _______________________________________________ > dev mailing list > dev at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/dev Links: ------ [1] https://help.scilab.org/docs/6.0.0/fr_FR/man.html [2] https://fr.mathworks.com/help/matlab/matlab_prog/marking-up-matlab-comments-for-publishing.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From Clement.David at esi-group.com Thu May 11 09:22:50 2017 From: Clement.David at esi-group.com (=?utf-8?B?Q2zDqW1lbnQgRGF2aWQ=?=) Date: Thu, 11 May 2017 07:22:50 +0000 Subject: [Scilab-Dev] Trying to update help_from_sci In-Reply-To: References: <1682080502.3871446.1494412418793.JavaMail.root@zimbra75-e12.priv.proxad.net> Message-ID: <1494487368.6500.22.camel@esi-group.com> Hello Pierre, Great news ! The help_from_sci() feature is currently really useful for new comers and improving it might be a good idea. The XML syntax used is a subset of Docbook 5 ; the man help page contains some information but I usually use the main Docbook documentation. About Markdown support, it might be a good idea to support it ; currently the syntax is similar but not standardized. Thanks, -- Cl?ment Le mercredi 10 mai 2017 ? 15:01 +0200, Pierre Vuillemin a ?crit?: > Thanks for the answers and the hints, I have finally managed to do what I wanted using xmltojar > and add_help_chapter. > > The xml file generated with help_from_sci seems to have some quirk, is there a reference page > concerning the xml that should be produced? The main reference I have found is this page but I > don't know if it is still up to date. > > Besides, I am thinking about extending the features of the routine so that is supports some > flavour of markdown (or similar stuff like Matlab's publishing features). > Has there already been some reflection in that direction? > ? > Regards, > ? > Pierre > > Le 10.05.2017 12:33, sgougeon at free.fr a ?crit?:? > > Hello, > > > > > De: "Cl?ment David" > > > > > > Hello Pierre, > > > > > > Currently the easiest way is to put the resulting xml file as an exemple of an empty toolbox > > > and > > > build/load this toolbox to check for the rendering. > > > > > > HTML files can also be used as an easy content to check using a standard web browser (eg. > > > without > > > loading the toolbox). See xmltoweb() to generate it. > > > > > > AFAIK Samuel usually commit updated help files using the pdf format produced by xmltopdf(). As > > > this > > > PDF backend is not the main one, I tend to prefer the HTML ones but PDF might be a good > > > alternative. > > ? > > AFAIRemember, xmltopdf() has some issue, so i use now PDF Creator > > applied the HTML. > > To illustrate the whole page setting and rendering, PDF does not need > > to be zipped, > > whereas HTML needs it to include css dependencies etc. > > > > Anyway, the rendering of the HTML (zipped in the .jar) through the > > Scilab helpbrowser > > is limited wrt the true HTML as it appears in web browsers: Many > > attributes or style > > values are well built but are not rendered... But this is another thread. > > > > Regards > > Samuel > > > > > > _______________________________________________ > > dev mailing list > > dev at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/dev > > _______________________________________________ > dev mailing list > dev at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/dev From caioc2bolado at gmail.com Thu May 18 18:48:45 2017 From: caioc2bolado at gmail.com (Caio Souza) Date: Thu, 18 May 2017 13:48:45 -0300 Subject: [Scilab-Dev] Machine Learning Toolbox In-Reply-To: References: <1493334215.25207.1.camel@yahoo.es> Message-ID: Hi, Yann Debray, I think it is great. Amanda Osvaldo, My first thought is about simplicity and organization, I totaly agree the less effort needed to use it the better. Besides I citing tensorflow as example, my idea is not to bring new data structures, but follow their organization. We would pass the data and a model(function) and let the scilab work. Writing it from scratch we have the freedom to make it the way we want, ofcourse the performance wouldnt match with the best libraries out there. In the other hand using a library we could have much more performance, but some restrictions in the organization and simplicity. I'm open to any approach, because I'm a bit suspect to speak about what the users want/need. :) On Thu, May 18, 2017 at 1:01 PM, Yann Debray wrote: > Dear Caio, Dhruv and Amanda, > > > > I would like to include my colleague Philippe Saad? to the exchanges on > Machine Learning for Scilab. > > He is an experienced mathematician working with us at ESI Group, and has > an interesting vision on the subject. > > He will be scientific advisor and mentor for a joint internship on Machine > learning starting mid june. > > > > @Philippe Saad? (ESI INENDI) : Could you > maybe share with us your view on the subject? > > > > We can keep this exchange public if it is alright with you all, since I > believe our success on the subject will depend on our capacity to > centralize and merge our community efforts. > > You can all collaborate on the project on our forge: > > http://forge.scilab.org/index.php/p/machine-learning-toolbox/ > > > > Yours > > Yann @ Scilab > > > > *De : *Amanda Osvaldo > *Date : *vendredi 28 avril 2017 ? 01:03 > *? : *List dedicated to the development of Scilab , > Yann Debray , Dhruv Khattar < > dhruvk1996 at gmail.com> > *Objet : *Re: [Scilab-Dev] Machine Learning Toolbox > > > > Hi Caio, sorry for the late. > > > > *I think we should ask ourselves what SciLAB's focus and what audience > are.* > > *I feel a lack of knowing what users of Scilab seek.* > > > > Me, for example, I want to do everything from protyping to running the > script on hundreds of Intel Xeon servers with the least possible effort. > > Even with less effort than it would have if the script were built in > Python. > > > > I am sure that new data structures will expand the use of SciLAB. > > > > But what advantage will this bring to users? > > Python, as example, have already optimized data structures and libraries. > > > > -- Amanda Osvaldo > > > > > > On Wed, 2017-04-26 at 14:32 -0300, Caio Souza wrote: > > Hi, > > > > > > I have been thinking about the usability of the toolbox and independent of > which algorithms we are going to have, would be interesting to have some > simplified structure (like TensorFlow). > > > > Despite it being a lot of work to have such structure, (data, model, cost > function, minimizer), it would make the toolbox easy to use and extend, > having minimum impact to the usability. > > > > IMHO, this is something that should be defined before any coding starts, > and also well explained to the student. > > > > I would like to hear from you what do you think, so we can start a > discussion. > > > > > > Best, > > Caio SOUZA > > _______________________________________________ > > dev mailing list > > dev at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lambdasoftware at yahoo.es Thu May 18 21:50:55 2017 From: lambdasoftware at yahoo.es (Amanda Osvaldo) Date: Thu, 18 May 2017 16:50:55 -0300 Subject: [Scilab-Dev] Machine Learning Toolbox In-Reply-To: References: <1493334215.25207.1.camel@yahoo.es> Message-ID: <1495137055.8877.1.camel@yahoo.es> Hi everybody, can I made some questions ? First, at all, I really agree that SciLab needs a Machine Learning toolbox. However, I'm pretty critical about Scilab in your limitations.I see very potential in the software but require a reform in your infrastructure. So, my questions. How large are we talking about the training dataset in scilab ? Even with Tensorflow compatibility if you need to put all the dataset into the RAM I fear the toolbox utility will be very limited. In another words: The toolbox will can handle a 250GB dataset or just a few GBs from a desktop ? Have I read right ? We are talking about to integrate Scilab and tensorflow or scikit-learn ? I think it's a good idea, I just whant to know if I'm interpreting right. Somebody have some idea how to handle this project in a software engineering perspective? Just to ensure the tests and code quality. -- Amanda Osvaldo On Thu, 2017-05-18 at 16:01 +0000, Yann Debray wrote: > Dear Caio, Dhruv and Amanda, > ? > I would like to include my colleague Philippe Saad? to the exchanges > on Machine Learning for Scilab. > He is an experienced mathematician working with us at ESI Group, and > has an interesting vision on the subject. > He will be scientific advisor and mentor for a joint internship on > Machine learning starting mid june. > ? > @Philippe > ?Saad??? (ESI INENDI): Could you maybe share with us your view on the > subject? ? > ? > We can keep this exchange public if it is alright with you all, since > I believe our success on the subject will depend on our capacity to > centralize > ?and merge our community efforts. > You can all collaborate on the project on our forge: > http://forge.scilab.org/index.php/p/machine-learning-toolbox/ > ? > Yours > Yann @ Scilab > ? > > De?:? > Amanda Osvaldo > > Date?: vendredi 28 avril 2017 ? 01:03 > > ??: List dedicated to the development of Scilab >, Yann Debray , Dhruv Khattar @gmail.com> > > Objet?: Re: [Scilab-Dev] Machine Learning Toolbox > > > ? > > > Hi Caio, sorry for the late. > > > ? > > > I think we should ask ourselves what SciLAB's focus and?what audience > are. > > > I feel a lack of knowing what users of Scilab seek. > > > ? > > > Me, for example, I want to do everything from protyping to running > the script on hundreds of Intel Xeon servers with the least possible > effort. > > > Even with less effort than it would have if the script were built in > Python. > > > ? > > > I am sure that new data structures will expand the use of SciLAB. > > > ? > > > But what advantage will this bring to users? > > > Python, as example, have already optimized data structures and > libraries. > > > ? > > > -- Amanda Osvaldo > > > ? > > > ? > > > On Wed, 2017-04-26 at 14:32 -0300, Caio Souza wrote: > > > > Hi,? > > ? > > > ? > > > I have been thinking about the usability of the toolbox and > independent of which algorithms we are going to have, would be > interesting to have some simplified structure (like TensorFlow). > > > ? > > > Despite it being a lot of work to have such structure, (data, model, > cost function, minimizer), it would make the toolbox easy to use and > extend, having minimum impact to the usability. > > > ? > > > IMHO, this is something that should be defined before any coding > starts, and also well explained to the student. > > > ? > > > I would like to hear from you what do you think, so we can start a > discussion. > > > ? > > > ? > > > Best, > > > Caio SOUZA > > > _______________________________________________ > dev mailing list > dev at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/dev > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dhruv at khattarindia.com Fri May 19 08:03:38 2017 From: dhruv at khattarindia.com (Dhruv Khattar) Date: Thu, 18 May 2017 23:03:38 -0700 (MST) Subject: [Scilab-Dev] Machine Learning Toolbox In-Reply-To: References: <1493334215.25207.1.camel@yahoo.es> Message-ID: <1495173818076-4036421.post@n3.nabble.com> Hi all, Caio, are you talking about something like an API to call tensorflow functions in Scilab? I think it would be better if we implement it from scratch as we can make functions which will be easier to use for our users. We can document it as well. Dhruv -- View this message in context: http://mailinglists.scilab.org/Machine-Learning-Toolbox-tp4036274p4036421.html Sent from the Scilab developers - Mailing Lists Archives mailing list archive at Nabble.com. From chinluh at tritytech.com Fri May 19 10:22:27 2017 From: chinluh at tritytech.com (Tan Chin Luh) Date: Fri, 19 May 2017 16:22:27 +0800 Subject: [Scilab-Dev] Machine Learning Toolbox In-Reply-To: <1495137055.8877.1.camel@yahoo.es> References: <1493334215.25207.1.camel@yahoo.es> <1495137055.8877.1.camel@yahoo.es> Message-ID: <5f93b5b5-63d0-610b-f41d-f07b736243bc@tritytech.com> Hi all Scilab and machine learning enthusiasts, Great to have this topic in the mailing list as I am also exploring in deep learning recently. From my point of view, there are a few possibilities to build the ML toolbox in Scilab, namely: 1. Using the Scilab Matrix operation (Pro: fast for the parts which allow vectorization, Con: memory issue. Not sure about GPU support) 2. Using C/C++ API, such as caffe, caffe2, dlib, tiny dnn....? 3. Using Python API through PIMS, such as python with tensorflow, keras, dlib...? 4. Using Java interface throught JIMS, such as....? (a few i came across which never explore..) For the small to medium size network such as conventional FFBP, i think method one would have advantage as the batch processing could speed up the training and the codes are highly "readable" for non hardcore programmer. The network weights which could be simply representing by the matrices (1-2 hidden layers) and let the users easily visualize the "internal beauty" of the trained network with Scilab visualization features. However, when we move to CNN, or other deep learning network, i am not sure whether we could leverage the advantage of this. Or at least, it won't be a "jumpstart" way to build a new ML module. In seeing this, a quick "jumpstart" could be looking into the 2-4 methods. Then another issue might appear. Each of these having their class/structure to keep the complicated deep network architecture, and how are we going to interface this to Scilab? Should we: 1. Use the objects (Java objects, C++ class object in Scilab) to access the network created or loaded through the API? 2. Convert the objects into the Scilab mlist so it is more readable? 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. 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 Finally as for the GPU usage concern, using libs could have solve this depending on the lib being used. Forgive me if I made any mistake, just my 2 cents. Regards, Tan Chin Luh From caioc2bolado at gmail.com Fri May 19 16:37:17 2017 From: caioc2bolado at gmail.com (Caio Souza) Date: Fri, 19 May 2017 11:37:17 -0300 Subject: [Scilab-Dev] Machine Learning Toolbox In-Reply-To: <5f93b5b5-63d0-610b-f41d-f07b736243bc@tritytech.com> References: <1493334215.25207.1.camel@yahoo.es> <1495137055.8877.1.camel@yahoo.es> <5f93b5b5-63d0-610b-f41d-f07b736243bc@tritytech.com> Message-ID: Hi, Thanks for input We have both possibilities, from scratch or/and using a library, still an open topic. 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 :) 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. Somebody have some idea how to handle this project in a software > engineering perspective? > Just to ensure the tests and code quality. 1) Define our interface (most important thing), here I think who uses most the feature should chose. 2) Start with simple algorithms, but working 100% inside our interface. 3) Demos, tests and documentation for everything 4) Repeat 2 and 3. After doing 2 and 3 for the first time we will be able to advance faster. 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. > Not sure what would be more convenient to users, but I would prefer to wrap everything inside scilab to make a simpler interface. 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 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. > Finally as for the GPU usage concern, using libs could have solve this > depending on the lib being used. > I see GPU support being an option after we have something solid working already on CPU. Best, Caio SOUZA -------------- next part -------------- An HTML attachment was scrubbed... URL: From lambdasoftware at yahoo.es Fri May 19 22:12:50 2017 From: lambdasoftware at yahoo.es (Amanda Osvaldo) Date: Fri, 19 May 2017 17:12:50 -0300 Subject: [Scilab-Dev] Machine Learning Toolbox In-Reply-To: References: <1493334215.25207.1.camel@yahoo.es> <1495137055.8877.1.camel@yahoo.es> <5f93b5b5-63d0-610b-f41d-f07b736243bc@tritytech.com> Message-ID: <1495224770.15384.2.camel@yahoo.es> Hi everybody.??:-D Well, i think here we are starting the "The Hopeless Machine Learning Team". :-D? It's a good news for all the community, we should celebrate. :-D I'm working on a series of studies to determine if SciLAB can meet the requirements for my job. 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. :-D A machine learning toolbox is very important, we need to do it. :-O? -- Amanda Osvaldo On Fri, 2017-05-19 at 11:37 -0300, Caio Souza wrote: > Hi, > Thanks for input > > We have both possibilities, from scratch or/and using a library, > still an open topic. > 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 :) > > 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. > > > > Somebody have some idea how to handle this project in a software > > engineering perspective? > > Just to ensure the tests and code quality. > > 1) Define our interface (most important thing), here I think who uses > most the feature should chose. > 2) Start with simple algorithms, but working 100% inside our > interface. > 3) Demos, tests and documentation for everything > 4) Repeat 2 and 3. > > After doing 2 and 3 for the first time we will be able to advance > faster. > > > > 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.? > ? > Not sure what would be more convenient to users, but I would prefer > to wrap everything inside scilab to make a simpler interface. > > > > 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 > > 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. > > ? > > Finally as for the GPU usage concern, using libs could have solve > > this depending on the lib being used. > > I see GPU support being an option after we have something solid > working already on CPU. > > > > Best, > Caio SOUZA > > _______________________________________________ > dev mailing list > dev at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/dev -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: face-surprise.png Type: image/png Size: 1603 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: face-smile-big.png Type: image/png Size: 1580 bytes Desc: not available URL: From chinluh at tritytech.com Wed May 24 02:51:16 2017 From: chinluh at tritytech.com (Tan Chin Luh) Date: Wed, 24 May 2017 08:51:16 +0800 Subject: [Scilab-Dev] Machine Learning Toolbox In-Reply-To: <1495224770.15384.2.camel@yahoo.es> References: <1493334215.25207.1.camel@yahoo.es> <1495137055.8877.1.camel@yahoo.es> <5f93b5b5-63d0-610b-f41d-f07b736243bc@tritytech.com> <1495224770.15384.2.camel@yahoo.es> Message-ID: <95ebd2e8-5050-b2ac-657b-86241c7ca49a@tritytech.com> Hi, Just to share a little bit of my experience in this field, which I think it is definitely possible to move further to more advance networks despite some negative feedback. Firstly, while working on the neural network module (https://atoms.scilab.org/toolboxes/neuralnetwork/2.0), all the codes are done in Scilab, with vectorized codes for batch learning to increase the speed. However, the trade off is that the training could not handle large data set especially for the LM algorithm. This could be improved by using the online training with slower speed but less memory usage. While exploring module like SVM, fuzzy (not ML perhaps? AI?), both modules using dll from third parties and seamlessly integrated into Scilab. In which both module performs well with my "not so big" datasets. Moving towards deeper network, I just used the dnn importer from OPENCV 3.2 to import the caffe model and try to classify the image. The next bottle neck is whether to put the loaded model into the shared library which could be referred by Scilab later with pointer, or to import the model into Scilab list which could be then read by the gateway when needed. Thanks. regards, Chin Luh From aashay225 at gmail.com Mon May 29 10:48:48 2017 From: aashay225 at gmail.com (Aashay Singhal) Date: Mon, 29 May 2017 14:18:48 +0530 Subject: [Scilab-Dev] Problem in wrapping classes for Scilab using SWIG Message-ID: Hello everyone, I was trying to run this example. I wrote the exact code as given in the example and changed the module name to 'classes'. But I wasn't able to load the shared library in scilab. The commands I ran were: $ swig -scilab -c++ classes.i $ g++ -fPIC -c -I/usr/local/include/scilab classes_wrap.cxx $ g++ -shared classes_wrap.o -o libclasses.so The error shown in scilab was the following : https://codepaste.net/o1ziok Also, among the examples that are already given with SWIG, 5 of them are giving same error. I am not sure if this a problem on Scilab side or SWIG side. It would be great if someone can help me with this. Thanks Aashay -------------- next part -------------- An HTML attachment was scrubbed... URL: From lambdasoftware at yahoo.es Wed May 31 16:19:56 2017 From: lambdasoftware at yahoo.es (Amanda Osvaldo) Date: Wed, 31 May 2017 11:19:56 -0300 Subject: [Scilab-Dev] Machine Learning Toolbox In-Reply-To: <705f529c-4809-5a4d-6ae6-dc671b0f3e20@esi-group.com> References: <1493334215.25207.1.camel@yahoo.es> <1495137055.8877.1.camel@yahoo.es> <705f529c-4809-5a4d-6ae6-dc671b0f3e20@esi-group.com> Message-ID: <1496240396.3532.1.camel@yahoo.es> I everyone, I think we have nothing about it. :-O So ... somebody have a plan ? :-O -- Amanda Osvaldo On Mon, 2017-05-29 at 00:04 +0200, Philippe Saad? (ESI INENDI) wrote: > Dear All, > > > > I took some time to jump in the discussion due to the fact that I > wanted to get a better understanding of the current status of > your > discussions, a better understanding of Mandar's profile and > expertise, and also what is easy/hard to do with Scilab to meet > some > serious and legitimate demands from Scilab's users. > > > > As I am the last to join the discussion, I will voluntarily reset > my > mind and start again the discussions with you so that we can try > to > structure the project and converge quickly on an achievable list > of > goals for this GSoC. > > > > For that purpose, I would like to list a series of questions on > which we need to share a mutual list of answers and common > understanding. > > This should serve as a basis to decide what to do, how and when. > > > > So, feel free to fill in... > > > > > Scilab has a way to use Python : PIMS. Originaly created in > August 2014. > > How mature do you think it is? > How compatible is it with the potential need of using > existing Python-based ML framework from within Scilab? > How easy/hard would it be for Mandar to pursue what has been > done here so that using the ML frameworks from Scilab would > be > working well? > > Data Management. I think the questions related to the actual > size of the data that would be possibly handled by Scilab's > users is key. Many ML methods (not necessarily "Deep" ones) > need > to be trained on large data sets. It doesn't mean that > everything has to sit in RAM during training or general > pre-processing but it must be possible to handle large data > sets. > > Do we use only "pointers" from Scilab to give an access to > the real data structures that are used by the ML > frameworks? > Do we want to integrate part or all of the data structures > that are useful, as native Scilab data structures? > Do we consider that the execution of ML algorithms should be > designed and architectured in a way that it is done > "remotely" > from the perspective of Scilab? > > > > Use Cases. We need to list some use cases that are typical of > what Scilab users do and that make the usage of ML an > exciting > perspective. If we can not demonstrate that ML within Scilab > is > possible, easy and really useful on these Use cases, I am not > sure we will have reached the main target of that GSoC > opportunity. > > Can we list use cases together? > > I will start by items some but your input is important here. > > image classification > object recognition in images and video > Data Driven Industrial Process Control > Anomaly Detection > Dimensionality / Model reduction > etc. > > > > > > > For sure, these questions do not cover all the important topics > for > this "ML Toolbox" project but this is a way to bootstrap. > > As we know, we need to be active and efficient for the 30th of > May! > > > > Thanks for your feedback and feel free to share your point of > view. > > > > > > > > > > > Cordialement ? Best regards, > > > Philippe SAAD? > > > > > > > > Le 18/05/2017 ? 21:50, Amanda Osvaldo a > ?crit : > > > > > > > > > > > > > > > Hi everybody, can I made some questions ? > > > > > > > > First, at all, I really agree that SciLab needs a Machine > > Learning toolbox. > > > > > > > > However, I'm pretty critical about Scilab in your > > limitations. > > I see very potential in the software but require a reform > > in your infrastructure. > > > > > > > > > > > > > > So, my questions. > > > > > > > > > > How large are we talking about the training dataset in > > scilab ? > > Even with Tensorflow compatibility if you need to put all > > the dataset into the RAM I fear the toolbox utility will > > be > > very limited. > > In another words: The toolbox will can handle a 250GB > > dataset or just a few GBs from a desktop ? > > > > > > > > Have I read right ? > > We are talking about to integrate Scilab and tensorflow or > > scikit-learn ? > > I think it's a good idea, I just whant to know if I'm > > interpreting right. > > > > > > > > Somebody have some idea how to handle this project in a > > software engineering perspective? > > Just to ensure the tests and code quality. > > > > > > > > > > > > > > > > -- Amanda Osvaldo > > > > > > > > > > > > > > On Thu, 2017-05-18 at 16:01 +0000, Yann Debray wrote: > > > > > > > > Dear Caio, Dhruv and Amanda, > > > > > > I would like to include my colleague Philippe > > > Saad? to the exchanges on Machine Learning for > > > Scilab. > > > He is an experienced mathematician working > > > with us at ESI Group, and has an interesting vision > > > on the > > > subject. > > > He will be scientific advisor and mentor for > > > a joint internship on Machine learning starting mid > > > june. > > > > > > @Philippe > > > Saad? (ESI INENDI): Could you maybe share > > > with us your view on the subject? > > > > > > We can keep this exchange public if it is > > > alright with you all, since I believe our success > > > on the > > > subject will depend on our capacity to centralize > > > and > > > merge our community efforts. > > > You can all collaborate on the project on our > > > forge: > > > http://forge.scilab.org/index.php/p/machine-learning-to > > > olbox/ > > > > > > Yours > > > Yann @ Scilab > > > > > > > > > De : > > > Amanda > > > Osvaldo > > > > > > Date : vendredi 28 avril 2017 ? 01:03 > > > > > > ? : List dedicated to the development of Scilab > > > , Yann Debray > > > , Dhruv Khattar > > > > > > > > > Objet : Re: [Scilab-Dev] Machine Learning > > > Toolbox > > > > > > > > > > > > > > > > > > Hi Caio, sorry for the late. > > > > > > > > > > > > > > > > > > I think we should ask ourselves what > > > SciLAB's focus and what audience are. > > > > > > > > > I feel a lack of knowing what users > > > of Scilab seek. > > > > > > > > > > > > > > > > > > Me, for example, I want to do > > > everything from protyping to running the script on > > > hundreds of Intel Xeon servers with the least > > > possible > > > effort. > > > > > > > > > Even with less effort than it would > > > have if the script were built in Python. > > > > > > > > > > > > > > > > > > I am sure that new data structures will > > > expand the use of SciLAB. > > > > > > > > > > > > > > > > > > But what advantage will this bring to > > > users? > > > > > > > > > Python, as example, have already > > > optimized data structures and libraries. > > > > > > > > > > > > > > > > > > -- Amanda Osvaldo > > > > > > > > > > > > > > > > > > > > > > > > > > > On Wed, 2017-04-26 at 14:32 -0300, Caio > > > Souza wrote: > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > > > > > > I have been thinking about the > > > usability of the toolbox and independent of > > > which > > > algorithms we are going to have, would be > > > interesting > > > to have some simplified structure (like > > > TensorFlow). > > > > > > > > > > > > > > > > > > Despite it being a lot of work to > > > have such structure, (data, model, cost > > > function, > > > minimizer), it would make the toolbox easy to > > > use and > > > extend, having minimum impact to the usability. > > > > > > > > > > > > > > > > > > IMHO, this is something that should > > > be defined before any coding starts, and also > > > well > > > explained to the student. > > > > > > > > > > > > > > > > > > I would like to hear from you what > > > do you think, so we can start a discussion. > > > > > > > > > > > > > > > > > > > > > > > > > > > Best, > > > > > > > > > Caio SOUZA > > > > > > > > > _______________________________________________ > > > dev mailing list > > > dev at lists.scilab.org > > > http://lists.scilab.org/mailman/listinfo/dev > > > > > > > > > > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: face-surprise.png Type: image/png Size: 1603 bytes Desc: not available URL: From caioc2bolado at gmail.com Wed May 31 16:41:38 2017 From: caioc2bolado at gmail.com (Caio Souza) Date: Wed, 31 May 2017 11:41:38 -0300 Subject: [Scilab-Dev] Machine Learning Toolbox In-Reply-To: References: <1493334215.25207.1.camel@yahoo.es> <1495137055.8877.1.camel@yahoo.es> <705f529c-4809-5a4d-6ae6-dc671b0f3e20@esi-group.com> <1496240396.3532.1.camel@yahoo.es> Message-ID: Hi, I have received it, I'm planning to answer all those questions untill the end of the week. Sorry for the delay. On Wed, May 31, 2017 at 11:25 AM, Philippe Saade < Philippe.Saade at esi-group.com> wrote: > Hi all > It looks like you didn't receive my first email ? > > Envoy? de mon mobile > > Le 31 mai 2017 ? 16:20, Amanda Osvaldo a ?crit : > > > I everyone, I think we have nothing about it. > So ... somebody have a plan ? > > -- Amanda Osvaldo > > > On Mon, 2017-05-29 at 00:04 +0200, Philippe Saad? (ESI INENDI) wrote: > > Dear All, > > I took some time to jump in the discussion due to the fact that I wanted > to get a better understanding of the current status of your discussions, a > better understanding of Mandar's profile and expertise, and also what is > easy/hard to do with Scilab to meet some serious and legitimate demands > from Scilab's users. > > As I am the last to join the discussion, I will voluntarily reset my mind > and start again the discussions with you so that we can try to structure > the project and converge quickly on an achievable list of goals for this > GSoC. > > For that purpose, I would like to list a series of questions on which we > need to share a mutual list of answers and common understanding. > This should serve as a basis to decide what to do, how and when. > > So, feel free to fill in... > > > 1. Scilab has a way to use Python : PIMS. Originaly created in August > 2014. > 1. How mature do you think it is? > 2. How compatible is it with the potential need of using existing > Python-based ML framework from within Scilab? > 3. How easy/hard would it be for Mandar to pursue what has been > done here so that using the ML frameworks from Scilab would be working > well? > 2. Data Management. I think the questions related to the actual size > of the data that would be possibly handled by Scilab's users is key. Many > ML methods (not necessarily "Deep" ones) need to be trained on large data > sets. It doesn't mean that everything has to sit in RAM during training or > general pre-processing but it must be possible to handle large data sets. > 1. Do we use only "pointers" from Scilab to give an access to the > real data structures that are used by the ML frameworks? > 2. Do we want to integrate part or all of the data structures that > are useful, as native Scilab data structures? > 3. Do we consider that the execution of ML algorithms should be > designed and architectured in a way that it is done "remotely" from the > perspective of Scilab? > 3. Use Cases. We need to list some use cases that are typical of > what Scilab users do and that make the usage of ML an exciting perspective. > If we can not demonstrate that ML within Scilab is possible, easy and > really useful on these Use cases, I am not sure we will have reached the > main target of that GSoC opportunity. > Can we list use cases together? > I will start by items some but your input is important here. > 1. image classification > 2. object recognition in images and video > 3. Data Driven Industrial Process Control > 4. Anomaly Detection > 5. Dimensionality / Model reduction > 6. etc. > > > For sure, these questions do not cover all the important topics for this > "ML Toolbox" project but this is a way to bootstrap. > As we know, we need to be active and efficient for the 30th of May! > > Thanks for your feedback and feel free to share your point of view. > > > > > Cordialement ? Best regards, > > > > Philippe SAAD? > * * > > > Le 18/05/2017 ? 21:50, Amanda Osvaldo a ?crit : > > Hi everybody, can I made some questions ? > > First, at all, I really agree that SciLab needs a Machine Learning toolbox. > > However, I'm pretty critical about Scilab in your limitations. > *I see very potential in the software but require a reform in your > infrastructure.* > > > So, my questions. > > How large are we talking about the training dataset in scilab ? > Even with Tensorflow compatibility if you need to put all the dataset into > the RAM I fear the toolbox utility will be very limited. > In another words: The toolbox will can handle a 250GB dataset or just a > few GBs from a desktop ? > > Have I read right ? > We are talking about to integrate Scilab and tensorflow or scikit-learn ? > I think it's a good idea, I just whant to know if I'm interpreting right. > > Somebody have some idea how to handle this project in a software > engineering perspective? > Just to ensure the tests and code quality. > > > -- Amanda Osvaldo > > > On Thu, 2017-05-18 at 16:01 +0000, Yann Debray wrote: > > Dear Caio, Dhruv and Amanda, > > > > I would like to include my colleague Philippe Saad? to the exchanges on > Machine Learning for Scilab. > > He is an experienced mathematician working with us at ESI Group, and has > an interesting vision on the subject. > > He will be scientific advisor and mentor for a joint internship on Machine > learning starting mid june. > > > > @Philippe Saad? (ESI INENDI) : Could you > maybe share with us your view on the subject? > > > > We can keep this exchange public if it is alright with you all, since I > believe our success on the subject will depend on our capacity to > centralize and merge our community efforts. > > You can all collaborate on the project on our forge: > > http://forge.scilab.org/index.php/p/machine-learning-toolbox/ > > > > Yours > > Yann @ Scilab > > > > *De : *Amanda Osvaldo > *Date : *vendredi 28 avril 2017 ? 01:03 > *? : *List dedicated to the development of Scilab > , Yann Debray > , Dhruv Khattar > > *Objet : *Re: [Scilab-Dev] Machine Learning Toolbox > > > > Hi Caio, sorry for the late. > > > > *I think we should ask ourselves what SciLAB's focus and what audience > are.* > > *I feel a lack of knowing what users of Scilab seek.* > > > > Me, for example, I want to do everything from protyping to running the > script on hundreds of Intel Xeon servers with the least possible effort. > > Even with less effort than it would have if the script were built in > Python. > > > > I am sure that new data structures will expand the use of SciLAB. > > > > But what advantage will this bring to users? > > Python, as example, have already optimized data structures and libraries. > > > > -- Amanda Osvaldo > > > > > > On Wed, 2017-04-26 at 14:32 -0300, Caio Souza wrote: > > Hi, > > > > > > I have been thinking about the usability of the toolbox and independent of > which algorithms we are going to have, would be interesting to have some > simplified structure (like TensorFlow). > > > > Despite it being a lot of work to have such structure, (data, model, cost > function, minimizer), it would make the toolbox easy to use and extend, > having minimum impact to the usability. > > > > IMHO, this is something that should be defined before any coding starts, > and also well explained to the student. > > > > I would like to hear from you what do you think, so we can start a > discussion. > > > > > > Best, > > Caio SOUZA > > _______________________________________________ > > dev mailing list > > dev at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Philippe.Saade at esi-group.com Mon May 29 00:04:09 2017 From: Philippe.Saade at esi-group.com (=?UTF-8?Q?Philippe_Saad=c3=a9_=28ESI_INENDI=29?=) Date: Mon, 29 May 2017 00:04:09 +0200 Subject: [Scilab-Dev] Machine Learning Toolbox In-Reply-To: <1495137055.8877.1.camel@yahoo.es> References: <1493334215.25207.1.camel@yahoo.es> <1495137055.8877.1.camel@yahoo.es> Message-ID: <705f529c-4809-5a4d-6ae6-dc671b0f3e20@esi-group.com> An HTML attachment was scrubbed... URL: From simon.marchetto at esi-group.com Tue May 30 15:36:56 2017 From: simon.marchetto at esi-group.com (Simon Marchetto) Date: Tue, 30 May 2017 15:36:56 +0200 Subject: [Scilab-Dev] Problem in wrapping classes for Scilab using SWIG In-Reply-To: References: Message-ID: <540ede17-7747-7a93-7499-2174295b4a59@esi-group.com> Hello, The issue is confirmed: https://github.com/swig/swig/issues/994 The fix will be commited soon. Please report any problem on Github next time, or on SWIG mailing lists, as you already did for other issues. Thanks for your contribution. Simon Marchetto Le 29/05/2017 ? 10:48, Aashay Singhal a ?crit : > Hello everyone, > > I was trying to run this > > example. I wrote the exact code as given in the example and changed > the module name to 'classes'. But I wasn't able to load the shared > library in scilab. The commands I ran were: > > $ swig -scilab -c++ classes.i > $ g++ -fPIC -c -I/usr/local/include/scilab classes_wrap.cxx > $ g++ -shared classes_wrap.o -o libclasses.so > > > The error shown in scilab was the following : > https://codepaste.net/o1ziok > Also, among the examples that are already given with SWIG, 5 of them > are giving same error. I am not sure if this a problem on Scilab side > or SWIG side. > > It would be great if someone can help me with this. > > Thanks > Aashay > > > _______________________________________________ > dev mailing list > dev at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From vashistharitveeka at gmail.com Wed May 31 09:55:01 2017 From: vashistharitveeka at gmail.com (Ritveeka Vashistha) Date: Wed, 31 May 2017 13:25:01 +0530 Subject: [Scilab-Dev] Regarding some anomaly in CMSCOPE.sci Message-ID: Respected Sir/Madam, I think that there is some anomaly in CMSCOPE.sci file path=r'modules/scicos_blocks/macros/Sink/CMSCOPE.sci' Could you please explain why model.ipar uses clrs(1:sum(in)) inside define case while it uses clrs(:) inside set case ? Please reply as soon as possible. Thanks, Ritveeka Vashistha IIT Guwahati -------------- next part -------------- An HTML attachment was scrubbed... URL: From Philippe.Saade at esi-group.com Wed May 31 16:25:15 2017 From: Philippe.Saade at esi-group.com (Philippe Saade) Date: Wed, 31 May 2017 14:25:15 +0000 Subject: [Scilab-Dev] Machine Learning Toolbox In-Reply-To: <1496240396.3532.1.camel@yahoo.es> References: <1493334215.25207.1.camel@yahoo.es> <1495137055.8877.1.camel@yahoo.es> <705f529c-4809-5a4d-6ae6-dc671b0f3e20@esi-group.com>, <1496240396.3532.1.camel@yahoo.es> Message-ID: Hi all It looks like you didn't receive my first email ? Envoy? de mon mobile Le 31 mai 2017 ? 16:20, Amanda Osvaldo > a ?crit : I everyone, I think we have nothing about it. So ... somebody have a plan ? -- Amanda Osvaldo On Mon, 2017-05-29 at 00:04 +0200, Philippe Saad? (ESI INENDI) wrote: Dear All, I took some time to jump in the discussion due to the fact that I wanted to get a better understanding of the current status of your discussions, a better understanding of Mandar's profile and expertise, and also what is easy/hard to do with Scilab to meet some serious and legitimate demands from Scilab's users. As I am the last to join the discussion, I will voluntarily reset my mind and start again the discussions with you so that we can try to structure the project and converge quickly on an achievable list of goals for this GSoC. For that purpose, I would like to list a series of questions on which we need to share a mutual list of answers and common understanding. This should serve as a basis to decide what to do, how and when. So, feel free to fill in... 1. Scilab has a way to use Python : PIMS. Originaly created in August 2014. * How mature do you think it is? * How compatible is it with the potential need of using existing Python-based ML framework from within Scilab? * How easy/hard would it be for Mandar to pursue what has been done here so that using the ML frameworks from Scilab would be working well? 2. Data Management. I think the questions related to the actual size of the data that would be possibly handled by Scilab's users is key. Many ML methods (not necessarily "Deep" ones) need to be trained on large data sets. It doesn't mean that everything has to sit in RAM during training or general pre-processing but it must be possible to handle large data sets. * Do we use only "pointers" from Scilab to give an access to the real data structures that are used by the ML frameworks? * Do we want to integrate part or all of the data structures that are useful, as native Scilab data structures? * Do we consider that the execution of ML algorithms should be designed and architectured in a way that it is done "remotely" from the perspective of Scilab? 3. Use Cases. We need to list some use cases that are typical of what Scilab users do and that make the usage of ML an exciting perspective. If we can not demonstrate that ML within Scilab is possible, easy and really useful on these Use cases, I am not sure we will have reached the main target of that GSoC opportunity. Can we list use cases together? I will start by items some but your input is important here. * image classification * object recognition in images and video * Data Driven Industrial Process Control * Anomaly Detection * Dimensionality / Model reduction * etc. For sure, these questions do not cover all the important topics for this "ML Toolbox" project but this is a way to bootstrap. As we know, we need to be active and efficient for the 30th of May! Thanks for your feedback and feel free to share your point of view. Cordialement ? Best regards, Philippe SAAD? Le 18/05/2017 ? 21:50, Amanda Osvaldo a ?crit : Hi everybody, can I made some questions ? First, at all, I really agree that SciLab needs a Machine Learning toolbox. However, I'm pretty critical about Scilab in your limitations. I see very potential in the software but require a reform in your infrastructure. So, my questions. How large are we talking about the training dataset in scilab ? Even with Tensorflow compatibility if you need to put all the dataset into the RAM I fear the toolbox utility will be very limited. In another words: The toolbox will can handle a 250GB dataset or just a few GBs from a desktop ? Have I read right ? We are talking about to integrate Scilab and tensorflow or scikit-learn ? I think it's a good idea, I just whant to know if I'm interpreting right. Somebody have some idea how to handle this project in a software engineering perspective? Just to ensure the tests and code quality. -- Amanda Osvaldo On Thu, 2017-05-18 at 16:01 +0000, Yann Debray wrote: Dear Caio, Dhruv and Amanda, I would like to include my colleague Philippe Saad? to the exchanges on Machine Learning for Scilab. He is an experienced mathematician working with us at ESI Group, and has an interesting vision on the subject. He will be scientific advisor and mentor for a joint internship on Machine learning starting mid june. @Philippe Saad? (ESI INENDI): Could you maybe share with us your view on the subject? We can keep this exchange public if it is alright with you all, since I believe our success on the subject will depend on our capacity to centralize and merge our community efforts. You can all collaborate on the project on our forge: http://forge.scilab.org/index.php/p/machine-learning-toolbox/ Yours Yann @ Scilab De : Amanda Osvaldo Date : vendredi 28 avril 2017 ? 01:03 ? : List dedicated to the development of Scilab , Yann Debray , Dhruv Khattar Objet : Re: [Scilab-Dev] Machine Learning Toolbox Hi Caio, sorry for the late. I think we should ask ourselves what SciLAB's focus and what audience are. I feel a lack of knowing what users of Scilab seek. Me, for example, I want to do everything from protyping to running the script on hundreds of Intel Xeon servers with the least possible effort. Even with less effort than it would have if the script were built in Python. I am sure that new data structures will expand the use of SciLAB. But what advantage will this bring to users? Python, as example, have already optimized data structures and libraries. -- Amanda Osvaldo On Wed, 2017-04-26 at 14:32 -0300, Caio Souza wrote: Hi, I have been thinking about the usability of the toolbox and independent of which algorithms we are going to have, would be interesting to have some simplified structure (like TensorFlow). Despite it being a lot of work to have such structure, (data, model, cost function, minimizer), it would make the toolbox easy to use and extend, having minimum impact to the usability. IMHO, this is something that should be defined before any coding starts, and also well explained to the student. I would like to hear from you what do you think, so we can start a discussion. Best, Caio SOUZA _______________________________________________ dev mailing list dev at lists.scilab.org http://lists.scilab.org/mailman/listinfo/dev -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: face-surprise.png Type: image/png Size: 1603 bytes Desc: face-surprise.png URL: