From communication at scilab-enterprises.com Fri Mar 14 12:07:16 2014 From: communication at scilab-enterprises.com (communication) Date: Fri, 14 Mar 2014 12:07:16 +0100 Subject: [Scilab-Dev] 2 months left before ScilabTEC 2014! In-Reply-To: <5322E1AC.6090401@scilab-enterprises.com> References: <5322E1AC.6090401@scilab-enterprises.com> Message-ID: <5322E2E4.7040908@scilab-enterprises.com> Is this email not displaying correctly? View it in your browser scilabtec 2 months left before ScilabTEC 2014 Program and registration on:***http://www.scilabtec.com/* scilabtec Communication Department, Scilab Enterprises | communication at scilab-enterprises.com 143bis rue Yves Le Coz - 78000 Versailles | www.scilab-enterprises.com - www.scilab.org Scilabtec20 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 22295 bytes Desc: http://www.scilabtec.com/ URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 16786 bytes Desc: http://scilabtec.com/ URL: From peter.balazovic at yahoo.com Wed Mar 12 23:13:29 2014 From: peter.balazovic at yahoo.com (pepe) Date: Wed, 12 Mar 2014 15:13:29 -0700 (PDT) Subject: [Scilab-Dev] Modelica & xcos Message-ID: <1394662409888-4029246.post@n3.nabble.com> Is there simple examples showing how to use Modelica (mblock) within xcos? -- View this message in context: http://mailinglists.scilab.org/Modelica-xcos-tp4029246.html Sent from the Scilab developers - Mailing Lists Archives mailing list archive at Nabble.com. From mkachhwani at gmail.com Mon Mar 24 17:13:07 2014 From: mkachhwani at gmail.com (Mohit Kachhwani) Date: Mon, 24 Mar 2014 21:43:07 +0530 Subject: [Scilab-Dev] Contribute to Scilab Message-ID: Respected Sir/Madam, -------------- next part -------------- An HTML attachment was scrubbed... URL: From mkachhwani at gmail.com Mon Mar 24 17:23:50 2014 From: mkachhwani at gmail.com (Mohit Kachhwani) Date: Mon, 24 Mar 2014 21:53:50 +0530 Subject: [Scilab-Dev] Contribute to Scilab In-Reply-To: References: Message-ID: Respected Sir/madam, I 'm currently pursuing btech in EXTC engineering from VJTI college,Matunga, Mumbai.I would like to part of Scilab development project by contributing to its work as a developer. So i request you to please add me in your development team. Thanking you. Yours faithfully, Mohit Kachhwani -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.baudin at contrib.scilab.org Mon Mar 31 14:52:07 2014 From: michael.baudin at contrib.scilab.org (michael.baudin at contrib.scilab.org) Date: Mon, 31 Mar 2014 14:52:07 +0200 Subject: [Scilab-Dev] Packaging issues Message-ID: Hi, I just released a new version of a module this week-end [1], and it was (wrongly) packaged this morning. Actually, I noticed two problems with this packaging, which are making the process a pain : I think they are worth to share. * The module contains C source code. But the packaging was (wrongly) done as if it was a macro-based module. This is a human error which can happen because the developper has no way to give the information to the packager. What we may need is a button "My module contains a C source" on the atoms web interface. This way, the packager knows what exactly must be done with the sources of the module (i.e. compile the code on several machines). * Many tests fail (as indicated in the distfun_0.8_test.txt logfile). The typical log looks like : [...] 001/160 - [SCI/contrib/distfun/0.8] betacdf..................failed: premature end of the test script 002/160 - [SCI/contrib/distfun/0.8] betainv..................passed [...] I have the same behavior on my machine. Notice that if you run the tests twice, you will not get the same failed/passed status. What happens is that, sometimes (looks like random), some module (say apifun, for example) is not loaded. But the betacdf uses apifun, and this makes the test fail. This happens if the module is loaded either manuall after an exec statement in the .scilab script, or automatically, after an atomsInstall statement. I think that there might be an issue with the way the modules are loaded at startup. Perhaps some function does not wait until all the packages are started up. I have never been able to see this precisely. But this makes the testing process really horrible when it involves dependent modules. Regards, Micha?l PS [1] http://atoms.scilab.org/toolboxes/distfun/0.8