From allan.cornet at scilab.org Wed Apr 1 08:31:11 2009 From: allan.cornet at scilab.org (Allan CORNET) Date: Wed, 1 Apr 2009 08:31:11 +0200 Subject: [Scilab-Dev] Compile Error SciLab In-Reply-To: <3c6df6d90903240212i18ac5e91vb77e9157340dc29d@mail.gmail.com> References: <3c6df6d90903240212i18ac5e91vb77e9157340dc29d@mail.gmail.com> Message-ID: <001a01c9b293$7313e4b0$593bae10$@cornet@scilab.org> Hi, Can you send to me your (full) buildlog.htm file generated by visual studio ? Thanks you Allan CORNET De : Saumya [mailto:saujee1985 at gmail.com] Envoy? : mardi 24 mars 2009 10:13 ? : dev at lists.scilab.org Objet : [Scilab-Dev] Compile Error SciLab Hi all, I tried to compile Scilab in visual Studio Pro 2008 and following error comes fatal error LNK1181: cannot open input file '..\..\..\..\..\bin\libscilab.lib' can you tell me why this error comes?? Thank you -------------- next part -------------- An HTML attachment was scrubbed... URL: From thanuka.sp at gmail.com Wed Apr 1 10:10:48 2009 From: thanuka.sp at gmail.com (Thotage Thanuka Srimal Piyasena) Date: Wed, 1 Apr 2009 13:40:48 +0530 Subject: Google Summer of Code 2009 (Pretty print and export in Scilab) In-Reply-To: References: Message-ID: Hi All, I am a final year undergraduate of University of Moratuwa, Sri Lanka, specializing in the field of Computer Science and Engineering. I am interested in participating on the project "Pretty print and export in Scilab". I have done several individual projects as well as participated for several group projects according to the requirements of some modules in our department.Some of projects I have done are as follows; Multi Agent System for Energy Management Online Student Registration System Online Railway Information System Pharmacy & Grocery Management System I have also done some other several mini projects. I need to emphasize that I have built a Pretty Printer for RelaxNG as an assignment of Programming Languages module. So, I believe I am aware of almost all the theoretical and practical concepts needed for this project because I have followed Programming Languages, Compiler Theory, Theory of Computing modules as well. If you need to observe my pretty printer source code, you can simply find it at my blog (http://thanukasp.blogspot.com/). (Note: within the Pretty Printer.zip file contains info.txt file describing how to run this application.) Actually I had a six month of training experience at IronOneTechnologies in Sri Lanka. I have been working with Java technologies for almost three years. I have developed a fair amount J2SE and J2EE applications. I gave my contribution to three main projects while I was there. I would be highly grateful if you can send me more details regarding this project as soon as possible and tell me how to subscribe to Scilab Google Summer of Code mailing list. Thank in Advance. ------------------------------------------------------------------------ Best Regards, Thanuka Piyasena. Computer Science & Engineering University of Moratuwa Tel : 071 - 6903313 Blog: http://thanukasp.blogspot.com/ ----------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From sylvestre.ledru at scilab.org Wed Apr 1 10:12:20 2009 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Wed, 01 Apr 2009 10:12:20 +0200 Subject: [Scilab-Dev] Google Summer of Code 2009 (Pretty print and export in Scilab) In-Reply-To: References: Message-ID: <1238573540.1446.74.camel@korcula.inria.fr> You are already registered to the gsoc ML. Sylvestre Le mercredi 01 avril 2009 ? 13:40 +0530, Thotage Thanuka Srimal Piyasena a ?crit : > Hi All, > > > I am a final year undergraduate of University of Moratuwa, Sri Lanka, > specializing in the field of Computer Science and Engineering. I am > interested in participating on the project "Pretty print and export in > Scilab". > > > I have done several individual projects as well as participated for > several group projects according to the requirements of some modules > in our department.Some of projects I have done are as follows; > Multi Agent System for Energy Management > > Online Student Registration System > Online Railway Information System > Pharmacy & Grocery Management System > I have also done some other several mini projects. > > > I need to emphasize that I have built a Pretty Printer for RelaxNG as > an assignment of Programming Languages module. So, I believe I am > aware of almost all the theoretical and practical concepts needed for > this project because I have followed Programming Languages, Compiler > Theory, Theory of Computing modules as well. > > > If you need to observe my pretty printer source code, you can simply > find it at my blog (http://thanukasp.blogspot.com/). > (Note: within the Pretty Printer.zip file contains info.txt file > describing how to run this application.) > > > Actually I had a six month of training experience at > IronOneTechnologies in Sri Lanka. I have been working with Java > technologies for almost three years. I have developed a fair amount > J2SE and J2EE applications. I gave my contribution to three main > projects while I was there. > > > I would be highly grateful if you can send me more details regarding > this project as soon as possible and tell me how to subscribe > to Scilab Google Summer of Code mailing list. > > > Thank in Advance. > > > > ------------------------------------------------------------------------ > Best Regards, > Thanuka Piyasena. > Computer Science & Engineering > University of Moratuwa > Tel : 071 - 6903313 > Blog: http://thanukasp.blogspot.com/ > ----------------------------------------------------------------------- > > > > From thanuka.sp at gmail.com Wed Apr 1 10:17:56 2009 From: thanuka.sp at gmail.com (Thotage Thanuka Srimal Piyasena) Date: Wed, 1 Apr 2009 13:47:56 +0530 Subject: [Scilab-Dev] Google Summer of Code 2009 (Pretty print and export in Scilab) In-Reply-To: <1238573540.1446.74.camel@korcula.inria.fr> References: <1238573540.1446.74.camel@korcula.inria.fr> Message-ID: But I cannot sent a mail to that mailing list. I tried to several times. I couldn't find out what is wrong. On Wed, Apr 1, 2009 at 1:42 PM, Sylvestre Ledru wrote: > You are already registered to the gsoc ML. > > Sylvestre > > Le mercredi 01 avril 2009 ? 13:40 +0530, Thotage Thanuka Srimal Piyasena > a ?crit : > > Hi All, > > > > > > I am a final year undergraduate of University of Moratuwa, Sri Lanka, > > specializing in the field of Computer Science and Engineering. I am > > interested in participating on the project "Pretty print and export in > > Scilab". > > > > > > I have done several individual projects as well as participated for > > several group projects according to the requirements of some modules > > in our department.Some of projects I have done are as follows; > > Multi Agent System for Energy Management > > > > Online Student Registration System > > Online Railway Information System > > Pharmacy & Grocery Management System > > I have also done some other several mini projects. > > > > > > I need to emphasize that I have built a Pretty Printer for RelaxNG as > > an assignment of Programming Languages module. So, I believe I am > > aware of almost all the theoretical and practical concepts needed for > > this project because I have followed Programming Languages, Compiler > > Theory, Theory of Computing modules as well. > > > > > > If you need to observe my pretty printer source code, you can simply > > find it at my blog (http://thanukasp.blogspot.com/). > > (Note: within the Pretty Printer.zip file contains info.txt file > > describing how to run this application.) > > > > > > Actually I had a six month of training experience at > > IronOneTechnologies in Sri Lanka. I have been working with Java > > technologies for almost three years. I have developed a fair amount > > J2SE and J2EE applications. I gave my contribution to three main > > projects while I was there. > > > > > > I would be highly grateful if you can send me more details regarding > > this project as soon as possible and tell me how to subscribe > > to Scilab Google Summer of Code mailing list. > > > > > > Thank in Advance. > > > > > > > > ------------------------------------------------------------------------ > > Best Regards, > > Thanuka Piyasena. > > Computer Science & Engineering > > University of Moratuwa > > Tel : 071 - 6903313 > > Blog: http://thanukasp.blogspot.com/ > > ----------------------------------------------------------------------- > > > > > > > > > > -- ------------------------------------------------------------------------ Best Regards, Thanuka Piyasena. Computer Science & Engineering University of Moratuwa Tel : 071 - 6903313 Blog: http://thanukasp.blogspot.com/ ----------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From thanuka.sp at gmail.com Wed Apr 1 10:20:51 2009 From: thanuka.sp at gmail.com (Thotage Thanuka Srimal Piyasena) Date: Wed, 1 Apr 2009 13:50:51 +0530 Subject: [Scilab-Dev] Google Summer of Code 2009 (Pretty print and export in Scilab) In-Reply-To: References: <1238573540.1446.74.camel@korcula.inria.fr> Message-ID: Thank now it is ok. On Wed, Apr 1, 2009 at 1:47 PM, Thotage Thanuka Srimal Piyasena < thanuka.sp at gmail.com> wrote: > But I cannot sent a mail to that mailing list. I tried to several times. > I couldn't find out what is wrong. > > > > On Wed, Apr 1, 2009 at 1:42 PM, Sylvestre Ledru < > sylvestre.ledru at scilab.org> wrote: > >> You are already registered to the gsoc ML. >> >> Sylvestre >> >> Le mercredi 01 avril 2009 ? 13:40 +0530, Thotage Thanuka Srimal Piyasena >> a ?crit : >> > Hi All, >> > >> > >> > I am a final year undergraduate of University of Moratuwa, Sri Lanka, >> > specializing in the field of Computer Science and Engineering. I am >> > interested in participating on the project "Pretty print and export in >> > Scilab". >> > >> > >> > I have done several individual projects as well as participated for >> > several group projects according to the requirements of some modules >> > in our department.Some of projects I have done are as follows; >> > Multi Agent System for Energy Management >> > >> > Online Student Registration System >> > Online Railway Information System >> > Pharmacy & Grocery Management System >> > I have also done some other several mini projects. >> > >> > >> > I need to emphasize that I have built a Pretty Printer for RelaxNG as >> > an assignment of Programming Languages module. So, I believe I am >> > aware of almost all the theoretical and practical concepts needed for >> > this project because I have followed Programming Languages, Compiler >> > Theory, Theory of Computing modules as well. >> > >> > >> > If you need to observe my pretty printer source code, you can simply >> > find it at my blog (http://thanukasp.blogspot.com/). >> > (Note: within the Pretty Printer.zip file contains info.txt file >> > describing how to run this application.) >> > >> > >> > Actually I had a six month of training experience at >> > IronOneTechnologies in Sri Lanka. I have been working with Java >> > technologies for almost three years. I have developed a fair amount >> > J2SE and J2EE applications. I gave my contribution to three main >> > projects while I was there. >> > >> > >> > I would be highly grateful if you can send me more details regarding >> > this project as soon as possible and tell me how to subscribe >> > to Scilab Google Summer of Code mailing list. >> > >> > >> > Thank in Advance. >> > >> > >> > >> > ------------------------------------------------------------------------ >> > Best Regards, >> > Thanuka Piyasena. >> > Computer Science & Engineering >> > University of Moratuwa >> > Tel : 071 - 6903313 >> > Blog: http://thanukasp.blogspot.com/ >> > ----------------------------------------------------------------------- >> > >> > >> > >> > >> >> > > > -- > ------------------------------------------------------------------------ > Best Regards, > Thanuka Piyasena. > Computer Science & Engineering > University of Moratuwa > Tel : 071 - 6903313 > Blog: http://thanukasp.blogspot.com/ > ----------------------------------------------------------------------- > -- ------------------------------------------------------------------------ Best Regards, Thanuka Piyasena. Computer Science & Engineering University of Moratuwa Tel : 071 - 6903313 Blog: http://thanukasp.blogspot.com/ ----------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From ycollet at freesurf.fr Wed Apr 1 13:49:37 2009 From: ycollet at freesurf.fr (ycollet at freesurf.fr) Date: Wed, 01 Apr 2009 13:49:37 +0200 Subject: scilab and overloading Message-ID: <5f2821e42301327e6c682e99e0aa19fa@freesurf.fr> I found an interesting information in the file mname.f in the overloading module: tlist: up to 8 first characters of the tlist type So, it seems that scilab is analyzing only 8 characters of the tlist type when looking for overloaded type ? YC From ycollet at freesurf.fr Wed Apr 1 14:40:06 2009 From: ycollet at freesurf.fr (ycollet at freesurf.fr) Date: Wed, 01 Apr 2009 14:40:06 +0200 Subject: overloading problem ... next Message-ID: A sample test for the overloading limitation for 8 char: myvar1 = tlist(['scilabmyvar1','x','y'],2.0,3.0); myvar2 = tlist(['scilabmyvar2','x','y','z'],2.0,3.0, 4.0); myvar3 = tlist(['scilabm','x','y','z'],2.0,3.0,4.0); function y = %scilabmyvar1_sin(myvar) printf('sin with a scilabmyvar1\n'); y = sin(2*%pi*sqrt(myvar('x')^2 + myvar('y')^2)); endfunction function y = %scilabmyvar2_sin(myvar) printf('sin with a scilabmyvar2\n'); y = sin(2*%pi*sqrt(myvar('x')^2 + myvar('y')^2 + myvar('z')^2)); endfunction function y = %scilabm_sin(myvar) printf('sin with a scilabm\n'); y = sin(2*%pi*sqrt(myvar('x')^2 + myvar('y')^2 + myvar('z')^2)); endfunction printf('sin + scilabmyvar1 = %f\n',sin(myvar1)); // Line 1 printf('sin + scilabmyvar2 = %f\n',sin(myvar2)); // Line 2 printf('sin + scilabm = %f\n',sin(myvar3)); // Line 3 ------------- end of test_overload.sce If you comment Line 1 and Line 2: -->exec test_overload.sce; sin with a scilabm sin + scilabm = 0.660535 Now, if I uncomment everything: -->exec test_overload.sce; printf('sin + scilabmyvar1 = %f\n',sin(myvar1)); !--error 246 Fonction non d?finie pour le type d'argument donn?. v?rifier les arguments ou d?finir la fonction %scilabmy_sin pour la surcharge. at line 20 of exec file called by : exec test_overload.sce; Scilab sees only the type "scilabmy" (8 chars) and not the "scilabmyvar1" YC From sylvestre.ledru at scilab.org Wed Apr 1 14:43:06 2009 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Wed, 01 Apr 2009 14:43:06 +0200 Subject: Change of version of autoconf to version 2.63 Message-ID: <1238589786.1446.653.camel@korcula.inria.fr> Hello, For those who are using --enable-maintainer-mode and touchy to m4 macros or the configure, we changed the version of autoconf from version 2.61 => 2.63. Please update you version (otherwise, it is changing all Makefile.in). For Ubuntu: http://mirrors.kernel.org/ubuntu/pool/main/a/autoconf/autoconf_2.63-2ubuntu1_all.deb It going to be the default version of autoconf in the future ubuntu (Jaunty). For Debian: It is available in testing and can be easily installed on a stable version. Sylvestre From ycollet at freesurf.fr Wed Apr 1 14:51:53 2009 From: ycollet at freesurf.fr (ycollet at freesurf.fr) Date: Wed, 01 Apr 2009 14:51:53 +0200 Subject: [Scilab-Dev] overloading problem ... next In-Reply-To: References: Message-ID: <816f785d141444fb5c2f8ccf063a6691@freesurf.fr> Sorry, it's in the documentation. But in the overload documentation, the limitation is set to the first 9 characters. It's 8. It's very annoying for "fake" object oriented programming ... YC On Wed, 01 Apr 2009 14:40:06 +0200, wrote: > A sample test for the overloading limitation for 8 char: > > myvar1 = tlist(['scilabmyvar1','x','y'],2.0,3.0); > myvar2 = tlist(['scilabmyvar2','x','y','z'],2.0,3.0, 4.0); > myvar3 = tlist(['scilabm','x','y','z'],2.0,3.0,4.0); > > function y = %scilabmyvar1_sin(myvar) > printf('sin with a scilabmyvar1\n'); > y = sin(2*%pi*sqrt(myvar('x')^2 + myvar('y')^2)); > endfunction > > function y = %scilabmyvar2_sin(myvar) > printf('sin with a scilabmyvar2\n'); > y = sin(2*%pi*sqrt(myvar('x')^2 + myvar('y')^2 + myvar('z')^2)); > endfunction > > function y = %scilabm_sin(myvar) > printf('sin with a scilabm\n'); > y = sin(2*%pi*sqrt(myvar('x')^2 + myvar('y')^2 + myvar('z')^2)); > endfunction > > printf('sin + scilabmyvar1 = %f\n',sin(myvar1)); // Line 1 > printf('sin + scilabmyvar2 = %f\n',sin(myvar2)); // Line 2 > printf('sin + scilabm = %f\n',sin(myvar3)); // Line 3 > > ------------- end of test_overload.sce > > If you comment Line 1 and Line 2: > > -->exec test_overload.sce; > sin with a scilabm > sin + scilabm = 0.660535 > > Now, if I uncomment everything: > > -->exec test_overload.sce; > printf('sin + scilabmyvar1 = %f\n',sin(myvar1)); > !--error 246 > Fonction non d?finie pour le type d'argument donn?. > > v?rifier les arguments ou d?finir la fonction %scilabmy_sin pour la > surcharge. > > at line 20 of exec file called by : > exec test_overload.sce; > > > Scilab sees only the type "scilabmy" (8 chars) and not the "scilabmyvar1" > > YC > From pawel.niechoda at gmail.com Thu Apr 2 21:14:34 2009 From: pawel.niechoda at gmail.com (=?ISO-8859-2?Q?Pawe=B3_Niechoda?=) Date: Thu, 2 Apr 2009 22:14:34 +0300 Subject: proposal - gsoc: Pretty print and export in Scilab Message-ID: <27cec44f0904021214y73d2bc68i8f5f180fc7fc2656@mail.gmail.com> Hi all I wrote down a draft of proposal about idea - Pretty print and export in Scilab. http://docs.google.com/Doc?id=df2wg5ch_29c5cbw3gn Everyone can look at it and give feedback. I will appreciate it. Pawe? Niechoda -------------- next part -------------- An HTML attachment was scrubbed... URL: From sylvestre.ledru at scilab.org Thu Apr 2 22:38:16 2009 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Thu, 02 Apr 2009 22:38:16 +0200 Subject: [Scilab-Dev] proposal - gsoc: Pretty print and export in Scilab In-Reply-To: <27cec44f0904021214y73d2bc68i8f5f180fc7fc2656@mail.gmail.com> References: <27cec44f0904021214y73d2bc68i8f5f180fc7fc2656@mail.gmail.com> Message-ID: <1238704696.7304.108.camel@zlarin> Hello Pawe?, Le jeudi 02 avril 2009 ? 22:14 +0300, Pawe? Niechoda a ?crit : > Hi all > > I wrote down a draft of proposal about idea - Pretty print and export > in Scilab. > http://docs.google.com/Doc?id=df2wg5ch_29c5cbw3gn > > Everyone can look at it and give feedback. I will appreciate it. A few comments, could you move to the gsoc interface. It is easier. Otherwise, could you add more example and technical description on our you are planning to do it ? Here is a good example of what is expected: http://www.dabeaz.com/cgi-bin/wiki.pl?GSoCPython3Proposal Don't forget that the deadline is tomorrow ! Sylvestre From pawel.niechoda at gmail.com Thu Apr 2 22:59:53 2009 From: pawel.niechoda at gmail.com (=?ISO-8859-2?Q?Pawe=B3_Niechoda?=) Date: Thu, 2 Apr 2009 23:59:53 +0300 Subject: [Scilab-Dev] proposal - gsoc: Pretty print and export in Scilab In-Reply-To: <1238704696.7304.108.camel@zlarin> References: <27cec44f0904021214y73d2bc68i8f5f180fc7fc2656@mail.gmail.com> <1238704696.7304.108.camel@zlarin> Message-ID: <27cec44f0904021359o1f49bf52gd0aed2cc89fb6518@mail.gmail.com> Ok thanks for feedback. I will try to add some more detailed information. Besides that I have already submited it to SoC. 2009/4/2 Sylvestre Ledru > Hello Pawe?, > Le jeudi 02 avril 2009 ? 22:14 +0300, Pawe? Niechoda a ?crit : > > Hi all > > > > I wrote down a draft of proposal about idea - Pretty print and export > > in Scilab. > > http://docs.google.com/Doc?id=df2wg5ch_29c5cbw3gn > > > > Everyone can look at it and give feedback. I will appreciate it. > A few comments, could you move to the gsoc interface. It is easier. > > Otherwise, could you add more example and technical description on our > you are planning to do it ? > Here is a good example of what is expected: > http://www.dabeaz.com/cgi-bin/wiki.pl?GSoCPython3Proposal > > Don't forget that the deadline is tomorrow ! > > Sylvestre > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhuyin.nju at gmail.com Fri Apr 3 07:39:17 2009 From: zhuyin.nju at gmail.com (Yin Zhu) Date: Fri, 3 Apr 2009 13:39:17 +0800 Subject: The LASSO proposal for GSoC 2009 Message-ID: Dear All, I've submitted the LASSO proposal to GSoC several days ago. This is missing feature in http://wiki.scilab.org/Missing_Mathematical_features_in_Scilab I have a good background in linear models. Could you give me some suggestions on the proposal? Thanks, -- Yin Zhu, Undergraduate Student of LAMDA Group, Nanjing University, China. http://lamda.nju.edu.cn E-Mail: zhuyin.nju at gmail.com or u-zhuy at lamda.nju.edu.cn -------------- next part -------------- An HTML attachment was scrubbed... URL: From derekhh at cse.ust.hk Sun Apr 5 08:08:45 2009 From: derekhh at cse.ust.hk (Derek Hao Hu) Date: Sun, 5 Apr 2009 14:08:45 +0800 Subject: About GSoC 2009 Program - MPFR/GMP Message-ID: <008601c9b5b4$fb495e40$f1dc1ac0$@ust.hk> To whom it may concern, I've submitted a proposal under the name "Hao Hu" on the project MPFR/GMP. And I had a comment from "Jonathan Blanchard" saying "Can you elaborate further on how you plan to implement your proposal?" Since I've already written a multiprecision library for myself in C++, I think there will be no major issues for me to implement these algorithms in SciLab. Can you tell me more about along which directions should I be anticipated to revise my proposal? Thanks! Regards, -- Derek Hao HU PhD Student Department of Computer Science and Engineering Hong Kong University of Science and Technology Clear Water Bay, Kowloon, Hong Kong Homepage: http://www.cse.ust.hk/~derekhh/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From BlanchardJ at ieee.org Sun Apr 5 14:20:08 2009 From: BlanchardJ at ieee.org (Jonathan Blanchard) Date: Sun, 5 Apr 2009 09:20:08 -0300 Subject: [Scilab-Dev] About GSoC 2009 Program - MPFR/GMP In-Reply-To: <008601c9b5b4$fb495e40$f1dc1ac0$@ust.hk> References: <008601c9b5b4$fb495e40$f1dc1ac0$@ust.hk> Message-ID: Hi, Simply put, more informations on the technical aspect of you proposal would be a plus for your proposition. Possibly including how you think this is going to be reflected in Scilab in term of functions and toolbox. Also any additional informations like a timeline or an implementation plan like the one in the example proposal. Finally if you have a rough idea of the structure of you code you may include if possible. http://www.dabeaz.com/cgi-bin/wiki.pl?GSoCPython3Proposal I wish you a good success with your proposal. Jonathan Blanchard On Sun, Apr 5, 2009 at 3:08 AM, Derek Hao Hu wrote: > To whom it may concern, > > I?ve submitted a proposal under the name ?Hao Hu? on the project MPFR/GMP. > And I had a comment from ?Jonathan Blanchard? saying ?Can you elaborate > further on how you plan to implement your proposal?? Since I?ve already > written a multiprecision library for myself in C++, I think there will be no > major issues for me to implement these algorithms in SciLab. Can you tell me > more about along which directions should I be anticipated to revise my > proposal? Thanks! > > Regards, > > -- > Derek Hao HU > > PhD Student > Department of Computer Science and Engineering > Hong Kong University of Science and Technology > Clear Water Bay, Kowloon, Hong Kong > Homepage: http://www.cse.ust.hk/~derekhh/ > > From mmorelli at users.sf.net Mon Apr 6 08:59:06 2009 From: mmorelli at users.sf.net (Matteo Morelli) Date: Mon, 06 Apr 2009 08:59:06 +0200 Subject: Header inclusion in external toolboxes source files (GNU/Linux) Message-ID: <49D9A83A.2040901@users.sf.net> Dear all, I'd like to point out two little issues I've encountered in applying the external contribs installation procedure in Scilab-5.x. In order to avoid a kilometric post, I decided to split my report in two separate mails. The following is the description of first little issue I dealt with. It only occurs by running Scilab-5.x under GNU/Linux. Let's take the toolbox skeleton and add to it the includes directory, which the header file "foo.h" has been defined in. If we modified the file src/c/csum.c as follows #include "../../includes/foo.h" /* header file inclusion */ int csum(double *a, double *b, double *c) { ... } and tried to build the toolbox, we'd get: [...] ilib_gen_Make: Copy csum.c to TMPDIR ilib_gen_Make: configure : Generate Makefile. ilib_gen_Make: Modification of the Makefile in TMPDIR. Running the Makefile ilib_compile: An error occured during the compilation: !csum.c:7:32: error: ../../includes/foo.h: No such file or directory ! ! ! !make: *** [csum.lo] Error 1 ! ilib_compile: The command was: make CFLAGS="-I/usr/local/share/scilab//../../include/scilab/malloc/ -I/usr/local/share/scilab//../../include/scilab/output_stream/ -I/usr/local/share/scilab//../../include/scilab/mexlib/ -I/usr/local/share/scilab//../../include/scilab/core/ " CXXFLAGS="-I/usr/local/share/scilab//../../include/scilab/malloc/ -I/usr/local/share/scilab//../../include/scilab/output_stream/ -I/usr/local/share/scilab//../../include/scilab/mexlib/ -I/usr/local/share/scilab//../../include/scilab/core/ " FFLAGS="-I/usr/local/share/scilab//../../include/scilab/core/ " [...] The error above occurs only under Linux, because ilib_gen_Make_unix() copies all *.c files from src/c to TMPDIR without caring about the headers the files include. Of course, you could expect the developers of toolboxes fix the problem by changing the file inclusion directive to #include , by adding something similar to the following directory search option to CFLAGS 1. "-I""" + tbx_src_path + "../../includes/""", in the Windows case or 2. "-I" + tbx_src_path + "../../includes/", in the GNU/Linux case, and, finally, by modifying the src builder with a piece of code like if MSDOS then ... 1. ... else ... 2. ... end That's just what I made to fix the problem with the toolbox skeleton. However, in my opinion, it would be better if Scilab handled the issue automatically. Any comments or suggestions? Regards, -- Matteo From mmorelli at users.sf.net Mon Apr 6 09:01:42 2009 From: mmorelli at users.sf.net (Matteo Morelli) Date: Mon, 06 Apr 2009 09:01:42 +0200 Subject: Inclusion of scicos_block4.h in external toolboxes source files Message-ID: <49D9A8D6.3030405@users.sf.net> Dear all, The following is the description of a second little issue I dealt with when running the external contribs installation procedure in Scilab-5.x (see http://lists.scilab.org/cgi-bin/ezmlm-browse?list=dev&cmd=threadindex&month=200904&threadid=gnflmlndbinnkpmaclij if you're interested in the first issue). It occurs both under Windows and under GNU/Linux. Let's take a generic toolbox "for Scilab/Scicos", i.e. a toolbox with both a Scilab and a Scicos part. It would be good if we could apply the standart method described at wiki.scilab.org/howto/Create_a_toolbox in this situation as well. As an example, let's suppose that the file src/c/csum.c in the toolbox skeleton needs to include the header file scicos_block4.h. we could do the following: #include /* header file inclusion */ int csum(double *a, double *b, double *c) { ... } In order to be able to build the toolbox, we also need to add to CFLAGS the following directory search option: 1. -I"$(SCIDIR)\modules\scicos_blocks\includes", in the Windows case or 2. -I$(SCIDIR)/../../include/scilab/scicos_blocks/, in the GNU/Linux case. Of course, you could say that is up to toolbox developers to handle this issue, by modifying the src builder with a piece of code like if MSDOS then ... 1. ... else ... 2. ... end However, in my opinion, it would be better if Scilab handled the issue automatically. For example, under Windows, just add line 1. to the INCLUDES variable in Makefile.incl.mak will do the job. A similar thing, I guess, could be done under GNU/Linux to change CFLAGS to something similar to CFLAGS="-I$(SCIDIR)/../../include/scilab/malloc/ -I$(SCIDIR)/../../include/scilab/output_stream/ -I$(SCIDIR)/../../include/scilab/mexlib/ -I$(SCIDIR)/../../include/scilab/core/ " CXXFLAGS="-I$(SCIDIR)/../../include/scilab/malloc/ -I$(SCIDIR)/../../include/scilab/output_stream/ -I$(SCIDIR)/../../include/scilab/mexlib/ -I$(SCIDIR)/../../include/scilab/core/ " FFLAGS="-I$(SCIDIR)/../../include/scilab/core/ -I$(SCIDIR)/../../include/scilab/scicos_blocks/ " where line 2. has been added to CFLAGS. What do you think about this "SEP"? comments or suggestions? Regards, -- Matteo From ycollet at freesurf.fr Mon Apr 6 09:04:21 2009 From: ycollet at freesurf.fr (ycollet at freesurf.fr) Date: Mon, 06 Apr 2009 09:04:21 +0200 Subject: [Scilab-Dev] Header inclusion in external toolboxes source files (GNU/Linux) In-Reply-To: <49D9A83A.2040901@users.sf.net> References: <49D9A83A.2040901@users.sf.net> Message-ID: <74538c1b51d7defa5813f0163b480dea@freesurf.fr> Hello, I agree with you. I needed to use the get_absolute_path('builder_c_gateway.sce') to add the path to the sci_gateway/c to get the .h included correctly by scilab during compilation. YC On Mon, 06 Apr 2009 08:59:06 +0200, Matteo Morelli wrote: > Dear all, > > I'd like to point out two little issues I've encountered in applying > the external contribs installation procedure in Scilab-5.x. In order to > avoid a kilometric post, I decided to split my report in two separate > mails. The following is the description of first little issue I dealt > with. It only occurs by running Scilab-5.x under GNU/Linux. > > Let's take the toolbox skeleton and add to it the includes directory, > which the header file "foo.h" has been defined in. If we modified the > file src/c/csum.c as follows > > #include "../../includes/foo.h" /* header file inclusion */ > int csum(double *a, double *b, double *c) > { > ... > } > > and tried to build the toolbox, we'd get: > > [...] > ilib_gen_Make: Copy csum.c to TMPDIR > ilib_gen_Make: configure : Generate Makefile. > ilib_gen_Make: Modification of the Makefile in TMPDIR. > Running the Makefile > ilib_compile: An error occured during the compilation: > > !csum.c:7:32: error: ../../includes/foo.h: No such file or directory ! > ! ! > !make: *** [csum.lo] Error 1 ! > > ilib_compile: The command was: > make > CFLAGS="-I/usr/local/share/scilab//../../include/scilab/malloc/ > -I/usr/local/share/scilab//../../include/scilab/output_stream/ > -I/usr/local/share/scilab//../../include/scilab/mexlib/ > -I/usr/local/share/scilab//../../include/scilab/core/ " > CXXFLAGS="-I/usr/local/share/scilab//../../include/scilab/malloc/ > -I/usr/local/share/scilab//../../include/scilab/output_stream/ > -I/usr/local/share/scilab//../../include/scilab/mexlib/ > -I/usr/local/share/scilab//../../include/scilab/core/ " > FFLAGS="-I/usr/local/share/scilab//../../include/scilab/core/ " > [...] > > The error above occurs only under Linux, because ilib_gen_Make_unix() > copies all *.c files from src/c to TMPDIR without caring about the > headers the files include. Of course, you could expect the developers of > toolboxes fix the problem by changing the file inclusion directive to > #include , by adding something similar to the following > directory search option to CFLAGS > > 1. "-I""" + tbx_src_path + "../../includes/""", in the Windows case > > or > > 2. "-I" + tbx_src_path + "../../includes/", in the GNU/Linux case, > > and, finally, by modifying the src builder with a piece of code like > > if MSDOS then > ... 1. ... > else > ... 2. ... > end > > That's just what I made to fix the problem with the toolbox skeleton. > However, in my opinion, it would be better if Scilab handled the issue > automatically. > > Any comments or suggestions? > > Regards, > > -- > Matteo > From ycollet at freesurf.fr Mon Apr 6 14:06:57 2009 From: ycollet at freesurf.fr (ycollet at freesurf.fr) Date: Mon, 06 Apr 2009 14:06:57 +0200 Subject: [Scilab-Dev] Inclusion of =?UTF-8?Q?scicos=5Fblock=34=2Eh=20in=20exte?= =?UTF-8?Q?rnal=20toolboxes=20source=20files?= In-Reply-To: <49D9A8D6.3030405@users.sf.net> References: <49D9A8D6.3030405@users.sf.net> Message-ID: <51754eb652e52fd594abac603c3b2e76@freesurf.fr> You should fill a bug report for both problems so as to leave a trail. See at http:/bugzilla.scilab.org YC On Mon, 06 Apr 2009 09:01:42 +0200, Matteo Morelli wrote: > Dear all, > > The following is the description of a second little issue I dealt with > when running the external contribs installation procedure in Scilab-5.x > (see > http://lists.scilab.org/cgi-bin/ezmlm-browse?list=dev&cmd=threadindex&month=200904&threadid=gnflmlndbinnkpmaclij > if you're interested in the first issue). It occurs both under Windows > and under GNU/Linux. > > Let's take a generic toolbox "for Scilab/Scicos", i.e. a toolbox with > both a Scilab and a Scicos part. It would be good if we could apply the > standart method described at wiki.scilab.org/howto/Create_a_toolbox in > this situation as well. As an example, let's suppose that the file > src/c/csum.c in the toolbox skeleton needs to include the header file > scicos_block4.h. we could do the following: > > #include /* header file inclusion */ > int csum(double *a, double *b, double *c) > { > ... > } > > In order to be able to build the toolbox, we also need to add to CFLAGS > the following directory search option: > > 1. -I"$(SCIDIR)\modules\scicos_blocks\includes", in the Windows case > > or > > 2. -I$(SCIDIR)/../../include/scilab/scicos_blocks/, in the GNU/Linux > case. > > Of course, you could say that is up to toolbox developers to handle > this issue, by modifying the src builder with a piece of code like > > if MSDOS then > ... 1. ... > else > ... 2. ... > end > > However, in my opinion, it would be better if Scilab handled the issue > automatically. For example, under Windows, just add line 1. to the > INCLUDES variable in Makefile.incl.mak will do the job. A similar thing, > I guess, could be done under GNU/Linux to change CFLAGS to something > similar to > > CFLAGS="-I$(SCIDIR)/../../include/scilab/malloc/ > -I$(SCIDIR)/../../include/scilab/output_stream/ > -I$(SCIDIR)/../../include/scilab/mexlib/ > -I$(SCIDIR)/../../include/scilab/core/ " > CXXFLAGS="-I$(SCIDIR)/../../include/scilab/malloc/ > -I$(SCIDIR)/../../include/scilab/output_stream/ > -I$(SCIDIR)/../../include/scilab/mexlib/ > -I$(SCIDIR)/../../include/scilab/core/ " > FFLAGS="-I$(SCIDIR)/../../include/scilab/core/ > -I$(SCIDIR)/../../include/scilab/scicos_blocks/ " > > where line 2. has been added to CFLAGS. > > What do you think about this "SEP"? comments or suggestions? > > Regards, > > -- > Matteo > From sylvestre.ledru at scilab.org Mon Apr 6 14:16:57 2009 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Mon, 06 Apr 2009 14:16:57 +0200 Subject: [Scilab-Dev] Inclusion of scicos_block4.h in external toolboxes source files In-Reply-To: <49D9A8D6.3030405@users.sf.net> References: <49D9A8D6.3030405@users.sf.net> Message-ID: <1239020217.27936.336.camel@korcula.inria.fr> I am trying to answer to both your emails since they are similar. [....] > #include "../../includes/foo.h" /* header file inclusion */ > int csum(double *a, double *b, double *c) > { > ... > } [....] In this case, if you add foo.h to the list of the files which must be compiled, it is going to copy the .h file to TMPDIR too and enable the capability of using #include "foo.h" > > The following is the description of a second little issue I dealt with > when running the external contribs installation procedure in Scilab-5.x > (see > http://lists.scilab.org/cgi-bin/ezmlm-browse?list=dev&cmd=threadindex&month=200904&threadid=gnflmlndbinnkpmaclij > if you're interested in the first issue). It occurs both under Windows > and under GNU/Linux. > > Let's take a generic toolbox "for Scilab/Scicos", i.e. a toolbox with > both a Scilab and a Scicos part. It would be good if we could apply the > standart method described at wiki.scilab.org/howto/Create_a_toolbox in > this situation as well. As an example, let's suppose that the file > src/c/csum.c in the toolbox skeleton needs to include the header file > scicos_block4.h. we could do the following: > > #include /* header file inclusion */ > int csum(double *a, double *b, double *c) > { > ... > } > > In order to be able to build the toolbox, we also need to add to CFLAGS > the following directory search option: > > 1. -I"$(SCIDIR)\modules\scicos_blocks\includes", in the Windows case > > or > > 2. -I$(SCIDIR)/../../include/scilab/scicos_blocks/, in the GNU/Linux > case. Yep, it is pretty painful for the toolbox developer. > Of course, you could say that is up to toolbox developers to handle > this issue, by modifying the src builder with a piece of code like > > if MSDOS then > ... 1. ... > else > ... 2. ... > end > > However, in my opinion, it would be better if Scilab handled the issue > automatically. Yep, we should do something. However, we cannot add all the include directories in the XXXFLAGS... it is the same bug problem as in bug #4146 [1]. I had the idea to install all include files into the same directory. Unfortunately, it has two issues: * we have to make sure that here is no two include files with the same name (it is easy to do) * This will break toolboxes doing include with relative path like in your example "../../includes/scicos_block/scicos_block4.h" Sylvestre [1] http://bugzilla.scilab.org/show_bug.cgi?id=4146 From knutmann at gmail.com Tue Apr 7 01:11:00 2009 From: knutmann at gmail.com (=?ISO-8859-1?Q?Christian_M=FCller?=) Date: Tue, 7 Apr 2009 01:11:00 +0200 Subject: mac version Message-ID: <7997B2D5-0F56-452E-8629-E0B2B38476FB@gmail.com> Hi. The mac version of scilab has incorrect library bindings. They refer to a user named 'pmarecha'. Noone except pmarecha can run this unless they change all bindings with install_name_tool. Thanks, Knut otool -L scilab-bin scilab-bin: /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 12.0.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscilab.0.dylib (compatibility version 1.0.0, current version 1.0.0) /System/Library/Frameworks/Accelerate.framework/Versions/A/ Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib (compatibility version 1.0.0, current version 218.0.0) /System/Library/Frameworks/Accelerate.framework/Versions/A/ Frameworks/vecLib.framework/Versions/A/libBLAS.dylib (compatibility version 1.0.0, current version 218.0.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscidouble.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciboolean. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscigraphic_export. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscilocalization. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/ libscispecial_functions.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciwindows_tools. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscipvm.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciconsole. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscishell.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscicompletion. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscisound.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscihelptools. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscimatio.0.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/local/matio-1.3.3/lib/libmatio.0.dylib (compatibility version 1.0.0, current version 1.0.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscirandlib. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscioptimization. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscisymbolic. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscimetanet. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscispreadsheet. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscistatistics. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/ libscisignal_processing.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciinterpolation. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscifftw.5.dylib (compatibility version 6.0.0, current version 6.1.0) /usr/local/fftw-3.2/lib/libfftw3.3.dylib (compatibility version 6.0.0, current version 6.2.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciumfpack. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscisparse.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciio.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscijvm.5.dylib (compatibility version 6.0.0, current version 6.1.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.3) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciscicos.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciintersci. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscitime.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscisundials. 0.dylib (compatibility version 1.0.0, current version 1.0.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciscicos_blocks. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscigraphics. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscigui.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscirenderer. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscipolynomials. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscicacsd.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libmx.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libmat.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/ libscidifferential_equations.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libmex.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/ libscidata_structures.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscilinear_algebra. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscidynamic_link. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscidynamiclibrary. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscihashtable. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/ libscidoublylinkedlist.5.dylib (compatibility version 6.0.0, current version 6.1.0) /sw/lib/ncurses/libncurses.5.dylib (compatibility version 5.0.0, current version 5.0.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/ libscihistory_manager.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscicore.5.dylib (compatibility version 6.0.0, current version 6.1.0) /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ Libraries/libclient.dylib (compatibility version 1.0.0, current version 1.0.0) /sw/lib/libintl.3.dylib (compatibility version 8.0.0, current version 8.3.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscitclsci.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciaction_binding. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciinteger. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscifileio.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscilibst.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscistring.5.dylib (compatibility version 6.0.0, current version 6.1.0) /usr/local/pcre-7.6/lib/libpcreposix.0.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/local/pcre-7.6/lib/libpcre.0.dylib (compatibility version 1.0.0, current version 1.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/ libscielementary_functions.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciarnoldi. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /sw/lib/libxml2.2.dylib (compatibility version 9.0.0, current version 9.30.0) /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3) /sw/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscimalloc.5.dylib (compatibility version 6.0.0, current version 6.1.0) /Users/pmarecha/compilation_chain_macosx/sci_binary/ scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscioutput_stream. 5.dylib (compatibility version 6.0.0, current version 6.1.0) /usr/local/lib/libgfortran.3.dylib (compatibility version 4.0.0, current version 4.0.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) From sylvestre.ledru at scilab.org Tue Apr 7 01:20:01 2009 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Tue, 07 Apr 2009 01:20:01 +0200 Subject: [Scilab-Dev] mac version In-Reply-To: <7997B2D5-0F56-452E-8629-E0B2B38476FB@gmail.com> References: <7997B2D5-0F56-452E-8629-E0B2B38476FB@gmail.com> Message-ID: <1239060001.4602.106.camel@zlarin> Le mardi 07 avril 2009 ? 01:11 +0200, Christian M?ller a ?crit : > Hi. > > The mac version of scilab has incorrect library bindings. They refer > to a user named 'pmarecha'. > Noone except pmarecha can run this unless they change all bindings > with install_name_tool. It is interesting. It is working for me (despite I don't have any pmarecha account on my Mac) and we have report that Scilab is working. You are using the official binary available on Scilab's website ? Sylvestre > Thanks, Knut > > > otool -L scilab-bin scilab-bin: > /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa > (compatibility version 1.0.0, current version 12.0.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscilab.0.dylib > (compatibility version 1.0.0, current version 1.0.0) > /System/Library/Frameworks/Accelerate.framework/Versions/A/ > Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib (compatibility > version 1.0.0, current version 218.0.0) > /System/Library/Frameworks/Accelerate.framework/Versions/A/ > Frameworks/vecLib.framework/Versions/A/libBLAS.dylib (compatibility > version 1.0.0, current version 218.0.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscidouble.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciboolean. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscigraphic_export. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscilocalization. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/ > libscispecial_functions.5.dylib (compatibility version 6.0.0, current > version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciwindows_tools. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscipvm.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciconsole. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscishell.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscicompletion. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscisound.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscihelptools. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscimatio.0.dylib > (compatibility version 1.0.0, current version 1.0.0) > /usr/local/matio-1.3.3/lib/libmatio.0.dylib (compatibility > version 1.0.0, current version 1.0.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscirandlib. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscioptimization. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscisymbolic. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscimetanet. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscispreadsheet. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscistatistics. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/ > libscisignal_processing.5.dylib (compatibility version 6.0.0, current > version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciinterpolation. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscifftw.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /usr/local/fftw-3.2/lib/libfftw3.3.dylib (compatibility > version 6.0.0, current version 6.2.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciumfpack. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscisparse.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciio.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscijvm.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, > current version 111.1.3) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciscicos.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciintersci. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscitime.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscisundials. > 0.dylib (compatibility version 1.0.0, current version 1.0.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciscicos_blocks. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscigraphics. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscigui.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscirenderer. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscipolynomials. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscicacsd.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libmx.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libmat.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/ > libscidifferential_equations.5.dylib (compatibility version 6.0.0, > current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libmex.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/ > libscidata_structures.5.dylib (compatibility version 6.0.0, current > version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscilinear_algebra. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscidynamic_link. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscidynamiclibrary. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscihashtable. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/ > libscidoublylinkedlist.5.dylib (compatibility version 6.0.0, current > version 6.1.0) > /sw/lib/ncurses/libncurses.5.dylib (compatibility version > 5.0.0, current version 5.0.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/ > libscihistory_manager.5.dylib (compatibility version 6.0.0, current > version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscicore.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/ > Libraries/libclient.dylib (compatibility version 1.0.0, current > version 1.0.0) > /sw/lib/libintl.3.dylib (compatibility version 8.0.0, > current version 8.3.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscitclsci.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciaction_binding. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciinteger. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscifileio.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscilibst.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscistring.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /usr/local/pcre-7.6/lib/libpcreposix.0.dylib (compatibility > version 1.0.0, current version 1.0.0) > /usr/local/pcre-7.6/lib/libpcre.0.dylib (compatibility > version 1.0.0, current version 1.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/ > libscielementary_functions.5.dylib (compatibility version 6.0.0, > current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libsciarnoldi. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /sw/lib/libxml2.2.dylib (compatibility version 9.0.0, > current version 9.30.0) > /usr/lib/libz.1.dylib (compatibility version 1.0.0, current > version 1.2.3) > /sw/lib/libiconv.2.dylib (compatibility version 7.0.0, > current version 7.0.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscimalloc.5.dylib > (compatibility version 6.0.0, current version 6.1.0) > /Users/pmarecha/compilation_chain_macosx/sci_binary/ > scilab-5.1-alpha-1.app/Contents/MacOS/lib/scilab/libscioutput_stream. > 5.dylib (compatibility version 6.0.0, current version 6.1.0) > /usr/local/lib/libgfortran.3.dylib (compatibility version > 4.0.0, current version 4.0.0) > /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, > current version 1.0.0) > From sylvestre.ledru at scilab.org Tue Apr 7 16:57:01 2009 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Tue, 07 Apr 2009 16:57:01 +0200 Subject: Google Summer of Code Update Message-ID: <1239116221.13145.15.camel@korcula.inria.fr> Hello, Just a quick email to let you know that for the first time, it has been a success from the "proposal point of view". We have 59 proposals (which is a lot compared to many projects). The most famous proposals have been pretty print, neural network, databases and symbolic computing. The next step is to sort the proposals before submitting them to Google and assign mentors. It is going to be hard to select the best proposals and projects!! We hope we will get from 4 to 6 slots from Google... We will see how it goes! As usual, don't hesitate if you have any questions, Sylvestre PS: the timeline is available here: http://socghop.appspot.com/document/show/program/google/gsoc2009/timeline From ycollet at freesurf.fr Wed Apr 8 16:18:50 2009 From: ycollet at freesurf.fr (Collette Yann) Date: Wed, 08 Apr 2009 16:18:50 +0200 Subject: XXE: add a link in a howto section Message-ID: <49DCB24A.5010106@freesurf.fr> Hello, I am currently writing a doc in xml and I have a problem: How do I add a link in a howto refsection ? For now, each time I have to add a link in the how to refsection, I edit the xml file via emacs and add this link manually. This should be doable with xxe, but I can't see how to do this. YC From michael.baudin at scilab.org Thu Apr 9 15:25:41 2009 From: michael.baudin at scilab.org (=?ISO-8859-1?Q?Micha=EBl_Baudin?=) Date: Thu, 09 Apr 2009 15:25:41 +0200 Subject: Nelder - Mead Algorithm Message-ID: <49DDF755.2010002@scilab.org> Hi, Several users requested a way to perform optimizations in Scilab with a tool similar to the fminsearch Matlab command. The SEP in attachment is a proposal for such a tool. A prototype is currently available, with the following features: * emulates the fminsearch command with the same numerical parameters and algorithm as Matlab's fminsearch, * Box's complex method with bound constraints and non linear inequality constraints, * oriented simplex restart (and variants) with automatic stagnation detection by O'Neill or Kelley criteria, * many other features and options... Numerical experiments show that the current prototype is able to reproduce exactly the behaviour of Matlab's fminsearch, including the initial simplex, the intermediate simplices and the final simplex at optimum. It allows to reproduce the behaviour analysed by Kelley on the Mc Kinnon couterexample. It behaves reasonably well on problems with bounds and non linear inequality constraints. Several improvements are possible on this algorithm : comments and suggestions are welcome ! Best regards, Micha?l Baudin -------------- next part -------------- A non-text attachment was scrubbed... Name: SEP_21_neldermead.odt Type: application/vnd.oasis.opendocument.text Size: 53477 bytes Desc: not available URL: From michael.baudin at scilab.org Fri Apr 10 10:57:32 2009 From: michael.baudin at scilab.org (=?ISO-8859-1?Q?Micha=EBl_Baudin?=) Date: Fri, 10 Apr 2009 10:57:32 +0200 Subject: SEP : Sorting in Scilab Message-ID: <49DF09FC.7050409@scilab.org> Hi, In this SEP, we discuss the improvement of the gsort command. We discuss the possibility to sort matrices containing complex numbers by real part order first, and imaginary part second. We also discuss the possibility to pass a Scilab comparison function as a second input argument of the gsort command. Comments and suggestions are welcome ! Best regards, Micha?l Baudin -------------- next part -------------- A non-text attachment was scrubbed... Name: SEP_21_gsort.odt Type: application/vnd.oasis.opendocument.text Size: 21940 bytes Desc: not available URL: From michael.baudin at scilab.org Fri Apr 10 11:00:46 2009 From: michael.baudin at scilab.org (=?ISO-8859-1?Q?Micha=EBl_Baudin?=) Date: Fri, 10 Apr 2009 11:00:46 +0200 Subject: SEP : Sparse preconditionners and Matrix Market Message-ID: <49DF0ABE.8040209@scilab.org> Hi, In this SEP, we discuss the update of several toolboxes which are used when processing sparse matrices. The first one, Scilin, provides sparse iterative algorithms for linear algebra. The second one, MatrixMarket, provides commands to read, write and quiery sparse matrices stored in the Matrix Market format, a text-based format for sparse matrices. As always, comments and suggestions are welcome ! Best regards, Micha?l Baudin -------------- next part -------------- A non-text attachment was scrubbed... Name: SEP_20_sparsepreconditionners.odt Type: application/vnd.oasis.opendocument.text Size: 25425 bytes Desc: not available URL: From kunigami at gmail.com Fri Apr 10 16:44:56 2009 From: kunigami at gmail.com (Guilherme Kunigami) Date: Fri, 10 Apr 2009 11:44:56 -0300 Subject: Beginner in Scilab Message-ID: <1fd0e24c0904100744w52f8930bt7ed2763f7f8308f5@mail.gmail.com> Hi all, I'd like to start developing something for Scilab, but I'm not quite sure from where to start. I've downloaded the source code (I think this is not the latest version though) and took a look at some source code from modules (e.g. gui module). But I still don't know much about the architecture of Scilab or how it works. Documents I've tried to read: http://www.scilab.org/developers/doxygen_scilab/index.html http://wiki.scilab.org/Developers I also tried to look for some bugs. This one seems quite simple to fix: http://bugzilla.scilab.org/show_bug.cgi?id=3264 but I'm not sure on how to proceed. I'd like to ask for some help on what can I do to start slow and learn more about Scilab code. Thanks, -- Guilherme Kunigami -------------- next part -------------- An HTML attachment was scrubbed... URL: From sylvestre.ledru at scilab.org Fri Apr 10 16:50:55 2009 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Fri, 10 Apr 2009 16:50:55 +0200 Subject: [Scilab-Dev] Beginner in Scilab In-Reply-To: <1fd0e24c0904100744w52f8930bt7ed2763f7f8308f5@mail.gmail.com> References: <1fd0e24c0904100744w52f8930bt7ed2763f7f8308f5@mail.gmail.com> Message-ID: <1239375055.16189.202.camel@korcula.inria.fr> Hello Guilherme, Le vendredi 10 avril 2009 ? 11:44 -0300, Guilherme Kunigami a ?crit : > Hi all, > > I'd like to start developing something for Scilab, but I'm not quite > sure from where to start. Cool! > I've downloaded the source code (I think this is not the latest > version though) and took a look at some source code from modules (e.g. > gui module). But I still don't know much about the architecture of > Scilab or how it works. We are using git to manage the source. If you clone the current git, you will get the future version 5.2 of Scilab. You can also checkout the branch 5.1 to get the future version 5.1.1. > Documents I've tried to read: > > http://www.scilab.org/developers/doxygen_scilab/index.html Well, don't start with that. It is hard to start understanding a software with the whole documentation. > http://wiki.scilab.org/Developers > > I also tried to look for some bugs. This one seems quite simple to > fix: > > http://bugzilla.scilab.org/show_bug.cgi?id=3264 > > but I'm not sure on how to proceed. Indeed, this one is easy. You just have to find out where these strings are in the code (grep is your friend) and to remplace them by better. After that, if you want to get familiar with Scilab, you need to have an objective in Scilab. It is a huge software with many different aspects... Just focus on some parts. Don't hesitate if you have any other questions/remarks... Sylvestre From ycollet at freesurf.fr Fri Apr 10 17:01:06 2009 From: ycollet at freesurf.fr (Collette Yann) Date: Fri, 10 Apr 2009 17:01:06 +0200 Subject: Nelder - Mead Algorithm In-Reply-To: <49DDF755.2010002@scilab.org> References: <49DDF755.2010002@scilab.org> Message-ID: <49DF5F32.6010709@freesurf.fr> Look OK for me. The thing very important to me is to be able to initialise fminsearch with our own simplex. fminsearch has not such a functionnality and if inputs variables have very different scale of variations, then the initial simplex, as created by fminsearch, will be degenerated. The Kelley restart is a plus. It allows to accelerate in some cases the convergence of the nelder and mead method. The optimization method implemented in my simplex-2.0 toolbox is a little bit special. It allows to "record" the state of the simplex and stop to ask the user to do a computation. With the step_nelder_mead, all the call to the objective function are done by the user. With the optim_nelder_mead, you ship the objective function to the method and optim_nelder_mead call by himself the objective function I will add somes tests in the simplex-2.0 toolbox. I've got a lot of test problems ... YC Micha?l Baudin a ?crit : > Hi, > > Several users requested a way to perform optimizations in Scilab with a > tool similar to the fminsearch Matlab command. > The SEP in attachment is a proposal for such a tool. > > A prototype is currently available, with the following features: > * emulates the fminsearch command with the same numerical > parameters and algorithm as Matlab's fminsearch, > * Box's complex method with bound constraints and non linear > inequality constraints, > * oriented simplex restart (and variants) with automatic > stagnation detection by O'Neill or Kelley criteria, > * many other features and options... > > Numerical experiments show that the current prototype is able > to reproduce exactly the behaviour of Matlab's fminsearch, including > the initial simplex, the intermediate simplices and the final simplex > at optimum. It allows to reproduce the behaviour analysed by Kelley > on the Mc Kinnon couterexample. It behaves reasonably well on > problems with bounds and non linear inequality constraints. > > Several improvements are possible on this algorithm : > comments and suggestions are welcome ! > > Best regards, > > Micha?l Baudin > From kunigami at gmail.com Fri Apr 10 20:22:42 2009 From: kunigami at gmail.com (Guilherme Kunigami) Date: Fri, 10 Apr 2009 15:22:42 -0300 Subject: [Scilab-Dev] Beginner in Scilab In-Reply-To: <1239375055.16189.202.camel@korcula.inria.fr> References: <1fd0e24c0904100744w52f8930bt7ed2763f7f8308f5@mail.gmail.com> <1239375055.16189.202.camel@korcula.inria.fr> Message-ID: <1fd0e24c0904101122l6763dbckf6c848752d7f2e21@mail.gmail.com> Hi again, I think I got the latest version using GIT, but this time I'm not being able to compile it. When I run 'make' I get some dependence errors. I think the relevant messages are these: http://pastebin.com/f4a117ca3 It seems I'm missing libjava.so, libverify.so, libjvm.so and libhpi.so at /usr/bin/ld. Executing a 'locate libjava.so' it show that I have this file at the following locations: /home/kunigami/downloads/scilab-5.1/java/jdk1.6.0_11/jre/lib/i386/libjava.so /home/kunigami/downloads/scilab-5.1/java/jre1.6.0_11/lib/i386/libjava.so /usr/lib/jvm/java-6-sun-1.6.0.10/jre/lib/i386/libjava.so The first two locations refer to a package I downloaded from Scilab page because of dependencies (but I haven't used those yet). I thought that setting the third location at $LD_LIBRARY_PATH would solve the problem, but that still give me some errors. I'm able to compile the stable version perfectly, but not the git version. Any clues? Thank you again, On Fri, Apr 10, 2009 at 11:50 AM, Sylvestre Ledru < sylvestre.ledru at scilab.org> wrote: > Hello Guilherme, > > Le vendredi 10 avril 2009 ? 11:44 -0300, Guilherme Kunigami a ?crit : > > Hi all, > > > > I'd like to start developing something for Scilab, but I'm not quite > > sure from where to start. > Cool! > > > I've downloaded the source code (I think this is not the latest > > version though) and took a look at some source code from modules (e.g. > > gui module). But I still don't know much about the architecture of > > Scilab or how it works. > We are using git to manage the source. If you clone the current git, you > will get the future version 5.2 of Scilab. You can also checkout the > branch 5.1 to get the future version 5.1.1. > > > Documents I've tried to read: > > > > http://www.scilab.org/developers/doxygen_scilab/index.html > Well, don't start with that. It is hard to start understanding a > software with the whole documentation. > > > http://wiki.scilab.org/Developers > > > > I also tried to look for some bugs. This one seems quite simple to > > fix: > > > > http://bugzilla.scilab.org/show_bug.cgi?id=3264 > > > > but I'm not sure on how to proceed. > Indeed, this one is easy. > You just have to find out where these strings are in the code (grep is > your friend) and to remplace them by better. > > After that, if you want to get familiar with Scilab, you need to have an > objective in Scilab. It is a huge software with many different > aspects... Just focus on some parts. > > Don't hesitate if you have any other questions/remarks... > > Sylvestre > > > -- Guilherme Kunigami -------------- next part -------------- An HTML attachment was scrubbed... URL: From kunigami at gmail.com Sat Apr 11 00:18:06 2009 From: kunigami at gmail.com (Guilherme Kunigami) Date: Fri, 10 Apr 2009 19:18:06 -0300 Subject: [Scilab-Dev] Beginner in Scilab In-Reply-To: <1fd0e24c0904101122l6763dbckf6c848752d7f2e21@mail.gmail.com> References: <1fd0e24c0904100744w52f8930bt7ed2763f7f8308f5@mail.gmail.com> <1239375055.16189.202.camel@korcula.inria.fr> <1fd0e24c0904101122l6763dbckf6c848752d7f2e21@mail.gmail.com> Message-ID: <1fd0e24c0904101518u151d734di989e675fb5dcbe93@mail.gmail.com> Hi, Sorry if I'm being inconvenient, but I'm really stuck. I tried some other things: I included in my $LD_LIBRARY_PATH the directories for libjava.so, libverify.so and libhpi.so. The error I get now is: http://pastebin.com/f1f57518f I'm not sure why the system is searching for the file in: > /usr/local/lib/scilab/libscilinear_algebra.so since it should be looked for in: > /home/kunigami/development/scilab/scilab/modules/linear_algebra/.libs/libscilinear_algebra.so Should I uninstall my installed copy of scilab to use the development version? Thanks, On Fri, Apr 10, 2009 at 3:22 PM, Guilherme Kunigami wrote: > Hi again, > > I think I got the latest version using GIT, but this time I'm not being > able to compile it. When I run 'make' I get some dependence errors. I think > the relevant messages are these: > > http://pastebin.com/f4a117ca3 > > It seems I'm missing libjava.so, libverify.so, libjvm.so and libhpi.so at > /usr/bin/ld. > > Executing a 'locate libjava.so' it show that I have this file at the > following locations: > > > /home/kunigami/downloads/scilab-5.1/java/jdk1.6.0_11/jre/lib/i386/libjava.so > /home/kunigami/downloads/scilab-5.1/java/jre1.6.0_11/lib/i386/libjava.so > /usr/lib/jvm/java-6-sun-1.6.0.10/jre/lib/i386/libjava.so > > The first two locations refer to a package I downloaded from Scilab page > because of dependencies (but I haven't used those yet). I thought that > setting the third location at $LD_LIBRARY_PATH would solve the problem, but > that still give me some errors. > > I'm able to compile the stable version perfectly, but not the git version. > Any clues? > > Thank you again, > > > On Fri, Apr 10, 2009 at 11:50 AM, Sylvestre Ledru < > sylvestre.ledru at scilab.org> wrote: > >> Hello Guilherme, >> >> Le vendredi 10 avril 2009 ? 11:44 -0300, Guilherme Kunigami a ?crit : >> > Hi all, >> > >> > I'd like to start developing something for Scilab, but I'm not quite >> > sure from where to start. >> Cool! >> >> > I've downloaded the source code (I think this is not the latest >> > version though) and took a look at some source code from modules (e.g. >> > gui module). But I still don't know much about the architecture of >> > Scilab or how it works. >> We are using git to manage the source. If you clone the current git, you >> will get the future version 5.2 of Scilab. You can also checkout the >> branch 5.1 to get the future version 5.1.1. >> >> > Documents I've tried to read: >> > >> > http://www.scilab.org/developers/doxygen_scilab/index.html >> Well, don't start with that. It is hard to start understanding a >> software with the whole documentation. >> >> > http://wiki.scilab.org/Developers >> > >> > I also tried to look for some bugs. This one seems quite simple to >> > fix: >> > >> > http://bugzilla.scilab.org/show_bug.cgi?id=3264 >> > >> > but I'm not sure on how to proceed. >> Indeed, this one is easy. >> You just have to find out where these strings are in the code (grep is >> your friend) and to remplace them by better. >> >> After that, if you want to get familiar with Scilab, you need to have an >> objective in Scilab. It is a huge software with many different >> aspects... Just focus on some parts. >> >> Don't hesitate if you have any other questions/remarks... >> >> Sylvestre >> >> >> > > > -- > Guilherme Kunigami > -- Guilherme Kunigami -------------- next part -------------- An HTML attachment was scrubbed... URL: From sylvestre.ledru at inria.fr Sat Apr 11 01:28:12 2009 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Sat, 11 Apr 2009 01:28:12 +0200 Subject: [Scilab-Dev] Beginner in Scilab In-Reply-To: <1fd0e24c0904101518u151d734di989e675fb5dcbe93@mail.gmail.com> References: <1fd0e24c0904100744w52f8930bt7ed2763f7f8308f5@mail.gmail.com> <1239375055.16189.202.camel@korcula.inria.fr> <1fd0e24c0904101122l6763dbckf6c848752d7f2e21@mail.gmail.com> <1fd0e24c0904101518u151d734di989e675fb5dcbe93@mail.gmail.com> Message-ID: <1239406092.10153.175.camel@zlarin> Le vendredi 10 avril 2009 ? 19:18 -0300, Guilherme Kunigami a ?crit : > Hi, > > Sorry if I'm being inconvenient, but I'm really stuck. Don't worry. We all have been beginners with Scilab ... and we are here to help! > I tried some other things: > > I included in my $LD_LIBRARY_PATH the directories for libjava.so, > libverify.so and libhpi.so. It was just a warning. No big deal! > The error I get now is: > > http://pastebin.com/f1f57518f > > I'm not sure why the system is searching for the file in: > > > /usr/local/lib/scilab/libscilinear_algebra.so > > since it should be looked for in: > > > /home/kunigami/development/scilab/scilab/modules/linear_algebra/.libs/libscilinear_algebra.so Indeed. > Should I uninstall my installed copy of scilab to use the development > version? Yep, please try this solution. However, that is a bug. The build system should try to load first the current source tree and not /usr/local/ I reported it here: http://bugzilla.scilab.org/show_bug.cgi?id=4382 Sylvestre > Thanks, > > On Fri, Apr 10, 2009 at 3:22 PM, Guilherme Kunigami > wrote: > Hi again, > > I think I got the latest version using GIT, but this time I'm > not being able to compile it. When I run 'make' I get some > dependence errors. I think the relevant messages are these: > > http://pastebin.com/f4a117ca3 > > It seems I'm missing libjava.so, libverify.so, libjvm.so and > libhpi.so at /usr/bin/ld. > > Executing a 'locate libjava.so' it show that I have this file > at the following locations: > > /home/kunigami/downloads/scilab-5.1/java/jdk1.6.0_11/jre/lib/i386/libjava.so > /home/kunigami/downloads/scilab-5.1/java/jre1.6.0_11/lib/i386/libjava.so > /usr/lib/jvm/java-6-sun-1.6.0.10/jre/lib/i386/libjava.so > > The first two locations refer to a package I downloaded from > Scilab page because of dependencies (but I haven't used those > yet). I thought that setting the third location at > $LD_LIBRARY_PATH would solve the problem, but that still give > me some errors. > > I'm able to compile the stable version perfectly, but not the > git version. Any clues? > > Thank you again, > > > > On Fri, Apr 10, 2009 at 11:50 AM, Sylvestre Ledru > wrote: > Hello Guilherme, > > Le vendredi 10 avril 2009 ? 11:44 -0300, Guilherme > Kunigami a ?crit : > > Hi all, > > > > I'd like to start developing something for Scilab, > but I'm not quite > > sure from where to start. > > Cool! > > > I've downloaded the source code (I think this is not > the latest > > version though) and took a look at some source code > from modules (e.g. > > gui module). But I still don't know much about the > architecture of > > Scilab or how it works. > > We are using git to manage the source. If you clone > the current git, you > will get the future version 5.2 of Scilab. You can > also checkout the > branch 5.1 to get the future version 5.1.1. > > > Documents I've tried to read: > > > > > http://www.scilab.org/developers/doxygen_scilab/index.html > > Well, don't start with that. It is hard to start > understanding a > software with the whole documentation. > > > http://wiki.scilab.org/Developers > > > > I also tried to look for some bugs. This one seems > quite simple to > > fix: > > > > http://bugzilla.scilab.org/show_bug.cgi?id=3264 > > > > but I'm not sure on how to proceed. > > Indeed, this one is easy. > You just have to find out where these strings are in > the code (grep is > your friend) and to remplace them by better. > > After that, if you want to get familiar with Scilab, > you need to have an > objective in Scilab. It is a huge software with many > different > aspects... Just focus on some parts. > > Don't hesitate if you have any other > questions/remarks... > > Sylvestre > > > > > > > -- > Guilherme Kunigami > > > > -- > Guilherme Kunigami From kunigami at gmail.com Sat Apr 11 01:49:00 2009 From: kunigami at gmail.com (Guilherme Kunigami) Date: Fri, 10 Apr 2009 20:49:00 -0300 Subject: [Scilab-Dev] Beginner in Scilab In-Reply-To: <1239406092.10153.175.camel@zlarin> References: <1fd0e24c0904100744w52f8930bt7ed2763f7f8308f5@mail.gmail.com> <1239375055.16189.202.camel@korcula.inria.fr> <1fd0e24c0904101122l6763dbckf6c848752d7f2e21@mail.gmail.com> <1fd0e24c0904101518u151d734di989e675fb5dcbe93@mail.gmail.com> <1239406092.10153.175.camel@zlarin> Message-ID: <1fd0e24c0904101649w7719cb11v21e1555fa0e02a4f@mail.gmail.com> Removing my installed version did the trick! Thank you for your help! On Fri, Apr 10, 2009 at 8:28 PM, Sylvestre Ledru wrote: > Le vendredi 10 avril 2009 ? 19:18 -0300, Guilherme Kunigami a ?crit : > > Hi, > > > > Sorry if I'm being inconvenient, but I'm really stuck. > Don't worry. We all have been beginners with Scilab ... and we are here > to help! > > > I tried some other things: > > > > I included in my $LD_LIBRARY_PATH the directories for libjava.so, > > libverify.so and libhpi.so. > It was just a warning. No big deal! > > > The error I get now is: > > > > http://pastebin.com/f1f57518f > > > > I'm not sure why the system is searching for the file in: > > > > > /usr/local/lib/scilab/libscilinear_algebra.so > > > > since it should be looked for in: > > > > > > /home/kunigami/development/scilab/scilab/modules/linear_algebra/.libs/libscilinear_algebra.so > Indeed. > > > Should I uninstall my installed copy of scilab to use the development > > version? > Yep, please try this solution. > However, that is a bug. The build system should try to load first the > current source tree and not /usr/local/ > I reported it here: > http://bugzilla.scilab.org/show_bug.cgi?id=4382 > > Sylvestre > > > > Thanks, > > > > On Fri, Apr 10, 2009 at 3:22 PM, Guilherme Kunigami > > wrote: > > Hi again, > > > > I think I got the latest version using GIT, but this time I'm > > not being able to compile it. When I run 'make' I get some > > dependence errors. I think the relevant messages are these: > > > > http://pastebin.com/f4a117ca3 > > > > It seems I'm missing libjava.so, libverify.so, libjvm.so and > > libhpi.so at /usr/bin/ld. > > > > Executing a 'locate libjava.so' it show that I have this file > > at the following locations: > > > > > /home/kunigami/downloads/scilab-5.1/java/jdk1.6.0_11/jre/lib/i386/libjava.so > > > /home/kunigami/downloads/scilab-5.1/java/jre1.6.0_11/lib/i386/libjava.so > > /usr/lib/jvm/java-6-sun-1.6.0.10/jre/lib/i386/libjava.so > > > > The first two locations refer to a package I downloaded from > > Scilab page because of dependencies (but I haven't used those > > yet). I thought that setting the third location at > > $LD_LIBRARY_PATH would solve the problem, but that still give > > me some errors. > > > > I'm able to compile the stable version perfectly, but not the > > git version. Any clues? > > > > Thank you again, > > > > > > > > On Fri, Apr 10, 2009 at 11:50 AM, Sylvestre Ledru > > wrote: > > Hello Guilherme, > > > > Le vendredi 10 avril 2009 ? 11:44 -0300, Guilherme > > Kunigami a ?crit : > > > Hi all, > > > > > > I'd like to start developing something for Scilab, > > but I'm not quite > > > sure from where to start. > > > > Cool! > > > > > I've downloaded the source code (I think this is not > > the latest > > > version though) and took a look at some source code > > from modules (e.g. > > > gui module). But I still don't know much about the > > architecture of > > > Scilab or how it works. > > > > We are using git to manage the source. If you clone > > the current git, you > > will get the future version 5.2 of Scilab. You can > > also checkout the > > branch 5.1 to get the future version 5.1.1. > > > > > Documents I've tried to read: > > > > > > > > > http://www.scilab.org/developers/doxygen_scilab/index.html > > > > Well, don't start with that. It is hard to start > > understanding a > > software with the whole documentation. > > > > > http://wiki.scilab.org/Developers > > > > > > I also tried to look for some bugs. This one seems > > quite simple to > > > fix: > > > > > > http://bugzilla.scilab.org/show_bug.cgi?id=3264 > > > > > > but I'm not sure on how to proceed. > > > > Indeed, this one is easy. > > You just have to find out where these strings are in > > the code (grep is > > your friend) and to remplace them by better. > > > > After that, if you want to get familiar with Scilab, > > you need to have an > > objective in Scilab. It is a huge software with many > > different > > aspects... Just focus on some parts. > > > > Don't hesitate if you have any other > > questions/remarks... > > > > Sylvestre > > > > > > > > > > > > > > -- > > Guilherme Kunigami > > > > > > > > -- > > Guilherme Kunigami > > -- Guilherme Kunigami -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierre.marechal at scilab.org Tue Apr 14 15:15:17 2009 From: pierre.marechal at scilab.org (Pierre MARECHAL) Date: Tue, 14 Apr 2009 15:15:17 +0200 Subject: Scilab 5.1.1 is released ! Message-ID: <49E48C65.20308@scilab.org> Hello, The Scilab Team is pleased to announce the release of Scilab 5.1.1. Misc information about this version: http://www.scilab.org/download/index_download.php?page=5.1.1 Main changes between Scilab 4 & Scilab 5 : http://www.scilab.org/changes_5/ Changes between Scilab 5.0.x & Scilab 5.1 : http://www.scilab.org/download/index_download.php?page=CHANGES_5.1 Changes between Scilab 5.1 & Scilab 5.1.1 : http://www.scilab.org/download/index_download.php?page=CHANGES_5.1.1 The release notes : http://www.scilab.org/download/index_download.php?page=RELEASE_NOTES_5.1.1 Pierre -- ============================================== Pierre MARECHAL ------ Fondation DIGITEO - Consortium Scilab Domaine de Voluceau - B.P. 105 78153 Le Chesnay Cedex B?timent 23 - Bureau 24 ------ Email : pierre.marechal at scilab.org T?l : +33 (0)1 39 63 56 81 Fax : +33 (0)1 39 63 55 94 ============================================== From Olivier.Poisson at cmi.univ-mrs.fr Tue Apr 14 15:29:09 2009 From: Olivier.Poisson at cmi.univ-mrs.fr (Olivier Poisson) Date: Tue, 14 Apr 2009 15:29:09 +0200 Subject: Fonction int2d de scilab Message-ID: <49E48FA5.1030803@cmi.univ-mrs.fr> Bonjour, j'ai lu avec interet qu'il y a dans Scilab la fonction "int2d" qui permet le calcul d'integrale double d'une fonction f par formule de quadrature. Or il me semble que ceci est restreint a une fonction f reelle. Ne pourrait-on pas etendre le calcul a une fonction f complexe? Et pourquoi pas a une fonction vectorielle de taille n (parametre)? Merci de me tenir au courant. Cordialement, Olivier Poisson (MCF, universite de Provence) From ycollet at freesurf.fr Wed Apr 15 08:23:20 2009 From: ycollet at freesurf.fr (ycollet at freesurf.fr) Date: Wed, 15 Apr 2009 08:23:20 +0200 Subject: sparse and sparses Message-ID: Hello, I found in the current master tree a modules sparse and a module sparses with only documentation. Is that normal ? YC From pierre.marechal at scilab.org Wed Apr 15 08:33:45 2009 From: pierre.marechal at scilab.org (Pierre MARECHAL) Date: Wed, 15 Apr 2009 08:33:45 +0200 Subject: [Scilab-Dev] sparse and sparses In-Reply-To: References: Message-ID: <49E57FC9.4030600@scilab.org> ycollet at freesurf.fr a ?crit : > Hello, > > I found in the current master tree a modules sparse and a module sparses > with only documentation. Is that normal ? > > YC > Hello Yann, Not at all. I'll fix it. Thx for the information. Pierre -- ============================================== Pierre MARECHAL ------ Fondation DIGITEO - Consortium Scilab Domaine de Voluceau - B.P. 105 78153 Le Chesnay Cedex B?timent 23 - Bureau 24 ------ Email : pierre.marechal at scilab.org T?l : +33 (0)1 39 63 56 81 Fax : +33 (0)1 39 63 55 94 ============================================== From allan.cornet at scilab.org Wed Apr 15 14:53:10 2009 From: allan.cornet at scilab.org (Allan CORNET) Date: Wed, 15 Apr 2009 14:53:10 +0200 Subject: [Scilab - Windows - master] update PCRE library Message-ID: <002501c9bdc9$21ddccf0$659966d0$@cornet@scilab.org> Hi, We have updated PCRE library (same version, only build options) for Windows on GIT master to manage UTF-8 strings. http://viewvc.scilab.org/bin/cgi/viewvc.cgi?view=rev&revision=28486 Please be sure to use this library on master (windows) Best regards Allan -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierre.marechal at scilab.org Thu Apr 16 15:24:10 2009 From: pierre.marechal at scilab.org (Pierre MARECHAL) Date: Thu, 16 Apr 2009 15:24:10 +0200 Subject: SEP 23 : Extend diary Message-ID: <49E7317A.6040500@scilab.org> Hi, This SEP deals with the addition of new functionalities to the diary management in Scilab. Comments and suggestions are welcome ! Best regards, Pierre -- ============================================== Pierre MARECHAL ------ Fondation DIGITEO - Consortium Scilab Domaine de Voluceau - B.P. 105 78153 Le Chesnay Cedex B?timent 23 - Bureau 24 ------ Email : pierre.marechal at scilab.org T?l : +33 (0)1 39 63 56 81 Fax : +33 (0)1 39 63 55 94 ============================================== -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SEP_23_extends_diary.pdf Type: application/pdf Size: 472354 bytes Desc: not available URL: From ycollette at free.fr Thu Apr 16 18:09:11 2009 From: ycollette at free.fr (Collette Yann) Date: Thu, 16 Apr 2009 18:09:11 +0200 Subject: compilation pb on current master Message-ID: <49E75827.6090001@free.fr> Hello, There is a problem during compilation: make[2]: entrant dans le r?pertoire ? /home/collette/scilab-dev/master/scilab/modules/optimization ? /bin/sh ../../libtool --tag=F77 --mode=compile gfortran -g -O2 -Wall -Wimplicit -Wsurprising -m64 -fPIC -I../../modules/core/includes/ -c -o n1qn1.lo `test -f 'src/fortran/n1qn1.f' || echo './'`src/fortran/n1qn1.f gfortran -g -O2 -Wall -Wimplicit -Wsurprising -m64 -fPIC -I../../modules/core/includes/ -c src/fortran/n1qn1.f -fPIC -o .libs/n1qn1.o f951: attention : l'option de la ligne de commande "-Wimplicit" est valide pour C/C++/ObjC/ObjC++ mais pas pour Fortran src/fortran/n1qn1.f:76.72: $ '', verbosity level: imp='',i)') n,eps,imp 1 Error: Nonnegative width required in format string at (1) src/fortran/n1qn1.f:76.6: $ '', verbosity level: imp='',i)') n,eps,imp 1 Error: Bad continuation line at (1) src/fortran/n1qn1.f:76.11: $ '', verbosity level: imp='',i)') n,eps,imp 1 Error: Invalid character in name at (1) src/fortran/n1qn1.f:80.72: $ '(''max number of iterations allowed: iter='',i)'),niter 1 Error: Nonnegative width required in format string at (1) src/fortran/n1qn1.f:84.72: $ '(''max number of calls to costf allowed: nap='',i)'),nsim 1 Error: Nonnegative width required in format string at (1) src/fortran/n1qn1.f:101.72: $ '(''***** leaves -qn code-, gradient norm='',d)') sqrt(eps) 1 Error: Positive width required in format string at (1) make[2]: *** [n1qn1.lo] Erreur 1 make[2]: quittant le r?pertoire ? /home/collette/scilab-dev/master/scilab/modules/optimization ? make[1]: *** [all-recursive] Erreur 1 make[1]: quittant le r?pertoire ? /home/collette/scilab-dev/master/scilab/modules ? make: *** [all-recursive] Erreur 1 [collette at localhost scilab]$ YC From sylvestre.ledru at scilab.org Thu Apr 16 18:12:01 2009 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Thu, 16 Apr 2009 18:12:01 +0200 Subject: [Scilab-Dev] compilation pb on current master In-Reply-To: <49E75827.6090001@free.fr> References: <49E75827.6090001@free.fr> Message-ID: <1239898321.12341.328.camel@zlarin> Le jeudi 16 avril 2009 ? 18:09 +0200, Collette Yann a ?crit : > Hello, > > There is a problem during compilation: > src/fortran/n1qn1.f:76.72: > > $ '', verbosity level: imp='',i)') n,eps,imp > 1 > Error: Nonnegative width required in format string at (1) Probably related to http://bugzilla.scilab.org/show_bug.cgi?id=4409 Sylvestre From Samuel.Gougeon at univ-lemans.fr Thu Apr 16 20:21:31 2009 From: Samuel.Gougeon at univ-lemans.fr (Samuel GOUGEON) Date: Thu, 16 Apr 2009 20:21:31 +0200 Subject: SEP 23 : Extend diary : Simultaneous sessions. Horodating. Logging depth In-Reply-To: <49E7317A.6040500@scilab.org> References: <49E7317A.6040500@scilab.org> Message-ID: <49E7772B.6010809@univ-lemans.fr> ----- Message d'origine ----- De : Pierre MARECHAL Date : 16/04/2009 15:24: > Hi, > > This SEP > > deals with the addition of new functionalities to the diary management > in Scilab. > > Comments and suggestions are welcome ! > > Best regards, > > Pierre Hi Pierre, hi everyone, There is another case that can be seen as as a drawback of the current behaviour: When several Scilab sessions are simultaneously running in distinct consoles on the same terminal, and then when diary(filename) is run with the same filename in several sessions, the current behaviour is confused: The closure of a diary overwrites the output of the previous one (starting from the beginning, but keeping the trail of the previous one if this one was longer). So, yes, reviewing and improving diary() management is welcome. *Simultaneous sessions management(s)* In the SEP, the checking of diary previously opened seems to be restricted to the current session, with no "external" "file locking" . Am i right, and if yes, would it be possible to implement an external Scilab file locking/checking ? Another possibility for managing this kind of conflict could be the following: When diary(filename) detects that filename already exists and is not empty, then an effective filename base(filemane) + _# + extension(filename) is built, used, and returned by diary(filename) as a second output argument (beside id). The rank # (integer with at least 2 digits: "01", "02", etc) would be set as the smallest integer for which the resultant filename does not yet exists. This behaviour could be the default. So no optional argument is (never) needed for it (specifying the default through an option is quite puzzling about what is the default...). Then, the "new" option would be a true option (or forget it). Because diary() seems to be bufferized with one buffer per diary() session, would an implementation of an interlacing mode with session_id line header be possible as another fixing alternative ? Then, reading of this kind of diary would required filtering capability of the used editor, working on the session_id header. What about the need of this kind of diary() e.g. for PVM operations (i have still never used PVM. I am just wondering about), or other comparable asynchronous operations that could need a "merged" log ? Some ideas for additional options: *Horodating* What about an option *horodating=format* that would add the date & hour as line header (or sub-header, whether a /session_id/ header is already written in the diary) to each logged command line. default format could be YY-MM-DD, HH:MN:SS: *Depth of logging* What about the optional possibility to restricted output logging to a certain (absolute ?) depth, since diary() can be run inside functions. For contribution and discussion, Best regards Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From allan.cornet at scilab.org Fri Apr 17 08:46:59 2009 From: allan.cornet at scilab.org (Allan CORNET) Date: Fri, 17 Apr 2009 08:46:59 +0200 Subject: [Scilab-Dev] compilation pb on current master In-Reply-To: <1239898321.12341.328.camel@zlarin> References: <49E75827.6090001@free.fr> <1239898321.12341.328.camel@zlarin> Message-ID: <000c01c9bf28$4f167a40$ed436ec0$@cornet@scilab.org> Hi, Gfortran does not like this syntax. (f2c & Intel fortran accept this syntax) Temporarily, I commented this part. I try to find another way to write this part, if you have a idea, do not hesitate :) It should be fixed on master @ http://gitweb.scilab.org/?p=scilab;a=commit;h=9d4eab7abe7738320649f0a3a8f3084000a13809 Allan -----Message d'origine----- De : Sylvestre Ledru [mailto:sylvestre.ledru at scilab.org] Envoy? : jeudi 16 avril 2009 18:12 ? : dev at lists.scilab.org Objet : Re: [Scilab-Dev] compilation pb on current master Le jeudi 16 avril 2009 ? 18:09 +0200, Collette Yann a ?crit : > Hello, > > There is a problem during compilation: > src/fortran/n1qn1.f:76.72: > > $ '', verbosity level: imp='',i)') n,eps,imp > 1 > Error: Nonnegative width required in format string at (1) Probably related to http://bugzilla.scilab.org/show_bug.cgi?id=4409 Sylvestre From ycollet at freesurf.fr Fri Apr 17 09:05:30 2009 From: ycollet at freesurf.fr (Collette Yann) Date: Fri, 17 Apr 2009 09:05:30 +0200 Subject: [Scilab-Dev] compilation pb on current master In-Reply-To: <000c01c9bf28$4f167a40$ed436ec0$@cornet@scilab.org> References: <49E75827.6090001@free.fr> <1239898321.12341.328.camel@zlarin> <000c01c9bf28$4f167a40$ed436ec0$@cornet@scilab.org> Message-ID: <49E82A3A.6090608@freesurf.fr> Hello, The compilation works fine now. I am still stuck with the documentation build (see bug 4406). Thanks a lot, YC Allan CORNET a ?crit : > Hi, > > Gfortran does not like this syntax. (f2c & Intel fortran accept this syntax) > > Temporarily, I commented this part. > > I try to find another way to write this part, if you have a idea, do not hesitate :) > > It should be fixed on master @ http://gitweb.scilab.org/?p=scilab;a=commit;h=9d4eab7abe7738320649f0a3a8f3084000a13809 > > > Allan > > -----Message d'origine----- > De : Sylvestre Ledru [mailto:sylvestre.ledru at scilab.org] > Envoy? : jeudi 16 avril 2009 18:12 > ? : dev at lists.scilab.org > Objet : Re: [Scilab-Dev] compilation pb on current master > > Le jeudi 16 avril 2009 ? 18:09 +0200, Collette Yann a ?crit : > >> Hello, >> >> There is a problem during compilation: >> > > >> src/fortran/n1qn1.f:76.72: >> >> $ '', verbosity level: imp='',i)') n,eps,imp >> 1 >> Error: Nonnegative width required in format string at (1) >> > > Probably related to > http://bugzilla.scilab.org/show_bug.cgi?id=4409 > > Sylvestre > > > > > From wzorski at poczta.onet.pl Sat Apr 18 13:10:08 2009 From: wzorski at poczta.onet.pl (Witold Zorski) Date: Sat, 18 Apr 2009 13:10:08 +0200 Subject: Fw: A mistake in Scilab 5.x Message-ID: <45C4355F427644C4836CB2623ACDD3DF@Conan> ----- Original Message ----- From: Witold Zorski To: dev-subscribe at lists.scilab.org Sent: Saturday, April 18, 2009 1:08 PM Subject: A mistake in Scilab 5.x Hello, I am a happy user of Scilab. Starting form version 5.x I encountered a problem with "plot" command. Below are two lines - the first doesn't work in the case of Scilab 5.x and is analogous to the second (that works in any Scilab version). plot([-4:1:4],0,'b+') //works only in older version of Scilab (e.g. 4.1.2) plot(0,[-4:1:4],'b+') //works in any version of Scilab (e.g. 5.1.1) Best regards, Witold Zorski PS. The error looks that way: !--error 10000 plot: Wrong size for input arguments 'X' and 'Y': Incompatible dimensions. at line 92 of function checkXYPair called by : line 225 of function plot called by : plot([-4:1:4],0,'b+') //works only in older version of Scilab (e.g. 4.1 line 6 of exec file called by : exec("D:/PRACA/Politechnika Radomska/Scilab/examples/PZK/mistake.sce"); while executing a callback -------------- next part -------------- An HTML attachment was scrubbed... URL: From tanmenglong at gmail.com Sun Apr 19 10:14:53 2009 From: tanmenglong at gmail.com (Menglong Tan) Date: Sun, 19 Apr 2009 16:14:53 +0800 Subject: Can I use components of scilab in my own C++/C application? In-Reply-To: <15def65f0904190113k656456c3x347c9d04139fb21c@mail.gmail.com> References: <15def65f0904190113k656456c3x347c9d04139fb21c@mail.gmail.com> Message-ID: <15def65f0904190114v33e6795fh82755717d84e4588@mail.gmail.com> Hello, Does scilab provide any interfaces for other 3rd-party application to use its components? If exists,how? -- Best wishes, Tan Menglong Email/GTalk:TanMenglong at gmail.com MSN:TanMenglong at hotmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From sylvestre.ledru at scilab.org Sun Apr 19 11:49:58 2009 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Sun, 19 Apr 2009 11:49:58 +0200 Subject: [Scilab-Dev] Can I use components of scilab in my own C++/C application? In-Reply-To: <15def65f0904190114v33e6795fh82755717d84e4588@mail.gmail.com> References: <15def65f0904190113k656456c3x347c9d04139fb21c@mail.gmail.com> <15def65f0904190114v33e6795fh82755717d84e4588@mail.gmail.com> Message-ID: <1240134598.12341.418.camel@zlarin> Le dimanche 19 avril 2009 ? 16:14 +0800, Menglong Tan a ?crit : > Hello, > Does scilab provide any interfaces for other 3rd-party application to > use its components? Yep, we are providing a module called call_scilab which is providing a set of C functions. Therefor, you are able to call Scilab engine from your application. There is also a Java interface (javasci) and in the future a Python one. Here is a serie of examples: Call Scilab: http://gitweb.scilab.org/?p=scilab;a=tree;f=scilab/modules/call_scilab/examples/call_scilab/c/common;h=dada99b5a8799688558d6044da29faee2e354d74;hb=HEAD http://gitweb.scilab.org/?p=scilab;a=tree;f=scilab/modules/call_scilab/examples/basicExamples;h=0e06c5875602a0960cf767ea3b00b0df6aa0946c;hb=HEAD Javasci: http://gitweb.scilab.org/?p=scilab;a=tree;f=scilab/modules/javasci/examples/others;h=1ef512af971f5249783a9db9e5f0cb99b139dbf1;hb=HEAD Don't hesitate if you have any other questions, Sylvestre From ycollet at freesurf.fr Sun Apr 19 15:05:24 2009 From: ycollet at freesurf.fr (Collette Yann) Date: Sun, 19 Apr 2009 15:05:24 +0200 Subject: [Scilab-Dev] Can I use components of scilab in my own C++/C application? In-Reply-To: <15def65f0904190114v33e6795fh82755717d84e4588@mail.gmail.com> References: <15def65f0904190113k656456c3x347c9d04139fb21c@mail.gmail.com> <15def65f0904190114v33e6795fh82755717d84e4588@mail.gmail.com> Message-ID: <49EB2194.9020008@freesurf.fr> Menglong Tan a ?crit : > Hello, > Does scilab provide any interfaces for other 3rd-party application to > use its components? > If exists,how? > > > -- > Best wishes, > > Tan Menglong > Email/GTalk:TanMenglong at gmail.com > MSN:TanMenglong at hotmail.com > have a look at the module call_scilab. It's in scilab/modules/call_scilab have also a look in the examples directory: examples/ examples/basicExamples examples/basicExamples/readwritewtring_vc examples/basicExamples/readwritewmatrix_vc examples/basicExamples/readwritecomplexmatrix_vc examples/basicExamples/readwriteboolean_vc examples/call_scilab examples/call_scilab/fortran examples/call_scilab/c examples/call_scilab/c/LabWindow examples/call_scilab/c/visual_studio examples/call_scilab/c/common examples/call_scilab/cpp examples/call_scilab/cpp/borlandcpp examples/call_scilab/cpp/common YC From heryboy at gmail.com Mon Apr 20 10:03:48 2009 From: heryboy at gmail.com (h e r y b o y) Date: Mon, 20 Apr 2009 16:03:48 +0800 Subject: Urgent! Step to create signal processing toolbox Message-ID: <4696b3390904200103q6b11c081w57b454e80a389f94@mail.gmail.com> Hye, Need your help on the most easy way to create my own signal processing toolbox based on the existing signal processing toolbox in scilab. Really appreciate if you could respond me as soon as possible as i need to compelete my assignment next 3days. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sylvestre.ledru at scilab.org Mon Apr 20 10:10:34 2009 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Mon, 20 Apr 2009 10:10:34 +0200 Subject: [Scilab-Dev] Urgent! Step to create signal processing toolbox In-Reply-To: <4696b3390904200103q6b11c081w57b454e80a389f94@mail.gmail.com> References: <4696b3390904200103q6b11c081w57b454e80a389f94@mail.gmail.com> Message-ID: <1240215034.21622.60.camel@korcula.inria.fr> Hello h e r y b o y, Le lundi 20 avril 2009 ? 16:03 +0800, h e r y b o y a ?crit : > Hye, > > Need your help on the most easy way > to create my own signal processing toolbox > based on the existing signal processing toolbox in scilab. > Really appreciate if you could respond me as soon as possible > as i need to compelete my assignment next 3days. I am sorry but we are not here to do your homework. You will find many information on this address: http://wiki.scilab.org/howto/Create_a_toolbox Sylvestre PS: Please stop flooding the team and I with your emails. From ycollet at freesurf.fr Mon Apr 20 10:20:24 2009 From: ycollet at freesurf.fr (ycollet at freesurf.fr) Date: Mon, 20 Apr 2009 10:20:24 +0200 Subject: [Scilab-Dev] Urgent! Step to create signal processing toolbox In-Reply-To: <4696b3390904200103q6b11c081w57b454e80a389f94@mail.gmail.com> References: <4696b3390904200103q6b11c081w57b454e80a389f94@mail.gmail.com> Message-ID: <1e4cb1fffb60f403ee504f93c31e64ed@freesurf.fr> Hello, You can have a look at: SCI/contrib/toolbox_skeleton This is an example of a simple toolbox. It contains the minimal files you need to build a toolbox. I use this skeleton to build all my toolboxes for 5.1. You still need to change some files, but that's an easy and fast way to start a toolbox. YC On Mon, 20 Apr 2009 16:03:48 +0800, h e r y b o y wrote: > Hye, > > Need your help on the most easy way > to create my own signal processing toolbox > based on the existing signal processing toolbox in scilab. > Really appreciate if you could respond me as soon as possible > as i need to compelete my assignment next 3days. > > Thanks. > From sylvestre.ledru at scilab.org Mon Apr 20 10:21:07 2009 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Mon, 20 Apr 2009 10:21:07 +0200 Subject: [Scilab-Dev] Urgent! Step to create signal processing toolbox In-Reply-To: <4696b3390904200113q35d2906et16b26eda91279ce2@mail.gmail.com> References: <4696b3390904200103q6b11c081w57b454e80a389f94@mail.gmail.com> <1240215034.21622.60.camel@korcula.inria.fr> <4696b3390904200113q35d2906et16b26eda91279ce2@mail.gmail.com> Message-ID: <1240215667.21622.89.camel@korcula.inria.fr> Le lundi 20 avril 2009 ? 16:13 +0800, h e r y b o y a ?crit : > thanks for your respond > i did read that page already > yet i kinda tedious, > is there any other simple way to create my own toolbox? Try to use the toolbox skeleton to start. S From pierre.marechal at scilab.org Mon Apr 20 11:30:43 2009 From: pierre.marechal at scilab.org (Pierre MARECHAL) Date: Mon, 20 Apr 2009 11:30:43 +0200 Subject: [Scilab-Dev] Re: SEP 23 : Extend diary : Simultaneous sessions. Horodating. Logging depth In-Reply-To: <49E7772B.6010809@univ-lemans.fr> References: <49E7317A.6040500@scilab.org> <49E7772B.6010809@univ-lemans.fr> Message-ID: <49EC40C3.1090903@scilab.org> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SEP_23_extends_diary.pdf Type: application/pdf Size: 521190 bytes Desc: not available URL: From bernard.hugueney at scilab.org Mon Apr 20 11:40:19 2009 From: bernard.hugueney at scilab.org (bernard.hugueney at scilab.org) Date: Mon, 20 Apr 2009 11:40:19 +0200 Subject: [Scilab-Dev] Re: SEP 23 : Extend diary : Simultaneous sessions. Horodating. Logging depth In-Reply-To: <49EC40C3.1090903@scilab.org> References: <49E7317A.6040500@scilab.org> <49E7772B.6010809@univ-lemans.fr> <49EC40C3.1090903@scilab.org> Message-ID: <5e2a2f7118fefc6c460e68fe1da147fe@localhost> On Mon, 20 Apr 2009 11:30:43 +0200, Pierre MARECHAL wrote: > HORODATING > What about an option HORODATING=FORMAT that would add the date & hour as > line header (or sub-header, whether a _session_id_ header is already > written in the > diary) to each logged command line. default format could be YY-MM-DD, > HH:MN:SS Added to the SEP (See diary & time-stamp section). For the moment, > only few formats will be supported but ideally, It should be useful the > user can build himself the format (As the date [1] php function). Why ? > because,? Date and time formats are different according to countries : > ??? > USA : MM-DD-YYYY > France : DD-MM-YYYY > German : DD.MM.YYYY > ... Please, let us fight the date format madness : creativity is *much* better spent elsewhere than in diverging from ISO 8601 [1]. I know that we must allow people to read/write other formats, but *please* make the ISO format the default, and document it as *the* *right* format. (As you may have guessed from my tone, I have already spent far to much time parsing exotic date formats). B. [1] http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=26780 From bruno.jofret at scilab.org Mon Apr 20 12:19:46 2009 From: bruno.jofret at scilab.org (Bruno JOFRET) Date: Mon, 20 Apr 2009 12:19:46 +0200 Subject: [Scilab-Dev] Fw: A mistake in Scilab 5.x In-Reply-To: <45C4355F427644C4836CB2623ACDD3DF@Conan> References: <45C4355F427644C4836CB2623ACDD3DF@Conan> Message-ID: <49EC4C42.6020800@scilab.org> Witold Zorski wrote: > > ----- Original Message ----- > *From:* Witold Zorski > *To:* dev-subscribe at lists.scilab.org > > *Sent:* Saturday, April 18, 2009 1:08 PM > *Subject:* A mistake in Scilab 5.x > > Hello, > > I am a happy user of Scilab. > Starting form version 5.x I encountered a problem with ?plot? command. > Below are two lines ? the first doesn?t work in the case of Scilab 5.x > and is analogous to the second (that works in any Scilab version). > > plot([-4:1:4],0,'b+') //works only in older version of Scilab (e.g. 4.1.2) > plot(0,[-4:1:4],'b+') //works in any version of Scilab (e.g. 5.1.1) > > Best regards, > Witold Zorski > > PS. The error looks that way: > !--error 10000 > plot: Wrong size for input arguments 'X' and 'Y': Incompatible dimensions. > at line 92 of function checkXYPair called by : > line 225 of function plot called by : > plot([-4:1:4],0,'b+') //works only in older version of Scilab (e.g. 4.1 > line 6 of exec file called by : > exec("D:/PRACA/Politechnika Radomska/Scilab/examples/PZK/mistake.sce"); > while executing a callback Hi, This was a "wrong" limitation introduced to correct another BUG. I reported (and corrected) this one [1] Thanks for using Scilab. Regards, [1] http://bugzilla.scilab.org/show_bug.cgi?id=4422 -- Bruno JOFRET Software Designer ___ SCILAB - DIGITEO ___ Tel : (+33/0)1.39.63.58.63 Mailto : bruno.jofret at scilab.org http://www.scilab.org http://www.digiteo.fr From ycollette at free.fr Mon Apr 20 20:41:09 2009 From: ycollette at free.fr (Collette Yann) Date: Mon, 20 Apr 2009 20:41:09 +0200 Subject: problem with clear console Message-ID: <49ECC1C5.4080309@free.fr> Hello, During a click on preference->clear console while a script was running, the following message appears in the shell: Dynamic-linking native method sun.awt.X11.XlibWrapper.XUngrabKeyboard ... JNI] javax.swing.text.BadLocationException: Invalid insert at javax.swing.text.GapContent.insertString(GapContent.java:112) at javax.swing.text.AbstractDocument.handleInsertString(AbstractDocument.java:709) at javax.swing.text.AbstractDocument.insertString(AbstractDocument.java:693) at org.scilab.modules.console.SciOutputView.displayLineBuffer(SciOutputView.java:200) at org.scilab.modules.console.SciOutputView.append(SciOutputView.java:310) at org.scilab.modules.gui.bridge.console.SwingScilabConsole.display(SwingScilabConsole.java:155) at org.scilab.modules.gui.console.ScilabConsoleBridge.display(ScilabConsoleBridge.java:52) at org.scilab.modules.gui.bridge.ScilabBridge.display(ScilabBridge.java:1029) at org.scilab.modules.gui.console.ScilabConsole.display(ScilabConsole.java:87) at org.scilab.modules.gui.bridge.CallScilabBridge.display(CallScilabBridge.java:187) [Dynamic-linking native method java.awt.Event.initIDs ... JNI] Nothing really annoying happens after that. The console has been cleaned (but I wanted that) and my script continues to run .. YC From sylvestre.ledru at scilab.org Mon Apr 20 23:49:26 2009 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Mon, 20 Apr 2009 23:49:26 +0200 Subject: GSOC 2009: List of accepted projects Message-ID: <1240264166.30696.84.camel@zlarin> Hello guys, Google just released the list of the accepted projects from our side. We have finally have 7 slots on many different aspects: http://socghop.appspot.com/org/home/google/gsoc2009/scilab It has been pretty hard to come up with a list of 7 proposals... I wished you could have asked for 20 slots with enough mentors to help them... but it is not the case. I am sorry for all students who spend some time on their proposal, prototyping, etc... We have also a common project with swig within the gsoc 2009. http://socghop.appspot.com/org/home/google/gsoc2009/swig We tried to find a good compromise between Science proposals, overall improvements and IT stuff keeping in mind the reality of the timeline and the project itself. For the information, we received 59 proposals. I tagged 14 of them as invalid (too bad quality)... On the 38 remaining, I think about 15 of them could have been selected... Some people come up with excellent ideas and proposals... Some of them were way to hard to implement, some other too easy... If you want some feedbacks why your proposal hasn't been selected (or has been), please drop me an email. I will try to answer to you. Of course, rejected proposals can still be implemented.. Contact me for more information. Cheers, Sylvestre From sylvestre.ledru at scilab.org Tue Apr 21 10:45:43 2009 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Tue, 21 Apr 2009 10:45:43 +0200 Subject: --enable-debug-java Message-ID: <1240303543.32469.290.camel@korcula.inria.fr> Hello, Following a request of Yann, I added the option --enable-debug-java to the configure. This is going to add two options to the configuration file modules/jvm/etc/jvm_options.xml. These options activate: * the JNI loads * the line numbering everywhere Note that it is runtime options. Sylvestre From jean-baptiste.silvy at scilab.org Tue Apr 21 18:05:25 2009 From: jean-baptiste.silvy at scilab.org (Jean-Baptiste Silvy) Date: Tue, 21 Apr 2009 18:05:25 +0200 Subject: [Scilab-Dev] SEP #16: anti-aliasing In-Reply-To: <499EC857.6080906@scilab.org> References: <499BCA1D.70308@scilab.org> <499C8ABC.5050109@free.fr> <499EC731.2050902@scilab.org> <499EC857.6080906@scilab.org> Message-ID: <49EDEEC5.3090608@scilab.org> I have updated the SEP with some benchmarks. All questions and comments are highly welcomed. Jean-Baptiste Jean-Baptiste Silvy a ?crit : > I enclose the current SEP version, for people who don't have a git > version on their computers. > > Jean-Baptiste > > Jean-Baptiste Silvy a ?crit : >> Hello, >> >> Thanks for your remarks. >> >> Fran?ois Vogel a ?crit : >> >>> Hi, >>> >>> Having AA activation control in Scilab sounds like a very good idea. >>> >>> Some comments from my side: >>> >>> - I think you should state explicitly that you are talking about >>> hardware AA, and you are not implementing oversampling and filtering >>> of the figures at the Scilab software level. You are merely using the >>> AA feature of the graphics board. Thus AA levels will depend on the >>> capability of the graphics board the user has. This may sound obvious >>> to you, but stating it clearly will not hurt. >>> >>> - You will have to check for graphics board capabilities when setting >>> the AA level requested by the user. For instance the hardware >>> configuration I'm running right now only has 2x, 4x and 6x but not 8x. >>> Warnings should be written in the console when the user requested >>> level of AA is not available from the hardware, and proper fallback be >>> used. >>> >>> >> >> Actually, in the master branch I tested two ways of doing antialiasing, >> the first one being multisampling. However, as you noticed, it might not >> be available on every hardware configurations or not with all quality >> settings. Knowing this, I also tested a fall back mode, by using the >> accumulation buffer[1]. This is a slower way, since the scene must be >> rendered as many time as the quality setting (so 4x, is almost twice >> slower than 2x). However, this will run on all configurations since >> accumulation buffers are part of OpenGL 1.0 specifications. >> >> Practically, for now in the master branch, I test whether hardware >> multisampling can be enable at the requested quality. If not I fall back >> to the second technique. >> >> I haven't run benchmarks yet to see the difference between the two >> approaches in term of speed. >> However, on my computers (2 and 3 years old), anti-aliasing can be >> activated in standard plots and graphics is still usable even with the >> accumulation buffers. >> >> >>> - In SEP#16 you say: >>> "A property ?anti_aliasing? will be added to figure handles. This >>> property value can be one of the following: ?off?, ?2x?, ?4x?, ?8x?, >>> ?16x?. If the property is set to ?off?, anti-aliasing is disabled. >>> Otherwise, the value stands for the anti-aliasing quality. >>> An other approach would be to have only two or three possible values, >>> more understandable by the user. The value could be chosen between >>> ?off? or ?on? (actually setting quality to ?4x?) or between ?off?, >>> ?performance? (quality ?4x?) and ?quality? (quality ?8x?). >>> " >>> >>> I'm strongly in favor of the first option. If a user has enough >>> knowledge in graphics to know what is anti-aliasing (and especially >>> FSAA) and to use this feature, then this user must also know how this >>> works (oversampling 4x == 4 sub-pixels and so on) and that this >>> feature can be adjusted to different levels. >>> Naming the AA levels "quality" or performance" or whatever would just >>> add to the confusion. Everybody calls this 2x, 4x, 8x etc, why would >>> Scilab have its own different names? >>> The tradeoff between AA level and graphics performance is real but >>> should be reminded in the help page for the new property (help figure?). >>> >>> >> >> That's my idea too. In the windows Nvidia control panel, they use the >> same terms also. >> >> >> >>> - FSAA (multisampling) has no effect on texture aliasing. What about >>> providing access to anisotropic filtering at the same time? Textures >>> in 3D views would look better (hem... I can't remember: is it possible >>> to apply textures on a mesh at all in Scilab? Right now I'm not sure >>> anymore) >>> >>> >> >> Yes Scilab 5 uses textures., though this is quite hidden. They >> successfully replaces triangle cutting when applying color >> interpolation. More texture will be used in Scilab when will add a way >> to display images. >> >> You're right, I did not know but multisampling does not work with >> textures. It works well with accumulation buffers though. >> In this case, I could enable linear filetring on textures to give some >> kind of anti_aliasing also, but the result would be even more smoothed. >> However, what your mentioning here is aliasing when texels are smaller >> than a pixel wide. In this case, you're right anisotropic filtering is nice. >> However, for now I don't think it is really needed in Scilab. When using >> color interpolation, user normally use quite "continuous" colormaps (in >> the color space), so it's not really a problem if the result is a bit >> blurry. >> >> However, we should keep that in mind for when we will want to apply >> various textures in Scilab such as images. >> >> Thanks again for your remarks. It highlights me the need for benchmarks >> and screenshots in the SEP for the different options argued above. >> >> Jean-Baptiste >> >> [1] >> http://www.opengl.org/resources/code/samples/advanced/advanced97/notes/node63.html >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SEP_16_anti_aliasing.odt Type: application/vnd.oasis.opendocument.text Size: 111871 bytes Desc: not available URL: From sylvestre.ledru at scilab.org Tue Apr 21 18:11:42 2009 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Tue, 21 Apr 2009 18:11:42 +0200 Subject: [Scilab-Dev] SEP #16: anti-aliasing In-Reply-To: <49EDEEC5.3090608@scilab.org> References: <499BCA1D.70308@scilab.org> <499C8ABC.5050109@free.fr> <499EC731.2050902@scilab.org> <499EC857.6080906@scilab.org> <49EDEEC5.3090608@scilab.org> Message-ID: <1240330302.27901.2345.camel@korcula.inria.fr> Pretty cool work! Yep, I have just a short comment, could you detail a bit more how you managed to produce these results ? (ie the code and the procedure you used). Thx! Sylvestre Le mardi 21 avril 2009 ? 18:05 +0200, Jean-Baptiste Silvy a ?crit : > I have updated the SEP with some benchmarks. > > All questions and comments are highly welcomed. > > Jean-Baptiste > > Jean-Baptiste Silvy a ?crit : > > I enclose the current SEP version, for people who don't have a git > > version on their computers. > > > > Jean-Baptiste > > > > Jean-Baptiste Silvy a ?crit : > > > Hello, > > > > > > Thanks for your remarks. > > > > > > Fran?ois Vogel a ?crit : > > > > > > > Hi, > > > > > > > > Having AA activation control in Scilab sounds like a very good idea. > > > > > > > > Some comments from my side: > > > > > > > > - I think you should state explicitly that you are talking about > > > > hardware AA, and you are not implementing oversampling and filtering > > > > of the figures at the Scilab software level. You are merely using the > > > > AA feature of the graphics board. Thus AA levels will depend on the > > > > capability of the graphics board the user has. This may sound obvious > > > > to you, but stating it clearly will not hurt. > > > > > > > > - You will have to check for graphics board capabilities when setting > > > > the AA level requested by the user. For instance the hardware > > > > configuration I'm running right now only has 2x, 4x and 6x but not 8x. > > > > Warnings should be written in the console when the user requested > > > > level of AA is not available from the hardware, and proper fallback be > > > > used. > > > > > > > > > > > > > > Actually, in the master branch I tested two ways of doing antialiasing, > > > the first one being multisampling. However, as you noticed, it might not > > > be available on every hardware configurations or not with all quality > > > settings. Knowing this, I also tested a fall back mode, by using the > > > accumulation buffer[1]. This is a slower way, since the scene must be > > > rendered as many time as the quality setting (so 4x, is almost twice > > > slower than 2x). However, this will run on all configurations since > > > accumulation buffers are part of OpenGL 1.0 specifications. > > > > > > Practically, for now in the master branch, I test whether hardware > > > multisampling can be enable at the requested quality. If not I fall back > > > to the second technique. > > > > > > I haven't run benchmarks yet to see the difference between the two > > > approaches in term of speed. > > > However, on my computers (2 and 3 years old), anti-aliasing can be > > > activated in standard plots and graphics is still usable even with the > > > accumulation buffers. > > > > > > > > > > - In SEP#16 you say: > > > > "A property ?anti_aliasing? will be added to figure handles. This > > > > property value can be one of the following: ?off?, ?2x?, ?4x?, ?8x?, > > > > ?16x?. If the property is set to ?off?, anti-aliasing is disabled. > > > > Otherwise, the value stands for the anti-aliasing quality. > > > > An other approach would be to have only two or three possible values, > > > > more understandable by the user. The value could be chosen between > > > > ?off? or ?on? (actually setting quality to ?4x?) or between ?off?, > > > > ?performance? (quality ?4x?) and ?quality? (quality ?8x?). > > > > " > > > > > > > > I'm strongly in favor of the first option. If a user has enough > > > > knowledge in graphics to know what is anti-aliasing (and especially > > > > FSAA) and to use this feature, then this user must also know how this > > > > works (oversampling 4x == 4 sub-pixels and so on) and that this > > > > feature can be adjusted to different levels. > > > > Naming the AA levels "quality" or performance" or whatever would just > > > > add to the confusion. Everybody calls this 2x, 4x, 8x etc, why would > > > > Scilab have its own different names? > > > > The tradeoff between AA level and graphics performance is real but > > > > should be reminded in the help page for the new property (help figure?). > > > > > > > > > > > > > > That's my idea too. In the windows Nvidia control panel, they use the > > > same terms also. > > > > > > > > > > > > > - FSAA (multisampling) has no effect on texture aliasing. What about > > > > providing access to anisotropic filtering at the same time? Textures > > > > in 3D views would look better (hem... I can't remember: is it possible > > > > to apply textures on a mesh at all in Scilab? Right now I'm not sure > > > > anymore) > > > > > > > > > > > > > > Yes Scilab 5 uses textures., though this is quite hidden. They > > > successfully replaces triangle cutting when applying color > > > interpolation. More texture will be used in Scilab when will add a way > > > to display images. > > > > > > You're right, I did not know but multisampling does not work with > > > textures. It works well with accumulation buffers though. > > > In this case, I could enable linear filetring on textures to give some > > > kind of anti_aliasing also, but the result would be even more smoothed. > > > However, what your mentioning here is aliasing when texels are smaller > > > than a pixel wide. In this case, you're right anisotropic filtering is nice. > > > However, for now I don't think it is really needed in Scilab. When using > > > color interpolation, user normally use quite "continuous" colormaps (in > > > the color space), so it's not really a problem if the result is a bit > > > blurry. > > > > > > However, we should keep that in mind for when we will want to apply > > > various textures in Scilab such as images. > > > > > > Thanks again for your remarks. It highlights me the need for benchmarks > > > and screenshots in the SEP for the different options argued above. > > > > > > Jean-Baptiste > > > > > > [1] > > > http://www.opengl.org/resources/code/samples/advanced/advanced97/notes/node63.html > > > > > > > > > From Samuel.Gougeon at univ-lemans.fr Tue Apr 21 20:07:52 2009 From: Samuel.Gougeon at univ-lemans.fr (Samuel GOUGEON) Date: Tue, 21 Apr 2009 20:07:52 +0200 Subject: [Scilab-Dev] Re: SEP 23 : Extend diary : Simultaneous sessions. Horodating. Logging depth In-Reply-To: <49EC40C3.1090903@scilab.org> References: <49E7317A.6040500@scilab.org> <49E7772B.6010809@univ-lemans.fr> <49EC40C3.1090903@scilab.org> Message-ID: <49EE0B78.4000004@univ-lemans.fr> Hello Pierre, ----- Message d'origine ----- De : Pierre MARECHAL Date : 20/04/2009 11:30: > .../... >> Another possibility for managing this kind of conflict could be the >> following: >> When diary(filename) detects that filename already exists and is not >> empty, >> then an effective filename base(filemane) + _# + extension(filename) >> is built, used, and returned by diary(filename) as a second output >> argument >> (beside id). The rank # (integer with at least 2 digits: "01", "02", >> etc) would >> be set as the smallest integer for which the resultant filename does >> not yet >> exists. > Good idea, I ve added this to the SEP. Just a little remark : I'am > sure for the 2 digits : what do we do if # > 100. If you feel that default numbering should go with 3 or 4 digits, why not. If the standard maximal number is reached (say with 2 digits, so 100 is reached), then either this would yield an error, or in a more comprehensive way, a digit would naturally be added, and so on. i am not convinced that proposing the wished number of digits as a new input option would be really useful. >> *Horodating* >> What about an option *horodating=format* that would add the date & >> hour as >> line header (or sub-header, whether a /session_id/ header is already >> written in the >> diary) to each logged command line. default format could be YY-MM-DD, >> HH:MN:SS > Added to the SEP (See diary & time-stamp section). For the moment, > only few formats will be supported but ideally, It should be useful > the user can build himself the format (As the date > php function). Why ? > because, Date and time formats are different according to countries : > > USA : MM-DD-YYYY > France : DD-MM-YYYY > German : DD.MM.YYYY > ... > > Again, this functionality (formating time and date) should be useful > for other functions than diary and described in a separate SEP. I agree with Bernard about standard as the default, and to the customization possibility. I have proposed YY-MM-DD, HH:MN:SS as a default near to the DATETIME MySQL format YYYY-MM-DD HH:MN:SS, that may be the standard. ":" separator is preferable to "-" for the TIME part (as you stated in a part of the SEP example) I tend to remove de first 2 digits of the century, since there is not really information in them (i mean, what will be the world by 91 years... :-). I am strongly favorable to set the *"prefix-only-command" as the default,* instead to time-stamping every output line (is there any acute need for such a flow, with respect to increase of file weight and decrease of diary readability ? It is always possible to use tic & toc outputs only when really needed). Moreover, for the same reason, in prefix-only-command mode, no wide white margin should be introduced. To facilitate post-processing of diaries with a parser and isolate time-stamps, what about introducing every time-stamp with a mark (say "@")(instead of reserve the 20 first columns). Example (reshaping the one given in the SEP): @2009-04-19 10:15:00 --> a = rand(3,3) ans = 0.2113249 0.3303271 0.8497452 0.7560439 0.6653811 0.6857310 0.0002211 0.6283918 0.8782165 @2009-04-19 10:15:09 --> diary(0); may be used instead, in order to keep a sober diary output. > *Depth of logging* >> What about the optional possibility to restricted output logging to a >> certain (absolute ?) >> depth, since diary() can be run inside functions. > I'am not sure to understand your request : can you give an example ? This was no more than an opened idea, instead of a request: if in a function one has pause diary(... maxdepth=3, ...) yielding -4-> then no diary would be opened after entering > Two new sections has been added > - pause/resume a diary session if no file identifier is provided, pause & resume commands might usefully be understood as to be applied to the last opened diary. Regards Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From jean-baptiste.silvy at scilab.org Wed Apr 22 14:16:55 2009 From: jean-baptiste.silvy at scilab.org (Jean-Baptiste Silvy) Date: Wed, 22 Apr 2009 14:16:55 +0200 Subject: [Scilab-Dev] SEP #16: anti-aliasing In-Reply-To: <1240330302.27901.2345.camel@korcula.inria.fr> References: <499BCA1D.70308@scilab.org> <499C8ABC.5050109@free.fr> <499EC731.2050902@scilab.org> <499EC857.6080906@scilab.org> <49EDEEC5.3090608@scilab.org> <1240330302.27901.2345.camel@korcula.inria.fr> Message-ID: <49EF0AB7.4030006@scilab.org> I added some comments on the procedure I used for the benchmarks! Don't forget to read the appendix chapter. Jean-Baptiste Sylvestre Ledru a ?crit : > Pretty cool work! > > Yep, I have just a short comment, could you detail a bit more how you > managed to produce these results ? (ie the code and the procedure you > used). > > Thx! > Sylvestre > > -------------- next part -------------- A non-text attachment was scrubbed... Name: SEP_16_anti_aliasing.odt Type: application/vnd.oasis.opendocument.text Size: 112419 bytes Desc: not available URL: From sylvestre.ledru at scilab.org Wed Apr 22 15:17:07 2009 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Wed, 22 Apr 2009 15:17:07 +0200 Subject: [Scilab-Dev] SEP #18: New Scilab Binaries In-Reply-To: <1235388929.11844.12.camel@korcula.inria.fr> References: <1235388929.11844.12.camel@korcula.inria.fr> Message-ID: <1240406227.27901.4975.camel@korcula.inria.fr> Le lundi 23 f?vrier 2009 ? 12:35 +0100, Sylvestre Ledru a ?crit : > Hello, > > Here is the SEP #18. This could lead to important changes for Scilab. > The aim of this SEP is to design new binaries. This SEP has been implemented around the March 18th 2009 in the master. I updated the document and changed the status to "Done". Three binaries are now available under Linux: - scilab - The current binary with no changes in the behaviour, ie nw & nwni are still available - scilab-adv-cli - The command line interpretor with graphic, gui and help capabilities - scilab-cli - The command line interpretor. Purely the numerical engine of Scilab. Does not need Java to run. I started a page about that: http://wiki.scilab.org/Different_execution_modes_of_Scilab which is going to be incorporated into the Docbook documentation. Sylvestre From fvogelnew1 at free.fr Fri Apr 24 20:19:13 2009 From: fvogelnew1 at free.fr (=?UTF-8?B?RnJhbsOnb2lzIFZvZ2Vs?=) Date: Fri, 24 Apr 2009 20:19:13 +0200 Subject: [Fwd: Re: sos scilab] Message-ID: <49F202A1.3030107@free.fr> Hi all, Still issues with bug 4196. I'm forwarding the message from the OP below. opteam, please note that I will not take care of this problem. You have fixed the input() problem (bug 1458, 2578, ...) the wrong way (IMO), now you go on. Francois -------- Message original -------- Sujet : Re: sos scilab Date : Fri, 24 Apr 2009 11:30:33 +0200 (CEST) De : yvon.degre at wanadoo.fr R?pondre ? : yvon.degre at wanadoo.fr Pour : fvogelnew1 at free.fr Copie ? : mehdi.lhommeau at univ-angers.fr R?f?rences : <007c01c9812a$43dee360$dfbef8c1 at atlas> <1233135542.498027b66cdbf at imp.free.fr> <000401c9b5d1$eefb2ac0$085df8c1 at atlas> <49D87FC3.7090408 at free.fr> Bonjour, j'ai install? scilab 5.1.1, la derni?re livraison de INRIA. le programme de la petite voiture ne fonctionne toujours pas correctement. Si on le lance depuis scipad il reste autiste, par contre si on le lance depuis l'ext?rieur il fonctionne bien. Je vous le mets en copie. si vous pouvez faire qque chose merci. sinc?res salutations PS c'est M. Lhommeau qui en est l'auteur. -------------- next part -------------- A non-text attachment was scrubbed... Name: angers_voiture_finale.sce Type: application/octet-stream Size: 4701 bytes Desc: not available URL: From sylvestre.ledru at scilab.org Sat Apr 25 01:36:57 2009 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Sat, 25 Apr 2009 01:36:57 +0200 Subject: [Fwd: Accepted scilab 5.1.1-1 (source all amd64)] Message-ID: <1240616217.4412.132.camel@zlarin> After Mandriva, OpenSuse, Ubuntu, here is Scilab integrated in the free repository of Debian! Sylvestre -------- Message transf?r? -------- De: Sylvestre Ledru ?: debian-devel-changes at lists.debian.org Sujet: Accepted scilab 5.1.1-1 (source all amd64) Date: Fri, 24 Apr 2009 22:37:01 +0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Sun, 19 Apr 2009 16:42:49 +0200 Source: scilab Binary: scilab scilab-data scilab-include scilab-bin libscilab-java scilab-doc scilab-doc-fr scilab-test Architecture: source all amd64 Version: 5.1.1-1 Distribution: experimental Urgency: low Maintainer: Debian Science Team Changed-By: Sylvestre Ledru Description: libscilab-java - Scientific software package for numerical computations (Java API) scilab - Scientific software package for numerical computations scilab-bin - Scientific software package for numerical computations (binary fi scilab-data - Scientific software package for numerical computations (data file scilab-doc - Scientific software package for numerical computations (documenta scilab-doc-fr - Scientific software package for numerical computations (french do scilab-include - Scientific software package for numerical computations (include f scilab-test - Scientific software package for numerical computations (test file Changes: scilab (5.1.1-1) experimental; urgency=low . [ Christoph Korn ] * New upstream version. (patches 64bitsdetection.diff filesWithSpace.diff javaHeadLess.diff displayStack.diff xmlCleanupParser.diff removed. Applied upstream) . [ Sylvestre Ledru ] * Add a patch to manage powerpc detection of the JVM (jvm-powerpc.diff) * Add a patch to use only fpu_control under Linux & x86 (fpu_control.diff) Checksums-Sha1: e640c193a3099b6078abb606c2b93f387fbbfe7e 1950 scilab_5.1.1-1.dsc b71c42073ad9c00232e4f01ac945a3fd50cc6554 35628542 scilab_5.1.1.orig.tar.gz ad9eb84c60b786749703cbe2125a6487c215dd46 32306 scilab_5.1.1-1.diff.gz 96d83d8e2dd33606a4e4d251fe0e58b18b862adc 214654 scilab_5.1.1-1_all.deb 034b50b8e1ff16ef710cb7cd3870914004fe87eb 11163164 scilab-data_5.1.1-1_all.deb 07c74529e03f6ad03b9fe6d90fe8f597c943491c 210470 scilab-include_5.1.1-1_all.deb 4a838b04237bc4a7189f10937c986ec93d7378c5 8555854 scilab-doc_5.1.1-1_all.deb e2d605ed46362dd6f695e1c52d2b386f63ff5ff4 6909104 scilab-doc-fr_5.1.1-1_all.deb 3d8e3887410ab964dc54c4975ac656b5d0fe9340 18609318 scilab-test_5.1.1-1_all.deb dea248fe2800430b837bbd86b876deb8993ace39 4701636 scilab-bin_5.1.1-1_amd64.deb 83334d77d4e3d9f0efc4e9d982a568548eac2035 36070 libscilab-java_5.1.1-1_amd64.deb Checksums-Sha256: 3913b3e6f804fa342b8ec4ff9d5e8d552d57124378eb5c7bc03d84685398e096 1950 scilab_5.1.1-1.dsc 185ff275c453462615daeab024a61d736de24a03b9bad35c1d1eda7d7d5a690e 35628542 scilab_5.1.1.orig.tar.gz d9f6d02c7eb87f55421773b233d0b198c23b1a189696f471a4bf4687544b538a 32306 scilab_5.1.1-1.diff.gz a08bcc8e760f3a5705b4966a155506528a430e48b1b7d161fccf0622ee06385a 214654 scilab_5.1.1-1_all.deb 354e67c12609cce56b261373b0ee0574816c7803edc730dee7af3d255e26df76 11163164 scilab-data_5.1.1-1_all.deb 2348108b7831b4844984adefb196567229eee8be00ce4179101d95bb8448b7e9 210470 scilab-include_5.1.1-1_all.deb 6fb77fd69a2512df7c04426fcf779f1fb4d8d86bed5f0fca3acd6d49cf5ff7a9 8555854 scilab-doc_5.1.1-1_all.deb f351deb0ba4ecd17ccf64db8ae1c505d6df7f9454a576e53c927e7cf45907a9b 6909104 scilab-doc-fr_5.1.1-1_all.deb 6be2a0be0b9e9c401aeee781c2b8f979e2af0339b6635d41995ec3b5a5f87316 18609318 scilab-test_5.1.1-1_all.deb ae4dcf613159dbfa455b97e981aebcbb0c67f56c1ba4fa51c19365bbfcdc09da 4701636 scilab-bin_5.1.1-1_amd64.deb 33df7b17422f99cd78cf3aafad0962c01bfa29cda2ec6c111e9dfe5bcab80d22 36070 libscilab-java_5.1.1-1_amd64.deb Files: ae2dbcd9bf62348a68c81f97237d3c39 1950 math optional scilab_5.1.1-1.dsc acc396708aaa7c703288301801714378 35628542 math optional scilab_5.1.1.orig.tar.gz 545d47a2837930ccf4eb89f8246faa4c 32306 math optional scilab_5.1.1-1.diff.gz 383b19928ff194458ec36f17948aecf2 214654 math optional scilab_5.1.1-1_all.deb 66660b4725e9e7a1b736ba95985ed18c 11163164 math optional scilab-data_5.1.1-1_all.deb 7edab8ea1c03687623c5a996bfb05006 210470 math optional scilab-include_5.1.1-1_all.deb 48b6c559b56e0c9d0571b1b862bb2f58 8555854 doc optional scilab-doc_5.1.1-1_all.deb bcd5551902310eef323362ca7961078d 6909104 doc optional scilab-doc-fr_5.1.1-1_all.deb 06f5b45f61511e09a619857f474cc21f 18609318 math optional scilab-test_5.1.1-1_all.deb 9b649383ca3421953e02494509a53e58 4701636 math optional scilab-bin_5.1.1-1_amd64.deb 3900733cc9a507c2277a68b61e96340c 36070 math optional libscilab-java_5.1.1-1_amd64.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAknuAy0ACgkQI2xgxmW0sWK2SQCgkfkS1id+7b2j7YjShmkS/yP1 VhQAn1m9TkcxnSM8jHKEUgtisO6BOsJT =qwRy -----END PGP SIGNATURE----- Accepted: libscilab-java_5.1.1-1_amd64.deb to pool/main/s/scilab/libscilab-java_5.1.1-1_amd64.deb scilab-bin_5.1.1-1_amd64.deb to pool/main/s/scilab/scilab-bin_5.1.1-1_amd64.deb scilab-data_5.1.1-1_all.deb to pool/main/s/scilab/scilab-data_5.1.1-1_all.deb scilab-doc-fr_5.1.1-1_all.deb to pool/main/s/scilab/scilab-doc-fr_5.1.1-1_all.deb scilab-doc_5.1.1-1_all.deb to pool/main/s/scilab/scilab-doc_5.1.1-1_all.deb scilab-include_5.1.1-1_all.deb to pool/main/s/scilab/scilab-include_5.1.1-1_all.deb scilab-test_5.1.1-1_all.deb to pool/main/s/scilab/scilab-test_5.1.1-1_all.deb scilab_5.1.1-1.diff.gz to pool/main/s/scilab/scilab_5.1.1-1.diff.gz scilab_5.1.1-1.dsc to pool/main/s/scilab/scilab_5.1.1-1.dsc scilab_5.1.1-1_all.deb to pool/main/s/scilab/scilab_5.1.1-1_all.deb scilab_5.1.1.orig.tar.gz to pool/main/s/scilab/scilab_5.1.1.orig.tar.gz From sylvestre.ledru at scilab.org Mon Apr 27 10:26:01 2009 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Mon, 27 Apr 2009 10:26:01 +0200 Subject: SEP #24: Introduce an easy way to manage sub chapters in the documentation Message-ID: <1240820761.10904.15401.camel@korcula.inria.fr> Hello, Pierre and I wrote a SEP about the introduction of the sub chapters into the documentation. As usual, don't hesitate to comment it. Pierre & Sylvestre -------------- next part -------------- A non-text attachment was scrubbed... Name: SEP_24_subcategory_documentation_mgmt.pdf Type: application/pdf Size: 394969 bytes Desc: not available URL: From Serge.Steer at inria.fr Mon Apr 27 10:55:23 2009 From: Serge.Steer at inria.fr (Serge Steer) Date: Mon, 27 Apr 2009 10:55:23 +0200 Subject: [Scilab-Dev] SEP #24: Introduce an easy way to manage sub chapters in the documentation In-Reply-To: <1240820761.10904.15401.camel@korcula.inria.fr> References: <1240820761.10904.15401.camel@korcula.inria.fr> Message-ID: <49F572FB.9000305@inria.fr> Sylvestre Ledru a ?crit : > Hello, > > Pierre and I wrote a SEP about the introduction of the sub chapters into > the documentation. > > As usual, don't hesitate to comment it. > > Pierre & Sylvestre > > Cela me parait une tres bonne idee Serge From sylvestre.ledru at scilab.org Mon Apr 27 15:49:13 2009 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Mon, 27 Apr 2009 15:49:13 +0200 Subject: [Scilab-Dev] [Fwd: Re: sos scilab] In-Reply-To: <49F202A1.3030107@free.fr> References: <49F202A1.3030107@free.fr> Message-ID: <1240840153.10904.17047.camel@korcula.inria.fr> Hello Fran?ois, Thanks for reporting this bug even if the best place to discuss about a specific bug is more in the bug tracker [1]. About the message of Mehdi, it was not working under Scilab 4.X. Therefor, it is not a regression. The issue reported by Mehdi is going to be fixed in an upcoming version. We have a fix for this issue. Regards, Sylvestre [1] http://bugzilla.scilab.org/ Le vendredi 24 avril 2009 ? 20:19 +0200, Fran?ois Vogel a ?crit : > Hi all, > > Still issues with bug 4196. > > I'm forwarding the message from the OP below. > > opteam, please note that I will not take care of this problem. > > You have fixed the input() problem (bug 1458, 2578, ...) the wrong way > (IMO), now you go on. > > Francois > > > -------- Message original -------- > Sujet : Re: sos scilab > Date : Fri, 24 Apr 2009 11:30:33 +0200 (CEST) > De : yvon.degre at wanadoo.fr > R?pondre ? : yvon.degre at wanadoo.fr > Pour : fvogelnew1 at free.fr > Copie ? : mehdi.lhommeau at univ-angers.fr > R?f?rences : <007c01c9812a$43dee360$dfbef8c1 at atlas> > <1233135542.498027b66cdbf at imp.free.fr> > <000401c9b5d1$eefb2ac0$085df8c1 at atlas> <49D87FC3.7090408 at free.fr> > > > > Bonjour, > j'ai install? scilab 5.1.1, la derni?re livraison de INRIA. > le programme de la petite voiture ne fonctionne toujours pas correctement. > Si on le lance depuis scipad il reste autiste, par contre si on le lance > depuis l'ext?rieur il fonctionne bien. > Je vous le mets en copie. > si vous pouvez faire qque chose merci. > sinc?res salutations > PS c'est M. Lhommeau qui en est l'auteur. > > > > From allan.cornet at scilab.org Thu Apr 30 10:47:57 2009 From: allan.cornet at scilab.org (Allan CORNET) Date: Thu, 30 Apr 2009 10:47:57 +0200 Subject: SEP 25 : fileinfo Message-ID: <001401c9c970$5bd2c6b0$13785410$@cornet@scilab.org> Hi, Here is the SEP #25. The aim of this SEP is to extend 'fileinfo' to manage column vector of strings as input argument. Best regards, Allan CORNET -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SEP_25_extend_fileinfo.pdf Type: application/pdf Size: 73176 bytes Desc: not available URL: From ycollet at freesurf.fr Thu Apr 30 11:20:55 2009 From: ycollet at freesurf.fr (ycollet at freesurf.fr) Date: Thu, 30 Apr 2009 11:20:55 +0200 (CEST) Subject: Get_Iname Message-ID: <76a0fef60c0a059629f5ec7fd89edf2c.squirrel@wmail.freesurf.fr> Hello, What about adding Get_Iname prototype into stack-c.h ? YC From ycollet at freesurf.fr Thu Apr 30 11:21:20 2009 From: ycollet at freesurf.fr (ycollet at freesurf.fr) Date: Thu, 30 Apr 2009 11:21:20 +0200 (CEST) Subject: CheckOpt Message-ID: Hello, I was checking the use of some functions defined in stack-c.h (so as to see if some functions can be documented or not) and I found that the CheckOpt function (which is a macro calling the function checkopt) doesn't exist anymore. We certainly can remove this function from stack-c.h. YC From sylvestre.ledru at scilab.org Thu Apr 30 11:33:07 2009 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Thu, 30 Apr 2009 11:33:07 +0200 Subject: [Scilab-Dev] Get_Iname In-Reply-To: <76a0fef60c0a059629f5ec7fd89edf2c.squirrel@wmail.freesurf.fr> References: <76a0fef60c0a059629f5ec7fd89edf2c.squirrel@wmail.freesurf.fr> Message-ID: <1241083987.10904.36624.camel@korcula.inria.fr> Le jeudi 30 avril 2009 ? 11:20 +0200, ycollet at freesurf.fr a ?crit : > Hello, > > What about adding Get_Iname prototype into stack-c.h ? Could you be more specific ? Thx S From Samuel.Gougeon at univ-lemans.fr Thu Apr 30 20:55:09 2009 From: Samuel.Gougeon at univ-lemans.fr (Samuel GOUGEON) Date: Thu, 30 Apr 2009 20:55:09 +0200 Subject: [Scilab-Dev] SEP #24: Introduce an easy way to manage sub chapters in the documentation In-Reply-To: <1240820761.10904.15401.camel@korcula.inria.fr> References: <1240820761.10904.15401.camel@korcula.inria.fr> Message-ID: <49F9F40D.3090302@univ-lemans.fr> Hello Sylvestre, ----- Message d'origine ----- De : Sylvestre Ledru Date : 27/04/2009 10:26: > Hello, > > Pierre and I wrote a SEP about the introduction of the sub chapters into > the documentation. > > As usual, don't hesitate to comment it. > > Pierre & Sylvestre > As previously discussed with Serge and you through some bugzilla & requestzilla comments, yes, this new feature will be very great. In these discussions, a topic strongly related to sub-chaptering has been evoked: capability to show a topic in different places in the help tree (alias management). For instance, derivat() would deserve appearing into a "polynomials" sub-directory, as well as into another "differential calculus" sub-directory. Does DocBook manage this feature ? Will it be possible to build the doc with - help files with inode having more than one link ? (Linux / Unix) - shortcuts pointing to an help file ? (Windows) Suggestion & question about the SEP: - renaming CHAPTER into CHAPTER.txt (is CHAPTER mandatory to follow any DocBook convention ?) - /SEP Proposal section: "As in the rest of the help build process, if help files are not available in a specific languages, the system will copy all of them from the english one. *Including all the subdirectory*"/ Does this mean that DocBook cannot manage a partially translated sub-directory ? What about such a processing: A list of declared files may be given in the CHAPTER file. While building the doc, this list is parsed. If a file is missing (from the locale directory), its en_US release is used (together with available files already translated from en_US to the locale). Best regards Samuel PS:The wiki page http://wiki.scilab.org/howto/scilab_documentation_kit is nice. However, i haven't found any example in the wiki, nor of source help file to imitate, in the Scilab tree of the distributed release. Where is it possible to find a source page example containing - a See also section with cross references, - inclusion of an image (i just know that such an inclusion is possible since an image is included in the segs_properties page. But how to do), - other external hyperlinks - etc Users who can spend a quite appreciable amount of time to go deep inside the /DocBook definitive reference Guide/ to find these infos (imageobject, imagedata, etc & main syntaxes and options), while they are mainly interested by Scilab programming, are likely rare. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sylvestre.ledru at scilab.org Thu Apr 30 21:48:52 2009 From: sylvestre.ledru at scilab.org (Sylvestre Ledru) Date: Thu, 30 Apr 2009 21:48:52 +0200 Subject: [Scilab-Dev] SEP #24: Introduce an easy way to manage sub chapters in the documentation In-Reply-To: <49F9F40D.3090302@univ-lemans.fr> References: <1240820761.10904.15401.camel@korcula.inria.fr> <49F9F40D.3090302@univ-lemans.fr> Message-ID: <1241120932.28970.15.camel@zlarin> Hello Samuel, Le jeudi 30 avril 2009 ? 20:55 +0200, Samuel GOUGEON a ?crit : > Hello Sylvestre, > > ----- Message d'origine ----- > De : Sylvestre Ledru > Date : 27/04/2009 10:26: > > Hello, > > > > Pierre and I wrote a SEP about the introduction of the sub chapters into > > the documentation. > > > > As usual, don't hesitate to comment it. > > > > Pierre & Sylvestre > > > As previously discussed with Serge and you through some bugzilla & > requestzilla > comments, yes, this new feature will be very great. Indeed. Pierre has done some work on it and it sounds great! > In these discussions, a topic strongly related to sub-chaptering has > been evoked: > capability to show a topic in different places in the help tree (alias > management). > > For instance, derivat() would deserve appearing into a "polynomials" > sub-directory, > as well as into another "differential calculus" sub-directory. > > Does DocBook manage this feature ? I don't know. Maybe it is written in the docbook documentation, I haven't dig deep enough to find it... > Will it be possible to build the doc with > - help files with inode having more than one link ? (Linux / Unix) > - shortcuts pointing to an help file ? (Windows) I don't think this solution would work. I believe the ID is unique for each page and this solution would conflict. > > Suggestion & question about the SEP: > - renaming CHAPTER into CHAPTER.txt (is CHAPTER mandatory to follow > any DocBook convention ?) No sure to understand your point here ?! > - SEP Proposal section: "As in the rest of the help build process, if > help files > are not available in a specific languages, the system will copy all of > them from > the english one. Including all the subdirectory" > > Does this mean that DocBook cannot manage a partially translated > sub-directory ? It can, we are just saying that if a page help/fr_FR/plop.xml is missing in the french localization, we will use the english one (help/en_US/plop.xml) as reference. > What about such a processing: A list of declared files may be given in > the CHAPTER > file. While building the doc, this list is parsed. If a file is > missing (from the locale directory), > its en_US release is used (together with available files already > translated from en_US > to the locale). File lists are often a bad idea. Too oftently, people forget to add a new file (or remove an other). > Best regards > Samuel > > PS:The wiki page http://wiki.scilab.org/howto/scilab_documentation_kit > is nice. This page is outdated. We should write a new documentation explaining how to use easily the documentation system. Thanks for reminding this! Sylvestre