From Simone.Mannori at inria.fr Fri Feb 1 07:41:07 2008 From: Simone.Mannori at inria.fr (Simone Mannori) Date: Fri, 01 Feb 2008 07:41:07 +0100 Subject: [Scilab-Dev] Scicos-PST In-Reply-To: <6ab64a060801311300n6876c7bax407d7f5883924410@mail.gmail.com> References: <316807.85417.qm@web28411.mail.ukl.yahoo.com> <6ab64a060801281854l20ec7d89i5c8715f7263199d3@mail.gmail.com> <1201636836.15086.16.camel@buta.inria.fr> <6ab64a060801291334n6a07760am4b82c6514888b7d2@mail.gmail.com> <1201677386.16647.26.camel@buta.inria.fr> <6ab64a060801301335m75c2b49ald311a5fb65a81e6a@mail.gmail.com> <1201757666.5166.44.camel@buta.inria.fr> <6ab64a060801311300n6876c7bax407d7f5883924410@mail.gmail.com> Message-ID: <1201848067.8227.25.camel@buta.inria.fr> Bonjour Raymundo, On Thu, 2008-01-31 at 16:00 -0500, Cordero R. wrote: > Dear Simone > At the moment, I also am working in the proyect about symbolic > computation (difficult but interesting), > However, motor control and modeling is part of my thesis and a > previous research work, so this is something I will do. > Now, I have a technical question. At last ;) I like technical question :). > I could make Scicos models using super block, but I would prefer to > make new blocks using C/C++. ... and it is the best option ... > But I have problems because in my computer I don?t have a C compiler. If you want to do serious development with Scilab/Scicos would suggest you to switch to Linux. Linux has A LOT of advantages for the developers. The default "gcc" compiler is one of the most important. Scilab/Scicos is born in Unix, grow in Linux and ported to Windows and Mac OSX. I have done some development also using Windows but is just a bit more tricky for the missing default C compiler. My suggested solution for Scicos development under Windows it is to install Scilab 4.1.2 binary version and the free (free as "free beer") Visual Studio Express 2005. You need to install manually some packages and patch some files. Microsoft has prepared some usable help pages ... Start from here: http://wiki.scilab.org/Visual_Studio_C%2B%2B_2005_Express then go here http://msdn2.microsoft.com/en-us/express/aa700755.aspx for a detailed explanation of the "hack" After the installation you will able to compile Scicos block computational functions. BEWARE: with this set up you will not able to compile the full Scicos, but if you are interest mainly to Scicos, this is not a big limitation. The C compiler is useful (and necessary) for Modelica. How to write good and efficient Scicos computational functions will be the subject of the next email :). Simone Mannori - Scilab/Scicos Embedded Applications Eng. > Which one I could use? > Raymundo > > 2008/1/31, Simone Mannori : > Bonjour Raymundo, > > > In 1 month I will start my postgrade in Brazil and I am > going to use SCILAB for modeling power system. > > As a result, I will make the "SCICOS-PST". > > Very good :) > > > > > Meanwhile, I almost finished a model of a SVPWM, SPWM.Park, > Clarke > > transform and THD. > > OK. > > > The video conference finished today. But I can organize > another one in > > February, where you can participate, even as an expositor. > The main > > problem is that if you speak Spanish. > > Not yet :(. (English, French, Italian). > > Back to our core business Scicos-PST. > > For the moment you can develop using the latest Scilab 4.1.2 > but, before > start to develop a serious toolbox we need to to sure that it > will be > compatible with the next Scilab 5.0 in the form and in the > substance. > > SUBSTANCE > A good starting point is to discuss the application field. I'm > understanding that you are working on electrical motor drive. > In this > field ( ops :) ) motor's modeling is the most critical point. > Define a pretty theoretical model could be a good idea for a > paper, but > the real challenge is to define a model sufficiently close to > reality > for the applications with parameters easy to extract from real > world, > clearly defined, measurements. "Simple, but not simpler". > >From this point of view I'm not sure that the Simulink > approach is the > best one. > Anyway, if you have positive experience on that, we can use a > dual/mode > Scicos model or two different blocks with the same layout but > with > different computational functions. > > FORM: > It is up to you decide the modality of development, > distribution and > licensing of you toolbox. > If you will join the community of Scilab/Scicos developers you > will have > more options and opportunities respect to the isolate > individual. > Feel be free to directly contact Sylvestre Ledru (he is in CC) > for any > question about joining the community. > > Best Regards > > Simone Mannori - Scilab/Scicos Embedded Applications Eng. > > > > > > > From mhammad at interchange.ubc.ca Sun Feb 3 09:37:39 2008 From: mhammad at interchange.ubc.ca (Mohammed Al-Taha) Date: Sun, 03 Feb 2008 00:37:39 -0800 (PST) Subject: Adding toolboxes to autostart For Vista Message-ID: <1114656.21431202027859806.JavaMail.myubc2@handel.my.ubc.ca> Greetings My name is Mohammed, I am a student at electrical engineering at the University of British Columbia. I send this e-mail because I dont know how to make the follwing advice: For Scilab users operating on Windows Vista who want to add a particular toolbox to the startup file for automatic loading should : 1. go to C:\Program files\scilab 2. go to scilab.star, and open it with wordpad 3. go to the end of the file and put the command exec('PATH\loader.sce'), where PATH is the path to the folder containing the toolbox. 4.save the file 5.If an error message pops up saying that access to the file is denied, go to scilab.star->righ click-> properties->go to the security tabs and you can change the edit properties to allow changes made to the file by users. From sylvestre.ledru at inria.fr Sun Feb 3 11:45:46 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Sun, 03 Feb 2008 11:45:46 +0100 Subject: [Scilab-Dev] Adding toolboxes to autostart For Vista In-Reply-To: <1114656.21431202027859806.JavaMail.myubc2@handel.my.ubc.ca> References: <1114656.21431202027859806.JavaMail.myubc2@handel.my.ubc.ca> Message-ID: <1202035546.6313.3.camel@zlarin.inria.fr> Hello Mohammed, You should send this email on the appropriate mailing list: users at lists.scilab.org This one is intended for the "inner" development of Scilab. Cheers, Sylvestre Le dimanche 03 f?vrier 2008 ? 00:37 -0800, Mohammed Al-Taha a ?crit : > Greetings > My name is Mohammed, I am a student at electrical engineering at the University of British Columbia. > I send this e-mail because I dont know how to make the follwing advice: > For Scilab users operating on Windows Vista who want to add a particular toolbox to the startup file for automatic loading should : > 1. go to C:\Program files\scilab > 2. go to scilab.star, and open it with wordpad > 3. go to the end of the file and put the command exec('PATH\loader.sce'), where PATH is the path to the folder containing the toolbox. > 4.save the file > 5.If an error message pops up saying that access to the file is denied, go to scilab.star->righ click-> properties->go to the security tabs and you can change the edit properties to allow changes made to the file by users. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Ceci est une partie de message num?riquement sign?e URL: From Simone.Mannori at inria.fr Sun Feb 3 11:46:48 2008 From: Simone.Mannori at inria.fr (Simone Mannori) Date: Sun, 03 Feb 2008 11:46:48 +0100 Subject: Hi there :) Message-ID: <1202035608.22056.3.camel@buta.inria.fr> Bonjour Sylvestre, I started to work this morning at 7:00AM on the final release of Scicos FLEX for the next demos in Milan (12/13/14 Feb) Actually I'm in pause because my Italian friends are looking for a nasty Cygwin bug ... In the meanwhile I'm customizing some boards ... See you :) Simone From sylvestre.ledru at inria.fr Sun Feb 3 22:26:29 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Sun, 03 Feb 2008 22:26:29 +0100 Subject: Use by default the GTK theme Message-ID: <1202073989.3813.15.camel@zlarin.inria.fr> Hi I just made a small change on the Java GUI. If the Java/GTK theme is available on the computer, we use it. There are a few graphical bugs but we know how to fix them (just need to go upstream on the flexdock bug). Allan, I leave you the work for Windows if you don't mind (Cannot test here) Cheers, Sylvestre -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Ceci est une partie de message num?riquement sign?e URL: From vincent.couvert at inria.fr Mon Feb 4 09:02:33 2008 From: vincent.couvert at inria.fr (Vincent COUVERT) Date: Mon, 04 Feb 2008 09:02:33 +0100 Subject: [Scilab-Dev] Use by default the GTK theme In-Reply-To: <1202073989.3813.15.camel@zlarin.inria.fr> References: <1202073989.3813.15.camel@zlarin.inria.fr> Message-ID: <47A6C699.3030500@inria.fr> Hi, I just add a temporary fix for the main problem of Flexdock used with GTK (no close button on tabs and exception thrown when creating a tab). Vincent Sylvestre Ledru a ?crit : > Hi > > I just made a small change on the Java GUI. If the Java/GTK theme is > available on the computer, we use it. > There are a few graphical bugs but we know how to fix them (just need to > go upstream on the flexdock bug). > > Allan, I leave you the work for Windows if you don't mind (Cannot test > here) > > Cheers, > Sylvestre > > -- ============================================== Vincent COUVERT Centre de Recherche INRIA Paris-Rocquencourt Domaine de Voluceau - B.P. 105 78153 Le Chesnay Cedex ============================================== Equipe Projet SCILAB B?timent 1B - Bureau 013 Email : vincent.couvert at inria.fr T?l : +33 (0)1 39 63 54 46 Fax : +33 (0)1 39 63 55 94 ============================================== From Simone.Mannori at inria.fr Mon Feb 4 14:05:58 2008 From: Simone.Mannori at inria.fr (Simone Mannori) Date: Mon, 04 Feb 2008 14:05:58 +0100 Subject: [Fwd: OpenGL BUG ?] Message-ID: <1202130358.3719.10.camel@buta.inria.fr> Hi: Same machine, same "plot2d" but: - with 3d support in hardware DISABLED (Mesa emulation) PERFECT - with 3d support in hardware ENABLED (ATI binary driver) Scilab 5.0 crash (see attached mail for details). On another NVIDIA machine both situation are OK. Some nasty issue in the ATI binary driver ? Simone Mannori -------------- next part -------------- An embedded message was scrubbed... From: "Simone Mannori" Subject: OpenGL BUG ? Date: Mon, 4 Feb 2008 13:59:06 +0100 Size: 9993 URL: From sylvestre.ledru at inria.fr Mon Feb 4 14:17:46 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Mon, 04 Feb 2008 14:17:46 +0100 Subject: [Scilab-Dev] [Fwd: OpenGL BUG ?] In-Reply-To: <1202130358.3719.10.camel@buta.inria.fr> References: <1202130358.3719.10.camel@buta.inria.fr> Message-ID: <1202131067.30140.654.camel@korcula.inria.fr> Can you provide the hs_err_pidXXXX.log file ? Cheers, Sylvestre Le lundi 04 f?vrier 2008 ? 14:05 +0100, Simone Mannori a ?crit : > Hi: > > Same machine, same "plot2d" but: > > - with 3d support in hardware DISABLED (Mesa emulation) > > PERFECT > > - with 3d support in hardware ENABLED (ATI binary driver) > > Scilab 5.0 crash (see attached mail for details). > > > > On another NVIDIA machine both situation are OK. > > Some nasty issue in the ATI binary driver ? > > Simone Mannori > > > pi?ce jointe message de courriel, "Forwarded message - OpenGL BUG ?" > > -------- Message transf?r? -------- > > De: Simone Mannori > > ?: Simone Mannori > > Sujet: OpenGL BUG ? > > Date: Mon, 4 Feb 2008 13:59:06 +0100 > > > > with3d active > > > > "plot2d" > > > > > > At revision 22140 > > > > [simone at tank scilab]$ Exception in thread "AWT-EventQueue-0" > > javax.media.opengl.GLException: Error making context current > > at > > com.sun.opengl.impl.x11.X11GLContext.makeCurrentImpl(X11GLContext.java:141) > > at > > com.sun.opengl.impl.x11.X11OffscreenGLContext.makeCurrentImpl(X11OffscreenGLContext.java:74) > > at > > com.sun.opengl.impl.GLContextImpl.makeCurrent(GLContextImpl.java:134) > > at > > com.sun.opengl.impl.GLDrawableHelper.invokeGL(GLDrawableHelper.java:182) > > at > > javax.media.opengl.GLJPanel.paintComponent(GLJPanel.java:661) > > at javax.swing.JComponent.paint(JComponent.java:1027) > > at javax.swing.JComponent.paintChildren(JComponent.java:864) > > at javax.swing.JComponent.paint(JComponent.java:1036) > > at javax.swing.JComponent.paintChildren(JComponent.java:864) > > at javax.swing.JComponent.paint(JComponent.java:1036) > > at > > org.flexdock.docking.defaults.DefaultDockingPort.paint(DefaultDockingPort.java:1976) > > at > > javax.swing.JComponent.paintToOffscreen(JComponent.java:5122) > > at > > javax.swing.BufferStrategyPaintManager.paint(BufferStrategyPaintManager.java:285) > > at > > javax.swing.RepaintManager.paint(RepaintManager.java:1128) > > at > > javax.swing.JComponent._paintImmediately(JComponent.java:5070) > > at > > javax.swing.JComponent.paintImmediately(JComponent.java:4880) > > at > > javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:723) > > at > > javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:679) > > at > > javax.swing.RepaintManager.seqPaintDirtyRegions(RepaintManager.java:659) > > at javax.swing.SystemEventQueueUtilities > > $ComponentWorkRequest.run(SystemEventQueueUtilities.java:128) > > at > > java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) > > at java.awt.EventQueue.dispatchEvent(EventQueue.java:597) > > at > > java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273) > > at > > java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183) > > at > > java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173) > > at > > java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168) > > at > > java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160) > > at > > java.awt.EventDispatchThread.run(EventDispatchThread.java:121) > > # > > # An unexpected error has been detected by Java Runtime Environment: > > # > > # SIGSEGV (0xb) at pc=0x009513d7, pid=4043, tid=1865935760 > > # > > # Java VM: Java HotSpot(TM) Server VM (1.6.0_03-b05 interpreted > > mode) > > # Problematic frame: > > # C [libX11.so.6+0x313d7] XQueryExtension+0x17 > > # > > # An error report file with more information is saved as > > hs_err_pid4043.log > > # > > # If you would like to submit a bug report, please visit: > > # http://java.sun.com/webapps/bugreport/crash.jsp > > # > > bin/scilab: line 378: 4043 Aborted "$SCILABBIN" $* > > > > > > From vincent.couvert at inria.fr Mon Feb 4 14:36:34 2008 From: vincent.couvert at inria.fr (Vincent COUVERT) Date: Mon, 04 Feb 2008 14:36:34 +0100 Subject: [Scilab-Dev] Localization behavior In-Reply-To: <1201689896.17931.3685.camel@korcula.inria.fr> References: <1201689896.17931.3685.camel@korcula.inria.fr> Message-ID: <47A714E2.6040802@inria.fr> Hello, As a Scilab user, the behavior I would have for Scilab is : - if I do not precise the locale I want to use: Scilab uses the default locale of my system - if I do not want to use the locale of my system, I precise in a Scilab configuration file which locale I want to use We have to remember that the locale settings must be read before Scilab GUIs are created but after all Scilab functions are loaded (to have access to localization functions). Vincent Sylvestre Ledru a ?crit : > Hello, > > We are thinking about how the localization should be handle in Scilab. > > At the moment, when Scilab is launched, each time, we are loading the > locale of the system and if we have the matching translation, we load > it. Otherwise, we switch back to english. > This behaviour is the standard one under Linux but we might want the > user to keep his favorite language when he starts Scilab. > > We have one potential solution : > > Under Windows, on the installation, the user choose his language and we > save it in the configuration (registry base). > > Under Linux, we detect it each time the user starts Scilab which > language is the default one on the system. > However, by calling the function setdefaultlanguage("xx_XX"), we are > saving the language he wants into the Scilab configuration file. > > How does it sound ? > Cheers, > Sylvestre > > > -- ============================================== Vincent COUVERT Centre de Recherche INRIA Paris-Rocquencourt Domaine de Voluceau - B.P. 105 78153 Le Chesnay Cedex ============================================== Equipe Projet SCILAB B?timent 1B - Bureau 013 Email : vincent.couvert at inria.fr T?l : +33 (0)1 39 63 54 46 Fax : +33 (0)1 39 63 55 94 ============================================== From Simone.Mannori at inria.fr Mon Feb 4 14:48:31 2008 From: Simone.Mannori at inria.fr (Simone Mannori) Date: Mon, 04 Feb 2008 14:48:31 +0100 Subject: [Fwd: OpenGL BUG ?] Message-ID: <1202132911.3719.12.camel@buta.inria.fr> Please see the attached email for the error log. Simone -------------- next part -------------- An embedded message was scrubbed... From: "Simone Mannori" Subject: OpenGL BUG ? Date: Mon, 4 Feb 2008 14:52:46 +0100 Size: 57503 URL: From laurent.vaylet at inria.fr Mon Feb 4 15:06:58 2008 From: laurent.vaylet at inria.fr (Laurent Vaylet) Date: Mon, 04 Feb 2008 15:06:58 +0100 Subject: [Scilab-Dev] Localization behavior In-Reply-To: <47A714E2.6040802@inria.fr> References: <1201689896.17931.3685.camel@korcula.inria.fr> <47A714E2.6040802@inria.fr> Message-ID: <1202134018.23211.75.camel@ibiza> Many many weeks ago, in a far far away city called Lyon, when i was a consultant, we used to design software that way: The first time the application was launched, the user was given a choice through a popup menu : french or english (independently of the OS language) ? This setting was saved in a file and retrieved at the next startup. At any moment, the user could decide to switch language through a menu item and the new setting applied immediately for both GUI and help files (and perhaps unit system). Would it be possible with Scilab ? Anyway, i agree with Vincent on the fact that functions must be loaded first and independently of this setting. Laurent On Mon, 2008-02-04 at 14:36 +0100, Vincent COUVERT wrote: > Hello, > > As a Scilab user, the behavior I would have for Scilab is : > - if I do not precise the locale I want to use: Scilab uses the default > locale of my system > - if I do not want to use the locale of my system, I precise in a > Scilab configuration file which locale I want to use > > We have to remember that the locale settings must be read before Scilab > GUIs are created but after all Scilab functions are loaded (to have > access to localization functions). > > Vincent > > Sylvestre Ledru a ?crit : > > Hello, > > > > We are thinking about how the localization should be handle in Scilab. > > > > At the moment, when Scilab is launched, each time, we are loading the > > locale of the system and if we have the matching translation, we load > > it. Otherwise, we switch back to english. > > This behaviour is the standard one under Linux but we might want the > > user to keep his favorite language when he starts Scilab. > > > > We have one potential solution : > > > > Under Windows, on the installation, the user choose his language and we > > save it in the configuration (registry base). > > > > Under Linux, we detect it each time the user starts Scilab which > > language is the default one on the system. > > However, by calling the function setdefaultlanguage("xx_XX"), we are > > saving the language he wants into the Scilab configuration file. > > > > How does it sound ? > > Cheers, > > Sylvestre > > > > > > > From pierre.marechal at inria.fr Mon Feb 4 17:16:23 2008 From: pierre.marechal at inria.fr (Pierre MARECHAL) Date: Mon, 04 Feb 2008 17:16:23 +0100 Subject: STRING_V2 => string Message-ID: <47A73A57.3080204@inria.fr> Hi all, "string" module has been removed and replaced by "STRING_V2" module. (http://viewvc.scilab.org/bin/cgi/viewvc.cgi/?view=query&dir=&file=&file_match=exact&who=pmarecha&who_match=exact&querysort=date&hours=2&date=explicit&mindate=2008-02-04+15%3A00%3A00&maxdate=2008-02-04+18%3A00%3A00&limit_changes=100) If you update your working copy (svn://svn.scilab.org/scilab/trunk/scilab), you have to do a "make distclean" in the SCI directory in order to re-compile Scilab : [SHELL ~/scilab] make distclean [SHELL ~/scilab] rm -rf modules/string [SHELL ~/scilab] rm -rf modules/STRING_V2 [SHELL ~/scilab] svn update [SHELL ~/scilab] ./configure [SHELL ~/scilab] make all Best regards, Pierre -- =================================================== Pierre MARECHAL INRIA - Centre de Recherche de Paris - Rocquencourt Domaine de Voluceau - B.P. 105 78153 Le Chesnay Cedex =================================================== Equipe-Projet Scilab B?timent 1B - Bureau 008 Email : pierre.marechal at inria.fr =================================================== From Simone.Mannori at inria.fr Tue Feb 5 06:24:07 2008 From: Simone.Mannori at inria.fr (Simone Mannori) Date: Tue, 05 Feb 2008 06:24:07 +0100 Subject: Scilab 5.0 graphics issues under Linux Message-ID: <1202189047.5941.58.camel@buta.inria.fr> Hi There, first, the good news: NVIDIA-binary if you own a NVIDIA card and you have installed the proprietary, binary only, drivers your soul is damned and you will go to the hell of the GPL3 violator .... BUT Scilab 5.0 will run pretty good :) and the bad news .... ATI-binary if you own a ATI card and you have installed the proprietary, binary only, drivers your soul is damned, you will go to the hell of the GPL3 violator and Scilab 5.0 - probably - will hang at the first "plot2d" or the graphics will looks incomplete (no text or string in the axes). NO PANIC : we have an almost infinite reserve of caffeine and we are working on these issues in order to fix it. Simple reports of positive/negative cases are very welcome ! Please specify: - Linux distribution - kernel version ("uname -a") - graphics card ("/sbin/lspci") - graphics driver installed - OpenGL support ("glxinfo") Report from 'the other OS from Redmond' (Windows) are very welcome too BUT, please note that this post is on a Linux specific issue. Thanks in advance for your collaboration .... M. Simone Mannori - Scilab/Scicos Embedded Applications Eng. From yann.collette at renault.com Tue Feb 5 08:21:26 2008 From: yann.collette at renault.com (COLLETTE Yann) Date: Tue, 05 Feb 2008 08:21:26 +0100 Subject: [Scilab-Dev] Scilab 5.0 graphics issues under Linux In-Reply-To: <1202189047.5941.58.camel@buta.inria.fr> References: <1202189047.5941.58.camel@buta.inria.fr> Message-ID: <47A80E76.2090900@renault.com> Hello, I can confirm the problem with the ATI driver. And maybe something more: if I start scilab in the installation directory, scilab hang quite brutally. If I start scilab in the build directory, I've just got a java error message and scilab doesn't hang. YC Simone Mannori a ?crit : > Hi There, > > first, the good news: > > NVIDIA-binary > if you own a NVIDIA card and you have installed the proprietary, binary > only, drivers your soul is damned and you will go to the hell of the > GPL3 violator .... BUT Scilab 5.0 will run pretty good :) > > and the bad news .... > > ATI-binary > if you own a ATI card and you have installed the proprietary, binary > only, drivers your soul is damned, you will go to the hell of the GPL3 > violator and Scilab 5.0 - probably - will hang at the first "plot2d" or > the graphics will looks incomplete (no text or string in the axes). > > NO PANIC : we have an almost infinite reserve of caffeine and we are > working on these issues in order to fix it. > > Simple reports of positive/negative cases are very welcome ! > > Please specify: > - Linux distribution > - kernel version ("uname -a") > - graphics card ("/sbin/lspci") > - graphics driver installed > - OpenGL support ("glxinfo") > > Report from 'the other OS from Redmond' (Windows) are very welcome too > BUT, please note that this post is on a Linux specific issue. > > Thanks in advance for your collaboration .... > > M. Simone Mannori - Scilab/Scicos Embedded Applications Eng. > > > -- Disclaimer ------------------------------------ Ce message ainsi que les eventuelles pieces jointes constituent une correspondance privee et confidentielle a l'attention exclusive du destinataire designe ci-dessus. Si vous n'etes pas le destinataire du present message ou une personne susceptible de pouvoir le lui delivrer, il vous est signifie que toute divulgation, distribution ou copie de cette transmission est strictement interdite. Si vous avez recu ce message par erreur, nous vous remercions d'en informer l'expediteur par telephone ou de lui retourner le present message, puis d'effacer immediatement ce message de votre systeme. *** This e-mail and any attachments is a confidential correspondence intended only for use of the individual or entity named above. If you are not the intended recipient or the agent responsible for delivering the message to the intended recipient, you are hereby notified that any disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by phone or by replying this message, and then delete this message from your system. From Simone.Mannori at inria.fr Tue Feb 5 10:15:47 2008 From: Simone.Mannori at inria.fr (Simone Mannori) Date: Tue, 05 Feb 2008 10:15:47 +0100 Subject: Scilab 5 ATI issue under Linux Message-ID: <1202202947.8797.9.camel@buta.inria.fr> Hi there: - SVN revision : At revision 22183. - Linux distribution : Fedora 7 - kernel version ("uname -a"): Linux tank 2.6.23.14-64.fc7 #1 SMP Sun Jan 20 23:54:08 EST 2008 i686 i686 i386 GNU/Linux - graphics card ("/sbin/lspci") 01:00.0 VGA compatible controller: ATI Technologies Inc M56P [Radeon Mobility X1600] - graphics driver installed ATI 8.45.4 (use the Catalyst Control center to recover the information) - OpenGL support ("glxinfo") [simone at tank ~]$ glxinfo name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.2 server glx extensions: GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_visual_select_group client glx vendor string: SGI client glx version string: 1.4 client glx extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory, GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap GLX version: 1.2 GLX extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_visual_select_group OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: ATI Mobility Radeon X1600 OpenGL version string: 2.1.7276 Release OpenGL extensions: GL_AMD_performance_monitor, GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_fragment_program, GL_ARB_fragment_shader, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_shader_objects, GL_ARB_shading_language_100, GL_ARB_shadow, GL_ARB_shadow_ambient, GL_ARB_texture_border_clamp, GL_ARB_texture_compression, GL_ARB_texture_cube_map, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, GL_ARB_texture_float, GL_ARB_texture_mirrored_repeat, GL_ARB_texture_rectangle, GL_ARB_transpose_matrix, GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_vertex_shader, GL_ARB_window_pos, GL_ATI_draw_buffers, GL_ATI_envmap_bumpmap, GL_ATI_fragment_shader, GL_ATI_meminfo, GL_ATI_separate_stencil, GL_ATI_texture_compression_3dc, GL_ATI_texture_env_combine3, GL_ATI_texture_float, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_func_separate, GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_compiled_vertex_array, GL_EXT_copy_texture, GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_framebuffer_object, GL_EXT_gpu_program_parameters, GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, GL_EXT_packed_pixels, GL_EXT_point_parameters, GL_EXT_rescale_normal, GL_EXT_secondary_color, GL_EXT_separate_specular_color, GL_EXT_shadow_funcs, GL_EXT_stencil_wrap, GL_EXT_subtexture, GL_EXT_texgen_reflection, GL_EXT_texture3D, GL_EXT_texture_compression_s3tc, GL_EXT_texture_cube_map, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod_bias, GL_EXT_texture_mirror_clamp, GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_texture_sRGB, GL_EXT_vertex_array, GL_KTX_buffer_region, GL_NV_blend_square, GL_NV_texgen_reflection, GL_SGIS_generate_mipmap, GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_WIN_swap_hint, WGL_EXT_swap_control ///======================================================================== Test procedure - run Scilab 5 from the command line "bin/scilab" - inside Scilab run "plot2d" - crash - :( I put the video on line here http://www.youtube.com/watch?v=13qeX98tAS8&feature=related - please report the error message on the terminal. Something like : [simone at tank scilab]$ bin/scilab [simone at tank scilab]$ Exception in thread "AWT-EventQueue-0" javax.media.opengl.GLException: Error making context current at com.sun.opengl.impl.x11.X11GLContext.makeCurrentImpl (X11GLContext.java:141) at com.sun.opengl.impl.x11.X11OffscreenGLContext.makeCurrentImpl (X11OffscreenGLContext.java:74) at com.sun.opengl.impl.GLContextImpl.makeCurrent (GLContextImpl.java:134) at com.sun.opengl.impl.GLDrawableHelper.invokeGL (GLDrawableHelper.java:182) at javax.media.opengl.GLJPanel.paintComponent(GLJPanel.java:661) at javax.swing.JComponent.paint(JComponent.java:1027) at javax.swing.JComponent.paintChildren(JComponent.java:864) at javax.swing.JComponent.paint(JComponent.java:1036) at javax.swing.JComponent.paintChildren(JComponent.java:864) at javax.swing.JComponent.paint(JComponent.java:1036) at org.flexdock.docking.defaults.DefaultDockingPort.paint (DefaultDockingPort.java:1976) at javax.swing.JComponent.paintToOffscreen(JComponent.java:5122) at javax.swing.BufferStrategyPaintManager.paint (BufferStrategyPaintManager.java:285) at javax.swing.RepaintManager.paint(RepaintManager.java:1128) at javax.swing.JComponent._paintImmediately (JComponent.java:5070) at javax.swing.JComponent.paintImmediately(JComponent.java:4880) at javax.swing.RepaintManager.paintDirtyRegions (RepaintManager.java:723) at javax.swing.RepaintManager.paintDirtyRegions (RepaintManager.java:679) at javax.swing.RepaintManager.seqPaintDirtyRegions (RepaintManager.java:659) at javax.swing.SystemEventQueueUtilities $ComponentWorkRequest.run(SystemEventQueueUtilities.java:128) at java.awt.event.InvocationEvent.dispatch (InvocationEvent.java:209) at java.awt.EventQueue.dispatchEvent(EventQueue.java:597) at java.awt.EventDispatchThread.pumpOneEventForFilters (EventDispatchThread.java:273) at java.awt.EventDispatchThread.pumpEventsForFilter (EventDispatchThread.java:183) at java.awt.EventDispatchThread.pumpEventsForHierarchy (EventDispatchThread.java:173) at java.awt.EventDispatchThread.pumpEvents (EventDispatchThread.java:168) at java.awt.EventDispatchThread.pumpEvents (EventDispatchThread.java:160) at java.awt.EventDispatchThread.run (EventDispatchThread.java:121) # # An unexpected error has been detected by Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x060663d7, pid=21815, tid=111479696 # # Java VM: Java HotSpot(TM) Server VM (1.6.0_03-b05 interpreted mode) # Problematic frame: # C [libX11.so.6+0x313d7] XQueryExtension+0x17 # # An error report file with more information is saved as hs_err_pid21815.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # bin/scilab: line 378: 21815 Aborted "$SCILABBIN" $* [simone at tank scilab]$ //=================================================================== So to speak : "Huston, we have a problem with ATI driver..." M. Simone Mannori - Scilab/Scicos Embedded Applications Eng From sylvestre.ledru at inria.fr Tue Feb 5 10:35:08 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Tue, 05 Feb 2008 10:35:08 +0100 Subject: FFTW enable by default Message-ID: <1202204108.30140.1206.camel@korcula.inria.fr> Hi, I would like to enable FFTW by default in the ./configure (and consequently rename the option --with-fftw => --without-fftw). Any objections ? Sylvestre From sylvestre.ledru at inria.fr Tue Feb 5 10:40:28 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Tue, 05 Feb 2008 10:40:28 +0100 Subject: [Scilab-Dev] STRING_V2 => string In-Reply-To: <47A73A57.3080204@inria.fr> References: <47A73A57.3080204@inria.fr> Message-ID: <1202204428.30140.1213.camel@korcula.inria.fr> By the way, this module is considered as stable now. However, we still have some optimisations to do on some functions. Sylvestre Le lundi 04 f?vrier 2008 ? 17:16 +0100, Pierre MARECHAL a ?crit : > Hi all, > > "string" module has been removed and replaced by "STRING_V2" module. > (http://viewvc.scilab.org/bin/cgi/viewvc.cgi/?view=query&dir=&file=&file_match=exact&who=pmarecha&who_match=exact&querysort=date&hours=2&date=explicit&mindate=2008-02-04+15%3A00%3A00&maxdate=2008-02-04+18%3A00%3A00&limit_changes=100) > > If you update your working copy > (svn://svn.scilab.org/scilab/trunk/scilab), you have to do a "make > distclean" in the SCI directory in order to re-compile Scilab : > > [SHELL ~/scilab] make distclean > [SHELL ~/scilab] rm -rf modules/string > [SHELL ~/scilab] rm -rf modules/STRING_V2 > [SHELL ~/scilab] svn update > [SHELL ~/scilab] ./configure > [SHELL ~/scilab] make all > > Best regards, > > Pierre > From sylvestre.ledru at inria.fr Tue Feb 5 10:46:56 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Tue, 05 Feb 2008 10:46:56 +0100 Subject: The configure now update SCI/etc/modules.xml.in Message-ID: <1202204816.30140.1217.camel@korcula.inria.fr> Hi again, Now, if you use the configure with the option ./configure --with-pvm it is going to update also the /etc/modules.xml file with the appropriate value. It is also doing this for Scicos and FFTW at the moment. Don't hesitate to tell me if I forgot one! Cheers Sylvestre PS: thanks Pierre for the idea. From yann.collette at renault.com Tue Feb 5 13:24:20 2008 From: yann.collette at renault.com (COLLETTE Yann) Date: Tue, 05 Feb 2008 13:24:20 +0100 Subject: Genetic algorithms and scilab In-Reply-To: <1202204428.30140.1213.camel@korcula.inria.fr> References: <47A73A57.3080204@inria.fr> <1202204428.30140.1213.camel@korcula.inria.fr> Message-ID: <47A85574.5080103@renault.com> Hello, I've made a Genetic Algorithm Toolbox. To test it, you will need to install some other packages: - Some test problems : http://www.scilab.org/contrib/index_contrib.php?page=displayContribution&fileID=1082 There are not loader.sce and builder.sce because I'm still implementing some test problems (a set of fortran functions from the La Cumparsita data set and the minpack2. The first one is nearly finished, I need to write the documentation for the other one). - The toolbox to manage parameters (like with optimset and optimget): http://www.scilab.org/contrib/index_contrib.php?page=displayContribution&fileID=1081 There is a loader.sce file and a builder.sce ... It's easier to manage extra parameters via a list of parameters than via a long command line. Using the param toolbox, I can leave on the command line only the most important parameters. All the fine tuning is done by setting up parameters values via the param toolbox. - The Genetic Algorithm toolbox: http://www.scilab.org/contrib/index_contrib.php?page=displayContribution&fileID=1080 There is a loader.sce file and a builder.sce ... In this toolbox, I've implemented some well known algorithms: - the classical genetic algorithm which works on binary string (tested in the second part of the demo file GAdemo.sce); - the evolutionnary algorithm which works directly on the variable (tested in the first part of the demo file GAdemo.sce for a continuous variable test problem and in the GAIsing2ddemo.sce for a combinatorial test problem); - MOGA: the multi-objective genetic algorithm. A classical multi-objective algorithm, be not really efficient. Tested in MOGAdemo.sce. - NSGA: the niched sharing genetic algorithm. A good improvement wrt MOGA. Tested in NSGAdemo.sce. - NSGA2: the 2nd version of NSGA. Certainly the best multi-objective algorithm so far. No extra parameters and quite efficient. See NSGA2demo.sce for a demonstration. The genetic algorithm is certainly the most flexible algorithm so far (not the most efficient). You can solve a large spectrum of problems with such a method. My question is: what do I need to do to see a genetic algorithm being included in scilab ? I am also very interested by some feedback to improve all these packages ... Your sincerely, Yann COLLETTE -- Disclaimer ------------------------------------ Ce message ainsi que les eventuelles pieces jointes constituent une correspondance privee et confidentielle a l'attention exclusive du destinataire designe ci-dessus. Si vous n'etes pas le destinataire du present message ou une personne susceptible de pouvoir le lui delivrer, il vous est signifie que toute divulgation, distribution ou copie de cette transmission est strictement interdite. Si vous avez recu ce message par erreur, nous vous remercions d'en informer l'expediteur par telephone ou de lui retourner le present message, puis d'effacer immediatement ce message de votre systeme. *** This e-mail and any attachments is a confidential correspondence intended only for use of the individual or entity named above. If you are not the intended recipient or the agent responsible for delivering the message to the intended recipient, you are hereby notified that any disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by phone or by replying this message, and then delete this message from your system. From sylvestre.ledru at inria.fr Tue Feb 5 14:14:43 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Tue, 05 Feb 2008 14:14:43 +0100 Subject: [Scilab-Dev] Genetic algorithms and scilab In-Reply-To: <47A85574.5080103@renault.com> References: <47A73A57.3080204@inria.fr> <1202204428.30140.1213.camel@korcula.inria.fr> <47A85574.5080103@renault.com> Message-ID: <1202217283.30140.1255.camel@korcula.inria.fr> [...] > My question is: what do I need to do to see a genetic algorithm being > included in scilab ? Having this stuff into Scilab could be interesting for users. However, we can only do that if : * you are OK to take care of this development (maintenance and debugging) * you understand that this dev will have to follow the release plan of Scilab (ie: low rate of release) * you add unitary tests for each function. Cheers, Sylvestre From yann.collette at renault.com Tue Feb 5 15:18:34 2008 From: yann.collette at renault.com (COLLETTE Yann) Date: Tue, 05 Feb 2008 15:18:34 +0100 Subject: [Scilab-Dev] Genetic algorithms and scilab In-Reply-To: <1202217283.30140.1255.camel@korcula.inria.fr> References: <47A73A57.3080204@inria.fr> <1202204428.30140.1213.camel@korcula.inria.fr> <47A85574.5080103@renault.com> <1202217283.30140.1255.camel@korcula.inria.fr> Message-ID: <47A8703A.5090002@renault.com> Sylvestre Ledru a ?crit : > [...] > > >> My question is: what do I need to do to see a genetic algorithm being >> included in scilab ? >> > Having this stuff into Scilab could be interesting for users. > > However, we can only do that if : > * you are OK to take care of this development (maintenance and debugging) > OK for me > * you understand that this dev will have to follow the release plan of Scilab (ie: low rate of release) > What is a "low rate of release" ? > * you add unitary tests for each function. > OK, I will have a look at the unitary tests in some scilab modules to see how these tests work. > Cheers, > Sylvestre > > -- Disclaimer ------------------------------------ Ce message ainsi que les eventuelles pieces jointes constituent une correspondance privee et confidentielle a l'attention exclusive du destinataire designe ci-dessus. Si vous n'etes pas le destinataire du present message ou une personne susceptible de pouvoir le lui delivrer, il vous est signifie que toute divulgation, distribution ou copie de cette transmission est strictement interdite. Si vous avez recu ce message par erreur, nous vous remercions d'en informer l'expediteur par telephone ou de lui retourner le present message, puis d'effacer immediatement ce message de votre systeme. *** This e-mail and any attachments is a confidential correspondence intended only for use of the individual or entity named above. If you are not the intended recipient or the agent responsible for delivering the message to the intended recipient, you are hereby notified that any disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by phone or by replying this message, and then delete this message from your system. From pierre.marechal at inria.fr Tue Feb 5 15:23:22 2008 From: pierre.marechal at inria.fr (Pierre MARECHAL) Date: Tue, 05 Feb 2008 15:23:22 +0100 Subject: [Scilab-Dev] Genetic algorithms and scilab In-Reply-To: <47A8703A.5090002@renault.com> References: <47A73A57.3080204@inria.fr> <1202204428.30140.1213.camel@korcula.inria.fr> <47A85574.5080103@renault.com> <1202217283.30140.1255.camel@korcula.inria.fr> <47A8703A.5090002@renault.com> Message-ID: <47A8715A.3010206@inria.fr> Hi Yann, >> * you add unitary tests for each function. > OK, I will have a look at the unitary tests in some scilab modules to > see how these tests work. You can also have look to the test_run() function : -->help test_run Pierre -- =================================================== Pierre MARECHAL INRIA - Centre de Recherche de Paris - Rocquencourt Domaine de Voluceau - B.P. 105 78153 Le Chesnay Cedex =================================================== Equipe-Projet Scilab B?timent 1B - Bureau 008 Email : pierre.marechal at inria.fr =================================================== From sylvestre.ledru at inria.fr Tue Feb 5 15:31:51 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Tue, 05 Feb 2008 15:31:51 +0100 Subject: [Scilab-Dev] Genetic algorithms and scilab In-Reply-To: <47A8703A.5090002@renault.com> References: <47A73A57.3080204@inria.fr> <1202204428.30140.1213.camel@korcula.inria.fr> <47A85574.5080103@renault.com> <1202217283.30140.1255.camel@korcula.inria.fr> <47A8703A.5090002@renault.com> Message-ID: <1202221911.30140.1277.camel@korcula.inria.fr> > > * you understand that this dev will have to follow the release plan of Scilab (ie: low rate of release) > > > What is a "low rate of release" ? At the moment, we will keep the same release schema. IE, one big release every 18 months (more or less) and a small one every 6 (but you may have noticed that we haven't respected this schedule during the last few months ;) > > * you add unitary tests for each function. > > > OK, I will have a look at the unitary tests in some scilab modules to > see how these tests work. It is straightforward. In a .tst file, you write some Scilab code using your function (normal use and special uses), for example: http://viewvc.scilab.org/bin/cgi/viewvc.cgi/trunk/scilab/modules/string/tests/unit_tests/strindex.tst?revision=22167&view=markup You run the test series on your module ( see: http://wiki.scilab.org/Unitary_and_non_regression_testing_of_Scilab ) It is going to complain since you don't have any reference for your test. But in the mean time, it is going to produce a .dia (for diary). Rename it to .dia.ref and launch the test again. Your test will be successfull. We use them more and more. Thanks to these tests, if we change anything in the "core" of Scilab, we can see very quickly the impact it will have. An user can also have quickly an idea of what we will broken on his Scilab if he tests with exotic lib or platform. Sylvestre From fvogelnew1 at free.fr Tue Feb 5 22:02:38 2008 From: fvogelnew1 at free.fr (=?ISO-8859-1?Q?Fran=E7ois_Vogel?=) Date: Tue, 05 Feb 2008 22:02:38 +0100 Subject: [Scilab-Dev] Genetic algorithms and scilab In-Reply-To: <1202217283.30140.1255.camel@korcula.inria.fr> References: <47A73A57.3080204@inria.fr> <1202204428.30140.1213.camel@korcula.inria.fr> <47A85574.5080103@renault.com> <1202217283.30140.1255.camel@korcula.inria.fr> Message-ID: <47A8CEEE.8020504@free.fr> Sylvestre Ledru said on 05/02/2008 14:14: > However, we can only do that if : > * you are OK to take care of this development (maintenance and > debugging) > * you understand that this dev will have to follow the release plan of > Scilab (ie: low rate of release) > * you add unitary tests for each function. No other condition? Any license can be used for his contribution? That's good news. Francois From sylvestre.ledru at inria.fr Wed Feb 6 09:05:52 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Wed, 06 Feb 2008 09:05:52 +0100 Subject: [Scilab-Dev] Genetic algorithms and scilab In-Reply-To: <47A8CEEE.8020504@free.fr> References: <47A73A57.3080204@inria.fr> <1202204428.30140.1213.camel@korcula.inria.fr> <47A85574.5080103@renault.com> <1202217283.30140.1255.camel@korcula.inria.fr> <47A8CEEE.8020504@free.fr> Message-ID: <1202285152.7441.16.camel@korcula.inria.fr> Le mardi 05 f?vrier 2008 ? 22:02 +0100, Fran?ois Vogel a ?crit : > Sylvestre Ledru said on 05/02/2008 14:14: > > However, we can only do that if : > > * you are OK to take care of this development (maintenance and > > debugging) > > * you understand that this dev will have to follow the release plan of > > Scilab (ie: low rate of release) > > * you add unitary tests for each function. > > > No other condition? Any license can be used for his contribution? Yann has signed the developer agreement. Sylvestre From enrico.segre at weizmann.ac.il Wed Feb 6 10:46:28 2008 From: enrico.segre at weizmann.ac.il (Enrico Segre) Date: Wed, 06 Feb 2008 11:46:28 +0200 Subject: bitand, bitor Message-ID: <1202291188.24980.75.camel@segre-pc2.weizmann.ac.il> Hi there, the recent bug activity about bitand, bitor & the like made me wonder and look a bit into the functions themselves. Maybe I miss something, but why at all does one need these contraptions? As they are written, besides argument parsing, now these functions use an absurd detour via converting their arguments to "binary" string, then to ascii codes, then make string substitutions, then again convert back to floats - all this is certainly not performant. Why can't one just use int32(x) & int32(y)? Is there a consideration of MAXINT? (a float can represent a 52bit integer without loss of precision, which is more than 32bit -- consider dec2hex(2^53+[-2:2]) But even then, that could be treated appropriately without waiting for int64, say, with a=2^32 z=double(int32(x/a) & int32(y/a))*a z=z+double(int32(x-z) & int32(y-z)) Enrico From pierre.marechal at inria.fr Wed Feb 6 11:07:53 2008 From: pierre.marechal at inria.fr (Pierre MARECHAL) Date: Wed, 06 Feb 2008 11:07:53 +0100 Subject: [Scilab-Dev] bitand, bitor In-Reply-To: <1202291188.24980.75.camel@segre-pc2.weizmann.ac.il> References: <1202291188.24980.75.camel@segre-pc2.weizmann.ac.il> Message-ID: <47A986F9.50404@inria.fr> Hi Enrico, These functions have been written by a developper that has left the team and I don't why bitor() and bitand() are coded in this way. For the time being, I've just dealed with argument check without paying attention to the algorithm. But you're totally right, I'll use & and | operators. Thanks Regards Pierre Enrico Segre a ?crit : > Hi there, > the recent bug activity about bitand, bitor & the like made me wonder > and look a bit into the functions themselves. Maybe I miss something, > but why at all does one need these contraptions? As they are written, > besides argument parsing, now these functions use an absurd detour via > converting their arguments to "binary" string, then to ascii codes, then > make string substitutions, then again convert back to floats - all this > is certainly not performant. Why can't one just use int32(x) & > int32(y)? > Is there a consideration of MAXINT? (a float can represent a 52bit > integer without loss of precision, which is more than 32bit -- consider > dec2hex(2^53+[-2:2]) But even then, that could be treated appropriately > without waiting for int64, say, with > > a=2^32 > z=double(int32(x/a) & int32(y/a))*a > z=z+double(int32(x-z) & int32(y-z)) > > Enrico > -- =================================================== Pierre MARECHAL INRIA - Centre de Recherche de Paris - Rocquencourt Domaine de Voluceau - B.P. 105 78153 Le Chesnay Cedex =================================================== Equipe-Projet Scilab B?timent 1B - Bureau 008 Email : pierre.marechal at inria.fr =================================================== From yann.collette at renault.com Wed Feb 6 14:50:30 2008 From: yann.collette at renault.com (COLLETTE Yann) Date: Wed, 06 Feb 2008 14:50:30 +0100 Subject: SciFunction In-Reply-To: <47A986F9.50404@inria.fr> References: <1202291188.24980.75.camel@segre-pc2.weizmann.ac.il> <47A986F9.50404@inria.fr> Message-ID: <47A9BB26.70501@renault.com> Hello, I'm trying to interface an optimisation method under scilab (the optimization method is in fortran and I'm writing the interface in C). My question is: how to retrieve the output parameters of a call to SciFunction ? The following program is called several times during the run of the optimization: ///////////////////////////////////// // First I create some parameters. The first one will contain the "x" vector and the second one the gradient of the output (I do this to give the correct size to the stack. If I don't do this, scilab says it doesn't know the ibegin + 1 parameter). // Create the first variable: x n_x1_tmp = n_x; m_x1_tmp = m_x; CreateVar(ibegin,"d",&n_x1_tmp,&m_x1_tmp,&l_x1_tmp); for(i=0;i0) { sciprint("conmin: error when calling objective function\n"); return 0; } /* End If */ n1 = ndv + 2; //////////////////////////////////// // Now I get the parameters via GetRhsVar. I hope that the size of the ibegin and ibegin+1 parameters are set correctly by SciFunction (first free the memory and then mallocated correctly to get the output parameters). // Get fobj GetRhsVar(ibegin, "d",&n_fobj_tmp, &m_fobj_tmp, &l_fobj_tmp); // Get gradient of fobj GetRhsVar(ibegin+1,"d",&n_dfobj_tmp,&m_dfobj_tmp,&l_dfobj_tmp); ///////////////////////////////////// // Finally, I store all the output parameters in temporary arrays (because just after the objective function, I called the constraints also via SciFunction). // Fill C2F(cnmn1).obj: objective function value C2F(cnmn1).obj = *dstk(l_fobj_tmp); // DF(N1) Analytic gradient of the objective function for the current decision variables, X(I). DF(I) contains the partial derivative // of OBJ with respect to X(I). Calculate DF(I), I = 1, NDV if INFO = 3 or INFO = 4 and if NFDG = 0 or NFDG = 2. double * DF = (double *)malloc(n1*sizeof(double)); // Fill DF(N1): gradient of objective function value for(j=0;j References: <47A73A57.3080204@inria.fr> <1202204428.30140.1213.camel@korcula.inria.fr> <47A85574.5080103@renault.com> <1202217283.30140.1255.camel@korcula.inria.fr> <47A8CEEE.8020504@free.fr> <1202285152.7441.16.camel@korcula.inria.fr> Message-ID: <47A9C677.20302@renault.com> Hello, A little question regarding a C interfacing of a fortan function: When I have a fortran variable A(n1,n2) as a parameter of a subroutine, is it a double ** array in C or a double * ? YC -- Disclaimer ------------------------------------ Ce message ainsi que les eventuelles pieces jointes constituent une correspondance privee et confidentielle a l'attention exclusive du destinataire designe ci-dessus. Si vous n'etes pas le destinataire du present message ou une personne susceptible de pouvoir le lui delivrer, il vous est signifie que toute divulgation, distribution ou copie de cette transmission est strictement interdite. Si vous avez recu ce message par erreur, nous vous remercions d'en informer l'expediteur par telephone ou de lui retourner le present message, puis d'effacer immediatement ce message de votre systeme. *** This e-mail and any attachments is a confidential correspondence intended only for use of the individual or entity named above. If you are not the intended recipient or the agent responsible for delivering the message to the intended recipient, you are hereby notified that any disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by phone or by replying this message, and then delete this message from your system. From yann.collette at renault.com Thu Feb 7 15:01:17 2008 From: yann.collette at renault.com (COLLETTE Yann) Date: Thu, 07 Feb 2008 15:01:17 +0100 Subject: Scilab and DDE In-Reply-To: <47A8CEEE.8020504@free.fr> References: <47A73A57.3080204@inria.fr> <1202204428.30140.1213.camel@korcula.inria.fr> <47A85574.5080103@renault.com> <1202217283.30140.1255.camel@korcula.inria.fr> <47A8CEEE.8020504@free.fr> Message-ID: <47AB0F2D.3060500@renault.com> Hello, I've found some really interesting non-documented commands: ddeopen, ddeclose, ddeexec, ddepoke, ddereq and ddeisopen. I want to use these commands to open a DDE connection with Excel and put some data inside excel, get some data from excel. How to use these commands ? How to retrieve the list of available DDE commands from excel ? YC -- Disclaimer ------------------------------------ Ce message ainsi que les eventuelles pieces jointes constituent une correspondance privee et confidentielle a l'attention exclusive du destinataire designe ci-dessus. Si vous n'etes pas le destinataire du present message ou une personne susceptible de pouvoir le lui delivrer, il vous est signifie que toute divulgation, distribution ou copie de cette transmission est strictement interdite. Si vous avez recu ce message par erreur, nous vous remercions d'en informer l'expediteur par telephone ou de lui retourner le present message, puis d'effacer immediatement ce message de votre systeme. *** This e-mail and any attachments is a confidential correspondence intended only for use of the individual or entity named above. If you are not the intended recipient or the agent responsible for delivering the message to the intended recipient, you are hereby notified that any disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by phone or by replying this message, and then delete this message from your system. From sylvestre.ledru at inria.fr Thu Feb 7 15:32:36 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Thu, 07 Feb 2008 15:32:36 +0100 Subject: License of Scilab 5 Message-ID: <1202394756.24488.93.camel@korcula.inria.fr> Hello, A big step for Scilab! It took a while, but here we are. The INRIA and the Scilab Consortium have finally decided to change the license of Scilab to CeCILL [1] [2]. The CeCILL (from "CEA CNRS INRIA Logiciel Libre") license is a free (as beer and speech) license. This license has been designed for both french and international laws and to be "GPL-Compatible" [3]. Thanks to this change, we send a strong signal of openness and free software orientation. By this action, we also intend to extend the use of Scilab by other free projects/software and facilitate the integration of Scilab in free Linux/BSD distributions. Regards, Sylvestre PS: Technically speaking, we will soon release the Alpha version of Scilab 5. This version will be released under the term of the CeCILL license. However, we are aware of a few licenses issues which will be dealt with later. [1] http://www.cecill.info/index.en.html [2] http://en.wikipedia.org/wiki/CeCILL [3] http://www.fsf.org/licensing/licenses/#CeCILL From sylvestre.ledru at inria.fr Thu Feb 7 23:32:44 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Thu, 07 Feb 2008 23:32:44 +0100 Subject: getdebuginfo() Message-ID: <1202423564.3434.18.camel@zlarin.inria.fr> Hello guys, I added a function in scilab called [dynamic_info,compilation_info]=getdebuginfo() In the dynamic part, at the moment, under Linux, I return all the memory (swap, cached and physical) information I can find. I also return some stuff about the version of the OS. [1] I am going to add more information about the CPU. Do you see anything else I could add in this function ? Sylvestre [1] -->getdebuginfo() ans = !Total memory: 2075292 ! ! ! !Used memory: 1957132 ! ! ! !Free memory: 118160 ! ! ! !Shared memory: 0 ! ! ! !Buffers memory: 82192 ! ! ! !Cached memory: 181492 ! ! ! !Used -/+ buffers/cache: 1693448 ! ! ! !Free -/+ buffers/cache: 381844 ! ! ! !Total swap: 3903784 ! ! ! !Used swap: 1962404 ! ! ! !Free swap: 1941380 ! ! ! !OS version: Linux 2.6.22-3-686 ! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Ceci est une partie de message num?riquement sign?e URL: From Simone.Mannori at inria.fr Fri Feb 8 04:33:07 2008 From: Simone.Mannori at inria.fr (Simone Mannori) Date: Fri, 08 Feb 2008 04:33:07 +0100 Subject: [Scilab-Dev] getdebuginfo() In-Reply-To: <1202423564.3434.18.camel@zlarin.inria.fr> References: <1202423564.3434.18.camel@zlarin.inria.fr> Message-ID: <1202441587.12066.10.camel@buta.inria.fr> Hi Sylvestre, nice job :) 1) please be terse about "cpuinfo" : a) model b) cores c) MHz will be more than enough 2) a parallel function for the graphics pipeline will be _extremely_ useful: a) extract the single line relative to the graphic card inside "lspci" b) extract some terse info using "xlginfo" (too verbose for my personal taste) The second function could be used to simplify our support for 3D cards. THX Simone //**----------------------------------------------------------------- On Thu, 2008-02-07 at 23:32 +0100, Sylvestre Ledru wrote: > Hello guys, > > I added a function in scilab called > [dynamic_info,compilation_info]=getdebuginfo() > > In the dynamic part, at the moment, under Linux, I return all the memory > (swap, cached and physical) information I can find. I also return some > stuff about the version of the OS. [1] > I am going to add more information about the CPU. > > Do you see anything else I could add in this function ? > > Sylvestre > > [1] > -->getdebuginfo() > ans = > > !Total memory: 2075292 ! > ! ! > !Used memory: 1957132 ! > ! ! > !Free memory: 118160 ! > ! ! > !Shared memory: 0 ! > ! ! > !Buffers memory: 82192 ! > ! ! > !Cached memory: 181492 ! > ! ! > !Used -/+ buffers/cache: 1693448 ! > ! ! > !Free -/+ buffers/cache: 381844 ! > ! ! > !Total swap: 3903784 ! > ! ! > !Used swap: 1962404 ! > ! ! > !Free swap: 1941380 ! > ! ! > !OS version: Linux 2.6.22-3-686 ! > From fvogelnew1 at free.fr Fri Feb 8 08:25:00 2008 From: fvogelnew1 at free.fr (=?ISO-8859-1?Q?Fran=E7ois_Vogel?=) Date: Fri, 08 Feb 2008 08:25:00 +0100 Subject: License of Scilab 5 In-Reply-To: <1202394756.24488.93.camel@korcula.inria.fr> References: <1202394756.24488.93.camel@korcula.inria.fr> Message-ID: <47AC03CC.5080801@free.fr> Sylvestre Ledru said on 07/02/2008 15:32: > The INRIA and the Scilab Consortium have finally decided to change the > license of Scilab to CeCILL [1] [2]. So you abandoned the dual licensing scheme. Please confirm. Moreover which CeCILL are you talking about here? Cecill-A ? please clarify. > PS: Technically speaking, we will soon release the Alpha version of > Scilab 5. This version will be released under the term of the CeCILL > license. However, we are aware of a few licenses issues which will be > dealt with later. Scipad must be among those. Please confirm. Several contributors have sent a formal letter to the Scilab Consortium about the license change recently and we would like to get a formal answer from the Consortium (and not from Sylvestre Ledru). This can also be brought to the public place if the Consortium likes it better. Francois From sylvestre.ledru at inria.fr Fri Feb 8 10:16:27 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Fri, 08 Feb 2008 10:16:27 +0100 Subject: function "ls" Message-ID: <1202462188.24488.177.camel@korcula.inria.fr> Hi, I am thinking about changing the behaviour of the function ls http://www.scilab.org/product/man/index.php?module=fileio&page=ls.htm I would like to remove the second input argument for a few reasons: * security issues. This simple example shows how weak it is : ls("*.sci","`echo hacked >/tmp/hmhm`") * Compatiblity and portability. A user working under Linux and using tricks on this function won't have the same result under proprietary operating systems. * We are too closely related to the ls behaviour on the platform * The code could be directly pluged to the listfiles and therefore facilitate the maintenance (It is already the case under Windows). Any objections ? Sylvestre From allan.cornet at inria.fr Fri Feb 8 10:26:25 2008 From: allan.cornet at inria.fr (Allan CORNET) Date: Fri, 08 Feb 2008 10:26:25 +0100 Subject: [Scilab-Dev] function "ls" In-Reply-To: <1202462188.24488.177.camel@korcula.inria.fr> References: <1202462188.24488.177.camel@korcula.inria.fr> Message-ID: <7.0.1.0.2.20080208102453.03f0fd40@inria.fr> Hi, +1 to use listfiles in ls on linux & windows Allan Le 10:16 AM 2/8/2008,Sylvestre Ledru ?crit: >Hi, > >I am thinking about changing the behaviour of the function ls >http://www.scilab.org/product/man/index.php?module=fileio&page=ls.htm > >I would like to remove the second input argument for a few reasons: >* security issues. This simple example shows how weak it is : > ls("*.sci","`echo hacked >/tmp/hmhm`") > >* Compatiblity and portability. A user working under Linux and using >tricks on this function won't have the same result under proprietary >operating systems. > >* We are too closely related to the ls behaviour on the platform > >* The code could be directly pluged to the listfiles and therefore >facilitate the maintenance (It is already the case under Windows). > >Any objections ? > >Sylvestre ============================================== Allan CORNET Scilab Consortium http://www.scilab.org INRIA - Unit? de Recherche de Rocquencourt Domaine de Voluceau - B.P. 105 78153 Le Chesnay Cedex ============================================== Projet Scilab B?timent 1B - Bureau 009 Email : allan.cornet at inria.fr ============================================== -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierre.marechal at inria.fr Fri Feb 8 10:30:28 2008 From: pierre.marechal at inria.fr (Pierre MARECHAL) Date: Fri, 08 Feb 2008 10:30:28 +0100 Subject: [Scilab-Dev] function "ls" In-Reply-To: <1202462188.24488.177.camel@korcula.inria.fr> References: <1202462188.24488.177.camel@korcula.inria.fr> Message-ID: <47AC2134.6060204@inria.fr> I agree with you, unix() call into .sci macros (of scilab distrib.) has to be prohibited. Pierre Sylvestre Ledru a ?crit : > Hi, > > I am thinking about changing the behaviour of the function ls > http://www.scilab.org/product/man/index.php?module=fileio&page=ls.htm > > I would like to remove the second input argument for a few reasons: > * security issues. This simple example shows how weak it is : > ls("*.sci","`echo hacked >/tmp/hmhm`") > > * Compatiblity and portability. A user working under Linux and using > tricks on this function won't have the same result under proprietary > operating systems. > > * We are too closely related to the ls behaviour on the platform > > * The code could be directly pluged to the listfiles and therefore > facilitate the maintenance (It is already the case under Windows). > > Any objections ? > > Sylvestre > > -- =================================================== Pierre MARECHAL INRIA - Centre de Recherche de Paris - Rocquencourt Domaine de Voluceau - B.P. 105 78153 Le Chesnay Cedex =================================================== Equipe-Projet Scilab B?timent 1B - Bureau 008 Email : pierre.marechal at inria.fr =================================================== -------------- next part -------------- An HTML attachment was scrubbed... URL: From vincent.couvert at inria.fr Fri Feb 8 10:35:31 2008 From: vincent.couvert at inria.fr (Vincent COUVERT) Date: Fri, 08 Feb 2008 10:35:31 +0100 Subject: [Scilab-Dev] function "ls" In-Reply-To: <1202462188.24488.177.camel@korcula.inria.fr> References: <1202462188.24488.177.camel@korcula.inria.fr> Message-ID: <47AC2263.9090406@inria.fr> Hi, I totally agree with you. You can remove this securoty issue and base ls on listfiles. Vincent Sylvestre Ledru a ?crit : > Hi, > > I am thinking about changing the behaviour of the function ls > http://www.scilab.org/product/man/index.php?module=fileio&page=ls.htm > > I would like to remove the second input argument for a few reasons: > * security issues. This simple example shows how weak it is : > ls("*.sci","`echo hacked >/tmp/hmhm`") > > * Compatiblity and portability. A user working under Linux and using > tricks on this function won't have the same result under proprietary > operating systems. > > * We are too closely related to the ls behaviour on the platform > > * The code could be directly pluged to the listfiles and therefore > facilitate the maintenance (It is already the case under Windows). > > Any objections ? > > Sylvestre > > > -- ============================================== Vincent COUVERT Centre de Recherche INRIA Paris-Rocquencourt Domaine de Voluceau - B.P. 105 78153 Le Chesnay Cedex ============================================== Equipe Projet SCILAB B?timent 1B - Bureau 013 Email : vincent.couvert at inria.fr T?l : +33 (0)1 39 63 54 46 Fax : +33 (0)1 39 63 55 94 ============================================== From sylvestre.ledru at inria.fr Fri Feb 8 11:38:47 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Fri, 08 Feb 2008 11:38:47 +0100 Subject: [Scilab-Dev] Re: License of Scilab 5 In-Reply-To: <47AC03CC.5080801@free.fr> References: <1202394756.24488.93.camel@korcula.inria.fr> <47AC03CC.5080801@free.fr> Message-ID: <1202467127.24488.184.camel@korcula.inria.fr> Le vendredi 08 f?vrier 2008 ? 08:25 +0100, Fran?ois Vogel a ?crit : > Sylvestre Ledru said on 07/02/2008 15:32: > > The INRIA and the Scilab Consortium have finally decided to change > the > > license of Scilab to CeCILL [1] [2]. > > So you abandoned the dual licensing scheme. Please confirm. As you said, not an answer for Sylvestre Ledru. > Moreover which CeCILL are you talking about here? Cecill-A ? please > clarify. In fact, there is no CeCILL-A. The first one is called CeCILL. http://www.cecill.info/licences.en.html Sylvestre From sylvestre.ledru at inria.fr Fri Feb 8 14:38:06 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Fri, 08 Feb 2008 14:38:06 +0100 Subject: [Scilab-Dev] SciFunction In-Reply-To: <47A9BB26.70501@renault.com> References: <1202291188.24980.75.camel@segre-pc2.weizmann.ac.il> <47A986F9.50404@inria.fr> <47A9BB26.70501@renault.com> Message-ID: <1202477886.24488.255.camel@korcula.inria.fr> HI Yann, I am not answering to your question (sorry). But I would like to inform you that we changed the data type declaration in CreateVar, GetRhsVar, etc for something less cryptic: + "c" => STRING_DATATYPE + "S" => MATRIX_OF_STRING_DATATYPE + "d" => MATRIX_OF_DOUBLE_DATATYPE + "r" => MATRIX_OF_RATIONAL_DATATYPE + "I" => MATRIX_OF_VARIABLE_SIZE_INTEGER_DATATYPE + "i" => MATRIX_OF_INTEGER_DATATYPE + "b" => MATRIX_OF_BOOLEAN_DATATYPE + "z" => MATRIX_OF_COMPLEX_DATATYPE + "s" => SPARSE_MATRIX_DATATYPE + "l" => LIST_DATATYPE + "t" => TYPED_LIST_DATATYPE + "m" => MATRIX_ORIENTED_TYPED_LIST_DATATYPE + "p" => SCILAB_POINTER_DATATYPE + "h" => GRAPHICAL_HANDLE_DATATYPE + "f" => EXTERNAL_DATATYPE You will find the list here: modules/core/includes/stackTypeVariable.h Cheers, Sylvestre Le mercredi 06 f?vrier 2008 ? 14:50 +0100, COLLETTE Yann a ?crit : > Hello, > > I'm trying to interface an optimisation method under scilab (the > optimization method is in fortran and I'm writing the interface in C). > My question is: how to retrieve the output parameters of a call to > SciFunction ? > The following program is called several times during the run of the > optimization: > > ///////////////////////////////////// > // First I create some parameters. The first one will contain the "x" > vector and the second one the gradient of the output (I do this to give > the correct size to the stack. If I don't do this, scilab says it > doesn't know the ibegin + 1 parameter). > > // Create the first variable: x > n_x1_tmp = n_x; > m_x1_tmp = m_x; > CreateVar(ibegin,"d",&n_x1_tmp,&m_x1_tmp,&l_x1_tmp); > for(i=0;i > // Create a fake 2nd variable on the stack. This will allow to call > GetRhsVar to retrieve the 2nd output argument > n_x2_tmp = 1; > m_x2_tmp = 1; > CreateVar(ibegin+1,"d",&n_x2_tmp,&m_x2_tmp,&l_x2_tmp); > > /////////////////////////////////// > // I call the scilab function via SciFunction > > > // Call to the scilab function > SciFunction(&ibegin,&l_fobj,&fobj_lhs,&fobj_rhs); > if (Err>0) > { > sciprint("conmin: error when calling objective function\n"); > return 0; > } /* End If */ > > n1 = ndv + 2; > > //////////////////////////////////// > // Now I get the parameters via GetRhsVar. I hope that the size of the > ibegin and ibegin+1 parameters are set correctly by SciFunction (first > free the memory and then mallocated correctly to get the output parameters). > // Get fobj > GetRhsVar(ibegin, "d",&n_fobj_tmp, &m_fobj_tmp, &l_fobj_tmp); > // Get gradient of fobj > GetRhsVar(ibegin+1,"d",&n_dfobj_tmp,&m_dfobj_tmp,&l_dfobj_tmp); > > ///////////////////////////////////// > // Finally, I store all the output parameters in temporary arrays > (because just after the objective function, I called the constraints > also via SciFunction). > > // Fill C2F(cnmn1).obj: objective function value > C2F(cnmn1).obj = *dstk(l_fobj_tmp); > > // DF(N1) Analytic gradient of the objective function for the current > decision variables, X(I). DF(I) contains the partial derivative > // of OBJ with respect to X(I). Calculate DF(I), I = 1, NDV if > INFO = 3 or INFO = 4 and if NFDG = 0 or NFDG = 2. > double * DF = (double *)malloc(n1*sizeof(double)); > // Fill DF(N1): gradient of objective function value > for(j=0;j > /////////////////////////////////////// > // Is my strategy good or do you recommend another method ? > > Your sincerely, > > Yann COLLETTE > > > -- Disclaimer ------------------------------------ > Ce message ainsi que les eventuelles pieces jointes constituent une correspondance privee et confidentielle a l'attention exclusive du destinataire designe ci-dessus. Si vous n'etes pas le destinataire du present message ou une personne susceptible de pouvoir le lui delivrer, il vous est signifie que toute divulgation, distribution ou copie de cette transmission est strictement interdite. Si vous avez recu ce message par erreur, nous vous remercions d'en informer l'expediteur par telephone ou de lui retourner le present message, puis d'effacer immediatement ce message de votre systeme. > *** > This e-mail and any attachments is a confidential correspondence intended only for use of the individual or entity named above. If you are not the intended recipient or the agent responsible for delivering the message to the intended recipient, you are hereby notified that any disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by phone or by replying this message, and then delete this message from your system. From ycollet at freesurf.fr Fri Feb 8 15:42:04 2008 From: ycollet at freesurf.fr (Collette Yann) Date: Fri, 08 Feb 2008 15:42:04 +0100 Subject: [Scilab-Dev] SciFunction In-Reply-To: <1202477886.24488.255.camel@korcula.inria.fr> References: <1202291188.24980.75.camel@segre-pc2.weizmann.ac.il> <47A986F9.50404@inria.fr> <47A9BB26.70501@renault.com> <1202477886.24488.255.camel@korcula.inria.fr> Message-ID: <47AC6A3C.5070408@freesurf.fr> Bonne et heureuse id?e. Ce sera beaucoup plus parlant. YC Sylvestre Ledru a ?crit : > HI Yann, > > I am not answering to your question (sorry). > But I would like to inform you that we changed the data type declaration > in CreateVar, GetRhsVar, etc for something less cryptic: > > + "c" => STRING_DATATYPE > + "S" => MATRIX_OF_STRING_DATATYPE > + "d" => MATRIX_OF_DOUBLE_DATATYPE > + "r" => MATRIX_OF_RATIONAL_DATATYPE > + "I" => MATRIX_OF_VARIABLE_SIZE_INTEGER_DATATYPE > + "i" => MATRIX_OF_INTEGER_DATATYPE > + "b" => MATRIX_OF_BOOLEAN_DATATYPE > + "z" => MATRIX_OF_COMPLEX_DATATYPE > + "s" => SPARSE_MATRIX_DATATYPE > + "l" => LIST_DATATYPE > + "t" => TYPED_LIST_DATATYPE > + "m" => MATRIX_ORIENTED_TYPED_LIST_DATATYPE > + "p" => SCILAB_POINTER_DATATYPE > + "h" => GRAPHICAL_HANDLE_DATATYPE > + "f" => EXTERNAL_DATATYPE > You will find the list here: > modules/core/includes/stackTypeVariable.h > > Cheers, > Sylvestre > > Le mercredi 06 f?vrier 2008 ? 14:50 +0100, COLLETTE Yann a ?crit : > >> Hello, >> >> I'm trying to interface an optimisation method under scilab (the >> optimization method is in fortran and I'm writing the interface in C). >> My question is: how to retrieve the output parameters of a call to >> SciFunction ? >> The following program is called several times during the run of the >> optimization: >> >> ///////////////////////////////////// >> // First I create some parameters. The first one will contain the "x" >> vector and the second one the gradient of the output (I do this to give >> the correct size to the stack. If I don't do this, scilab says it >> doesn't know the ibegin + 1 parameter). >> >> // Create the first variable: x >> n_x1_tmp = n_x; >> m_x1_tmp = m_x; >> CreateVar(ibegin,"d",&n_x1_tmp,&m_x1_tmp,&l_x1_tmp); >> for(i=0;i> >> // Create a fake 2nd variable on the stack. This will allow to call >> GetRhsVar to retrieve the 2nd output argument >> n_x2_tmp = 1; >> m_x2_tmp = 1; >> CreateVar(ibegin+1,"d",&n_x2_tmp,&m_x2_tmp,&l_x2_tmp); >> >> /////////////////////////////////// >> // I call the scilab function via SciFunction >> >> >> // Call to the scilab function >> SciFunction(&ibegin,&l_fobj,&fobj_lhs,&fobj_rhs); >> if (Err>0) >> { >> sciprint("conmin: error when calling objective function\n"); >> return 0; >> } /* End If */ >> >> n1 = ndv + 2; >> >> //////////////////////////////////// >> // Now I get the parameters via GetRhsVar. I hope that the size of the >> ibegin and ibegin+1 parameters are set correctly by SciFunction (first >> free the memory and then mallocated correctly to get the output parameters). >> // Get fobj >> GetRhsVar(ibegin, "d",&n_fobj_tmp, &m_fobj_tmp, &l_fobj_tmp); >> // Get gradient of fobj >> GetRhsVar(ibegin+1,"d",&n_dfobj_tmp,&m_dfobj_tmp,&l_dfobj_tmp); >> >> ///////////////////////////////////// >> // Finally, I store all the output parameters in temporary arrays >> (because just after the objective function, I called the constraints >> also via SciFunction). >> >> // Fill C2F(cnmn1).obj: objective function value >> C2F(cnmn1).obj = *dstk(l_fobj_tmp); >> >> // DF(N1) Analytic gradient of the objective function for the current >> decision variables, X(I). DF(I) contains the partial derivative >> // of OBJ with respect to X(I). Calculate DF(I), I = 1, NDV if >> INFO = 3 or INFO = 4 and if NFDG = 0 or NFDG = 2. >> double * DF = (double *)malloc(n1*sizeof(double)); >> // Fill DF(N1): gradient of objective function value >> for(j=0;j> >> /////////////////////////////////////// >> // Is my strategy good or do you recommend another method ? >> >> Your sincerely, >> >> Yann COLLETTE >> >> >> -- Disclaimer ------------------------------------ >> Ce message ainsi que les eventuelles pieces jointes constituent une correspondance privee et confidentielle a l'attention exclusive du destinataire designe ci-dessus. Si vous n'etes pas le destinataire du present message ou une personne susceptible de pouvoir le lui delivrer, il vous est signifie que toute divulgation, distribution ou copie de cette transmission est strictement interdite. Si vous avez recu ce message par erreur, nous vous remercions d'en informer l'expediteur par telephone ou de lui retourner le present message, puis d'effacer immediatement ce message de votre systeme. >> *** >> This e-mail and any attachments is a confidential correspondence intended only for use of the individual or entity named above. If you are not the intended recipient or the agent responsible for delivering the message to the intended recipient, you are hereby notified that any disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by phone or by replying this message, and then delete this message from your system. >> > > From bruno.jofret at inria.fr Tue Feb 12 07:59:51 2008 From: bruno.jofret at inria.fr (Bruno JOFRET) Date: Tue, 12 Feb 2008 07:59:51 +0100 Subject: TCL : Milestone and further investigations. Message-ID: <47B143E7.8070406@inria.fr> Hi there, Sorry for the delay, but I have been sick and busy for a while... So first, I beg your pardon for this pending situation, I did not want this thread to "die". Just want to gather all the informations and state we are involved in. Actual State : (Trunk Version) ========= I created a separated TCL thread in Scilab in order to have all TCL Gui no more muddy. It fixes BUG 2514 and 2640 (for me, do you all agree ?). Extended features : - Separate TCL "update" loop - TCL_* Commands available (except TCL_EvalFile, see below) - Recursive commands using ScilabEval & TCL_EvalStr are working. (For this issue, can you Francois and Enrico tell me the need of such a think. I guess it was for some synchro but I confess it looks obscure to me) Broken stuff : - Scipad Debug Mode - TCL_EvalFile. Investigations : (Dev version, not published in order to have an operationnal Trunk) ========== - Doing some active loops in Scipad freeze to update process. (But if you kill the loop from scilab, everything came right back). I am trying 2 solutions : 1-Join the "main" Scilab thread to execute the script 2-Launch another thread... I face troubles for the 2 cases, despite the fact I locked Scilab "run" process to only have a single execution. - Scipad Debug Mode is not working anymore : I did not have enough time to investigate on that. Is there any wiki page or whatsoever describing the communication process between Scilab & Scipad ? - TCL_EvalFile : There is a simple solution, but Ido not know if it's effective or not : TCL_EvalFile(file) <=> TCL_EvalStr("source "+file) When I will have free time, I will this hack and test it. This might be a final solution but it may unlock this situation. I hope I did not forget any remarks/question. If i did, feel free to answer back :-P I will mail each time I commit a new step on that work. Regards, -- Bruno JOFRET Project Engineer ___SCILAB - INRIA Rocquencourt___ Domaine de Voluceau - B.P. 105 78153 Le Chesnay Cedex Tel : (+33/0)1.39.63.58.63 Mailto : bruno.jofret at inria.fr http://www.scilab.org From enrico.segre at weizmann.ac.il Tue Feb 12 09:06:36 2008 From: enrico.segre at weizmann.ac.il (Enrico Segre) Date: Tue, 12 Feb 2008 10:06:36 +0200 Subject: [Scilab-Dev] TCL : Milestone and further investigations. In-Reply-To: <47B143E7.8070406@inria.fr> References: <47B143E7.8070406@inria.fr> Message-ID: <1202803596.3635.27.camel@segre-pc2.weizmann.ac.il> Bruno, I'm sorry, but as for me, I can't build the trunk on the two machines I work most (bugs 2678 and 2709) so I can't test. I have no time for trying yet another installation, or download every nightly build to check if it accidentally works. > Is there any wiki > page or whatsoever describing > the communication process between Scilab & Scipad ? ROFL. Well, if it helps the communication we could think of starting one, using the discussion in many of the "ScilabEval" bugs in bugzilla as a starting point. Enrico From mottelet at dma.utc.fr Tue Feb 12 09:37:15 2008 From: mottelet at dma.utc.fr (mottelet at dma.utc.fr) Date: Tue, 12 Feb 2008 09:37:15 +0100 Subject: [Scilab-Dev] TCL : Milestone and further investigations. In-Reply-To: <47B143E7.8070406@inria.fr> References: <47B143E7.8070406@inria.fr> Message-ID: <1202805435.47b15abb5b2b8@mail.hds.utc.fr> > - Recursive commands using ScilabEval & TCL_EvalStr are working. > (For this issue, can you Francois and Enrico tell me the need of such a > think. I guess it was for some synchro > but I confess it looks obscure to me) Not obscure, but vital As far as I am concerned : when you have a Tk gui with a ScilabEval callback, for example on a button, which has to make some computations (this is Scilab's job) and display the result back in the gui, then there is no other way : the callback script, which is called from Tk by ScilabEval, must use a TCL_SetVar. My 2 cents... S. ------------------------------------------------- From sylvestre.ledru at inria.fr Tue Feb 12 11:27:34 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Tue, 12 Feb 2008 11:27:34 +0100 Subject: Completion in command line Message-ID: <1202812054.3414.789.camel@korcula.inria.fr> Hi, I added the completion when Scilab is used in command line under GNU/Linux / Unix. It is based on the same completion code as in Jrosetta. For now, it is only working on the first string. -->getv[TABULATION] getvalue getvariablesonstack getversion Cheers, Sylvestre From sylvestre.ledru at inria.fr Tue Feb 12 11:57:52 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Tue, 12 Feb 2008 11:57:52 +0100 Subject: [Scilab-Dev] TCL : Milestone and further investigations. In-Reply-To: <1202803596.3635.27.camel@segre-pc2.weizmann.ac.il> References: <47B143E7.8070406@inria.fr> <1202803596.3635.27.camel@segre-pc2.weizmann.ac.il> Message-ID: <1202813872.3414.804.camel@korcula.inria.fr> Le mardi 12 f?vrier 2008 ? 10:06 +0200, Enrico Segre a ?crit : > Bruno, > I'm sorry, but as for me, I can't build the trunk on the two machines I > work most (bugs 2678 and 2709) I am working on the bug 2709 (Actually, I am waiting for Enrico to confirm if it is fixed or not). For the bug 2678, it is the 64 bits bug of the stack. I have to spend more time on this. Sylvestre From fvogelnew1 at free.fr Tue Feb 12 14:02:46 2008 From: fvogelnew1 at free.fr (fvogelnew1 at free.fr) Date: Tue, 12 Feb 2008 14:02:46 +0100 Subject: [Scilab-Dev] TCL : Milestone and further investigations. In-Reply-To: <47B143E7.8070406@inria.fr> References: <47B143E7.8070406@inria.fr> Message-ID: <1202821366.47b198f6030e4@imp.free.fr> Selon Bruno JOFRET : > It fixes BUG 2514 and 2640 (for me, do you all agree ?). I think it does, I remember having checked some weeks ago (was however not perfect I think), but I can't check on Linux right now since I'm far away from home. > - Recursive commands using ScilabEval & TCL_EvalStr are working. I'n not so sure. Look at this (in debug(-1) mode so that you can see the output of the queueing and unqueueing processes): -->TCL_EvalStr("ScilabEval a=10") << << Btw, in Scilab5 the width of the debug(-1) output has become much narrower than it was in Scilab 4.x. Doesn't help readability and should be fixed too. Moreover: -->TCL_EvalStr("ScilabEval TCL_EvalStr(""pwd"")") TCL_EvalScilabCmd TCL_EvalStr("pwd") ans = --> <<< hit enter here, apart from this, this is OK below Unqueuing TCL_EvalStr("pwd") - No optio (end) n BUT: -->TCL_EvalStr("ScilabEval TCL_EvalStr(""set a 1"")") TCL_EvalScilabCmd TCL_EvalStr("set a 1") ans = --> <<< hit enter here Unqueuing TCL_EvalStr("set - No option TCL_EvalStr("set !--error 31 Incorrect string. while executing a callback --> Apparently a problem when the string passed contains spaces. Which means I think you're wrong when you say that recursive commands using ScilabEval & TCL_EvalStr are working, such as TCL_EvalStr("ScilabEval TCL_EvalStr(""ScilabEval a=7"")") > - TCL_EvalFile : > There is a simple solution, A simple solution to what problem? Why doesn't it work any more? Why is the current code not compatible with your changes? This looks strange to me since it's a similar code for TCL_EvalStr and you state that the latter is working. > I hope I did not forget any remarks/question. Did I miss your answers to my email somewhere in January where I asked a number of wuestions about what you're doing exactly (I don't have this email at hand sorry, not even its send date)? Francois From fvogelnew1 at free.fr Tue Feb 12 14:15:08 2008 From: fvogelnew1 at free.fr (fvogelnew1 at free.fr) Date: Tue, 12 Feb 2008 14:15:08 +0100 Subject: [Scilab-Dev] TCL : Milestone and further investigations. In-Reply-To: <1202821366.47b198f6030e4@imp.free.fr> References: <47B143E7.8070406@inria.fr> <1202821366.47b198f6030e4@imp.free.fr> Message-ID: <1202822108.47b19bdc1da79@imp.free.fr> Selon fvogelnew1 at free.fr: > Selon Bruno JOFRET : > > It fixes BUG 2514 and 2640 (for me, do you all agree ?). > > I think it does, I remember having checked some weeks ago (was however not > perfect I think), but I can't check on Linux right now since I'm far away > from home. After all even bug 2514 is not completely fixed. Test case: 1. Open Scilab 5. 2. Open Scipad 3. type debug(-1) in the Scilab console (just so that you can see what's happening) 4. In Scipad type anything having a help file, say the word function 5. Place the cursor in Scipad somewhere inside the word function 6. Hit Ctrl-F1 This launches a ScilabEval command having "help ""function""" as string, and with no option. In the shell you can see: TCL_EvalScilabCmd help "fu (end) nction" --> Note that the help widget doesn't open at this stage. 7. Now hit enter in the Scilab shell. The following gets displayed: Unqueuing help "functio (end) n" - No option --> and the help widget opens at last. Conclusion: you still have to fiddle in the Scilab hell in order to have the Tcl commands get executed. Francois From enrico.segre at weizmann.ac.il Tue Feb 12 19:18:51 2008 From: enrico.segre at weizmann.ac.il (Enrico Segre) Date: Tue, 12 Feb 2008 20:18:51 +0200 Subject: [Scilab-Dev] TCL : Milestone and further investigations. Message-ID: <47B1FF2B02000044000228A7@wisegate.weizmann.ac.il> So finally I painfully built scilab on one system (real PIA, indeed, and without jogl, possibly). I could observe: -open scipad, file/open source of/any function -> nothing before a CR is typed in the shell window -debug(-1), any scipad command -> vavavuma gringo *** glibc detected *** /usr/local/scilab/.libs/lt-scilab-bin: free(): invalid pointer: 0x0063e793 *** ======= Backtrace: ========= /lib/libc.so.6[0x3706ac1] /lib/libc.so.6(cfree+0x90)[0x370a0f0] /usr/local/scilab/modules/tclsci/.libs/libscitclsci.so.0(TCL_EvalScilabCmd+0x658)[0x638d48] /usr/lib/libtcl8.4.so(TclInvokeStringCommand+0x6e)[0x486575e] /usr/lib/libtcl8.4.so(TclEvalObjvInternal+0x333)[0x4866f93] /usr/lib/libtcl8.4.so(Tcl_EvalObjv+0x11b)[0x4869ddb] /usr/lib/libtcl8.4.so[0x48a2165] /usr/lib/libtcl8.4.so(TclEvalObjvInternal+0x333)[0x4866f93] /usr/lib/libtcl8.4.so[0x4894075] /usr/lib/libtcl8.4.so(Tcl_ExprObj+0x1ad)[0x48912ed] /usr/lib/libtcl8.4.so(Tcl_ExprBooleanObj+0x33)[0x48667b3] /usr/lib/libtcl8.4.so(Tcl_IfObjCmd+0x112)[0x4874d12] /usr/lib/libtcl8.4.so(TclEvalObjvInternal+0x333)[0x4866f93] /usr/lib/libtcl8.4.so(Tcl_EvalEx+0x437)[0x48693d7] /usr/lib/libtcl8.4.so(Tcl_FSEvalFile+0x21b)[0x48b18bb] /usr/lib/libtcl8.4.so(Tcl_SourceObjCmd+0x56)[0x4877606] /usr/lib/libtcl8.4.so(TclEvalObjvInternal+0x333)[0x4866f93] /usr/lib/libtcl8.4.so[0x4894075] /usr/lib/libtcl8.4.so(TclCompEvalObj+0x9c)[0x4897e2c] /usr/lib/libtcl8.4.so(Tcl_EvalObjEx+0x69)[0x4869f89] /usr/lib/libtcl8.4.so(Tcl_IfObjCmd+0x1b7)[0x4874db7] /usr/lib/libtcl8.4.so(TclEvalObjvInternal+0x333)[0x4866f93] /usr/lib/libtcl8.4.so(Tcl_EvalEx+0x437)[0x48693d7] /usr/lib/libtcl8.4.so(Tcl_FSEvalFile+0x21b)[0x48b18bb] /usr/lib/libtcl8.4.so(Tcl_SourceObjCmd+0x56)[0x4877606] /usr/lib/libtcl8.4.so(TclEvalObjvInternal+0x333)[0x4866f93] /usr/lib/libtcl8.4.so(Tcl_EvalEx+0x437)[0x48693d7] /usr/lib/libtcl8.4.so(Tcl_Eval+0x3c)[0x48696dc] /usr/local/scilab/modules/tclsci/.libs/libscitclsci.so.0(startTclLoop+0x123)[0x63a7b3] /usr/local/scilab/modules/tclsci/.libs/libscitclsci.so.0(DaemonOpenTCLsci+0x1e2)[0x638472] /lib/libpthread.so.0[0x1e3450b] /lib/libc.so.6(clone+0x5e)[0x3770b2e] ======= Memory map: ======== 00110000-00111000 r-xp 00110000 00:00 0 [vdso] 00111000-00113000 r-xp 00000000 08:12 1393091 /usr/local/scilab/modules/.libs/libscilab.so.0.0.0 00113000-00114000 rwxp 00001000 08:12 1393091 /usr/local/scilab/modules/.libs/libscilab.so.0.0.0 00114000-0011d000 r-xp 00000000 08:12 1377852 /usr/local/scilab/modules/mexlib/.libs/libmex.so.0.0.0 0011d000-0011e000 rwxp 00009000 08:12 1377852 /usr/local/scilab/modules/mexlib/.libs/libmex.so.0.0.0 0011e000-0011f000 rwxp 0011e000 00:00 0 0011f000-00126000 r-xp 00000000 08:12 1360563 /usr/local/scilab/modules/boolean/.libs/libsciboolean.so.0.0.0 00126000-00127000 rwxp 00006000 08:12 1360563 /usr/local/scilab/modules/boolean/.libs/libsciboolean.so.0.0.0 00127000-001e1000 rwxp 00127000 00:00 0 001e1000-00210000 r-xp 00000000 08:12 1331715 /usr/local/scilab/modules/arnoldi/.libs/libsciarnoldi.so.0.0.0 00210000-00211000 rwxp 0002f000 08:12 1331715 /usr/local/scilab/modules/arnoldi/.libs/libsciarnoldi.so.0.0.0 00211000-0021e000 r-xp 00000000 08:12 1377704 /usr/local/scilab/modules/double/.libs/libscidouble.so.0.0.0 0021e000-0021f000 rwxp 0000c000 08:12 1377704 /usr/local/scilab/modules/double/.libs/libscidouble.so.0.0.0 0021f000-002d9000 rwxp 0021f000 00:00 0 002d9000-0034c000 r-xp 00000000 08:12 854537 /usr/local/scilab/modules/graphics/.libs/libscigraphics.so.0.0.0 0034c000-0034f000 rwxp 00073000 08:12 854537 /usr/local/scilab/modules/graphics/.libs/libscigraphics.so.0.0.0 0034f000-00354000 rwxp 0034f000 00:00 0 00354000-00360000 r-xp 00000000 08:12 1377804 /usr/local/scilab/modules/data_structures/.libs/libscidata_structures.so.0.0.0 00360000-00361000 rwxp 0000b000 08:12 1377804 /usr/local/scilab/modules/data_structures/.libs/libscidata_structures.so.0.0.0 00361000-0041b000 rwxp 00361000 00:00 0 0041b000-00442000 r-xp 00000000 08:12 753801 /usr/local/scilab/modules/graphic_export/.libs/libscigraphic_export.so.0.0.0 00442000-00443000 rwxp 00027000 08:12 753801 /usr/local/scilab/modules/graphic_export/.libs/libscigraphic_export.so.0.0.0 00443000-005c6000 r-xp 00000000 08:12 1343759 /usr/local/scilab/modules/renderer/.libs/libscirenderer.so.0.0.0 005c6000-005d5000 rwxp 00182000 08:12 1343759 /usr/local/scilab/modules/renderer/.libs/libscirenderer.so.0.0.0 005d5000-005d6000 rwxp 005d5000 00:00 0 005d6000-00607000 r-xp 00000000 08:12 1392778 /usr/local/scilab/modules/gui/.libs/libscigui.so.0.0.0 00607000-00608000 rwxp 00031000 08:12 1392778 /usr/local/scilab/modules/gui/.libs/libscigui.so.0.0.0 00608000-0061a000 r-xp 00000000 08:12 1377414 /usr/local/scilab/modules/interpolation/.libs/libsciinterpolation.so.0.0.0 0061a000-0061b000 rwxp 00012000 08:12 1377414 /usr/local/scilab/modules/interpolation/.libs/libsciinterpolation.so.0.0.0 0061b000-0061e000 r-xp 00000000 08:12 1377450 /usr/local/scilab/modules/localization/.libs/libscilocalization.so.0.0.0 0061e000-00624000 rwxp 00002000 08:12 1377450 /usr/local/scilab/modules/localization/.libs/libscilocalization.so.0.0.0 00624000-0062a000 r-xp 00000000 08:12 1377440 /usr/local/scilab/modules/sound/.libs/libscisound.so.0.0.0 0062a000-0062b000 rwxp 00005000 08:12 1377440 /usr/local/scilab/modules/sound/.libs/libscisound.so.0.0.0 0062b000-0062e000 rwxp 0062b000 00:00 0 0062e000-00631000 r-xp 00000000 08:12 1377479 /usr/local/scilab/modules/time/.libs/libscitime.so.0.0.0 00631000-00632000 rwxp 00003000 08:12 1377479 /usr/local/scilab/modules/time/.libs/libscitime.so.0.0.0 00632000-00633000 r-xp 00000000 08:12 1392999 /usr/local/scilab/modules/windows_tools/.libs/libsciwindows_tools.so.0.0.0 00633000-00634000 rwxp 00000000 08:12 1392999 /usr/local/scilab/modules/windows_tools/.libs/libsciwindows_tools.so.0.0.0 00634000-00640000 r-xp 00000000 08:12 1377882 /usr/local/scilab/modules/tclsci/.libs/libscitclsci.so.0.0.0 00640000-00641000 rwxp 0000b000 08:12 1377882 /usr/local/scilab/modules/tclsci/.libs/libscitclsci.so.0.0.0 00641000-00643000 r-xp 00000000 08:12 1360097 /usr/local/scilab/modules/intersci/.libs/libsciintersci.so.0.0.0 00643000-00644000 rwxp 00001000 08:12 1360097 /usr/local/scilab/modules/intersci/.libs/libsciintersci.so.0.0.0 00644000-00645000 r-xp 00000000 08:12 1393019 /usr/local/scilab/modules/fftw/.libs/libscifftw.so.0.0.0 00645000-00646000 rwxp 00000000 08:12 1393019 /usr/local/scilab/modules/fftw/.libs/libscifftw.so.0.0.0 00646000-00647000 r-xp 00000000 08:12 1393027 /usr/local/scilab/modules/pvm/.libs/libscipvm.so.0.0.0 00647000-00648000 rwxp 00000000 08:12 1393027 /usr/local/scilab/modules/pvm/.libs/libscipvm.so.0.0.0 00648000-0065b000 r-xp 00000000 08:12 1376824 /usr/local/scilab/modules/fileio/.libs/libscifileio.so.0.0.0 0065b000-0065c000 rwxp 00013000 08:12 1376824 /usr/local/scilab/modules/fileio/.libs/libscifileio.so.0.0.0 0065c000-0065e000 rwxp 0065c000 00:00 0 0065e000-00665000 r-xp 00000000 08:12 884777 /usr/local/scilab/modules/shell/.libs/libscishell.so.0.0.0 00665000-00666000 rwxp 00007000 08:12 884777 /usr/local/scilab/modules/shell/.libs/libscishell.so.0.0.0 00666000-0066c000 r-xp 00000000 08:12 1343528 /usr/local/scilab/modules/console/.libs/libsciconsole.so.0.0.0 0066c000-0066d000 rwxp 00005000 08:12 1343528 /usr/local/scilab/modules/console/.libs/libsciconsole.so.0.0.0 0066d000-00671000 r-xp 00000000 08:12 1343524 /usr/local/scilab/modules/completion/.libs/libscicompletion.so.0.0.0 00671000-00672000 rwxp 00003000 08:12 1343524 /usr/local/scilab/modules/completion/.libs/libscicompletion.so.0.0.0 00672000-0067f000 r-xp 00000000 08:12 1343526 /usr/local/scilab/modules/history_manager/.libs/libscihistory_manager.so.0.0.0 0067f000-00680000 rwxp 0000c000 08:12 1343526 /usr/local/scilab/modules/history_manager/.libs/libscihistory_manager.so.0.0.0 00680000-0068c000 r-xp 00000000 08:12 1393045 /usr/local/scilab/modules/spreadsheet/.libs/libscispreadsheet.so.0.0.0 0068c000-0068d000 rwxp 0000b000 08:12 1393045 /usr/local/scilab/modules/spreadsheet/.libs/libscispreadsheet.so.0.0.0 0068d000-0068e000 r-xp 00000000 08:12 1343516 /usr/local/scilab/modules/action_binding/.libs/libsciaction_binding.so.0.0.0 0068e000-0068f000 rwxp 00000000 08:12 1343516 /usr/local/scilab/modules/action_binding/.libs/libsciaction_binding.so.0.0.0 0068f000-0069b000 r-xp 00000000 08:12 1376491 /usr/local/scilab/modules/output_stream/.libs/libscioutput_stream.so.0.0.0 0069b000-0069c000 rwxp 0000b000 08:12 1376491 /usr/local/scilab/modules/output_stream/.libs/libscioutput_stream.so.0.0.0 0069c000-0069e000 rwxp 0069c000 00:00 0 0069e000-0069f000 r-xp 00000000 08:12 77351 /usr/lib/libpcreposix.so.0.0.0 0069f000-006a0000 rwxp 00001000 08:12 77351 /usr/lib/libpcreposix.so.0.0.0 006a0000-006a5000 r-xp 00000000 08:12 1393073 /usr/local/scilab/modules/jvm/.libs/libscijvm.so.0.0.0 006a5000-006a6000 rwxp 00004000 08:12 1393073 /usr/local/scilab/modules/jvm/.libs/libscijvm.so.0.0.0 006a6000-006a9000 r-xp 00000000 08:12 213042 /lib/libdl-2.7.so 006a9000-006aa000 r-xp 00002000 08:12 213042 /lib/libdl-2.7.so 006aa000-006ab000 rwxp 00003000 08:12 213042 /lib/libdl-2.7.so 006ab000-006ac000 r-xp 00000000 08:12 1360169 /usr/local/scilab/libs/dynamiclibrary/.libs/libscidynamiclibrary.so.0.0.0 006ac000-006ad000 rwxp 00000000 08:12 1360169 /usr/local/scilab/libs/dynamiclibrary/.libs/libscidynamiclibrary.so.0.0.0 006ad000-006ae000 r-xp 00000000 08:12 1393011 /usr/local/scilab/modules/scicos/.libs/libsciscicos.so.0.0.0 006ae000-006af000 rwxp 00000000 08:12 1393011 /usr/local/scilab/modules/scicos/.libs/libsciscicos.so.0.0.0 006b0000-006cb000 r-xp 00000000 08:12 213023 /lib/ld-2.7.so 006cb000-006cc000 r-xp 0001a000 08:12 213023 /lib/ld-2.7.so 006cc000-006cd000 rwxp 0001b000 08:12 213023 /lib/ld-2.7.so 006cd000-006f7000 r-xp 00000000 08:12 1377588 /usr/local/scilab/modules/integer/.libs/libsciinteger.so.0.0.0 006f7000-006f8000 rwxp 00029000 08:12 1377588 /usr/local/scilab/modules/integer/.libs/libsciinteger.so.0.0.0 006f8000-007b2000 rwxp 006f8000 00:00 0 007b2000-007c7000 r-xp 00000000 08:12 1343496 /usr/local/scilab/modules/io/.libs/libsciio.so.0.0.0 007c7000-007c8000 rwxp 00015000 08:12 1343496 /usr/local/scilab/modules/io/.libs/libsciio.so.0.0.0 007c8000-00882000 rwxp 007c8000 00:00 0 00882000-008c8000 r-xp 00000000 08:12 1377926 /usr/local/scilab/modules/sparse/.libs/libscisparse.so.0.0.0 008c8000-008c9000 rwxp 00045000 08:12 1377926 /usr/local/scilab/modules/sparse/.libs/libscisparse.so.0.0.0 008c9000-00983000 rwxp 008c9000 00:00 0 00983000-009a6000 r-xp 00000000 08:12 1376470 /usr/local/scilab/modules/linear_algebra/.libs/libscilinear_algebra.so.0.0.0 009a6000-009a7000 rwxp 00022000 08:12 1376470 /usr/local/scilab/modules/linear_algebra/.libs/libscilinear_algebra.so.0.0.0 009a7000-00a61000 rwxp 009a7000 00:00 0 00a61000-00aad000 r-xp 00000000 08:12 1377164 /usr/local/scilab/modules/metanet/.libs/libscimetanet.so.0.0.0 00aad000-00aae000 rwxp 0004b000 08:12 1377164 /usr/local/scilab/modules/metanet/.libs/libscimetanet.so.0.0.0 00aae000-00c9a000 rwxp 00aae000 00:00 0 00c9a000-00ce6000 r-xp 00000000 08:12 1377279 /usr/local/scilab/modules/optimization/.libs/libscioptimization.so.0.0.0 00ce6000-00ce7000 rwxp 0004c000 08:12 1377279 /usr/local/scilab/modules/optimization/.libs/libscioptimization.so.0.0.0 00ce7000-00da1000 rwxp 00ce7000 00:00 0 00da1000-00daf000 r-xp 00000000 08:12 1377765 /usr/local/scilab/modules/randlib/.libs/libscirandlib.so.0.0.0 00daf000-00db0000 rwxp 0000d000 08:12 1377765 /usr/local/scilab/modules/randlib/.libs/libscirandlib.so.0.0.0 00db0000-00e6c000 rwxp 00db0000 00:00 0 00e6c000-00e70000 r-xp 00000000 08:12 1377866 /usr/local/scilab/modules/symbolic/.libs/libscisymbolic.so.0.0.0 00e70000-00e71000 rwxp 00003000 08:12 1377866 /usr/local/scilab/modules/symbolic/.libs/libscisymbolic.so.0.0.0 00e71000-00f2b000 rwxp 00e71000 00:00 0 00f2b000-00f34000 r-xp 00000000 08:12 1377731 /usr/local/scilab/modules/special_functions/.libs/libscispecial_functions.so.0.0.0 00f34000-00f35000 rwxp 00008000 08:12 1377731 /usr/local/scilab/modules/special_functions/.libs/libscispecial_functions.so.0.0.0 00f35000-00fef000 rwxp 00f35000 00:00 0 00fef000-01004000 r-xp 00000000 08:12 1377565 /usr/local/scilab/modules/statistics/.libs/libscistatistics.so.0.0.0 01004000-01005000 rwxp 00014000 08:12 1377565 /usr/local/scilab/modules/statistics/.libs/libscistatistics.so.0.0.0 01005000-010bf000 rwxp 01005000 00:00 0 010bf000-010e5000 r-xp 00000000 08:12 1360526 /usr/local/scilab/modules/polynomials/.libs/libscipolynomials.so.0.0.0 010e5000-010e6000 rwxp 00025000 08:12 1360526 /usr/local/scilab/modules/polynomials/.libs/libscipolynomials.so.0.0.0 010e6000-011a1000 rwxp 010e6000 00:00 0 011a1000-01285000 r-xp 00000000 08:12 1362297 /usr/local/scilab/libs/lapack/.libs/libscilapack.so.0.0.0 01285000-01286000 rwxp 000e4000 08:12 1362297 /usr/local/scilab/libs/lapack/.libs/libscilapack.so.0.0.0 01286000-01301000 rwxp 01286000 00:00 0 01301000-0130c000 r-xp 00000000 08:12 213073 /lib/libgcc_s-4.1.2-20070925.so.1 0130c000-0130d000 rwxp 0000a000 08:12 213/usr/local/scilab/bin/scilab: line 381: 5980 Aborted "$SCILABBIN" $* From sylvestre.ledru at inria.fr Mon Feb 18 16:24:22 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Mon, 18 Feb 2008 16:24:22 +0100 Subject: Update of JoGL Message-ID: <1203348262.5557.391.camel@korcula.inria.fr> Hello, Because of a well known bug with ATI graphical cards with OpenGL [1], JoGL version 1.1.1~rc8 is now needed to work. # svn export svn://svn.scilab.org/scilab/trunk/Dev-Tools/SE/Prerequirements/Linux/bin bin # svn export svn://svn.scilab.org/scilab/trunk/Dev-Tools/SE/Prerequirements/Linux/thirdparty thirdparty Sylvestre [1] https://jogl.dev.java.net/issues/show_bug.cgi?id=339 http://www.javagaming.org/forums/index.php?topic=18080.0 From sylvestre.ledru at inria.fr Wed Feb 20 18:10:59 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Wed, 20 Feb 2008 18:10:59 +0100 Subject: Parallel build of Scilab Message-ID: <1203527459.29799.362.camel@korcula.inria.fr> Hi, The option -j of make is now working in Scilab. You can now bootstrap Scilab with the option make -j4 for example. It will launch in the same time 4 compilers. For those who are interested in the trick, you have to use the option: .NOTPARALLEL: macros doc in the Makefile.am where you need "atomic operation". Sylvestre From sylvestre.ledru at inria.fr Wed Feb 20 18:23:43 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Wed, 20 Feb 2008 18:23:43 +0100 Subject: Change of license of Scipad Message-ID: <1203528223.29799.370.camel@korcula.inria.fr> Bonsoir, In collaboration with the two main developers of Scipad, we are happy to annonce that the license of Scipad will be changed to the GPL V2 license. Sylvestre From sridevi.rao at cpii.com Tue Feb 26 01:14:42 2008 From: sridevi.rao at cpii.com (Rao, Sridevi) Date: Mon, 25 Feb 2008 16:14:42 -0800 Subject: Building application for Windows as well as Linux Message-ID: <55AA0C1DA2CCD648947DFF5FFCBB695A2EEBFF@shark.cpii.com> Hi I am new to scilab. I found this while I was searching for open source equivalent to Lab View. Scilab provides separate installation packages for Linux and windows. My intention is to develop application on either Windows or Linux and make executables for both Linux and Windows (executable). If I develop my application on Windows can I make executable for Linux too ? I want to write code once and compile for both platforms. This way I do not have to maintain same code on separate OSes. Thanks for help Sridevi Rao -------------- next part -------------- An HTML attachment was scrubbed... URL: From sylvestre.ledru at inria.fr Thu Feb 28 11:07:04 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Thu, 28 Feb 2008 11:07:04 +0100 Subject: Dependency graphs of Scilab modules Message-ID: <1204193224.19982.344.camel@korcula.inria.fr> Hi Here is a graph showing the dependencies of Scilab libs/modules on the current trunk version of Scilab. As attachement, the source of the graph (dot format). In the source of this file, you will find which symbol(s) the libs depends on. I removed some dependencies which are not very usefull for this graph: libsciarnoldi libext1f /* dyn link */ librosenc /* dyn link */ libmytest /* dyn link */ libgluegen-rt /* jogl */ libscioutput_stream libscicore libscimalloc libsciblas libscilapack To regenerate the graph: dot -Tjpg scilab_module_dependency_28_feb_2008_10-40.dot > scilab_module_dependency_28_feb_2008_10-40.jpg This stuff is provided by the graphviz package under Debian (and consequently Ubuntu). Sylvestre -------------- next part -------------- digraph world { node [color=lightblue2, style=filled]; libjavasci -> { libscigraphics ; # sciHasFigures from name lib : libscigraphics }; libscidifferential_equations -> { libscidynamic_link ; # AddFunctionInTable from name lib : libscidynamic_link libsciincremental_link ; # AddFunctionInTable from name lib : libsciincremental_link libscistring ; # cvstr_ from name lib : libscistring # cvstr_ from name lib : libscistring libscielementary_functions ; # dgefa_ from name lib : libscielementary_functions # dgesl_ from name lib : libscielementary_functions # dmmul_ from name lib : libscielementary_functions # dset_ from name lib : libscielementary_functions # entier_ from name lib : libscielementary_functions # icopy_ from name lib : libscielementary_functions # int2db_ from name lib : libscielementary_functions # iset_ from name lib : libscielementary_functions # setjmp_slatec_jmp_env from name lib : libscielementary_functions # unsfdcopy_ from name lib : libscielementary_functions # xermsg_ from name lib : libscielementary_functions }; libscioptimization -> { libscidynamic_link ; # AddFunctionInTable from name lib : libscidynamic_link libsciincremental_link ; # AddFunctionInTable from name lib : libsciincremental_link libscistring ; # cvstr_ from name lib : libscistring # cvstr_ from name lib : libscistring libscielementary_functions ; # d1mach_ from name lib : libscielementary_functions # dadd_ from name lib : libscielementary_functions # ddif_ from name lib : libscielementary_functions # dgefa_ from name lib : libscielementary_functions # dgesl_ from name lib : libscielementary_functions # dmmul_ from name lib : libscielementary_functions # dset_ from name lib : libscielementary_functions # entier_ from name lib : libscielementary_functions # icopy_ from name lib : libscielementary_functions # iset_ from name lib : libscielementary_functions # unsfdcopy_ from name lib : libscielementary_functions # vfinite_ from name lib : libscielementary_functions }; libscilinear_algebra -> { libscidynamic_link ; # AddFunctionInTable from name lib : libscidynamic_link libsciincremental_link ; # AddFunctionInTable from name lib : libsciincremental_link libscielementary_functions ; # bdiag_ from name lib : libscielementary_functions # dset_ from name lib : libscielementary_functions # iset_ from name lib : libscielementary_functions # unsfdcopy_ from name lib : libscielementary_functions # vfinite_ from name lib : libscielementary_functions # wbdiag_ from name lib : libscielementary_functions }; libsciinterpolation -> { libscistring ; # convertAsciiCodeToScilabCode from name lib : libscistring # convertAsciiCodeToScilabCode from name lib : libscistring libscielementary_functions ; # dset_ from name lib : libscielementary_functions }; libscilocalization -> { libsciio ; # setenvc from name lib : libsciio }; libscisound -> { libscilibst ; # rfloat from name lib : libscilibst # rllong from name lib : libscilibst # rlshort from name lib : libscilibst # rshort from name lib : libscilibst # st_Alaw_to_linear from name lib : libscilibst # st_linear_to_Alaw from name lib : libscilibst # st_linear_to_ulaw from name lib : libscilibst # st_ulaw_to_linear from name lib : libscilibst # wfloat from name lib : libscilibst # wllong from name lib : libscilibst # wlshort from name lib : libscilibst # wshort from name lib : libscilibst }; libscistatistics -> { }; libscijvm -> { libscifileio ; # FileExist from name lib : libscifileio # isdir from name lib : libscifileio libscidynamiclibrary ; # FreeDynLibrary from name lib : libscidynamiclibrary # GetDynLibFuncPtr from name lib : libscidynamiclibrary }; libscimetanet -> { libsciintersci ; # cchar_ from name lib : libsciintersci # cdoublef_ from name lib : libsciintersci # cintf_ from name lib : libsciintersci # out_ from name lib : libsciintersci libscielementary_functions ; # entier_ from name lib : libscielementary_functions # int2db_ from name lib : libscielementary_functions # simple_ from name lib : libscielementary_functions libscihashtable ; # create_hashtable from name lib : libscihashtable # hashtable_destroy from name lib : libscihashtable # hashtable_insert from name lib : libscihashtable # hashtable_search from name lib : libscihashtable }; libscipvm -> { }; libscitime -> { }; libscipvm -> { libscisparse ; # mycmatptr_ from name lib : libscisparse }; libsciincremental_link -> { libscistring ; # ScilabMStr2CM from name lib : libscistring # ScilabMStr2CM from name lib : libscistring # cvstr_ from name lib : libscistring # cvstr_ from name lib : libscistring libscielementary_functions ; # icopy_ from name lib : libscielementary_functions # iset_ from name lib : libscielementary_functions # unsfdcopy_ from name lib : libscielementary_functions }; libmat -> { libscistring ; # cvstr_ from name lib : libscistring # cvstr_ from name lib : libscistring libscidata_structures ; # stcreate_ from name lib : libscidata_structures libscielementary_functions ; # dset_ from name lib : libscielementary_functions }; libmex -> { libscistring ; # cvstr_ from name lib : libscistring # cvstr_ from name lib : libscistring libscidata_structures ; # stcreate_ from name lib : libscidata_structures libscielementary_functions ; # dset_ from name lib : libscielementary_functions }; libmx -> { libscistring ; # cvstr_ from name lib : libscistring # cvstr_ from name lib : libscistring libscidata_structures ; # stcreate_ from name lib : libscidata_structures libscielementary_functions ; # dset_ from name lib : libscielementary_functions }; libscispecial_functions -> { libscistatistics ; # betaln_ from name lib : libscistatistics libscielementary_functions ; # calerf_ from name lib : libscielementary_functions # dbesiv_ from name lib : libscielementary_functions # dbesjv_ from name lib : libscielementary_functions # dbeskv_ from name lib : libscielementary_functions # dbesyv_ from name lib : libscielementary_functions # dgammacody_ from name lib : libscielementary_functions # dlgama_ from name lib : libscielementary_functions # dset_ from name lib : libscielementary_functions # dxlegf_ from name lib : libscielementary_functions # infinity_ from name lib : libscielementary_functions # psi_ from name lib : libscielementary_functions # ribesl_ from name lib : libscielementary_functions # rjbesl_ from name lib : libscielementary_functions # rkbesl_ from name lib : libscielementary_functions # rybesl_ from name lib : libscielementary_functions # setjmp_slatec_jmp_env from name lib : libscielementary_functions # unsfdcopy_ from name lib : libscielementary_functions # zbeshv_ from name lib : libscielementary_functions # zbesiv_ from name lib : libscielementary_functions # zbesjv_ from name lib : libscielementary_functions # zbeskv_ from name lib : libscielementary_functions # zbesyv_ from name lib : libscielementary_functions }; libscisignal_processing -> { libscidynamic_link ; # AddFunctionInTable from name lib : libscidynamic_link libsciincremental_link ; # AddFunctionInTable from name lib : libsciincremental_link libscielementary_functions ; # arcosh_ from name lib : libscielementary_functions # arsinh_ from name lib : libscielementary_functions # coshin_ from name lib : libscielementary_functions # dset_ from name lib : libscielementary_functions # entier_ from name lib : libscielementary_functions # iset_ from name lib : libscielementary_functions # simple_ from name lib : libscielementary_functions # unsfdcopy_ from name lib : libscielementary_functions }; libscidouble -> { libscipolynomials ; # polops_ from name lib : libscipolynomials libscilinear_algebra ; # intbackslash_ from name lib : libscilinear_algebra # intinv_ from name lib : libscilinear_algebra # intslash_ from name lib : libscilinear_algebra libscielementary_functions ; # dadd_ from name lib : libscielementary_functions # ddif_ from name lib : libscielementary_functions # ddpow1_ from name lib : libscielementary_functions # ddrdiv_ from name lib : libscielementary_functions # dmcopy_ from name lib : libscielementary_functions # dset_ from name lib : libscielementary_functions # dvmul_ from name lib : libscielementary_functions # dwpow1_ from name lib : libscielementary_functions # dwrdiv_ from name lib : libscielementary_functions # icopy_ from name lib : libscielementary_functions # idcmp_ from name lib : libscielementary_functions # mtran_ from name lib : libscielementary_functions # unsfdcopy_ from name lib : libscielementary_functions # wdpow1_ from name lib : libscielementary_functions # wdrdiv_ from name lib : libscielementary_functions # wmmul_ from name lib : libscielementary_functions # wscal_ from name lib : libscielementary_functions # wvmul_ from name lib : libscielementary_functions # wwpow1_ from name lib : libscielementary_functions # wwrdiv_ from name lib : libscielementary_functions libsciboolean ; # matlog_ from name lib : libsciboolean }; libscirandlib -> { libscielementary_functions ; # logp1_ from name lib : libscielementary_functions }; libscidata_structures -> { libscipolynomials ; # ddmpev_ from name lib : libscipolynomials libscistring ; # cvstr_ from name lib : libscistring # cvstr_ from name lib : libscistring libscielementary_functions ; # icopy_ from name lib : libscielementary_functions # iset_ from name lib : libscielementary_functions # unsfdcopy_ from name lib : libscielementary_functions libsciinteger ; # tpconv_ from name lib : libsciinteger }; libsciboolean -> { libscielementary_functions ; # dset_ from name lib : libscielementary_functions # dsort_ from name lib : libscielementary_functions # icopy_ from name lib : libscielementary_functions # imcopy_ from name lib : libscielementary_functions # iset_ from name lib : libscielementary_functions # unsfdcopy_ from name lib : libscielementary_functions }; libscisymbolic -> { libscielementary_functions ; # icopy_ from name lib : libscielementary_functions }; libscifileio -> { libscishell ; # zzledt_ from name lib : libscishell libscistring ; # cvstr_ from name lib : libscistring # cvstr_ from name lib : libscistring libscilibst ; # swapd from name lib : libscilibst # swapf from name lib : libscilibst # swapi from name lib : libscilibst # swapl from name lib : libscilibst # swapw from name lib : libscilibst }; libscisundials -> { }; libsciscicos -> { libmx ; # listentry from name lib : libmx libmat ; # listentry from name lib : libmat libsciintersci ; # FreeRhsSVar from name lib : libsciintersci libscigraphics ; # ConstructCompoundSeq from name lib : libscigraphics # Objstring from name lib : libscigraphics # SciWin from name lib : libscigraphics # sciGetCurrentObj from name lib : libscigraphics # sciGetParentSubwin from name lib : libscigraphics # sciGetPointerFromHandle from name lib : libscigraphics # sciSetCurrentObj from name lib : libscigraphics # sciSetFontSize from name lib : libscigraphics libscielementary_functions ; # dset_ from name lib : libscielementary_functions # entier_ from name lib : libscielementary_functions # int2db_ from name lib : libscielementary_functions # iset_ from name lib : libscielementary_functions # isort_ from name lib : libscielementary_functions # scidcopy_ from name lib : libscielementary_functions # unsfdcopy_ from name lib : libscielementary_functions libscidynamic_link ; # GetDynFunc from name lib : libscidynamic_link # iislink_ from name lib : libscidynamic_link libscisundials ; # CVDense from name lib : libscisundials # CVode from name lib : libscisundials # CVodeCreate from name lib : libscisundials # CVodeFree from name lib : libscisundials # CVodeGetRootInfo from name lib : libscisundials # CVodeMalloc from name lib : libscisundials # CVodeReInit from name lib : libscisundials # CVodeRootInit from name lib : libscisundials # CVodeSetMaxStep from name lib : libscisundials # CVodeSetStopTime from name lib : libscisundials # IDACalcIC from name lib : libscisundials # IDACreate from name lib : libscisundials # IDADense from name lib : libscisundials # IDADenseSetJacFn from name lib : libscisundials # IDAFree from name lib : libscisundials # IDAGetConsistentIC from name lib : libscisundials # IDAGetCurrentOrder from name lib : libscisundials # IDAGetCurrentStep from name lib : libscisundials # IDAGetErrWeights from name lib : libscisundials # IDAGetRootInfo from name lib : libscisundials # IDAMalloc from name lib : libscisundials # IDAReInit from name lib : libscisundials # IDARootInit from name lib : libscisundials # IDASetId from name lib : libscisundials # IDASetMaxNumItersIC from name lib : libscisundials # IDASetMaxNumJacsIC from name lib : libscisundials # IDASetMaxStep from name lib : libscisundials # IDASetRdata from name lib : libscisundials # IDASetStopTime from name lib : libscisundials # IDASolve from name lib : libscisundials # N_VConst from name lib : libscisundials # N_VDestroy_Serial from name lib : libscisundials # N_VGetArrayPointer from name lib : libscisundials # N_VNewEmpty_Serial from name lib : libscisundials # N_VNew_Serial from name lib : libscisundials # RAbs from name lib : libscisundials # RSqrt from name lib : libscisundials libsciscicos_blocks ; # absolute_value from name lib : libsciscicos_blocks # acos_blk from name lib : libsciscicos_blocks # acosh_blk from name lib : libsciscicos_blocks # affich2_ from name lib : libsciscicos_blocks # affich_ from name lib : libsciscicos_blocks # asin_blk from name lib : libsciscicos_blocks # asinh_blk from name lib : libsciscicos_blocks # atan_blk from name lib : libsciscicos_blocks # atanh_blk from name lib : libsciscicos_blocks # automat from name lib : libsciscicos_blocks # backlash from name lib : libsciscicos_blocks # bit_clear_16 from name lib : libsciscicos_blocks # bit_clear_32 from name lib : libsciscicos_blocks # bit_clear_8 from name lib : libsciscicos_blocks # bit_set_16 from name lib : libsciscicos_blocks # bit_set_32 from name lib : libsciscicos_blocks # bit_set_8 from name lib : libsciscicos_blocks # bounce_ball from name lib : libsciscicos_blocks # bouncexy from name lib : libsciscicos_blocks # canimxy from name lib : libsciscicos_blocks # canimxy3d from name lib : libsciscicos_blocks # cdummy from name lib : libsciscicos_blocks # cevscpe from name lib : libsciscicos_blocks # cfscope from name lib : libsciscicos_blocks # cmat3d from name lib : libsciscicos_blocks # cmatview from name lib : libsciscicos_blocks # cmscope from name lib : libsciscicos_blocks # constraint_ from name lib : libsciscicos_blocks # convert from name lib : libsciscicos_blocks # cos_blk from name lib : libsciscicos_blocks # cosh_blk from name lib : libsciscicos_blocks # counter from name lib : libsciscicos_blocks # cscope from name lib : libsciscicos_blocks # cscopxy from name lib : libsciscicos_blocks # cscopxy3d from name lib : libsciscicos_blocks # csslti4 from name lib : libsciscicos_blocks # csslti_ from name lib : libsciscicos_blocks # cstblk4 from name lib : libsciscicos_blocks # cstblk4_m from name lib : libsciscicos_blocks # cstblk_ from name lib : libsciscicos_blocks # cumsum_c from name lib : libsciscicos_blocks # cumsum_m from name lib : libsciscicos_blocks # cumsum_r from name lib : libsciscicos_blocks # cumsumz_c from name lib : libsciscicos_blocks # cumsumz_m from name lib : libsciscicos_blocks # cumsumz_r from name lib : libsciscicos_blocks # curve_c from name lib : libsciscicos_blocks # deadband from name lib : libsciscicos_blocks # delay4 from name lib : libsciscicos_blocks # delay4_i16 from name lib : libsciscicos_blocks # delay4_i32 from name lib : libsciscicos_blocks # delay4_i8 from name lib : libsciscicos_blocks # delay4_ui16 from name lib : libsciscicos_blocks # delay4_ui32 from name lib : libsciscicos_blocks # delay4_ui8 from name lib : libsciscicos_blocks # delay_ from name lib : libsciscicos_blocks # delayv_ from name lib : libsciscicos_blocks # demux_ from name lib : libsciscicos_blocks # deriv from name lib : libsciscicos_blocks # diffblk_ from name lib : libsciscicos_blocks # dlradp_ from name lib : libsciscicos_blocks # dmmul from name lib : libsciscicos_blocks # dmmul1 from name lib : libsciscicos_blocks # dollar4 from name lib : libsciscicos_blocks # dollar4_m from name lib : libsciscicos_blocks # dollar_ from name lib : libsciscicos_blocks # dsslti4 from name lib : libsciscicos_blocks # dsslti_ from name lib : libsciscicos_blocks # edgetrig from name lib : libsciscicos_blocks # eselect_ from name lib : libsciscicos_blocks # evaluate_expr from name lib : libsciscicos_blocks # evtdly4 from name lib : libsciscicos_blocks # evtdly_ from name lib : libsciscicos_blocks # evtvardly from name lib : libsciscicos_blocks # expblk_ from name lib : libsciscicos_blocks # expblk_m from name lib : libsciscicos_blocks # extdiag from name lib : libsciscicos_blocks # extdiagz from name lib : libsciscicos_blocks # extract from name lib : libsciscicos_blocks # extract_bit_16_LH from name lib : libsciscicos_blocks # extract_bit_16_LSB from name lib : libsciscicos_blocks # extract_bit_16_MSB0 from name lib : libsciscicos_blocks # extract_bit_16_MSB1 from name lib : libsciscicos_blocks # extract_bit_16_RB0 from name lib : libsciscicos_blocks # extract_bit_16_RB1 from name lib : libsciscicos_blocks # extract_bit_16_UH0 from name lib : libsciscicos_blocks # extract_bit_16_UH1 from name lib : libsciscicos_blocks # extract_bit_32_LH from name lib : libsciscicos_blocks # extract_bit_32_LSB from name lib : libsciscicos_blocks # extract_bit_32_MSB0 from name lib : libsciscicos_blocks # extract_bit_32_MSB1 from name lib : libsciscicos_blocks # extract_bit_32_RB0 from name lib : libsciscicos_blocks # extract_bit_32_RB1 from name lib : libsciscicos_blocks # extract_bit_32_UH0 from name lib : libsciscicos_blocks # extract_bit_32_UH1 from name lib : libsciscicos_blocks # extract_bit_8_LH from name lib : libsciscicos_blocks # extract_bit_8_LSB from name lib : libsciscicos_blocks # extract_bit_8_MSB0 from name lib : libsciscicos_blocks # extract_bit_8_MSB1 from name lib : libsciscicos_blocks # extract_bit_8_RB0 from name lib : libsciscicos_blocks # extract_bit_8_RB1 from name lib : libsciscicos_blocks # extract_bit_8_UH0 from name lib : libsciscicos_blocks # extract_bit_8_UH1 from name lib : libsciscicos_blocks # extract_bit_u16_MSB1 from name lib : libsciscicos_blocks # extract_bit_u16_RB1 from name lib : libsciscicos_blocks # extract_bit_u16_UH1 from name lib : libsciscicos_blocks # extract_bit_u32_MSB1 from name lib : libsciscicos_blocks # extract_bit_u32_RB1 from name lib : libsciscicos_blocks # extract_bit_u32_UH1 from name lib : libsciscicos_blocks # extract_bit_u8_MSB1 from name lib : libsciscicos_blocks # extract_bit_u8_RB1 from name lib : libsciscicos_blocks # extract_bit_u8_UH1 from name lib : libsciscicos_blocks # extractor from name lib : libsciscicos_blocks # extractz from name lib : libsciscicos_blocks # exttril from name lib : libsciscicos_blocks # exttrilz from name lib : libsciscicos_blocks # exttriu from name lib : libsciscicos_blocks # exttriuz from name lib : libsciscicos_blocks # forblk_ from name lib : libsciscicos_blocks # fromws_c from name lib : libsciscicos_blocks # fsv_ from name lib : libsciscicos_blocks # gainblk from name lib : libsciscicos_blocks # gainblk_i16e from name lib : libsciscicos_blocks # gainblk_i16n from name lib : libsciscicos_blocks # gainblk_i16s from name lib : libsciscicos_blocks # gainblk_i32e from name lib : libsciscicos_blocks # gainblk_i32n from name lib : libsciscicos_blocks # gainblk_i32s from name lib : libsciscicos_blocks # gainblk_i8e from name lib : libsciscicos_blocks # gainblk_i8n from name lib : libsciscicos_blocks # gainblk_i8s from name lib : libsciscicos_blocks # gainblk_ui16e from name lib : libsciscicos_blocks # gainblk_ui16n from name lib : libsciscicos_blocks # gainblk_ui16s from name lib : libsciscicos_blocks # gainblk_ui32e from name lib : libsciscicos_blocks # gainblk_ui32n from name lib : libsciscicos_blocks # gainblk_ui32s from name lib : libsciscicos_blocks # gainblk_ui8e from name lib : libsciscicos_blocks # gainblk_ui8n from name lib : libsciscicos_blocks # gainblk_ui8s from name lib : libsciscicos_blocks # gensin_ from name lib : libsciscicos_blocks # gensqr_ from name lib : libsciscicos_blocks # getgeom_ from name lib : libsciscicos_blocks # hltblk_ from name lib : libsciscicos_blocks # hystheresis from name lib : libsciscicos_blocks # ifthel_ from name lib : libsciscicos_blocks # integr_ from name lib : libsciscicos_blocks # integral_func from name lib : libsciscicos_blocks # integralz_func from name lib : libsciscicos_blocks # intplt_ from name lib : libsciscicos_blocks # intpol_ from name lib : libsciscicos_blocks # intrp2_ from name lib : libsciscicos_blocks # intrpl_ from name lib : libsciscicos_blocks # invblk4 from name lib : libsciscicos_blocks # invblk_ from name lib : libsciscicos_blocks # iocopy_ from name lib : libsciscicos_blocks # logblk_ from name lib : libsciscicos_blocks # logic from name lib : libsciscicos_blocks # logicalop from name lib : libsciscicos_blocks # logicalop_i16 from name lib : libsciscicos_blocks # logicalop_i32 from name lib : libsciscicos_blocks # logicalop_i8 from name lib : libsciscicos_blocks # logicalop_m from name lib : libsciscicos_blocks # logicalop_ui16 from name lib : libsciscicos_blocks # logicalop_ui32 from name lib : libsciscicos_blocks # logicalop_ui8 from name lib : libsciscicos_blocks # lookup_ from name lib : libsciscicos_blocks # lsplit_ from name lib : libsciscicos_blocks # lusat_ from name lib : libsciscicos_blocks # m_frequ from name lib : libsciscicos_blocks # mat_bksl from name lib : libsciscicos_blocks # mat_cath from name lib : libsciscicos_blocks # mat_catv from name lib : libsciscicos_blocks # mat_det from name lib : libsciscicos_blocks # mat_diag from name lib : libsciscicos_blocks # mat_div from name lib : libsciscicos_blocks # mat_expm from name lib : libsciscicos_blocks # mat_inv from name lib : libsciscicos_blocks # mat_lu from name lib : libsciscicos_blocks # mat_pinv from name lib : libsciscicos_blocks # mat_reshape from name lib : libsciscicos_blocks # mat_sing from name lib : libsciscicos_blocks # mat_sqrt from name lib : libsciscicos_blocks # mat_sum from name lib : libsciscicos_blocks # mat_sumc from name lib : libsciscicos_blocks # mat_suml from name lib : libsciscicos_blocks # mat_svd from name lib : libsciscicos_blocks # mat_vps from name lib : libsciscicos_blocks # mat_vpv from name lib : libsciscicos_blocks # mathermit_m from name lib : libsciscicos_blocks # matmul2_m from name lib : libsciscicos_blocks # matmul_i16e from name lib : libsciscicos_blocks # matmul_i16n from name lib : libsciscicos_blocks # matmul_i16s from name lib : libsciscicos_blocks # matmul_i32e from name lib : libsciscicos_blocks # matmul_i32n from name lib : libsciscicos_blocks # matmul_i32s from name lib : libsciscicos_blocks # matmul_i8e from name lib : libsciscicos_blocks # matmul_i8n from name lib : libsciscicos_blocks # matmul_i8s from name lib : libsciscicos_blocks # matmul_m from name lib : libsciscicos_blocks # matmul_ui16e from name lib : libsciscicos_blocks # matmul_ui16n from name lib : libsciscicos_blocks # matmul_ui16s from name lib : libsciscicos_blocks # matmul_ui32e from name lib : libsciscicos_blocks # matmul_ui32n from name lib : libsciscicos_blocks # matmul_ui32s from name lib : libsciscicos_blocks # matmul_ui8e from name lib : libsciscicos_blocks # matmul_ui8n from name lib : libsciscicos_blocks # matmul_ui8s from name lib : libsciscicos_blocks # mattran_m from name lib : libsciscicos_blocks # matz_abs from name lib : libsciscicos_blocks # matz_absc from name lib : libsciscicos_blocks # matz_bksl from name lib : libsciscicos_blocks # matz_cath from name lib : libsciscicos_blocks # matz_catv from name lib : libsciscicos_blocks # matz_conj from name lib : libsciscicos_blocks # matz_det from name lib : libsciscicos_blocks # matz_diag from name lib : libsciscicos_blocks # matz_div from name lib : libsciscicos_blocks # matz_expm from name lib : libsciscicos_blocks # matz_inv from name lib : libsciscicos_blocks # matz_lu from name lib : libsciscicos_blocks # matz_pinv from name lib : libsciscicos_blocks # matz_reim from name lib : libsciscicos_blocks # matz_reimc from name lib : libsciscicos_blocks # matz_reshape from name lib : libsciscicos_blocks # matz_sing from name lib : libsciscicos_blocks # matz_sqrt from name lib : libsciscicos_blocks # matz_sum from name lib : libsciscicos_blocks # matz_sumc from name lib : libsciscicos_blocks # matz_suml from name lib : libsciscicos_blocks # matz_svd from name lib : libsciscicos_blocks # matz_vps from name lib : libsciscicos_blocks # matz_vpv from name lib : libsciscicos_blocks # matzmul2_m from name lib : libsciscicos_blocks # matzmul_m from name lib : libsciscicos_blocks # matztran_m from name lib : libsciscicos_blocks # maxblk_ from name lib : libsciscicos_blocks # memo_ from name lib : libsciscicos_blocks # mfclck_ from name lib : libsciscicos_blocks # minblk_ from name lib : libsciscicos_blocks # minmax from name lib : libsciscicos_blocks # modulo_count from name lib : libsciscicos_blocks # mswitch from name lib : libsciscicos_blocks # multiplex from name lib : libsciscicos_blocks # mux_ from name lib : libsciscicos_blocks # permutobj from name lib : libsciscicos_blocks # pload_ from name lib : libsciscicos_blocks # plusblk from name lib : libsciscicos_blocks # powblk_ from name lib : libsciscicos_blocks # prod from name lib : libsciscicos_blocks # product from name lib : libsciscicos_blocks # qzcel_ from name lib : libsciscicos_blocks # qzflr_ from name lib : libsciscicos_blocks # qzrnd_ from name lib : libsciscicos_blocks # qztrn_ from name lib : libsciscicos_blocks # ramp from name lib : libsciscicos_blocks # ratelimiter from name lib : libsciscicos_blocks # readau from name lib : libsciscicos_blocks # readc from name lib : libsciscicos_blocks # readf_ from name lib : libsciscicos_blocks # relational_op from name lib : libsciscicos_blocks # relational_op_i16 from name lib : libsciscicos_blocks # relational_op_i32 from name lib : libsciscicos_blocks # relational_op_i8 from name lib : libsciscicos_blocks # relational_op_ui16 from name lib : libsciscicos_blocks # relational_op_ui32 from name lib : libsciscicos_blocks # relational_op_ui8 from name lib : libsciscicos_blocks # relationalop from name lib : libsciscicos_blocks # relay from name lib : libsciscicos_blocks # ricc_m from name lib : libsciscicos_blocks # rndblk_ from name lib : libsciscicos_blocks # rndblk_m from name lib : libsciscicos_blocks # rndblkz_m from name lib : libsciscicos_blocks # root_coef from name lib : libsciscicos_blocks # rootz_coef from name lib : libsciscicos_blocks # samphold4 from name lib : libsciscicos_blocks # samphold4_m from name lib : libsciscicos_blocks # samphold_ from name lib : libsciscicos_blocks # satur from name lib : libsciscicos_blocks # sawtth_ from name lib : libsciscicos_blocks # scalar2vector from name lib : libsciscicos_blocks # sciblk_ from name lib : libsciscicos_blocks # selblk_ from name lib : libsciscicos_blocks # selector from name lib : libsciscicos_blocks # selector_m from name lib : libsciscicos_blocks # shift_16_LA from name lib : libsciscicos_blocks # shift_16_LC from name lib : libsciscicos_blocks # shift_16_RA from name lib : libsciscicos_blocks # shift_16_RC from name lib : libsciscicos_blocks # shift_32_LA from name lib : libsciscicos_blocks # shift_32_LC from name lib : libsciscicos_blocks # shift_32_RA from name lib : libsciscicos_blocks # shift_32_RC from name lib : libsciscicos_blocks # shift_8_LA from name lib : libsciscicos_blocks # shift_8_LC from name lib : libsciscicos_blocks # shift_8_RA from name lib : libsciscicos_blocks # shift_8_RC from name lib : libsciscicos_blocks # shift_u16_RA from name lib : libsciscicos_blocks # shift_u32_RA from name lib : libsciscicos_blocks # shift_u8_RA from name lib : libsciscicos_blocks # signum from name lib : libsciscicos_blocks # sin_blk from name lib : libsciscicos_blocks # sinblk_ from name lib : libsciscicos_blocks # sinh_blk from name lib : libsciscicos_blocks # sqrblk_ from name lib : libsciscicos_blocks # step_func from name lib : libsciscicos_blocks # submat from name lib : libsciscicos_blocks # submatz from name lib : libsciscicos_blocks # sum from name lib : libsciscicos_blocks # sum2_ from name lib : libsciscicos_blocks # sum3_ from name lib : libsciscicos_blocks # summation from name lib : libsciscicos_blocks # summation_i16e from name lib : libsciscicos_blocks # summation_i16n from name lib : libsciscicos_blocks # summation_i16s from name lib : libsciscicos_blocks # summation_i32e from name lib : libsciscicos_blocks # summation_i32n from name lib : libsciscicos_blocks # summation_i32s from name lib : libsciscicos_blocks # summation_i8e from name lib : libsciscicos_blocks # summation_i8n from name lib : libsciscicos_blocks # summation_i8s from name lib : libsciscicos_blocks # summation_ui16e from name lib : libsciscicos_blocks # summation_ui16n from name lib : libsciscicos_blocks # summation_ui16s from name lib : libsciscicos_blocks # summation_ui32e from name lib : libsciscicos_blocks # summation_ui32n from name lib : libsciscicos_blocks # summation_ui32s from name lib : libsciscicos_blocks # summation_ui8e from name lib : libsciscicos_blocks # summation_ui8n from name lib : libsciscicos_blocks # summation_ui8s from name lib : libsciscicos_blocks # summation_z from name lib : libsciscicos_blocks # switch2 from name lib : libsciscicos_blocks # switch2_m from name lib : libsciscicos_blocks # switchn from name lib : libsciscicos_blocks # tan_blk from name lib : libsciscicos_blocks # tanblk_ from name lib : libsciscicos_blocks # tanh_blk from name lib : libsciscicos_blocks # tcslti4 from name lib : libsciscicos_blocks # tcslti_ from name lib : libsciscicos_blocks # tcsltj4 from name lib : libsciscicos_blocks # tcsltj_ from name lib : libsciscicos_blocks # timblk_ from name lib : libsciscicos_blocks # time_delay from name lib : libsciscicos_blocks # tows_c from name lib : libsciscicos_blocks # trash_ from name lib : libsciscicos_blocks # variable_delay from name lib : libsciscicos_blocks # writeau from name lib : libsciscicos_blocks # writec from name lib : libsciscicos_blocks # writef_ from name lib : libsciscicos_blocks # zcross2 from name lib : libsciscicos_blocks # zcross_ from name lib : libsciscicos_blocks libmex ; # listentry from name lib : libmex libsciincremental_link ; # GetDynFunc from name lib : libsciincremental_link # iislink_ from name lib : libsciincremental_link libscistring ; # cvstr_ from name lib : libscistring # cvstr_ from name lib : libscistring libscitime ; # realtime_ from name lib : libscitime # realtimeinit_ from name lib : libscitime }; libscigui -> { libscijvm ; # getScilabJNIEnv from name lib : libscijvm # getScilabJavaVM from name lib : libscijvm # getScilabObject from name lib : libscijvm libscigraphics ; # ConstructUimenu from name lib : libscigraphics # callSetProperty from name lib : libscigraphics # getDoubleFromStack from name lib : libscigraphics # getDoubleMatrixFromStack from name lib : libscigraphics # getFigureFromIndex from name lib : libscigraphics # getHandleFromStack from name lib : libscigraphics # getStringFromStack from name lib : libscigraphics # getStringMatrixFromStack from name lib : libscigraphics # sciAddNewHandle from name lib : libscigraphics # sciAddThisToItsParent from name lib : libscigraphics # sciGetCurrentFigure from name lib : libscigraphics # sciGetEntityType from name lib : libscigraphics # sciGetHandle from name lib : libscigraphics # sciGetHeight from name lib : libscigraphics # sciGetNum from name lib : libscigraphics # sciGetParent from name lib : libscigraphics # sciGetPointerFromHandle from name lib : libscigraphics # sciGetRelationship from name lib : libscigraphics # sciInitSelectedSons from name lib : libscigraphics # sciInitVisibility from name lib : libscigraphics # sciSetEntityType from name lib : libscigraphics # sciStandardBuildOperations from name lib : libscigraphics libscirenderer ; # createDrawingObserver from name lib : libscirenderer }; libsciinteger -> { libscipolynomials ; # blktit_ from name lib : libscipolynomials libscifileio ; # mgetnc_ from name lib : libscifileio libscistring ; # cvstr_ from name lib : libscistring # cvstr_ from name lib : libscistring libscielementary_functions ; # dset_ from name lib : libscielementary_functions # getorient_ from name lib : libscielementary_functions # icopy_ from name lib : libscielementary_functions # int2db_ from name lib : libscielementary_functions # iset_ from name lib : libscielementary_functions # mtlbsel_ from name lib : libscielementary_functions # unsfdcopy_ from name lib : libscielementary_functions libscilibst ; # rblong from name lib : libscilibst # rbshort from name lib : libscilibst # rllong from name lib : libscilibst # rlshort from name lib : libscilibst # swapl from name lib : libscilibst # swapw from name lib : libscilibst # wblong from name lib : libscilibst # wbshort from name lib : libscilibst # wllong from name lib : libscilibst # wlshort from name lib : libscilibst }; libscisparse -> { libscipolynomials ; # fmt_ from name lib : libscipolynomials libsciio ; # v2unit_ from name lib : libsciio libscistring ; # cvstr_ from name lib : libscistring # cvstr_ from name lib : libscistring libscielementary_functions ; # ddpow_ from name lib : libscielementary_functions # dset_ from name lib : libscielementary_functions # dwpow_ from name lib : libscielementary_functions # entier_ from name lib : libscielementary_functions # icopy_ from name lib : libscielementary_functions # int2db_ from name lib : libscielementary_functions # iset_ from name lib : libscielementary_functions # unsfdcopy_ from name lib : libscielementary_functions # wdpow_ from name lib : libscielementary_functions # wscal_ from name lib : libscielementary_functions # wwpow_ from name lib : libscielementary_functions }; libscigraphics -> { libscihashtable ; # create_hashtable from name lib : libscihashtable # hashtable_destroy from name lib : libscihashtable # hashtable_insert from name lib : libscihashtable # hashtable_search from name lib : libscihashtable libsciaction_binding ; # StoreCommand from name lib : libsciaction_binding libscielementary_functions ; # dsort_ from name lib : libscielementary_functions libscirenderer ; # createDrawingObserver from name lib : libscirenderer # createGraphicSynchronizer from name lib : libscirenderer # deleteObservers from name lib : libscirenderer # destroyGraphicSynchronizer from name lib : libscirenderer # destroyHandleDrawer from name lib : libscirenderer # endFigureDataReading from name lib : libscirenderer # endFigureDataWriting from name lib : libscirenderer # endGraphicDataReading from name lib : libscirenderer # endGraphicDataWriting from name lib : libscirenderer # forceHierarchyRedraw from name lib : libscirenderer # forceRedraw from name lib : libscirenderer # notifyObservers from name lib : libscirenderer # sciDrawObj from name lib : libscirenderer # sciDrawSingleObj from name lib : libscirenderer # sciGetJava2dViewCoordFromPixel from name lib : libscirenderer # sciGetJava2dViewCoordinates from name lib : libscirenderer # sciGetJavaColormap from name lib : libscirenderer # sciGetJavaFigureSize from name lib : libscirenderer # sciGetJavaPixelCoordinates from name lib : libscirenderer # sciGetJavaPixmapMode from name lib : libscirenderer # sciGetJavaSegsBoundingBox from name lib : libscirenderer # sciGetJavaViewingArea from name lib : libscirenderer # sciGetJavaWindowPosition from name lib : libscirenderer # sciGetJavaWindowSize from name lib : libscirenderer # sciJavaZoomRect from name lib : libscirenderer # sciSetJavaColormap from name lib : libscirenderer # sciSetJavaFigureSize from name lib : libscirenderer # sciSetJavaInfoMessage from name lib : libscirenderer # sciSetJavaPixmapMode from name lib : libscirenderer # sciSetJavaRenderingEnable from name lib : libscirenderer # sciSetJavaWindowPosition from name lib : libscirenderer # sciSetJavaWindowSize from name lib : libscirenderer # startFigureDataReading from name lib : libscirenderer # startFigureDataWriting from name lib : libscirenderer # startGraphicDataReading from name lib : libscirenderer # startGraphicDataWriting from name lib : libscirenderer libscitclsci ; # sciDestroyGed from name lib : libscitclsci libscigui ; # CallJxclick from name lib : libscigui # CallJxgetmouse from name lib : libscigui # CallJxgetmouseWithOptions from name lib : libscigui # DestroyUIControl from name lib : libscigui # GetUicontrolBackgroundColor from name lib : libscigui # GetUicontrolFontAngle from name lib : libscigui # GetUicontrolFontName from name lib : libscigui # GetUicontrolFontSize from name lib : libscigui # GetUicontrolFontUnits from name lib : libscigui # GetUicontrolFontWeight from name lib : libscigui # GetUicontrolHorizontalAlignment from name lib : libscigui # GetUicontrolListboxTop from name lib : libscigui # GetUicontrolMax from name lib : libscigui # GetUicontrolMin from name lib : libscigui # GetUicontrolPosition from name lib : libscigui # GetUicontrolRelief from name lib : libscigui # GetUicontrolSliderStep from name lib : libscigui # GetUicontrolString from name lib : libscigui # GetUicontrolStyle from name lib : libscigui # GetUicontrolUnits from name lib : libscigui # GetUicontrolValue from name lib : libscigui # GetUicontrolVerticalAlignment from name lib : libscigui # GetUimenuLabel from name lib : libscigui # GetUiobjectCallback from name lib : libscigui # GetUiobjectForegroundColor from name lib : libscigui # GetUiobjectTag from name lib : libscigui # InitUIMenu from name lib : libscigui # SetUicontrolBackgroundColor from name lib : libscigui # SetUicontrolFontAngle from name lib : libscigui # SetUicontrolFontName from name lib : libscigui # SetUicontrolFontSize from name lib : libscigui # SetUicontrolFontUnits from name lib : libscigui # SetUicontrolFontWeight from name lib : libscigui # SetUicontrolHorizontalAlignment from name lib : libscigui # SetUicontrolListboxTop from name lib : libscigui # SetUicontrolMax from name lib : libscigui # SetUicontrolMin from name lib : libscigui # SetUicontrolParent from name lib : libscigui # SetUicontrolPosition from name lib : libscigui # SetUicontrolRelief from name lib : libscigui # SetUicontrolSliderStep from name lib : libscigui # SetUicontrolString from name lib : libscigui # SetUicontrolUnits from name lib : libscigui # SetUicontrolValue from name lib : libscigui # SetUicontrolVerticalAlignment from name lib : libscigui # SetUimenuLabel from name lib : libscigui # SetUiobjectCallback from name lib : libscigui # SetUiobjectForegroundColor from name lib : libscigui # SetUiobjectTag from name lib : libscigui # getJxclickMenuCallback from name lib : libscigui # getJxclickMouseButtonNumber from name lib : libscigui # getJxclickWindowID from name lib : libscigui # getJxclickXCoordinate from name lib : libscigui # getJxclickYCoordinate from name lib : libscigui # getJxgetmouseMouseButtonNumber from name lib : libscigui # getJxgetmouseXCoordinate from name lib : libscigui # getJxgetmouseYCoordinate from name lib : libscigui # setMenuParent from name lib : libscigui libscidoublylinkedlist ; # List_append from name lib : libscidoublylinkedlist # List_find from name lib : libscidoublylinkedlist # List_find_full from name lib : libscidoublylinkedlist # List_free from name lib : libscidoublylinkedlist # List_free_full from name lib : libscidoublylinkedlist # List_free_item from name lib : libscidoublylinkedlist # List_nb_item from name lib : libscidoublylinkedlist # List_pop from name lib : libscidoublylinkedlist }; libsciintersci -> { libscistring ; # ScilabStr2C from name lib : libscistring # ScilabStr2C from name lib : libscistring # cvstr_ from name lib : libscistring # cvstr_ from name lib : libscistring }; libscitclsci -> { libsciaction_binding ; # GetCommand from name lib : libsciaction_binding # SetCommandflag from name lib : libsciaction_binding # StoreCommand from name lib : libsciaction_binding # ismenu from name lib : libsciaction_binding libscifileio ; # FileExist from name lib : libscifileio }; libscifftw -> { libscidynamiclibrary ; # FreeDynLibrary from name lib : libscidynamiclibrary # GetDynLibFuncPtr from name lib : libscidynamiclibrary libscielementary_functions ; # dset_ from name lib : libscielementary_functions }; libscipolynomials -> { libscilinear_algebra ; # inteig_ from name lib : libscilinear_algebra libscicacsd ; # calcsc_ from name lib : libscicacsd # giv_ from name lib : libscicacsd libscielementary_functions ; # dadd_ from name lib : libscielementary_functions # ddif_ from name lib : libscielementary_functions # dset_ from name lib : libscielementary_functions # dtild_ from name lib : libscielementary_functions # icopy_ from name lib : libscielementary_functions # iset_ from name lib : libscielementary_functions # ivimp_ from name lib : libscielementary_functions # sciround_ from name lib : libscielementary_functions # unsfdcopy_ from name lib : libscielementary_functions # wasum_ from name lib : libscielementary_functions # waxpy_ from name lib : libscielementary_functions # wmul_ from name lib : libscielementary_functions # wscal_ from name lib : libscielementary_functions # wwdiv_ from name lib : libscielementary_functions }; libsciio -> { libscitclsci ; # setenvtcl from name lib : libscitclsci libscifileio ; # getfiledesc_ from name lib : libscifileio # getfileinfo_ from name lib : libscifileio # getfiletype_ from name lib : libscifileio # mclose_ from name lib : libscifileio # mgetnc_ from name lib : libscifileio # mopen_ from name lib : libscifileio # mputnc_ from name lib : libscifileio # mseek_ from name lib : libscifileio # mtell_ from name lib : libscifileio # readnextline_ from name lib : libscifileio libscistring ; # cvstr_ from name lib : libscistring # cvstr_ from name lib : libscistring libscielementary_functions ; # entier_ from name lib : libscielementary_functions # icopy_ from name lib : libscielementary_functions # iset_ from name lib : libscielementary_functions # isort_ from name lib : libscielementary_functions # mtran_ from name lib : libscielementary_functions # rat_ from name lib : libscielementary_functions # rea2db_ from name lib : libscielementary_functions # unsfdcopy_ from name lib : libscielementary_functions libsciinteger ; # memused_ from name lib : libsciinteger }; libscielementary_functions -> { libscipolynomials ; # balbak_ from name lib : libscipolynomials # dmpcle_ from name lib : libscipolynomials libscisparse ; # spreshape_ from name lib : libscisparse libscistring ; # cvstr_ from name lib : libscistring # cvstr_ from name lib : libscistring libscicacsd ; # dgeco_ from name lib : libscicacsd # giv_ from name lib : libscicacsd # shrslv_ from name lib : libscicacsd # wgeco_ from name lib : libscicacsd # wgesl_ from name lib : libscicacsd libsciinteger ; # tpconv_ from name lib : libsciinteger }; libscicacsd -> { libmat ; # fortran_mex_gateway from name lib : libmat # mexerrmsgtxt_ from name lib : libmat # mexprintf_ from name lib : libmat # mxcopyptrtoreal8_ from name lib : libmat # mxcopyreal8toptr_ from name lib : libmat # mxcreatefull_ from name lib : libmat # mxgetm_ from name lib : libmat # mxgetn_ from name lib : libmat # mxgetpr_ from name lib : libmat # mxiscomplex_ from name lib : libmat # mxisnumeric_ from name lib : libmat # sci_gateway from name lib : libmat libscipolynomials ; # balbak_ from name lib : libscipolynomials # dmp2pm_ from name lib : libscipolynomials # dpmul1_ from name lib : libscipolynomials # dpodiv_ from name lib : libscipolynomials # horner_ from name lib : libscipolynomials # idegre_ from name lib : libscipolynomials # mpdegr_ from name lib : libscipolynomials # quadsd_ from name lib : libscipolynomials # residu_ from name lib : libscipolynomials # rpoly_ from name lib : libscipolynomials # wpodiv_ from name lib : libscipolynomials libscielementary_functions ; # balanc_ from name lib : libscielementary_functions # dadd_ from name lib : libscielementary_functions # ddif_ from name lib : libscielementary_functions # dgefa_ from name lib : libscielementary_functions # dgesl_ from name lib : libscielementary_functions # dmmul_ from name lib : libscielementary_functions # dset_ from name lib : libscielementary_functions # dtild_ from name lib : libscielementary_functions # entier_ from name lib : libscielementary_functions # exch_ from name lib : libscielementary_functions # hqror2_ from name lib : libscielementary_functions # icopy_ from name lib : libscielementary_functions # int2db_ from name lib : libscielementary_functions # iwamax_ from name lib : libscielementary_functions # orthes_ from name lib : libscielementary_functions # ortran_ from name lib : libscielementary_functions # unsfdcopy_ from name lib : libscielementary_functions # wasum_ from name lib : libscielementary_functions # waxpy_ from name lib : libscielementary_functions # wdiv_ from name lib : libscielementary_functions # wdotci_ from name lib : libscielementary_functions # wdotcr_ from name lib : libscielementary_functions # wmul_ from name lib : libscielementary_functions # wrscal_ from name lib : libscielementary_functions # wscal_ from name lib : libscielementary_functions # wsign_ from name lib : libscielementary_functions libscidifferential_equations ; # lsode_ from name lib : libscidifferential_equations libmex ; # fortran_mex_gateway from name lib : libmex # mexerrmsgtxt_ from name lib : libmex # mexprintf_ from name lib : libmex # mxcopyptrtoreal8_ from name lib : libmex # mxcopyreal8toptr_ from name lib : libmex # mxcreatefull_ from name lib : libmex # mxgetm_ from name lib : libmex # mxgetn_ from name lib : libmex # mxgetpr_ from name lib : libmex # mxiscomplex_ from name lib : libmex # mxisnumeric_ from name lib : libmex # sci_gateway from name lib : libmex libmx ; # fortran_mex_gateway from name lib : libmx # mexerrmsgtxt_ from name lib : libmx # mexprintf_ from name lib : libmx # mxcopyptrtoreal8_ from name lib : libmx # mxcopyreal8toptr_ from name lib : libmx # mxcreatefull_ from name lib : libmx # mxgetm_ from name lib : libmx # mxgetn_ from name lib : libmx # mxgetpr_ from name lib : libmx # mxiscomplex_ from name lib : libmx # mxisnumeric_ from name lib : libmx # sci_gateway from name lib : libmx libscilinear_algebra ; # sb02mv_ from name lib : libscilinear_algebra # sb02mw_ from name lib : libscilinear_algebra # sb02ow_ from name lib : libscilinear_algebra # sb02ox_ from name lib : libscilinear_algebra # voiddummy_ from name lib : libscilinear_algebra }; libsciwintools -> { }; libscilab -> { }; libscimpi -> { }; libscistring -> { libscipolynomials ; # blktit_ from name lib : libscipolynomials # impcnc_ from name lib : libscipolynomials # impext_ from name lib : libscipolynomials # impins_ from name lib : libscipolynomials # imptra_ from name lib : libscipolynomials # mpinsp_ from name lib : libscipolynomials libscielementary_functions ; # icopy_ from name lib : libscielementary_functions # unsfdcopy_ from name lib : libscielementary_functions libsciinteger ; # tpconv_ from name lib : libsciinteger }; libjavasci -> { }; libscishell -> { libsciaction_binding ; # ismenu from name lib : libsciaction_binding libsciconsole ; # ClearConsole from name lib : libsciconsole # ClearConsolePart from name lib : libsciconsole # ConsoleIsWaitingForInput from name lib : libsciconsole # ConsolePrintf from name lib : libsciconsole # ConsoleRead from name lib : libsciconsole # GetCharWithoutOutput from name lib : libsciconsole # PromptToHome from name lib : libsciconsole # SetConsolePrompt from name lib : libsciconsole libscihistory_manager ; # appendLineToScilabHistory from name lib : libscihistory_manager # appendLineToScilabHistory from name lib : libscihistory_manager # getNextLineInScilabHistory from name lib : libscihistory_manager # getNextLineInScilabHistory from name lib : libscihistory_manager # getPreviousLineInScilabHistory from name lib : libscihistory_manager # getPreviousLineInScilabHistory from name lib : libscihistory_manager # setSearchedTokenInScilabHistory from name lib : libscihistory_manager # setSearchedTokenInScilabHistory from name lib : libscihistory_manager libscicompletion ; # completion from name lib : libscicompletion }; libscirenderer -> { libscijvm ; # getScilabJavaVM from name lib : libscijvm libscigraphics ; # ChoixFormatE from name lib : libscigraphics # ComputeC_format from name lib : libscigraphics # ComputeNbSubTics from name lib : libscigraphics # ComputeXIntervals from name lib : libscigraphics # GradLog from name lib : libscigraphics # TheTicks from name lib : libscigraphics # allocatePolyline from name lib : libscigraphics # allocateText from name lib : libscigraphics # copyFormatedArray from name lib : libscigraphics # deallocatePolyline from name lib : libscigraphics # deallocateText from name lib : libscigraphics # destroyGraphicPointer from name lib : libscigraphics # destroyGraphicStringArray from name lib : libscigraphics # doubleArrayCopy from name lib : libscigraphics # getFigureFromIndex from name lib : libscigraphics # getMatNbCol from name lib : libscigraphics # getMatNbRow from name lib : libscigraphics # getStrMatData from name lib : libscigraphics # getStrMatElement from name lib : libscigraphics # intArrayCopy from name lib : libscigraphics # mat4DMult from name lib : libscigraphics # sciGetAlignment from name lib : libscigraphics # sciGetArrowSize from name lib : libscigraphics # sciGetAutoPosition from name lib : libscigraphics # sciGetAutoRotation from name lib : libscigraphics # sciGetAutoSize from name lib : libscigraphics # sciGetAutoTicks from name lib : libscigraphics # sciGetAxesBounds from name lib : libscigraphics # sciGetAxesReverse from name lib : libscigraphics # sciGetAxesVisible from name lib : libscigraphics # sciGetBackground from name lib : libscigraphics # sciGetBoxType from name lib : libscigraphics # sciGetCenterPos from name lib : libscigraphics # sciGetClipping from name lib : libscigraphics # sciGetDataBounds from name lib : libscigraphics # sciGetDisplayedDataBounds from name lib : libscigraphics # sciGetEntityType from name lib : libscigraphics # sciGetFontContext from name lib : libscigraphics # sciGetFontOrientation from name lib : libscigraphics # sciGetFontSize from name lib : libscigraphics # sciGetFontStyle from name lib : libscigraphics # sciGetForeground from name lib : libscigraphics # sciGetGraphicContext from name lib : libscigraphics # sciGetGridStyle from name lib : libscigraphics # sciGetInterpVector from name lib : libscigraphics # sciGetIs3d from name lib : libscigraphics # sciGetIsAutoDrawable from name lib : libscigraphics # sciGetIsBoxed from name lib : libscigraphics # sciGetIsClipping from name lib : libscigraphics # sciGetIsClosed from name lib : libscigraphics # sciGetIsColorInterpolated from name lib : libscigraphics # sciGetIsCubeScaled from name lib : libscigraphics # sciGetIsFilled from name lib : libscigraphics # sciGetIsIsoView from name lib : libscigraphics # sciGetIsLine from name lib : libscigraphics # sciGetIsMark from name lib : libscigraphics # sciGetLastSons from name lib : libscigraphics # sciGetLineStyle from name lib : libscigraphics # sciGetLineWidth from name lib : libscigraphics # sciGetLogFlags from name lib : libscigraphics # sciGetMargins from name lib : libscigraphics # sciGetMarkBackground from name lib : libscigraphics # sciGetMarkForeground from name lib : libscigraphics # sciGetMarkSize from name lib : libscigraphics # sciGetMarkSizeUnit from name lib : libscigraphics # sciGetMarkStyle from name lib : libscigraphics # sciGetNbPoints from name lib : libscigraphics # sciGetNum from name lib : libscigraphics # sciGetNumColors from name lib : libscigraphics # sciGetParent from name lib : libscigraphics # sciGetParentFigure from name lib : libscigraphics # sciGetParentSubwin from name lib : libscigraphics # sciGetPixelBoundingBox from name lib : libscigraphics # sciGetPolylineStyle from name lib : libscigraphics # sciGetRealDataBounds from name lib : libscigraphics # sciGetText from name lib : libscigraphics # sciGetTextPos from name lib : libscigraphics # sciGetTightLimitsOn from name lib : libscigraphics # sciGetUserSize from name lib : libscigraphics # sciGetViewingAngles from name lib : libscigraphics # sciGetViewingArea from name lib : libscigraphics # sciGetVisibility from name lib : libscigraphics # sciGetXorMode from name lib : libscigraphics # sciInitFontForeground from name lib : libscigraphics # sciInitFontSize from name lib : libscigraphics # sciInitForeground from name lib : libscigraphics # sciInitIsClipping from name lib : libscigraphics # sciInitIsLine from name lib : libscigraphics # sciInitIsMark from name lib : libscigraphics # sciInitLineStyle from name lib : libscigraphics # sciInitLineWidth from name lib : libscigraphics # sciInitMarkBackground from name lib : libscigraphics # sciInitMarkForeground from name lib : libscigraphics # sciInitMarkSize from name lib : libscigraphics # sciInitMarkSizeUnit from name lib : libscigraphics # sciSetClipping from name lib : libscigraphics # sciSetFontOrientation from name lib : libscigraphics # sciSetRealDataBounds from name lib : libscigraphics # sciSetTextPos from name lib : libscigraphics # sciSetXorMode from name lib : libscigraphics # sciSetZoomBox from name lib : libscigraphics # setDoubleArraySingleValue from name lib : libscigraphics # setToIdentity from name lib : libscigraphics # vectSubstract2D from name lib : libscigraphics libscidoublylinkedlist ; # List_append from name lib : libscidoublylinkedlist # List_free from name lib : libscidoublylinkedlist # List_free_item from name lib : libscidoublylinkedlist }; libsciconsole -> { libsciaction_binding ; # StoreCommand from name lib : libsciaction_binding libscishell ; # getLinesSize from name lib : libscishell # scilines from name lib : libscishell libscifileio ; # FindFileExtension from name lib : libscifileio # URIFileToFilename from name lib : libscifileio libscijvm ; # getScilabJavaVM from name lib : libscijvm }; libscicompletion -> { libscifileio ; # findfiles from name lib : libscifileio libscigraphics ; # getDictionaryGetProperties from name lib : libscigraphics # getDictionarySetProperties from name lib : libscigraphics }; libscihistory_manager -> { }; libsciwindows_tools -> { }; libscispreadsheet -> { libscifileio ; # mgetnc_ from name lib : libscifileio # mopen_ from name lib : libscifileio # mseek_ from name lib : libscifileio # mtell_ from name lib : libscifileio }; libsciaction_binding -> { }; libscistring -> { libscipolynomials ; # blktit_ from name lib : libscipolynomials # impcnc_ from name lib : libscipolynomials # impext_ from name lib : libscipolynomials # impins_ from name lib : libscipolynomials # imptra_ from name lib : libscipolynomials # mpinsp_ from name lib : libscipolynomials libscielementary_functions ; # icopy_ from name lib : libscielementary_functions # unsfdcopy_ from name lib : libscielementary_functions }; libscihistory_manager -> { }; libscigraphic_export -> { libscijvm ; # getScilabJavaVM from name lib : libscijvm libscigraphics ; # getFigureFromIndex from name lib : libscigraphics # sciGetNum from name lib : libscigraphics }; libscidynamic_link -> { libscistring ; # cvstr_ from name lib : libscistring # cvstr_ from name lib : libscistring libscidynamiclibrary ; # FreeDynLibrary from name lib : libscidynamiclibrary # GetDynLibFuncPtr from name lib : libscidynamiclibrary libscielementary_functions ; # icopy_ from name lib : libscielementary_functions # iset_ from name lib : libscielementary_functions # unsfdcopy_ from name lib : libscielementary_functions }; libsciscicos_blocks -> { libscicacsd ; # riccms_ from name lib : libscicacsd # riccsl_ from name lib : libscicacsd # ricdmf_ from name lib : libscicacsd # ricdsl_ from name lib : libscicacsd libscipolynomials ; # dprxc_ from name lib : libscipolynomials # wprxc_ from name lib : libscipolynomials libscigraphics ; # ConstructArc from name lib : libscigraphics # ConstructGrayplot from name lib : libscigraphics # ConstructPolyline from name lib : libscigraphics # ConstructRectangle from name lib : libscigraphics # ConstructSegs from name lib : libscigraphics # ConstructSubWin from name lib : libscigraphics # ConstructSurface from name lib : libscigraphics # DeleteObjs from name lib : libscigraphics # DestroyPolyline from name lib : libscigraphics # getFigureFromIndex from name lib : libscigraphics # sciDeleteWindow from name lib : libscigraphics # sciGetBackground from name lib : libscigraphics # sciGetCurrentFigure from name lib : libscigraphics # sciGetEntityType from name lib : libscigraphics # sciGetFirstTypedSelectedSon from name lib : libscigraphics # sciGetHandle from name lib : libscigraphics # sciGetPixmapMode from name lib : libscigraphics # sciGetPointerFromHandle from name lib : libscigraphics # sciGetRelationship from name lib : libscigraphics # sciInitFontSize from name lib : libscigraphics # sciInitScreenPosition from name lib : libscigraphics # sciIsExistingFigure from name lib : libscigraphics # sciSetBoxType from name lib : libscigraphics # sciSetColormap from name lib : libscigraphics # sciSetDimension from name lib : libscigraphics # sciSetFontSize from name lib : libscigraphics # sciSetForeground from name lib : libscigraphics # sciSetIsBoxed from name lib : libscigraphics # sciSetIsClipping from name lib : libscigraphics # sciSetIsLine from name lib : libscigraphics # sciSetIsMark from name lib : libscigraphics # sciSetLineStyle from name lib : libscigraphics # sciSetLineWidth from name lib : libscigraphics # sciSetMarkBackground from name lib : libscigraphics # sciSetMarkForeground from name lib : libscigraphics # sciSetMarkSize from name lib : libscigraphics # sciSetMarkSizeUnit from name lib : libscigraphics # sciSetMarkStyle from name lib : libscigraphics # sciSetName from name lib : libscigraphics # sciSetPixmapMode from name lib : libscigraphics # sciSetSelectedSubWin from name lib : libscigraphics # sciSetText from name lib : libscigraphics # sciSetUsedWindow from name lib : libscigraphics libscielementary_functions ; # dexpm1_ from name lib : libscielementary_functions # dmmul1_ from name lib : libscielementary_functions # dmmul_ from name lib : libscielementary_functions # dset_ from name lib : libscielementary_functions # intp_ from name lib : libscielementary_functions # iset_ from name lib : libscielementary_functions # mtran_ from name lib : libscielementary_functions # sciround_ from name lib : libscielementary_functions # unsfdcopy_ from name lib : libscielementary_functions # urand_ from name lib : libscielementary_functions # wexpm1_ from name lib : libscielementary_functions # wmmul_ from name lib : libscielementary_functions # wsqrt_ from name lib : libscielementary_functions libscirenderer ; # forceRedraw from name lib : libscirenderer # sciDrawObj from name lib : libscirenderer # sciDrawSingleObj from name lib : libscirenderer libscifileio ; # mclose_ from name lib : libscifileio # mget2 from name lib : libscifileio # mgetnc_ from name lib : libscifileio # mopen_ from name lib : libscifileio # mput2 from name lib : libscifileio # mputnc_ from name lib : libscifileio libsciscicos ; # do_cold_restart from name lib : libsciscicos # dtosci_ from name lib : libsciscicos # get_block_number from name lib : libsciscicos # get_phase_simulation from name lib : libsciscicos # get_scicos_time from name lib : libsciscicos # getlabel_ from name lib : libsciscicos # getouttb_ from name lib : libsciscicos # itosci_ from name lib : libsciscicos # scicos_free from name lib : libsciscicos # scicos_malloc from name lib : libsciscicos # scitod_ from name lib : libsciscicos # set_block_error from name lib : libsciscicos # set_pointer_xproperty from name lib : libsciscicos libscistring ; # cvstr_ from name lib : libscistring # cvstr_ from name lib : libscistring libscilinear_algebra ; # dgelsy1_ from name lib : libscilinear_algebra # zgelsy1_ from name lib : libscilinear_algebra }; libsciumfpack -> { libscisparse ; # genmmd_ from name lib : libscisparse libmx ; # sci_gateway from name lib : libmx libmex ; # sci_gateway from name lib : libmex libmat ; # sci_gateway from name lib : libmat }; libscihashtable -> { }; libscilibst -> { }; libscidynamiclibrary -> { }; libscidoublylinkedlist -> { }; }; -------------- next part -------------- A non-text attachment was scrubbed... Name: scilab_module_dependency_28_feb_2008_10-40.jpg Type: image/jpeg Size: 456213 bytes Desc: not available URL: From enrico.segre at weizmann.ac.il Thu Feb 28 11:30:58 2008 From: enrico.segre at weizmann.ac.il (Enrico Segre) Date: Thu, 28 Feb 2008 12:30:58 +0200 Subject: Building application for Windows as well as Linux Message-ID: <1204194658.27867.133.camel@segre-pc2.weizmann.ac.il> > I am new to scilab. I found this while I was searching for open source > equivalent to Lab View. Labview is programmed visually. Scicos too, but despite Ramine's sisiphean efforts, the graphic editing of Scicos diagrams is nothing compared with that of Labview (sorry Ramine, I DO appreciate your work, but it's difficult to compete with a dedicated megacorp) Labview is for programming, simulation, display, processing, GUI, hardware interfacing. Scicos is only for simulation and display, so to say. Scilab in the more extended sense is for programming, visualization (ehm) and rapid prototyping of algorithms, inclusive of some minimal gui. LabView interfaces very nicely with a HUGE lot of hardware, Scilab's hardware support is essentially nonexistent (save some very sparse contributions and Scicos-RTAI, via Comedi AFAIU) - and not even serial port... Scilab's GUI building is ridiculous; Labview IS for building complex GUI's (Virtual instrument front panels) Having said that, I develop a lot in both programs, but for different purposes. > Scilab provides separate installation packages for Linux and windows. So most any other package... > My intention is to develop application on either Windows or Linux and > make executables for both Linux and Windows (executable). Scilab does not make standalone executables. FAQ. > If I develop my application on Windows can I make executable for Linux > too ? only some cross-platforms compilers do such things. > I want to write code once and compile for both platforms. This way I do > not have to maintain same code on separate OSes. Scilab code is portable. Scilab does not compile it, but you can run (interpreted) code in batch mode on any platform. hth, Enrico From sylvestre.ledru at inria.fr Thu Feb 28 14:17:05 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Thu, 28 Feb 2008 14:17:05 +0100 Subject: Update of the memory profiling with Valgrind Message-ID: <1204204625.19982.392.camel@korcula.inria.fr> Re, I updated the option -profiling when Scilab is called under Linux with this option. Many warnings coming from thirdparty libraries are now suppressed automatically. The list of suppression is in tools/profiling/valgrind.supp By default, valgrind is providing the suppression syntax on each error. It is something like that: { Memcheck:Addr2 fun:getenv fun:g_get_filename_charsets obj:/usr/lib/libglib-2.0.so.0.1400.6 fun:g_filename_to_utf8 fun:g_dir_open obj:/usr/lib/libgtk-x11-2.0.so.0.1200.7 } And can be added to tools/profiling/valgrind.supp I haven't done every warnings, feel free to update this file. Sylvestre PS: I updated the wiki: http://wiki.scilab.org/Debugging_and_Profiling_Scilab_5?action=diff&rev2=17&rev1=16 From Simone.Mannori at inria.fr Thu Feb 28 14:16:51 2008 From: Simone.Mannori at inria.fr (Simone Mannori) Date: Thu, 28 Feb 2008 14:16:51 +0100 Subject: [Scilab-Dev] Re: Building application for Windows as well as Linux In-Reply-To: <1204194658.27867.133.camel@segre-pc2.weizmann.ac.il> References: <1204194658.27867.133.camel@segre-pc2.weizmann.ac.il> Message-ID: <1204204611.4174.30.camel@buta.inria.fr> Dear Sirs, On Thu, 2008-02-28 at 12:30 +0200, Enrico Segre wrote: > > I am new to scilab. I found this while I was searching for open source > > equivalent to Lab View. > > Labview is programmed visually. Scicos too, but despite Ramine's > sisiphean efforts, the graphic editing of Scicos diagrams is nothing > compared with that of Labview (sorry Ramine, I DO appreciate your work, > but it's difficult to compete with a dedicated megacorp) I like competition: I have a brand new editor for Scicos that leave Scilab command line free all the time. I worked on this code six months with the help of Serge Steer. Actually it was an idea from Serge that, at the beginning, I had classified as "a bit too wild". Fortunately, I was wrong ;) > Labview is for programming, simulation, display, processing, GUI, > hardware interfacing. Scicos is only for simulation and display, so to > say. Scilab in the more extended sense is for programming, visualization > (ehm) and rapid prototyping of algorithms, inclusive of some minimal > gui. > Not exactly. For instance you can use Scicos-HIL to run simulation in real time connection with real hardware. > LabView interfaces very nicely with a HUGE lot of hardware, Scilab's > hardware support is essentially nonexistent (save some very sparse > contributions and Scicos-RTAI, via Comedi AFAIU) - and not even serial > port... > Not exactly: - Scicos-RTAI: the remote control panel of Scicos RTAI offer performances similar to to LabView - Scicos-HIL: see above Please, don't forget Scicos-FLEX: the brand new code generator for small embedded systems (batteries included :) ) http://www.evidence.eu.com/ the latest version, Scilab 4.1.2 compatible with native integer support is available here: http://www.evidence.eu.com/content/view/175/216 > Scilab's GUI building is ridiculous; Labview IS for building complex > GUI's (Virtual instrument front panels) > Next Scilab 5.0 will implement a quite rich UICONTROL API. > Having said that, I develop a lot in both programs, but for different > purposes. > Me too :). I like LabView. The graphics of the control panel is "superbe" :). > > > Scilab provides separate installation packages for Linux and windows. > > So most any other package... > > > > My intention is to develop application on either Windows or Linux and > > make executables for both Linux and Windows (executable). > > Scilab does not make standalone executables. FAQ. ... but you can use Scicos-FLEX or Scicos-RTAI to do that. > > > If I develop my application on Windows can I make executable for Linux > > too ? > only some cross-platforms compilers do such things. > > > I want to write code once and compile for both platforms. This way I do > > not have to maintain same code on separate OSes. If you have any - and I say any - wild idea about Embedded and Real Time applications, there are some people here ready to hear your voice, because the VOICE OF THE CUSTOMER (I means YOU) it is the only things that really matter. "Grazie Molto a" Enrico for the post : you share the name with my son. Enrico (my son) is the mastermind beyond all my LEGO models ;) http://www.scicos.org/scicoshil.html Simone Mannori - Scilab/INRIA Rocquencourt From sylvestre.ledru at inria.fr Thu Feb 28 18:02:25 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Thu, 28 Feb 2008 18:02:25 +0100 Subject: Alpha 1 version of Scilab Message-ID: <1204218145.26548.73.camel@korcula.inria.fr> Hello, We just released the first alpha version of Scilab. We don't plan/want to communicate around this version since our bug lists will keep us busy for a few days/weeks and also because we plan to release a few alpha versions when big bugs are fixed. Misc information about this version: http://www.scilab.org/download/index_download.php?page=5.0-alpha-1 List of changes: http://www.scilab.org/download/index_download.php?page=CHANGES_5.0-alpha-1 The release notes (short bug list... and of course not full): http://www.scilab.org/download/index_download.php?page=RELEASE_NOTES_5.0-alpha-1 Sylvestre From sylvestre.ledru at inria.fr Thu Feb 28 20:10:40 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Thu, 28 Feb 2008 20:10:40 +0100 Subject: [Scilab-Dev] Dependency graphs of Scilab modules In-Reply-To: <1204193224.19982.344.camel@korcula.inria.fr> References: <1204193224.19982.344.camel@korcula.inria.fr> Message-ID: <1204225840.26548.137.camel@korcula.inria.fr> Based on the script which is producing this output, I updated all the Makefile.am with right dependencies. This was needed since many deps changed since the Makefile.am were wrote. Please note that I had to comment some of them because of cyclic dependencies or because the processing order is way too complicated to do. Please note that I may have broken the trunk under Linux. I also removed a borring "bug" (" because some people call it a feature) describe here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=419228 If you have 3 libtool convenient libs: libA => libB => libC libC will embded all the dep that libA has. In Scilab case, this was causing some stupid stuff like: The boolean library had to do a string test, then we linked it to the scilab String library which is using pcre. This was causing lib boolean to link the pcre library. For those who will find this email on Google (or me, in a few months when I will have forgotten how I did it), I am using the Debian patched version of libtool currently the one in unstable (1.5.26-1). I updated the appropriate files doing # libtoolize -c -f And I use the macros: AC_PROG_LIBTOOL AM_PROG_LIBTOOL in the configure.ac And, still in the configure.ac, I added the option: link_all_deplibs=no to make sure that deps are not propagated. And finally, watch you the version you are using, I found a few bugs in it. Sylvestre Le jeudi 28 f?vrier 2008 ? 11:07 +0100, Sylvestre Ledru a ?crit : > Hi > > Here is a graph showing the dependencies of Scilab libs/modules on the > current trunk version of Scilab. > > As attachement, the source of the graph (dot format). In the source of > this file, you will find which symbol(s) the libs depends on. > I removed some dependencies which are not very usefull for this graph: > > libsciarnoldi > libext1f /* dyn link */ > librosenc /* dyn link */ > libmytest /* dyn link */ > libgluegen-rt /* jogl */ > libscioutput_stream > libscicore > libscimalloc > libsciblas > libscilapack > > > To regenerate the graph: > dot -Tjpg scilab_module_dependency_28_feb_2008_10-40.dot > > scilab_module_dependency_28_feb_2008_10-40.jpg > > This stuff is provided by the graphviz package under Debian (and > consequently Ubuntu). > > Sylvestre > From sylvestre.ledru at inria.fr Fri Feb 29 13:10:52 2008 From: sylvestre.ledru at inria.fr (Sylvestre Ledru) Date: Fri, 29 Feb 2008 13:10:52 +0100 Subject: Machin is not a valid libtool object Message-ID: <1204287052.26548.326.camel@korcula.inria.fr> Because of my modifications of yesterday, if you get: libtool: link: `libscigraphic_export_la-gl2ps.lo' is not a valid libtool object Go into the module and a dirty "make clean all" should fix your issue. Sylvestre