From clement.david at scilab-enterprises.com Mon Feb 1 08:33:52 2016 From: clement.david at scilab-enterprises.com (=?ISO-8859-1?Q?Cl=E9ment?= David) Date: Mon, 01 Feb 2016 08:33:52 +0100 Subject: [Scilab-users] Document for xcos In-Reply-To: References: Message-ID: <1454312032.2921.11.camel@scilab-enterprises.com> (answered on dev) Hi Adhitya, please avoid cross-posting on mailing-lists. See?http://mailinglists.scilab.org/Documentation-for-Xcos-td4033357.html -- Cl?ment Le samedi 30 janvier 2016 ? 11:52 +0530, Adhitya Kamakshidasan a ?crit?: > Hi, > > My name is Adhitya Kamakshidasan and I'm an Intern at FOSSEE, IIT Bombay.? > > We are trying to develop a standalone version of Xcos, that is completely web-based. > > I would like to know if there is any documentation with respect to how Xcos has been written - > Flowcharts, Main methods, PDF's, etc. > > Currently, I'm trying to reverse-engineer the code, by slowly move through the code, and remove > the parts that are not related to Xcos. However, this is taking a lot of time. > > We would like your support in this regard. > > Thanks, > > Adhitya Kamakshidasan > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From shamika.i.nair at gmail.com Mon Feb 1 09:10:56 2016 From: shamika.i.nair at gmail.com (shamikam) Date: Mon, 1 Feb 2016 01:10:56 -0700 (MST) Subject: [Scilab-users] Logical zero Message-ID: <1454314256757-4033361.post@n3.nabble.com> Is there a Scilab equivalent for the false function in Matlab? I want to create a matrix of logical zeros. Is there any other way to do it. Shamika -- View this message in context: http://mailinglists.scilab.org/Logical-zero-tp4033361.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From stephane.mottelet at utc.fr Mon Feb 1 09:20:43 2016 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Mon, 1 Feb 2016 09:20:43 +0100 Subject: [Scilab-users] Logical zero In-Reply-To: <1454314256757-4033361.post@n3.nabble.com> References: <1454314256757-4033361.post@n3.nabble.com> Message-ID: <56AF155B.8020407@utc.fr> Le 01/02/2016 09:10, shamikam a ?crit : > Is there a Scilab equivalent for the false function in Matlab? I want to > create a matrix of logical zeros. Is there any other way to do it. > > Shamika > > > > > > > -- > View this message in context: http://mailinglists.scilab.org/Logical-zero-tp4033361.html > Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users Many ways, such as ~ones(n,m), zeros(n,m)>0, ... S. -- D?partement de G?nie Informatique EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable Universit? de Technologie de Compi?gne - CS 60319 60203 Compi?gne cedex From Tim at Wescottdesign.com Mon Feb 1 10:16:38 2016 From: Tim at Wescottdesign.com (Tim Wescott) Date: Mon, 01 Feb 2016 01:16:38 -0800 Subject: [Scilab-users] Logical zero Message-ID: I believe that a = zeros(n, m) == 1 will do it, but it may not be either the best or the official way.? Sent from my Verizon Wireless 4G LTE smartphone -------- Original message -------- From: shamikam Date: 02/01/2016 12:10 AM (GMT-08:00) To: users at lists.scilab.org Subject: [Scilab-users] Logical zero Is there a Scilab equivalent for the false function in Matlab? I want to create a matrix of logical zeros. Is there any other way to do it. Shamika -- View this message in context: http://mailinglists.scilab.org/Logical-zero-tp4033361.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. _______________________________________________ users mailing list users at lists.scilab.org http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From Serge.Steer at inria.fr Mon Feb 1 11:07:26 2016 From: Serge.Steer at inria.fr (Serge Steer) Date: Mon, 1 Feb 2016 11:07:26 +0100 Subject: [Scilab-users] Logical zero In-Reply-To: References: Message-ID: <56AF2E5E.4050207@inria.fr> Le 01/02/2016 10:16, Tim Wescott a ?crit : > I believe that a = zeros(n, m) == 1 will do it, but it may not be > either the best or the official way. > An other solution is %f(ones(n,m)) Serge > > > Sent from my Verizon Wireless 4G LTE smartphone > > > -------- Original message -------- > From: shamikam > Date: 02/01/2016 12:10 AM (GMT-08:00) > To: users at lists.scilab.org > Subject: [Scilab-users] Logical zero > > Is there a Scilab equivalent for the false function in Matlab? I want to > create a matrix of logical zeros. Is there any other way to do it. > > Shamika > > > > > > > -- > View this message in context: > http://mailinglists.scilab.org/Logical-zero-tp4033361.html > Sent from the Scilab users - Mailing Lists Archives mailing list > archive at Nabble.com. > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From j-lan at online.no Mon Feb 1 14:40:48 2016 From: j-lan at online.no (=?UTF-8?Q?Jan-=c3=85ge_Langeland?=) Date: Mon, 1 Feb 2016 14:40:48 +0100 Subject: [Scilab-users] Logical zero In-Reply-To: <56AF2E5E.4050207@inria.fr> References: <56AF2E5E.4050207@inria.fr> Message-ID: <56AF6060.4040300@online.no> I ran a little speed test with the different alternatives, I found the results surprising: Jan //script ftest.sce m=10000 n=10000 v=ver(); disp(v(1,1:2)); clear a; timer(); a = zeros(n, m) == 1; //best in Scilab 6.0.0 disp(timer()); clear a; timer(); a=zeros(n,m)>0; disp(timer()); clear a; timer(); a=%f(ones(n,m)); disp(timer()); clear a; timer(); a(1:n,1:m)=%f; //best in Scilab 5.5.1 disp(timer()); clear a; //end script ftest.sce -->exec('ftest.sce',-1) !Scilab Version: 5.5.1.1412169962 ! 1.4820095000000037543941 1.372808800000029805233 0.5304033999999546722393 0.2964018999999780135113 -->exec('ftest.sce',-1) !Scilab Version: 6.0.0.1447231131 ! 0.6708043 1.3260085 2.7300175 3.3228213 -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephane.mottelet at utc.fr Mon Feb 1 14:56:35 2016 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Mon, 1 Feb 2016 14:56:35 +0100 Subject: [Scilab-users] Logical zero In-Reply-To: <56AF6060.4040300@online.no> References: <56AF2E5E.4050207@inria.fr> <56AF6060.4040300@online.no> Message-ID: <56AF6413.6020409@utc.fr> BTY, I am worried about the Scilab 6.0 timing (3.3228213 seconds) of a(1:n,1:m)=%f; i.e. more than ten times slower than Scilab 5.5.1 (0.2964019 seconds). Does somebody have an explanation ? S. Le 01/02/2016 14:40, Jan-?ge Langeland a ?crit : > I ran a little speed test with the different alternatives, I found the > results surprising: > > Jan > > //script ftest.sce m=10000 n=10000 v=ver(); disp(v(1,1:2)); clear a; > timer(); a = zeros(n, m) == 1; //best in Scilab 6.0.0 disp(timer()); > clear a; timer(); a=zeros(n,m)>0; disp(timer()); clear a; timer(); > a=%f(ones(n,m)); disp(timer()); clear a; timer(); > *a**(**1**:**n**,**1**:**m**)**=**%f**;* //best in Scilab 5.5.1 > disp(timer()); clear a; //end script ftest.sce -->exec('ftest.sce',-1) > !Scilab Version: 5.5.1.1412169962 ! 1.4820095000000037543941 > 1.372808800000029805233 0.5304033999999546722393 > 0.2964018999999780135113 -->exec('ftest.sce',-1) !Scilab Version: > 6.0.0.1447231131 ! 0.6708043 1.3260085 2.7300175 3.3228213 > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -- D?partement de G?nie Informatique EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable Universit? de Technologie de Compi?gne - CS 60319 60203 Compi?gne cedex -------------- next part -------------- An HTML attachment was scrubbed... URL: From j-lan at online.no Mon Feb 1 15:31:51 2016 From: j-lan at online.no (=?UTF-8?Q?Jan-=c3=85ge_Langeland?=) Date: Mon, 1 Feb 2016 15:31:51 +0100 Subject: [Scilab-users] Logical zero In-Reply-To: References: Message-ID: <56AF6C57.5040709@online.no> I forgot to test a=~ones(n,m). I guess this is the overall winner (from St?phane Mottelet): Scilab 5.5.1: 0.2964019 Scilab 6.0.0: 0.5616036 Jan From Serge.Steer at inria.fr Mon Feb 1 16:06:13 2016 From: Serge.Steer at inria.fr (Serge Steer) Date: Mon, 1 Feb 2016 16:06:13 +0100 Subject: [Scilab-users] Logical zero In-Reply-To: <56AF6060.4040300@online.no> References: <56AF2E5E.4050207@inria.fr> <56AF6060.4040300@online.no> Message-ID: <56AF7465.2020608@inria.fr> find below the results on my computer (Linux) for Scilab-5.5.2 and last nightly build Version de Scilab : 6.0.0.1454090908 Version de Scilab : 5.5.2.1427793548 zeros(n, m) == 1 11.788 1.416 zeros(n,m)>0 8.47 1.043 %f(ones(n,m)) 9.347 1.164 a(1:n,1:m)=%f 4.352 0.816 *The scilab6 times are quite high!* -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christophe.Dang at sidel.com Mon Feb 1 17:43:11 2016 From: Christophe.Dang at sidel.com (Dang Ngoc Chan, Christophe) Date: Mon, 1 Feb 2016 16:43:11 +0000 Subject: [Scilab-users] Logical zero In-Reply-To: <56AF6060.4040300@online.no> References: <56AF2E5E.4050207@inria.fr> <56AF6060.4040300@online.no> Message-ID: Hello, > De : Jan-?ge Langeland > Envoy? : lundi 1 f?vrier 2016 14:41 > > I ran a little speed test with the different alternatives, I found the results surprising: These kind of tests are of course interesting, but I'm always suspicious because of the buffering. -- Christophe Dang Ngoc Chan Mechanical calculation engineer This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error), please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. From j-lan at online.no Tue Feb 2 09:16:52 2016 From: j-lan at online.no (=?UTF-8?Q?Jan_=c3=85ge_Langeland?=) Date: Tue, 2 Feb 2016 09:16:52 +0100 Subject: [Scilab-users] Logical zero In-Reply-To: References: <56AF2E5E.4050207@inria.fr> <56AF6060.4040300@online.no> Message-ID: <56B065F4.40400@online.no> On 01.02.2016 17:43, Dang Ngoc Chan, Christophe wrote: > Hello, > >> De : Jan-?ge Langeland >> Envoy? : lundi 1 f?vrier 2016 14:41 >> >> I ran a little speed test with the different alternatives, I found the results surprising: > These kind of tests are of course interesting, but I'm always suspicious because of the buffering. > > -- > Christophe Dang Ngoc Chan > Mechanical calculation engineer > Well when I watch the CPU load during execution of this script (in Windows 7 and 10), I can clearly see that they work longer and harder for Scilab 6. The load distribution is a bit different, Scilab 5.5 loads one CPU to 100%, while Scilab 6 distributes the load more on 2-4 CPUs. Jan From clement.david at scilab-enterprises.com Tue Feb 2 11:36:32 2016 From: clement.david at scilab-enterprises.com (=?ISO-8859-1?Q?Cl=E9ment?= David) Date: Tue, 02 Feb 2016 11:36:32 +0100 Subject: [Scilab-users] Logical zero In-Reply-To: <56AF6413.6020409@utc.fr> References: <56AF2E5E.4050207@inria.fr> <56AF6060.4040300@online.no> <56AF6413.6020409@utc.fr> Message-ID: <1454409392.2799.15.camel@scilab-enterprises.com> Hello all, Yes, that's quiet strange results and we probably have a bug on that expression. Could you open a bug to track that issue please ? But more generally, on the Scilab5 vs Scilab6 performance, we (Calixte in fact) made some analysis pass for our JIT demo use-case and we may re-use it to speed-up the interpreter but this is not done yet. There is only "trivial" shortcuts for common use-cases and, of course, the 5.x version might be more "performant" as it contains more and more complex shortcuts. While micro-benchmarking Scilab 6, please keep also in mind that the Copy-On-Write mechanism on Scilab 6 speed up auto-magically function calls and we checked that on average Scilab 6 is sometimes slower sometimes speeder than Scilab 5 but in the same order of magnitude. If you found any other issue like this one, do not hesitate to open a bug. Scilab6 may probably fallback in the generic (and worst case) implementation instead of having either a shortcut or an analysis pass. -- Cl?ment Le lundi 01 f?vrier 2016 ? 14:56 +0100, St?phane Mottelet a ?crit?: > BTY, I am worried about the Scilab 6.0 timing (3.3228213 seconds)? of > > a(1:n,1:m)=%f; > > i.e. more than ten times slower than Scilab 5.5.1 (0.2964019 seconds).? > > Does somebody have an explanation ?? > > S. > > > Le 01/02/2016 14:40, Jan-?ge Langeland a ?crit?: > > ?I ran a little speed test with the different alternatives, I found the results surprising: > > > > Jan? > > > > //script ftest.sce > > m=10000 > > n=10000 > > v=ver(); > > disp(v(1,1:2)); > > clear a; > > timer(); > > a = zeros(n, m) == 1; //best in Scilab 6.0.0 > > disp(timer()); > > clear a; > > timer(); > > a=zeros(n,m)>0; > > disp(timer()); > > clear a; > > timer(); > > a=%f(ones(n,m)); > > disp(timer()); > > clear a; > > timer(); > > a(1:n,1:m)=%f; //best in Scilab 5.5.1? > > disp(timer()); > > clear a; > > //end script ftest.sce > > > > > > -->exec('ftest.sce',-1) > > ? > > !Scilab Version:???5.5.1.1412169962??! > > ? > > ????1.4820095000000037543941?? > > ? > > ????1.372808800000029805233?? > > ? > > ????0.5304033999999546722393?? > > ? > > ????0.2964018999999780135113?? > > > > -->exec('ftest.sce',-1) > > > > !Scilab Version:???6.0.0.1447231131??! > > > > ????0.6708043 > > > > ????1.3260085 > > > > ????2.7300175 > > > > ????3.3228213 > > > > > > > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/users > > --? > D?partement de G?nie Informatique > EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable > Universit? de Technologie de Compi?gne -??CS 60319 > 60203 Compi?gne cedex > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From alex_jameson48 at hotmail.com Tue Feb 2 14:31:41 2016 From: alex_jameson48 at hotmail.com (jamesona) Date: Tue, 2 Feb 2016 06:31:41 -0700 (MST) Subject: [Scilab-users] Installing IPD in Scilab on an iMac Message-ID: <1454419901294-4033375.post@n3.nabble.com> I've installed Scilab (5.5.2) {version 6 won't come up} on both my iMac running El Capitan [but using the Yosemite dmg (the other dmg won't accept it!)] and also on my wifes' Windows 10 machine and on a Windows 7 OS within a virtual box on the iMac [This of course is just too slow and awkward]. On the Windows machines all the image processing toolboxes have installed: no issues needed resolving. Unfortunately on the iMac two of the toolboxes won't install; the one i'm most concerned with is the IPD. My ultimate aim is to learn enough about Scilab to be able to replicate image processing I have done on Matlab. Clearly this is a major stumbling block and help would be most appreciated in this regard! -- View this message in context: http://mailinglists.scilab.org/Installing-IPD-in-Scilab-on-an-iMac-tp4033375.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From david.cheze at cea.fr Wed Feb 3 14:21:26 2016 From: david.cheze at cea.fr (=?UTF-8?Q?David_Ch=C3=A8ze?=) Date: Wed, 3 Feb 2016 06:21:26 -0700 (MST) Subject: [Scilab-users] issue providing command to powershell Message-ID: <1454505686276-4033376.post@n3.nabble.com> Hi all, to automate some text file encoding conversion to UTF-8 (for csvRead) under windows platform, I'm using the powershell windows native scripting language : PS get-content -Path "C:\Users\dc227480\Documents\temp\Donn?es IAQ SENSE 29_01_2016 10_45_00 1.dat.csv" | out-file "C:\Users\dc227480\Documents\temp\Donn?es IAQ SENSE 29_01_2016 10_45_00 1.UTF-8.csv" -encoding utf8 that is running properly in powershell window but fails when I ask from scilab: pscmd="get-content -Path ""C:\Users\dc227480\Documents\temp\Donn?es IAQ SENSE 29_01_2016 10_45_00 1.dat.csv"" | out-file ""C:\Users\dc227480\Documents\temp\Donn?es IAQ SENSE 29_01_2016 10_45_00 1.UTF-8.csv"" -encoding utf8" powershell(pscmd) ans = !Get-Content : Impossible de trouver un param?tre positionnel acceptant ! ! ! !l'argument ?IAQ?. ! ! ! !Au caract?re Ligne:1 : 1 ! ! ! !+ get-content -Path C:\Users\dc227480\Documents\temp\Donn?es IAQ SENSE ! ! ! !29_01_2016 ... ! ! ! !+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ! ! ! !~~~ ! ! ! ! + CategoryInfo : InvalidArgument : (:) [Get-Content], ParameterBi ! ! ! ! ndingException ! ! ! ! + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell ! ! ! ! .Commands.GetContentCommand ! ! ! ! ! Then I remove space from the file name and it works: pscmd="get-content -Path ""C:\Users\dc227480\Documents\temp\Donn?es_IAQ_SENSE_29_01_2016_10_45_00_1.dat.csv"" | out-file ""C:\Users\dc227480\Documents\temp\Donn?es_IAQ_SENSE_29_01_2016_10_45_00_1.UTF-8.csv"" -encoding utf8" powershell(pscmd) Is there a workaround to make the powershell() function from scilab to provide proper string to powershell ? Thank you for your feedback, David -- View this message in context: http://mailinglists.scilab.org/issue-providing-command-to-powershell-tp4033376.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From sgougeon at free.fr Wed Feb 3 16:47:31 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Wed, 3 Feb 2016 16:47:31 +0100 Subject: [Scilab-users] issue providing command to powershell In-Reply-To: <1454505686276-4033376.post@n3.nabble.com> References: <1454505686276-4033376.post@n3.nabble.com> Message-ID: <56B22113.7090805@free.fr> Hello, Le 03/02/2016 14:21, David Ch?ze a ?crit : > .../... > pscmd="get-content -Path ""C:\Users\dc227480\Documents\temp\Donn?es IAQ > SENSE 29_01_2016 10_45_00 1.dat.csv"" | out-file > ""C:\Users\dc227480\Documents\temp\Donn?es IAQ SENSE 29_01_2016 10_45_00 > 1.UTF-8.csv"" -encoding utf8" > powershell(pscmd) > .../... > > Is there a workaround to make the powershell() function from scilab to > provide proper string to powershell ? I would first try doubling double-quotes, as in: pscmd="get-content -Path """"C:\Users\dc227480\Documents\temp\Donn?es IAQ SENSE 29_01_2016 10_45_00 1.dat.csv"""" | out-file """"C:\Users\dc227480\Documents\temp\Donn?es IAQ SENSE 29_01_2016 10_45_00 1.UTF-8.csv"""" -encoding utf8" powershell(pscmd) Let us know what it yields. Regards Samuel Gougeon From grivet at cnrs-orleans.fr Wed Feb 3 16:30:01 2016 From: grivet at cnrs-orleans.fr (grivet) Date: Wed, 3 Feb 2016 16:30:01 +0100 Subject: [Scilab-users] mixing normal and math mode in label In-Reply-To: <5698DAA7.90103@free.fr> References: <56941D70.8040301@free.fr> <5698DAA7.90103@free.fr> Message-ID: <56B21CF9.8020606@cnrs-orleans.fr> Hello, How can I insert exponents inside a text label ? I tried: xlabel("frequency (h$^{-1}$)"). This did not work for me (Win 7, Scilab 5.5.1): the Latex part is not interpreted but reproduced verbatim. Thank you for any suggestion JP Grivet From sgougeon at free.fr Wed Feb 3 17:07:24 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Wed, 3 Feb 2016 17:07:24 +0100 Subject: [Scilab-users] mixing normal and math mode in label In-Reply-To: <56B21CF9.8020606@cnrs-orleans.fr> References: <56941D70.8040301@free.fr> <5698DAA7.90103@free.fr> <56B21CF9.8020606@cnrs-orleans.fr> Message-ID: <56B225BC.6000205@free.fr> Hello, Le 03/02/2016 16:30, grivet a ?crit : > Hello, > How can I insert exponents inside a text label ? > I tried: xlabel("frequency (h$^{-1}$)"). This did not work for me > (Win 7, Scilab 5.5.1): > the Latex part is not interpreted but reproduced verbatim. > Thank you for any suggestion > JP Grivet . When you need LaTeX in a string, the whole string must be in LaTeX, started with "$" from the beginning, and ended with "$" at its complete end. If you need to mix text and LaTeX as in your example, the text must be protected for instance in a \mbox{}. For you example: xlabel("$\mbox{frequency }(h^{-1})$") // will work Samuel Gougeon From Jean-Yves.Baudais at insa-rennes.fr Wed Feb 3 17:07:36 2016 From: Jean-Yves.Baudais at insa-rennes.fr (jbaudais@insa-rennes.fr) Date: Wed, 3 Feb 2016 17:07:36 +0100 Subject: [Scilab-users] mixing normal and math mode in label In-Reply-To: <56B21CF9.8020606@cnrs-orleans.fr> References: <56941D70.8040301@free.fr> <5698DAA7.90103@free.fr> <56B21CF9.8020606@cnrs-orleans.fr> Message-ID: <56B225C8.9060704@insa-rennes.fr> Le 03/02/2016 16:30, grivet a ?crit : > Hello, > How can I insert exponents inside a text label ? > I tried: xlabel("frequency (h$^{-1}$)"). This did not work for me (Win > 7, Scilab 5.5.1): > the Latex part is not interpreted but reproduced verbatim. I don?t know how to mix verbatim and LaTeX but all can be in LaTeX format xlabel("$\text{frequency} (h^{-1})$") Jean-Yves From sgougeon at free.fr Wed Feb 3 17:16:09 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Wed, 3 Feb 2016 17:16:09 +0100 Subject: [Scilab-users] issue providing command to powershell In-Reply-To: <56B22113.7090805@free.fr> References: <1454505686276-4033376.post@n3.nabble.com> <56B22113.7090805@free.fr> Message-ID: <56B227C9.8020504@free.fr> Le 03/02/2016 16:47, Samuel Gougeon a ?crit : > > Let us know what it yields. . Actually, as editing the macro powershell teaches it, this proposal should work. Fixing the Scilab powershell() code to no longer demand this doubling will be straightforward, whether a bug report is opened (not yet the case). The powershell help page could be also a bit improved. S. Gougeon From grivet at cnrs-orleans.fr Wed Feb 3 17:47:49 2016 From: grivet at cnrs-orleans.fr (grivet) Date: Wed, 3 Feb 2016 17:47:49 +0100 Subject: [Scilab-users] mixing normal and math mode in label In-Reply-To: <56B225C8.9060704@insa-rennes.fr> References: <56941D70.8040301@free.fr> <5698DAA7.90103@free.fr> <56B21CF9.8020606@cnrs-orleans.fr> <56B225C8.9060704@insa-rennes.fr> Message-ID: <56B22F35.5000706@cnrs-orleans.fr> Thank you Samuel and Jean-Yves. The line xlabel("$\mbox{fr?quence (h}^{-1})$"); does exactly what I wanted. A small complement: the first $ must not be followed by a space and the last $ must not be preceded by a space. JP Grivet From sgougeon at free.fr Wed Feb 3 17:54:00 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Wed, 3 Feb 2016 17:54:00 +0100 Subject: [Scilab-users] mixing normal and math mode in label In-Reply-To: <56B22F35.5000706@cnrs-orleans.fr> References: <56941D70.8040301@free.fr> <5698DAA7.90103@free.fr> <56B21CF9.8020606@cnrs-orleans.fr> <56B225C8.9060704@insa-rennes.fr> <56B22F35.5000706@cnrs-orleans.fr> Message-ID: <56B230A8.8040808@free.fr> Le 03/02/2016 17:47, grivet a ?crit : > Thank you Samuel and Jean-Yves. The line > xlabel("$\mbox{fr?quence (h}^{-1})$"); > does exactly what I wanted. > A small complement: the first $ must not be followed by a space and > the last $ > must not be preceded by a space. . ? No problem for me, even with such spaces: xlabel("$ \mbox{fr?quence (h}^{-1}) $"); // also works (tested). SG From grivet at cnrs-orleans.fr Wed Feb 3 18:09:17 2016 From: grivet at cnrs-orleans.fr (grivet) Date: Wed, 3 Feb 2016 18:09:17 +0100 Subject: [Scilab-users] labels again In-Reply-To: <56B225C8.9060704@insa-rennes.fr> References: <56941D70.8040301@free.fr> <5698DAA7.90103@free.fr> <56B21CF9.8020606@cnrs-orleans.fr> <56B225C8.9060704@insa-rennes.fr> Message-ID: <56B2343D.9000704@cnrs-orleans.fr> Hello, When I do xlabel("$\mbox{fr?quence (h}^{-1})$"); ylabel("DSP (?chelle logarithmique)" ); I find that the x and y labels are neither in the same font nor in the same size. I have to add "fontsize",3,"fontname","times" (for instance) in order to get to labels looking almost alike. Samuel: you are correct about spaces. I don't know what happened in my previous trials. Cheers, JP Grivet From david.cheze at cea.fr Wed Feb 3 18:12:43 2016 From: david.cheze at cea.fr (=?UTF-8?Q?David_Ch=C3=A8ze?=) Date: Wed, 3 Feb 2016 10:12:43 -0700 (MST) Subject: [Scilab-users] issue providing command to powershell In-Reply-To: <56B227C9.8020504@free.fr> References: <1454505686276-4033376.post@n3.nabble.com> <56B22113.7090805@free.fr> <56B227C9.8020504@free.fr> Message-ID: <1454519563086-4033385.post@n3.nabble.com> Hi Samuel, I tried but was not successful: --> pscmd="get-content -Path """C:\Users\dc227480\Documents\temp\Donn?es IAQ SENSE 29_01_2016 10_45_00 1.dat.csv""" | out-file """C:\Users\dc227480\Documents\temp\Donn?es IAQ SENSE 29_01_2016 10_45_00 1.UTF-8.csv""" -encoding utf8" [Scilab6] pscmd="get-content -Path """C:\Users\dc227480\Documents\temp\Donn?es IAQ SENSE 29_01_2016 10_45_00 1.dat.csv""" | out-file """C:\Users\dc227480\Documents\temp\Donn?es IAQ SENSE 29_01_2016 10_45_00 1.UTF-8.csv""" -encoding utf8" [Scilab6] prompt : 1.29 - 1.30 : syntax error, unexpected identifier, expecting end of file scilab6 prompt indicates error detected after the third double quote: pscmd="get-content -Path """ -- View this message in context: http://mailinglists.scilab.org/issue-providing-command-to-powershell-tp4033376p4033385.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From sgougeon at free.fr Wed Feb 3 18:16:17 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Wed, 3 Feb 2016 18:16:17 +0100 Subject: [Scilab-users] labels again In-Reply-To: <56B2343D.9000704@cnrs-orleans.fr> References: <56941D70.8040301@free.fr> <5698DAA7.90103@free.fr> <56B21CF9.8020606@cnrs-orleans.fr> <56B225C8.9060704@insa-rennes.fr> <56B2343D.9000704@cnrs-orleans.fr> Message-ID: <56B235E1.5060306@free.fr> Le 03/02/2016 18:09, grivet a ?crit : > Hello, > When I do > xlabel("$\mbox{fr?quence (h}^{-1})$"); > ylabel("DSP (?chelle logarithmique)" ); > I find that the x and y labels are neither in the same font nor in the > same size. I have to add > "fontsize",3,"fontname","times" > (for instance) in order to get to labels looking almost alike. When this really matters, you may do as well ylabel("$\mbox{DSP (?chelle logarithmique)}$" ); to be sure using the same (LaTeX) fonts. SG From david.cheze at cea.fr Wed Feb 3 18:27:10 2016 From: david.cheze at cea.fr (=?UTF-8?Q?David_Ch=C3=A8ze?=) Date: Wed, 3 Feb 2016 10:27:10 -0700 (MST) Subject: [Scilab-users] issue providing command to powershell In-Reply-To: <1454519563086-4033385.post@n3.nabble.com> References: <1454505686276-4033376.post@n3.nabble.com> <56B22113.7090805@free.fr> <56B227C9.8020504@free.fr> <1454519563086-4033385.post@n3.nabble.com> Message-ID: <1454520430057-4033387.post@n3.nabble.com> finallly it's solved: you don't need doubling, you don't need tripling but you need four double quotes and it works like a charm ! Good to know... thank you , David --> pscmd="get-content -Path """"C:\Users\dc227480\Documents\temp\Donn?es IAQ SENSE 29_01_2016 10_45_00 1.dat.csv"""" | out-file """"C:\Users\dc227480\Documents\temp\Donn?es IAQ SENSE 29_01_2016 10_45_00 1.UTF-8.csv"""" -encoding utf8" pscmd = get-content -Path ""C:\Users\dc227480\Documents\temp\Donn?es IAQ SENSE 29_01_201 6 10_45_00 1.dat.csv"" | out-file ""C:\Users\dc227480\Documents\temp\Donn?es IAQ SENSE 29_01_2016 10_45_00 1.UTF-8.csv"" -encoding utf8 --> powershell(pscmd) ans = [] -- View this message in context: http://mailinglists.scilab.org/issue-providing-command-to-powershell-tp4033376p4033387.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From sgougeon at free.fr Wed Feb 3 18:35:47 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Wed, 3 Feb 2016 18:35:47 +0100 Subject: [Scilab-users] issue providing command to powershell In-Reply-To: <1454520430057-4033387.post@n3.nabble.com> References: <1454505686276-4033376.post@n3.nabble.com> <56B22113.7090805@free.fr> <56B227C9.8020504@free.fr> <1454519563086-4033385.post@n3.nabble.com> <1454520430057-4033387.post@n3.nabble.com> Message-ID: <56B23A73.8090608@free.fr> Le 03/02/2016 18:27, David Ch?ze a ?crit : > finallly it's solved: > you don't need doubling, you don't need tripling but you need four double > quotes and it works like a charm ! . As posted. > Good to know... Better to correct it. Could you report it? > thank you , You are welcome Samuel From arctica1963 at gmail.com Fri Feb 5 10:48:05 2016 From: arctica1963 at gmail.com (Lester Anderson) Date: Fri, 5 Feb 2016 09:48:05 +0000 Subject: [Scilab-users] Using Scinetcdf module Message-ID: Hello all I am looking to use the sciNetCDF module to work with GMT grid files but have some issues. Reading a GMT grid is not a problem as far as I can tell, so the following does read the file (and z variable), storing the values in the grav array: source = fullfile('Q:\geophys\Gz.grd') grav = ncread(source,'z') Hy = hilbert(grav); // write Hy variable to new file I am having problems with writing out the processed data e.g write a new grid (Gz_Hy.grd) with the Hilbert transform solution filename = fullfile('Q:\geophys\Gz_Hy.grd') ncwrite(filename, 'Hy') // does not work Error return: ncwrite(filename, 'Hy') !--error 77 ncwrite: Wrong number of input argument(s): 3 to 5 expected. at line 5 of exec file called by : exec('Q:\geophys\Lester\SCILAB_work\netcdf1.sce', -1) Any advice would be appreciated. Thanks Lester From arctica1963 at gmail.com Fri Feb 5 10:56:16 2016 From: arctica1963 at gmail.com (Lester Anderson) Date: Fri, 5 Feb 2016 09:56:16 +0000 Subject: [Scilab-users] Hilbert transform query Message-ID: Hello A quick query. How would one define the Hilbert transform of a grid for X and Y directions; looking for two solutions Hx and Hy (for the real values). Thanks Lester From harpreet.mertia at gmail.com Fri Feb 5 11:15:39 2016 From: harpreet.mertia at gmail.com (Harpreet Singh Rathore) Date: Fri, 5 Feb 2016 15:45:39 +0530 Subject: [Scilab-users] Using Scinetcdf module In-Reply-To: References: Message-ID: Dear Lester, As I can see the error is saying minimum 3 inputs are required. And after going through the help of the following function, you also have to pass the value which you have to store in the 'Hy'. You can go through the help files of ncwrite by typing *help ncwrite* in the console. Regards Harpreet On Fri, Feb 5, 2016 at 3:18 PM, Lester Anderson wrote: > Hello all > > I am looking to use the sciNetCDF module to work with GMT grid files > but have some issues. > > Reading a GMT grid is not a problem as far as I can tell, so the > following does read the file (and z variable), storing the values in > the grav array: > > source = fullfile('Q:\geophys\Gz.grd') > grav = ncread(source,'z') > Hy = hilbert(grav); // write Hy variable to new file > > I am having problems with writing out the processed data e.g write a > new grid (Gz_Hy.grd) with the Hilbert transform solution > > filename = fullfile('Q:\geophys\Gz_Hy.grd') > ncwrite(filename, 'Hy') // does not work > > Error return: > > ncwrite(filename, 'Hy') > !--error 77 > ncwrite: Wrong number of input argument(s): 3 to 5 expected. > at line 5 of exec file called by : > exec('Q:\geophys\Lester\SCILAB_work\netcdf1.sce', -1) > > Any advice would be appreciated. > > Thanks > Lester > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > -- Thanks and Regards Harpreet Singh -------------- next part -------------- An HTML attachment was scrubbed... URL: From arctica1963 at gmail.com Fri Feb 5 11:31:51 2016 From: arctica1963 at gmail.com (Lester Anderson) Date: Fri, 5 Feb 2016 10:31:51 +0000 Subject: [Scilab-users] Using Scinetcdf module In-Reply-To: References: Message-ID: Hello Harpreet, I altered the code a bit but still get a problem Hy = hilbert(grav); filename = fullfile('Q:\geophys\Gz_Hy.grd') // set output filename // ncwrite(filename, varname, vardata, [start, [stride]]) ncwrite(filename, 'Hilb_Hy','Hy') // write variable Hilb_Hy with data from Hy Error message: ncwrite(filename, 'Hilb_Hy','Hy') // write variable Hilb_Hy with data from Hy !--error 999 ncwrite: nc_inq_varid() returned the error -49: NetCDF: Variable not found. at line 6 of exec file called by : exec('Q:\geophys\Lester\SCILAB_work\netcdf1.sce', -1) In this case I want to define a variable name Hilb_Hy (although can use any name really) in the netCDF file and write the output of the Hilbert (Hy) transform. Cannot see the solution On 5 February 2016 at 10:15, Harpreet Singh Rathore wrote: > Dear Lester, > > As I can see the error is saying minimum 3 inputs are required. And after > going through the help of the following function, you also have to pass the > value which you have to store in the 'Hy'. You can go through the help files > of ncwrite by typing help ncwrite in the console. > > Regards > Harpreet > > On Fri, Feb 5, 2016 at 3:18 PM, Lester Anderson > wrote: >> >> Hello all >> >> I am looking to use the sciNetCDF module to work with GMT grid files >> but have some issues. >> >> Reading a GMT grid is not a problem as far as I can tell, so the >> following does read the file (and z variable), storing the values in >> the grav array: >> >> source = fullfile('Q:\geophys\Gz.grd') >> grav = ncread(source,'z') >> Hy = hilbert(grav); // write Hy variable to new file >> >> I am having problems with writing out the processed data e.g write a >> new grid (Gz_Hy.grd) with the Hilbert transform solution >> >> filename = fullfile('Q:\geophys\Gz_Hy.grd') >> ncwrite(filename, 'Hy') // does not work >> >> Error return: >> >> ncwrite(filename, 'Hy') >> !--error 77 >> ncwrite: Wrong number of input argument(s): 3 to 5 expected. >> at line 5 of exec file called by : >> exec('Q:\geophys\Lester\SCILAB_work\netcdf1.sce', -1) >> >> Any advice would be appreciated. >> >> Thanks >> Lester >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> http://lists.scilab.org/mailman/listinfo/users > > > > > -- > Thanks and Regards > Harpreet Singh > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > From simon.marchetto at scilab-enterprises.com Fri Feb 5 11:45:57 2016 From: simon.marchetto at scilab-enterprises.com (Simon Marchetto) Date: Fri, 5 Feb 2016 11:45:57 +0100 Subject: [Scilab-users] Using Scinetcdf module In-Reply-To: References: Message-ID: <56B47D65.1020805@scilab-enterprises.com> Hello Lester , As explained in the ncwrite() help page, you have to create first the variable with nccreate() before writing it. As Hy is probably a matrix, you may have to specify also its dimensions as argument of nccreate(). And eventually its type, if it is not double. See the documentation for help. About your script: ncwrite(filename, 'Hilb_Hy','Hy') With this, you write the string 'Hy' into the variable 'Hilb_Hy', I don't think that's what you want to do. Regards, Simon Le 05/02/2016 11:31, Lester Anderson a ?crit : > Hello Harpreet, > > I altered the code a bit but still get a problem > > Hy = hilbert(grav); > filename = fullfile('Q:\geophys\Gz_Hy.grd') // set output filename > // ncwrite(filename, varname, vardata, [start, [stride]]) > ncwrite(filename, 'Hilb_Hy','Hy') // write variable Hilb_Hy with data from Hy > > Error message: > > ncwrite(filename, 'Hilb_Hy','Hy') // write variable Hilb_Hy with data from Hy > !--error 999 > ncwrite: nc_inq_varid() returned the error -49: NetCDF: Variable not found. > at line 6 of exec file called by : > exec('Q:\geophys\Lester\SCILAB_work\netcdf1.sce', -1) > > In this case I want to define a variable name Hilb_Hy (although can > use any name really) in the netCDF file and write the output of the > Hilbert (Hy) transform. > > Cannot see the solution > > > > On 5 February 2016 at 10:15, Harpreet Singh Rathore > wrote: >> Dear Lester, >> >> As I can see the error is saying minimum 3 inputs are required. And after >> going through the help of the following function, you also have to pass the >> value which you have to store in the 'Hy'. You can go through the help files >> of ncwrite by typing help ncwrite in the console. >> >> Regards >> Harpreet >> >> On Fri, Feb 5, 2016 at 3:18 PM, Lester Anderson >> wrote: >>> Hello all >>> >>> I am looking to use the sciNetCDF module to work with GMT grid files >>> but have some issues. >>> >>> Reading a GMT grid is not a problem as far as I can tell, so the >>> following does read the file (and z variable), storing the values in >>> the grav array: >>> >>> source = fullfile('Q:\geophys\Gz.grd') >>> grav = ncread(source,'z') >>> Hy = hilbert(grav); // write Hy variable to new file >>> >>> I am having problems with writing out the processed data e.g write a >>> new grid (Gz_Hy.grd) with the Hilbert transform solution >>> >>> filename = fullfile('Q:\geophys\Gz_Hy.grd') >>> ncwrite(filename, 'Hy') // does not work >>> >>> Error return: >>> >>> ncwrite(filename, 'Hy') >>> !--error 77 >>> ncwrite: Wrong number of input argument(s): 3 to 5 expected. >>> at line 5 of exec file called by : >>> exec('Q:\geophys\Lester\SCILAB_work\netcdf1.sce', -1) >>> >>> Any advice would be appreciated. >>> >>> Thanks >>> Lester >>> _______________________________________________ >>> users mailing list >>> users at lists.scilab.org >>> http://lists.scilab.org/mailman/listinfo/users >> >> >> >> -- >> Thanks and Regards >> Harpreet Singh >> >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> http://lists.scilab.org/mailman/listinfo/users >> > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From harpreet.mertia at gmail.com Fri Feb 5 11:46:50 2016 From: harpreet.mertia at gmail.com (Harpreet Singh Rathore) Date: Fri, 5 Feb 2016 16:16:50 +0530 Subject: [Scilab-users] Using Scinetcdf module In-Reply-To: References: Message-ID: Hey You have not created the variable in the file. First you have to create a variable in the following file using the command nccreate(filename, 'Hilb_Hy', 'Dimensions', list('r', no_row, 'c', no_column); after that you can pass the ncwrite command and you have to pass like this ncwrite(filename, 'Hilb_Hy',Hy) as Hy is a matrix. Regards Harpreet Singh On Fri, Feb 5, 2016 at 4:01 PM, Lester Anderson wrote: > Hello Harpreet, > > I altered the code a bit but still get a problem > > Hy = hilbert(grav); > filename = fullfile('Q:\geophys\Gz_Hy.grd') // set output filename > // ncwrite(filename, varname, vardata, [start, [stride]]) > ncwrite(filename, 'Hilb_Hy','Hy') // write variable Hilb_Hy with data from > Hy > > Error message: > > ncwrite(filename, 'Hilb_Hy','Hy') // write variable Hilb_Hy with data from > Hy > !--error 999 > ncwrite: nc_inq_varid() returned the error -49: NetCDF: Variable not found. > at line 6 of exec file called by : > exec('Q:\geophys\Lester\SCILAB_work\netcdf1.sce', -1) > > In this case I want to define a variable name Hilb_Hy (although can > use any name really) in the netCDF file and write the output of the > Hilbert (Hy) transform. > > Cannot see the solution > > > > On 5 February 2016 at 10:15, Harpreet Singh Rathore > wrote: > > Dear Lester, > > > > As I can see the error is saying minimum 3 inputs are required. And after > > going through the help of the following function, you also have to pass > the > > value which you have to store in the 'Hy'. You can go through the help > files > > of ncwrite by typing help ncwrite in the console. > > > > Regards > > Harpreet > > > > On Fri, Feb 5, 2016 at 3:18 PM, Lester Anderson > > wrote: > >> > >> Hello all > >> > >> I am looking to use the sciNetCDF module to work with GMT grid files > >> but have some issues. > >> > >> Reading a GMT grid is not a problem as far as I can tell, so the > >> following does read the file (and z variable), storing the values in > >> the grav array: > >> > >> source = fullfile('Q:\geophys\Gz.grd') > >> grav = ncread(source,'z') > >> Hy = hilbert(grav); // write Hy variable to new file > >> > >> I am having problems with writing out the processed data e.g write a > >> new grid (Gz_Hy.grd) with the Hilbert transform solution > >> > >> filename = fullfile('Q:\geophys\Gz_Hy.grd') > >> ncwrite(filename, 'Hy') // does not work > >> > >> Error return: > >> > >> ncwrite(filename, 'Hy') > >> !--error 77 > >> ncwrite: Wrong number of input argument(s): 3 to 5 expected. > >> at line 5 of exec file called by : > >> exec('Q:\geophys\Lester\SCILAB_work\netcdf1.sce', -1) > >> > >> Any advice would be appreciated. > >> > >> Thanks > >> Lester > >> _______________________________________________ > >> users mailing list > >> users at lists.scilab.org > >> http://lists.scilab.org/mailman/listinfo/users > > > > > > > > > > -- > > Thanks and Regards > > Harpreet Singh > > > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/users > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > -- Thanks and Regards Harpreet Singh -------------- next part -------------- An HTML attachment was scrubbed... URL: From arctica1963 at gmail.com Fri Feb 5 12:26:45 2016 From: arctica1963 at gmail.com (Lester Anderson) Date: Fri, 5 Feb 2016 11:26:45 +0000 Subject: [Scilab-users] Using Scinetcdf module In-Reply-To: References: Message-ID: Hi Simon, Hy is a matrix and the input grid used has dimensions of 601 x 601 (x,y). Reading the data in is fine and the matrix is as expected in the variable browser. grav = ncread(source,'z') is all fine with a 601 x 601 matrix Create variable Hilb_Hy: nccreate(filename,'Hilb_Hy','Dimensions',list('r',601,'c',601)) !--error 999 nccreate: nc_def_var() returned the error -42: NetCDF: String match to name in use. Do you have an example grid to test the read and write function. Would it help to send you a copy of the grid file? Thanks On 5 February 2016 at 10:46, Harpreet Singh Rathore wrote: > Hey > > You have not created the variable in the file. First you have to create a > variable in the following file using the command nccreate(filename, > 'Hilb_Hy', 'Dimensions', list('r', no_row, 'c', no_column); after that you > can pass the ncwrite command and you have to pass like this > ncwrite(filename, 'Hilb_Hy',Hy) as Hy is a matrix. > > Regards > Harpreet Singh > > On Fri, Feb 5, 2016 at 4:01 PM, Lester Anderson > wrote: >> >> Hello Harpreet, >> >> I altered the code a bit but still get a problem >> >> Hy = hilbert(grav); >> filename = fullfile('Q:\geophys\Gz_Hy.grd') // set output filename >> // ncwrite(filename, varname, vardata, [start, [stride]]) >> ncwrite(filename, 'Hilb_Hy','Hy') // write variable Hilb_Hy with data from >> Hy >> >> Error message: >> >> ncwrite(filename, 'Hilb_Hy','Hy') // write variable Hilb_Hy with data from >> Hy >> !--error 999 >> ncwrite: nc_inq_varid() returned the error -49: NetCDF: Variable not >> found. >> at line 6 of exec file called by : >> exec('Q:\geophys\Lester\SCILAB_work\netcdf1.sce', -1) >> >> In this case I want to define a variable name Hilb_Hy (although can >> use any name really) in the netCDF file and write the output of the >> Hilbert (Hy) transform. >> >> Cannot see the solution >> >> >> >> On 5 February 2016 at 10:15, Harpreet Singh Rathore >> wrote: >> > Dear Lester, >> > >> > As I can see the error is saying minimum 3 inputs are required. And >> > after >> > going through the help of the following function, you also have to pass >> > the >> > value which you have to store in the 'Hy'. You can go through the help >> > files >> > of ncwrite by typing help ncwrite in the console. >> > >> > Regards >> > Harpreet >> > >> > On Fri, Feb 5, 2016 at 3:18 PM, Lester Anderson >> > wrote: >> >> >> >> Hello all >> >> >> >> I am looking to use the sciNetCDF module to work with GMT grid files >> >> but have some issues. >> >> >> >> Reading a GMT grid is not a problem as far as I can tell, so the >> >> following does read the file (and z variable), storing the values in >> >> the grav array: >> >> >> >> source = fullfile('Q:\geophys\Gz.grd') >> >> grav = ncread(source,'z') >> >> Hy = hilbert(grav); // write Hy variable to new file >> >> >> >> I am having problems with writing out the processed data e.g write a >> >> new grid (Gz_Hy.grd) with the Hilbert transform solution >> >> >> >> filename = fullfile('Q:\geophys\Gz_Hy.grd') >> >> ncwrite(filename, 'Hy') // does not work >> >> >> >> Error return: >> >> >> >> ncwrite(filename, 'Hy') >> >> !--error 77 >> >> ncwrite: Wrong number of input argument(s): 3 to 5 expected. >> >> at line 5 of exec file called by : >> >> exec('Q:\geophys\Lester\SCILAB_work\netcdf1.sce', -1) >> >> >> >> Any advice would be appreciated. >> >> >> >> Thanks >> >> Lester >> >> _______________________________________________ >> >> users mailing list >> >> users at lists.scilab.org >> >> http://lists.scilab.org/mailman/listinfo/users >> > >> > >> > >> > >> > -- >> > Thanks and Regards >> > Harpreet Singh >> > >> > _______________________________________________ >> > users mailing list >> > users at lists.scilab.org >> > http://lists.scilab.org/mailman/listinfo/users >> > >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> http://lists.scilab.org/mailman/listinfo/users > > > > > -- > Thanks and Regards > Harpreet Singh > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > From Serge.Steer at inria.fr Fri Feb 5 13:24:12 2016 From: Serge.Steer at inria.fr (Serge Steer) Date: Fri, 5 Feb 2016 13:24:12 +0100 Subject: [Scilab-users] Hilbert transform query In-Reply-To: References: Message-ID: <56B4946C.2090202@inria.fr> Le 05/02/2016 10:56, Lester Anderson a ?crit : > Hello > > A quick query. How would one define the Hilbert transform of a grid > for X and Y directions; looking for two solutions Hx and Hy (for the > real values). Can you explain more precisely what you expect? Do you want to apply Hilbert transform to each column and to each rows or to perform a 2D Hilbert transform? Serge > > Thanks > Lester > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > From arctica1963 at gmail.com Fri Feb 5 13:52:50 2016 From: arctica1963 at gmail.com (Lester Anderson) Date: Fri, 5 Feb 2016 12:52:50 +0000 Subject: [Scilab-users] Hilbert transform query In-Reply-To: <56B4946C.2090202@inria.fr> References: <56B4946C.2090202@inria.fr> Message-ID: Hi Serge, I am working with grid data, so looking for the 2D Hilbert, the results I think should appear similar to doing a directional derivative, where X highlights features with N-S trends and E-W for Y. Lester On 5 February 2016 at 12:24, Serge Steer wrote: > Le 05/02/2016 10:56, Lester Anderson a ?crit : >> >> Hello >> >> A quick query. How would one define the Hilbert transform of a grid >> for X and Y directions; looking for two solutions Hx and Hy (for the >> real values). > > Can you explain more precisely what you expect? > Do you want to apply Hilbert transform to each column and to each rows or > to perform a 2D Hilbert transform? > Serge >> >> >> Thanks >> Lester >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> http://lists.scilab.org/mailman/listinfo/users >> > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From simon.marchetto at scilab-enterprises.com Fri Feb 5 14:03:39 2016 From: simon.marchetto at scilab-enterprises.com (Simon Marchetto) Date: Fri, 5 Feb 2016 14:03:39 +0100 Subject: [Scilab-users] Using Scinetcdf module In-Reply-To: References: Message-ID: <56B49DAB.1040107@scilab-enterprises.com> The error message means that the variable is already created, you cannot create it twice. Delete the file, and try again. An example of grid writing, taken from the ncwrite() help page: nccreate(filename, 'mat', 'Dimensions', list('r', 3, 'c', 4)); ncwrite(filename, 'mat', [1 2 3 4; 5 6 7 8; 9 10 11 12]); And to read it: ncread(filename, 'mat'); Simon Le 05/02/2016 12:26, Lester Anderson a ?crit : > Hi Simon, > > Hy is a matrix and the input grid used has dimensions of 601 x 601 > (x,y). Reading the data in is fine and the matrix is as expected in > the variable browser. > > grav = ncread(source,'z') is all fine with a 601 x 601 matrix > > Create variable Hilb_Hy: > > nccreate(filename,'Hilb_Hy','Dimensions',list('r',601,'c',601)) > !--error 999 > nccreate: nc_def_var() returned the error -42: NetCDF: String match to > name in use. > > Do you have an example grid to test the read and write function. > > Would it help to send you a copy of the grid file? > > Thanks > > On 5 February 2016 at 10:46, Harpreet Singh Rathore > wrote: >> Hey >> >> You have not created the variable in the file. First you have to create a >> variable in the following file using the command nccreate(filename, >> 'Hilb_Hy', 'Dimensions', list('r', no_row, 'c', no_column); after that you >> can pass the ncwrite command and you have to pass like this >> ncwrite(filename, 'Hilb_Hy',Hy) as Hy is a matrix. >> >> Regards >> Harpreet Singh >> >> On Fri, Feb 5, 2016 at 4:01 PM, Lester Anderson >> wrote: >>> Hello Harpreet, >>> >>> I altered the code a bit but still get a problem >>> >>> Hy = hilbert(grav); >>> filename = fullfile('Q:\geophys\Gz_Hy.grd') // set output filename >>> // ncwrite(filename, varname, vardata, [start, [stride]]) >>> ncwrite(filename, 'Hilb_Hy','Hy') // write variable Hilb_Hy with data from >>> Hy >>> >>> Error message: >>> >>> ncwrite(filename, 'Hilb_Hy','Hy') // write variable Hilb_Hy with data from >>> Hy >>> !--error 999 >>> ncwrite: nc_inq_varid() returned the error -49: NetCDF: Variable not >>> found. >>> at line 6 of exec file called by : >>> exec('Q:\geophys\Lester\SCILAB_work\netcdf1.sce', -1) >>> >>> In this case I want to define a variable name Hilb_Hy (although can >>> use any name really) in the netCDF file and write the output of the >>> Hilbert (Hy) transform. >>> >>> Cannot see the solution >>> >>> >>> >>> On 5 February 2016 at 10:15, Harpreet Singh Rathore >>> wrote: >>>> Dear Lester, >>>> >>>> As I can see the error is saying minimum 3 inputs are required. And >>>> after >>>> going through the help of the following function, you also have to pass >>>> the >>>> value which you have to store in the 'Hy'. You can go through the help >>>> files >>>> of ncwrite by typing help ncwrite in the console. >>>> >>>> Regards >>>> Harpreet >>>> >>>> On Fri, Feb 5, 2016 at 3:18 PM, Lester Anderson >>>> wrote: >>>>> Hello all >>>>> >>>>> I am looking to use the sciNetCDF module to work with GMT grid files >>>>> but have some issues. >>>>> >>>>> Reading a GMT grid is not a problem as far as I can tell, so the >>>>> following does read the file (and z variable), storing the values in >>>>> the grav array: >>>>> >>>>> source = fullfile('Q:\geophys\Gz.grd') >>>>> grav = ncread(source,'z') >>>>> Hy = hilbert(grav); // write Hy variable to new file >>>>> >>>>> I am having problems with writing out the processed data e.g write a >>>>> new grid (Gz_Hy.grd) with the Hilbert transform solution >>>>> >>>>> filename = fullfile('Q:\geophys\Gz_Hy.grd') >>>>> ncwrite(filename, 'Hy') // does not work >>>>> >>>>> Error return: >>>>> >>>>> ncwrite(filename, 'Hy') >>>>> !--error 77 >>>>> ncwrite: Wrong number of input argument(s): 3 to 5 expected. >>>>> at line 5 of exec file called by : >>>>> exec('Q:\geophys\Lester\SCILAB_work\netcdf1.sce', -1) >>>>> >>>>> Any advice would be appreciated. >>>>> >>>>> Thanks >>>>> Lester >>>>> _______________________________________________ >>>>> users mailing list >>>>> users at lists.scilab.org >>>>> http://lists.scilab.org/mailman/listinfo/users >>>> >>>> >>>> >>>> -- >>>> Thanks and Regards >>>> Harpreet Singh >>>> >>>> _______________________________________________ >>>> users mailing list >>>> users at lists.scilab.org >>>> http://lists.scilab.org/mailman/listinfo/users >>>> >>> _______________________________________________ >>> users mailing list >>> users at lists.scilab.org >>> http://lists.scilab.org/mailman/listinfo/users >> >> >> >> -- >> Thanks and Regards >> Harpreet Singh >> >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> http://lists.scilab.org/mailman/listinfo/users >> > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From arctica1963 at gmail.com Fri Feb 5 14:48:54 2016 From: arctica1963 at gmail.com (Lester Anderson) Date: Fri, 5 Feb 2016 13:48:54 +0000 Subject: [Scilab-users] Using Scinetcdf module In-Reply-To: <56B49DAB.1040107@scilab-enterprises.com> References: <56B49DAB.1040107@scilab-enterprises.com> Message-ID: Hi Simon, Sorted it now: source = fullfile('Q:\geophys\Gz.grd') grav = ncread(source,'z') // read the gravity data from GMT grid Hy = hilbert(grav); // do some math on the grid filename = fullfile('Q:\geophys\Gz_Hy_testprog.grd') nccreate(filename,'Hilb_Hy','Dimensions',list('r',601,'c',601)) // define variable Hilb_Hy and grid dimensions ncwrite(filename, 'Hilb_Hy',Hy) // write variable Hilb_Hy with data from Hy One query is how to make it store the Longitude and Latitude values rather than a cartesian? >From GMT the grdinfo results for the original grid are: grdinfo gz.grd gz.grd: Title: Grid computed inside Mirone gz.grd: Command: gz.grd: Remark: File written from Matlab gz.grd: Gridline node registration used [Geographic grid] gz.grd: Grid file format: nf = GMT netCDF format (32-bit float), COARDS, CF-1.5 gz.grd: x_min: 5.00833333333 x_max: 15.0083333333 x_inc: 0.0166666666667 name: longitude [degrees_east] nx: 601 gz.grd: y_min: -5.99166666667 y_max: 4.00833333333 y_inc: 0.0166666666667 name: latitude [degrees_north] ny: 601 gz.grd: z_min: -48.2753601074 z_max: 143.910430908 name: z [unknown] gz.grd: scale_factor: 1 add_offset: 0 gz.grd: format: classic The computed grid results from Scilab give: grdinfo Gz_Hy_testprog5.grd Gz_Hy_testprog5.grd: Title: Gz_Hy_testprog5.grd: Command: Gz_Hy_testprog5.grd: Remark: Gz_Hy_testprog5.grd: Gridline node registration used [Cartesian grid] Gz_Hy_testprog5.grd: Grid file format: nd = GMT netCDF format (64-bit float), COARDS, CF-1.5 Gz_Hy_testprog5.grd: x_min: 0 x_max: 600 x_inc: 1 name: nx: 601 Gz_Hy_testprog5.grd: y_min: 0 y_max: 600 y_inc: 1 name: ny: 601 Gz_Hy_testprog5.grd: z_min: NaN z_max: NaN name: Hilb_Hy Gz_Hy_testprog5.grd: scale_factor: 1 add_offset: 0 Gz_Hy_testprog5.grd: format: netCDF-4 chunk_size: 0,0 shuffle: off deflation_level: 0 Do you have to assign variables for the X, Y and Z. Thanks On 5 February 2016 at 13:03, Simon Marchetto wrote: > The error message means that the variable is already created, you cannot > create it twice. > > Delete the file, and try again. > > > An example of grid writing, taken from the ncwrite() help page: > > nccreate(filename, 'mat', 'Dimensions', list('r', 3, 'c', 4)); > ncwrite(filename, 'mat', [1 2 3 4; 5 6 7 8; 9 10 11 12]); > > And to read it: > > ncread(filename, 'mat'); > > Simon > > > Le 05/02/2016 12:26, Lester Anderson a ?crit : >> >> Hi Simon, >> >> Hy is a matrix and the input grid used has dimensions of 601 x 601 >> (x,y). Reading the data in is fine and the matrix is as expected in >> the variable browser. >> >> grav = ncread(source,'z') is all fine with a 601 x 601 matrix >> >> Create variable Hilb_Hy: >> >> nccreate(filename,'Hilb_Hy','Dimensions',list('r',601,'c',601)) >> !--error >> 999 >> nccreate: nc_def_var() returned the error -42: NetCDF: String match to >> name in use. >> >> Do you have an example grid to test the read and write function. >> >> Would it help to send you a copy of the grid file? >> >> Thanks >> >> On 5 February 2016 at 10:46, Harpreet Singh Rathore >> wrote: >>> >>> Hey >>> >>> You have not created the variable in the file. First you have to create a >>> variable in the following file using the command nccreate(filename, >>> 'Hilb_Hy', 'Dimensions', list('r', no_row, 'c', no_column); after that >>> you >>> can pass the ncwrite command and you have to pass like this >>> ncwrite(filename, 'Hilb_Hy',Hy) as Hy is a matrix. >>> >>> Regards >>> Harpreet Singh >>> >>> On Fri, Feb 5, 2016 at 4:01 PM, Lester Anderson >>> wrote: >>>> >>>> Hello Harpreet, >>>> >>>> I altered the code a bit but still get a problem >>>> >>>> Hy = hilbert(grav); >>>> filename = fullfile('Q:\geophys\Gz_Hy.grd') // set output filename >>>> // ncwrite(filename, varname, vardata, [start, [stride]]) >>>> ncwrite(filename, 'Hilb_Hy','Hy') // write variable Hilb_Hy with data >>>> from >>>> Hy >>>> >>>> Error message: >>>> >>>> ncwrite(filename, 'Hilb_Hy','Hy') // write variable Hilb_Hy with data >>>> from >>>> Hy >>>> !--error 999 >>>> ncwrite: nc_inq_varid() returned the error -49: NetCDF: Variable not >>>> found. >>>> at line 6 of exec file called by : >>>> exec('Q:\geophys\Lester\SCILAB_work\netcdf1.sce', -1) >>>> >>>> In this case I want to define a variable name Hilb_Hy (although can >>>> use any name really) in the netCDF file and write the output of the >>>> Hilbert (Hy) transform. >>>> >>>> Cannot see the solution >>>> >>>> >>>> >>>> On 5 February 2016 at 10:15, Harpreet Singh Rathore >>>> wrote: >>>>> >>>>> Dear Lester, >>>>> >>>>> As I can see the error is saying minimum 3 inputs are required. And >>>>> after >>>>> going through the help of the following function, you also have to pass >>>>> the >>>>> value which you have to store in the 'Hy'. You can go through the help >>>>> files >>>>> of ncwrite by typing help ncwrite in the console. >>>>> >>>>> Regards >>>>> Harpreet >>>>> >>>>> On Fri, Feb 5, 2016 at 3:18 PM, Lester Anderson >>>>> wrote: >>>>>> >>>>>> Hello all >>>>>> >>>>>> I am looking to use the sciNetCDF module to work with GMT grid files >>>>>> but have some issues. >>>>>> >>>>>> Reading a GMT grid is not a problem as far as I can tell, so the >>>>>> following does read the file (and z variable), storing the values in >>>>>> the grav array: >>>>>> >>>>>> source = fullfile('Q:\geophys\Gz.grd') >>>>>> grav = ncread(source,'z') >>>>>> Hy = hilbert(grav); // write Hy variable to new file >>>>>> >>>>>> I am having problems with writing out the processed data e.g write a >>>>>> new grid (Gz_Hy.grd) with the Hilbert transform solution >>>>>> >>>>>> filename = fullfile('Q:\geophys\Gz_Hy.grd') >>>>>> ncwrite(filename, 'Hy') // does not work >>>>>> >>>>>> Error return: >>>>>> >>>>>> ncwrite(filename, 'Hy') >>>>>> !--error 77 >>>>>> ncwrite: Wrong number of input argument(s): 3 to 5 expected. >>>>>> at line 5 of exec file called by : >>>>>> exec('Q:\geophys\Lester\SCILAB_work\netcdf1.sce', -1) >>>>>> >>>>>> Any advice would be appreciated. >>>>>> >>>>>> Thanks >>>>>> Lester >>>>>> _______________________________________________ >>>>>> users mailing list >>>>>> users at lists.scilab.org >>>>>> http://lists.scilab.org/mailman/listinfo/users >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Thanks and Regards >>>>> Harpreet Singh >>>>> >>>>> _______________________________________________ >>>>> users mailing list >>>>> users at lists.scilab.org >>>>> http://lists.scilab.org/mailman/listinfo/users >>>>> >>>> _______________________________________________ >>>> users mailing list >>>> users at lists.scilab.org >>>> http://lists.scilab.org/mailman/listinfo/users >>> >>> >>> >>> >>> -- >>> Thanks and Regards >>> Harpreet Singh >>> >>> _______________________________________________ >>> users mailing list >>> users at lists.scilab.org >>> http://lists.scilab.org/mailman/listinfo/users >>> >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> http://lists.scilab.org/mailman/listinfo/users > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From david.cheze at cea.fr Fri Feb 5 15:30:52 2016 From: david.cheze at cea.fr (=?UTF-8?Q?David_Ch=C3=A8ze?=) Date: Fri, 5 Feb 2016 07:30:52 -0700 (MST) Subject: [Scilab-users] issue providing command to powershell In-Reply-To: <56B23A73.8090608@free.fr> References: <1454505686276-4033376.post@n3.nabble.com> <56B22113.7090805@free.fr> <56B227C9.8020504@free.fr> <1454519563086-4033385.post@n3.nabble.com> <1454520430057-4033387.post@n3.nabble.com> <56B23A73.8090608@free.fr> Message-ID: <1454682652763-4033401.post@n3.nabble.com> Hi all, finally I got the solution for passing path comprising blanck character as string to the powershell() function from scilab: two simple quote ' should be used instead of n times double quotes. NB: powershell console should receive the path string encompassed with simple quote: to generate this correct string from scilab you have to use a second simple quote. The scilab script below performed the creation of a new file encoded in UTF-8 from my original file encoded in UTF16 LE: pscmd='get-content -Path ''C:\Users\dc227480\Documents\temp\Donn?es IAQ SENSE 29_01_2016 10_45_00 1.dat.csv'' | out-file ''C:\Users\dc227480\Documents\temp\Donn?es IAQ SENSE 29_01_2016 10_45_00 1.UTF-8.csv'' -encoding utf8' powershell(pscmd) David -- View this message in context: http://mailinglists.scilab.org/issue-providing-command-to-powershell-tp4033376p4033401.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From tim at wescottdesign.com Fri Feb 5 20:02:30 2016 From: tim at wescottdesign.com (Tim Wescott) Date: Fri, 05 Feb 2016 11:02:30 -0800 Subject: [Scilab-users] Hilbert transform query In-Reply-To: References: <56B4946C.2090202@inria.fr> Message-ID: <1454698950.17554.86.camel@Servo> Any time you go from 1D to 2D you suddenly end up with more than one way to do things, so I'm pretty sure that "how would one..." should really be worded "how would YOU...", or perhaps "how would someone in this field...". It sounds like you want to keep things rectilinear, so it may be best to just apply the transform column-by-column and row-by-row. That SHOULD work, and if you do it as matrix operations it should be pretty fast in Scilab. On Fri, 2016-02-05 at 12:52 +0000, Lester Anderson wrote: > Hi Serge, > > I am working with grid data, so looking for the 2D Hilbert, the > results I think should appear similar to doing a directional > derivative, where X highlights features with N-S trends and E-W for Y. > > Lester > > > > On 5 February 2016 at 12:24, Serge Steer wrote: > > Le 05/02/2016 10:56, Lester Anderson a ?crit : > >> > >> Hello > >> > >> A quick query. How would one define the Hilbert transform of a grid > >> for X and Y directions; looking for two solutions Hx and Hy (for the > >> real values). > > > > Can you explain more precisely what you expect? > > Do you want to apply Hilbert transform to each column and to each rows or > > to perform a 2D Hilbert transform? > > Serge > >> > >> > >> Thanks > >> Lester > >> _______________________________________________ > >> users mailing list > >> users at lists.scilab.org > >> http://lists.scilab.org/mailman/listinfo/users > >> > > > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/users > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -- Tim Wescott www.wescottdesign.com Control & Communications systems, circuit & software design. Phone: 503.631.7815 Cell: 503.349.8432 From antoine.monmayrant at laas.fr Mon Feb 8 11:47:45 2016 From: antoine.monmayrant at laas.fr (antoine.monmayrant at laas.fr) Date: Mon, 8 Feb 2016 11:47:45 +0100 Subject: [Scilab-users] Put an image as the background of an axis Message-ID: <56B87251.7040903@laas.fr> Hi everyone, I just failed at placing an image behind a plot. I thought that would be easy: - create a figure - create an image uicontrol - create an axis - plot in the axis - set axis.filled="off" Apparently I was wrong. I did not find a way to overlap a plot with transparent background over my image. It seems that the image is always above the plot no matter what order the uicontrol/axes where created. I also tried to put both of them inside the same frame, but I did not work either. Any idea? From Fabrice.Le_fessant at inria.fr Mon Feb 8 17:42:39 2016 From: Fabrice.Le_fessant at inria.fr (Fabrice Le Fessant) Date: Mon, 08 Feb 2016 16:42:39 +0000 Subject: [Scilab-users] online interpreter for Scilab Message-ID: Hi, During the FUI project Richelieu that just ended in October 2015, Inria and OCamlPro developed a small Scilab interpreter in OCaml (its main purpose was to test the parser of Scilint, a style-checker for Scilab also developed during the project). A demonstrator of this interpreter is available on the following page: http://sciweb.ocamlpro.com/ Sciweb can be used to write and execute simple examples of Scilab code directly inside the browser, without the need to install Scilab on the computer. The set of available primitives is of course incomplete, and much slower (all computations are done in Javascript, to which OCaml is compiled). Nevertheless, it can be interesting in specific contextes, in particular education, where computations are usually simpler and shorter, with the need for fewer primitivies. Several plotting functions are available too. The OCaml code is open-source and available on Github: http://github.com/OCamlPro/scilint/ and it is thus possible to add new primitives quite easily. All feedback is welcome ! --Fabrice, Inria et OCamlPro -------------- next part -------------- An HTML attachment was scrubbed... URL: From j-lan at online.no Mon Feb 8 17:49:08 2016 From: j-lan at online.no (=?UTF-8?Q?Jan_=c3=85ge_Langeland?=) Date: Mon, 8 Feb 2016 17:49:08 +0100 Subject: [Scilab-users] Put an image as the background of an axis In-Reply-To: <56B87251.7040903@laas.fr> References: <56B87251.7040903@laas.fr> Message-ID: <56B8C704.3090106@online.no> On 08.02.2016 11:47, antoine.monmayrant at laas.fr wrote: > Hi everyone, > > I just failed at placing an image behind a plot. > I thought that would be easy: > - create a figure > - create an image uicontrol > - create an axis > - plot in the axis > - set axis.filled="off" > > Apparently I was wrong. > I did not find a way to overlap a plot with transparent background > over my image. > It seems that the image is always above the plot no matter what order > the uicontrol/axes where created. > I also tried to put both of them inside the same frame, but I did not > work either. > > Any idea? > > ShowImage(im,'J2'); b=newaxes(); b.filled = "off"; plot(a) J? > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From arctica1963 at gmail.com Mon Feb 8 17:51:51 2016 From: arctica1963 at gmail.com (Lester Anderson) Date: Mon, 8 Feb 2016 16:51:51 +0000 Subject: [Scilab-users] Hilbert transform query In-Reply-To: <1454698950.17554.86.camel@Servo> References: <56B4946C.2090202@inria.fr> <1454698950.17554.86.camel@Servo> Message-ID: So what would the syntax be for doing a column run Hilbert, and row run Hilbert? It does sound like the suggesting would do what I think it is meant to. X = hilbert(data) // does compute pretty fast! At the moment I have used the netCDF code to read in GMT (net CDF) data, which is a 601 x 601 matrix (x,y). So in order to do the column and row method is it necessary to transpose the matrix, e.g. x = x' ? Thanks for any pointers On 5 February 2016 at 19:02, Tim Wescott wrote: > Any time you go from 1D to 2D you suddenly end up with more than one way > to do things, so I'm pretty sure that "how would one..." should really > be worded "how would YOU...", or perhaps "how would someone in this > field...". > > It sounds like you want to keep things rectilinear, so it may be best to > just apply the transform column-by-column and row-by-row. That SHOULD > work, and if you do it as matrix operations it should be pretty fast in > Scilab. > > On Fri, 2016-02-05 at 12:52 +0000, Lester Anderson wrote: >> Hi Serge, >> >> I am working with grid data, so looking for the 2D Hilbert, the >> results I think should appear similar to doing a directional >> derivative, where X highlights features with N-S trends and E-W for Y. >> >> Lester >> >> >> >> On 5 February 2016 at 12:24, Serge Steer wrote: >> > Le 05/02/2016 10:56, Lester Anderson a ?crit : >> >> >> >> Hello >> >> >> >> A quick query. How would one define the Hilbert transform of a grid >> >> for X and Y directions; looking for two solutions Hx and Hy (for the >> >> real values). >> > >> > Can you explain more precisely what you expect? >> > Do you want to apply Hilbert transform to each column and to each rows or >> > to perform a 2D Hilbert transform? >> > Serge >> >> >> >> >> >> Thanks >> >> Lester >> >> _______________________________________________ >> >> users mailing list >> >> users at lists.scilab.org >> >> http://lists.scilab.org/mailman/listinfo/users >> >> >> > >> > _______________________________________________ >> > users mailing list >> > users at lists.scilab.org >> > http://lists.scilab.org/mailman/listinfo/users >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> http://lists.scilab.org/mailman/listinfo/users > > -- > > Tim Wescott > www.wescottdesign.com > Control & Communications systems, circuit & software design. > Phone: 503.631.7815 > Cell: 503.349.8432 > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From p.muehlmann at gmail.com Tue Feb 9 00:04:17 2016 From: p.muehlmann at gmail.com (=?UTF-8?Q?Philipp_M=C3=BChlmann?=) Date: Tue, 9 Feb 2016 00:04:17 +0100 Subject: [Scilab-users] Put an image as the background of an axis In-Reply-To: <56B8C704.3090106@online.no> References: <56B87251.7040903@laas.fr> <56B8C704.3090106@online.no> Message-ID: Well, as I understand you want to plot a function over an background image. In the case the image pixel number fits the X-Y range of your graph it's rather simple. img = ReadImage(IPD_PATH + 'demos\teaset.png'); rows = size(img,'r');cols = size(img,'c'); img(rows,1,:) = (0); // changing left lower image corner for checking purpose // change all 3 colour channels to get a black pixel ShowColorImage(img,''); a = gca();a.axes_visible = ["on","on","off"];x = linspace(1,600,600);y = 1/2*(x);plot(x,y,'-');a.data_bounds = [0,0;cols,rows]; Two tricky things though: 1st: image coordinates (center of pixel) start at "1", hence there is a gap of 0.5 between image borders and the axes 2nd: it might become tricky if you want to have negative values on the axis. Probably there is a way to shift the image to other position within the coordinate system? So....not sure if this helps your purpose. You could also switch "ON" / "OFF" the background image by access the children of the figure, such as: IMGPlot = a.Children(2); // children(2) is the background in this caseIMGPlot.visible = 'off'; A complete other way would be to combine two images of same size. Say...background image is img1. your plot = img2. Plot the graph and save the figure as a temporary image. load img1 load temporary image If size (img1) == size(img2)....You could use SIVP module to linear combine two images: img_gray = double(RGB2Gray(img));img2 = zeros(rows, cols) + 255;img2(rows/2,:) = 0;img3 = imlincomb( 0.5, img_gray, 0.4, img2) // the values here define some kind of transparency.figure(); ShowImage(img3,''); Best regards, Philipp 2016-02-08 17:49 GMT+01:00 Jan ?ge Langeland : > > > On 08.02.2016 11:47, antoine.monmayrant at laas.fr wrote: > > Hi everyone, > > I just failed at placing an image behind a plot. > I thought that would be easy: > - create a figure > - create an image uicontrol > - create an axis > - plot in the axis > - set axis.filled="off" > > Apparently I was wrong. > I did not find a way to overlap a plot with transparent background over my > image. > It seems that the image is always above the plot no matter what order the > uicontrol/axes where created. > I also tried to put both of them inside the same frame, but I did not work > either. > > Any idea? > > > > ShowImage(im,'J2'); > > b=newaxes(); > b.filled = "off"; > plot(a) > > J? > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > > -- There we have the salad. -------------- next part -------------- An HTML attachment was scrubbed... URL: From amonmayr at laas.fr Tue Feb 9 08:01:02 2016 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Tue, 09 Feb 2016 08:01:02 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ICBQdXQgYW4gaW1hZ2UgYXMg?= =?utf-8?q?the_background_of_an_axis?= In-Reply-To: <56B8C704.3090106@online.no> Message-ID: <10c1-56b98e80-45-6bea2400@25978922> Le Lundi 8 F?vrier 2016 17:49 CET, Jan ?ge Langeland a ?crit: > > > On 08.02.2016 11:47, antoine.monmayrant at laas.fr wrote: > > Hi everyone, > > > > I just failed at placing an image behind a plot. > > I thought that would be easy: > > - create a figure > > - create an image uicontrol > > - create an axis > > - plot in the axis > > - set axis.filled="off" > > > > Apparently I was wrong. > > I did not find a way to overlap a plot with transparent background > > over my image. > > It seems that the image is always above the plot no matter what order > > the uicontrol/axes where created. > > I also tried to put both of them inside the same frame, but I did not > > work either. > > > > Any idea? > > > > > > ShowImage(im,'J2'); Well, ShowImage comes from an atom module and is not part of Scilab. Saddly, none of the image processing toolboxes work on my machine. I even filled some bug reports on forge, but it did not trigger any reaction from the developpers. Thanks anyway for your proposition, Antoine > > b=newaxes(); b.filled = "off"; plot(a) > > J? > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/users > > > From amonmayr at laas.fr Tue Feb 9 08:04:09 2016 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Tue, 09 Feb 2016 08:04:09 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ICBQdXQgYW4gaW1hZ2UgYXMg?= =?utf-8?q?the_background_of_an_axis?= In-Reply-To: Message-ID: <133b-56b98f80-1f-51a2c000@131108136> Le Mardi 9 F?vrier 2016 00:04 CET, Philipp M?hlmann a ?crit: > Well, as I understand you want to plot a function over an background image. > > In the case the image pixel number fits the X-Y range of your graph it's > rather simple. Well, it is, unless IPD does not work on your system, which is my case! None, absolutely none of the image processing toolboxes work on my machine. And it's not only my machine, it's the case for most of the machines we have at work. So I cannot rely on an image processing toolbox to achieve what I want and I have to rely on base functions. Thanks anyway for you help, Antoine > > img = ReadImage(IPD_PATH + 'demos\teaset.png'); > rows = size(img,'r');cols = size(img,'c'); > img(rows,1,:) = (0); // changing left lower image corner for > checking purpose > // change all 3 colour > channels to get a black pixel > ShowColorImage(img,''); > a = gca();a.axes_visible = ["on","on","off"];x = linspace(1,600,600);y > = 1/2*(x);plot(x,y,'-');a.data_bounds = [0,0;cols,rows]; > > Two tricky things though: > > 1st: image coordinates (center of pixel) start at "1", hence there is a gap > of 0.5 between image borders and the axes > > 2nd: it might become tricky if you want to have negative values on the axis. > > Probably there is a way to shift the image to other position within the > coordinate system? > > > So....not sure if this helps your purpose. > > You could also switch "ON" / "OFF" the background image by access the > children of the figure, such as: > > IMGPlot = a.Children(2); // children(2) is the background in this > caseIMGPlot.visible = 'off'; > > > A complete other way would be to combine two images of same size. > Say...background image is img1. > > your plot = img2. > Plot the graph and save the figure as a temporary image. > > load img1 > load temporary image > > If size (img1) == size(img2)....You could use SIVP module to linear combine > two images: > > img_gray = double(RGB2Gray(img));img2 = zeros(rows, cols) + > 255;img2(rows/2,:) = 0;img3 = imlincomb( 0.5, img_gray, 0.4, img2) > // the values here define some kind of transparency.figure(); > ShowImage(img3,''); > > > > Best regards, > Philipp > > > > > 2016-02-08 17:49 GMT+01:00 Jan ?ge Langeland : > > > > > > > On 08.02.2016 11:47, antoine.monmayrant at laas.fr wrote: > > > > Hi everyone, > > > > I just failed at placing an image behind a plot. > > I thought that would be easy: > > - create a figure > > - create an image uicontrol > > - create an axis > > - plot in the axis > > - set axis.filled="off" > > > > Apparently I was wrong. > > I did not find a way to overlap a plot with transparent background over my > > image. > > It seems that the image is always above the plot no matter what order the > > uicontrol/axes where created. > > I also tried to put both of them inside the same frame, but I did not work > > either. > > > > Any idea? > > > > > > > > ShowImage(im,'J2'); > > > > b=newaxes(); > > b.filled = "off"; > > plot(a) > > > > J? > > > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/users > > > > > > > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/users > > > > > > > -- > There we have the salad. From p.muehlmann at gmail.com Tue Feb 9 08:34:23 2016 From: p.muehlmann at gmail.com (=?UTF-8?Q?Philipp_M=C3=BChlmann?=) Date: Tue, 9 Feb 2016 08:34:23 +0100 Subject: [Scilab-users] ?==?utf-8?q? Put an image as the background of an axis In-Reply-To: <133b-56b98f80-1f-51a2c000@131108136> References: <133b-56b98f80-1f-51a2c000@131108136> Message-ID: Well, the base function behind "ShowImage" is "Matplot". You can use a search engine of your choice to find ShowImage.sci. "ShowColorImage" than is using "ShowImage" to create a colored Image. Hope that helps, Philipp 2016-02-09 8:04 GMT+01:00 Antoine Monmayrant : > > Le Mardi 9 F?vrier 2016 00:04 CET, Philipp M?hlmann > a ?crit: > > > Well, as I understand you want to plot a function over an background > image. > > > > In the case the image pixel number fits the X-Y range of your graph it's > > rather simple. > > Well, it is, unless IPD does not work on your system, which is my case! > None, absolutely none of the image processing toolboxes work on my machine. > And it's not only my machine, it's the case for most of the machines we > have at work. > So I cannot rely on an image processing toolbox to achieve what I want and > I have to rely on base functions. > > Thanks anyway for you help, > > Antoine > > > > > img = ReadImage(IPD_PATH + 'demos\teaset.png'); > > rows = size(img,'r');cols = size(img,'c'); > > img(rows,1,:) = (0); // changing left lower image corner for > > checking purpose > > // change all 3 colour > > channels to get a black pixel > > ShowColorImage(img,''); > > a = gca();a.axes_visible = ["on","on","off"];x = linspace(1,600,600);y > > = 1/2*(x);plot(x,y,'-');a.data_bounds = [0,0;cols,rows]; > > > > Two tricky things though: > > > > 1st: image coordinates (center of pixel) start at "1", hence there is a > gap > > of 0.5 between image borders and the axes > > > > 2nd: it might become tricky if you want to have negative values on the > axis. > > > > Probably there is a way to shift the image to other position within the > > coordinate system? > > > > > > So....not sure if this helps your purpose. > > > > You could also switch "ON" / "OFF" the background image by access the > > children of the figure, such as: > > > > IMGPlot = a.Children(2); // children(2) is the background in this > > caseIMGPlot.visible = 'off'; > > > > > > A complete other way would be to combine two images of same size. > > Say...background image is img1. > > > > your plot = img2. > > Plot the graph and save the figure as a temporary image. > > > > load img1 > > load temporary image > > > > If size (img1) == size(img2)....You could use SIVP module to linear > combine > > two images: > > > > img_gray = double(RGB2Gray(img));img2 = zeros(rows, cols) + > > 255;img2(rows/2,:) = 0;img3 = imlincomb( 0.5, img_gray, 0.4, img2) > > // the values here define some kind of transparency.figure(); > > ShowImage(img3,''); > > > > > > > > Best regards, > > Philipp > > > > > > > > > > 2016-02-08 17:49 GMT+01:00 Jan ?ge Langeland : > > > > > > > > > > > On 08.02.2016 11:47, antoine.monmayrant at laas.fr wrote: > > > > > > Hi everyone, > > > > > > I just failed at placing an image behind a plot. > > > I thought that would be easy: > > > - create a figure > > > - create an image uicontrol > > > - create an axis > > > - plot in the axis > > > - set axis.filled="off" > > > > > > Apparently I was wrong. > > > I did not find a way to overlap a plot with transparent background > over my > > > image. > > > It seems that the image is always above the plot no matter what order > the > > > uicontrol/axes where created. > > > I also tried to put both of them inside the same frame, but I did not > work > > > either. > > > > > > Any idea? > > > > > > > > > > > > ShowImage(im,'J2'); > > > > > > b=newaxes(); > > > b.filled = "off"; > > > plot(a) > > > > > > J? > > > > > > _______________________________________________ > > > users mailing list > > > users at lists.scilab.org > > > http://lists.scilab.org/mailman/listinfo/users > > > > > > > > > > > > _______________________________________________ > > > users mailing list > > > users at lists.scilab.org > > > http://lists.scilab.org/mailman/listinfo/users > > > > > > > > > > > > -- > > There we have the salad. > > > > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > -- There we have the salad. -------------- next part -------------- An HTML attachment was scrubbed... URL: From amonmayr at laas.fr Tue Feb 9 09:09:50 2016 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Tue, 09 Feb 2016 09:09:50 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ID89PT91dGYtOD9xPyA/PSBQ?= =?utf-8?q?ut_an_image_as_the_background_of_an_axi?= In-Reply-To: Message-ID: <2ff4-56b99f00-b-1c98bd80@91958063> Le Mardi 9 F?vrier 2016 08:34 CET, Philipp M?hlmann a ?crit: > Well, the base function behind "ShowImage" is "Matplot". I don't get what you mean. My point is the following: "ShowImage" is not defined in the scilab base install. You have to install an atom module to get access to it, in this case, it's IPD. Saddly, IPD is broken for both the fedora and ubuntu linux distributions we use at work so I cannot use it. IPD fails at detecting the installed opencv library installed. I tried to patch "IPD.start" to load the installed opencv libs, but it crashes scilab. Antoine > > You can use a search engine of your choice to find ShowImage.sci. > > "ShowColorImage" than is using "ShowImage" to create a colored Image. > > Hope that helps, > > Philipp > > > > > 2016-02-09 8:04 GMT+01:00 Antoine Monmayrant : > > > > > Le Mardi 9 F?vrier 2016 00:04 CET, Philipp M?hlmann > > a ?crit: > > > > > Well, as I understand you want to plot a function over an background > > image. > > > > > > In the case the image pixel number fits the X-Y range of your graph it's > > > rather simple. > > > > Well, it is, unless IPD does not work on your system, which is my case! > > None, absolutely none of the image processing toolboxes work on my machine. > > And it's not only my machine, it's the case for most of the machines we > > have at work. > > So I cannot rely on an image processing toolbox to achieve what I want and > > I have to rely on base functions. > > > > Thanks anyway for you help, > > > > Antoine > > > > > > > > img = ReadImage(IPD_PATH + 'demos\teaset.png'); > > > rows = size(img,'r');cols = size(img,'c'); > > > img(rows,1,:) = (0); // changing left lower image corner for > > > checking purpose > > > // change all 3 colour > > > channels to get a black pixel > > > ShowColorImage(img,''); > > > a = gca();a.axes_visible = ["on","on","off"];x = linspace(1,600,600);y > > > = 1/2*(x);plot(x,y,'-');a.data_bounds = [0,0;cols,rows]; > > > > > > Two tricky things though: > > > > > > 1st: image coordinates (center of pixel) start at "1", hence there is a > > gap > > > of 0.5 between image borders and the axes > > > > > > 2nd: it might become tricky if you want to have negative values on the > > axis. > > > > > > Probably there is a way to shift the image to other position within the > > > coordinate system? > > > > > > > > > So....not sure if this helps your purpose. > > > > > > You could also switch "ON" / "OFF" the background image by access the > > > children of the figure, such as: > > > > > > IMGPlot = a.Children(2); // children(2) is the background in this > > > caseIMGPlot.visible = 'off'; > > > > > > > > > A complete other way would be to combine two images of same size. > > > Say...background image is img1. > > > > > > your plot = img2. > > > Plot the graph and save the figure as a temporary image. > > > > > > load img1 > > > load temporary image > > > > > > If size (img1) == size(img2)....You could use SIVP module to linear > > combine > > > two images: > > > > > > img_gray = double(RGB2Gray(img));img2 = zeros(rows, cols) + > > > 255;img2(rows/2,:) = 0;img3 = imlincomb( 0.5, img_gray, 0.4, img2) > > > // the values here define some kind of transparency.figure(); > > > ShowImage(img3,''); > > > > > > > > > > > > Best regards, > > > Philipp > > > > > > > > > > > > > > > 2016-02-08 17:49 GMT+01:00 Jan ?ge Langeland : > > > > > > > > > > > > > > > On 08.02.2016 11:47, antoine.monmayrant at laas.fr wrote: > > > > > > > > Hi everyone, > > > > > > > > I just failed at placing an image behind a plot. > > > > I thought that would be easy: > > > > - create a figure > > > > - create an image uicontrol > > > > - create an axis > > > > - plot in the axis > > > > - set axis.filled="off" > > > > > > > > Apparently I was wrong. > > > > I did not find a way to overlap a plot with transparent background > > over my > > > > image. > > > > It seems that the image is always above the plot no matter what order > > the > > > > uicontrol/axes where created. > > > > I also tried to put both of them inside the same frame, but I did not > > work > > > > either. > > > > > > > > Any idea? > > > > > > > > > > > > > > > > ShowImage(im,'J2'); > > > > > > > > b=newaxes(); > > > > b.filled = "off"; > > > > plot(a) > > > > > > > > J? > > > > > > > > _______________________________________________ > > > > users mailing list > > > > users at lists.scilab.org > > > > http://lists.scilab.org/mailman/listinfo/users > > > > > > > > > > > > > > > > _______________________________________________ > > > > users mailing list > > > > users at lists.scilab.org > > > > http://lists.scilab.org/mailman/listinfo/users > > > > > > > > > > > > > > > > > -- > > > There we have the salad. > > > > > > > > > > > > > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/users > > > > > > -- > There we have the salad. From end48war at yahoo.fr Tue Feb 9 10:20:35 2016 From: end48war at yahoo.fr (azerty azerty) Date: Tue, 9 Feb 2016 09:20:35 +0000 (UTC) Subject: [Scilab-users] Xcos: Error when running a compiled superblock In-Reply-To: <1453802352.3014.4.camel@scilab-enterprises.com> References: <1453802352.3014.4.camel@scilab-enterprises.com> Message-ID: <1842713919.2251599.1455009635546.JavaMail.yahoo@mail.yahoo.com> Hello Cl?ment, Thank you for the tip. Indeed running the "loader.sce" and the "*.sci" file allowed me to reuse the model later.I will definitively look at the toolbox thing too, as I want to distribute my model to other people. Regards,Benoit Le Mardi 26 janvier 2016 11h01, Cl?ment David a ?crit : Hello?Benoit, During code generation, scilab will generate both the C file of the superblock and the equivalent block interface function (a scilab macro). To re-use it later, you have to link the library (to load the simulation function) and the execute the interface function file (to load the block). To generalize your approach I strongly suggest you to ship both the Xcos schema and the C, macro files as an external module (aka toolbox). This way you will only need to build the block once on your side and distribute the module to your users. Regards, -- Cl?ment Le vendredi 22 janvier 2016 ? 03:26 -0700, ENd48 a ?crit?: > Good morning, > > I'm trying to compile a superblock but I've got problem running the > simulation afterwards. > Here is what I do: > ?* I create a very simple diagram (constant value fed into the two ports of > a sum block then a AFFICH_m block with an event clock) > ?* I convert the sum block into a superblock > ?* At this stage the diagram works just well > ?* I then compile the superblock (right click -> compile) > ?* The compilation works and the diagram is still working > ?* Now if I close Scilab and reopen it, I run the "loader.sce" file that has > been generated during the compilation (I get a "Link done" message) > ?* If I try to run the diagram, I got an error message like this one: > ??????????o=Untitled__111506_c('set',o) > ????????????????????????????????????????!--error 4? > ??????????Undefined variable: Untitled__111506_c > ? > ? > ??????????do_eval: Error while calling block Untitled__111506_c > [uid='-16a0de62:15268d37? > ???????????????216:-7fb8']: invalid parameter (ier=4.000000, > %scicos_prob=%F).??????????? > > Does anybody know about such an error? What could be the solution to this > problem? > > Thanks in advance for your help. > > Regards, > Benoit > > > > -- > View this message in context: http://mailinglists.scilab.org/Xcos-Error-when-running-a-compiled-su > perblock-tp4033315.html > Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users _______________________________________________ users mailing list users at lists.scilab.org http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From j-lan at online.no Tue Feb 9 10:26:01 2016 From: j-lan at online.no (=?UTF-8?Q?Jan_=c3=85ge_Langeland?=) Date: Tue, 9 Feb 2016 10:26:01 +0100 Subject: [Scilab-users] ?= Put an image as the background of an axi In-Reply-To: <2ff4-56b99f00-b-1c98bd80@91958063> References: <2ff4-56b99f00-b-1c98bd80@91958063> Message-ID: <56B9B0A9.3010602@online.no> On 09.02.2016 09:09, Antoine Monmayrant wrote: > > Le Mardi 9 F?vrier 2016 08:34 CET, Philipp M?hlmann a ?crit: > >> Well, the base function behind "ShowImage" is "Matplot". > I don't get what you mean. > --- > 2nd: it might become tricky if you want to have negative values on the axis. > Probably there is a way to shift the image to other position within the > coordinate system? > If you look at the source code for ShowImage you should be able to figure out how to plot an image with matplot(). However the tricky part may be to get the image imported into Scilab without IPD. This is done in c++ with ReadImageFile.cpp. https://atoms.scilab.org/toolboxes/IPD/8.3.2/files/IPD-8.3.2-1-src.zip If you manage to get an image into a graphical window, the purpose of newaxes() is to make the XY range of the plot independent of the pixel ranges. Jan ? From Serge.Steer at inria.fr Tue Feb 9 10:46:59 2016 From: Serge.Steer at inria.fr (Serge Steer) Date: Tue, 9 Feb 2016 10:46:59 +0100 Subject: [Scilab-users] Hilbert transform query In-Reply-To: References: <56B4946C.2090202@inria.fr> <1454698950.17554.86.camel@Servo> Message-ID: <56B9B593.6050006@inria.fr> X = hilbert(data) computes the hilbert transform of data(:) not a N dimensionnal Hilbert transform. Please find attached a function which is intended to compute the N dimensionnal Hilbert transform obtained applying the 1D hilbert transform to all columns then to all rows, .... This function exploits the ability of fft to compute all fft along a given dimension with a single call. Serge Le 08/02/2016 17:51, Lester Anderson a ?crit : > So what would the syntax be for doing a column run Hilbert, and row run Hilbert? > > It does sound like the suggesting would do what I think it is meant to. > > X = hilbert(data) // does compute pretty fast! > > At the moment I have used the netCDF code to read in GMT (net CDF) > data, which is a 601 x 601 matrix (x,y). So in order to do the column > and row method is it necessary to transpose the matrix, e.g. x = x' ? > > Thanks for any pointers > > On 5 February 2016 at 19:02, Tim Wescott wrote: >> Any time you go from 1D to 2D you suddenly end up with more than one way >> to do things, so I'm pretty sure that "how would one..." should really >> be worded "how would YOU...", or perhaps "how would someone in this >> field...". >> >> It sounds like you want to keep things rectilinear, so it may be best to >> just apply the transform column-by-column and row-by-row. That SHOULD >> work, and if you do it as matrix operations it should be pretty fast in >> Scilab. >> >> On Fri, 2016-02-05 at 12:52 +0000, Lester Anderson wrote: >>> Hi Serge, >>> >>> I am working with grid data, so looking for the 2D Hilbert, the >>> results I think should appear similar to doing a directional >>> derivative, where X highlights features with N-S trends and E-W for Y. >>> >>> Lester >>> >>> >>> >>> On 5 February 2016 at 12:24, Serge Steer wrote: >>>> Le 05/02/2016 10:56, Lester Anderson a ?crit : >>>>> Hello >>>>> >>>>> A quick query. How would one define the Hilbert transform of a grid >>>>> for X and Y directions; looking for two solutions Hx and Hy (for the >>>>> real values). >>>> Can you explain more precisely what you expect? >>>> Do you want to apply Hilbert transform to each column and to each rows or >>>> to perform a 2D Hilbert transform? >>>> Serge >>>>> >>>>> Thanks >>>>> Lester >>>>> _______________________________________________ >>>>> users mailing list >>>>> users at lists.scilab.org >>>>> http://lists.scilab.org/mailman/listinfo/users >>>>> >>>> _______________________________________________ >>>> users mailing list >>>> users at lists.scilab.org >>>> http://lists.scilab.org/mailman/listinfo/users >>> _______________________________________________ >>> users mailing list >>> users at lists.scilab.org >>> http://lists.scilab.org/mailman/listinfo/users >> -- >> >> Tim Wescott >> www.wescottdesign.com >> Control & Communications systems, circuit & software design. >> Phone: 503.631.7815 >> Cell: 503.349.8432 >> >> >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> http://lists.scilab.org/mailman/listinfo/users > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- function x = hilbertND(x) // Marple, S.L., "Computing the discrete-time analytic signal via FFT," // IEEE Transactions on Signal Processing, Vol. 47, No.9 (September // 1999), pp.2600-2603 // http://ieeexplore.ieee.org/iel5/78/16975/00782222.pdf?arnumber=782222 if type(x)<>1 then error(msprintf(gettext("%s: Wrong type for input argument #%d: Array of floating point numbers expected.\n"),"hilbert",1)) end if x==[] then return;end if ~isreal(x,0) then error(msprintf(gettext("%s: Input argument #%d must be real.\n"),"hilbert",1)); end d=size(x); for k=1:size(d,'*') n=d(k) if k<>1 then x=permute(x,[k,1]); end dp=size(x) x=matrix(x,d(k),-1) x = fft(real(x),-1,1); h=zeros(x) no2 = int(n/2); if ((2*no2) == n) then // n is even h([1,no2+1],:) = 1; h(2:no2,:) = 2; else // n is odd h(1,:) = 1; h(2:(n+1)/2,:) = 2; end x = fft(x.*h,1,1); x=matrix(x,dp) if k<>1 then x=permute(x,[k,1]);end end endfunction From amonmayr at laas.fr Tue Feb 9 13:36:06 2016 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Tue, 09 Feb 2016 13:36:06 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ID89PT91dGYtOD9xPyA/PSBQ?= =?utf-8?q?ut_an_image_as_the_background_of_an_axi?= In-Reply-To: <56B9B0A9.3010602@online.no> Message-ID: <4f95-56b9dd00-21-3eb04e80@120306340> Le Mardi 9 F?vrier 2016 10:26 CET, Jan ?ge Langeland a ?crit: > > > On 09.02.2016 09:09, Antoine Monmayrant wrote: > > > > Le Mardi 9 F?vrier 2016 08:34 CET, Philipp M?hlmann a ?crit: > > > >> Well, the base function behind "ShowImage" is "Matplot". > > I don't get what you mean. > > --- > > 2nd: it might become tricky if you want to have negative values on the axis. > > Probably there is a way to shift the image to other position within the > > coordinate system? > > > If you look at the source code for ShowImage you should be able to > figure out how to plot an image with matplot(). However the tricky part > may be to get the image imported into Scilab without IPD. This is done > in c++ with ReadImageFile.cpp. > https://atoms.scilab.org/toolboxes/IPD/8.3.2/files/IPD-8.3.2-1-src.zip > > If you manage to get an image into a graphical window, the purpose of > newaxes() is to make the XY range of the plot independent of the pixel > ranges. Ah, OK, I get your point now: if I can convert my image into scilab data, I can plot this data and overlap an axis ontop. Of course, you are right. I was trying to use the uicontrol "image" to avoid the hassle of conversion and directly use the image, well as an image! You are right, I can convert my image into ppm, load my ppm image into scilab as rgb hypermatrix and use Matplot + overlapped plots to get a backgournd. Thanks, Antoine > > Jan ? > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > From p.muehlmann at gmail.com Tue Feb 9 17:49:15 2016 From: p.muehlmann at gmail.com (=?UTF-8?Q?Philipp_M=C3=BChlmann?=) Date: Tue, 9 Feb 2016 17:49:15 +0100 Subject: [Scilab-users] =?utf-8?b?Pz0gID89PT91dGYtOD9xPyBQdXQgYW4gaW1hZ2Ug?= =?utf-8?q?as_the_background_of_an_axi?= In-Reply-To: <4f95-56b9dd00-21-3eb04e80@120306340> References: <56B9B0A9.3010602@online.no> <4f95-56b9dd00-21-3eb04e80@120306340> Message-ID: Just a side question to Antoine: What do you mean with uicontrol "image". Do you speak about creating an uicontrol of type "image" and try to put an image into that uicontrol? I tried this a couple of times, but didn't manage how to do that. Never worked. But I always thought this is a bug from the uicontrol and not from IPD or SIVP. Best regards, Philipp 2016-02-09 13:36 GMT+01:00 Antoine Monmayrant : > > Le Mardi 9 F?vrier 2016 10:26 CET, Jan ?ge Langeland a > ?crit: > > > > > > > On 09.02.2016 09:09, Antoine Monmayrant wrote: > > > > > > Le Mardi 9 F?vrier 2016 08:34 CET, Philipp M?hlmann < > p.muehlmann at gmail.com> a ?crit: > > > > > >> Well, the base function behind "ShowImage" is "Matplot". > > > I don't get what you mean. > > > --- > > > 2nd: it might become tricky if you want to have negative values on the > axis. > > > Probably there is a way to shift the image to other position within the > > > coordinate system? > > > > > If you look at the source code for ShowImage you should be able to > > figure out how to plot an image with matplot(). However the tricky part > > may be to get the image imported into Scilab without IPD. This is done > > in c++ with ReadImageFile.cpp. > > https://atoms.scilab.org/toolboxes/IPD/8.3.2/files/IPD-8.3.2-1-src.zip > > > > If you manage to get an image into a graphical window, the purpose of > > newaxes() is to make the XY range of the plot independent of the pixel > > ranges. > > > Ah, OK, I get your point now: if I can convert my image into scilab data, > I can plot this data and overlap an axis ontop. > Of course, you are right. > I was trying to use the uicontrol "image" to avoid the hassle of > conversion and directly use the image, well as an image! > You are right, I can convert my image into ppm, load my ppm image into > scilab as rgb hypermatrix and use Matplot + overlapped plots to get a > backgournd. > > Thanks, > > Antoine > > > > > Jan ? > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/users > > > > > > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > -- There we have the salad. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Tue Feb 9 20:27:09 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Tue, 9 Feb 2016 20:27:09 +0100 Subject: [Scilab-users] Put an image as the background of an axis In-Reply-To: <56B87251.7040903@laas.fr> References: <56B87251.7040903@laas.fr> Message-ID: <56BA3D8D.4070207@free.fr> Hello, Without images, this post should pass the moderation ;)[to the moderator: did you decrease the max size of body recently? It was formerly possible to post with images and body> 100kB] Le 08/02/2016 11:47, antoine.monmayrant at laas.fr a ?crit : > Hi everyone, > > I just failed at placing an image behind a plot. > I thought that would be easy: > - create a figure > - create an image uicontrol > - create an axis > - plot in the axis > - set axis.filled="off" > > Apparently I was wrong. > I did not find a way to overlap a plot with transparent background > over my image. > It seems that the image is always above the plot no matter what order > the uicontrol/axes where created. > I also tried to put both of them inside the same frame, but I did not > work either. You may use the z coordinate of your flat curves to manage overlays, as in: clf x = linspace(0,20,200); plot(x,sin(x)) e = gce(); c = e.children; // Example with a local image. The image is from https://atoms.scilab.org/atoms.png //xstring(0,-1,"$\scalebox{1}{\includegraphics{atoms.png}}$") // Example with a remote image under http:// (http*s*: not accepted) xstring(0,-1,"$\scalebox{1}{\includegraphics{http://www.cnrs.fr/fr/z-tools/newune/themes/CNRSTheme/images/logocnrs.png}}$") c.data(:,3) = 0.1; // <<<==== HERE c.thickness = 2;You may then tune the scalebox factor. Actually, like with an uicontrol(style="image"), the imported image is inlaid and is not resized accordingly with the embedding graphical figure. HTH Samuel Gougeon -------------- next part -------------- An HTML attachment was scrubbed... URL: From j-lan at online.no Tue Feb 9 22:54:32 2016 From: j-lan at online.no (=?UTF-8?Q?Jan_=c3=85ge_Langeland?=) Date: Tue, 9 Feb 2016 22:54:32 +0100 Subject: [Scilab-users] Put an image as the background of an axis In-Reply-To: <56BA3D8D.4070207@free.fr> References: <56B87251.7040903@laas.fr> <56BA3D8D.4070207@free.fr> Message-ID: <56BA6018.2060206@online.no> On 09.02.2016 20:27, Samuel Gougeon wrote: > > You may use the z coordinate of your flat curves to manage overlays, > as in: > clf > x = linspace(0,20,200); > plot(x,sin(x)) > e = gce(); > c = e.children; > // Example with a local image. The image is from > https://atoms.scilab.org/atoms.png > //xstring(0,-1,"$\scalebox{1}{\includegraphics{atoms.png}}$") > // Example with a remote image under http:// (http*s*: not accepted) > xstring(0,-1,"$\scalebox{1}{\includegraphics{http://www.cnrs.fr/fr/z-tools/newune/themes/CNRSTheme/images/logocnrs.png}}$") > c.data(:,3) = 0.1; // <<<==== HERE > c.thickness = 2;You may then tune the scalebox factor. Actually, like with an > uicontrol(style="image"), the imported image is inlaid and is not > resized accordingly with the embedding graphical figure. HTH Samuel > Gougeon Samuel Thank you for sharing these very good methods. It opens a lot of new possibilities. The way I want to use images in figure I find it better to modify your script with newaxis() before plotting. This makes the picture stay while zooming for instance: clf xstring(0,0,"$\scalebox{.3}{\includegraphics{http://photos.marinetraffic.com/ais/showphoto.aspx?photoid=445734}}$"); g=get("current_figure"); g.figure_size=[345,575]; b=newaxes(); b.filled = "off"; x = linspace(0,20,200); plot(x,sin(x)) By the way it would have been interesting to see an example with uicontrol(style="image") that you mention. I could never get that right. Brgds Jan ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From amonmayr at laas.fr Wed Feb 10 09:19:26 2016 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Wed, 10 Feb 2016 09:19:26 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ICBQdXQgYW4gaW1hZ2UgYXMg?= =?utf-8?q?the_background_of_an_axis?= In-Reply-To: <56BA6018.2060206@online.no> Message-ID: <3b08-56baf280-1-3247acc0@67949075> Le Mardi 9 F?vrier 2016 22:54 CET, Jan ?ge Langeland a ?crit: > > > On 09.02.2016 20:27, Samuel Gougeon wrote: > > > > You may use the z coordinate of your flat curves to manage overlays, > > as in: > > clf > > x = linspace(0,20,200); > > plot(x,sin(x)) > > e = gce(); > > c = e.children; > > // Example with a local image. The image is from > > https://atoms.scilab.org/atoms.png > > //xstring(0,-1,"$\scalebox{1}{\includegraphics{atoms.png}}$") > > // Example with a remote image under http:// (http*s*: not accepted) > > xstring(0,-1,"$\scalebox{1}{\includegraphics{http://www.cnrs.fr/fr/z-tools/newune/themes/CNRSTheme/images/logocnrs.png}}$") > > c.data(:,3) = 0.1; // <<<==== HERE > > c.thickness = 2;You may then tune the scalebox factor. Actually, like with an > > uicontrol(style="image"), the imported image is inlaid and is not > > resized accordingly with the embedding graphical figure. HTH Samuel > > Gougeon > Samuel > > Thank you for sharing these very good methods. It opens a lot of new > possibilities. > > The way I want to use images in figure I find it better to modify your > script with newaxis() before plotting. This makes the picture stay > while zooming for instance: > > clf > xstring(0,0,"$\scalebox{.3}{\includegraphics{http://photos.marinetraffic.com/ais/showphoto.aspx?photoid=445734}}$"); > g=get("current_figure"); g.figure_size=[345,575]; b=newaxes(); b.filled > = "off"; x = linspace(0,20,200); > plot(x,sin(x)) > > By the way it would have been interesting to see an example with > uicontrol(style="image") that you mention. I could never get that right. Here we go: //Image inside a figure with exactly the right size f = gcf(); imageWidth = 181; imageHeight = 144; f.axes_size=[imageWidth,imageHeight]; //here image parent can be set to something else than the figure f (like a frame, ...) h = uicontrol("Parent", f, .. "Style", "image", .. "Position", [0 0 imageWidth imageHeight], .. "String", SCI + "/modules/demo_tools/images/logo_scilab.png"); > > Brgds > Jan ? > > From arctica1963 at gmail.com Wed Feb 10 09:49:32 2016 From: arctica1963 at gmail.com (Lester Anderson) Date: Wed, 10 Feb 2016 08:49:32 +0000 Subject: [Scilab-users] Padarray Matlab equivalent in Scilab Message-ID: Hi all, A quick one. I am looking for the Scilab equivalent to padarray in Matlab. In the Matlab code the line is: datapad = padarray(data, [rdiff cdiff], 'replicate') where cdiff/rdiff are column/row, with the replicate function padding with the values at the borders of "data" The closest I can find in Scilab is: resize_matrix resMat = resize_matrix(mat, nbRows, nbCols, resType, padding) Just want to verify I am looking at the correct option. Lester From j-lan at online.no Wed Feb 10 10:52:13 2016 From: j-lan at online.no (=?UTF-8?Q?Jan_=c3=85ge_Langeland?=) Date: Wed, 10 Feb 2016 10:52:13 +0100 Subject: [Scilab-users] ?==?utf-8?q? Put an image as the background of an axis In-Reply-To: <3b08-56baf280-1-3247acc0@67949075> References: <3b08-56baf280-1-3247acc0@67949075> Message-ID: <56BB084D.3090004@online.no> On 10.02.2016 09:19, Antoine Monmayrant wrote: > f = gcf(); > imageWidth = 181; > imageHeight = 144; > f.axes_size=[imageWidth,imageHeight]; > > //here image parent can be set to something else than the figure f (like a frame, ...) > h = uicontrol("Parent", f, .. > "Style", "image", .. > "Position", [0 0 imageWidth imageHeight], .. > "String", SCI + "/modules/demo_tools/images/logo_scilab.png"); Thank you, that works fine, but I find that I have more control over the image with: im2=SCI + "/modules/demo_tools/images/logo_scilab.png"; xstring(0.4,0.4,"$\scalebox{.5}{\includegraphics{"+im2+"}}$"); Jan ? From sgougeon at free.fr Wed Feb 10 11:02:41 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Wed, 10 Feb 2016 11:02:41 +0100 Subject: [Scilab-users] Padarray Matlab equivalent in Scilab In-Reply-To: References: Message-ID: <56BB0AC1.5030909@free.fr> Hello, Le 10/02/2016 09:49, Lester Anderson a ?crit : > Hi all, > > A quick one. I am looking for the Scilab equivalent to padarray in Matlab. > > In the Matlab code the line is: > datapad = padarray(data, [rdiff cdiff], 'replicate') where cdiff/rdiff > are column/row, with the replicate function padding with the values at > the borders of "data" > > The closest I can find in Scilab is: resize_matrix > resMat = resize_matrix(mat, nbRows, nbCols, resType, padding) > > Just want to verify I am looking at the correct option. There is no real Scilab equivalent. Scilab's repmat() could be extended. For the time being, to process, you may use the 2 following lines: tmp = [data ; data($, :) .*. ones(addedRows, 1)]; paddedMat = [tmp tmp(:, $) .*. ones(1,addedCols)]; // EXAMPLE: addedRows = 3; addedCols = 2; data = grand(4,3,"uin",-9,9) tmp = [data ; data($, :) .*. ones(addedRows, 1)]; paddedMat = [tmp tmp(:, $) .*. ones(1,addedCols)] --> addedRows = 3; addedCols = 2; --> data = grand(4,3,"uin",-9,9) data = -5. -1. -7. -7. 3. -4. -4. 3. 2. 7. 2. 9. --> tmp = [data ; data($, :) .*. ones(addedRows, 1)]; --> paddedMat = [tmp tmp(:, $) .*. ones(1,addedCols)] paddedMat = -5. -1. -7. -7. -7. -7. 3. -4. -4. -4. -4. 3. 2. 2. 2. 7. 2. 9. 9. 9. 7. 2. 9. 9. 9. 7. 2. 9. 9. 9. 7. 2. 9. 9. 9. HTH Samuel Gougeon From sgougeon at free.fr Wed Feb 10 11:16:54 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Wed, 10 Feb 2016 11:16:54 +0100 Subject: [Scilab-users] Padarray Matlab equivalent in Scilab In-Reply-To: <56BB0AC1.5030909@free.fr> References: <56BB0AC1.5030909@free.fr> Message-ID: <56BB0E16.4060609@free.fr> Le 10/02/2016 11:02, Samuel Gougeon a ?crit : > There is no real Scilab equivalent. Scilab's repmat() could be extended. > For the time being, to process, you may use the 2 following lines: > > tmp = [data ; data($, :) .*. ones(addedRows, 1)]; > paddedMat = [tmp tmp(:, $) .*. ones(1,addedCols)]; This workaround works with numerical data (reals, complexes, encoded integers, polynomials). For boolean data, paddedMat becomes {0|1}. To recover a boolean padded matrix: paddedMat = (paddedMat==1) For a matrix of text, repmat() must be used instead of the kronecker product. The following will work whatever is the type of unmixed data, boolean and text included: tmp = [data ; repmat(data($, :), addedRows, 1)]; paddedMat = [tmp repmat(tmp(:, $) , 1, addedCols)] SG -------------- next part -------------- An HTML attachment was scrubbed... URL: From lavitha89 at gmail.com Wed Feb 10 11:50:14 2016 From: lavitha89 at gmail.com (Lavitha Pereira) Date: Wed, 10 Feb 2016 16:20:14 +0530 Subject: [Scilab-users] Maxima(Symbolic) Toolbox Message-ID: Hi All, I am trying to install 'Maxima' and facing issues. Has anyone installed it on 'Scilab 5.2.2'(Ubuntu/any Linux OS)?. Is there any better toolbox than Maxima available?. I have installed the dependencies perl, overloading,maxima separately and facing problem while integrating them. Error below: -->ilib_build('overload',table,files,[],'',ldflags,include,include,%f,''); !--error 999 ilib_build: Wrong value for input argument #3: existing file(s) expected. at line 46 of function ilib_build called by : ilib_build('overload',table,files,[],'',ldflags,include,include,%f,''); at line 31 of exec file called by : exec builder_src.sce -- Thanks & Regards, Lavitha M. Pereira -------------- next part -------------- An HTML attachment was scrubbed... URL: From antoine.monmayrant at laas.fr Wed Feb 10 13:37:44 2016 From: antoine.monmayrant at laas.fr (Antoine Monmayrant) Date: Wed, 10 Feb 2016 13:37:44 +0100 Subject: [Scilab-users] ?==?utf-8?q? Put an image as the background of an axis In-Reply-To: <56BB084D.3090004@online.no> References: <3b08-56baf280-1-3247acc0@67949075> <56BB084D.3090004@online.no> Message-ID: <56BB2F18.1010505@laas.fr> Le 02/10/2016 10:52 AM, Jan ?ge Langeland a ?crit : > > > On 10.02.2016 09:19, Antoine Monmayrant wrote: >> f = gcf(); >> imageWidth = 181; >> imageHeight = 144; >> f.axes_size=[imageWidth,imageHeight]; >> >> //here image parent can be set to something else than the figure f >> (like a frame, ...) >> h = uicontrol("Parent", f, .. >> "Style", "image", .. >> "Position", [0 0 imageWidth imageHeight], .. >> "String", SCI + "/modules/demo_tools/images/logo_scilab.png"); > Thank you, that works fine, but I find that I have more control over > the image with: > > im2=SCI + "/modules/demo_tools/images/logo_scilab.png"; > xstring(0.4,0.4,"$\scalebox{.5}{\includegraphics{"+im2+"}}$"); Yes, you are right, it's more convenient. The only added bonus with the uicontrol is that you have access to a callback function to react to the user's action. Antoine > > Jan ? > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ Antoine Monmayrant LAAS - CNRS 7 avenue du Colonel Roche BP 54200 31031 TOULOUSE Cedex 4 FRANCE Tel:+33 5 61 33 64 59 email : antoine.monmayrant at laas.fr permanent email : antoine.monmayrant at polytechnique.org +++++++++++++++++++++++++++++++++++++++++++++++++++++++ From arctica1963 at gmail.com Wed Feb 10 14:10:37 2016 From: arctica1963 at gmail.com (Lester Anderson) Date: Wed, 10 Feb 2016 13:10:37 +0000 Subject: [Scilab-users] Padarray Matlab equivalent in Scilab In-Reply-To: <56BB0E16.4060609@free.fr> References: <56BB0AC1.5030909@free.fr> <56BB0E16.4060609@free.fr> Message-ID: Thanks for the ideas, it kind of solves the need, but pads to left and bottom only: adding 2 cols/rows say to [1 2 3; 4 5 6; 7 8 9] 1 2 3 3 3 4 5 6 6 6 7 8 9 9 9 7 8 9 9 9 7 8 8 9 9 Is it possible to replicate on the top and right edges? (1 2 3) and (1 4 7) Also looked at resize_matrix(data, nr, nc) and that too only worked on right and bottom values, padding with 0 by default. On 10 February 2016 at 10:16, Samuel Gougeon wrote: > Le 10/02/2016 11:02, Samuel Gougeon a ?crit : > > There is no real Scilab equivalent. Scilab's repmat() could be extended. > For the time being, to process, you may use the 2 following lines: > > tmp = [data ; data($, :) .*. ones(addedRows, 1)]; > paddedMat = [tmp tmp(:, $) .*. ones(1,addedCols)]; > > > This workaround works with numerical data (reals, complexes, encoded > integers, polynomials). > > For boolean data, paddedMat becomes {0|1}. To recover a boolean padded > matrix: > paddedMat = (paddedMat==1) > > For a matrix of text, repmat() must be used instead of the kronecker > product. > The following will work whatever is the type of unmixed data, boolean and > text included: > > tmp = [data ; repmat(data($, :), addedRows, 1)]; > paddedMat = [tmp repmat(tmp(:, $) , 1, addedCols)] > > SG > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > From sgougeon at free.fr Wed Feb 10 16:43:33 2016 From: sgougeon at free.fr (sgougeon at free.fr) Date: Wed, 10 Feb 2016 16:43:33 +0100 (CET) Subject: [Scilab-users] Padarray Matlab equivalent in Scilab In-Reply-To: Message-ID: <1316244675.85049238.1455119013223.JavaMail.root@zimbra75-e12.priv.proxad.net> >Thanks for the ideas, it kind of solves the need, but pads to left and bottom only: tmp = [data ; repmat(data($, :), addedRows, 1)]; paddedMat = [tmp repmat(tmp(:, $) , 1, addedCols)] padds on the bottom and RIGHT. To pad on the left and top, just tune the concatenation: tmp = [repmat(data($, :), addedRows, 1) ; data]; paddedMat = [repmat(tmp(:, $) , 1, addedCols) tmp] Every side combination is possible. SG From tim at wescottdesign.com Wed Feb 10 18:13:29 2016 From: tim at wescottdesign.com (Tim Wescott) Date: Wed, 10 Feb 2016 09:13:29 -0800 Subject: [Scilab-users] Maxima(Symbolic) Toolbox In-Reply-To: References: Message-ID: <1455124409.2881.52.camel@Servo> On Wed, 2016-02-10 at 16:20 +0530, Lavitha Pereira wrote: > Hi All, > > > I am trying to install 'Maxima' and facing issues. Has anyone > installed it on 'Scilab 5.2.2'(Ubuntu/any Linux OS)?. Is there any > better toolbox than Maxima available?. > > I have installed the dependencies perl, overloading,maxima separately > and facing problem while integrating them. > > > Error below: > > > -->ilib_build('overload',table,files,[],'',ldflags,include,include,% > f,''); > !--error 999 > ilib_build: Wrong value for input argument #3: existing file(s) > expected. > at line 46 of function ilib_build called by : > ilib_build('overload',table,files,[],'',ldflags,include,include,% > f,''); > at line 31 of exec file called by : > exec builder_src.sce FWIW I use both Maxima (usually via WxMaxima) and Scilab fairly heavily. I use them separately and have never felt a need to have them merged. Generally my symbolic and my numerical calculations happen at significantly different times in my workflow, so why try to bolt them together? I don't know if this applies to you, of course. -- Tim Wescott www.wescottdesign.com Control & Communications systems, circuit & software design. Phone: 503.631.7815 Cell: 503.349.8432 From sgougeon at free.fr Wed Feb 10 20:00:43 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Wed, 10 Feb 2016 20:00:43 +0100 Subject: [Scilab-users] Padarray Matlab equivalent in Scilab In-Reply-To: <1316244675.85049238.1455119013223.JavaMail.root@zimbra75-e12.priv.proxad.net> References: <1316244675.85049238.1455119013223.JavaMail.root@zimbra75-e12.priv.proxad.net> Message-ID: <56BB88DB.3000006@free.fr> Le 10/02/2016 16:43, sgougeon at free.fr a ?crit : >> Thanks for the ideas, it kind of solves the need, but pads to left and bottom only: > tmp = [data ; repmat(data($, :), addedRows, 1)]; > paddedMat = [tmp repmat(tmp(:, $) , 1, addedCols)] > > padds on the bottom and RIGHT. > To pad on the left and top, just tune the concatenation: > > tmp = [repmat(data($, :), addedRows, 1) ; data]; > paddedMat = [repmat(tmp(:, $) , 1, addedCols) tmp] Rather tmp = [repmat(data(1, : ), addedRows, 1) ; data]; paddedMat = [repmat(tmp(:,1) , 1, addedCols) tmp] SG From sgougeon at free.fr Wed Feb 10 20:11:33 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Wed, 10 Feb 2016 20:11:33 +0100 Subject: [Scilab-users] ?==?utf-8?q? Put an image as the background of an axis In-Reply-To: <56BB2F18.1010505@laas.fr> References: <3b08-56baf280-1-3247acc0@67949075> <56BB084D.3090004@online.no> <56BB2F18.1010505@laas.fr> Message-ID: <56BB8B65.5070002@free.fr> Le 10/02/2016 13:37, Antoine Monmayrant a ?crit : > Le 02/10/2016 10:52 AM, Jan ?ge Langeland a ?crit : >> ..../... >> Thank you, that works fine, but I find that I have more control over >> the image with: >> >> im2=SCI + "/modules/demo_tools/images/logo_scilab.png"; >> xstring(0.4,0.4,"$\scalebox{.5}{\includegraphics{"+im2+"}}$"); > > Yes, you are right, it's more convenient. > The only added bonus with the uicontrol is that you have access to a > callback function to react to the user's action. Not even: as for the text style (http://bugzilla.scilab.org/7111), the callback is not implemented for the image style. After your example, add: h.callback_type=0; h.callback = "disp(""Hello"")" // Then click on the image => "Hello" should be displayed in the console for each click, but nothing is displayed. // You may change the instructions => nothing is never done. Samuel From vandithanvsl at gmail.com Thu Feb 11 07:52:42 2016 From: vandithanvsl at gmail.com (ramyavanditha) Date: Wed, 10 Feb 2016 23:52:42 -0700 (MST) Subject: [Scilab-users] Error occured while loading PIMS Message-ID: <1455173562346-4033435.post@n3.nabble.com> Dear ScilabUsers, while loading PIMS module we got an error as below: ->atomsLoad("PIMS") Start PIMS Load gateways atomsLoad: An error occurred while loading 'PIMS-1.1-0': link: The shared archive was not loaded: Unknown Error !--error 10000 at line 335 of function atomsLoad called by : atomsLoad("PIMS") please help us to get rid of it..... -- View this message in context: http://mailinglists.scilab.org/Error-occured-while-loading-PIMS-tp4033435.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From j-lan at online.no Thu Feb 11 10:00:45 2016 From: j-lan at online.no (=?UTF-8?Q?Jan-=c3=85ge_Langeland?=) Date: Thu, 11 Feb 2016 10:00:45 +0100 Subject: [Scilab-users] ?==?utf-8?q? Put an image as the background of an axis In-Reply-To: <56BB8B65.5070002@free.fr> References: <3b08-56baf280-1-3247acc0@67949075> <56BB084D.3090004@online.no> <56BB2F18.1010505@laas.fr> <56BB8B65.5070002@free.fr> Message-ID: <56BC4DBD.3020101@online.no> >> The only added bonus with the uicontrol is that you have access to a >> callback function to react to the user's action. > Not even: as for the text style (http://bugzilla.scilab.org/7111), the > callback is not implemented for the image style. After your example, add: > h.callback_type=0; > h.callback = "disp(""Hello"")" > // Then click on the image => "Hello" should be displayed in the > console for each click, but nothing is displayed. > // You may change the instructions => nothing is never done. > > Samuel What would a callback bring anyway, that you cannot do with xclick() ? Jan ? From lebevc at gmail.com Thu Feb 11 10:02:04 2016 From: lebevc at gmail.com (Leon Bevc) Date: Thu, 11 Feb 2016 10:02:04 +0100 Subject: [Scilab-users] Error occured while loading PIMS In-Reply-To: <1455173562346-4033435.post@n3.nabble.com> References: <1455173562346-4033435.post@n3.nabble.com> Message-ID: For Scilab 5.5.0 there was a known bug in PIMS: If you get an error message, here is a a workaround (Scilab 5.5 only): - close Scilab - open terminal and execute: git clone git://git.forge.scilab.org/pims.git Files from "git" are cloned into "pims" folder (in the context of terminal). - open Scilab, navigate to "pims" folder - execute "builder.sce" (right click / Execute) - refresh file list and execute "loader.sce" - Close Scilab and manually copy files from "pims" folder to "SCIHOME" folder which is usually: /home/'user_name'/.Scilab/scilab-5.5.0/atoms/PIMS/1.0-1/ ==> overwrite existing files! You can now delete "pims" foder created with "git". 2016-02-11 7:52 GMT+01.00, ramyavanditha : > Dear ScilabUsers, > while loading PIMS module we got an error as below: > ->atomsLoad("PIMS") > > Start PIMS > Load gateways > atomsLoad: An error occurred while loading 'PIMS-1.1-0': > link: The shared archive was not loaded: Unknown Error > !--error 10000 > > at line 335 of function atomsLoad called by : > atomsLoad("PIMS") > > please help us to get rid of it..... > > > > -- > View this message in context: > http://mailinglists.scilab.org/Error-occured-while-loading-PIMS-tp4033435.html > Sent from the Scilab users - Mailing Lists Archives mailing list archive at > Nabble.com. > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > From amonmayr at laas.fr Thu Feb 11 10:11:50 2016 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Thu, 11 Feb 2016 10:11:50 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ID89PT91dGYtOD9xPyA/PSBQ?= =?utf-8?q?ut_an_image_as_the_background_of_an_axi?= In-Reply-To: <56BC4DBD.3020101@online.no> Message-ID: <7961-56bc5080-4d-45856d80@103307384> Le Jeudi 11 F?vrier 2016 10:00 CET, Jan-?ge Langeland a ?crit: > > >> The only added bonus with the uicontrol is that you have access to a > >> callback function to react to the user's action. > > Not even: as for the text style (http://bugzilla.scilab.org/7111), the > > callback is not implemented for the image style. After your example, add: > > h.callback_type=0; > > h.callback = "disp(""Hello"")" > > // Then click on the image => "Hello" should be displayed in the > > console for each click, but nothing is displayed. > > // You may change the instructions => nothing is never done. > > > > Samuel > > What would a callback bring anyway, that you cannot do with xclick() ? Well, callbacks are the "official" way of interacting with the user. It would allow you to create an intereface in a consistant way, using only callbacks. Antoine > > Jan ? > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > From lebevc at gmail.com Thu Feb 11 10:27:54 2016 From: lebevc at gmail.com (Leon Bevc) Date: Thu, 11 Feb 2016 10:27:54 +0100 Subject: [Scilab-users] Error occured while loading PIMS In-Reply-To: References: <1455173562346-4033435.post@n3.nabble.com> Message-ID: For GNU-Linux users, related to Ubuntu 14.04 and derivatives: If you get an error message loading PIMS, here is a workaround (Scilab 5.5.0 only): - close Scilab - install "git" application: *sudo apt-get install git* - open terminal and execute: *git clone git://git.forge.scilab.org/pims.git * Files from "git" are cloned into "pims" folder (in the context of terminal). - open Scilab, navigate to downloaded "pims" folder - execute "*builder.sce*" (right click / Execute) - refresh file list and execute "*loader.sce*" - Close Scilab and manually copy files from "pims" folder to "SCIHOME" folder "*disp(SCIHOME)*", which is usually something like " */home/'user_name'/.Scilab/scilab-5.5.0/atoms/PIMS/1.0-1/*" ==> overwrite existing files! You can now delete "pims" foder created with "git". 2016-02-11 10:02 GMT+01:00 Leon Bevc : > For Scilab 5.5.0 there was a known bug in PIMS: > > If you get an error message, here is a a workaround (Scilab 5.5 only): > - close Scilab > - open terminal and execute: git clone > git://git.forge.scilab.org/pims.git > > Files from "git" are cloned into "pims" folder (in the context of > terminal). > - open Scilab, navigate to "pims" folder > - execute "builder.sce" (right click / Execute) > - refresh file list and execute "loader.sce" > - Close Scilab and manually copy files from "pims" folder to > "SCIHOME" folder which is usually: > /home/'user_name'/.Scilab/scilab-5.5.0/atoms/PIMS/1.0-1/ ==> > overwrite existing files! > > You can now delete "pims" foder created with "git". > > > 2016-02-11 7:52 GMT+01.00, ramyavanditha : > > Dear ScilabUsers, > > while loading PIMS module we got an error as below: > > ->atomsLoad("PIMS") > > > > Start PIMS > > Load gateways > > atomsLoad: An error occurred while loading 'PIMS-1.1-0': > > link: The shared archive was not loaded: Unknown Error > > !--error 10000 > > > > at line 335 of function atomsLoad called by : > > atomsLoad("PIMS") > > > > please help us to get rid of it..... > > > > > > > > -- > > View this message in context: > > > http://mailinglists.scilab.org/Error-occured-while-loading-PIMS-tp4033435.html > > Sent from the Scilab users - Mailing Lists Archives mailing list archive > at > > Nabble.com. > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/users > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From arctica1963 at gmail.com Thu Feb 11 10:32:38 2016 From: arctica1963 at gmail.com (Lester Anderson) Date: Thu, 11 Feb 2016 09:32:38 +0000 Subject: [Scilab-users] Padarray Matlab equivalent in Scilab In-Reply-To: <56BB88DB.3000006@free.fr> References: <1316244675.85049238.1455119013223.JavaMail.root@zimbra75-e12.priv.proxad.net> <56BB88DB.3000006@free.fr> Message-ID: Thanks for the update Samuel. Got the padding working as you suggested: clear() data = [1 2 3; 4 5 6; 7 8 9] addedRows = 3; addedCols = 3; tmp = [data ; data($, :) .*. ones(addedRows, 1)]; tmp = [tmp tmp(:, $) .*. ones(1,addedCols)]; tmp = [repmat(tmp(1, : ), addedRows, 1) ; tmp]; paddedMat = [repmat(tmp(:,1) , 1, addedCols) tmp] Perhaps an equivalent to "padarray" could be built into the next version(s). On 10 February 2016 at 19:00, Samuel Gougeon wrote: > Le 10/02/2016 16:43, sgougeon at free.fr a ?crit : >>> >>> Thanks for the ideas, it kind of solves the need, but pads to left and >>> bottom only: >> >> tmp = [data ; repmat(data($, :), addedRows, 1)]; >> paddedMat = [tmp repmat(tmp(:, $) , 1, addedCols)] >> >> padds on the bottom and RIGHT. >> To pad on the left and top, just tune the concatenation: >> >> tmp = [repmat(data($, :), addedRows, 1) ; data]; >> paddedMat = [repmat(tmp(:, $) , 1, addedCols) tmp] > > Rather > > tmp = [repmat(data(1, : ), addedRows, 1) ; data]; > paddedMat = [repmat(tmp(:,1) , 1, addedCols) tmp] > > > SG > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From j-lan at online.no Thu Feb 11 12:01:12 2016 From: j-lan at online.no (=?UTF-8?Q?Jan-=c3=85ge_Langeland?=) Date: Thu, 11 Feb 2016 12:01:12 +0100 Subject: [Scilab-users] ?= Put an image as the background of an axi In-Reply-To: <7961-56bc5080-4d-45856d80@103307384> References: <7961-56bc5080-4d-45856d80@103307384> Message-ID: <56BC69F8.6090009@online.no> What would a callback bring anyway, that you cannot do with xclick() ? > Well, callbacks are the "official" way of interacting with the user. > It would allow you to create an intereface in a consistant way, using only callbacks. > > Antoine > > Well you can put the image on top of a button: figure() h=uicontrol() h.callback = "disp(""Hello"")" h.position = [20,40,200,160] im2=SCI + "/modules/demo_tools/images/logo_scilab.png"; h.string="$\scalebox{1}{\includegraphics{"+im2+"}}$" I would really like to get the cursor position in the callback, like I do with xclick(), so clicking on different part of the image can work like a menu (Samuel?): Jan ? From vandithanvsl at gmail.com Thu Feb 11 16:41:18 2016 From: vandithanvsl at gmail.com (ramyavanditha) Date: Thu, 11 Feb 2016 08:41:18 -0700 (MST) Subject: [Scilab-users] Error occured while loading PIMS In-Reply-To: References: <1455173562346-4033435.post@n3.nabble.com> Message-ID: <1455205278232-4033442.post@n3.nabble.com> thank you LeBevc -- View this message in context: http://mailinglists.scilab.org/Error-occured-while-loading-PIMS-tp4033435p4033442.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From sgougeon at free.fr Thu Feb 11 20:14:38 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Thu, 11 Feb 2016 20:14:38 +0100 Subject: [Scilab-users] ?= Put an image as the background of an axi In-Reply-To: <56BC69F8.6090009@online.no> References: <7961-56bc5080-4d-45856d80@103307384> <56BC69F8.6090009@online.no> Message-ID: <56BCDD9E.30301@free.fr> Le 11/02/2016 12:01, Jan-?ge Langeland a ?crit : > .../... > I would really like to get the cursor position in the callback, like > I do with xclick(), so clicking on different part of the image can > work like a menu (Samuel?): Why not putting xclick() in the callback ? :) Have a try. From j-lan at online.no Thu Feb 11 21:07:37 2016 From: j-lan at online.no (=?UTF-8?Q?Jan_=c3=85ge_Langeland?=) Date: Thu, 11 Feb 2016 21:07:37 +0100 Subject: [Scilab-users] ?= Put an image as the background of an axi In-Reply-To: <56BCDD9E.30301@free.fr> References: <7961-56bc5080-4d-45856d80@103307384> <56BC69F8.6090009@online.no> <56BCDD9E.30301@free.fr> Message-ID: <56BCEA09.3010405@online.no> On 11.02.2016 20:14, Samuel Gougeon wrote: > Le 11/02/2016 12:01, Jan-?ge Langeland a ?crit : >> .../... >> I would really like to get the cursor position in the callback, like >> I do with xclick(), so clicking on different part of the image can >> work like a menu (Samuel?): > > Why not putting xclick() in the callback ? :) Have a try. > I did try: h.callback="disp(xclick())"; //disp can obviously be replaced with a suitable selection function. I can get it to work in a two click mode: First click the button, then click an image next to the button. The problem with making one big button with the picture on top, is that xclick() will not give the correct cursor position when on top of a button. Just static values [-2. -1. -1.]. "cbmenu - String: callback associated to a menu if |xclick| returns due to a click on a menu. In this case, |ibutton|, |xcoord|, |ycoord|, and |iwin| take arbitrary values". Jan ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From FritzLederer at web.de Thu Feb 11 22:04:42 2016 From: FritzLederer at web.de (Fritz Lederer) Date: Thu, 11 Feb 2016 22:04:42 +0100 Subject: [Scilab-users] [Sein o, km Mi n] ?= Put an image as the background of an axi Message-ID: An HTML attachment was scrubbed... URL: From p.muehlmann at gmail.com Fri Feb 12 09:21:10 2016 From: p.muehlmann at gmail.com (=?UTF-8?Q?Philipp_M=C3=BChlmann?=) Date: Fri, 12 Feb 2016 09:21:10 +0100 Subject: [Scilab-users] uicontrol style layer Message-ID: Can anyone please explain in more detail - than given in the help - the purpose of the uicontrol layer-style? How would one use this? Could one put several layer one over each other? Example: 1st layer: Image 2nd layer: plot of a function? result: plot over an Background Image BR Philipp -- There we have the salad. -------------- next part -------------- An HTML attachment was scrubbed... URL: From amonmayr at laas.fr Fri Feb 12 11:03:35 2016 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Fri, 12 Feb 2016 11:03:35 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ICB1aWNvbnRyb2wgc3R5bGUg?= =?utf-8?q?layer?= In-Reply-To: Message-ID: <231b-56bdae00-3-4677d180@85521322> Le Vendredi 12 F?vrier 2016 09:21 CET, Philipp M?hlmann a ?crit: > Can anyone please explain in more detail - than given in the help - the > purpose of the uicontrol layer-style? > > How would one use this? > > Could one put several layer one over each other? Short answer: I don't think so. Longer answer: I found some info on the layers in the unit tests: function layer = create_layer(count) c = get(0);c.usedeprecatedskin = "off" f = figure("dockable", "off" ,"infobar_visible", "off", "toolbar_visible", "off", "menubar_visible", "off", "layout", "border") f.figure_size = [300, 300]; //layer layer = uicontrol(f, "style", "layer", "constraints", createConstraints("border", "center")); for i = 1:count fr1 = uicontrol(layer, "style", "frame"); fr1.layout_options = createLayoutOptions("border", [10, 10]); fr1.layout = "border"; uicontrol(fr1, "string", "button " + string(i) + "1", "constraints", createConstraints("border", "top")); uicontrol(fr1, "string", "button " + string(i) + "2", "constraints", createConstraints("border", "left")); uicontrol(fr1, "string", "button " + string(i) + "3", "constraints", createConstraints("border", "center")); uicontrol(fr1, "string", "button " + string(i) + "4", "constraints", createConstraints("border", "bottom")); uicontrol(fr1, "string", "button " + string(i) + "5", "constraints", createConstraints("border", "right")); end endfunction What you can do with this function: ll=createlayer(3). ll.value=1; //figure shows the 4 buttons you put in the 1st layer ll.value=2; // now figure shows the 4 buttons you put in the 2nd layer ll.value=3; // now figure shows the 4 buttons you put in the 3rd layer This is how I understand the usage of such layer uicontrol: use a layer for each user interface you want (like one with a graph taking up all the figure size, one with parameter boxes, one with loading data infos, ...) then use the layer.value=i to show quickly the ith bit of the interface you want. If I'm correct, this is just like a tab uicontrol, minus the tab at the top! Antoine > > Example: > > 1st layer: Image > > 2nd layer: plot of a function? > > result: plot over an Background Image > > > BR > Philipp > > > -- > There we have the salad. From p.muehlmann at gmail.com Fri Feb 12 20:01:40 2016 From: p.muehlmann at gmail.com (=?UTF-8?Q?Philipp_M=C3=BChlmann?=) Date: Fri, 12 Feb 2016 20:01:40 +0100 Subject: [Scilab-users] ?==?utf-8?q? uicontrol style layer In-Reply-To: <231b-56bdae00-3-4677d180@85521322> References: <231b-56bdae00-3-4677d180@85521322> Message-ID: OK, thank you. 2016-02-12 11:03 GMT+01:00 Antoine Monmayrant : > > Le Vendredi 12 F?vrier 2016 09:21 CET, Philipp M?hlmann < > p.muehlmann at gmail.com> a ?crit: > > > Can anyone please explain in more detail - than given in the help - the > > purpose of the uicontrol layer-style? > > > > How would one use this? > > > > Could one put several layer one over each other? > > Short answer: I don't think so. > > Longer answer: I found some info on the layers in the unit tests: > > function layer = create_layer(count) > c = get(0);c.usedeprecatedskin = "off" > f = figure("dockable", "off" ,"infobar_visible", "off", > "toolbar_visible", "off", "menubar_visible", "off", "layout", "border") > f.figure_size = [300, 300]; > > //layer > layer = uicontrol(f, "style", "layer", "constraints", > createConstraints("border", "center")); > > for i = 1:count > fr1 = uicontrol(layer, "style", "frame"); > fr1.layout_options = createLayoutOptions("border", [10, 10]); > fr1.layout = "border"; > uicontrol(fr1, "string", "button " + string(i) + "1", > "constraints", createConstraints("border", "top")); > uicontrol(fr1, "string", "button " + string(i) + "2", > "constraints", createConstraints("border", "left")); > uicontrol(fr1, "string", "button " + string(i) + "3", > "constraints", createConstraints("border", "center")); > uicontrol(fr1, "string", "button " + string(i) + "4", > "constraints", createConstraints("border", "bottom")); > uicontrol(fr1, "string", "button " + string(i) + "5", > "constraints", createConstraints("border", "right")); > end > endfunction > > > What you can do with this function: > > ll=createlayer(3). > > ll.value=1; //figure shows the 4 buttons you put in the 1st layer > ll.value=2; // now figure shows the 4 buttons you put in the 2nd layer > ll.value=3; // now figure shows the 4 buttons you put in the 3rd layer > > > This is how I understand the usage of such layer uicontrol: use a layer > for each user interface you want (like one with a graph taking up all the > figure size, one with parameter boxes, one with loading data infos, ...) > then use the layer.value=i to show quickly the ith bit of the interface you > want. > If I'm correct, this is just like a tab uicontrol, minus the tab at the > top! > > Antoine > > > > > Example: > > > > 1st layer: Image > > > > 2nd layer: plot of a function? > > > > result: plot over an Background Image > > > > > > BR > > Philipp > > > > > > -- > > There we have the salad. > > > > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > -- There we have the salad. -------------- next part -------------- An HTML attachment was scrubbed... URL: From yann.debray at scilab-enterprises.com Mon Feb 15 16:35:08 2016 From: yann.debray at scilab-enterprises.com (Yann DEBRAY) Date: Mon, 15 Feb 2016 16:35:08 +0100 Subject: [Scilab-users] News: Scilab 6 Beta, VISA Toolbox, Embedded World 2016 In-Reply-To: <56C1DEEF.6050905@scilab-enterprises.com> References: <56C1DEEF.6050905@scilab-enterprises.com> Message-ID: <56C1F02C.7010600@scilab-enterprises.com> Hello Scilab user, It has been a while since we last shared news with you. Here are some recent updates we hope you will like. Scilab 6 Beta Scilab 6.0 is a major new release of Scilab, the open source modeling & simulation platform. This beta version is a preview for all users, commercial as well as community. *What's new: * --> New computation coreenabling bigger data sets --> Improved Xcos allowing larger models --> Utilities for development productivity (debugger, profiler and coverage) To provide relevant informations to the user, we also introduced a new view called "Newsfeed". The release will come soon, so feel free to give us feedback about your experience. Find out more Signal acquisition and instrument control with the Scilab VISA Toolbox (beta version) In partnership with National Instruments, we have developed a Scilab interface for measurement devices from leading manufacturers (National Instruments, Agilent/HP, ... ) Here is the first version of this VISA toolbox for signal acquisition and instrument control. This is a beta version: your feedbacks are welcome. TheVirtual Instrument Software Architecture (VISA) is a standard for configuring, programming, and troubleshooting instrumentation systems comprising GPIB, VXI, PXI, Serial, Ethernet, and/or USB interfaces. VISA provides the programming interface between the hardware and development environments. Find out more Event Embedded World // 23-25 February 2016, Nuremberg Starting with the largest embedded systems' event of the year:Embedded World 2016 23 - 25 February 2016 in Nuremberg, Germany We will be present on the booth of Evidence (Hall 4 / 4-545 _)_ and Emmtrix (Hall 4A, booth 520d _)_ Scilab has many applications in the field of embedded systems : --> post-processing of test data --> automation of tasks -->prototyping of control algorithms -->identification of systems parameter -->simulation of control systems --> embedded code generation Here are some use cases of Scilab in this field, from our last ScilabTEC : * ZYNQ-7000 High Performance Electric Drive and Silicon Carbide Multilevel inverter with Scilab Hardware-in-the-loop * E4Coder on Scilab: State Machines simulation and GUI prototyping * Can programming of multi-core systems be easier, please? * Real-time control and measurement applications Prior to this important event, we want to highlight some Scilab partners in the world of Embedded Systems which will be present at Embedded World: * Evidence , * Emmtrix , * Xilinx * LCM (present at Microchip's booth) Please do contact us, to set up a time for some quality exchange. Meet us @ Embedded World -- The Scilab Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From szymon.gapa at gmail.com Tue Feb 16 01:45:31 2016 From: szymon.gapa at gmail.com (simon_46_scilab) Date: Mon, 15 Feb 2016 17:45:31 -0700 (MST) Subject: [Scilab-users] Xcos-vector size error Message-ID: <1455583531168-4033453.post@n3.nabble.com> Hi, I am Simon I am doing some project for my studies. We have to simulate regulation systems with use of state information (x(t) - from state space). But for hours I can't manage the problem with vector size I used in simulation. I have been trying to simulate this model: In this part of project we've got make a model of so called Luenberger Observer (state observer). The subsystem looks like this: And in this part the problem appears: the vector after integration doesn't match to the 'F' gain which is 3x3 matrix. I have been trying many ways to solve that... The code-context to this simulation is: s = poly(0, "s"); numK= 64.75; b0=numK; b1=0; b2=0; denK = s^3 + 8*s^2 + 16.25*s + 64.75; a3=1; a2=8; a1=16.25; a0=64.75; K=numK/denK; //r=roots(denK) //i=%i; //r1=-7;r2=-0.5+3*i;r3=-0.5-3*i; A=[0 1 0;0 0 1;-a0 -a1 -a2]; b=[0;0;1] C=[b0,b1,b2]; D=zeros(3,1); //simA h=0.01; //clock period t=30; //simulation time x0=[1;2;3]; //vector of initial condition c0=eye(3,3); buf=1280; //simB //regulatory normal form lambda1=4; //experimentally derived lambda2=3; lambda3=-6; a_z=(s-lambda1)*(s-lambda2)*(s-lambda3); //polynomial of closed system alfa0=coeff(a_z,0); alfa1=coeff(a_z,1); alfa2=coeff(a_z,2); alfa3=coeff(a_z,3); //new polynomial coefficients kr1=alfa0-a0; kr2=alfa1-a1; kr3=alfa2-a2; k=[kr1; kr2; kr3]; //gain vector //Ackermann method I=eye(3,3); PHI=A^3+alfa2*A^2+alfa1*A+alfa0*I; Qc=[b A*b A^2*b]; //matrix of controllability kAk=([0 0 1]*(Qc)^(-1)*PHI)'; //Ackermann gain vector // simC lambda_f1=-15; //exemplary lambda values lambda_f2=-12; lambda_f3=-7; a_f=(s-lambda_f1)*(s-lambda_f2)*(s-lambda_f3); //observer characteristic polynomial alfa_f0=coeff(a_f,0); alfa_f1=coeff(a_f,1); alfa_f2=coeff(a_f,2); alfa_f3=coeff(a_f,3) PHIf=alfa_f3*A^3+alfa_f2*A^2+alfa_f1*A+alfa_f0*I;//matrix polynominal Qo=[C;C*A;C*A^2];//observability matrix kf=PHIf*inv(Qo)*[0; 0; 1]; //observer gain F=A-kf*C; //observer matrix I would be very very greateful for any help or prompt Simulation file: simC.zip -- View this message in context: http://mailinglists.scilab.org/Xcos-vector-size-error-tp4033453.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From shamika.i.nair at gmail.com Tue Feb 16 06:48:13 2016 From: shamika.i.nair at gmail.com (shamikam) Date: Mon, 15 Feb 2016 22:48:13 -0700 (MST) Subject: [Scilab-users] Activate Scilab MPI Message-ID: <1455601693703-4033454.post@n3.nabble.com> How do I activate Scilab MPI? On Scilab 5.5.0, I get errors when I type the following mpirun -c !--error 4 Undefined variable: mpirun MPI_Init() !--error 4 Undefined variable: MPI_Init Shamika -- View this message in context: http://mailinglists.scilab.org/Activate-Scilab-MPI-tp4033454.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From amonmayr at laas.fr Tue Feb 16 08:51:34 2016 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Tue, 16 Feb 2016 08:51:34 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ID89PT91dGYtOD9xPyBOZXdz?= =?utf-8?q?=3A_Scilab_6_Beta=2C_VISA_Toolbox=2C_Embedded_World_2016?= In-Reply-To: <56C1F02C.7010600@scilab-enterprises.com> Message-ID: <534d-56c2d500-b-1f2952e0@115531729> Hi all, I just installed the 6.0 beta and tried to install the visa module, without success: --> atomsInstall('visa') atomsInstallList: The package visa is not available. Any idea what's wrong? Antoine Le Lundi 15 F?vrier 2016 16:35 CET, Yann DEBRAY a ?crit: > Hello Scilab user, > > It has been a while since we last shared news with you. Here are some > recent updates we hope you will like. > > > Scilab 6 Beta > > Scilab 6.0 is a major new release of Scilab, the open source modeling & > simulation platform. This beta version is a preview for all users, > commercial as well as community. > > *What's new: * > > --> New computation coreenabling bigger data sets > --> Improved Xcos allowing larger models > --> Utilities for development productivity (debugger, profiler and coverage) > > To provide relevant informations to the user, we also introduced a new > view called "Newsfeed". > The release will come soon, so feel free to give us feedback about your > experience. > > Find out more > > > Signal acquisition and instrument control > with the Scilab VISA Toolbox (beta version) > > > In partnership with National Instruments, we have developed a Scilab > interface for measurement devices from leading manufacturers > (National Instruments, Agilent/HP, ... ) > > Here is the first version of this VISA toolbox for signal acquisition > and instrument control. This is a beta version: your feedbacks are welcome. > > TheVirtual Instrument Software Architecture > (VISA) is a standard for configuring, > programming, and troubleshooting instrumentation systems comprising > GPIB, VXI, PXI, Serial, Ethernet, and/or USB interfaces. VISA provides > the programming interface between the hardware and development > environments. > > Find out more > > > Event Embedded World // 23-25 February 2016, Nuremberg > > Starting with the largest embedded systems' event of the year:Embedded > World 2016 > 23 - 25 February 2016 in Nuremberg, Germany > > We will be present on the booth of Evidence (Hall 4 / 4-545 > _)_ and > Emmtrix (Hall 4A, booth 520d > _)_ > > Scilab has many applications in the field of embedded systems : > --> post-processing of test data > --> automation of tasks > -->prototyping of control algorithms > -->identification of systems parameter > -->simulation of control systems > --> embedded code generation > > Here are some use cases of Scilab in this field, from our last ScilabTEC : > > > > * ZYNQ-7000 High Performance Electric Drive and Silicon Carbide > Multilevel inverter with Scilab Hardware-in-the-loop > > * E4Coder on Scilab: State Machines simulation and GUI prototyping > > * Can programming of multi-core systems be easier, please? > > * Real-time control and measurement applications > > > Prior to this important event, we want to highlight some Scilab partners > in the world of Embedded Systems which will be present at Embedded World: > > * Evidence > , > * Emmtrix > , > * Xilinx > * LCM (present at Microchip's booth) > > Please do contact us, to set up a time for some quality exchange. > > Meet us @ Embedded World > > > -- > The Scilab Team > > > From amonmayr at laas.fr Tue Feb 16 08:54:57 2016 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Tue, 16 Feb 2016 08:54:57 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ID89PT91dGYtOD9xPyBOZXdz?= =?utf-8?q?=3A_Scilab_6_Beta=2C_VISA_Toolbox=2C_Embedded_World_2016?= In-Reply-To: <56C1F02C.7010600@scilab-enterprises.com> Message-ID: <534d-56c2d600-15-1f2952e0@115531773> Hi again, I also tried to install 'visa' module in scilab 5.5.0 and it also failed. Antoine Le Lundi 15 F?vrier 2016 16:35 CET, Yann DEBRAY a ?crit: > Hello Scilab user, > > It has been a while since we last shared news with you. Here are some > recent updates we hope you will like. > > > Scilab 6 Beta > > Scilab 6.0 is a major new release of Scilab, the open source modeling & > simulation platform. This beta version is a preview for all users, > commercial as well as community. > > *What's new: * > > --> New computation coreenabling bigger data sets > --> Improved Xcos allowing larger models > --> Utilities for development productivity (debugger, profiler and coverage) > > To provide relevant informations to the user, we also introduced a new > view called "Newsfeed". > The release will come soon, so feel free to give us feedback about your > experience. > > Find out more > > > Signal acquisition and instrument control > with the Scilab VISA Toolbox (beta version) > > > In partnership with National Instruments, we have developed a Scilab > interface for measurement devices from leading manufacturers > (National Instruments, Agilent/HP, ... ) > > Here is the first version of this VISA toolbox for signal acquisition > and instrument control. This is a beta version: your feedbacks are welcome. > > TheVirtual Instrument Software Architecture > (VISA) is a standard for configuring, > programming, and troubleshooting instrumentation systems comprising > GPIB, VXI, PXI, Serial, Ethernet, and/or USB interfaces. VISA provides > the programming interface between the hardware and development > environments. > > Find out more > > > Event Embedded World // 23-25 February 2016, Nuremberg > > Starting with the largest embedded systems' event of the year:Embedded > World 2016 > 23 - 25 February 2016 in Nuremberg, Germany > > We will be present on the booth of Evidence (Hall 4 / 4-545 > _)_ and > Emmtrix (Hall 4A, booth 520d > _)_ > > Scilab has many applications in the field of embedded systems : > --> post-processing of test data > --> automation of tasks > -->prototyping of control algorithms > -->identification of systems parameter > -->simulation of control systems > --> embedded code generation > > Here are some use cases of Scilab in this field, from our last ScilabTEC : > > > > * ZYNQ-7000 High Performance Electric Drive and Silicon Carbide > Multilevel inverter with Scilab Hardware-in-the-loop > > * E4Coder on Scilab: State Machines simulation and GUI prototyping > > * Can programming of multi-core systems be easier, please? > > * Real-time control and measurement applications > > > Prior to this important event, we want to highlight some Scilab partners > in the world of Embedded Systems which will be present at Embedded World: > > * Evidence > , > * Emmtrix > , > * Xilinx > * LCM (present at Microchip's booth) > > Please do contact us, to set up a time for some quality exchange. > > Meet us @ Embedded World > > > -- > The Scilab Team > > > From sgougeon at free.fr Tue Feb 16 11:11:07 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Tue, 16 Feb 2016 11:11:07 +0100 Subject: [Scilab-users] ?= =?utf-8?q? News: Scilab 6 Beta, VISA Toolbox, Embedded World 2016 In-Reply-To: <534d-56c2d500-b-1f2952e0@115531729> References: <534d-56c2d500-b-1f2952e0@115531729> Message-ID: <56C2F5BB.4090906@free.fr> Hello, Le 16/02/2016 08:51, Antoine Monmayrant a ?crit : > Hi all, > > I just installed the 6.0 beta and tried to install the visa module, without success: > > --> atomsInstall('visa') > atomsInstallList: The package visa is not available. > > Any idea what's wrong? In ATOMS, the flag indicating /Supported Scilab versions/ is set to ">= 5.5": https://atoms.scilab.org/toolboxes/visa/0.9.0 Despite 6.0> 5.5, the flag ">=5.5" excludes Scilab >=6.0 This has been reported here http://bugzilla.scilab.org/13891 and there http://bugzilla.scilab.org/13938 (proposal). This behavior is apparently intentional, i guess to compel modules maintainers to review and regenerate specific releases for Scilab >= 6.0 This should deserve to explicitly warn modules maintainers about that. Le 16/02/2016 08:54, Antoine Monmayrant a ?crit : > Hi again, > > I also tried to install 'visa' module in scilab 5.5.0 and it also failed. If the 0.9.0 release has been compiled for Scilab 6.0 -- has it ? --, then it can't run under Scilab 5.5 I am afraid that these explanations do not help much. Regards Samuel Gougeon -------------- next part -------------- An HTML attachment was scrubbed... URL: From grocer.toolbox at gmail.com Tue Feb 16 11:55:35 2016 From: grocer.toolbox at gmail.com (Eric Dubois) Date: Tue, 16 Feb 2016 11:55:35 +0100 Subject: [Scilab-users] News: Scilab 6 Beta, VISA Toolbox, Embedded World 2016 In-Reply-To: <56C1F02C.7010600@scilab-enterprises.com> References: <56C1DEEF.6050905@scilab-enterprises.com> <56C1F02C.7010600@scilab-enterprises.com> Message-ID: Hello Thank you for this release and the improvements this Scilab version contains. I have however a major concern with the change of behaviour of the addition or subtraction of a null matrix to another matrix. As explained in the release notes, []+a will now result in [] whereas it resulted in a in previous versions. This means that developments made under older Scilab versions will have to be adapted to Scilab 6.0. This is potentially a huge task, since all additions or subtractions in the programs have a priori to be checked. Needless to say, additions and subtractions are very pervasive operations in numerical programs. And since all additions and subtractions cannot be checked in a systematic way (in my toolbox, I have more than 20 000 of them!), the needed modifications will be made over a long period of time, at the rhythm of the discovery of bugs by a developer or its users. More worrying still, not all additions or subtractions involving null matrices will generate errors when switching from Scilab 5 or older to Scilab 6: for example, z=size([a+1 y],1) applied to the null matrix a will simply add 1 in Scilab 6 to the result of Scilab 5, without generating errors. The attentive user will be alerted by the warning message generated by Scilab 6, but the inattentive one may not notice it or fully understand its consequences. So it may lead some users to generate wrong results without being aware of it, which should be very embarrassing for the provider of the programs used and for Scilab-enterprises itself. Another problem will come from users sticking to Scilab older versions: as for me I have regularly e-mails from users that work for a reason or another on old Scilab versions (5.3.3 at the moment for instance): avoiding problems to these users will constrain the adaptation, prevent from using all capabilities of Scilab and complicate the code. With my example, it will be necessary to introduce a conditional such as: if isempty(x) then z=size(y,1)+1 else z=size([a y],1) end And this will apply to new programs as well, which will need so much care that, I fear, some cases will be missed by even the most careful programmer. And in this case users working with older Scilab versions will not even be alerted by a warning message. Moreover, considering the importance of the change, it is all the more surprising that it has not been announced in advance, as was the ?good? practice for previous changes, even minor (such as the replacement of x^n by x .^n when x was a vector, a change that a) affected much less numerous lines of code b) did entail a simple replacement of some ^ by .^ c) had no side effect). Don?t other Scilab users share my concern? Regards ?ric. PS: I find a little bit provocative the sentence in the release notes: ?To simplify the transition of your code base during beta, a specific warning is issued when such operation is detected?. With a little exaggeration, it sounds like digging the Great canyon and saying to people now separated by it: to help you, we will give you beach shovels so that you can build a bridge between the two rivers of the canyon... 2016-02-15 16:35 GMT+01:00 Yann DEBRAY : > Hello Scilab user, > > It has been a while since we last shared news with you. Here are some > recent updates we hope you will like. > Scilab 6 Beta > > Scilab 6.0 is a major new release of Scilab, the open source modeling & > simulation platform. This beta version is a preview for all users, > commercial as well as community. > > *What's new: * > > --> New computation core enabling bigger data sets > --> Improved Xcos allowing larger models > --> Utilities for development productivity (debugger, profiler and > coverage) > > To provide relevant informations to the user, we also introduced a new > view called "Newsfeed". > The release will come soon, so feel free to give us feedback about your > experience. > > Find out more > > Signal acquisition and instrument control > with the Scilab VISA Toolbox (beta version) In partnership with National > Instruments, we have developed a Scilab interface for measurement devices > from leading manufacturers (National Instruments, Agilent/HP, ... ) > > Here is the first version of this VISA toolbox for signal acquisition and > instrument control. This is a beta version: your feedbacks are welcome. > > The Virtual Instrument Software Architecture (VISA) > is a standard for configuring, programming, and troubleshooting > instrumentation systems comprising GPIB, VXI, PXI, Serial, Ethernet, and/or > USB interfaces. VISA provides the programming interface between the > hardware and development environments. > > Find out more > > Event Embedded World // 23-25 February 2016, Nuremberg > > Starting with the largest embedded systems' event of the year : Embedded > World 2016 > 23 - 25 February 2016 in Nuremberg, Germany > > We will be present on the booth of Evidence (Hall 4 / 4-545 > > *)* and Emmtrix (Hall 4A, booth 520d > > *)* > > Scilab has many applications in the field of embedded systems : > --> post-processing of test data > --> automation of tasks > --> prototyping of control algorithms > --> identification of systems parameter > --> simulation of control systems > --> embedded code generation > > Here are some use cases of Scilab in this field, from our last ScilabTEC : > > > > > - ZYNQ-7000 High Performance Electric Drive and Silicon Carbide > Multilevel inverter with Scilab Hardware-in-the-loop > > - E4Coder on Scilab: State Machines simulation and GUI prototyping > > - Can programming of multi-core systems be easier, please? > > - Real-time control and measurement applications > > > Prior to this important event, we want to highlight some Scilab partners > in the world of Embedded Systems which will be present at Embedded World: > > > - Evidence , > > - Emmtrix , > > - Xilinx > - LCM (present at Microchip's > booth) > > Please do contact us, to set up a time for some quality exchange. > > Meet us @ Embedded World > > > -- > The Scilab Team > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From clement.david at scilab-enterprises.com Tue Feb 16 12:00:10 2016 From: clement.david at scilab-enterprises.com (=?ISO-8859-1?Q?Cl=E9ment?= David) Date: Tue, 16 Feb 2016 12:00:10 +0100 Subject: [Scilab-users] Activate Scilab MPI In-Reply-To: <1455601693703-4033454.post@n3.nabble.com> References: <1455601693703-4033454.post@n3.nabble.com> Message-ID: <1455620410.2703.14.camel@scilab-enterprises.com> Hello Shamikan, Inside Scilab, the MPI functions are used on `parallel_run`. Take a look at the example on the help page. See?https://help.scilab.org/docs/5.5.2/en_US/parallel_run.html -- Cl?ment Le lundi 15 f?vrier 2016 ? 22:48 -0700, shamikam a ?crit?: > How do I activate Scilab MPI? On Scilab 5.5.0, I get errors when I type the > following? > > mpirun -c > ? !--error 4? > Undefined variable: mpirun > > MPI_Init() > ???????????!--error 4? > Undefined variable: MPI_Init > > Shamika > > > > -- > View this message in context: http://mailinglists.scilab.org/Activate-Scilab-MPI-tp4033454.html > Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From amonmayr at laas.fr Tue Feb 16 12:21:12 2016 From: amonmayr at laas.fr (amonmayr at laas.fr) Date: Tue, 16 Feb 2016 12:21:12 +0100 Subject: [Scilab-users] News: Scilab 6 Beta, VISA Toolbox, Embedded World 2016 In-Reply-To: References: <56C1DEEF.6050905@scilab-enterprises.com> <56C1F02C.7010600@scilab-enterprises.com> Message-ID: <56C30628.9050505@laas.fr> Le 02/16/2016 11:55 AM, Eric Dubois a ?crit : > > Hello > > Thank you for this release and the improvements this Scilab version > contains. > > I have however a major concern with the change of behaviour of the > addition or subtraction of a null matrix to another matrix. As > explained in the release notes, []+a will now result in [] whereas it > resulted in a in previous versions. > > This means that developments made under older Scilab versions will > have to be adapted to Scilab 6.0. This is potentially a huge task, > since all additions or subtractions in the programs have a priori to > be checked. Needless to say, additions and subtractions are very > pervasive operations in numerical programs. And since all additions > and subtractions cannot be checked in a systematic way (in my toolbox, > I have more than 20 000 of them!), the needed modifications will be > made over a long period of time, at the rhythm of the discovery of > bugs by a developer or its users. > > More worrying still, not all additions or subtractions involving null > matrices will generate errors when switching from Scilab 5 or older to > Scilab 6: for example, z=size([a+1 y],1) applied to the null matrix a > will simply add 1 in Scilab 6 to the result of Scilab 5, without > generating errors. The attentive user will be alerted by the warning > message generated by Scilab 6, but the inattentive one may not notice > it or fully understand its consequences. So it may lead some users to > generate wrong results without being aware of it, which should be very > embarrassing for the provider of the programs used and for > Scilab-enterprises itself. > > Another problem will come from users sticking to Scilab older > versions: as for me I have regularly e-mails from users that work for > a reason or another on old Scilab versions (5.3.3 at the moment for > instance): avoiding problems to these users will constrain the > adaptation, prevent from using all capabilities of Scilab and > complicate the code. With my example, it will be necessary to > introduce a conditional such as: > > if isempty(x) then > > z=size(y,1)+1 > > else > > z=size([a y],1) > > end > > And this will apply to new programs as well, which will need so much > care that, I fear, some cases will be missed by even the most careful > programmer. And in this case users working with older Scilab versions > will not even be alerted by a warning message. > > Moreover, considering the importance of the change, it is all the more > surprising that it has not been announced in advance, as was the > ?good? practice for previous changes, even minor (such as the > replacement of x^n by x .^n when x was a vector, a change that a) > affected much less numerous lines of code b) did entail a simple > replacement of some ^ by .^ c) had no side effect). > > Don?t other Scilab users share my concern? > Well, I understand your concern. However, I buy the fact that this change will make the language more consistent. Indeed, "ms=m+s" where m is a matrix and s a scalar gives a matrix ms of same size than m in most cases (ie when m is not empty). It thus makes sense that adding a scalar to an empty matrix returns an empty matrix. This is also the default behavior with other similar languages like octave, matlab, julia, so it makes sense. I think the old behavior was kind of weird. But you are right that this is a major change that will introduce subtle and hard to find bugs. We should keep in mind that it's a major change (5.x->6.x) and I think the last one (4.x->5.x) was even worse in terms of backward compatibility! Cheers, Antoine > Regards > > ?ric. > > PS: I find a little bit provocative the sentence in the release notes: > ?To simplify the transition of your code base during beta, a specific > warning is issued when such operation is detected?. With a little > exaggeration, it sounds like digging the Great canyon and saying to > people now separated by it: to help you, we will give you beach > shovels so that you can build a bridge between the two rivers of the > canyon... > > > 2016-02-15 16:35 GMT+01:00 Yann DEBRAY > >: > > Hello Scilab user, > > It has been a while since we last shared news with you. Here are > some recent updates we hope you will like. > > > Scilab 6 Beta > > Scilab 6.0 is a major new release of Scilab, the open source > modeling & simulation platform. This beta version is a preview for > all users, commercial as well as community. > > *What's new: * > > --> New computation coreenabling bigger data sets > --> Improved Xcos allowing larger models > --> Utilities for development productivity (debugger, profiler and > coverage) > > To provide relevant informations to the user, we also introduced a > new view called "Newsfeed". > The release will come soon, so feel free to give us feedback about > your experience. > > Find out more > > > Signal acquisition and instrument control > with the Scilab VISA Toolbox (beta version) > > > In partnership with National Instruments, we have developed a > Scilab interface for measurement devices from leading > manufacturers (National Instruments, Agilent/HP, ... ) > > Here is the first version of this VISA toolbox for signal > acquisition and instrument control. This is a beta version: your > feedbacks are welcome. > > TheVirtual Instrument Software Architecture > (VISA) is a standard for configuring, > programming, and troubleshooting instrumentation systems > comprising GPIB, VXI, PXI, Serial, Ethernet, and/or USB > interfaces. VISA provides the programming interface between the > hardware and development environments. > > Find out more > > > Event Embedded World // 23-25 February 2016, Nuremberg > > Starting with the largest embedded systems' event of the > year:Embedded World 2016 > 23 - 25 February 2016 in Nuremberg, Germany > > We will be present on the booth of Evidence (Hall 4 / 4-545 > _)_ and > Emmtrix (Hall 4A, booth 520d > _)_ > > Scilab has many applications in the field of embedded systems : > --> post-processing of test data > --> automation of tasks > -->prototyping of control algorithms > -->identification of systems parameter > -->simulation of control systems > --> embedded code generation > > Here are some use cases of Scilab in this field, from our last > ScilabTEC : > > > > * ZYNQ-7000 High Performance Electric Drive and Silicon Carbide > Multilevel inverter with Scilab Hardware-in-the-loop > > * E4Coder on Scilab: State Machines simulation and GUI > prototyping > > * Can programming of multi-core systems be easier, please? > > * Real-time control and measurement applications > > > Prior to this important event, we want to highlight some Scilab > partners in the world of Embedded Systems which will be present at > Embedded World: > > * Evidence > , > * Emmtrix > , > * Xilinx > * LCM (present at > Microchip's booth) > > Please do contact us, to set up a time for some quality exchange. > > Meet us @ Embedded World > > > -- > The Scilab Team > > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ Antoine Monmayrant LAAS - CNRS 7 avenue du Colonel Roche BP 54200 31031 TOULOUSE Cedex 4 FRANCE Tel:+33 5 61 33 64 59 email : antoine.monmayrant at laas.fr permanent email : antoine.monmayrant at polytechnique.org +++++++++++++++++++++++++++++++++++++++++++++++++++++++ -------------- next part -------------- An HTML attachment was scrubbed... URL: From clement.david at scilab-enterprises.com Tue Feb 16 12:35:43 2016 From: clement.david at scilab-enterprises.com (=?ISO-8859-1?Q?Cl=E9ment?= David) Date: Tue, 16 Feb 2016 12:35:43 +0100 Subject: [Scilab-users] ?==?utf-8?q? ?==?utf-8?q? News: Scilab 6 Beta, VISA Toolbox, Embedded World 2016 In-Reply-To: <534d-56c2d600-15-1f2952e0@115531773> References: <534d-56c2d600-15-1f2952e0@115531773> Message-ID: <1455622542.2703.18.camel@scilab-enterprises.com> Hi Antoine, In fact this module is only available for windows x86 or x64 with Scilab 5.5.2 installed. I just checked and it is not available on Scilab 5.5.0. You have to enforce the installation by downloading the zip file and using `atomsInstall('visa.zip')` directly. -- Cl?ment Le mardi 16 f?vrier 2016 ? 08:54 +0100, Antoine Monmayrant a ?crit?: > Hi again, > > I also tried to install 'visa' module in scilab 5.5.0 and it also failed. > > Antoine > > ? > Le Lundi 15 F?vrier 2016 16:35 CET, Yann DEBRAY a ?crit:? > ? > > Hello Scilab user, > > > > It has been a while since we last shared news with you. Here are some? > > recent updates we hope you will like. > > > > > > ????Scilab 6 Beta > > > > Scilab 6.0 is a major new release of Scilab, the open source modeling &? > > simulation platform. This beta version is a preview for all users,? > > commercial as well as community. > > > > *What's new: * > > > > --> New computation coreenabling bigger data sets > > --> Improved Xcos allowing larger models > > --> Utilities for development productivity (debugger, profiler and coverage) > > > > To provide relevant informations to the user, we also introduced a new? > > view called "Newsfeed". > > The release will come soon, so feel free to give us feedback about your? > > experience. > > > > Find out more > > > > > > ????Signal acquisition and instrument control > > ????with the Scilab VISA Toolbox (beta version) > > > > > > ????In partnership with National Instruments, we have developed a Scilab > > ????interface for measurement devices from leading manufacturers > > ????(National Instruments, Agilent/HP, ... ) > > > > Here is the first version of this VISA toolbox for signal acquisition? > > and instrument control. This is a beta version: your feedbacks are welcome. > > > > TheVirtual Instrument Software Architecture? > > (VISA) is a standard for configuring,? > > programming, and troubleshooting instrumentation systems comprising? > > GPIB, VXI, PXI, Serial, Ethernet, and/or USB interfaces. VISA provides? > > the programming interface between the hardware and development? > > environments. > > > > Find out more > > > > > > ????Event Embedded World // 23-25 February 2016, Nuremberg > > > > Starting with the largest embedded systems' event of the year:Embedded? > > World 2016 > > 23 - 25 February 2016 in Nuremberg, Germany > > > > We will be present on the booth of Evidence (Hall 4 / 4-545? > > _) > > _ and? > > Emmtrix (Hall 4A, booth 520d? > > > ogies>_)_ > > > > Scilab has many applications in the field of embedded systems : > > --> post-processing of test data > > --> automation of tasks > > -->prototyping of control algorithms > > -->identification of systems parameter > > -->simulation of control systems > > --> embedded code generation > > > > Here are some use cases of Scilab in this field, from our last ScilabTEC : > > > > > -Silicon-Carbide-Multilevel-inverter-with-SCILAB-Hardware-in-the-loop> > > > > ? * ZYNQ-7000 High Performance Electric Drive and Silicon Carbide > > ????Multilevel inverter with Scilab Hardware-in-the-loop > > ???? > -and-Silicon-Carbide-Multilevel-inverter-with-SCILAB-Hardware-in-the-loop> > > ? * E4Coder on Scilab: State Machines simulation and GUI prototyping > > ???? > on-and-GUI-prototyping-for-Scilab-5.x> > > ? * Can programming of multi-core systems be easier, please? > > ???? > easier-please-The-ALMA-Approach> > > ? * Real-time control and measurement applications > > ???? > ontrol-and-measurement-applications> > > > > Prior to this important event, we want to highlight some Scilab partners? > > in the world of Embedded Systems which will be present at Embedded World: > > > > ? * Evidence > > ????, > ovL3d3dy5lbW10cml4LmNvbQ> > > ? * Emmtrix > > ????, > ovL3d3dy54aWxpbnguY29tLw> > > ? * Xilinx > > ? * LCM (present at Microchip's booth) > > > > Please do contact us, to set up a time for some quality exchange. > > > > Meet us @ Embedded World? > > > > > > -- > > The Scilab Team > > > > > > > ? > ? > ? > ? > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From j-lan at online.no Tue Feb 16 13:00:47 2016 From: j-lan at online.no (=?UTF-8?Q?Jan_=c3=85ge_Langeland?=) Date: Tue, 16 Feb 2016 13:00:47 +0100 Subject: [Scilab-users] News: Scilab 6 Beta, VISA Toolbox, Embedded World 2016 In-Reply-To: References: <56C1DEEF.6050905@scilab-enterprises.com> <56C1F02C.7010600@scilab-enterprises.com> Message-ID: <56C30F6F.6060803@online.no> On 16.02.2016 11:55, Eric Dubois wrote: > Don?t other Scilab users share my concern? > > Regards > > ?ric. > > I have a similar (but simpler) problem, with stacksize(). All my old scripts containing stacksize('max') etc. need to be modified. All it will take is to keep the standard function stacksize(a) in Scilab 6, just let it do nothing. Jan ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From arctica1963 at gmail.com Tue Feb 16 13:02:53 2016 From: arctica1963 at gmail.com (Lester Anderson) Date: Tue, 16 Feb 2016 12:02:53 +0000 Subject: [Scilab-users] Scilab (5.5.2) and proxy settings Message-ID: Hello At the moment the only way I can install additional modules is in "offline" mode. Tried all the usual routes for proxy settings but the program will not find the default proxy in place, even though other applications will do (without manually setting the values). Tested with the free GIS program QGIS to verify. The following fails to get access to the atoms online repository: atomsSetConfig('offline','False') atomsSetConfig('useProxy','True') atomsSetConfig('proxyHost',' IP address') atomsSetConfig('proxyPort','port value') Similarly setting the proxy 'on' in the preferences does not work. Note: there is no username/password to apply, and even if those were entered it still does not work through the proxy. Attempting to access the repository would give this error: gzip: C:\Users\xxxxxx\AppData\Local\Temp\SCCDAC~1\ATOMS~1\1_TOOLBOXES.gz: not ! ! in gzip format ! WARNING: atomsDESCRIPTIONget: Extraction of the DESCRIPTION file ('C:\Users\xxxxxx\AppData\Local\Temp\SCCDAC~1\ATOMS~1\1_TOOLBOXES.gz') has failed. Scanning repository http://atoms.scilab.org/5.5 ... Skipped The preferences are setb to use the default web browser and therefore it would also follow the default proxy, I would have thought. Now, this is not a big problem as one can install modules offline, but it is hard to know why the program cannot find the proxy details automatically. I have also checked with some IT guys and they also confirm that the proxy settings are correct and so all should be fine. Be interested to see what the experts say on this point. From antoine.monmayrant at laas.fr Tue Feb 16 13:12:40 2016 From: antoine.monmayrant at laas.fr (Antoine Monmayrant) Date: Tue, 16 Feb 2016 13:12:40 +0100 Subject: [Scilab-users] News: Scilab 6 Beta, VISA Toolbox, Embedded World 2016 In-Reply-To: <56C30F6F.6060803@online.no> References: <56C1DEEF.6050905@scilab-enterprises.com> <56C1F02C.7010600@scilab-enterprises.com> <56C30F6F.6060803@online.no> Message-ID: <56C31238.4060104@laas.fr> Le 02/16/2016 01:00 PM, Jan ?ge Langeland a ?crit : > On 16.02.2016 11:55, Eric Dubois wrote: >> Don?t other Scilab users share my concern? >> >> Regards >> >> ?ric. >> >> > I have a similar (but simpler) problem, with stacksize(). All my > old scripts containing stacksize('max') etc. need to be modified. > > All it will take is to keep the standard function stacksize(a) in > Scilab 6, just let it do nothing. Well, you have your fix: add the definition of a dummy stacksize() function at the beginning of your init. My 5 cents fix is this: //on older version of scilab, set the memory to the max version_numbers = getversion('scilab'); if version_numbers(1) < 6 then stacksize('max'); end that I added to all my ressource-hungry scripts. But you are right, I don't see why they did not implement a dummy stacksize() that just output a warning about the fact that it's useless, obsolete and should not be used in new code. Antoine > > Jan ? > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ Antoine Monmayrant LAAS - CNRS 7 avenue du Colonel Roche BP 54200 31031 TOULOUSE Cedex 4 FRANCE Tel:+33 5 61 33 64 59 email : antoine.monmayrant at laas.fr permanent email : antoine.monmayrant at polytechnique.org +++++++++++++++++++++++++++++++++++++++++++++++++++++++ -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Tue Feb 16 13:19:30 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Tue, 16 Feb 2016 13:19:30 +0100 Subject: [Scilab-users] News: Scilab 6 Beta, VISA Toolbox, Embedded World 2016 In-Reply-To: <56C30628.9050505@laas.fr> References: <56C1DEEF.6050905@scilab-enterprises.com> <56C1F02C.7010600@scilab-enterprises.com> <56C30628.9050505@laas.fr> Message-ID: <56C313D2.300@free.fr> Le 16/02/2016 12:21, amonmayr at laas.fr a ?crit : > Le 02/16/2016 11:55 AM, Eric Dubois a ?crit : >> .../... >> >> More worrying still, not all additions or subtractions involving null >> matrices will generate errors when switching from Scilab 5 or older >> to Scilab 6: for example, z=size([a+1 y],1) applied to the null >> matrix a will simply add 1 in Scilab 6 to the result of Scilab 5, >> without generating errors. >> . It does: --> a=[]; y = 3; z=size([a+1 y],1) operation +: Warning adding a matrix with the empty matrix will give an empty matrix result. z = 1. >> The attentive user will be alerted by the warning message generated >> by Scilab 6, but the inattentive one may not notice it or fully >> understand its consequences. >> This is why, fortunately, unworkaroundly, a new warning("stop") synopsis has been implemented. Announcements and Releases notes failed announcing and stressing on it: warningstopfunctiontest()a=[];y=3;z=size([a+1y],1)endfunctiontest() --> warning stop --> function test() > a=[]; y = 3; z=size([a+1 y],1) > endfunction --> test() operation +: Warning adding a matrix with the empty matrix will give an empty matrix result. at line 2 of function test *** Execution stopped after a warning. *** Set warning("on") to continue execution after a warning. Again and again and again, more and more publicity MUST be done about how to translate Scilab 5 code and modules into SCilab 6 code and modules. For the moment, S/E fails on that. >> .../... >> >> Don?t other Scilab users share my concern? >> . Sure i did. This is why i claimed for a warning, and for a way to get the where() trace. > Le 16/02/2016 12:21, amonmayr at laas.fr a ?crit : > > Well, I understand your concern. > However, I buy the fact that this change will make the language more > consistent. > Indeed, "ms=m+s" where m is a matrix and s a scalar gives a matrix ms > of same size than m in most cases (ie when m is not empty). > It thus makes sense that adding a scalar to an empty matrix returns an > empty matrix. > This is also the default behavior with other similar languages like > octave, matlab, julia, so it makes sense. > I think the old behavior was kind of weird. > But you are right that this is a major change that will introduce > subtle and hard to find bugs. > We should keep in mind that it's a major change (5.x->6.x) . This is why IMO all major changes should be done now, not postponed for Scilab 6.x. For my part, i will refuse reviewing all my codes several times after 6.0. For instance : http://bugzilla.scilab.org/14287 should be fixed before the final 6.0 release, or tagged WONTFIX. > and I think the last one (4.x->5.x) was even worse in terms of > backward compatibility! . I don't think so, by far. The new graphical system -- that was the main change -- was already implemented in 4. As far as i remember, 5. mainly removed the old graphical system that was still supported in addition to the new one (by the way, there are still some traces of the oldies... For instance, xset() is still unremoved, in 95% duplicate of set() that was introduced (but still with some features unported to set()) ). Regards Samuel Gougeon -------------- next part -------------- An HTML attachment was scrubbed... URL: From clement.david at scilab-enterprises.com Tue Feb 16 13:58:39 2016 From: clement.david at scilab-enterprises.com (=?ISO-8859-1?Q?Cl=E9ment?= David) Date: Tue, 16 Feb 2016 13:58:39 +0100 Subject: [Scilab-users] News: Scilab 6 Beta, VISA Toolbox, Embedded World 2016 In-Reply-To: <56C31238.4060104@laas.fr> References: <56C1DEEF.6050905@scilab-enterprises.com> <56C1F02C.7010600@scilab-enterprises.com> <56C30F6F.6060803@online.no> <56C31238.4060104@laas.fr> Message-ID: <1455627519.2703.20.camel@scilab-enterprises.com> Hello guys, Just a pointer there : about the stacksize re-introduction or not please comment on?http://bugzilla. scilab.org/show_bug.cgi?id=14266?. -- Cl?ment Le mardi 16 f?vrier 2016 ? 13:12 +0100, Antoine Monmayrant a ?crit?: > Le 02/16/2016 01:00 PM, Jan ?ge Langeland a ?crit?: > > ?On 16.02.2016 11:55, Eric Dubois wrote: > > > Don?t other Scilab users share my concern? > > > ?Regards > > > ??ric. > > > > > I have a similar (but simpler)? problem, with stacksize().?? All my old scripts containing > > stacksize('max') etc. need to be modified.? > > > > All it will take is to keep the? standard function stacksize(a)? in Scilab 6, just let it do > > nothing.? > Well, you have your fix: add the definition of a dummy stacksize() function at the beginning of > your init. > My 5 cents fix is this: > > //on older version of scilab, set the memory to the max > version_numbers = getversion('scilab'); > if? version_numbers(1) < 6 then > ??? stacksize('max'); > end > ???? > that I added to all my ressource-hungry scripts. > > But you are right, I don't see why they did not implement a dummy stacksize() that just output a > warning about the fact that it's useless, obsolete and should not be used in new code. > > Antoine > > > ? > > Jan ? > > > > > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/users > > --? > +++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > ?Antoine Monmayrant LAAS - CNRS > ?7 avenue du Colonel Roche > ?BP 54200 > ?31031 TOULOUSE Cedex 4 > ?FRANCE > > ?Tel:+33 5 61 33 64 59 > ? > ?email : antoine.monmayrant at laas.fr > ?permanent email : antoine.monmayrant at polytechnique.org > > +++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From szymon.gapa at gmail.com Tue Feb 16 14:04:00 2016 From: szymon.gapa at gmail.com (simon_46_scilab) Date: Tue, 16 Feb 2016 06:04:00 -0700 (MST) Subject: [Scilab-users] Xcos-vector size error In-Reply-To: <1455583531168-4033453.post@n3.nabble.com> References: <1455583531168-4033453.post@n3.nabble.com> Message-ID: <1455627840909-4033467.post@n3.nabble.com> Ok, I have solved the problem already. The answer is to use INTEGRAL_m block instead of INTEGRAL_f and declare proper vector of initial condicions, which in this case was 3x1 dimension - [0; 0 ; 0] for example - and then all simulation runs almost perfectly. Almost... because of problem in DEMUX and MUX part, there appears information like this "Not enough information to find port sizes. I try to find the problem". ...and then for each connection I get info: "Highlighted block(s) have connected ports with sizes that cannot be determined by the context. What is the size of this link?" ...and I have to manually tell the program what size it should expect. If anyone know how to make it run without any errors, please reply, I would be thankful But most importantly the simulation runs :) -- View this message in context: http://mailinglists.scilab.org/Xcos-vector-size-error-tp4033453p4033467.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From clement.david at scilab-enterprises.com Tue Feb 16 16:59:00 2016 From: clement.david at scilab-enterprises.com (=?ISO-8859-1?Q?Cl=E9ment?= David) Date: Tue, 16 Feb 2016 16:59:00 +0100 Subject: [Scilab-users] Xcos-vector size error In-Reply-To: <1455627840909-4033467.post@n3.nabble.com> References: <1455583531168-4033453.post@n3.nabble.com> <1455627840909-4033467.post@n3.nabble.com> Message-ID: <1455638340.2703.24.camel@scilab-enterprises.com> Hi Simon, Thanks for answering yourself :) about the port sizes prompting for MUX / DEMUX you can enforce the size on parameters using a vector notation `[1 1 1]` instead of `3`. -- Cl?ment Le mardi 16 f?vrier 2016 ? 06:04 -0700, simon_46_scilab a ?crit?: > Ok, I have solved the problem already. The answer is to use INTEGRAL_m block > instead of INTEGRAL_f and declare proper vector of initial condicions, which > in this case was 3x1 dimension - [0; 0 ; 0] for example - and then all > simulation runs almost perfectly. > > Almost... because of problem in DEMUX and MUX part, there appears > information like this > > "Not enough information to find port sizes. > ?I try to find the problem". > > ...and then for each connection I get info: > > "Highlighted block(s) have connected ports > ?with sizes that cannot be determined by the context. > ?What is the size of this link?" > > ...and I have to manually tell the program what size it should expect. > > If anyone know how to make it run without any errors, please reply, I would > be thankful > But most importantly the simulation runs :) > > > > -- > View this message in context: http://mailinglists.scilab.org/Xcos-vector-size-error-tp4033453p4033 > 467.html > Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From grocer.toolbox at gmail.com Tue Feb 16 22:06:31 2016 From: grocer.toolbox at gmail.com (Eric Dubois) Date: Tue, 16 Feb 2016 22:06:31 +0100 Subject: [Scilab-users] News: Scilab 6 Beta, VISA Toolbox, Embedded World 2016 In-Reply-To: <1455627519.2703.20.camel@scilab-enterprises.com> References: <56C1DEEF.6050905@scilab-enterprises.com> <56C1F02C.7010600@scilab-enterprises.com> <56C30F6F.6060803@online.no> <56C31238.4060104@laas.fr> <1455627519.2703.20.camel@scilab-enterprises.com> Message-ID: Thanks for the answers. I share Samuel opinion that the changes from Scilab 5 to Scilab 6 are much important than previous ones (and I have experienced all of them since starting with Scilab 2.6!). In the previous cases, functionnalities became obsolote; this time they change... This is a much more difficult to deal with I do not know, Samuel, how you plan to review all your codes. As for me this should be a daunting task: - I have arorund 1400 Scilab functions, representing something like 70 000 lines of code, containing around 20 000 additions or subtractions; so I cannot imagine reviewing all this code; - Another avenue is to devise a battery of tests covering all possible cases; this should be less costly, but could miss some relevant cases; and this means in my cases extending the battery of tests, a useful task anyway, but also costly The command warning stop seems to be a good idea for dealing with this problem, but it has also major drawbacks: you should put it in the .start file, to prevent users to generate wrong results, but this will also stop programs that work perfectly. So I do not think it will help dealing with my concern that inexperimented users could generate wrong results with a toolbox such as mine. Am I missing something? Anyway, I fully agree with Samuel that more and more publicity MUST be done about how to translate Scilab 5 code and modules into SCilab 6 code and modules, and maybe they will convince me that I have overestimated the problems... Regards ?ric 2016-02-16 13:58 GMT+01:00 Cl?ment David < clement.david at scilab-enterprises.com>: > Hello guys, > > Just a pointer there : about the stacksize re-introduction or not please > comment on http://bugzilla. > scilab.org/show_bug.cgi?id=14266 . > > -- > Cl?ment > > Le mardi 16 f?vrier 2016 ? 13:12 +0100, Antoine Monmayrant a ?crit : > > Le 02/16/2016 01:00 PM, Jan ?ge Langeland a ?crit : > > > On 16.02.2016 11:55, Eric Dubois wrote: > > > > Don?t other Scilab users share my concern? > > > > Regards > > > > ?ric. > > > > > > > I have a similar (but simpler) problem, with stacksize(). All my > old scripts containing > > > stacksize('max') etc. need to be modified. > > > > > > All it will take is to keep the standard function stacksize(a) in > Scilab 6, just let it do > > > nothing. > > Well, you have your fix: add the definition of a dummy stacksize() > function at the beginning of > > your init. > > My 5 cents fix is this: > > > > //on older version of scilab, set the memory to the max > > version_numbers = getversion('scilab'); > > if version_numbers(1) < 6 then > > stacksize('max'); > > end > > > > that I added to all my ressource-hungry scripts. > > > > But you are right, I don't see why they did not implement a dummy > stacksize() that just output a > > warning about the fact that it's useless, obsolete and should not be > used in new code. > > > > Antoine > > > > > > > > Jan ? > > > > > > > > > _______________________________________________ > > > users mailing list > > > users at lists.scilab.org > > > http://lists.scilab.org/mailman/listinfo/users > > > > -- > > +++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > Antoine Monmayrant LAAS - CNRS > > 7 avenue du Colonel Roche > > BP 54200 > > 31031 TOULOUSE Cedex 4 > > FRANCE > > > > Tel:+33 5 61 33 64 59 > > > > email : antoine.monmayrant at laas.fr > > permanent email : antoine.monmayrant at polytechnique.org > > > > +++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/users > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lambdasoftware at yahoo.es Wed Feb 17 01:04:12 2016 From: lambdasoftware at yahoo.es (AlvaroOsvaldo) Date: Tue, 16 Feb 2016 17:04:12 -0700 (MST) Subject: [Scilab-users] Installing IPT3 in Scilab on an iMac In-Reply-To: <1454419901294-4033375.post@n3.nabble.com> References: <1454419901294-4033375.post@n3.nabble.com> Message-ID: <1455667452430-4033470.post@n3.nabble.com> I have a similiar problem with IPT3 in Linux with SciLab 5.5.3, i don't believe it have a quick solucion. -- View this message in context: http://mailinglists.scilab.org/Installing-IPT3-in-Scilab-on-an-iMac-tp4033375p4033470.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From lambdasoftware at yahoo.es Wed Feb 17 01:23:14 2016 From: lambdasoftware at yahoo.es (AlvaroOsvaldo) Date: Tue, 16 Feb 2016 17:23:14 -0700 (MST) Subject: [Scilab-users] What is the future of Scilab? Message-ID: <1455668594640-4033471.post@n3.nabble.com> I am worried, in previous versions of scilab, I implemented a medium project for scientific computing with scilab at that time had many memory leaks and had been a nightmare.With the new updates that was fixed and this much better.?But now I am implementing another project involving massive image processing.And the three atoms for this, one does not work, one does not load images but the manual says they can do, and other charges but leak the computer's memory and it took me longer skirting the problem than implementing the solution. And worse, because this the system is much slower than it should.This atom memory failure it has been known, however, despite it make impraticable to use the atom for medium and large projects, makes three years that no one gets the bug.forge.scilab.org/index.php/p/IPD/issues/992/There are high expectations with Scilab 6 and I believe we will have a much better platform. But for what you know, in the meantime we will run out of many atoms, and this greatly reduces the possibility of working in scilab.What is the future of Scilab?For now, the impression I have is that the atoms are abandoned and without the atoms the usefulness of scilab is reduced a lot. -- View this message in context: http://mailinglists.scilab.org/What-is-the-future-of-Scilab-tp4033471.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. -------------- next part -------------- An HTML attachment was scrubbed... URL: From amonmayr at laas.fr Wed Feb 17 09:20:19 2016 From: amonmayr at laas.fr (amonmayr at laas.fr) Date: Wed, 17 Feb 2016 09:20:19 +0100 Subject: [Scilab-users] What is the future of Scilab? In-Reply-To: <1455668594640-4033471.post@n3.nabble.com> References: <1455668594640-4033471.post@n3.nabble.com> Message-ID: <56C42D43.5040004@laas.fr> Le 02/17/2016 01:23 AM, AlvaroOsvaldo a ?crit : > I am worried, in previous versions of scilab, I implemented a medium > project for scientific computing with scilab at that time had many > memory leaks and had been a nightmare. With the new updates that was > fixed and this much better. But now I am implementing another project > involving massive image processing. And the three atoms for this, one > does not work, one does not load images but the manual says they can > do, and other charges but leak the computer's memory and it took me > longer skirting the problem than implementing the solution. And worse, > because this the system is much slower than it should. This atom > memory failure it has been known, however, despite it make > impraticable to use the atom for medium and large projects, makes > three years that no one gets the bug. > forge.scilab.org/index.php/p/IPD/issues/992/ There are high > expectations with Scilab 6 and I believe we will have a much better > platform. But for what you know, in the meantime we will run out of > many atoms, and this greatly reduces the possibility of working in > scilab. What is the future of Scilab? For now, the impression I have > is that the atoms are abandoned and without the atoms the usefulness > of scilab is reduced a lot. Hi, I think there are two issues here: 1) The sad state of image processing toolbox with Scilab. It's terrrible. Image processing with Scilab is a nightmare. Every other language I use is far better than Scilab in this area (even extremely young language like Julia offers a better experience. The 3 toolboxes are either broken, unmaintained or difficult (or impossible) to install. And the experience is even worse under Linux (IPD for example requires a very old version of opencv to be manually installed under Linux which is a daunting task for most user and which introduces many compatibility issues with other softwares relying on opencv). 2) The lack of information on the life (or lack of life) for a given atoms module. I know some information is available on the atoms website, but I've always found it difficult to determine whether the package was long dead or under active development. There are some long dead modules that are still listed alongside with actively maintained ones and that show excellent rating. It's a bit confusing. Concerning the first issue, image processing with scilab, I think a basic core image support should be part of scilab. Antoine > ------------------------------------------------------------------------ > View this message in context: What is the future of Scilab? > > Sent from the Scilab users - Mailing Lists Archives mailing list > archive > > at Nabble.com. > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From alex_jameson48 at hotmail.com Wed Feb 17 10:26:28 2016 From: alex_jameson48 at hotmail.com (jamesona) Date: Wed, 17 Feb 2016 02:26:28 -0700 (MST) Subject: [Scilab-users] Installing IPT3 in Scilab on an iMac In-Reply-To: <1455667452430-4033470.post@n3.nabble.com> References: <1454419901294-4033375.post@n3.nabble.com> <1455667452430-4033470.post@n3.nabble.com> Message-ID: <1455701188817-4033473.post@n3.nabble.com> Version 6 beta version is out now, unfortunately on my iMac it bounces a couple of times and thats it! -- View this message in context: http://mailinglists.scilab.org/Installing-IPT3-in-Scilab-on-an-iMac-tp4033375p4033473.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From amca01 at gmail.com Wed Feb 17 12:21:50 2016 From: amca01 at gmail.com (Alasdair McAndrew) Date: Wed, 17 Feb 2016 22:21:50 +1100 Subject: [Scilab-users] What is the future of Scilab? In-Reply-To: <56C42D43.5040004@laas.fr> References: <1455668594640-4033471.post@n3.nabble.com> <56C42D43.5040004@laas.fr> Message-ID: The poor quality of image processing toolboxes is what turned me off Scilab to GNU Octave, which has a very good imaging toolbox. Or Python, which with its various imaging libraries and scientific/numeric libraries is now a serious competitor for matrix-oriented software like Matlab/Scilab/Octave. I've written two image processing textbooks, and at no time has Scilab ever been a serious contender for their software. On Wed, Feb 17, 2016 at 7:20 PM, wrote: > Le 02/17/2016 01:23 AM, AlvaroOsvaldo a ?crit : > > I am worried, in previous versions of scilab, I implemented a medium > project for scientific computing with scilab at that time had many memory > leaks and had been a nightmare. With the new updates that was fixed and > this much better. But now I am implementing another project involving > massive image processing. And the three atoms for this, one does not work, > one does not load images but the manual says they can do, and other charges > but leak the computer's memory and it took me longer skirting the problem > than implementing the solution. And worse, because this the system is much > slower than it should. This atom memory failure it has been known, however, > despite it make impraticable to use the atom for medium and large projects, > makes three years that no one gets the bug. > forge.scilab.org/index.php/p/IPD/issues/992/ There are high expectations > with Scilab 6 and I believe we will have a much better platform. But for > what you know, in the meantime we will run out of many atoms, and this > greatly reduces the possibility of working in scilab. What is the future of > Scilab? For now, the impression I have is that the atoms are abandoned and > without the atoms the usefulness of scilab is reduced a lot. > > > Hi, > > I think there are two issues here: > > 1) The sad state of image processing toolbox with Scilab. It's terrrible. > Image processing with Scilab is a nightmare. Every other language I use is > far better than Scilab in this area (even extremely young language like > Julia offers a better experience. The 3 toolboxes are either broken, > unmaintained or difficult (or impossible) to install. And the experience is > even worse under Linux (IPD for example requires a very old version of > opencv to be manually installed under Linux which is a daunting task for > most user and which introduces many compatibility issues with other > softwares relying on opencv). > > 2) The lack of information on the life (or lack of life) for a given atoms > module. I know some information is available on the atoms website, but I've > always found it difficult to determine whether the package was long dead or > under active development. There are some long dead modules that are still > listed alongside with actively maintained ones and that show excellent > rating. It's a bit confusing. > > Concerning the first issue, image processing with scilab, I think a basic > core image support should be part of scilab. > > Antoine > > > > > ------------------------------ > View this message in context: What is the future of Scilab? > > Sent from the Scilab users - Mailing Lists Archives mailing list archive > > at Nabble.com. > > > _______________________________________________ > users mailing listusers at lists.scilab.orghttp://lists.scilab.org/mailman/listinfo/users > > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > > -- [image: http://www.facebook.com/alasdairmcandrew] [image: https://twitter.com/amca01] -------------- next part -------------- An HTML attachment was scrubbed... URL: From p.muehlmann at gmail.com Wed Feb 17 14:24:13 2016 From: p.muehlmann at gmail.com (=?UTF-8?Q?Philipp_M=C3=BChlmann?=) Date: Wed, 17 Feb 2016 14:24:13 +0100 Subject: [Scilab-users] What is the future of Scilab? In-Reply-To: References: <1455668594640-4033471.post@n3.nabble.com> <56C42D43.5040004@laas.fr> Message-ID: Quote: ''Concerning the first issue, image processing with scilab, I think a basic core image support should be part of scilab.'' Well, agreed to this. However here a different approach: I wonder if it couldn't be helpful to connect Scilab with a native Image processing Programm...like Inkscape. Why trying to convert Scilab into a image processing tool, while there are dedicated programs for it? Yes I know: It might be better to have everything in one package, beeing independent from other Software. As I use IPD very much I'm glad to have this available. I just have to think about a discussion about one complaining about Images, trying to manage his images with MS-Word instead of using a proper Software. Basic Image processing functions like rotate, shift, etc. might be done using the "dos" command and Inkscape as well. BR Philipp 2016-02-17 12:21 GMT+01:00 Alasdair McAndrew : > The poor quality of image processing toolboxes is what turned me off > Scilab to GNU Octave, which has a very good imaging toolbox. Or Python, > which with its various imaging libraries and scientific/numeric libraries > is now a serious competitor for matrix-oriented software like > Matlab/Scilab/Octave. I've written two image processing textbooks, and at > no time has Scilab ever been a serious contender for their software. > > On Wed, Feb 17, 2016 at 7:20 PM, wrote: > >> Le 02/17/2016 01:23 AM, AlvaroOsvaldo a ?crit : >> >> I am worried, in previous versions of scilab, I implemented a medium >> project for scientific computing with scilab at that time had many memory >> leaks and had been a nightmare. With the new updates that was fixed and >> this much better. But now I am implementing another project involving >> massive image processing. And the three atoms for this, one does not work, >> one does not load images but the manual says they can do, and other charges >> but leak the computer's memory and it took me longer skirting the problem >> than implementing the solution. And worse, because this the system is much >> slower than it should. This atom memory failure it has been known, however, >> despite it make impraticable to use the atom for medium and large projects, >> makes three years that no one gets the bug. >> forge.scilab.org/index.php/p/IPD/issues/992/ There are high expectations >> with Scilab 6 and I believe we will have a much better platform. But for >> what you know, in the meantime we will run out of many atoms, and this >> greatly reduces the possibility of working in scilab. What is the future of >> Scilab? For now, the impression I have is that the atoms are abandoned and >> without the atoms the usefulness of scilab is reduced a lot. >> >> >> Hi, >> >> I think there are two issues here: >> >> 1) The sad state of image processing toolbox with Scilab. It's terrrible. >> Image processing with Scilab is a nightmare. Every other language I use is >> far better than Scilab in this area (even extremely young language like >> Julia offers a better experience. The 3 toolboxes are either broken, >> unmaintained or difficult (or impossible) to install. And the experience is >> even worse under Linux (IPD for example requires a very old version of >> opencv to be manually installed under Linux which is a daunting task for >> most user and which introduces many compatibility issues with other >> softwares relying on opencv). >> >> 2) The lack of information on the life (or lack of life) for a given >> atoms module. I know some information is available on the atoms website, >> but I've always found it difficult to determine whether the package was >> long dead or under active development. There are some long dead modules >> that are still listed alongside with actively maintained ones and that show >> excellent rating. It's a bit confusing. >> >> Concerning the first issue, image processing with scilab, I think a basic >> core image support should be part of scilab. >> >> Antoine >> >> >> >> >> ------------------------------ >> View this message in context: What is the future of Scilab? >> >> Sent from the Scilab users - Mailing Lists Archives mailing list archive >> >> at Nabble.com. >> >> >> _______________________________________________ >> users mailing listusers at lists.scilab.orghttp://lists.scilab.org/mailman/listinfo/users >> >> >> >> >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> http://lists.scilab.org/mailman/listinfo/users >> >> > > > -- > [image: http://www.facebook.com/alasdairmcandrew] [image: > https://twitter.com/amca01] > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > > -- There we have the salad. -------------- next part -------------- An HTML attachment was scrubbed... URL: From antoine.monmayrant at laas.fr Wed Feb 17 14:34:55 2016 From: antoine.monmayrant at laas.fr (Antoine Monmayrant) Date: Wed, 17 Feb 2016 14:34:55 +0100 Subject: [Scilab-users] What is the future of Scilab? In-Reply-To: References: <1455668594640-4033471.post@n3.nabble.com> <56C42D43.5040004@laas.fr> Message-ID: <56C476FF.4020709@laas.fr> Le 02/17/2016 02:24 PM, Philipp M?hlmann a ?crit : > Quote: > > ''Concerning the first issue, image processing with scilab, I think a > basic core image support should be part of scilab.'' > > Well, agreed to this. > > > However here a different approach: > > I wonder if it couldn't be helpful to connect Scilab with a native > Image processing Programm...like Inkscape. > > Why trying to convert Scilab into a image processing tool, while there > are dedicated programs for it? > > Yes I know: It might be better to have everything in one package, > beeing independent from other Software. > As I use IPD very much I'm glad to have this available. > > I just have to think about a discussion about one complaining about > Images, trying to manage his images with MS-Word instead of using a > proper Software. > > > Basic Image processing functions like rotate, shift, etc. might be > done using the "dos" command and Inkscape as well. Hi Philipp, I think we are not talking about the same kind of processing here. Image processing in the context of Scilab is more opencv-like than inkscape-like. I want to import into scilab an image (3*8bits RGB bmp, 3*32bits RGB bmp, 16bits grayscale TIFF, ...) and map it to the most relevant variable in scilab (HxWX3 hypermatrix of uint8 for HxW 8bitRGB bmp, ...), in order to do some number crunching on the data contained in the image. It's not really cropping, rotating or some sort of "photoshoping" that I need, it's basically a way to "process" (as in signal processing). Cheers, Antoine > > > BR > Philipp > > > > > > > > > > > > > > 2016-02-17 12:21 GMT+01:00 Alasdair McAndrew >: > > The poor quality of image processing toolboxes is what turned me > off Scilab to GNU Octave, which has a very good imaging toolbox. > Or Python, which with its various imaging libraries and > scientific/numeric libraries is now a serious competitor for > matrix-oriented software like Matlab/Scilab/Octave. I've written > two image processing textbooks, and at no time has Scilab ever > been a serious contender for their software. > > On Wed, Feb 17, 2016 at 7:20 PM, > wrote: > > Le 02/17/2016 01:23 AM, AlvaroOsvaldo a ?crit : >> I am worried, in previous versions of scilab, I implemented a >> medium project for scientific computing with scilab at that >> time had many memory leaks and had been a nightmare. With the >> new updates that was fixed and this much better. But now I >> am implementing another project involving massive image >> processing. And the three atoms for this, one does not work, >> one does not load images but the manual says they can do, and >> other charges but leak the computer's memory and it took me >> longer skirting the problem than implementing the solution. >> And worse, because this the system is much slower than it >> should. This atom memory failure it has been known, however, >> despite it make impraticable to use the atom for medium and >> large projects, makes three years that no one gets the bug. >> forge.scilab.org/index.php/p/IPD/issues/992/ >> There >> are high expectations with Scilab 6 and I believe we will >> have a much better platform. But for what you know, in the >> meantime we will run out of many atoms, and this greatly >> reduces the possibility of working in scilab. What is the >> future of Scilab? For now, the impression I have is that the >> atoms are abandoned and without the atoms the usefulness of >> scilab is reduced a lot. > > Hi, > > I think there are two issues here: > > 1) The sad state of image processing toolbox with Scilab. It's > terrrible. Image processing with Scilab is a nightmare. Every > other language I use is far better than Scilab in this area > (even extremely young language like Julia offers a better > experience. The 3 toolboxes are either broken, unmaintained or > difficult (or impossible) to install. And the experience is > even worse under Linux (IPD for example requires a very old > version of opencv to be manually installed under Linux which > is a daunting task for most user and which introduces many > compatibility issues with other softwares relying on opencv). > > 2) The lack of information on the life (or lack of life) for a > given atoms module. I know some information is available on > the atoms website, but I've always found it difficult to > determine whether the package was long dead or under active > development. There are some long dead modules that are still > listed alongside with actively maintained ones and that show > excellent rating. It's a bit confusing. > > Concerning the first issue, image processing with scilab, I > think a basic core image support should be part of scilab. > > Antoine > > > > >> ------------------------------------------------------------------------ >> View this message in context: What is the future of Scilab? >> >> Sent from the Scilab users - Mailing Lists Archives mailing >> list archive >> >> at Nabble.com. >> >> >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> http://lists.scilab.org/mailman/listinfo/users > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > > > > > -- > http://www.facebook.com/alasdairmcandrew > https://twitter.com/amca01 > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > > > > > -- > There we have the salad. -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ Antoine Monmayrant LAAS - CNRS 7 avenue du Colonel Roche BP 54200 31031 TOULOUSE Cedex 4 FRANCE Tel:+33 5 61 33 64 59 email : antoine.monmayrant at laas.fr permanent email : antoine.monmayrant at polytechnique.org +++++++++++++++++++++++++++++++++++++++++++++++++++++++ -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Wed Feb 17 14:55:06 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Wed, 17 Feb 2016 14:55:06 +0100 Subject: [Scilab-users] disp(a,b,c) => display a, b, and finally c ; not c, b and then a <= Re: News: Scilab 6 Beta, VISA Toolbox, Embedded World 2016 In-Reply-To: <56C1F02C.7010600@scilab-enterprises.com> References: <56C1DEEF.6050905@scilab-enterprises.com> <56C1F02C.7010600@scilab-enterprises.com> Message-ID: <56C47BBA.6030200@free.fr> Hello Scilab Team, The impact of the changed []+a is pointed in this thread. Since an extensive code review will be needed from Scilab 5 to Scilab 6, some other long standing bugs could be fixed before the final release. Already, * The 1./m trick is fixed (now parsed as 1 ./m rather than 1. / m)): Great! * The space between the minus sign and the absolute mantissa is removed when numbers are displayed in the console: Great! Copying/pasting will now be straightforward. * ... But still, for instance, the unconsistent display by disp() inversed wrt to the order of its parameters is still there. Wouldn't it be the best moment to correct it as well? http://bugzilla.scilab.org/5512 http://bugzilla.scilab.org/9463 http://bugzilla.scilab.org/13447 The impact of this correction on existing codes would be much less than for []+a, but would fix a ridiculous behavior met by every user (not ones of a highly specific Scilab function or feature). Best regards Samuel Gougeon Le 15/02/2016 16:35, Yann DEBRAY a ?crit : > > Hello Scilab user, > > It has been a while since we last shared news with you. Here are some > recent updates we hope you will like. > > > Scilab 6 Beta > > Scilab 6.0 is a major new release of Scilab, the open source modeling > & simulation platform. This beta version is a preview for all users, > commercial as well as community. > > *What's new: * > > --> New computation coreenabling bigger data sets > --> Improved Xcos allowing larger models > --> Utilities for development productivity (debugger, profiler and > coverage) > > To provide relevant informations to the user, we also introduced a new > view called "Newsfeed". > The release will come soon, so feel free to give us feedback about > your experience. > > Find out more > > > Signal acquisition and instrument control > with the Scilab VISA Toolbox (beta version) > > > In partnership with National Instruments, we have developed a > Scilab interface for measurement devices from leading > manufacturers (National Instruments, Agilent/HP, ... ) > > Here is the first version of this VISA toolbox for signal acquisition > and instrument control. This is a beta version: your feedbacks are > welcome. > > TheVirtual Instrument Software Architecture > (VISA) is a standard for configuring, > programming, and troubleshooting instrumentation systems comprising > GPIB, VXI, PXI, Serial, Ethernet, and/or USB interfaces. VISA provides > the programming interface between the hardware and development > environments. > > Find out more > > > Event Embedded World // 23-25 February 2016, Nuremberg > > Starting with the largest embedded systems' event of the year:Embedded > World 2016 > 23 - 25 February 2016 in Nuremberg, Germany > > We will be present on the booth of Evidence (Hall 4 / 4-545 > _)_ and > Emmtrix (Hall 4A, booth 520d > _)_ > > Scilab has many applications in the field of embedded systems : > --> post-processing of test data > --> automation of tasks > -->prototyping of control algorithms > -->identification of systems parameter > -->simulation of control systems > --> embedded code generation > > Here are some use cases of Scilab in this field, from our last ScilabTEC : > > > > * ZYNQ-7000 High Performance Electric Drive and Silicon Carbide > Multilevel inverter with Scilab Hardware-in-the-loop > > * E4Coder on Scilab: State Machines simulation and GUI prototyping > > * Can programming of multi-core systems be easier, please? > > * Real-time control and measurement applications > > > Prior to this important event, we want to highlight some Scilab > partners in the world of Embedded Systems which will be present at > Embedded World: > > * Evidence > , > * Emmtrix > , > * Xilinx > * LCM (present at Microchip's booth) > > Please do contact us, to set up a time for some quality exchange. > > Meet us @ Embedded World > > > -- > The Scilab Team > > > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From amonmayr at laas.fr Wed Feb 17 15:12:38 2016 From: amonmayr at laas.fr (amonmayr at laas.fr) Date: Wed, 17 Feb 2016 15:12:38 +0100 Subject: [Scilab-users] disp(a,b,c) => display a, b, and finally c ; not c, b and then a <= Re: News: Scilab 6 Beta, VISA Toolbox, Embedded World 2016 In-Reply-To: <56C47BBA.6030200@free.fr> References: <56C1DEEF.6050905@scilab-enterprises.com> <56C1F02C.7010600@scilab-enterprises.com> <56C47BBA.6030200@free.fr> Message-ID: <56C47FD6.9040504@laas.fr> Le 02/17/2016 02:55 PM, Samuel Gougeon a ?crit : > Hello Scilab Team, > > The impact of the changed []+a is pointed in this thread. > > Since an extensive code review will be needed from Scilab 5 to Scilab > 6, some other long standing bugs could be fixed before the final release. > Already, > > * The 1./m trick is fixed (now parsed as 1 ./m rather than 1. / m)): > Great! > * The space between the minus sign and the absolute mantissa is > removed when numbers are displayed in the console: Great! > Copying/pasting will now be straightforward. > * ... > > But still, for instance, the unconsistent display by disp() inversed > wrt to the order of its parameters is still there. Wouldn't it be the > best moment to correct it as well? > http://bugzilla.scilab.org/5512 http://bugzilla.scilab.org/9463 > http://bugzilla.scilab.org/13447 What about adding to the list the infamous forgotten ";" after a huge matrix, aka "huge matrix display scrolling of death"? See http://mailinglists.scilab.org/Scilab-users-Accidentally-displaying-huge-matrices-tc4032315.html#a4032319 and http://bugzilla.scilab.org/show_bug.cgi?id=6286 It seems that a patch was proposed but never merged? I have plenty of time to write this email because my scilab session is currently trying to list every value in my 2775x570 matrix. I am not kidding, I did it again, forgot the ";" after a huge matrix, arggh! Antoine PS:ah, the last value in my matrix just showed up, back to work! > > The impact of this correction on existing codes would be much less > than for []+a, but would fix a ridiculous behavior met by every user > (not ones of a highly specific Scilab function or feature). > > Best regards > Samuel Gougeon > > > Le 15/02/2016 16:35, Yann DEBRAY a ?crit : >> >> Hello Scilab user, >> >> It has been a while since we last shared news with you. Here are some >> recent updates we hope you will like. >> >> >> Scilab 6 Beta >> >> Scilab 6.0 is a major new release of Scilab, the open source modeling >> & simulation platform. This beta version is a preview for all users, >> commercial as well as community. >> >> *What's new: * >> >> --> New computation coreenabling bigger data sets >> --> Improved Xcos allowing larger models >> --> Utilities for development productivity (debugger, profiler and >> coverage) >> >> To provide relevant informations to the user, we also introduced a >> new view called "Newsfeed". >> The release will come soon, so feel free to give us feedback about >> your experience. >> >> Find out more >> >> >> Signal acquisition and instrument control >> with the Scilab VISA Toolbox (beta version) >> >> >> In partnership with National Instruments, we have developed a >> Scilab interface for measurement devices from leading >> manufacturers (National Instruments, Agilent/HP, ... ) >> >> Here is the first version of this VISA toolbox for signal acquisition >> and instrument control. This is a beta version: your feedbacks are >> welcome. >> >> TheVirtual Instrument Software Architecture >> (VISA) is a standard for configuring, >> programming, and troubleshooting instrumentation systems comprising >> GPIB, VXI, PXI, Serial, Ethernet, and/or USB interfaces. VISA >> provides the programming interface between the hardware and >> development environments. >> >> Find out more >> >> >> Event Embedded World // 23-25 February 2016, Nuremberg >> >> Starting with the largest embedded systems' event of the >> year:Embedded World 2016 >> 23 - 25 February 2016 in Nuremberg, Germany >> >> We will be present on the booth of Evidence (Hall 4 / 4-545 >> _)_ and >> Emmtrix (Hall 4A, booth 520d >> _)_ >> >> Scilab has many applications in the field of embedded systems : >> --> post-processing of test data >> --> automation of tasks >> -->prototyping of control algorithms >> -->identification of systems parameter >> -->simulation of control systems >> --> embedded code generation >> >> Here are some use cases of Scilab in this field, from our last >> ScilabTEC : >> >> >> >> * ZYNQ-7000 High Performance Electric Drive and Silicon Carbide >> Multilevel inverter with Scilab Hardware-in-the-loop >> >> * E4Coder on Scilab: State Machines simulation and GUI prototyping >> >> * Can programming of multi-core systems be easier, please? >> >> * Real-time control and measurement applications >> >> >> Prior to this important event, we want to highlight some Scilab >> partners in the world of Embedded Systems which will be present at >> Embedded World: >> >> * Evidence >> , >> * Emmtrix >> , >> * Xilinx >> * LCM (present at Microchip's >> booth) >> >> Please do contact us, to set up a time for some quality exchange. >> >> Meet us @ Embedded World >> >> >> -- >> The Scilab Team >> >> >> >> >> >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> http://lists.scilab.org/mailman/listinfo/users > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ Antoine Monmayrant LAAS - CNRS 7 avenue du Colonel Roche BP 54200 31031 TOULOUSE Cedex 4 FRANCE Tel:+33 5 61 33 64 59 email : antoine.monmayrant at laas.fr permanent email : antoine.monmayrant at polytechnique.org +++++++++++++++++++++++++++++++++++++++++++++++++++++++ -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Wed Feb 17 15:27:57 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Wed, 17 Feb 2016 15:27:57 +0100 Subject: [Scilab-users] disp(a,b,c) => display a, b, and finally c ; not c, b and then a <= Re: News: Scilab 6 Beta, VISA Toolbox, Embedded World 2016 In-Reply-To: <56C47FD6.9040504@laas.fr> References: <56C1DEEF.6050905@scilab-enterprises.com> <56C1F02C.7010600@scilab-enterprises.com> <56C47BBA.6030200@free.fr> <56C47FD6.9040504@laas.fr> Message-ID: <56C4836D.9020108@free.fr> Le 17/02/2016 15:12, amonmayr at laas.fr a ?crit : > > What about adding to the list the infamous forgotten ";" after a huge > matrix, aka "huge matrix display scrolling of death"? > See > http://mailinglists.scilab.org/Scilab-users-Accidentally-displaying-huge-matrices-tc4032315.html#a4032319 > and http://bugzilla.scilab.org/show_bug.cgi?id=6286 > It seems that a patch was proposed but never merged? You can customize your lines() in your .ini / .scilab. It is not infamous to do. Unfortunately, disp() has no order option that could be tuned in the .ini. When reviewing your code, you wouldn't need to remove existing ";" because the display of big matrices would be abstracted. An abstracted display could be implemented later. SG -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Wed Feb 17 15:50:32 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Wed, 17 Feb 2016 15:50:32 +0100 Subject: [Scilab-users] disp(a,b,c) => display a, b, and finally c ; not c, b and then a <= Re: News: Scilab 6 Beta, VISA Toolbox, Embedded World 2016 In-Reply-To: <56C47FD6.9040504@laas.fr> References: <56C1DEEF.6050905@scilab-enterprises.com> <56C1F02C.7010600@scilab-enterprises.com> <56C47BBA.6030200@free.fr> <56C47FD6.9040504@laas.fr> Message-ID: <56C488B8.80504@free.fr> Le 17/02/2016 15:12, amonmayr at laas.fr a ?crit : > > What about adding to the list the infamous forgotten ";" after a huge > matrix, aka "huge matrix display scrolling of death"? > See > http://mailinglists.scilab.org/Scilab-users-Accidentally-displaying-huge-matrices-tc4032315.html#a4032319 > and http://bugzilla.scilab.org/show_bug.cgi?id=6286 > It seems that a patch was proposed but never merged? . As reported here : http://bugzilla.scilab.org/3817 , the true issue is that the display can't be interrupted with CTRL+C It can also be fixed later without needing user code review. SG -------------- next part -------------- An HTML attachment was scrubbed... URL: From antoine.monmayrant at laas.fr Wed Feb 17 16:36:16 2016 From: antoine.monmayrant at laas.fr (Antoine Monmayrant) Date: Wed, 17 Feb 2016 16:36:16 +0100 Subject: [Scilab-users] disp(a,b,c) => display a, b, and finally c ; not c, b and then a <= Re: News: Scilab 6 Beta, VISA Toolbox, Embedded World 2016 In-Reply-To: <56C4836D.9020108@free.fr> References: <56C1DEEF.6050905@scilab-enterprises.com> <56C1F02C.7010600@scilab-enterprises.com> <56C47BBA.6030200@free.fr> <56C47FD6.9040504@laas.fr> <56C4836D.9020108@free.fr> Message-ID: <56C49370.6090806@laas.fr> Le 02/17/2016 03:27 PM, Samuel Gougeon a ?crit : > Le 17/02/2016 15:12, amonmayr at laas.fr a ?crit : >> >> What about adding to the list the infamous forgotten ";" after a huge >> matrix, aka "huge matrix display scrolling of death"? >> See >> http://mailinglists.scilab.org/Scilab-users-Accidentally-displaying-huge-matrices-tc4032315.html#a4032319 >> and http://bugzilla.scilab.org/show_bug.cgi?id=6286 >> It seems that a patch was proposed but never merged? > > You can customize your lines() in your .ini / .scilab. It is not > infamous to do. Nope, that's not a decent solution. As discussed previously, if you set lines() to a low value to avoid the "missing ; of death", you might break a lot of your script that generates some outuput on the console. I've done it in the past, and it's never good to find out in the morning that the script that was supposed to run all night (and that reports progress from time to time) has stopped after half an hour, asking whether it should go own with the output on the console. The default behaviour of the display should change and personally, I like the solution adopted by julia. Antoine > Unfortunately, disp() has no order option that could be tuned in the .ini. > When reviewing your code, you wouldn't need to remove existing ";" > because the display of big matrices would be abstracted. An abstracted > display could be implemented later. > > SG > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ Antoine Monmayrant LAAS - CNRS 7 avenue du Colonel Roche BP 54200 31031 TOULOUSE Cedex 4 FRANCE Tel:+33 5 61 33 64 59 email : antoine.monmayrant at laas.fr permanent email : antoine.monmayrant at polytechnique.org +++++++++++++++++++++++++++++++++++++++++++++++++++++++ -------------- next part -------------- An HTML attachment was scrubbed... URL: From j-lan at online.no Wed Feb 17 17:10:41 2016 From: j-lan at online.no (JLan) Date: Wed, 17 Feb 2016 09:10:41 -0700 (MST) Subject: [Scilab-users] Scilab 6.0.0 Beta crashed by input() Message-ID: <1455725441162-4033482.post@n3.nabble.com> Is this just on my machine? a=input('How can this line cause Scilab 6.0.0 Beta to crash when pressing enter?:'); Result in error message: Scilab 6.0.0(GUI) has stopped working - close program. Jan ? -- View this message in context: http://mailinglists.scilab.org/Scilab-6-0-0-Beta-crashed-by-input-tp4033482.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From cfuttrup at gmail.com Wed Feb 17 17:45:16 2016 From: cfuttrup at gmail.com (Claus Futtrup) Date: Wed, 17 Feb 2016 17:45:16 +0100 Subject: [Scilab-users] disp(a,b,c) => display a, b, and finally c ; not c, b and then a <= Re: News: Scilab 6 Beta, VISA Toolbox, Embedded World 2016 In-Reply-To: <56C47BBA.6030200@free.fr> References: <56C1DEEF.6050905@scilab-enterprises.com> <56C1F02C.7010600@scilab-enterprises.com> <56C47BBA.6030200@free.fr> Message-ID: <56C4A39C.8090802@gmail.com> Hi there With Samuel pointing to bug 5512, I see that disp() behaves in a surprising way. My approach to deciding what Scilab should do would be to achieve the reaction from the software which is least surprising to the users. Scilab 6 is a good opportunity to modify such behavior, if the modification means that the behavior becomes less surprising. As mentioned in another thread, which I agree to - it's OK to break code when entering a new major release. Hereafter backwards compatibility is recommended. Best regards, Claus On 17-02-2016 14:55, Samuel Gougeon wrote: > Hello Scilab Team, > > The impact of the changed []+a is pointed in this thread. > > Since an extensive code review will be needed from Scilab 5 to Scilab > 6, some other long standing bugs could be fixed before the final release. > Already, > > * The 1./m trick is fixed (now parsed as 1 ./m rather than 1. / m)): > Great! > * The space between the minus sign and the absolute mantissa is > removed when numbers are displayed in the console: Great! > Copying/pasting will now be straightforward. > * ... > > But still, for instance, the unconsistent display by disp() inversed > wrt to the order of its parameters is still there. Wouldn't it be the > best moment to correct it as well? > http://bugzilla.scilab.org/5512 http://bugzilla.scilab.org/9463 > http://bugzilla.scilab.org/13447 > > The impact of this correction on existing codes would be much less > than for []+a, but would fix a ridiculous behavior met by every user > (not ones of a highly specific Scilab function or feature). > > Best regards > Samuel Gougeon > > > Le 15/02/2016 16:35, Yann DEBRAY a ?crit : >> >> Hello Scilab user, >> >> It has been a while since we last shared news with you. Here are some >> recent updates we hope you will like. >> >> >> Scilab 6 Beta >> >> Scilab 6.0 is a major new release of Scilab, the open source modeling >> & simulation platform. This beta version is a preview for all users, >> commercial as well as community. >> >> *What's new: * >> >> --> New computation coreenabling bigger data sets >> --> Improved Xcos allowing larger models >> --> Utilities for development productivity (debugger, profiler and >> coverage) >> >> To provide relevant informations to the user, we also introduced a >> new view called "Newsfeed". >> The release will come soon, so feel free to give us feedback about >> your experience. >> >> Find out more >> >> >> Signal acquisition and instrument control >> with the Scilab VISA Toolbox (beta version) >> >> >> In partnership with National Instruments, we have developed a >> Scilab interface for measurement devices from leading >> manufacturers (National Instruments, Agilent/HP, ... ) >> >> Here is the first version of this VISA toolbox for signal acquisition >> and instrument control. This is a beta version: your feedbacks are >> welcome. >> >> TheVirtual Instrument Software Architecture >> (VISA) is a standard for configuring, >> programming, and troubleshooting instrumentation systems comprising >> GPIB, VXI, PXI, Serial, Ethernet, and/or USB interfaces. VISA >> provides the programming interface between the hardware and >> development environments. >> >> Find out more >> >> >> Event Embedded World // 23-25 February 2016, Nuremberg >> >> Starting with the largest embedded systems' event of the >> year:Embedded World 2016 >> 23 - 25 February 2016 in Nuremberg, Germany >> >> We will be present on the booth of Evidence (Hall 4 / 4-545 >> _)_ and >> Emmtrix (Hall 4A, booth 520d >> _)_ >> >> Scilab has many applications in the field of embedded systems : >> --> post-processing of test data >> --> automation of tasks >> -->prototyping of control algorithms >> -->identification of systems parameter >> -->simulation of control systems >> --> embedded code generation >> >> Here are some use cases of Scilab in this field, from our last >> ScilabTEC : >> >> >> >> * ZYNQ-7000 High Performance Electric Drive and Silicon Carbide >> Multilevel inverter with Scilab Hardware-in-the-loop >> >> * E4Coder on Scilab: State Machines simulation and GUI prototyping >> >> * Can programming of multi-core systems be easier, please? >> >> * Real-time control and measurement applications >> >> >> Prior to this important event, we want to highlight some Scilab >> partners in the world of Embedded Systems which will be present at >> Embedded World: >> >> * Evidence >> , >> * Emmtrix >> , >> * Xilinx >> * LCM (present at Microchip's >> booth) >> >> Please do contact us, to set up a time for some quality exchange. >> >> Meet us @ Embedded World >> >> >> -- >> The Scilab Team >> >> >> >> >> >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> http://lists.scilab.org/mailman/listinfo/users > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Wed Feb 17 18:22:11 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Wed, 17 Feb 2016 18:22:11 +0100 Subject: [Scilab-users] a{i, j} specific extraction syntax with {} should not be introduced Message-ID: <56C4AC43.6040408@free.fr> Hello, Scilab 6.0 is being to introduce a very specific extraction syntax for cells. Is it really worthwhile to do so, when everywhere else Scilab 6.0 tries to remove features that are too specific, and works to improve consistency? When we use a list -- that is the simplest heterogeneous container -- and address a component of it, we do it with (). We do not need specific extractors like [] or {}. Moreover, this does not return a list with a single component, but the component itself, unwrapped from its container: L = list(%pi, %i, %t, "abcd") L(2) // => returns %i, not list(%i) -->L(2) ans = i -->typeof(L(2)) ans = constant But the syntax that is being introduced for cells with 6.0.0 is not consistent with that: C = {%pi %i ; %t "abcd"} C(3) // returns a cell instead of directly the component %t typeof(C(3)) // A specific addressing is introduced /just to strip off the cell container //OR convert it to a list/(): C{3} // returns %i (...not list(%i)) C{1,:} // returns list(%pi, %i) --> C = {%pi %i ; %t "abcd"} C = [1x1 constant] [1x1 constant] [1x1 boolean ] [1x1 string ] --> C(3) ans = [1x1 constant] --> typeof(C(3)) ans = ce --> C{3} ans = i *After C(3), who will need a cell with a single component, instead of the component itself?* As, again, who after L = list(%pi, %i, %t, "abcd"), L(2) would expect list(%i) instead of %i ? This has never been reported as a wish. When several components are extracted, {} returns a list and therefore looses the sizes of the extraction. This is a poor result. Do we really need to introduce just {} to get it? To get the same when needed, why not "simply" implementing a similar behavior of the ":" linearized selector as for lists with *C(:)*? Or more simply, a cell2list() function could be applied to C(i:j,m:n) **Conclusion: {} specific extract**ors* *degenerate index addressing, are unhandy and inconsistent with extraction from a list when only one component is extracted, and have a poor result when several components are extracted. As extractors, they should be removed from Scilab 6.0 and kept only as cells constructors**. **Hoping to read your own thoughts about that, Best regards Samuel Gougeon -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Wed Feb 17 18:42:59 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Wed, 17 Feb 2016 18:42:59 +0100 Subject: [Scilab-users] a{i, j} specific extraction syntax with {} should not be introduced In-Reply-To: <56C4AC43.6040408@free.fr> References: <56C4AC43.6040408@free.fr> Message-ID: <56C4B123.7060409@free.fr> Le 17/02/2016 18:22, Samuel Gougeon a ?crit : > Hello, > > Scilab 6.0 is being to introduce a very specific extraction syntax for > cells. > Is it really worthwhile to do so, when everywhere else Scilab 6.0 > tries to remove features that are too specific, and works to improve > consistency? *What about insertion?** * --> C1 = { %pi %e ; %i %z}; --> C1(1) = 3 Wrong insertion: A Cell expected: use {...} instead of (...). Why isn't this simple case silently handled, and the RHS scalar automatically wrapped in a cell to be accepted? --> C1([1 3]) = {3,"abc"} C1 = [1x1 constant] [1x1 string ] [1x1 constant] [1x1 polynomial] OK. So here, no need to use C1{..} to make the assignmentdistributive. Perfect! --> C1([1 3]) = list(3,"abc") Wrong insertion: A Cell expected: use {...} instead of (...). This should be as well accepted, as soon as length(RHS list) == length of the LHS vector of indices. Could anyone find and show any case for which the {} specific insertion or extraction syntax would be worthwhile? BR Samuel Gougeon -------------- next part -------------- An HTML attachment was scrubbed... URL: From szymon.gapa at gmail.com Wed Feb 17 23:35:15 2016 From: szymon.gapa at gmail.com (simon_46_scilab) Date: Wed, 17 Feb 2016 15:35:15 -0700 (MST) Subject: [Scilab-users] Xcos-vector size error In-Reply-To: <1455638340.2703.24.camel@scilab-enterprises.com> References: <1455583531168-4033453.post@n3.nabble.com> <1455627840909-4033467.post@n3.nabble.com> <1455638340.2703.24.camel@scilab-enterprises.com> Message-ID: <1455748515487-4033486.post@n3.nabble.com> Thank you for the answer, very helpful. [1 1 1] ->Now it's obvious ...like it always is after the puzzel has been revealed :) Simon -- View this message in context: http://mailinglists.scilab.org/Xcos-vector-size-error-tp4033453p4033486.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From antoine.monmayrant at laas.fr Thu Feb 18 08:47:27 2016 From: antoine.monmayrant at laas.fr (Antoine Monmayrant) Date: Thu, 18 Feb 2016 08:47:27 +0100 Subject: [Scilab-users] Scilab 6.0.0 Beta crashed by input() In-Reply-To: <1455725441162-4033482.post@n3.nabble.com> References: <1455725441162-4033482.post@n3.nabble.com> Message-ID: <56C5770F.9090504@laas.fr> Le 02/17/2016 05:10 PM, JLan a ?crit : > Is this just on my machine? Saddly, no! I just tried it on my machine (linux ubuntu 14.04 64bits) and bye bye scilab. Could you report a bug ? Antoine > > a=input('How can this line cause Scilab 6.0.0 Beta to crash when pressing > enter?:'); > > Result in error message: Scilab 6.0.0(GUI) has stopped working - close > program. > > Jan ? > > > > -- > View this message in context: http://mailinglists.scilab.org/Scilab-6-0-0-Beta-crashed-by-input-tp4033482.html > Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > From j-lan at online.no Thu Feb 18 09:09:08 2016 From: j-lan at online.no (=?UTF-8?Q?Jan_=c3=85ge_Langeland?=) Date: Thu, 18 Feb 2016 09:09:08 +0100 Subject: [Scilab-users] Scilab 6.0.0 Beta crashed by input() In-Reply-To: <56C5770F.9090504@laas.fr> References: <1455725441162-4033482.post@n3.nabble.com> <56C5770F.9090504@laas.fr> Message-ID: <56C57C24.6090409@online.no> On 18.02.2016 08:47, Antoine Monmayrant wrote: > Le 02/17/2016 05:10 PM, JLan a ?crit : >> Is this just on my machine? > > Saddly, no! > > I just tried it on my machine (linux ubuntu 14.04 64bits) and bye bye > scilab. > > Could you report a bug ? > > Antoine Thank you Antoine http://bugzilla.scilab.org/show_bug.cgi?id=14375 Brgds Jan ? >> >> a=input('How can this line cause Scilab 6.0.0 Beta to crash when >> pressing >> enter?:'); >> >> Result in error message: Scilab 6.0.0(GUI) has stopped working - close >> program. >> >> Jan ? >> >> >> >> -- >> View this message in context: >> http://mailinglists.scilab.org/Scilab-6-0-0-Beta-crashed-by-input-tp4033482.html >> Sent from the Scilab users - Mailing Lists Archives mailing list >> archive at Nabble.com. >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> http://lists.scilab.org/mailman/listinfo/users >> > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From cedric.delamarre at scilab-enterprises.com Thu Feb 18 11:03:04 2016 From: cedric.delamarre at scilab-enterprises.com (Cedric Delamarre) Date: Thu, 18 Feb 2016 11:03:04 +0100 Subject: [Scilab-users] a{i, j} specific extraction syntax with {} should not be introduced In-Reply-To: <56C4B123.7060409@free.fr> References: <56C4AC43.6040408@free.fr> <56C4B123.7060409@free.fr> Message-ID: <1455789784.2595.103.camel@blink> Hello Samuel, Cells are specific container which can contain any types of Scilab, but each element of a Cell matrix is a Cell. So, the rules for a Cell are same than the rules for a matrix of something. This feature is consistent with matrix extraction because when you extract from or insert to a matrix of constant, the result is a matrix of constant. For example: m = [1 2 3]; m(1:2) // extracts a matrix of constant m(4) = 4 // inserts a constant s = ["this" "is a" "string"]; s(1:2) // extracts a matrix of strings s(4) = "true?" // inserts a string a={1, %s, "test"}; a(1:2) // extracts a matrix of cells a(4) = {5} // inserts a cell This insert a cell at the forth position of "a" as you can insert a constant in a matrix of constant and not a string. For example: m(5) = "5" s(5) = 5 a(5) = 5 But, because Cells array can contain any Scilab types, we need a new operator to insert another type in a cell. a{4} = [5 5 5] This insert the matrix of constant at the forth position of "a". a{4} = {5 5 5} This insert the Cell array at the forth position of "a". a(4:6) = {5 5 5} This insert each cell elements in "a". If we apply that in your test cases, the first case returns an error because a Cell array is a matrix of a homogeneous elements. The second case is good because you insert a Cell in a Cell. The third case returns an error because of the same reason as the first one. To conclude, keep in mind, Cells array are homogeneous array of cell and not a list. Hope this helps, Le mercredi 17 f?vrier 2016 ? 18:42 +0100, Samuel Gougeon a ?crit : > Le 17/02/2016 18:22, Samuel Gougeon a ?crit : > > > Hello, > > > > Scilab 6.0 is being to introduce a very specific extraction syntax > > for cells. > > Is it really worthwhile to do so, when everywhere else Scilab 6.0 > > tries to remove features that are too specific, and works to improve > > consistency? > > What about insertion? > > --> C1 = { %pi %e ; %i %z}; > > --> C1(1) = 3 > > Wrong insertion: A Cell expected: use {...} instead of (...). > > Why isn't this simple case silently handled, and the RHS scalar > automatically wrapped in a cell to be accepted? > > > --> C1([1 3]) = {3,"abc"} > C1 = > > [1x1 constant] [1x1 string ] > [1x1 constant] [1x1 polynomial] > > > OK. So here, no need to use C1{..} to make the assignment > distributive. Perfect! > > --> C1([1 3]) = list(3,"abc") > > Wrong insertion: A Cell expected: use {...} instead of (...). > > This should be as well accepted, as soon as length(RHS list) == length > of the LHS vector of indices. > > > Could anyone find and show any case for which the {} specific > insertion or extraction syntax would be worthwhile? > > BR > Samuel Gougeon > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -- C?dric DELAMARRE Ing?nieur de d?veloppement ------------------------------------------- Scilab Enterprises 143bis rue Yves Le Coz - 78000 Versailles http://www.scilab-enterprises.com ------------------------------------------- From sgougeon at free.fr Thu Feb 18 13:45:12 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Thu, 18 Feb 2016 13:45:12 +0100 Subject: [Scilab-users] a{i, j} specific extraction syntax with {} should not be introduced In-Reply-To: <1455789784.2595.103.camel@blink> References: <56C4AC43.6040408@free.fr> <56C4B123.7060409@free.fr> <1455789784.2595.103.camel@blink> Message-ID: <56C5BCD8.4020603@free.fr> Hello C?dric, Thanks for your answer. I am aware of what cells are. I understand the reported error messages. The new {} heterogeneous concatenators are ones of the best new features that Scilab 6 offers. But i strongly disagree with the present implementation of {} as extractors and inserters, because they are not user-oriented, look useless, and are unhandy. Your answer does not provide any example that could not be dealt with () instead of {}, i.e. for which no unambiguous implementation with () could exist. I am answering to some points in the thread of your message, with a user point of view: Le 18/02/2016 11:03, Cedric Delamarre a ?crit : > Hello Samuel, > > Cells are specific container which can contain any types of Scilab, but > each element of a Cell matrix is a Cell. So, the rules for a Cell are > same than the rules for a matrix of something. > > This feature is consistent with matrix extraction because when you > extract from or insert to a matrix of constant, the result is a matrix > of constant. . Sorry, but this rational looks absolutely not user-oriented. When a user builds a cell array, he/she is aware that it is a container of mixed data, not a matrix with the same type of objects. The fact that actually all objects are wrapped in a elementary cell to look with the same type is an internal consideration. The matrix becomes a matrix of pointers toward objects. OK. Pointers have all the same type: pointer. OK. And then? If users want to deal with homogeneous pointers, they code in C/C++, not in Scilab language. There is no reason to expect extracting from a cell array, one by one, objects that all have the same type = "cell", since it is chosen to be an heterogeneous container! And the user rather wishes to use a syntax to insert or extract parts of the array in a way that is the most simple, direct, intuitive and unambiguous as possible. And so the nearest to the matrix syntax as possible. This is why addressing cells contents with the same symbols () as used for matrix, and only these ones, should be of high priority. > For example: > m = [1 2 3]; > m(1:2) // extracts a matrix of constant > m(4) = 4 // inserts a constant > s = ["this" "is a" "string"]; > s(1:2) // extracts a matrix of strings > s(4) = "true?" // inserts a string > a={1, %s, "test"}; > a(1:2) // extracts a matrix of cells > a(4) = {5} // inserts a cell Exactly the same could be done with a(4) = 5. There is absolutely no ambiguity about what the user wish to do there. Is there? > This insert a cell at the forth position of "a" as you can insert a > constant in a matrix of constant and not a string. > > For example: > m(5) = "5"// m is an homogeneous container not of type string => Error is OK > s(5) = 5// s is an homogeneous container not of type decimal => Error is OK > a(5) = 5// a is an heterogeneous container accepting *any* type of data => > This could and should be handled > > But, because Cells array can contain any Scilab types, we need a new > operator to insert another type in a cell. > > a{4} = [5 5 5] > This insert the matrix of constant at the forth position of "a". a(4) = [5 5 5] // could handle it exactly in the same way > a{4} = {5 5 5} > This insert the Cell array at the forth position of "a". a(4) = {5 5 5} // could handle it exactly in the same way. Since size([4],"*")~=size({5 5 5}, "*"), there is absolutely no ambiguity about what must be done. If there was, a(4) = { {5 5 5} } could be used. By the way, to use a syntax completely consistent, why {5 5 5} is used instead of { {5} {5} {5}} in your example? As far as i understand, the result of {5 5 5} is a 1x3 array of cells, so cells that are horizontally concatenated: External { ..} concatenate them, and the listed objects should be cells, not direct data. But { 5 5 5 } *automatically* wraps listed data in a cell before concatenating them. This is exactly the type of automatism that should be silently performed on every scalar data involved in cells, as well for extraction and insertion, what we claim for. > a(4:6) = {5 5 5} > This insert each cell elements in "a". OK for that. It is straightforward, and unambiguous. For this kind of operation, the distributive assignment is performed *with absolutely no respect with unmatching sizes/formats of the recipient and of the source*. Only the linearized indices of components are used. Example: c = {%pi %i %t ; %z "abc" list(1,"a")} --> c(:,1) = { 1 2 } // an horizontal array feeds a column, and *it is fine and OK!* c = [1x1 constant] [1x1 constant] [1x1 boolean] [1x1 constant] [1x1 string ] [ list ] *This is why using a list() as linearized/serialized data source could and should do exactly the same*: c([3 1 2]) = list("cde", %s, %e) // should be accepted and performed in a /distributive/ way, whereas c([3 1 2]) = {list("cde", %s, %e)} // isaccepted but performed in a /replicative/ way. > ../.. When the JIMS module was published as a part of Scilab, there were two main issues concerning usages and users: * The first one was about wrapping/unwrapping java objects from/into scilab objects. These wrapping/unwrapping operations were implemented, but were not done automatically. Yet, afterwards, they have been set as the default mode in order to be done in a transparent way for users. And it is very great, because most users do not want to deal with internal handlings. They have an object and only one, and they don't care about the way it is encoded on the Scilab side or on the java side. * The second issue was about indexing numbers, that started at 0 instead of 1 as with any other type of scilab object. This was modified in order to keep an homogeneous indexation policy. With the present implementation of cells, we have exactly the same kind of issues. {} insertion and extraction operators should really be abandoned. *Or, again, please provide cases for which these**would be demonstrated as mandatory*. And single data should be automatically wrapped or unwrapped from their cell container in a transparent way. When there could be an ambiguity at insertion, the user can always force the wrapping by using some {} around the data source. I haven't found any SEP presenting usages of new {} as extractors, inserters, and concatenators. It would be great to have a pointer about such a document. Otherwise, i am afraid that we would miss a great opportunity to make Scilab really friendly to deal with mixed data. Improvements could be done with existing structures. And mistakes should be avoided before launching new cells features. {} extractors/inserters look to have been implemented in memory of the former .entries mlist field. But this way to address contents was directly connected to the technical way cells were encoded, as mlists. Cells are no longer mlists. Please forget completely .entries and remove a{} addressing. Best regards Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Thu Feb 18 16:13:29 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Thu, 18 Feb 2016 16:13:29 +0100 Subject: [Scilab-users] a{i, j} specific extraction syntax with {} should not be introduced In-Reply-To: <56C5BCD8.4020603@free.fr> References: <56C4AC43.6040408@free.fr> <56C4B123.7060409@free.fr> <1455789784.2595.103.camel@blink> <56C5BCD8.4020603@free.fr> Message-ID: <56C5DF99.2090004@free.fr> Le 18/02/2016 13:45, Samuel Gougeon a ?crit : > .../... > I haven't found any SEP presenting usages of new {} as extractors, > inserters, and concatenators. > It would be great to have a pointer about such a document. My fault, i missed it: It is the SEP #40, published on dev@ in 2010 for discussion: http://mailinglists.scilab.org/SEP-40-Cell-Arrays-tt2611124.html http://gitweb.scilab.org/?p=scilab.git;a=blob;f=SEP/SEP_040_cell_arrays.odt SG -------------- next part -------------- An HTML attachment was scrubbed... URL: From p.muehlmann at gmail.com Thu Feb 18 22:53:03 2016 From: p.muehlmann at gmail.com (=?UTF-8?Q?Philipp_M=C3=BChlmann?=) Date: Thu, 18 Feb 2016 22:53:03 +0100 Subject: [Scilab-users] linking help pages to each other Message-ID: Dear all, for a toolbox I write some help pages. The help pages contain a section ("See Also") , that allows to switch from one help page to another one. These links are displayed correctly, but when I click on them I get a blank site with the Error: "Error" requested page could not be found However, if I enter "help function" in the console, I do get the correct help page. The error also not occurs on every function. e.g: sometimes the link from one page to another is working. This is strange, because the xml-files are just copy/paste. Afterwards I adjust the content for a new function. The help pages are built with Scilab 5.5.1 and it's toolbox skeleton. Any idea? BR Philipp -- There we have the salad. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Fri Feb 19 01:41:15 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Fri, 19 Feb 2016 01:41:15 +0100 Subject: [Scilab-users] linking help pages to each other In-Reply-To: References: Message-ID: <56C664AB.1000401@free.fr> Hello, If the target is in the same external module, you may use in the xml (for instance, taken from the metanet module) edge_number If the target is a Scilab "native" help page, then (example targetting the linspace page): linspace should work. If the target is in another external module, then: I don't know ;) Do not hesitate to post your trials. HTH Samuel Gougeon Le 18/02/2016 22:53, Philipp M?hlmann a ?crit : > Dear all, > > for a toolbox I write some help pages. > > The help pages contain a section ("See Also") , that allows to switch > from one help page to another one. > > These links are displayed correctly, but when I click on them I get a > blank site with the Error: > > "Error" requested page could not be found > > However, if I enter "help function" in the console, I do get the > correct help page. > > The error also not occurs on every function. e.g: sometimes the link > from one page to another is working. > This is strange, because the xml-files are just copy/paste. > Afterwards I adjust the content for a new function. > > The help pages are built with Scilab 5.5.1 and it's toolbox skeleton. > > Any idea? > > BR > Philipp > > -- > There we have the salad. > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christophe.Dang at sidel.com Fri Feb 19 08:52:15 2016 From: Christophe.Dang at sidel.com (Dang Ngoc Chan, Christophe) Date: Fri, 19 Feb 2016 07:52:15 +0000 Subject: [Scilab-users] Scilab 6.0.0 Beta crashed by input() In-Reply-To: <56C5770F.9090504@laas.fr> References: <1455725441162-4033482.post@n3.nabble.com> <56C5770F.9090504@laas.fr> Message-ID: Hello, De Antoine Monmayrant Envoy? : jeudi 18 f?vrier 2016 08:47 > Le 02/17/2016 05:10 PM, JLan a ?crit : > > > Is this just on my machine? > > a=input('How can this line cause Scilab 6.0.0 Beta to crash when > > pressing enter?:'); > > > >Result in error message: > > Saddly, no! > > I just tried it on my machine (linux ubuntu 14.04 64bits) and bye bye scilab. It works fine on my side (6.0.0-alpha2 64 bits on MS-W7). -- Christophe Dang Ngoc Chan Mechanical calculation engineer This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error), please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. From p.muehlmann at gmail.com Fri Feb 19 08:58:06 2016 From: p.muehlmann at gmail.com (=?UTF-8?Q?Philipp_M=C3=BChlmann?=) Date: Fri, 19 Feb 2016 08:58:06 +0100 Subject: [Scilab-users] linking help pages to each other In-Reply-To: <56C664AB.1000401@free.fr> References: <56C664AB.1000401@free.fr> Message-ID: OK, here an example: all functions are within one and the same external module. The toolbox is named IR_TBX code sniplet from the help xml-file: See Also FLIR_IMGGetFrame that somehow does not link to the help page of FLIR_IMGGetFrame BR Philipp 2016-02-19 1:41 GMT+01:00 Samuel Gougeon : > Hello, > > If the target is in the same external module, you may use in the xml (for > instance, taken from the metanet module) > edge_number > > If the target is a Scilab "native" help page, then (example targetting the > linspace page): > linspace > should work. > > If the target is in another external module, then: I don't know ;) Do not > hesitate to post your trials. > > HTH > Samuel Gougeon > > > > Le 18/02/2016 22:53, Philipp M?hlmann a ?crit : > > Dear all, > > for a toolbox I write some help pages. > > The help pages contain a section ("See Also") , that allows to switch from > one help page to another one. > > These links are displayed correctly, but when I click on them I get a > blank site with the Error: > > "Error" requested page could not be found > > However, if I enter "help function" in the console, I do get the correct > help page. > > The error also not occurs on every function. e.g: sometimes the link from > one page to another is working. > This is strange, because the xml-files are just copy/paste. > Afterwards I adjust the content for a new function. > > The help pages are built with Scilab 5.5.1 and it's toolbox skeleton. > > Any idea? > > BR > Philipp > > -- > There we have the salad. > > > _______________________________________________ > users mailing listusers at lists.scilab.orghttp://lists.scilab.org/mailman/listinfo/users > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > > -- There we have the salad. -------------- next part -------------- An HTML attachment was scrubbed... URL: From antoine.monmayrant at laas.fr Fri Feb 19 09:14:28 2016 From: antoine.monmayrant at laas.fr (Antoine Monmayrant) Date: Fri, 19 Feb 2016 09:14:28 +0100 Subject: [Scilab-users] Scilab 6.0.0 Beta crashed by input() In-Reply-To: References: <1455725441162-4033482.post@n3.nabble.com> <56C5770F.9090504@laas.fr> Message-ID: <56C6CEE4.2070200@laas.fr> Le 02/19/2016 08:52 AM, Dang Ngoc Chan, Christophe a ?crit : > Hello, > > De Antoine Monmayrant > Envoy? : jeudi 18 f?vrier 2016 08:47 > >> Le 02/17/2016 05:10 PM, JLan a ?crit : >> >>> Is this just on my machine? >>> a=input('How can this line cause Scilab 6.0.0 Beta to crash when >>> pressing enter?:'); >>> >> >Result in error message: >> >> Saddly, no! >> >> I just tried it on my machine (linux ubuntu 14.04 64bits) and bye bye scilab. > It works fine on my side (6.0.0-alpha2 64 bits on MS-W7). Did you try it with the 6.0.0 beta and not the alpha? For me, the beta crashes right away, while the alpha keeps on working and only segfaults when I close it later on. Cheers, Antoine > > -- > Christophe Dang Ngoc Chan > Mechanical calculation engineer > This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error), please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. > From sgougeon at free.fr Fri Feb 19 09:38:12 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Fri, 19 Feb 2016 09:38:12 +0100 Subject: [Scilab-users] linking help pages to each other In-Reply-To: References: <56C664AB.1000401@free.fr> Message-ID: <56C6D474.6060803@free.fr> Hello, Le 19/02/2016 08:58, Philipp M?hlmann a ?crit : > OK, here an example: > > all functions are within one and the same external module. > > The toolbox is named IR_TBX > > code sniplet from the help xml-file: > > > See Also > > > FLIR_IMGGetFrame > > > > > > that somehow does not link to the help page of FLIR_IMGGetFrame Because your linkend tag does not specify the target: In the head of each XML page, the entry specifies the id of the page, whatever is its language (specified with the xml:lang="en" for en_US here, or any other language) If you want to target this page, the linkend must indicate the proper xml id: So, in the XML file of your FLIR_IMGGetFrame() help page, you must specify and in the "See also" of another page willing to target the FLIR_IMGGetFrame page, you must specify FLIR_IMGGetFrame or more simply FLIR_IMGGetFrame HTH Samuel Gougeon PS : By the way, i am as well working with a FLIR (S60), through its serial connection. So i am eager to discover your toolbox :) I should publish soon in 2016 a Scilab driver for the S60, on FileExchange, with other drivers i pushed there. From p.muehlmann at gmail.com Fri Feb 19 10:07:47 2016 From: p.muehlmann at gmail.com (=?UTF-8?Q?Philipp_M=C3=BChlmann?=) Date: Fri, 19 Feb 2016 10:07:47 +0100 Subject: [Scilab-users] linking help pages to each other In-Reply-To: <56C6D474.6060803@free.fr> References: <56C664AB.1000401@free.fr> <56C6D474.6060803@free.fr> Message-ID: that works like charm...thank you. Well, we work with SC3000 and SC7000 cameras in the company, which produce *.img and *.ptw files. But since the data format is - to my knowledge - still is not published by FLIR I'm not sure if I can share code to the public. We did buy from FLIR the data description (and the SDK) ones, so I could make a small toolbox for handling these files at work. BR Philipp 2016-02-19 9:38 GMT+01:00 Samuel Gougeon : > Hello, > > Le 19/02/2016 08:58, Philipp M?hlmann a ?crit : > >> OK, here an example: >> >> all functions are within one and the same external module. >> >> The toolbox is named IR_TBX >> >> code sniplet from the help xml-file: >> >> >> See Also >> >> >> FLIR_IMGGetFrame >> >> >> >> >> >> that somehow does not link to the help page of FLIR_IMGGetFrame >> > Because your linkend tag does not specify the target: > In the head of each XML page, the entry > > specifies the id of the page, whatever is its language (specified with the > xml:lang="en" for en_US here, or any other language) > If you want to target this page, the linkend must indicate the proper xml > id: > So, in the XML file of your FLIR_IMGGetFrame() help page, you must specify > > and in the "See also" of another page willing to target the > FLIR_IMGGetFrame page, you must specify > FLIR_IMGGetFrame > or more simply > FLIR_IMGGetFrame > > HTH > Samuel Gougeon > > PS : By the way, i am as well working with a FLIR (S60), through its > serial connection. So i am eager to discover your toolbox :) > I should publish soon in 2016 a Scilab driver for the S60, on > FileExchange, with other drivers i pushed there. > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > -- There we have the salad. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christophe.Dang at sidel.com Fri Feb 19 11:00:15 2016 From: Christophe.Dang at sidel.com (Dang Ngoc Chan, Christophe) Date: Fri, 19 Feb 2016 10:00:15 +0000 Subject: [Scilab-users] Scilab 6.0.0 Beta crashed by input() In-Reply-To: <56C6CEE4.2070200@laas.fr> References: <1455725441162-4033482.post@n3.nabble.com> <56C5770F.9090504@laas.fr> <56C6CEE4.2070200@laas.fr> Message-ID: Hello, > De : Antoine MonmayrantEnvoy? : vendredi 19 f?vrier 2016 09:14 > Objet : Re: [Scilab-users] Scilab 6.0.0 Beta crashed by input() > > Did you try it with the 6.0.0 beta and not the alpha? Nope, I was not up-to-date. I downloaded the beta, and it also crashed for me. -- Christophe Dang Ngoc Chan Mechanical calculation engineer This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error), please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. From stephane.mottelet at utc.fr Fri Feb 19 11:05:05 2016 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Fri, 19 Feb 2016 11:05:05 +0100 Subject: [Scilab-users] Scilab 6 bad performances In-Reply-To: <1455725441162-4033482.post@n3.nabble.com> References: <1455725441162-4033482.post@n3.nabble.com> Message-ID: <56C6E8D1.3030308@utc.fr> Hello, I am currently porting a Scilab package (Sysmetab, on the Scilab forge but not yet Atoms packaged) and I have noticed that Scilab 6 is two times slower than Scilab 5.5.2. The involved computations are very diverse but are vectorized products of submatrices, sparse matrix algebra and sparse linear systems solving. Until now, I did not have time to make a precise profiling, but knowing in advance which type of operations/computations have eventually regressed could be of great help to identify the bottlenecks... S. -- D?partement de G?nie Informatique EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable Universit? de Technologie de Compi?gne - CS 60319 60203 Compi?gne cedex From sgougeon at free.fr Fri Feb 19 11:17:42 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Fri, 19 Feb 2016 11:17:42 +0100 Subject: [Scilab-users] Scilab 6 bad performances In-Reply-To: <56C6E8D1.3030308@utc.fr> References: <1455725441162-4033482.post@n3.nabble.com> <56C6E8D1.3030308@utc.fr> Message-ID: <56C6EBC6.6030007@free.fr> Hello, Le 19/02/2016 11:05, St?phane Mottelet a ?crit : > Hello, > > I am currently porting a Scilab package (Sysmetab, on the Scilab forge > but not yet Atoms packaged) and I have noticed that Scilab 6 is two > times slower than Scilab 5.5.2. The involved computations are very > diverse but are vectorized products of submatrices, sparse matrix > algebra and sparse linear systems solving. Until now, I did not have > time to make a precise profiling, but knowing in advance which type of > operations/computations have eventually regressed could be of great > help to identify the bottlenecks... bench_run() is designed for that: https://help.scilab.org/docs/5.5.2/en_US/bench_run.html On the same computer, you may run it on 5.5.2 for chosen modules, run it as well on 6.0, and compare results. SG From stephane.mottelet at utc.fr Fri Feb 19 11:31:29 2016 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Fri, 19 Feb 2016 11:31:29 +0100 Subject: [Scilab-users] Scilab 6 bad performances In-Reply-To: <56C6EBC6.6030007@free.fr> References: <1455725441162-4033482.post@n3.nabble.com> <56C6E8D1.3030308@utc.fr> <56C6EBC6.6030007@free.fr> Message-ID: <56C6EF01.7000506@utc.fr> Le 19/02/2016 11:17, Samuel Gougeon a ?crit : > Hello, > > Le 19/02/2016 11:05, St?phane Mottelet a ?crit : >> Hello, >> >> I am currently porting a Scilab package (Sysmetab, on the Scilab >> forge but not yet Atoms packaged) and I have noticed that Scilab 6 is >> two times slower than Scilab 5.5.2. The involved computations are >> very diverse but are vectorized products of submatrices, sparse >> matrix algebra and sparse linear systems solving. Until now, I did >> not have time to make a precise profiling, but knowing in advance >> which type of operations/computations have eventually regressed could >> be of great help to identify the bottlenecks... > > bench_run() is designed for that: > https://help.scilab.org/docs/5.5.2/en_US/bench_run.html > On the same computer, you may run it on 5.5.2 for chosen modules, run > it as well on 6.0, and compare results. > This looks like finding a needle in a haystack... > SG > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -- D?partement de G?nie Informatique EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable Universit? de Technologie de Compi?gne - CS 60319 60203 Compi?gne cedex From sgougeon at free.fr Fri Feb 19 11:41:25 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Fri, 19 Feb 2016 11:41:25 +0100 Subject: [Scilab-users] Scilab 6 bad performances In-Reply-To: <56C6EF01.7000506@utc.fr> References: <1455725441162-4033482.post@n3.nabble.com> <56C6E8D1.3030308@utc.fr> <56C6EBC6.6030007@free.fr> <56C6EF01.7000506@utc.fr> Message-ID: <56C6F155.4030509@free.fr> Le 19/02/2016 11:31, St?phane Mottelet a ?crit : > Le 19/02/2016 11:17, Samuel Gougeon a ?crit : >> .../... >> bench_run() is designed for that: >> https://help.scilab.org/docs/5.5.2/en_US/bench_run.html >> On the same computer, you may run it on 5.5.2 for chosen modules, run >> it as well on 6.0, and compare results. >> > This looks like finding a needle in a haystack... . Right. Since bench_run() does not return its results -- just displays them --, they can't be post-processed to make a diff and filter it for instance to get only the slower instructions. However, bench_run.sci can be edited and modified to do so. SG From stephane.mottelet at utc.fr Fri Feb 19 11:51:50 2016 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Fri, 19 Feb 2016 11:51:50 +0100 Subject: [Scilab-users] Scilab 6 bad performances In-Reply-To: <56C6F155.4030509@free.fr> References: <1455725441162-4033482.post@n3.nabble.com> <56C6E8D1.3030308@utc.fr> <56C6EBC6.6030007@free.fr> <56C6EF01.7000506@utc.fr> <56C6F155.4030509@free.fr> Message-ID: <56C6F3C6.6060501@utc.fr> Le 19/02/2016 11:41, Samuel Gougeon a ?crit : > Le 19/02/2016 11:31, St?phane Mottelet a ?crit : >> Le 19/02/2016 11:17, Samuel Gougeon a ?crit : >>> .../... >>> bench_run() is designed for that: >>> https://help.scilab.org/docs/5.5.2/en_US/bench_run.html >>> On the same computer, you may run it on 5.5.2 for chosen modules, >>> run it as well on 6.0, and compare results. >>> >> This looks like finding a needle in a haystack... > . > Right. Since bench_run() does not return its results -- just displays > them --, they can't be post-processed to make a diff and filter it for > instance to get only the slower instructions. > However, bench_run.sci can be edited and modified to do so. at first sight, I already see the following problem (OSX) Scilab 6 001/001 - [linear_algebra] bench_inv ....................... 2281.91 ms Scilab 5.5.2 001/001 - [linear_algebra] bench_inv ....................... 871.99 ms I never compute inverses or solve full linear systems in my program, but seeing this could orient me... S. > > SG > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -- D?partement de G?nie Informatique EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable Universit? de Technologie de Compi?gne - CS 60319 60203 Compi?gne cedex From agardeux.ge at gmail.com Fri Feb 19 16:38:12 2016 From: agardeux.ge at gmail.com (Antoine Gardeux) Date: Fri, 19 Feb 2016 08:38:12 -0700 (MST) Subject: [Scilab-users] Call C function never returns (Scilab 5.5.2) Message-ID: <1455896292895-4033515.post@n3.nabble.com> Hello, Has anyone already heard about a limitation on the number of input arguments for a C function called using the "call" function? If the number of input arguments of the C function is ≤ 13, then the call to the function works well. If I add a 14th input argument, then the "call" function never returns. Any idea why this would happen ? *Version and platforms details:* OS: Windows 7 Scilab 5.5.2 (32 bits) C++ compiler/linker: gcc version 4.8.1, Target: mingw32, Thread model: win32 For more information on how to reproduce the problem and to get the test case, see bug #1433 . Thanks for your help, regards, Antoine -- View this message in context: http://mailinglists.scilab.org/Call-C-function-never-returns-Scilab-5-5-2-tp4033515.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From chema.valencia at gmail.com Sat Feb 20 03:07:47 2016 From: chema.valencia at gmail.com (Chema) Date: Fri, 19 Feb 2016 19:07:47 -0700 (MST) Subject: [Scilab-users] Plotting as stem function Message-ID: <1455934067373-4033516.post@n3.nabble.com> Hi, I have a problem when I'm trying to plot as in "stem" function in matlab using plot2d3, my scilab code is: n=0:20; x=cos(2*%pi*4.*n); plot2d3(n,x) tha plot shows some values in 0, why if the vector x is all ones? -- View this message in context: http://mailinglists.scilab.org/Plotting-as-stem-function-tp4033516.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From Serge.Steer at inria.fr Sat Feb 20 11:19:28 2016 From: Serge.Steer at inria.fr (Serge Steer) Date: Sat, 20 Feb 2016 11:19:28 +0100 Subject: [Scilab-users] Plotting as stem function In-Reply-To: <1455934067373-4033516.post@n3.nabble.com> References: <1455934067373-4033516.post@n3.nabble.com> Message-ID: <56C83DB0.4080800@inria.fr> Le 20/02/2016 03:07, Chema a ?crit : > Hi, > > I have a problem when I'm trying to plot as in "stem" function in matlab > using plot2d3, my scilab code is: > > n=0:20; > x=cos(2*%pi*4.*n); > plot2d3(n,x) > > tha plot shows some values in 0, why if the vector x is all ones? > > Which Scilab version do you use? I have tried your code on Scilab-5.5.2 and it gives good result. The y axis of your plot ranges from 1 to 1, so if a value is slightly less than 1 (due to rounding errors) the bar dispears You can fix the problem changing the y axis limits ax=gca(); ax.data_bounds(1,2)=0; > > > > -- > View this message in context: http://mailinglists.scilab.org/Plotting-as-stem-function-tp4033516.html > Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > From sgougeon at free.fr Sat Feb 20 14:40:59 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Sat, 20 Feb 2016 14:40:59 +0100 Subject: [Scilab-users] Plotting as stem function In-Reply-To: <56C83DB0.4080800@inria.fr> References: <1455934067373-4033516.post@n3.nabble.com> <56C83DB0.4080800@inria.fr> Message-ID: <56C86CEB.5020606@free.fr> Le 20/02/2016 11:19, Serge Steer a ?crit : > Le 20/02/2016 03:07, Chema a ?crit : >> Hi, >> >> I have a problem when I'm trying to plot as in "stem" function in matlab >> using plot2d3, my scilab code is: >> >> n=0:20; >> x=cos(2*%pi*4.*n); >> plot2d3(n,x) >> >> tha plot shows some values in 0, why if the vector x is all ones? >> >> > > Which Scilab version do you use? I guess 5.5.0 or 5.5.1. Reddished plots are their signature ;) BTW, i am able to 100% reproduce this bug with all 5.5.x releases, even with 5.5.2, on win7_x64 So, Serge, it may depend on the graphical card, as apparently the red-bug did (partially fixed in 5.5.2). The bug is fixed in Scilab 6.0-b1 (even for my card :) BR Samuel Gougeon From p.muehlmann at gmail.com Sun Feb 21 01:01:49 2016 From: p.muehlmann at gmail.com (=?UTF-8?Q?Philipp_M=C3=BChlmann?=) Date: Sun, 21 Feb 2016 01:01:49 +0100 Subject: [Scilab-users] mget at Scilab 5.4.1 and 5.5.1 Message-ID: Dear all, I have a binary file which contains some time data that I want to extract. in Scilab 5.4.1 my code does work: fid = mopen(FILE,'rb'); // switch to position of time information mseek( pos ,fid,'set'); Time = mget(1,'ul',fid); // time in seconds MilliTime = mget(1,'ul',fid); // milliseconds mclose(fid); doing this allows me to find the correct time information and I can create DATE and TIME as DATE = 'yyyy-mm-dd' TIME = hh:mm:ss.ms Now, using the exact same code in Scilab 5.5.1 creates somehow a different result. Example: Scilab 5.4.1: DATE = 2012-06-18 TIME = 09:18:58.870 Scilab 5.5.1: DATE = 120421-04-14 TIME = 23:10:58.7.311D+18 Next to aboves code I use: "datevec()" and "datenum()" to create the correct date and time. Does anything changed in these functions between Scialb 5.4.1 and 5.5.1 ? Thank you, BR Philipp -- There we have the salad. -------------- next part -------------- An HTML attachment was scrubbed... URL: From j-lan at online.no Sun Feb 21 08:46:57 2016 From: j-lan at online.no (=?ISO-8859-1?Q?Jan-=C5ge_Langeland_=28p=29?=) Date: Sun, 21 Feb 2016 08:46:57 +0100 Subject: [Scilab-users] mget at Scilab 5.4.1 and 5.5.1 Message-ID: Are the double numbers Time and Millitime the same in both versions? How many bytes do you acually read with 'ul'? (can check with mtell()). Is it unsigned long long integer? Converting it to double may cause lost prescision. ? Jan ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From j-lan at online.no Sun Feb 21 09:27:57 2016 From: j-lan at online.no (JLan) Date: Sun, 21 Feb 2016 01:27:57 -0700 (MST) Subject: [Scilab-users] mget at Scilab 5.4.1 and 5.5.1 In-Reply-To: References: Message-ID: <1456043277963-4033522.post@n3.nabble.com> Are the double numbers Time and Millitime the same in both versions? How many bytes do you acually read with 'ul'? (can check with mtell()). Is it unsigned long long integer? Converting it to double may cause lost prescision. Jan ? -- View this message in context: http://mailinglists.scilab.org/Scilab-users-mget-at-Scilab-5-4-1-and-5-5-1-tp4033520p4033522.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From p.muehlmann at gmail.com Sun Feb 21 11:21:42 2016 From: p.muehlmann at gmail.com (=?UTF-8?Q?Philipp_M=C3=BChlmann?=) Date: Sun, 21 Feb 2016 11:21:42 +0100 Subject: [Scilab-users] mget at Scilab 5.4.1 and 5.5.1 In-Reply-To: <1456043277963-4033522.post@n3.nabble.com> References: <1456043277963-4033522.post@n3.nabble.com> Message-ID: Sciab 5.4.1: pos before Time 488. pos after Time 492. pos after MilliTime 496. Time 1340097538. MilliTime 870. Scilab 5.5.1: pos before Time 488. pos after Time 496. pos after MilliTime 504. Time 3737961645058. MilliTime 7.3111468202388D+18 mh, I want to read 4 bytes fo Time and for MilliTime In the binary file description the variables are only specified as unsigned long. What I do not understand: Why would Scilab 5.5.1 read 8 bytes instead of 4? Thanks, Philipp 2016-02-21 9:27 GMT+01:00 JLan : > > Are the double numbers Time and Millitime the same in both versions? > > How many bytes do you acually read with 'ul'? (can check with mtell()). Is > it unsigned long long integer? Converting it to double may cause lost > prescision. > > Jan ? > > > > > -- > View this message in context: > http://mailinglists.scilab.org/Scilab-users-mget-at-Scilab-5-4-1-and-5-5-1-tp4033520p4033522.html > Sent from the Scilab users - Mailing Lists Archives mailing list archive > at Nabble.com. > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > -- There we have the salad. -------------- next part -------------- An HTML attachment was scrubbed... URL: From p.muehlmann at gmail.com Sun Feb 21 11:32:31 2016 From: p.muehlmann at gmail.com (=?UTF-8?Q?Philipp_M=C3=BChlmann?=) Date: Sun, 21 Feb 2016 11:32:31 +0100 Subject: [Scilab-users] mget at Scilab 5.4.1 and 5.5.1 In-Reply-To: References: <1456043277963-4033522.post@n3.nabble.com> Message-ID: changed the code from ...mget('1','ul',fid) to ...mget('1','ui',fid) Result = correct for both Scilab version. BR Philipp 2016-02-21 11:21 GMT+01:00 Philipp M?hlmann : > Sciab 5.4.1: > > pos before Time 488. > > pos after Time 492. > > pos after MilliTime 496. > > Time 1340097538. > > MilliTime 870. > > > Scilab 5.5.1: > > pos before Time 488. > > pos after Time 496. > > pos after MilliTime 504. > > Time 3737961645058. > > MilliTime 7.3111468202388D+18 > > > mh, I want to read 4 bytes fo Time and for MilliTime > > In the binary file description the variables are only specified as > unsigned long. > > What I do not understand: Why would Scilab 5.5.1 read 8 bytes instead of 4? > > Thanks, > Philipp > > > > 2016-02-21 9:27 GMT+01:00 JLan : > >> >> Are the double numbers Time and Millitime the same in both versions? >> >> How many bytes do you acually read with 'ul'? (can check with mtell()). Is >> it unsigned long long integer? Converting it to double may cause lost >> prescision. >> >> Jan ? >> >> >> >> >> -- >> View this message in context: >> http://mailinglists.scilab.org/Scilab-users-mget-at-Scilab-5-4-1-and-5-5-1-tp4033520p4033522.html >> Sent from the Scilab users - Mailing Lists Archives mailing list archive >> at Nabble.com. >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> http://lists.scilab.org/mailman/listinfo/users >> > > > > -- > There we have the salad. > -- There we have the salad. -------------- next part -------------- An HTML attachment was scrubbed... URL: From j-lan at online.no Sun Feb 21 12:26:13 2016 From: j-lan at online.no (JLan) Date: Sun, 21 Feb 2016 04:26:13 -0700 (MST) Subject: [Scilab-users] mget at Scilab 5.4.1 and 5.5.1 In-Reply-To: References: <1456043277963-4033522.post@n3.nabble.com> Message-ID: <1456053973187-4033525.post@n3.nabble.com> Good that you got it fixed. 'ul' - unsigned long long int should be 8 bytes, but since uint64 is not available in Scilab 5, it is nowhere to store it correctly. In Scilab 6 it is also problematic, since mgeti() does not correctly transfer all the bits. An unsigned long long little endian can however be read in like this: ULLLE=uint64(mgeti(1,'uil',fid))+uint64(mgeti(1,'uil',fid))*2^32 Jan ? -- View this message in context: http://mailinglists.scilab.org/Scilab-users-mget-at-Scilab-5-4-1-and-5-5-1-tp4033520p4033525.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From p.muehlmann at gmail.com Sun Feb 21 13:28:43 2016 From: p.muehlmann at gmail.com (=?UTF-8?Q?Philipp_M=C3=BChlmann?=) Date: Sun, 21 Feb 2016 13:28:43 +0100 Subject: [Scilab-users] mget at Scilab 5.4.1 and 5.5.1 In-Reply-To: <1456053973187-4033525.post@n3.nabble.com> References: <1456043277963-4033522.post@n3.nabble.com> <1456053973187-4033525.post@n3.nabble.com> Message-ID: OK, but why did it work with Scilab 5.4.1? Thanks, Philipp 2016-02-21 12:26 GMT+01:00 JLan : > Good that you got it fixed. > > 'ul' - unsigned long long int should be 8 bytes, but since uint64 is not > available in Scilab 5, it is nowhere to store it correctly. > > In Scilab 6 it is also problematic, since mgeti() does not correctly > transfer all the bits. An unsigned long long little endian can however be > read in like this: > > ULLLE=uint64(mgeti(1,'uil',fid))+uint64(mgeti(1,'uil',fid))*2^32 > > Jan ? > > > > -- > View this message in context: > http://mailinglists.scilab.org/Scilab-users-mget-at-Scilab-5-4-1-and-5-5-1-tp4033520p4033525.html > Sent from the Scilab users - Mailing Lists Archives mailing list archive > at Nabble.com. > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > -- There we have the salad. -------------- next part -------------- An HTML attachment was scrubbed... URL: From j-lan at online.no Sun Feb 21 14:10:46 2016 From: j-lan at online.no (JLan) Date: Sun, 21 Feb 2016 06:10:46 -0700 (MST) Subject: [Scilab-users] mget at Scilab 5.4.1 and 5.5.1 In-Reply-To: References: <1456043277963-4033522.post@n3.nabble.com> <1456053973187-4033525.post@n3.nabble.com> Message-ID: <1456060246189-4033527.post@n3.nabble.com> Well, remember to read a the small print in the help files before changing version :) 5.4.1 help, mget(): l long 5.5.1 help, mget(): l long long int i int or long int The definition of long and long long however is a bit open https://en.wikipedia.org/wiki/C_data_types. J? -- View this message in context: http://mailinglists.scilab.org/Scilab-users-mget-at-Scilab-5-4-1-and-5-5-1-tp4033520p4033527.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From p.muehlmann at gmail.com Sun Feb 21 17:23:02 2016 From: p.muehlmann at gmail.com (=?UTF-8?Q?Philipp_M=C3=BChlmann?=) Date: Sun, 21 Feb 2016 17:23:02 +0100 Subject: [Scilab-users] mget at Scilab 5.4.1 and 5.5.1 In-Reply-To: <1456060246189-4033527.post@n3.nabble.com> References: <1456043277963-4033522.post@n3.nabble.com> <1456053973187-4033525.post@n3.nabble.com> <1456060246189-4033527.post@n3.nabble.com> Message-ID: ...need better glasses :-)..thanks a lot 2016-02-21 14:10 GMT+01:00 JLan : > Well, remember to read a the small print in the help files before changing > version :) > > 5.4.1 help, mget(): > l long > > 5.5.1 help, mget(): > l long long int > i int or long int > > The definition of long and long long however is a bit open > https://en.wikipedia.org/wiki/C_data_types. > > J? > > > > -- > View this message in context: > http://mailinglists.scilab.org/Scilab-users-mget-at-Scilab-5-4-1-and-5-5-1-tp4033520p4033527.html > Sent from the Scilab users - Mailing Lists Archives mailing list archive > at Nabble.com. > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > -- There we have the salad. -------------- next part -------------- An HTML attachment was scrubbed... URL: From amonmayr at laas.fr Mon Feb 22 11:21:55 2016 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Mon, 22 Feb 2016 11:21:55 +0100 Subject: [Scilab-users] =?utf-8?q?How_to_replicate_what_=22load=22_does_?= =?utf-8?q?=28aka__creating_variable_in_the_current_workspace_from_inside_?= =?utf-8?q?a_function=29=3F?= Message-ID: <3f56-56cae180-1-32e173c0@52694930> Hi all, I need to create variables dynamically depending on what I parse from a text file. For testing, I just made a simple script that parses the file and generates a string array that defines some variables: txt=["a=1";"b=2"]; I then execstr(txt);; to create the variables needed (here "a" and "b"). So far, so good. Now, I need to refactor my code to turn my messy script into a proper set of functions (see example code below). The issue now is that I can't figure out how to define "a" and "b" from within the function. I tried to declare them as "global" inside the function, but it does not work: as I haven't declared them global at the top level before calling my function, it cannot work. Sadly, as I don't know in advance the variables I'll find when I parse the file, I cannot declare the variables global at the top level. Any solution or workaround? Cheers, Antoine /////example code //script version: clear a b; exists("a")// nope exists("b")// nope txt=["a=1";"b=2"];//typical result from parsing my txt file execstr(txt); exists("a")// yes exists("b")// yes //now with a function //broken & useless function myload() txt=["a=1";"b=2"]; //string to declare a and b global globaltxt="global "+strsubst(txt, '/=.*/', ';','r'); //does not work execstr(globaltxt); execstr(txt); endfunction //does not work clear a b; exists("a")// nope exists("b")// nope myload()// exists("a")// nope exists("b")// nope //this will work clear a b exists("a")// nope exists("b")// nope global a b // well I can't do that in practice, I don't know a and b in advance myload()// exists("a")// nope exists("b")// nope From Serge.Steer at inria.fr Mon Feb 22 11:51:46 2016 From: Serge.Steer at inria.fr (Serge Steer) Date: Mon, 22 Feb 2016 11:51:46 +0100 Subject: [Scilab-users] How to replicate what "load" does (aka creating variable in the current workspace from inside a function)? In-Reply-To: <3f56-56cae180-1-32e173c0@52694930> References: <3f56-56cae180-1-32e173c0@52694930> Message-ID: <56CAE842.2080406@inria.fr> The following function does the job: function myload() txt=["a=1";"b=2"]; ncur= size(who("local"),"*") execstr(txt); vars=who("local"); vars=vars(1:size(vars,'*')-ncur-1) args=strcat(vars,",") execstr("["+args+"]=resume("+args+")") endfunction Serge Le 22/02/2016 11:21, Antoine Monmayrant a ?crit : > Hi all, > > I need to create variables dynamically depending on what I parse from a text file. > For testing, I just made a simple script that parses the file and generates a string array that defines some variables: > txt=["a=1";"b=2"]; > I then > execstr(txt);; > to create the variables needed (here "a" and "b"). > So far, so good. > Now, I need to refactor my code to turn my messy script into a proper set of functions (see example code below). > The issue now is that I can't figure out how to define "a" and "b" from within the function. > I tried to declare them as "global" inside the function, but it does not work: as I haven't declared them global at the top level before calling my function, it cannot work. > Sadly, as I don't know in advance the variables I'll find when I parse the file, I cannot declare the variables global at the top level. > > Any solution or workaround? > > Cheers, > > Antoine > > /////example code > > //script version: > > clear a b; > exists("a")// nope > exists("b")// nope > txt=["a=1";"b=2"];//typical result from parsing my txt file > execstr(txt); > exists("a")// yes > exists("b")// yes > > //now with a function > > //broken & useless > function myload() > txt=["a=1";"b=2"]; > //string to declare a and b global > globaltxt="global "+strsubst(txt, '/=.*/', ';','r'); > //does not work > execstr(globaltxt); > execstr(txt); > endfunction > > > //does not work > clear a b; > exists("a")// nope > exists("b")// nope > myload()// > exists("a")// nope > exists("b")// nope > > > //this will work > clear a b > exists("a")// nope > exists("b")// nope > global a b // well I can't do that in practice, I don't know a and b in advance > myload()// > exists("a")// nope > exists("b")// nope > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > From amonmayr at laas.fr Mon Feb 22 12:04:03 2016 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Mon, 22 Feb 2016 12:04:03 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ICBIb3cgdG8gcmVwbGljYXRl?= =?utf-8?q?_what_=22load=22_does_=28aka_creating_variable_in_the_current_w?= =?utf-8?q?orkspace_from_inside_a_function=29=3F?= In-Reply-To: <56CAE842.2080406@inria.fr> Message-ID: <4572-56caeb00-3-345d4980@196712909> Le Lundi 22 F?vrier 2016 11:51 CET, Serge Steer a ?crit: > The following function does the job: > > function myload() > txt=["a=1";"b=2"]; > ncur= size(who("local"),"*") > execstr(txt); > vars=who("local"); > vars=vars(1:size(vars,'*')-ncur-1) > args=strcat(vars,",") > execstr("["+args+"]=resume("+args+")") > endfunction Thank you Serge! It does work on 5.5.0, but it does not work on 6.6.0-beta1. It might be due to the way variables are ordered when calling "who". Cheers, Antoine > > Serge > Le 22/02/2016 11:21, Antoine Monmayrant a ?crit : > > Hi all, > > > > I need to create variables dynamically depending on what I parse from a text file. > > For testing, I just made a simple script that parses the file and generates a string array that defines some variables: > > txt=["a=1";"b=2"]; > > I then > > execstr(txt);; > > to create the variables needed (here "a" and "b"). > > So far, so good. > > Now, I need to refactor my code to turn my messy script into a proper set of functions (see example code below). > > The issue now is that I can't figure out how to define "a" and "b" from within the function. > > I tried to declare them as "global" inside the function, but it does not work: as I haven't declared them global at the top level before calling my function, it cannot work. > > Sadly, as I don't know in advance the variables I'll find when I parse the file, I cannot declare the variables global at the top level. > > > > Any solution or workaround? > > > > Cheers, > > > > Antoine > > > > /////example code > > > > //script version: > > > > clear a b; > > exists("a")// nope > > exists("b")// nope > > txt=["a=1";"b=2"];//typical result from parsing my txt file > > execstr(txt); > > exists("a")// yes > > exists("b")// yes > > > > //now with a function > > > > //broken & useless > > function myload() > > txt=["a=1";"b=2"]; > > //string to declare a and b global > > globaltxt="global "+strsubst(txt, '/=.*/', ';','r'); > > //does not work > > execstr(globaltxt); > > execstr(txt); > > endfunction > > > > > > //does not work > > clear a b; > > exists("a")// nope > > exists("b")// nope > > myload()// > > exists("a")// nope > > exists("b")// nope > > > > > > //this will work > > clear a b > > exists("a")// nope > > exists("b")// nope > > global a b // well I can't do that in practice, I don't know a and b in advance > > myload()// > > exists("a")// nope > > exists("b")// nope > > > > > > > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/users > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > From amonmayr at laas.fr Mon Feb 22 12:12:05 2016 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Mon, 22 Feb 2016 12:12:05 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ID89PT91dGYtOD9xPyA/PSBI?= =?utf-8?q?ow_to_replicate_what_=22load=22_does_=28aka_creating_variable_i?= =?utf-8?q?n_the_current_workspace_from_inside_a_function=29?= In-Reply-To: <4572-56caeb00-3-345d4980@196712909> Message-ID: <3e5e-56caed00-15-17666560@77935798> Le Lundi 22 F?vrier 2016 12:04 CET, "Antoine Monmayrant" a ?crit: > > Le Lundi 22 F?vrier 2016 11:51 CET, Serge Steer a ?crit: > > > The following function does the job: > > > > function myload() > > txt=["a=1";"b=2"]; > > ncur= size(who("local"),"*") > > execstr(txt); > > vars=who("local"); > > vars=vars(1:size(vars,'*')-ncur-1) > > args=strcat(vars,",") > > execstr("["+args+"]=resume("+args+")") > > endfunction > > Thank you Serge! > It does work on 5.5.0, but it does not work on 6.6.0-beta1. > It might be due to the way variables are ordered when calling "who". OK, it seems that "who" no longer list variables with the most recent at the top, but in alphabetical order. Is this a known change? Should I fill a bug report? Antoine > > Cheers, > > Antoine > > > > > > Serge > > Le 22/02/2016 11:21, Antoine Monmayrant a ?crit : > > > Hi all, > > > > > > I need to create variables dynamically depending on what I parse from a text file. > > > For testing, I just made a simple script that parses the file and generates a string array that defines some variables: > > > txt=["a=1";"b=2"]; > > > I then > > > execstr(txt);; > > > to create the variables needed (here "a" and "b"). > > > So far, so good. > > > Now, I need to refactor my code to turn my messy script into a proper set of functions (see example code below). > > > The issue now is that I can't figure out how to define "a" and "b" from within the function. > > > I tried to declare them as "global" inside the function, but it does not work: as I haven't declared them global at the top level before calling my function, it cannot work. > > > Sadly, as I don't know in advance the variables I'll find when I parse the file, I cannot declare the variables global at the top level. > > > > > > Any solution or workaround? > > > > > > Cheers, > > > > > > Antoine > > > > > > /////example code > > > > > > //script version: > > > > > > clear a b; > > > exists("a")// nope > > > exists("b")// nope > > > txt=["a=1";"b=2"];//typical result from parsing my txt file > > > execstr(txt); > > > exists("a")// yes > > > exists("b")// yes > > > > > > //now with a function > > > > > > //broken & useless > > > function myload() > > > txt=["a=1";"b=2"]; > > > //string to declare a and b global > > > globaltxt="global "+strsubst(txt, '/=.*/', ';','r'); > > > //does not work > > > execstr(globaltxt); > > > execstr(txt); > > > endfunction > > > > > > > > > //does not work > > > clear a b; > > > exists("a")// nope > > > exists("b")// nope > > > myload()// > > > exists("a")// nope > > > exists("b")// nope > > > > > > > > > //this will work > > > clear a b > > > exists("a")// nope > > > exists("b")// nope > > > global a b // well I can't do that in practice, I don't know a and b in advance > > > myload()// > > > exists("a")// nope > > > exists("b")// nope > > > > > > > > > > > > _______________________________________________ > > > users mailing list > > > users at lists.scilab.org > > > http://lists.scilab.org/mailman/listinfo/users > > > > > > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/users > > > > > > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > From amonmayr at laas.fr Mon Feb 22 12:24:01 2016 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Mon, 22 Feb 2016 12:24:01 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ID89PT91dGYtOD9xPyA/PSBI?= =?utf-8?q?ow_to_replicate_what_=22load=22_does_=28aka_creating_variable_i?= =?utf-8?q?n_the_current_workspace_from_inside_a_function=29?= In-Reply-To: <3e5e-56caed00-15-17666560@77935798> Message-ID: <4a45-56caf000-3-7464b600@63565> This bug (who results are always sorted) was already reported here : http://bugzilla.scilab.org/show_bug.cgi?id=14352 From clement.david at scilab-enterprises.com Mon Feb 22 12:38:36 2016 From: clement.david at scilab-enterprises.com (=?ISO-8859-1?Q?Cl=E9ment?= David) Date: Mon, 22 Feb 2016 12:38:36 +0100 Subject: [Scilab-users] ?==?utf-8?q? How to replicate what "load" does (aka creating variable in the current workspace from inside a function)? In-Reply-To: <4572-56caeb00-3-345d4980@196712909> References: <4572-56caeb00-3-345d4980@196712909> Message-ID: <1456141116.5766.5.camel@scilab-enterprises.com> Hello Antoine, Serge, Le lundi 22 f?vrier 2016 ? 12:04 +0100, Antoine Monmayrant a ?crit?: > ? > Le Lundi 22 F?vrier 2016 11:51 CET, Serge Steer a ?crit:? > ? > > The following function does the job: > > > > function myload() > > ???txt=["a=1";"b=2"]; > > ???ncur= size(who("local"),"*") > > ???execstr(txt); > > ???vars=who("local"); > > ???vars=vars(1:size(vars,'*')-ncur-1) > > ???args=strcat(vars,",") > > ???execstr("["+args+"]=resume("+args+")") > > endfunction > > Thank you Serge! > It does work on 5.5.0, but it does not work on 6.6.0-beta1. > It might be due to the way variables are ordered when calling "who". Not sure if it is related to `who` or to the special use of `resume`. The resume will push its arguments to the caller context and thus make some variables visible. This is used inside Scilab to define variables on the caller and mimic the library loading behavior. -- Cl?ment From amonmayr at laas.fr Mon Feb 22 12:39:57 2016 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Mon, 22 Feb 2016 12:39:57 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ID89PT91dGYtOD9xPyA/PSBI?= =?utf-8?q?ow_to_replicate_what_=22load=22_does_=28aka_creating_variable_i?= =?utf-8?q?n_the_current_workspace_from_inside_a_function=29?= In-Reply-To: <4a45-56caf000-3-7464b600@63565> Message-ID: <4b46-56caf380-9-62a93f0@206409010> Hi all, For information, I found a solution that works fine in both 5.5.X and 6.0.X: function myload() txt=["a=1";"b=2"]; execstr(txt);//load local variables defined in txt; //build comma separated list of variables in txt csvar=strsubst(txt,'/=.*/',',','r').'; csvar=part(strcat(csvar),1:$-1); //return local variables to the calling environment execstr("["+csvar+"]=resume("+csvar+")"); endfunction Thank you Serge for your kind help. TIL that scilab has a 'resume' function. Cheers, Antoine From sgougeon at free.fr Mon Feb 22 12:44:25 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Mon, 22 Feb 2016 12:44:25 +0100 Subject: [Scilab-users] How to replicate what "load" does (aka creating variable in the current workspace from inside a function) In-Reply-To: <3e5e-56caed00-15-17666560@77935798> References: <3e5e-56caed00-15-17666560@77935798> Message-ID: <56CAF499.6050903@free.fr> Le 22/02/2016 12:12, Antoine Monmayrant a ?crit : Le Lundi 22 F?vrier 2016 12:04 CET, "Antoine Monmayrant" a ?crit: >> Le Lundi 22 F?vrier 2016 11:51 CET, Serge Steer a ?crit: >>> The following function does the job: >>> >>> function myload() >>> txt=["a=1";"b=2"]; >>> ncur= size(who("local"),"*") >>> execstr(txt); >>> vars=who("local"); >>> vars=vars(1:size(vars,'*')-ncur-1) >>> args=strcat(vars,",") >>> execstr("["+args+"]=resume("+args+")") >>> endfunction >> Thank you Serge! >> It does work on 5.5.0, but it does not work on 6.6.0-beta1. >> It might be due to the way variables are ordered when calling "who". > OK, it seems that "who" no longer list variables with the most recent at the top, but in alphabetical order. . You can use setdiff() to get the names of the new variables, knowing the former set, whatever is their order. Then, you will need to the same before and after calling the function, to get the unknown names of returned variables. Samuel From amonmayr at laas.fr Mon Feb 22 12:51:58 2016 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Mon, 22 Feb 2016 12:51:58 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ID89PT91dGYtOD9xPyA/PSBI?= =?utf-8?q?ow_to_replicate_what_=22load=22_does_=28aka_creating_variable_i?= =?utf-8?q?n_the_current_workspace_from_inside_a_function=29?= In-Reply-To: <1456141116.5766.5.camel@scilab-enterprises.com> Message-ID: <4f56-56caf680-3-45a0ce80@197447866> > Not sure if it is related to `who` or to the special use of `resume`. I can confirm that it comes from the bug in who for scilab 6.0. See also my solution that uses 'resume' and not 'who' and work in both 5.5 and 6.0 Cheers, Antoine From sgougeon at free.fr Mon Feb 22 13:13:42 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Mon, 22 Feb 2016 13:13:42 +0100 Subject: [Scilab-users] new option "@" <= uman : help in the console, with language switch, automatic redirections, related online pages. In-Reply-To: References: <5575F0C7.3080207@free.fr> <55769561.8050605@laas.fr> Message-ID: <56CAFB76.4010502@free.fr> Hello Rafael, Le 22/11/2015 22:47, Rafael Guerra a ?crit : > > Hello Samuel, > > Thanks for sharing *uman* and congratulations for the amazing work done. > > This is a very useful tool to increase Scilab users productivity. > > The quick access to the appropriate bug webpages is awesome. > > May we also use uman to query the relevant threads in Scilab users > webpages? > . Thanks for using and supporting *uman*. The present release for Scilab 6 is out of work due to Scilab 6 running changes, but the next uman's release will come very soon, for both Scilab 5 and Scilab 6. It will propose the new option "*@*" (and other new features) to do what you wish. Here is how "@" is presently implemented (examples from the help page, all already working): // Mailing lists: Search Scilab online archives: The "@" option // ------------------------------------------------------------ // To search only in Subject of messages, end the pattern with "!" // Operators grouping (), | (or), & (and), ~ (not/without) can be used. // If it has spaces or a leading ( , put the pattern between quotes "..." // Author(s) may be also be selected with "author>..." or "......" etc. // uman aliasing @ // Search "aliasing" in any part of messages uman aliasing! @ // Search "aliasing" only in Subjects uman grand&setting @ // Messages with "grand" AND "setting" in any part uman grand&~setting @ // Messages with "grand" AND WITHOUT "setting" in any part uman "grand & ~setting" @ // idem. Use quotes when there are blanks. uman cell|struct! @ // Subject with "cell" OR "struct" uman "(cell|struct)&~matrix!" @ // Subject with "cell" OR "struct", AND NOT matrix // Quotes are mandatory to protect the leading ( uman struct&~(array|scilab)! @ // Subject with "struct" AND NOT ("array" OR "scilab") uman "(cell|struct)&~(function|array)!" @ // Subject with "cell" OR "struct", // AND NOT "function" OR "array" uman denizet>SEP|graphics! @ // Subject with ("SEP" OR "graphics") FROM Denizet uman SEP From sgougeon at free.fr Mon Feb 22 13:35:43 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Mon, 22 Feb 2016 13:35:43 +0100 Subject: [Scilab-users] new option "@" <= uman : help in the console, with language switch, automatic redirections, related online pages. In-Reply-To: <56CAFB76.4010502@free.fr> References: <5575F0C7.3080207@free.fr> <55769561.8050605@laas.fr> <56CAFB76.4010502@free.fr> Message-ID: <56CB009F.1010007@free.fr> Le 22/02/2016 13:13, Samuel Gougeon a ?crit : > .../... > uman denizet>SEP|graphics! @ // Subject with ("SEP" OR "graphics") > FROM Denizet > uman SEP "Couvert") > . OK, i already know that, if any, selection of authors will be kept only as leading field: uman steer|couvert>SEP! @ // Subject with "SEP" FROM ("Steer" OR "Couvert") in order to use the trailing "<###" to specify the number of most recent days within which messages were posted. It will be added to the forthcoming release. SG -------------- next part -------------- An HTML attachment was scrubbed... URL: From noguchi at kje.biglobe.ne.jp Mon Feb 22 14:28:40 2016 From: noguchi at kje.biglobe.ne.jp (noguchi) Date: Mon, 22 Feb 2016 06:28:40 -0700 (MST) Subject: [Scilab-users] usage of libsvm Toolbox Message-ID: <1456147720112-4033540.post@n3.nabble.com> Dear Scilab Users I would like to lean how to use libsvm Toolbox - (1.4.5). I would like to do multi variable regression by using this tool box. If you have any tutrial material with sample data for beginner of this tool box, could you please please send it to me. Especially, I would like to know that how I can know the regression equation and their parameters so that I can implement it in the computer to calculate the predicted value on-line. Thank you for your help. Y. Noguchi -- View this message in context: http://mailinglists.scilab.org/usage-of-libsvm-Toolbox-tp4033540.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From noguchi at kje.biglobe.ne.jp Mon Feb 22 14:18:25 2016 From: noguchi at kje.biglobe.ne.jp (Y. Noguchi) Date: Mon, 22 Feb 2016 22:18:25 +0900 (JST) Subject: [Scilab-users] usage of libsvm In-Reply-To: <936dbd3e-71ef-48b3-a8bd-7f1684d0620c@bvec34483> Message-ID: <38a76530-37cb-49af-a0d3-8db16aabeb7b@bvec34483> Dear Scilab Users I would like to lean how to use libsvm Toolbox - (1.4.5). I would like to do multi variable regression by using this tool box. If you have any tutrial material for beginner of this tool box, could you please please send it to me. Thank you for your help. Y. Noguchi From chema.valencia at gmail.com Mon Feb 22 19:00:09 2016 From: chema.valencia at gmail.com (Chema) Date: Mon, 22 Feb 2016 11:00:09 -0700 (MST) Subject: [Scilab-users] Plotting as stem function In-Reply-To: <56C86CEB.5020606@free.fr> References: <1455934067373-4033516.post@n3.nabble.com> <56C83DB0.4080800@inria.fr> <56C86CEB.5020606@free.fr> Message-ID: <1456164009769-4033542.post@n3.nabble.com> Thanks, the two answers were usefull for me... -- View this message in context: http://mailinglists.scilab.org/Plotting-as-stem-function-tp4033516p4033542.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From p.muehlmann at gmail.com Tue Feb 23 05:31:13 2016 From: p.muehlmann at gmail.com (=?UTF-8?Q?Philipp_M=C3=BChlmann?=) Date: Tue, 23 Feb 2016 05:31:13 +0100 Subject: [Scilab-users] adjust image Message-ID: Dear all, please have a look at following code. The aim is to adjust the intensitivity levels of an image to new values...something like imadjust in Matlab. I did not find something like this in IPD or in SIVP, therefore the try. For my purposes it's enough, though not all image types are maybe supported... But the code did work with a bmp and jpg-file. function out=AdjustImage(img, In_low, In_high, Out_low, Out_high) //make sure we work with doubles img = double(img); select ndims(img) case 2 // 2D array (GrayScaleImage) //normalize image MIN = min(img); MAX = max(img); img = (img-MIN)./ (MAX-MIN); //make sure img is in the range [In_low;In_high] img = max(In_low, min(In_high,img)); out = ( (img - In_low) ./ (In_high - In_low) ) ; out = out .* (Out_high - Out_low) + Out_low; case 3 // hypermat (ColorImage) for i = 1:3 //normalize image MIN = min(img(:,:,i)); MAX = max(img(:,:,i)); img(:,:,i) = (img(:,:,i)-MIN)./ (MAX-MIN); //make sure img is in the range [In_low;In_high] img(:,:,i) = max(In_low, min(In_high,img(:,:,i))); out(:,:,i) = ((img(:,:,i) - In_low) ./ (In_high - In_low)) ; out(:,:,i) = out(:,:,i) .* (Out_high - Out_low) + Out_low; end endendfunction; //test case 2D img = rand(240,320); adj_im = AdjustImage(img,0.2,0.8,0,1); //test case hypermat img(:,:,1) = rand(240,320); img(:,:,2) = rand(240,320); img(:,:,3) = rand(240,320); adj_im = AdjustImage(img,0.2,0.8,0,1); For those who have IPD installed, you can use ShowImage() or ShowColorImage() to see the results. For those who don't at least the 2D case should be possible to visualize with Matplot()...the hypermat case...don't know. f = figure(); f.color_map = graycolormap(255); Matplot(img); BR, Philipp -- There we have the salad. -------------- next part -------------- An HTML attachment was scrubbed... URL: From antoine.elias at scilab-enterprises.com Tue Feb 23 10:25:39 2016 From: antoine.elias at scilab-enterprises.com (antoine.elias at scilab-enterprises.com) Date: Tue, 23 Feb 2016 10:25:39 +0100 Subject: [Scilab-users] How to replicate what "load" does (aka creating variable in the current workspace from inside a function) In-Reply-To: <4f56-56caf680-3-45a0ce80@197447866> References: <4f56-56caf680-3-45a0ce80@197447866> Message-ID: <9bd6546060f7251fb07a6c46aba86838@scilab-enterprises.com> Hi users, Just to explain, why "who" change. Previous implementation of "who" was stack dependant, so when you ask local variables names, Scilab 5 reads the stack from bottom to top ( or the opposite ), and returns list of variables it found. Now in Scilab 6, we have remove this stack ( i'm sure you already know that ^^ ). And we use map to store local variables names. maps are pretty fast but do not ensure order of elements. "who" returns a list of local variables names, that's all. The alphabetical order is a side effect of implementation like creation order was in Scilab 5. If we use another system to store local variables names, we can get another output. So please, do not use "alphabetical" order without "sorted" argument. It may change in future. Antoine ps: I'm pretty sure that "who"'s help page does not say "'who' returns variables names in creation order." Le 2016-02-22 12:51, Antoine Monmayrant a ?crit?: >> Not sure if it is related to `who` or to the special use of `resume`. > > I can confirm that it comes from the bug in who for scilab 6.0. > See also my solution that uses 'resume' and not 'who' and work in both > 5.5 and 6.0 > > Cheers, > > Antoine > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From grivet at cnrs-orleans.fr Tue Feb 23 12:21:14 2016 From: grivet at cnrs-orleans.fr (grivet) Date: Tue, 23 Feb 2016 12:21:14 +0100 Subject: [Scilab-users] bug in function iir ? In-Reply-To: <56BA3D8D.4070207@free.fr> References: <56B87251.7040903@laas.fr> <56BA3D8D.4070207@free.fr> Message-ID: <56CC40AA.6030506@cnrs-orleans.fr> Hello, I am beginning to use digital filters to treat some data. As my first step, I try to run the examples in the help,how to design an elliptic filter (using Scilab 5.5.1, Win7-64). This works . However, when I select a Butterworth filter: hz = iir(Order,'lp','butt',Fcutoff/Fs/2,[0.1 0.1]); I get this error message: Singularit? de la fonction log ou tan. at line 6 of function dbphi called by : [db_repf, phi_repf] = dbphi(repf); What did I miss ? No bugs have been reported for function dbphi, but three similar bugs are listed for iir. Any suggestion welcome. JPGrivet -------------- next part -------------- An HTML attachment was scrubbed... URL: From Serge.Steer at inria.fr Tue Feb 23 14:21:05 2016 From: Serge.Steer at inria.fr (Serge Steer) Date: Tue, 23 Feb 2016 14:21:05 +0100 Subject: [Scilab-users] bug in function iir ? In-Reply-To: <56CC40AA.6030506@cnrs-orleans.fr> References: <56B87251.7040903@laas.fr> <56BA3D8D.4070207@free.fr> <56CC40AA.6030506@cnrs-orleans.fr> Message-ID: <56CC5CC1.1050607@inria.fr> Please can you give more details : value of Order and Fcutoff/Fs/2 and what you are doing with hz (because iir does not call dbphi) Serge Le 23/02/2016 12:21, grivet a ?crit : > Hello, > I am beginning to use digital filters to treat some data. As my first > step, I try to run the examples in the help,how to design an elliptic > filter (using Scilab 5.5.1, Win7-64). This works . However, when I > select a Butterworth filter: > hz = iir(Order,'lp','butt',Fcutoff/Fs/2,[0.1 0.1]); > I get this error message: > > Singularit? de la fonction log ou tan. > at line 6 of function dbphi called by : > [db_repf, phi_repf] = dbphi(repf); > > What did I miss ? > No bugs have been reported for function dbphi, but three similar bugs > are listed for iir. > Any suggestion welcome. > JPGrivet > > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From grivet at cnrs-orleans.fr Tue Feb 23 14:41:19 2016 From: grivet at cnrs-orleans.fr (grivet) Date: Tue, 23 Feb 2016 14:41:19 +0100 Subject: [Scilab-users] bug in function iir ? In-Reply-To: <56CC5CC1.1050607@inria.fr> References: <56B87251.7040903@laas.fr> <56BA3D8D.4070207@free.fr> <56CC40AA.6030506@cnrs-orleans.fr> <56CC5CC1.1050607@inria.fr> Message-ID: <56CC617F.3000508@cnrs-orleans.fr> Le 23/02/2016 14:21, Serge Steer a ?crit : > Please can you give more details : > value of Order and Fcutoff/Fs/2 > and what you are doing with hz (because iir does not call dbphi) > Serge I am just running the example found in "how to design an elliptic filter". Here is the code: Order = 2; // The order of the filter Fs = 1000; // The sampling frequency Fcutoff = 40; // The cutoff frequency // We design a low pass elliptic filter hz = iir (Order,'lp','ellip',[Fcutoff/Fs/2 0],[0.1 0.1]); // We compute the frequency response of the filter [frq,repf]=repfreq (hz,0:0.001:0.5); [db_repf, phi_repf] = dbphi (repf); // And plot the bode like representation of the digital filter subplot (2,1,1); plot2d (Fs*frq,db_repf); xtitle ('Obtained Frequency Response (Magnitude)'); subplot (2,1,2); plot2d (Fs*frq,phi_repf); xtitle ('Obtained Frequency Response (Phase in degree)'); with 'ellip' replaced by 'butt', and [Fcutoff/Fs/2 0] replaced byFcutoff/Fs/2. I am beginning to use digital filters to treat some data. As my first step, I try to run the examples in the help,how to design an elliptic filter (using Scilab 5.5.1, Win7-64). This works . However, when I select a Butterworth filter: >> hz = iir(Order,'lp','butt',Fcutoff/Fs/2,[0.1 0.1]); >> I get this error message: >> >> Singularit? de la fonction log ou tan. >> at line 6 of function dbphi called by : >> [db_repf, phi_repf] = dbphi(repf); >> >> What did I miss ? >> No bugs have been reported for function dbphi, but three similar bugs >> are listed for iir. >> Any suggestion welcome. >> JPGrivet -------------- next part -------------- An HTML attachment was scrubbed... URL: From Serge.Steer at inria.fr Tue Feb 23 15:34:08 2016 From: Serge.Steer at inria.fr (Serge Steer) Date: Tue, 23 Feb 2016 15:34:08 +0100 Subject: [Scilab-users] bug in function iir ? In-Reply-To: <56CC617F.3000508@cnrs-orleans.fr> References: <56B87251.7040903@laas.fr> <56BA3D8D.4070207@free.fr> <56CC40AA.6030506@cnrs-orleans.fr> <56CC5CC1.1050607@inria.fr> <56CC617F.3000508@cnrs-orleans.fr> Message-ID: <56CC6DE0.7040602@inria.fr> Your problem arises because one frequency value you ask for corresponds exactly to a zero of hz.num log(roots(hz.num))/(2*%pi) so you want to compute the gain in dB of a zero value which is -inf To avoid such problem you can let repfreq to do the frequency discretization. [frq,repf]=repfreq (hz) or equivalently [frq,repf]=repfreq (hz,0,0.5) in this case the discretization uses varying frequency step Serge Le 23/02/2016 14:41, grivet a ?crit : > Le 23/02/2016 14:21, Serge Steer a ?crit : >> Please can you give more details : >> value of Order and Fcutoff/Fs/2 >> and what you are doing with hz (because iir does not call dbphi) >> Serge > I am just running the example found in "how to design an elliptic > filter". Here is the code: > > Order = 2; // The order of the filter > Fs = 1000; // The sampling frequency > Fcutoff = 40; // The cutoff frequency > > // We design a low pass elliptic filter > hz = iir (Order,'lp','ellip',[Fcutoff/Fs/2 0],[0.1 0.1]); > > // We compute the frequency response of the filter > [frq,repf]=repfreq (hz,0:0.001:0.5); > [db_repf, phi_repf] = dbphi (repf); > > // And plot the bode like representation of the digital filter > subplot (2,1,1); > plot2d (Fs*frq,db_repf); > xtitle ('Obtained Frequency Response (Magnitude)'); > subplot (2,1,2); > plot2d (Fs*frq,phi_repf); > xtitle ('Obtained Frequency Response (Phase in degree)'); > > > with 'ellip' replaced by 'butt', and [Fcutoff/Fs/2 0] replaced > byFcutoff/Fs/2. > I am beginning to use digital filters to treat some data. As my first > step, I try to run the examples in the help,how to design an elliptic > filter (using Scilab 5.5.1, Win7-64). This works . However, when I > select a Butterworth filter: >>> hz = iir(Order,'lp','butt',Fcutoff/Fs/2,[0.1 0.1]); >>> I get this error message: >>> >>> Singularit? de la fonction log ou tan. >>> at line 6 of function dbphi called by : >>> [db_repf, phi_repf] = dbphi(repf); >>> >>> What did I miss ? >>> No bugs have been reported for function dbphi, but three similar >>> bugs are listed for iir. >>> Any suggestion welcome. >>> JPGrivet > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From W.Schulz at ove.at Tue Feb 23 15:48:22 2016 From: W.Schulz at ove.at (SCHULZ Wolfgang) Date: Tue, 23 Feb 2016 14:48:22 +0000 Subject: [Scilab-users] Bug of input function in Scilab 6.0 beta 1 Message-ID: <07A8AF089844A549B0F0CCC727AF31AA57A879E1@OVEKBG.ove.at> Hello, since Scilab 6.0 beta 1 I have a problem with the input function (everything worked under Scilab 6.0 alpha 1). I execute the following code: Code: mode(0); ieee(1); clear; iteration = input("Sensor data of which Iteration:"); name = sprintf("iteration%03d.sensor",iteration) With Scilab 5.5.2 I enter 1 and get the following output: -->exec('H:\SCILAB\Problem_input_data.sce', -1) Sensor data of which Iteration:1 name = iteration001.sensor Scilab 6.0 beta 1: I had to input "1" 2 times: --> exec('H:\SCILAB\Problem_input_data.sce', -1) Sensor data of which Iteration:1 Sensor data of which Iteration:1 name = iteration001.sensor As mentioned Scilab 5.5.2 and the Scilab 6.0 alpha 1 worked without problems (I didn't try Scilab 6.0 alpha 2). Is this a bug and simply a new behavior of the input function? Best regards Wolfgang -------------- next part -------------- An HTML attachment was scrubbed... URL: From clement.david at scilab-enterprises.com Tue Feb 23 17:16:03 2016 From: clement.david at scilab-enterprises.com (=?ISO-8859-1?Q?Cl=E9ment?= David) Date: Tue, 23 Feb 2016 17:16:03 +0100 Subject: [Scilab-users] Bug of input function in Scilab 6.0 beta 1 In-Reply-To: <07A8AF089844A549B0F0CCC727AF31AA57A879E1@OVEKBG.ove.at> References: <07A8AF089844A549B0F0CCC727AF31AA57A879E1@OVEKBG.ove.at> Message-ID: <1456244163.2863.7.camel@scilab-enterprises.com> Hi Wolfgang, It seems to be a bug, please report it. -- Cl?ment Le mardi 23 f?vrier 2016 ? 14:48 +0000, SCHULZ Wolfgang a ?crit?: > Hello, > since Scilab 6.0 beta 1 I have a problem with the input function (everything worked under Scilab > 6.0 alpha 1). > ? > I execute the following code: > Code: > mode(0); > ieee(1); > clear; > iteration = input("Sensor data of which Iteration:"); > name = sprintf("iteration%03d.sensor",iteration) > ? > With Scilab 5.5.2 I enter 1 and get the following output: > -->exec('H:\SCILAB\Problem_input_data.sce', -1) > Sensor data of which Iteration:1 > name? = > ?iteration001.sensor?? > ? > Scilab 6.0 beta 1: I had to input ?1? 2 times: > ? > --> exec('H:\SCILAB\Problem_input_data.sce', -1) > Sensor data of which Iteration:1 > Sensor data of which Iteration:1 name? = > ? > iteration001.sensor > ? > As mentioned Scilab 5.5.2 and the Scilab 6.0 alpha 1 worked without problems (I didn?t try Scilab > 6.0 alpha 2). > ? > Is this a bug and simply a new behavior of the input function? > Best regards > Wolfgang > ? > ? > ? > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From amonmayr at laas.fr Tue Feb 23 18:27:46 2016 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Tue, 23 Feb 2016 18:27:46 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ICBCdWcgb2YgaW5wdXQgZnVu?= =?utf-8?q?ction_in_Scilab_6=2E0_beta_1?= In-Reply-To: <1456244163.2863.7.camel@scilab-enterprises.com> Message-ID: <7ed8-56cc9680-23-a922560@180664195> Le Mardi 23 F?vrier 2016 17:16 CET, Cl?ment David a ?crit: > Hi Wolfgang, > > It seems to be a bug, please report it. Is this related to the previous 'input()' bug reported here (crashing for long input string)? Antoine > > -- > Cl?ment > > Le mardi 23 f?vrier 2016 ? 14:48 +0000, SCHULZ Wolfgang a ?crit?: > > Hello, > > since Scilab 6.0 beta 1 I have a problem with the input function (everything worked under Scilab > > 6.0 alpha 1). > > ? > > I execute the following code: > > Code: > > mode(0); > > ieee(1); > > clear; > > iteration = input("Sensor data of which Iteration:"); > > name = sprintf("iteration%03d.sensor",iteration) > > ? > > With Scilab 5.5.2 I enter 1 and get the following output: > > -->exec('H:\SCILAB\Problem_input_data.sce', -1) > > Sensor data of which Iteration:1 > > name? = > > ?iteration001.sensor?? > > ? > > Scilab 6.0 beta 1: I had to input ?1? 2 times: > > ? > > --> exec('H:\SCILAB\Problem_input_data.sce', -1) > > Sensor data of which Iteration:1 > > Sensor data of which Iteration:1 name? = > > ? > > iteration001.sensor > > ? > > As mentioned Scilab 5.5.2 and the Scilab 6.0 alpha 1 worked without problems (I didn?t try Scilab > > 6.0 alpha 2). > > ? > > Is this a bug and simply a new behavior of the input function? > > Best regards > > Wolfgang > > ? > > ? > > ? > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/users > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > From amonmayr at laas.fr Wed Feb 24 08:56:55 2016 From: amonmayr at laas.fr (amonmayr at laas.fr) Date: Wed, 24 Feb 2016 08:56:55 +0100 Subject: [Scilab-users] How to replicate what "load" does (aka creating variable in the current workspace from inside a function) In-Reply-To: <9bd6546060f7251fb07a6c46aba86838@scilab-enterprises.com> References: <4f56-56caf680-3-45a0ce80@197447866> <9bd6546060f7251fb07a6c46aba86838@scilab-enterprises.com> Message-ID: <56CD6247.5000509@laas.fr> Le 02/23/2016 10:25 AM, antoine.elias at scilab-enterprises.com a ?crit : > Hi users, > > Just to explain, why "who" change. > Previous implementation of "who" was stack dependant, so when you ask > local variables names, > Scilab 5 reads the stack from bottom to top ( or the opposite ), and > returns list of variables it found. > > Now in Scilab 6, we have remove this stack ( i'm sure you already know > that ^^ ). > And we use map to store local variables names. > maps are pretty fast but do not ensure order of elements. > "who" returns a list of local variables names, that's all. > > The alphabetical order is a side effect of implementation like > creation order was in Scilab 5. > If we use another system to store local variables names, we can get > another output. > > So please, do not use "alphabetical" order without "sorted" argument. > It may change in future. OK, thanks for the in-depth explanations. Any chance to get some sort of time-stamp or order info with 'who' or any other function? Because that was a neat feature to know right away what were the last variables created. > > > Antoine > ps: I'm pretty sure that "who"'s help page does not say "'who' returns > variables names in creation order." Indeed, it does not. But now we have an option to sort them whereas they are already sorted. Kind of weird and confusing. > > Le 2016-02-22 12:51, Antoine Monmayrant a ?crit : >>> Not sure if it is related to `who` or to the special use of `resume`. >> >> I can confirm that it comes from the bug in who for scilab 6.0. >> See also my solution that uses 'resume' and not 'who' and work in both >> 5.5 and 6.0 >> >> Cheers, >> >> Antoine >> >> >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> http://lists.scilab.org/mailman/listinfo/users > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ Antoine Monmayrant LAAS - CNRS 7 avenue du Colonel Roche BP 54200 31031 TOULOUSE Cedex 4 FRANCE Tel:+33 5 61 33 64 59 email : antoine.monmayrant at laas.fr permanent email : antoine.monmayrant at polytechnique.org +++++++++++++++++++++++++++++++++++++++++++++++++++++++ From grivet at cnrs-orleans.fr Wed Feb 24 11:30:45 2016 From: grivet at cnrs-orleans.fr (grivet) Date: Wed, 24 Feb 2016 11:30:45 +0100 Subject: [Scilab-users] bug in function iir ? In-Reply-To: <56CC6DE0.7040602@inria.fr> References: <56B87251.7040903@laas.fr> <56BA3D8D.4070207@free.fr> <56CC40AA.6030506@cnrs-orleans.fr> <56CC5CC1.1050607@inria.fr> <56CC617F.3000508@cnrs-orleans.fr> <56CC6DE0.7040602@inria.fr> Message-ID: <56CD8655.10403@cnrs-orleans.fr> I appreciate your help; however, neither suggestion works: I still get the same error message. The similar line [frq,repf]=repfreq(hz,0.01,0.49); has no problem > Your problem arises because one frequency value you ask for > corresponds exactly to a zero of hz.num > log(roots(hz.num))/(2*%pi) > so you want to compute the gain in dB of a zero value which is -inf > > To avoid such problem you can let repfreq to do the frequency > discretization. > [frq,repf]=repfreq (hz) or equivalently > [frq,repf]=repfreq (hz,0,0.5) > in this case the discretization uses varying frequency step > Serge > > Le 23/02/2016 14:41, grivet a ?crit : >> Le 23/02/2016 14:21, Serge Steer a ?crit : >>> Please can you give more details : >>> value of Order and Fcutoff/Fs/2 >>> and what you are doing with hz (because iir does not call dbphi) >>> Serge >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Wed Feb 24 14:43:01 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Wed, 24 Feb 2016 14:43:01 +0100 Subject: [Scilab-users] disp(a,b,c) => display a, b, and finally c ; not c, b and then a <= Re: News: Scilab 6 Beta, VISA Toolbox, Embedded World 2016 In-Reply-To: <56C488B8.80504@free.fr> References: <56C1DEEF.6050905@scilab-enterprises.com> <56C1F02C.7010600@scilab-enterprises.com> <56C47BBA.6030200@free.fr> <56C47FD6.9040504@laas.fr> <56C488B8.80504@free.fr> Message-ID: <56CDB365.4010100@free.fr> Le 17/02/2016 15:50, Samuel Gougeon a ?crit : > Le 17/02/2016 15:12, amonmayr at laas.fr a ?crit : >> >> What about adding to the list the infamous forgotten ";" after a huge >> matrix, aka "huge matrix display scrolling of death"? >> See >> http://mailinglists.scilab.org/Scilab-users-Accidentally-displaying-huge-matrices-tc4032315.html#a4032319 >> and http://bugzilla.scilab.org/show_bug.cgi?id=6286 >> It seems that a patch was proposed but never merged? > . > As reported here : http://bugzilla.scilab.org/3817 , the true issue is > that the display can't be interrupted with CTRL+C > It can also be fixed later without needing user code review. Actually, it is already fixed in Scilab 6.0-b1 :)) SG -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Wed Feb 24 15:27:40 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Wed, 24 Feb 2016 15:27:40 +0100 Subject: [Scilab-users] mprintf("%d *\n", nHiters, M) horizontal format iterator ? Message-ID: <56CDBDDC.6090607@free.fr> Hello, I am pretty sure that an horizontal iterator was recently implemented for the format used within mprintf(), but i am failing to find any information about how to use it. Or am i getting confused with this feature described in the/help print_conver//sion/ page: "A field width or precision can be indicated by an |*| (asterisk) instead of a digit string. In this case, an integer |value| parameter supplies the field width or precision. The |value| parameter converted for output is not fetched until the conversion letter is reached, so the parameters specifying field width or precision must appear before the value to be converted (if any)." ? By the way, i did not find any examples for any of both features in help pages of m*print() functions. Thanks for any help Regards Samuel Gougeon -------------- next part -------------- An HTML attachment was scrubbed... URL: From clement.david at scilab-enterprises.com Wed Feb 24 17:05:50 2016 From: clement.david at scilab-enterprises.com (=?ISO-8859-1?Q?Cl=E9ment?= David) Date: Wed, 24 Feb 2016 17:05:50 +0100 Subject: [Scilab-users] ?==?utf-8?q? Bug of input function in Scilab 6.0 beta 1 In-Reply-To: <7ed8-56cc9680-23-a922560@180664195> References: <7ed8-56cc9680-23-a922560@180664195> Message-ID: <1456329950.3141.6.camel@scilab-enterprises.com> Hi Antoine, Note sure about that, we have to investigate more on that point and opening two bug will leave the door open to solving issues in two ways. -- Cl?ment Le mardi 23 f?vrier 2016 ? 18:27 +0100, Antoine Monmayrant a ?crit?: > ? > Le Mardi 23 F?vrier 2016 17:16 CET, Cl?ment David a ?crit:? > ? > > Hi Wolfgang, > > > > It seems to be a bug, please report it. > > Is this related to the previous 'input()' bug reported here (crashing for long input string)? From clement.david at scilab-enterprises.com Wed Feb 24 17:10:19 2016 From: clement.david at scilab-enterprises.com (=?ISO-8859-1?Q?Cl=E9ment?= David) Date: Wed, 24 Feb 2016 17:10:19 +0100 Subject: [Scilab-users] mprintf("%d *\n", nHiters, M) horizontal format iterator ? In-Reply-To: <56CDBDDC.6090607@free.fr> References: <56CDBDDC.6090607@free.fr> Message-ID: <1456330219.3141.9.camel@scilab-enterprises.com> Hi Samuel, Le mercredi 24 f?vrier 2016 ? 15:27 +0100, Samuel Gougeon a ?crit?: > I am pretty sure that an horizontal iterator was recently implemented for the format? > used within mprintf(), but i am failing to find any information about how to use it. What do you mean by "horizontal iterator" ? Is it like the "argument_index$" for Java [1] ? [1]:?http://docs.oracle.com/javase/8/docs/api/java/util/Formatter.html -- Cl?ment From sgougeon at free.fr Wed Feb 24 18:06:22 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Wed, 24 Feb 2016 18:06:22 +0100 Subject: [Scilab-users] mprintf("%d *\n", nHiters, M) horizontal format iterator ? In-Reply-To: <1456330219.3141.9.camel@scilab-enterprises.com> References: <56CDBDDC.6090607@free.fr> <1456330219.3141.9.camel@scilab-enterprises.com> Message-ID: <56CDE30E.3050801@free.fr> Le 24/02/2016 17:10, Cl?ment David a ?crit : > Hi Samuel, > > Le mercredi 24 f?vrier 2016 ? 15:27 +0100, Samuel Gougeon a ?crit : >> I am pretty sure that an horizontal iterator was recently implemented for the format >> used within mprintf(), but i am failing to find any information about how to use it. > What do you mean by "horizontal iterator" ? Is it like the "argument_index$" for Java [1] ? I don't know much java, but as Fortran format allows it with "#(...)", this one replicates at most #times the content of () (that may have other (...) patterns (recursive replication/substitution))... Then, for all provided data, the format is feed with row-wise input data and builds the output with replicating the format as many times as some input data remain (for the current row), and then stop without error (even before the end of the format). Unfortunately, write() that could manage such a handy fortran format is not well implemented: * the write() format cannot mix input data types (bug 3798) * when the write() format meets a string (a), its parsing stops (bug 12476) Being so handicaped, write() has not much interest wrt mprintf(), and AFAIK, there is presently no native Scilab function handling input data in this way. We are compelled to use things like this msprintf(): --> NL=4; NC=6; Nchar=5; --> data = matrix(strsplit(ascii(grand(NL*NC*Nchar,1,"uin",32,126)),(1:NL*NC-1)*Nchar),NL,NC) data = !/6QV0 L)3zw I mprintf(strcat(emptystr(1,size(data,2))+"%10s ")+"\n", data) /6QV0 L)3zw I write(%io(2), data, "((2x a))") /6QV0 +`kUF FdBRS xJZH3 L)3zw !'{*` !Gsp" W!(g" I From amonmayr at laas.fr Wed Feb 24 18:11:18 2016 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Wed, 24 Feb 2016 18:11:18 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ICBkaXNwKGEsYixjKT89PT91?= =?utf-8?b?dGYtOD9xPyA9PiBkaXNwbGF5IGEsPz09P3V0Zi04P3E/IGIsIGFuZCBmaW5h?= =?utf-8?b?bGx5IGMgOyBub3QgYywgYiBhbmQgdGhlbiBhIDw9Pz09P3V0Zi04P3E/IFJl?= =?utf-8?q?=3A_News=3A_Scilab_6_Beta=2C_VISA_Toolbox=2C_Embedded_World_201?= =?utf-8?q?6?= In-Reply-To: <56CDB365.4010100@free.fr> Message-ID: <528-56cde400-3-16b63900@5856220> Le Mercredi 24 F?vrier 2016 14:43 CET, Samuel Gougeon a ?crit: > Le 17/02/2016 15:50, Samuel Gougeon a ?crit : > > Le 17/02/2016 15:12, amonmayr at laas.fr a ?crit : > >> > >> What about adding to the list the infamous forgotten ";" after a huge > >> matrix, aka "huge matrix display scrolling of death"? > >> See > >> http://mailinglists.scilab.org/Scilab-users-Accidentally-displaying-huge-matrices-tc4032315.html#a4032319 > >> and http://bugzilla.scilab.org/show_bug.cgi?id=6286 > >> It seems that a patch was proposed but never merged? > > . > > As reported here : http://bugzilla.scilab.org/3817 , the true issue is > > that the display can't be interrupted with CTRL+C > > It can also be fixed later without needing user code review. > > Actually, it is already fixed in Scilab 6.0-b1 :)) Neat! Ah ah, that's a good news. Thanks for the info. Antoine > > SG > From Serge.Steer at inria.fr Wed Feb 24 21:40:46 2016 From: Serge.Steer at inria.fr (Serge Steer) Date: Wed, 24 Feb 2016 21:40:46 +0100 Subject: [Scilab-users] bug in function iir ? In-Reply-To: <56CD8655.10403@cnrs-orleans.fr> References: <56B87251.7040903@laas.fr> <56BA3D8D.4070207@free.fr> <56CC40AA.6030506@cnrs-orleans.fr> <56CC5CC1.1050607@inria.fr> <56CC617F.3000508@cnrs-orleans.fr> <56CC6DE0.7040602@inria.fr> <56CD8655.10403@cnrs-orleans.fr> Message-ID: <56CE154E.40302@inria.fr> Le 24/02/2016 11:30, grivet a ?crit : > I appreciate your help; however, neither suggestion works: I still get > the same error message. > The similar line > [frq,repf]=repfreq(hz,0.01,0.49); > has no problem please can you save the hz value using the Scilab save function and send the file? Serge >> Your problem arises because one frequency value you ask for >> corresponds exactly to a zero of hz.num >> log(roots(hz.num))/(2*%pi) >> so you want to compute the gain in dB of a zero value which is -inf >> >> To avoid such problem you can let repfreq to do the frequency >> discretization. >> [frq,repf]=repfreq (hz) >> or equivalently >> [frq,repf]=repfreq (hz,0,0.5) >> in this case the discretization uses varying frequency step >> Serge >> >> Le 23/02/2016 14:41, grivet a ?crit : >>> Le 23/02/2016 14:21, Serge Steer a ?crit : >>>> Please can you give more details : >>>> value of Order and Fcutoff/Fs/2 >>>> and what you are doing with hz (because iir does not call dbphi) >>>> Serge >>> > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From Serge.Steer at inria.fr Wed Feb 24 21:54:23 2016 From: Serge.Steer at inria.fr (Serge Steer) Date: Wed, 24 Feb 2016 21:54:23 +0100 Subject: [Scilab-users] mprintf("%d *\n", nHiters, M) horizontal format iterator ? In-Reply-To: <56CDBDDC.6090607@free.fr> References: <56CDBDDC.6090607@free.fr> Message-ID: <56CE187F.5000007@inria.fr> As far as I know there is no iterator operator in C format, but it is quite easy to generate an "iterated format* using scilab. suppose the patterm of the format has been save in the variable f then the "iterated format" can be generated by strcat( f+emptystr(1,n)," ") //here I suppose the patterns are separated by a space example //Create the data x1=(1:5)';t1="sin(x)="+string(sin(x1));x2=(1:5)'/10;t2="cos(x)="+string(cos(x2)); f="x=%f %s";//The format template mprintf(strcat( f+emptystr(1,2)," ") +"\n",x1,t1,x2,t2) Le 24/02/2016 15:27, Samuel Gougeon a ?crit : > Hello, > > I am pretty sure that an horizontal iterator was recently implemented > for the format > used within mprintf(), but i am failing to find any information about > how to use it. > > Or am i getting confused with this feature described in the/help > print_conver//sion/ page: > > "A field width or precision can be indicated by an |*| (asterisk) > instead of a digit string. > In this case, an integer |value| parameter supplies the field width or > precision. > The |value| parameter converted for output is not fetched until the > conversion > letter is reached, so the parameters specifying field width or > precision must > appear before the value to be converted (if any)." > > ? > > By the way, i did not find any examples for any of both features in > help pages > of m*print() functions. > > Thanks for any help > Regards > Samuel Gougeon > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From W.Schulz at ove.at Thu Feb 25 16:00:49 2016 From: W.Schulz at ove.at (SCHULZ Wolfgang) Date: Thu, 25 Feb 2016 15:00:49 +0000 Subject: [Scilab-users] Bug of input function in Scilab 6.0 beta 1 Message-ID: <07A8AF089844A549B0F0CCC727AF31AA57A899D8@OVEKBG.ove.at> Clement, shoud I add my findings to the original bug report? In case of yes - which bug report number is it? Thanks Wolfgang > -----Urspr?ngliche Nachricht----- > Von: users [mailto:users-bounces at lists.scilab.org] Im Auftrag von Cl?ment > David > Gesendet: Mittwoch, 24. Februar 2016 17:06 > An: users at lists.scilab.org > Betreff: Re: [Scilab-users] ?==?utf-8?q? Bug of input function in Scilab 6.0 > beta 1 > > Hi Antoine, > > Note sure about that, we have to investigate more on that point and opening > two bug will leave the door open to solving issues in two ways. > > -- > Cl?ment > > > Le mardi 23 f?vrier 2016 ? 18:27 +0100, Antoine Monmayrant a ?crit?: > > > > Le Mardi 23 F?vrier 2016 17:16 CET, Cl?ment David > > a ?crit: > > > > > Hi Wolfgang, > > > > > > It seems to be a bug, please report it. > > > > Is this related to the previous 'input()' bug reported here (crashing for long > input string)? > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From clement.david at scilab-enterprises.com Thu Feb 25 16:05:10 2016 From: clement.david at scilab-enterprises.com (=?ISO-8859-1?Q?Cl=E9ment?= David) Date: Thu, 25 Feb 2016 16:05:10 +0100 Subject: [Scilab-users] Bug of input function in Scilab 6.0 beta 1 In-Reply-To: <07A8AF089844A549B0F0CCC727AF31AA57A899D8@OVEKBG.ove.at> References: <07A8AF089844A549B0F0CCC727AF31AA57A899D8@OVEKBG.ove.at> Message-ID: <1456412710.2439.6.camel@scilab-enterprises.com> Hi Wolfgang, It might be the?http://bugzilla.scilab.org/show_bug.cgi?id=14375?about input behavior. Regards, -- Cl?ment Le jeudi 25 f?vrier 2016 ? 15:00 +0000, SCHULZ Wolfgang a ?crit?: > Clement, > shoud I add my findings to the original bug report? In case of yes - which bug report number is > it? > Thanks > Wolfgang > > > > -----Urspr?ngliche Nachricht----- > > Von: users [mailto:users-bounces at lists.scilab.org] Im Auftrag von Cl?ment > > David > > Gesendet: Mittwoch, 24. Februar 2016 17:06 > > An: users at lists.scilab.org > > Betreff: Re: [Scilab-users] ?==?utf-8?q? Bug of input function in Scilab 6.0 > > beta 1 > > > > Hi Antoine, > > > > Note sure about that, we have to investigate more on that point and opening > > two bug will leave the door open to solving issues in two ways. > > > > -- > > Cl?ment > > > > > > Le mardi 23 f?vrier 2016 ? 18:27 +0100, Antoine Monmayrant a ?crit?: > > > > > > Le Mardi 23 F?vrier 2016 17:16 CET, Cl?ment David > > > a ?crit: > > > > > > > Hi Wolfgang, > > > > > > > > It seems to be a bug, please report it. > > > > > > Is this related to the previous 'input()' bug reported here (crashing for long > > input string)? > > > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/users > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From j-lan at online.no Thu Feb 25 17:53:05 2016 From: j-lan at online.no (JLan) Date: Thu, 25 Feb 2016 09:53:05 -0700 (MST) Subject: [Scilab-users] Bug of input function in Scilab 6.0 beta 1 In-Reply-To: <1456412710.2439.6.camel@scilab-enterprises.com> References: <07A8AF089844A549B0F0CCC727AF31AA57A879E1@OVEKBG.ove.at> <07A8AF089844A549B0F0CCC727AF31AA57A899D8@OVEKBG.ove.at> <1456412710.2439.6.camel@scilab-enterprises.com> Message-ID: <1456419185790-4033571.post@n3.nabble.com> I doubt that it is related to bug 14375. That seems to be caused by a long temporary prompt: prompt('CRASH CRASH CRASH CRASH CRASH CRASH CRASH CRASH CRASH CRASH CRASH >') But the behavior is certainly strange and inconsistent, should be reported as a separate bug. This is what I got once, but I cannot repeat it exactly: --> a=input("a:"); a:1 a:2 --> disp(a) 2. --> b=input('b:'); b:3 --> disp(b) 3. --> b=input("b:"); b:4 --> a=input("a:"); b:5 b:6 ans = 6. --> disp(a) 2. --> disp(b) 5. -- View this message in context: http://mailinglists.scilab.org/Scilab-users-Bug-of-input-function-in-Scilab-6-0-beta-1-tp4033549p4033571.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com. From grivet at cnrs-orleans.fr Thu Feb 25 18:10:07 2016 From: grivet at cnrs-orleans.fr (grivet) Date: Thu, 25 Feb 2016 18:10:07 +0100 Subject: [Scilab-users] bug in function iir ? In-Reply-To: <56CE154E.40302@inria.fr> References: <56B87251.7040903@laas.fr> <56BA3D8D.4070207@free.fr> <56CC40AA.6030506@cnrs-orleans.fr> <56CC5CC1.1050607@inria.fr> <56CC617F.3000508@cnrs-orleans.fr> <56CC6DE0.7040602@inria.fr> <56CD8655.10403@cnrs-orleans.fr> <56CE154E.40302@inria.fr> Message-ID: <56CF356F.1090108@cnrs-orleans.fr> Le 24/02/2016 21:40, Serge Steer a ?crit : > Le 24/02/2016 11:30, grivet a ?crit : >> I appreciate your help; however, neither suggestion works: I still >> get the same error message. >> The similar line >> [frq,repf]=repfreq(hz,0.01,0.49); >> has no problem > please can you save the hz value using the Scilab save function and > send the file? > Serge >>> Voila le code: //filtre Butterworth Order = 2; // The order of the filter Fs = 1000; // The sampling frequency Fcutoff = 40; // The cutoff frequency // We design a low pass Butterworth filter hz = iir(Order,'lp','butt',Fcutoff/Fs/2,[0.1 0.1]); // We compute the frequency response of the filter [frq,repf]=repfreq(hz,0,0.5); [db_repf, phi_repf] = dbphi(repf); // And plot the bode like representation of the digital filter subplot(2,1,1); plot2d(Fs*frq,db_repf); xtitle('Obtained Frequency Response (Magnitude)'); subplot(2,1,2); plot2d(Fs*frq,phi_repf); xtitle('Obtained Frequency Response (Phase in degree)'); iir est sauvegard? dans "svgd_iir" joint (binaire). Cordialement, JP Grivet -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: svgd_iir Type: application/octet-stream Size: 12608 bytes Desc: not available URL: From Jean-Yves.Baudais at insa-rennes.fr Fri Feb 26 09:17:26 2016 From: Jean-Yves.Baudais at insa-rennes.fr (jbaudais@insa-rennes.fr) Date: Fri, 26 Feb 2016 09:17:26 +0100 Subject: [Scilab-users] mprintf and backspace Message-ID: <56D00A16.3090602@insa-rennes.fr> Hello, I'd like to use \b, for backspace as in C, in mprintf function but it seems to not be implemented. How it can be obtained? (Only \n, \r and \t seems to be implemented.) Thanks, Jean-Yves From Serge.Steer at inria.fr Fri Feb 26 10:03:10 2016 From: Serge.Steer at inria.fr (Serge Steer) Date: Fri, 26 Feb 2016 10:03:10 +0100 Subject: [Scilab-users] bug in function iir ? In-Reply-To: <56CF356F.1090108@cnrs-orleans.fr> References: <56B87251.7040903@laas.fr> <56BA3D8D.4070207@free.fr> <56CC40AA.6030506@cnrs-orleans.fr> <56CC5CC1.1050607@inria.fr> <56CC617F.3000508@cnrs-orleans.fr> <56CC6DE0.7040602@inria.fr> <56CD8655.10403@cnrs-orleans.fr> <56CE154E.40302@inria.fr> <56CF356F.1090108@cnrs-orleans.fr> Message-ID: <56D014CE.20806@inria.fr> Le 25/02/2016 18:10, grivet a ?crit : > Le 24/02/2016 21:40, Serge Steer a ?crit : >> Le 24/02/2016 11:30, grivet a ?crit : >>> I appreciate your help; however, neither suggestion works: I still >>> get the same error message. >>> The similar line >>> [frq,repf]=repfreq(hz,0.01,0.49); >>> has no problem You are right the problem is exactly for the frequency 0.5 besause exp(2*%pi*%i*0.5) -> - 1. + 1.225D-16i and hz.num has 2 zeros very near -1 I checked the hz value with Matlab, the results are the same. So it seems that hz is ok. So it is probabily a probleme due to floating point computations procucing a zero value instead of a very small one. Serge >> please can you save the hz value using the Scilab save function and >> send the file? >> Serge >>>> > Voila le code: > //filtre Butterworth > Order = 2; // The order of the filter > Fs = 1000; // The sampling frequency > Fcutoff = 40; // The cutoff frequency > > // We design a low pass Butterworth filter > hz = iir(Order,'lp','butt',Fcutoff/Fs/2,[0.1 0.1]); > > // We compute the frequency response of the filter > [frq,repf]=repfreq(hz,0,0.5); > [db_repf, phi_repf] = dbphi(repf); > > // And plot the bode like representation of the digital filter > subplot(2,1,1); > plot2d(Fs*frq,db_repf); > xtitle('Obtained Frequency Response (Magnitude)'); > subplot(2,1,2); > plot2d(Fs*frq,phi_repf); > xtitle('Obtained Frequency Response (Phase in degree)'); > > iir est sauvegard? dans "svgd_iir" joint (binaire). > > Cordialement, > JP Grivet > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From W.Schulz at ove.at Fri Feb 26 10:45:37 2016 From: W.Schulz at ove.at (SCHULZ Wolfgang) Date: Fri, 26 Feb 2016 09:45:37 +0000 Subject: [Scilab-users] Bug of input function in Scilab 6.0 beta 1 In-Reply-To: <1456419185790-4033571.post@n3.nabble.com> References: <07A8AF089844A549B0F0CCC727AF31AA57A879E1@OVEKBG.ove.at> <07A8AF089844A549B0F0CCC727AF31AA57A899D8@OVEKBG.ove.at> <1456412710.2439.6.camel@scilab-enterprises.com> <1456419185790-4033571.post@n3.nabble.com> Message-ID: <07A8AF089844A549B0F0CCC727AF31AA57A8A1B6@OVEKBG.ove.at> Ok, because it is not clear whether this bug is related to another one I decided to enter a new bug report: Bug 14424 Wolfgang > -----Urspr?ngliche Nachricht----- > Von: users [mailto:users-bounces at lists.scilab.org] Im Auftrag von JLan > Gesendet: Donnerstag, 25. Februar 2016 17:53 > An: users at lists.scilab.org > Betreff: Re: [Scilab-users] Bug of input function in Scilab 6.0 beta 1 > > I doubt that it is related to bug 14375. > That seems to be caused by a long temporary prompt: > prompt('CRASH CRASH CRASH CRASH CRASH CRASH CRASH CRASH CRASH > CRASH CRASH > >') > > But the behavior is certainly strange and inconsistent, should be reported as > a separate bug. This is what I got once, but I cannot repeat it exactly: > > --> a=input("a:"); > a:1 > a:2 > --> disp(a) > 2. > --> b=input('b:'); > b:3 > --> disp(b) > 3. > --> b=input("b:"); > b:4 > --> a=input("a:"); > b:5 > b:6 > ans = > 6. > --> disp(a) > 2. > --> disp(b) > 5. > > > > > > -- > View this message in context: http://mailinglists.scilab.org/Scilab-users-Bug- > of-input-function-in-Scilab-6-0-beta-1-tp4033549p4033571.html > Sent from the Scilab users - Mailing Lists Archives mailing list archive at > Nabble.com. > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From j-lan at online.no Fri Feb 26 11:43:13 2016 From: j-lan at online.no (=?UTF-8?Q?Jan_=c3=85ge_Langeland?=) Date: Fri, 26 Feb 2016 11:43:13 +0100 Subject: [Scilab-users] mprintf and backspace In-Reply-To: <56D00A16.3090602@insa-rennes.fr> References: <56D00A16.3090602@insa-rennes.fr> Message-ID: <56D02C41.8070008@online.no> ref. the somewhat related bug report: http://bugzilla.scilab.org/show_bug.cgi?id=14342 Jan ? From sgougeon at free.fr Fri Feb 26 12:14:44 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Fri, 26 Feb 2016 12:14:44 +0100 Subject: [Scilab-users] mprintf and backspace In-Reply-To: <56D00A16.3090602@insa-rennes.fr> References: <56D00A16.3090602@insa-rennes.fr> Message-ID: <56D033A4.5050605@free.fr> Hello, Le 26/02/2016 09:17, jbaudais at insa-rennes.fr a ?crit : > Hello, > > I'd like to use \b, for backspace as in C, in mprintf function but it > seems to not be implemented. How it can be obtained? (Only \n, \r and > \t seems to be implemented.) . with ascii(8) ? HTH Samuel From sgougeon at free.fr Fri Feb 26 12:29:34 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Fri, 26 Feb 2016 12:29:34 +0100 Subject: [Scilab-users] mprintf and backspace In-Reply-To: <56D033A4.5050605@free.fr> References: <56D00A16.3090602@insa-rennes.fr> <56D033A4.5050605@free.fr> Message-ID: <56D0371E.6090001@free.fr> Le 26/02/2016 12:14, Samuel Gougeon a ?crit : > Hello, > > Le 26/02/2016 09:17, jbaudais at insa-rennes.fr a ?crit : >> Hello, >> >> I'd like to use \b, for backspace as in C, in mprintf function but it >> seems to not be implemented. How it can be obtained? (Only \n, \r and >> \t seems to be implemented.) > . > with ascii(8) ? . apparently not (Scilab 5.5.2 and 6.0-b1): --> "abc"+ascii(8)+"def" ans = abcdef --> mprintf("abc"+ascii(8)+"def") abcdef SG From antoine.monmayrant at laas.fr Fri Feb 26 13:17:26 2016 From: antoine.monmayrant at laas.fr (antoine.monmayrant at laas.fr) Date: Fri, 26 Feb 2016 13:17:26 +0100 Subject: [Scilab-users] Maximum allocation with Scilab 6.0 beta Message-ID: <56D04256.8070206@laas.fr> Hi all, For testing purposes, I am trying to allocate big chunks of memory with scilab 6.0beta. I have ~256GB of free ram on my machine, however, Scilab fails creating variables that are way smaller than that: --> a=rand(100000,100000); Can not allocate 80000.00 MB memory. Any idea what is going on? What is the actual ram limitation with the new "stackless" scilab? Cheers, Antoine From antoine.monmayrant at laas.fr Fri Feb 26 13:24:34 2016 From: antoine.monmayrant at laas.fr (antoine.monmayrant at laas.fr) Date: Fri, 26 Feb 2016 13:24:34 +0100 Subject: [Scilab-users] Update: Maximum allocation with Scilab 6.0 beta In-Reply-To: <56D04256.8070206@laas.fr> References: <56D04256.8070206@laas.fr> Message-ID: <56D04402.2000102@laas.fr> Le 02/26/2016 01:17 PM, antoine.monmayrant at laas.fr a ?crit : > Hi all, > > For testing purposes, I am trying to allocate big chunks of memory > with scilab 6.0beta. > I have ~256GB of free ram on my machine, however, Scilab fails > creating variables that are way smaller than that: > > --> a=rand(100000,100000); > > Can not allocate 80000.00 MB memory. > > > Any idea what is going on? > What is the actual ram limitation with the new "stackless" scilab? > Here is some more infon: it seems to be a "per variable" limit. I can create many variables that are ~16GB, but cannot allocate one 32GB variable. Is this limitation documented somewhere? Antoine From sgougeon at free.fr Fri Feb 26 13:41:09 2016 From: sgougeon at free.fr (Samuel Gougeon) Date: Fri, 26 Feb 2016 13:41:09 +0100 Subject: [Scilab-users] Update: Maximum allocation with Scilab 6.0 beta In-Reply-To: <56D04402.2000102@laas.fr> References: <56D04256.8070206@laas.fr> <56D04402.2000102@laas.fr> Message-ID: <56D047E5.8070807@free.fr> Le 26/02/2016 13:24, antoine.monmayrant at laas.fr a ?crit : > Le 02/26/2016 01:17 PM, antoine.monmayrant at laas.fr a ?crit : >> Hi all, >> >> For testing purposes, I am trying to allocate big chunks of memory >> with scilab 6.0beta. >> I have ~256GB of free ram on my machine, however, Scilab fails >> creating variables that are way smaller than that: >> >> --> a=rand(100000,100000); . With Scilab <6, the maximal number of components in a matrix is 2^31-1, since their linearized index is encoded with 4-byte-signed integers. Now, 1e10 is bigger than that. I do not think that this limit is removed in Scilab 6, but a confirmation from the dev team would be useful. So here, the misleading message could come from this "index limit", without respect to the available or allocatable memory. HTH Samuel From antoine.monmayrant at laas.fr Fri Feb 26 14:08:52 2016 From: antoine.monmayrant at laas.fr (Antoine Monmayrant) Date: Fri, 26 Feb 2016 14:08:52 +0100 Subject: [Scilab-users] Update: Maximum allocation with Scilab 6.0 beta In-Reply-To: <56D047E5.8070807@free.fr> References: <56D04256.8070206@laas.fr> <56D04402.2000102@laas.fr> <56D047E5.8070807@free.fr> Message-ID: <56D04E64.1050805@laas.fr> Le 02/26/2016 01:41 PM, Samuel Gougeon a ?crit : > Le 26/02/2016 13:24, antoine.monmayrant at laas.fr a ?crit : >> Le 02/26/2016 01:17 PM, antoine.monmayrant at laas.fr a ?crit : >>> Hi all, >>> >>> For testing purposes, I am trying to allocate big chunks of memory >>> with scilab 6.0beta. >>> I have ~256GB of free ram on my machine, however, Scilab fails >>> creating variables that are way smaller than that: >>> >>> --> a=rand(100000,100000); > . > With Scilab <6, the maximal number of components in a matrix is > 2^31-1, since their linearized index is encoded with 4-byte-signed > integers. > Now, 1e10 is bigger than that. It seems that you are right. But things can get a bit funny: --> a=[1:2^31-2]; //no problemo --> a=[1:2^31-1]; //no problemo --> a=[1:2^31]; // no error, just never ending Antoine > I do not think that this limit is removed in Scilab 6, but a > confirmation from the dev team would be useful. > > So here, the misleading message could come from this "index limit", > without respect to the available or allocatable memory. > > HTH > Samuel > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > From jasper at amsterchem.com Fri Feb 26 14:33:41 2016 From: jasper at amsterchem.com (jasper van baten) Date: Fri, 26 Feb 2016 14:33:41 +0100 Subject: [Scilab-users] gateway compatibility Message-ID: <56D05435.50106@amsterchem.com> Dear all, I noticed that the gateway routines are not binary compatible between 6.0 alpha and 6.0 beta. Also the source has changed somewhat, so the ilib_gen_gateway has to be rerun to update source (particularly C_GATEWAY_PROTOTYPE changed to STACK_GATEWAY_PROTOTYPE) Will the 6.0 beta gateway routines be binary compatible with the 6.0 release? Many thanks, best wishes, Jasper. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rouxph.22 at gmail.com Mon Feb 29 20:17:55 2016 From: rouxph.22 at gmail.com (Philippe Roux) Date: Mon, 29 Feb 2016 12:17:55 -0700 (MST) Subject: [Scilab-users] Maxima(Symbolic) Toolbox In-Reply-To: References: Message-ID: <1456773475334-4033587.post@n3.nabble.com> hi, I use mainly scimax toolbox , they are 2 requirements : 1) you have to work on linux 2) you have to install the overload toolbox before scimax toolbox (install it from atoms from atoms) http://forge.scilab.org/index.php/p/overload/ then you can install scimax with scilab 5.5.2, I have not installed scimax from atoms but from git.forge.scilab (https://forge.scilab.org/index.php/p/scimax/source/tree/master/) . With the last versions of scilab/maxima some maxima functions can't be overloaded (like erf) so you have to modify some file created by build.sce to run the load.sce of scimax (see work around in https://forge.scilab.org/index.php/p/scimax/issues/1560/ ) for me it works perfectly, IMHO symbolic expressions are easier to handle in scilab (with scimax) than in wxmaxima, for examplescilab matrix of symbolic expression is really simpler than maxima ones, or writing text files from symbolic expression is so easy with scilab compared to maxima ! I should write some tutorial about it .... Philippe -- View this message in context: http://mailinglists.scilab.org/Scilab-users-Maxima-Symbolic-Toolbox-tp4033428p4033587.html Sent from the Scilab users - Mailing Lists Archives mailing list archive at Nabble.com.