From Jean-Yves.Baudais at insa-rennes.fr Mon Feb 1 10:31:50 2021 From: Jean-Yves.Baudais at insa-rennes.fr (Jean-Yves Baudais) Date: Mon, 1 Feb 2021 10:31:50 +0100 Subject: [Scilab-users] Update library and help In-Reply-To: <4cf60797-6e58-a4e5-30ca-a2193cd58c5f@free.fr> References: <651679944.417448.1611942448778.JavaMail.zimbra@insa-rennes.fr> <4cf60797-6e58-a4e5-30ca-a2193cd58c5f@free.fr> Message-ID: Le 30/01/2021 ? 15:42, Samuel Gougeon a ?crit?: > Thanks Philipp, > Now i can answer inside the recovered thread: > > Jean-Yves, i remember -- from another thread -- that you are running all > this with Scilab 5.5.2. Aren't you? Yes I am. I also did tests on Scilab 6.1.0, but not on my computer. > Well, for more than 6 years that 5.5.2 was released, a lot of things > were done, noticeably about fixing some help_from_sci bugs. > Have you checked fixed bugs? If you installed uman, > --> uman help_from_sci b > I didn't see any corresponding bug report. Anyway, I will first update my numerical environment (OS, tools, own libraries...) as soon as possible and comeback if needed. Thanks, --Jean-Yves From sgougeon at free.fr Mon Feb 1 23:26:59 2021 From: sgougeon at free.fr (Samuel Gougeon) Date: Mon, 1 Feb 2021 23:26:59 +0100 Subject: [Scilab-users] Default x|y|z labels and title font size = 2? Message-ID: <454e2c08-0535-9c4e-aa70-ad6860be803b@free.fr> Dear all, After having changed the default grid style in Scilab 6.1.0, i propose to go on, tuning more carefully the default font size of axes labels. Each time that i define a xlabel, ylabel or sometimes zlabel, and a title, i have also to set explicitly their fontsize property, because i find the default size=1 always too small. Is it also your usage? Indeed, the font size = 1 is fine for ticks labels. From here, axes labels must be displayed with a bigger font size. Sometime size=2 is still not enough, noticeably with a LaTeX content. But well, then we can actually use an explicit fontsize setting. This proposal impacts everybody and frequently, because making plots is a basic task in Scilab Every comment is welcome, before implementing this simple change. Hope reading you soon. Samuel Gougeon clf subplot(1,3,1) plot2d xlabel "Title for abscissas" ylabel "Title for ordinates" subplot(1,3,2) xlabel "Title for abscissas" fontsize 2 ylabel "Title for ordinates" fontsize 2 plot2d subplot(1,3,3) xlabel "$\alpha\text{ coefficient }[m^{-1}]$" fontsize 2 ylabel "$\beta\text{ result }[lm^{-1}]$" fontsize 2 plot2d -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: oncnhnldchdgigpi.png Type: image/png Size: 23866 bytes Desc: not available URL: From denis.crete at thalesgroup.com Tue Feb 2 09:39:04 2021 From: denis.crete at thalesgroup.com (CRETE Denis) Date: Tue, 2 Feb 2021 08:39:04 +0000 Subject: [Scilab-users] Default x|y|z labels and title font size = 2? In-Reply-To: <454e2c08-0535-9c4e-aa70-ad6860be803b@free.fr> References: <454e2c08-0535-9c4e-aa70-ad6860be803b@free.fr> Message-ID: <53b416003338445b8641a15e54d5e292@thalesgroup.com> Hello , Very good idea ! I actually defined a function to perform xtitle and immediately increase font sizes for the axes labels, axis titles and title of the figure. I originally set them to a size of 2 for the labels and 3 for the titles. Still, the reviewers for publications seldom complain about too large font sizes, much more about too small font sizes! For these applications, the risk of having to change the font sizes upon revision of a paper is smaller with default font sizes of 3 for the labels and 4 (or even 5 when LaTeX style is used) for the titles ? Best regards Denis De : users De la part de Samuel Gougeon Envoy? : lundi 1 f?vrier 2021 23:27 ? : International users mailing list for Scilab. Objet : [Scilab-users] Default x|y|z labels and title font size = 2? Dear all, After having changed the default grid style in Scilab 6.1.0, i propose to go on, tuning more carefully the default font size of axes labels. Each time that i define a xlabel, ylabel or sometimes zlabel, and a title, i have also to set explicitly their fontsize property, because i find the default size=1 always too small. Is it also your usage? Indeed, the font size = 1 is fine for ticks labels. From here, axes labels must be displayed with a bigger font size. Sometime size=2 is still not enough, noticeably with a LaTeX content. But well, then we can actually use an explicit fontsize setting. This proposal impacts everybody and frequently, because making plots is a basic task in Scilab Every comment is welcome, before implementing this simple change. Hope reading you soon. Samuel Gougeon clf subplot(1,3,1) plot2d xlabel "Title for abscissas" ylabel "Title for ordinates" subplot(1,3,2) xlabel "Title for abscissas" fontsize 2 ylabel "Title for ordinates" fontsize 2 plot2d subplot(1,3,3) xlabel "$\alpha\text{ coefficient }[m^{-1}]$" fontsize 2 ylabel "$\beta\text{ result }[lm^{-1}]$" fontsize 2 plot2d [cid:image001.png at 01D6F93C.C37F9280] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 23866 bytes Desc: image001.png URL: From stephane.mottelet at utc.fr Tue Feb 2 09:52:09 2021 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Tue, 2 Feb 2021 09:52:09 +0100 Subject: [Scilab-users] Default x|y|z labels and title font size = 2? In-Reply-To: <454e2c08-0535-9c4e-aa70-ad6860be803b@free.fr> References: <454e2c08-0535-9c4e-aa70-ad6860be803b@free.fr> Message-ID: <046f82a6-ea9e-9e73-acdf-a6a957da3733@utc.fr> Hi, +1 for this missing feature. But since the name of the concerned Label entity property of is "font_size" I would recommend to use it instead of "fontsize". S. Le 01/02/2021 ? 23:26, Samuel Gougeon a ?crit?: > > Dear all, > > After having changed the default grid style in Scilab 6.1.0, i propose > to go on, tuning more carefully the default font size of axes labels. > > Each time that i define a xlabel, ylabel or sometimes zlabel, and a > title, i have also to set explicitly their fontsize property, because > i find the default size=1 always too small. > Is it also your usage? > Indeed, the font size = 1 is fine for ticks labels. From here, axes > labels must be displayed with a bigger font size. > Sometime size=2 is still not enough, noticeably with a LaTeX content. > But well, then we can actually use an explicit fontsize setting. > > This proposal impacts everybody and frequently, because making plots > is a basic task in Scilab > Every comment is welcome, before implementing this simple change. > > Hope reading you soon. > > Samuel Gougeon > > clf > subplot(1,3,1) > plot2d > xlabel "Title for abscissas" > ylabel "Title for ordinates" > > subplot(1,3,2) > xlabel "Title for abscissas" fontsize 2 > ylabel "Title for ordinates" fontsize 2 > plot2d > > subplot(1,3,3) > xlabel "$\alpha\text{ coefficient }[m^{-1}]$" fontsize 2 > ylabel "$\beta\text{ result }[lm^{-1}]$" fontsize 2 > plot2d > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users -- St?phane Mottelet Ing?nieur de recherche EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable D?partement G?nie des Proc?d?s Industriels Sorbonne Universit?s - Universit? de Technologie de Compi?gne CS 60319, 60203 Compi?gne cedex Tel : +33(0)344234688 http://www.utc.fr/~mottelet -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: oncnhnldchdgigpi.png Type: image/png Size: 23866 bytes Desc: not available URL: From david.cheze at cea.fr Tue Feb 2 08:59:17 2021 From: david.cheze at cea.fr (CHEZE David 227480) Date: Tue, 2 Feb 2021 07:59:17 +0000 Subject: [Scilab-users] Default x|y|z labels and title font size = 2? In-Reply-To: <454e2c08-0535-9c4e-aa70-ad6860be803b@free.fr> References: <454e2c08-0535-9c4e-aa70-ad6860be803b@free.fr> Message-ID: Dear Samuel, I also have the same feeling that larger default font size would suit better, most of the time, as in the end the figures worked and analysed in Scilab environment are inserted into reports. Regards, David De : users De la part de Samuel Gougeon Envoy? : lundi 1 f?vrier 2021 23:27 ? : International users mailing list for Scilab. Objet : [Scilab-users] Default x|y|z labels and title font size = 2? Dear all, After having changed the default grid style in Scilab 6.1.0, i propose to go on, tuning more carefully the default font size of axes labels. Each time that i define a xlabel, ylabel or sometimes zlabel, and a title, i have also to set explicitly their fontsize property, because i find the default size=1 always too small. Is it also your usage? Indeed, the font size = 1 is fine for ticks labels. From here, axes labels must be displayed with a bigger font size. Sometime size=2 is still not enough, noticeably with a LaTeX content. But well, then we can actually use an explicit fontsize setting. This proposal impacts everybody and frequently, because making plots is a basic task in Scilab Every comment is welcome, before implementing this simple change. Hope reading you soon. Samuel Gougeon clf subplot(1,3,1) plot2d xlabel "Title for abscissas" ylabel "Title for ordinates" subplot(1,3,2) xlabel "Title for abscissas" fontsize 2 ylabel "Title for ordinates" fontsize 2 plot2d subplot(1,3,3) xlabel "$\alpha\text{ coefficient }[m^{-1}]$" fontsize 2 ylabel "$\beta\text{ result }[lm^{-1}]$" fontsize 2 plot2d [cid:image001.png at 01D6F941.AF9FE350] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 23866 bytes Desc: image001.png URL: From antoine.monmayrant at laas.fr Tue Feb 2 10:51:38 2021 From: antoine.monmayrant at laas.fr (Antoine Monmayrant) Date: Tue, 2 Feb 2021 10:51:38 +0100 Subject: [Scilab-users] Default x|y|z labels and title font size = 2? In-Reply-To: <454e2c08-0535-9c4e-aa70-ad6860be803b@free.fr> References: <454e2c08-0535-9c4e-aa70-ad6860be803b@free.fr> Message-ID: <4727c53e-2b82-b583-2f15-0d74e7c43e00@laas.fr> Hello Samuel, Le 01/02/2021 ? 23:26, Samuel Gougeon a ?crit?: > > Dear all, > > After having changed the default grid style in Scilab 6.1.0, i propose > to go on, tuning more carefully the default font size of axes labels. > > Each time that i define a xlabel, ylabel or sometimes zlabel, and a > title, i have also to set explicitly their fontsize property, because > i find the default size=1 always too small. > Is it also your usage? > Yes! > > Indeed, the font size = 1 is fine for ticks labels. From here, axes > labels must be displayed with a bigger font size. > Sometime size=2 is still not enough, noticeably with a LaTeX content. > But well, then we can actually use an explicit fontsize setting. > Indeed, I usually use font_size=4 or 5 when using LaTeX strings. > > > This proposal impacts everybody and frequently, because making plots > is a basic task in Scilab > Every comment is welcome, before implementing this simple change. > I have a comment concerning the syntax. I'm not particularly fan of the "inline" syntax without parenthesis. Is your: ??? xlabel "Title for abscissas" fontsize 2 syntaxic sugar for ??? xlabel( "Title for abscissas", fontsize=2) or something equivalent? Antoine > > Hope reading you soon. > > Samuel Gougeon > > clf > subplot(1,3,1) > plot2d > xlabel "Title for abscissas" > ylabel "Title for ordinates" > > subplot(1,3,2) > xlabel "Title for abscissas" fontsize 2 > ylabel "Title for ordinates" fontsize 2 > plot2d > > subplot(1,3,3) > xlabel "$\alpha\text{ coefficient }[m^{-1}]$" fontsize 2 > ylabel "$\beta\text{ result }[lm^{-1}]$" fontsize 2 > plot2d > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: oncnhnldchdgigpi.png Type: image/png Size: 23866 bytes Desc: not available URL: From p.muehlmann at gmail.com Tue Feb 2 10:52:32 2021 From: p.muehlmann at gmail.com (P M) Date: Tue, 2 Feb 2021 10:52:32 +0100 Subject: [Scilab-users] Default x|y|z labels and title font size = 2? In-Reply-To: References: <454e2c08-0535-9c4e-aa70-ad6860be803b@free.fr> Message-ID: Dear Samual, thanks for the proposal...I fully agree with it. Best Regards, Philipp Am Di., 2. Feb. 2021 um 09:53 Uhr schrieb CHEZE David 227480 < david.cheze at cea.fr>: > Dear Samuel, > > > > I also have the same feeling that larger default font size would suit > better, most of the time, as in the end the figures worked and analysed in > Scilab environment are inserted into reports. > > > > Regards, > > > > David > > > > *De :* users *De la part de* Samuel > Gougeon > *Envoy? :* lundi 1 f?vrier 2021 23:27 > *? :* International users mailing list for Scilab. > > *Objet :* [Scilab-users] Default x|y|z labels and title font size = 2? > > > > Dear all, > > After having changed the default grid style in Scilab 6.1.0, i propose to > go on, tuning more carefully the default font size of axes labels. > > Each time that i define a xlabel, ylabel or sometimes zlabel, and a title, > i have also to set explicitly their fontsize property, because i find the > default size=1 always too small. > Is it also your usage? > Indeed, the font size = 1 is fine for ticks labels. From here, axes labels > must be displayed with a bigger font size. > Sometime size=2 is still not enough, noticeably with a LaTeX content. But > well, then we can actually use an explicit fontsize setting. > > This proposal impacts everybody and frequently, because making plots is a > basic task in Scilab > Every comment is welcome, before implementing this simple change. > > Hope reading you soon. > > Samuel Gougeon > > clf > > subplot(1,3,1) > > plot2d > > xlabel "Title for abscissas" > > ylabel "Title for ordinates" > > > > subplot(1,3,2) > > xlabel "Title for abscissas" fontsize 2 > > ylabel "Title for ordinates" fontsize 2 > > plot2d > > > > subplot(1,3,3) > > xlabel "$\alpha\text{ coefficient }[m^{-1}]$" fontsize 2 > > ylabel "$\beta\text{ result }[lm^{-1}]$" fontsize 2 > > plot2d > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 23866 bytes Desc: not available URL: From cfuttrup at gmail.com Tue Feb 2 17:02:40 2021 From: cfuttrup at gmail.com (Claus Futtrup) Date: Tue, 2 Feb 2021 17:02:40 +0100 Subject: [Scilab-users] Default x|y|z labels and title font size = 2? In-Reply-To: <454e2c08-0535-9c4e-aa70-ad6860be803b@free.fr> References: <454e2c08-0535-9c4e-aa70-ad6860be803b@free.fr> Message-ID: <49b91a73-cb7d-d640-3131-6558a010433a@gmail.com> Hi Samuel I agree. The font is always too small. The font = 2 seems to be the smallest feasible increment and it sounds like a good one (i.e. without overdoing it). You mention grid. I always do xgrid(color("grey70")); ... is this default now, to have the grid a bit greyed? Cheers, Claus On 01-02-2021 23:26, Samuel Gougeon wrote: > > Dear all, > > After having changed the default grid style in Scilab 6.1.0, i propose > to go on, tuning more carefully the default font size of axes labels. > > Each time that i define a xlabel, ylabel or sometimes zlabel, and a > title, i have also to set explicitly their fontsize property, because > i find the default size=1 always too small. > Is it also your usage? > Indeed, the font size = 1 is fine for ticks labels. From here, axes > labels must be displayed with a bigger font size. > Sometime size=2 is still not enough, noticeably with a LaTeX content. > But well, then we can actually use an explicit fontsize setting. > > This proposal impacts everybody and frequently, because making plots > is a basic task in Scilab > Every comment is welcome, before implementing this simple change. > > Hope reading you soon. > > Samuel Gougeon > > clf > subplot(1,3,1) > plot2d > xlabel "Title for abscissas" > ylabel "Title for ordinates" > > subplot(1,3,2) > xlabel "Title for abscissas" fontsize 2 > ylabel "Title for ordinates" fontsize 2 > plot2d > > subplot(1,3,3) > xlabel "$\alpha\text{ coefficient }[m^{-1}]$" fontsize 2 > ylabel "$\beta\text{ result }[lm^{-1}]$" fontsize 2 > plot2d > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: oncnhnldchdgigpi.png Type: image/png Size: 23866 bytes Desc: not available URL: From p.muehlmann at gmail.com Mon Feb 8 21:36:42 2021 From: p.muehlmann at gmail.com (P M) Date: Mon, 8 Feb 2021 21:36:42 +0100 Subject: [Scilab-users] xpoly in x-y-z coordinates Message-ID: Dear Users, I have a 3D-plot. Onto that, I would like to add a xpoly-line with the following specs: xpoly ( [0 1], [0 0], [-0.4 -0.4], 'lines' 0) in other words: The polyline should be at the X-Y Plane, but shifted to Z = -0.4 I know that I can just plot the line, but that would destroy the layout, which I would have to reconfigure. Similary to that I also would like xstring-Text in such a manner. Is something like this possible?....xpoly3D() ? Thank you, Philipp -------------- next part -------------- An HTML attachment was scrubbed... URL: From p.muehlmann at gmail.com Mon Feb 8 22:29:36 2021 From: p.muehlmann at gmail.com (P M) Date: Mon, 8 Feb 2021 22:29:36 +0100 Subject: [Scilab-users] xpoly in x-y-z coordinates In-Reply-To: References: Message-ID: sorry.... I am completely fine with xarrows instead of xpoly. Philipp Am Mo., 8. Feb. 2021 um 21:36 Uhr schrieb P M : > Dear Users, > > I have a 3D-plot. > > Onto that, I would like to add a xpoly-line with the following specs: > > xpoly ( [0 1], [0 0], [-0.4 -0.4], 'lines' 0) > > in other words: The polyline should be at the X-Y Plane, but shifted to Z > = -0.4 > > I know that I can just plot the line, but that would destroy the layout, > which I would have to reconfigure. > > Similary to that I also would like xstring-Text in such a manner. > > Is something like this possible?....xpoly3D() ? > > Thank you, Philipp > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fmiyara at fceia.unr.edu.ar Tue Feb 9 03:24:23 2021 From: fmiyara at fceia.unr.edu.ar (Federico Miyara) Date: Mon, 8 Feb 2021 23:24:23 -0300 Subject: [Scilab-users] slight bug in exists() Message-ID: Dear all, I had already mentioned this a while ago (http://mailinglists.scilab.org/Scilab-users-exists-yields-double-tt4039853.html), but as I guess we are in the update season, it would be good opportunity to fix this (if there isn't strong opposition, or a good reason for this behavior, of course). I'm referring to the fact that the function exists() should by nature yield a Boolean result such as T or F. However, it yields 1 or 0. While this is not a big deal, similar functions performing a binary decision on their arguments, such as isreal(), isvector(), isfile() and many others, yield Boolean results. Regards, Federico Miyara -- El software de antivirus Avast ha analizado este correo electr?nico en busca de virus. https://www.avast.com/antivirus -------------- next part -------------- An HTML attachment was scrubbed... URL: From antoine.monmayrant at laas.fr Tue Feb 9 04:27:48 2021 From: antoine.monmayrant at laas.fr (Antoine Monmayrant) Date: Tue, 9 Feb 2021 04:27:48 +0100 Subject: [Scilab-users] slight bug in exists() In-Reply-To: References: Message-ID: <7fbeab24-7f23-d8fd-a42b-75a60cc14b9c@laas.fr> Hello Federico, I agree with you that this would make more sense. Could such a change be implemented for a point release? I assume it would introduce some bugs in existing code relying on the (unusual) double output... Antoine On 09/02/2021 03:24, Federico Miyara wrote: > > Dear all, > > I had already mentioned this a while ago > (http://mailinglists.scilab.org/Scilab-users-exists-yields-double-tt4039853.html), > but as I guess we are in the update season, it would be good > opportunity to fix this (if there isn't strong opposition, or a good > reason for this behavior, of course). > > I'm referring to the fact that the function exists() should by nature > yield a Boolean result such as T or F. However, it yields 1 or 0. > While this is not a big deal, similar functions performing a binary > decision on their arguments, such as isreal(), isvector(), isfile() > and many others, yield Boolean results. > > Regards, > > Federico Miyara > > > Libre de virus. www.avast.com > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > _______________________________________________ > 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 esi-group.com Tue Feb 9 08:53:25 2021 From: Clement.David at esi-group.com (=?utf-8?B?Q2zDqW1lbnQgRGF2aWQ=?=) Date: Tue, 9 Feb 2021 07:53:25 +0000 Subject: [Scilab-users] slight bug in exists() In-Reply-To: <7fbeab24-7f23-d8fd-a42b-75a60cc14b9c@laas.fr> References: <7fbeab24-7f23-d8fd-a42b-75a60cc14b9c@laas.fr> Message-ID: Hello all, Indeed this would probably break some code. We should carefully check the exist() usage within Scilab to ensure the output value is not passed to macros/gateways checking for a ?double? datatype. Code using exists() output value as index or as condition might not be affected. Don?t hesitate to push such a change on the master branch I will review it. Thanks, Cl?ment From: users On Behalf Of Antoine Monmayrant Sent: Tuesday, February 9, 2021 4:28 AM To: users at lists.scilab.org Subject: Re: [Scilab-users] slight bug in exists() Hello Federico, I agree with you that this would make more sense. Could such a change be implemented for a point release? I assume it would introduce some bugs in existing code relying on the (unusual) double output... Antoine On 09/02/2021 03:24, Federico Miyara wrote: Dear all, I had already mentioned this a while ago (http://mailinglists.scilab.org/Scilab-users-exists-yields-double-tt4039853.html), but as I guess we are in the update season, it would be good opportunity to fix this (if there isn't strong opposition, or a good reason for this behavior, of course). I'm referring to the fact that the function exists() should by nature yield a Boolean result such as T or F. However, it yields 1 or 0. While this is not a big deal, similar functions performing a binary decision on their arguments, such as isreal(), isvector(), isfile() and many others, yield Boolean results. Regards, Federico Miyara [Image removed by sender.] Libre de virus. www.avast.com _______________________________________________ users mailing list users at lists.scilab.org http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 350 bytes Desc: image001.jpg URL: From fmiyara at fceia.unr.edu.ar Tue Feb 9 09:49:51 2021 From: fmiyara at fceia.unr.edu.ar (Federico Miyara) Date: Tue, 9 Feb 2021 05:49:51 -0300 Subject: [Scilab-users] slight bug in exists() In-Reply-To: <7fbeab24-7f23-d8fd-a42b-75a60cc14b9c@laas.fr> References: <7fbeab24-7f23-d8fd-a42b-75a60cc14b9c@laas.fr> Message-ID: <4149ea63-1646-ac81-fe3c-4d81f5db034b@fceia.unr.edu.ar> Antoine, Well, to be sure, there are some functions that do not work on booleans. For instance, mean(), max() and mean() will cause error; but not sum() and prod(). However, I think exists() is used mostly in conditionals, where both types work fine. And if getting errors, they can be easily solved by using double() to convert to double. This workaround could be included in the documentation. If not fixed in this release, a warning could be issued in the documentation that the current output argument type will be changed to boolean in the next release. Federico Miyara On 09/02/2021 00:27, Antoine Monmayrant wrote: > > Hello Federico, > > I agree with you that this would make more sense. > Could such a change be implemented for a point release? > I assume it would introduce some bugs in existing code relying on the > (unusual) double output... > > Antoine > > On 09/02/2021 03:24, Federico Miyara wrote: >> >> Dear all, >> >> I had already mentioned this a while ago >> (http://mailinglists.scilab.org/Scilab-users-exists-yields-double-tt4039853.html), >> but as I guess we are in the update season, it would be good >> opportunity to fix this (if there isn't strong opposition, or a good >> reason for this behavior, of course). >> >> I'm referring to the fact that the function exists() should by nature >> yield a Boolean result such as T or F. However, it yields 1 or 0. >> While this is not a big deal, similar functions performing a binary >> decision on their arguments, such as isreal(), isvector(), isfile() >> and many others, yield Boolean results. >> >> Regards, >> >> Federico Miyara >> >> >> Libre de virus. www.avast.com >> >> >> >> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >> >> _______________________________________________ >> 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 -- El software de antivirus Avast ha analizado este correo electr?nico en busca de virus. https://www.avast.com/antivirus -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Tue Feb 9 12:27:27 2021 From: sgougeon at free.fr (Samuel Gougeon) Date: Tue, 9 Feb 2021 12:27:27 +0100 Subject: [Scilab-users] exists yields double In-Reply-To: <58cbd60a-5380-80af-d1a2-38dd16e5adc2@fceia.unr.edu.ar> References: <58cbd60a-5380-80af-d1a2-38dd16e5adc2@fceia.unr.edu.ar> Message-ID: Hello Federico, Le 10/10/2019 ? 06:33, Federico Miyara a ?crit?: > > Dear all, > > I wonder why the function "exists" yields 1 or 0 as doubles, instead > of boolean. I know there is little distinction between booleans and > {0, 1} and can be easily converted back and forth. I also know that > Scilab is not meant to be a strongly typed language. But wouldn't it > make more sense that this kind of funtion yielded a boolean result? > > It challenges reason the fact that "isreal", for instance, yields a > boolean and "exists" yields a double. Please use isdef() instead. exists() is a pure duplicate of isdef(), except for the output type. Converting its output into a boolean was asked 9 years ago as bug 10892 . We should hate introducing such duplicates, that just multiply issues and confusion with strictly no added value. This is why its removal was proposed sortly after, as bug 11000 . To me, there is no added value either to convert exist()'s output into boolean, except if this function is actually removed, or at least masked, i.e. kept only for backcompatibility reason but undocumented. Best regards Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephane.mottelet at utc.fr Tue Feb 9 12:38:11 2021 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Tue, 9 Feb 2021 12:38:11 +0100 Subject: [Scilab-users] exists yields double In-Reply-To: References: <58cbd60a-5380-80af-d1a2-38dd16e5adc2@fceia.unr.edu.ar> Message-ID: <6a0ea73c-0f8b-652e-d48d-dd4e90554438@utc.fr> Hi, I completely agree with Samuel ! S. Le 09/02/2021 ? 12:27, Samuel Gougeon a ?crit?: > Hello Federico, > > Le 10/10/2019 ? 06:33, Federico Miyara a ?crit?: >> >> Dear all, >> >> I wonder why the function "exists" yields 1 or 0 as doubles, instead >> of boolean. I know there is little distinction between booleans and >> {0, 1} and can be easily converted back and forth. I also know that >> Scilab is not meant to be a strongly typed language. But wouldn't it >> make more sense that this kind of funtion yielded a boolean result? >> >> It challenges reason the fact that "isreal", for instance, yields a >> boolean and "exists" yields a double. > > > Please use isdef() instead. > > exists() is a pure duplicate of isdef(), except for the output type. > Converting its output into a boolean was asked 9 years ago as bug > 10892 > . > > We should hate introducing such duplicates, that just multiply issues > and confusion with strictly no added value. > This is why its removal was proposed sortly after, as bug 11000 > . > > To me, there is no added value either to convert exist()'s output into > boolean, except if this function is actually removed, or at least > masked, i.e. kept only for backcompatibility reason but undocumented. > > Best regards > > Samuel > > > _______________________________________________ > users mailing list > users at lists.scilab.org > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users -- St?phane Mottelet Ing?nieur de recherche EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable D?partement G?nie des Proc?d?s Industriels Sorbonne Universit?s - Universit? de Technologie de Compi?gne CS 60319, 60203 Compi?gne cedex Tel : +33(0)344234688 http://www.utc.fr/~mottelet -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Tue Feb 9 12:41:21 2021 From: sgougeon at free.fr (Samuel Gougeon) Date: Tue, 9 Feb 2021 12:41:21 +0100 Subject: [Scilab-users] exists yields double In-Reply-To: References: <58cbd60a-5380-80af-d1a2-38dd16e5adc2@fceia.unr.edu.ar> Message-ID: <05170fea-4f8a-7e79-6f29-bd749f89cde1@free.fr> Le 09/02/2021 ? 12:27, Samuel Gougeon a ?crit?: > ../... > > We should hate introducing such duplicates, that just multiply issues > and confusion with strictly no added value. > Actually, isdef() was introduced after exist(), just about this output type: http://bugzilla.scilab.org/show_bug.cgi?id=1011#c1 IMHO, this is a good example of an insufficient discussion about arguments, when exist() was introduced. Still, simply introducing duplicates to "fix" afterward issues, without deprecating and finally and *actually* removing the former syntax, or at least without undocumenting it, should be avoided as much as possible. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fmiyara at fceia.unr.edu.ar Tue Feb 9 19:33:29 2021 From: fmiyara at fceia.unr.edu.ar (Federico Miyara) Date: Tue, 9 Feb 2021 15:33:29 -0300 Subject: [Scilab-users] exists yields double In-Reply-To: References: <58cbd60a-5380-80af-d1a2-38dd16e5adc2@fceia.unr.edu.ar> Message-ID: Samuel, You are right, sorry I wasn't aware of isdef(). Regards, Federico On 09/02/2021 08:27, Samuel Gougeon wrote: > Hello Federico, > > Le 10/10/2019 ? 06:33, Federico Miyara a ?crit?: >> >> Dear all, >> >> I wonder why the function "exists" yields 1 or 0 as doubles, instead >> of boolean. I know there is little distinction between booleans and >> {0, 1} and can be easily converted back and forth. I also know that >> Scilab is not meant to be a strongly typed language. But wouldn't it >> make more sense that this kind of funtion yielded a boolean result? >> >> It challenges reason the fact that "isreal", for instance, yields a >> boolean and "exists" yields a double. > > > Please use isdef() instead. > > exists() is a pure duplicate of isdef(), except for the output type. > Converting its output into a boolean was asked 9 years ago as bug > 10892 . > > We should hate introducing such duplicates, that just multiply issues > and confusion with strictly no added value. > This is why its removal was proposed sortly after, as bug 11000 > . > > To me, there is no added value either to convert exist()'s output into > boolean, except if this function is actually removed, or at least > masked, i.e. kept only for backcompatibility reason but undocumented. > > Best regards > > Samuel > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -- El software de antivirus Avast ha analizado este correo electr?nico en busca de virus. https://www.avast.com/antivirus -------------- next part -------------- An HTML attachment was scrubbed... URL: From johan.lafitte at gmail.com Wed Feb 10 18:41:25 2021 From: johan.lafitte at gmail.com (Johan Lafitte) Date: Wed, 10 Feb 2021 18:41:25 +0100 Subject: [Scilab-users] xcos_simulate() Message-ID: Hi, My xcos model becomes quite large and takes time to compile. In order to launch batches and optimisation process, it seems possible to compile the model juste one time. However, I meet the same difficulties as described in this post : http://mailinglists.scilab.org/xcos-xcos-simulate-scs-m-1-or-xcos-simulate-scs-m-4-td4031207.html#a4031274">http://mailinglists.scilab.org/xcos-xcos-simulate-scs-m-1-or-xcos-simulate-scs-m-4-td4031207.html#a4031274 Indeed, the following script... * ___________________________________ * *loadXcosLibs;* *importXcosDiagram("C:\Users\johan\OneDrive\Micro entreprise\Technique\Kayak guide\Mod?lisation\Scilab\optimisation"+"\mod?le physique et commande simple_10_opti.zcos");* *tic();* *xcos_simulate(scs_m, 4);* *disp("m?thode 2",toc());* *tic();* *%cpr = xcos_compile(scs_m);* *disp( "Dur?e compilation",toc());* *tic();* *xcos_simulate(scs_m,1)* *disp( "m?thode 1",toc());* ___________________________________ ...gives the following results : ___________________________________ *"scicos_simulate step 1"* * 50.813412 s* * "scicos_simulate step 2"* * 57.440604 s* * "xcos_simulate(scs_m, 4) m?thode 2"* * 58.808546 s* * "Compilation duration"* * 55.615238 s* * "xcos_simulate(scs_m,1) m?thode 1"* *61.133700 s* ______________________________ It seems the compilation step is done in all these cases. *Thank you for your time and for your help* Johan note 1 : when the final time of the simulation is set from 20s to 200s, the execution time increases about 15s note 2 : according to the windows task manager, CPUs seem to be used about 30% during compilation and about 100% during simulation which takes few seconds -------------- next part -------------- An HTML attachment was scrubbed... URL: From p.muehlmann at gmail.com Wed Feb 10 19:19:25 2021 From: p.muehlmann at gmail.com (P M) Date: Wed, 10 Feb 2021 19:19:25 +0100 Subject: [Scilab-users] Scilab & cdf-file format Message-ID: Dear Users, Is there any Scilab toolbox available, handling the cdf-file-format? cdf = "common data file", which was original developed by NASA : https://cdf.gsfc.nasa.gov/ Thank you, Philipp -------------- next part -------------- An HTML attachment was scrubbed... URL: From p.muehlmann at gmail.com Wed Feb 10 19:44:53 2021 From: p.muehlmann at gmail.com (P M) Date: Wed, 10 Feb 2021 19:44:53 +0100 Subject: [Scilab-users] scicv - CV_FOURCC Message-ID: Dear , from the scicv toolbox I use the new_VideoWriter - function: videoWriter = new_VideoWriter(filename, fourcc, fps, frameSize) Everything fine so far, except: There are artefacts in the final video., which I guess are connected to compression. Here are some lines from my code: videoWriter = new_VideoWriter(outPath, CV_FOURCC('M', 'P', '4', '2'), frameRate, size(img)); if ~VideoWriter_isOpened(videoWriter) then disp("Cannot create video file: " + outPath);end for i = 1:nrOfFiles img = imread(inPath(i)); VideoWriter_write(videoWriter, img); disp(i)end delete_VideoWriter(videoWriter); *Question 1:* What other formats are possible for "CV_FOURCC"? I just used 'M', 'P', '4', '2' , because it's the only mentioned in the help. *Question 2:* What format should - ideally - the input images have? Currently I use BMP's, created with xs2bmp. Thank you, Philipp -------------- next part -------------- An HTML attachment was scrubbed... URL: From fmiyara at fceia.unr.edu.ar Thu Feb 11 08:12:30 2021 From: fmiyara at fceia.unr.edu.ar (Federico Miyara) Date: Thu, 11 Feb 2021 04:12:30 -0300 Subject: [Scilab-users] Why window() provides only symmetric weighting? Message-ID: Dear All, I wonder why windowing functions such as Hann, Hamming, etc., provided by window(), are only symmetric. When used for spectral analysis by subsequent use of fft(), the periodic weighting is better than the symmetric one. The symmetric window is mainly used in the design of FIR filters, which I guess is a less frequent application than spectral analysis. While it is true that an easy workaround to get a periodic window of length n is, for instance w = window("hn", n+1)(1:$-1); a syntax such as this w = window("hn", n, "per"); would be easier.Setting "sym" as the default option, no backward compatibility issues would possibly arise. Regards, Federico Miyara -- El software de antivirus Avast ha analizado este correo electr?nico en busca de virus. https://www.avast.com/antivirus -------------- next part -------------- An HTML attachment was scrubbed... URL: From Clement.David at esi-group.com Thu Feb 11 09:57:29 2021 From: Clement.David at esi-group.com (=?utf-8?B?Q2zDqW1lbnQgRGF2aWQ=?=) Date: Thu, 11 Feb 2021 08:57:29 +0000 Subject: [Scilab-users] Scilab & cdf-file format In-Reply-To: References: Message-ID: Hello, From my knowledge there is no existing toolbox to manage this CDF format. However conversion tools exists [1] that can convert CDF to HDF4 and HDF4 to HDF5 (natively supported by Scilab) ; IMHO this will be the simpler way to handle that format. You could also : 1. use SWIG to create your own toolbox mapping the C API to Scilab OR 1. the CDFj package to call CDF function using Java from Scilab (there might be some dataset copies) [1]: https://cdf.gsfc.nasa.gov/html/faq.html#conversion Regards, Cl?ment From: users On Behalf Of P M Sent: Wednesday, February 10, 2021 7:19 PM To: International users mailing list for Scilab. Subject: [Scilab-users] Scilab & cdf-file format Dear Users, Is there any Scilab toolbox available, handling the cdf-file-format? cdf = "common data file", which was original developed by NASA : https://cdf.gsfc.nasa.gov/ Thank you, Philipp -------------- next part -------------- An HTML attachment was scrubbed... URL: From Clement.David at esi-group.com Thu Feb 11 10:09:48 2021 From: Clement.David at esi-group.com (=?utf-8?B?Q2zDqW1lbnQgRGF2aWQ=?=) Date: Thu, 11 Feb 2021 09:09:48 +0000 Subject: [Scilab-users] scicv - CV_FOURCC In-Reply-To: References: Message-ID: Hello Philipp, Question 1: What other formats are possible for "CV_FOURCC"? https://www.fourcc.org/ describes what exist and might be supported by our binary. The codecs are only the ones supported by ffmpeg (included as a DLLs) or your system ones. Question 2: What format should - ideally - the input images have? Currently I use BMP's, created with xs2bmp. Yes BMP is fine. The rational are ; for a better encoding, use lossless image format ; for speed use non-compressed ones. Thanks, Cl?ment From: users On Behalf Of P M Sent: Wednesday, February 10, 2021 7:45 PM To: International users mailing list for Scilab. Subject: [Scilab-users] scicv - CV_FOURCC Dear , from the scicv toolbox I use the new_VideoWriter - function: videoWriter = new_VideoWriter(filename, fourcc, fps, frameSize) Everything fine so far, except: There are artefacts in the final video., which I guess are connected to compression. Here are some lines from my code: videoWriter = new_VideoWriter(outPath, CV_FOURCC('M', 'P', '4', '2'), frameRate, size(img)); if ~VideoWriter_isOpened(videoWriter) then disp("Cannot create video file: " + outPath); end for i = 1:nrOfFiles img = imread(inPath(i)); VideoWriter_write(videoWriter, img); disp(i) end delete_VideoWriter(videoWriter); Question 1: What other formats are possible for "CV_FOURCC"? I just used 'M', 'P', '4', '2' , because it's the only mentioned in the help. Question 2: What format should - ideally - the input images have? Currently I use BMP's, created with xs2bmp. Thank you, Philipp -------------- next part -------------- An HTML attachment was scrubbed... URL: From arctica1963 at gmail.com Fri Feb 12 15:55:34 2021 From: arctica1963 at gmail.com (arctica1963) Date: Fri, 12 Feb 2021 07:55:34 -0700 (MST) Subject: [Scilab-users] Scilab & cdf-file format In-Reply-To: References: Message-ID: <1613141734608-0.post@n3.nabble.com> Hello There is a toolbox for 5.5.2 called scinetcdf which will work - this will work with the standard netCDF format. However, it will not work in version 6.x of Scilab. Perhaps a Scilab expert could look at how to get it compiled for the latest Scilab? Cheers Lester -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From sgougeon at free.fr Fri Feb 12 21:25:36 2021 From: sgougeon at free.fr (Samuel Gougeon) Date: Fri, 12 Feb 2021 21:25:36 +0100 Subject: [Scilab-users] Scilab & cdf-file format In-Reply-To: <1613141734608-0.post@n3.nabble.com> References: <1613141734608-0.post@n3.nabble.com> Message-ID: <216626ca-842d-6cb4-fd87-b2876764680f@free.fr> Le 12/02/2021 ? 15:55, arctica1963 a ?crit?: > Hello > > There is a toolbox for 5.5.2 called scinetcdf which will work - this will > work with the standard netCDF format. However, it will not work in version > 6.x of Scilab. Perhaps a Scilab expert could look at how to get it compiled > for the latest Scilab? Previous thread about this topic: http://mailinglists.scilab.org/Scilab-users-Getting-netCDF-files-into-Scilab-6-0-1-tp4038278p4038374.html https://atoms.scilab.org/toolboxes/scinetcdf/1.2#comment3102 Regards Samuel From sgougeon at free.fr Fri Feb 12 22:45:53 2021 From: sgougeon at free.fr (Samuel Gougeon) Date: Fri, 12 Feb 2021 22:45:53 +0100 Subject: [Scilab-users] Default x|y|z labels and title font size = 2? In-Reply-To: <49b91a73-cb7d-d640-3131-6558a010433a@gmail.com> References: <454e2c08-0535-9c4e-aa70-ad6860be803b@free.fr> <49b91a73-cb7d-d640-3131-6558a010433a@gmail.com> Message-ID: <788e74a1-8479-42f8-9309-5e0de9e1c8b6@free.fr> Dear all, Thank you for your comments. Le 02/02/2021 ? 17:02, Claus Futtrup a ?crit?: > Hi Samuel > > I agree. The font is always too small. The font = 2 seems to be the > smallest feasible increment and it sounds like a good one (i.e. > without overdoing it). I agree, 2 is a minimal value.? Unless there are more "votes" for 3, let's propose this new default value = 2 for Scilab 6.1.1. Le 02/02/2021 ? 09:39, CRETE Denis a ?crit?: > > .../... I actually defined a function to perform xtitle and > immediately increase font sizes for the axes labels, axis titles and > title of the figure. I originally set them to a size of 2 for the > labels and 3 for the titles. > So do i. But technically speaking, setting a different default value for the title is much harder (to me. I got lost in the code..). As well, detecting when the input is some LaTeX content and then increase the default font size is technically more complicated. Let's start with a simple but urgent improvement. > Still, the reviewers for publications seldom complain about too large > font sizes, much more about too small font sizes! For these > applications, the risk of having to change the font sizes upon > revision of a paper is smaller with default font sizes of 3 for the > labels and 4 (or even 5 when LaTeX style is used) for the titles Right. I am afraid that some "final touch" will anyway most often be required, depending on the Reviewer, the Editor, etc. Le 02/02/2021 ? 17:02, Claus Futtrup a ?crit?: > You mention grid. I always do xgrid(color("grey70")); ... is this > default now, to have the grid a bit greyed? That's something else, to be discussed in another thread. Thanks Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Fri Feb 12 23:49:50 2021 From: sgougeon at free.fr (Samuel Gougeon) Date: Fri, 12 Feb 2021 23:49:50 +0100 Subject: [Scilab-users] Default x|y|z labels and title font size = 2? In-Reply-To: <788e74a1-8479-42f8-9309-5e0de9e1c8b6@free.fr> References: <454e2c08-0535-9c4e-aa70-ad6860be803b@free.fr> <49b91a73-cb7d-d640-3131-6558a010433a@gmail.com> <788e74a1-8479-42f8-9309-5e0de9e1c8b6@free.fr> Message-ID: Le 12/02/2021 ? 22:45, Samuel Gougeon a ?crit?: > Le 02/02/2021 ? 09:39, CRETE Denis a ?crit?: >> >> .../... I actually defined a function to perform xtitle and >> immediately increase font sizes for the axes labels, axis titles and >> title of the figure. I originally set them to a size of 2 for the >> labels and 3 for the titles. >> > So do i. But technically speaking, setting a different default value > for the title is much harder (to me. I got lost in the code..). > Finally, it should be OK for fontsize=2 for xyz labels, and fontsize=3 for the title. Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Sat Feb 13 00:14:07 2021 From: sgougeon at free.fr (Samuel Gougeon) Date: Sat, 13 Feb 2021 00:14:07 +0100 Subject: [Scilab-users] Default grid color = grey? Increase the zoom factor (per wheel step)? Message-ID: <8e7b970e-4c00-8778-fccb-e807cf572581@free.fr> Dear all, *1)* After http://mailinglists.scilab.org/Scilab-users-Default-x-y-z-labels-and-title-font-size-2-tp4041291p4041297.html : Le 02/02/2021 ? 17:02, Claus Futtrup a ?crit?: > .../... > You mention grid. I always do xgrid(color("grey70")); So do i. > ... is this default now, to have the grid a bit greyed? The issue with a non black or white color is that, if the current colormap does not have it, then the color is automatically appended to the colormap. With the current colormap implementation as a figure's property, this may have some side effects for plotting functions like grayplot() whose rendering in "scaled" mode spans the whole colormap, including the appended gray that we do not wish to include in the plot rendering... This is why carefully tuning the default grid style /density/ was required, as discussed in the description of the report #15421 , implemented in Scilab 6.0.2 (so even before 6.1.0). *2)* Too small zoom factor On any graphic, zooming by a factor 2 (in size) requires 11 wheel steps! To me, this is too slow. In another similar software, /each/ wheel step increases the scale by the same factor 2. This is likely too much, but don't you think we could increase a bit the Scilab zoom factor? Hope reading you soon. Regards Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From cfuttrup at gmail.com Sat Feb 13 07:02:17 2021 From: cfuttrup at gmail.com (Claus Futtrup) Date: Sat, 13 Feb 2021 07:02:17 +0100 Subject: [Scilab-users] Default grid color = grey? Increase the zoom factor (per wheel step)? In-Reply-To: <8e7b970e-4c00-8778-fccb-e807cf572581@free.fr> References: <8e7b970e-4c00-8778-fccb-e807cf572581@free.fr> Message-ID: <35bf3968-942b-a861-5b82-dfe4824d912d@gmail.com> Hi Scilabers and Samuel I normally don't have good luck with zoom or rotate functions, so I don't use this feature, but I also rarely am plotting in 3D - and in classic 2D I just continue until I have the right plot size (no need to zoom). P.S. For grid color, it's OK to keep it black and avoid trouble with colormaps. P.P.S. Regarding the size of the plot window (figure.size), it's standard [626,587] and I find it a bit small. Maybe it's a good size if your screen is 1024 x 768 (?), but I think most computers these days are with 1366 x 768 or larger screens (mine is 1920 x 1080 on a 14 inch screen). We should avoid the plot window to be too big for anybody (that would be frustrating), but could the plot be rescaled depending on screen resolution? I find myself typically increasing figure.size by 50%. Best regards, Claus On 13-02-2021 00:14, Samuel Gougeon wrote: > > Dear all, > > *1)* > After > http://mailinglists.scilab.org/Scilab-users-Default-x-y-z-labels-and-title-font-size-2-tp4041291p4041297.html > : > > Le 02/02/2021 ? 17:02, Claus Futtrup a ?crit?: >> .../... >> You mention grid. I always do xgrid(color("grey70")); > > So do i. > >> ... is this default now, to have the grid a bit greyed? > > The issue with a non black or white color is that, if the current > colormap does not have it, then the color is automatically appended to > the colormap. > With the current colormap implementation as a figure's property, this > may have some side effects for plotting functions like grayplot() > whose rendering in "scaled" mode spans the whole colormap, including > the appended gray that we do not wish to include in the plot rendering... > > This is why carefully tuning the default grid style /density/ was > required, as discussed in the description of the report #15421 > , implemented in Scilab 6.0.2 (so > even before 6.1.0). > > > *2)* Too small zoom factor > On any graphic, zooming by a factor 2 (in size) requires 11 wheel steps! > To me, this is too slow. In another similar software, /each/ wheel > step increases the scale by the same factor 2. > This is likely too much, but don't you think we could increase a bit > the Scilab zoom factor? > > Hope reading you soon. > > Regards > Samuel > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From p.muehlmann at gmail.com Sat Feb 13 18:09:15 2021 From: p.muehlmann at gmail.com (P M) Date: Sat, 13 Feb 2021 18:09:15 +0100 Subject: [Scilab-users] Scilab & cdf-file format In-Reply-To: <216626ca-842d-6cb4-fd87-b2876764680f@free.fr> References: <1613141734608-0.post@n3.nabble.com> <216626ca-842d-6cb4-fd87-b2876764680f@free.fr> Message-ID: Dear, thanks for the suggestions. I did install scilab 5.5.2 & the scinetcdf-toolbox. Turns out: The cdf-file at hand is of other format: ncread(inFile, "GMT"); !--error 999 ncread: nc_open() returned the error -51: NetCDF: Unknown file format. BR Philipp Am Fr., 12. Feb. 2021 um 21:26 Uhr schrieb Samuel Gougeon : > Le 12/02/2021 ? 15:55, arctica1963 a ?crit : > > Hello > > > > There is a toolbox for 5.5.2 called scinetcdf which will work - this will > > work with the standard netCDF format. However, it will not work in > version > > 6.x of Scilab. Perhaps a Scilab expert could look at how to get it > compiled > > for the latest Scilab? > Previous thread about this topic: > > http://mailinglists.scilab.org/Scilab-users-Getting-netCDF-files-into-Scilab-6-0-1-tp4038278p4038374.html > https://atoms.scilab.org/toolboxes/scinetcdf/1.2#comment3102 > > Regards > Samuel > > _______________________________________________ > 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 13:09:08 2021 From: sgougeon at free.fr (Samuel Gougeon) Date: Wed, 17 Feb 2021 13:09:08 +0100 Subject: [Scilab-users] xpoly in x-y-z coordinates In-Reply-To: References: Message-ID: Hello Philipp, Le 08/02/2021 ? 21:36, P M a ?crit?: > Dear Users, > > I have a 3D-plot. > > Onto that, I would like to add a xpoly-line with the following specs: > > xpoly ( [0 1], [0 0], [-0.4 -0.4], 'lines' 0) > > in other words: The polyline should be at the X-Y Plane, but shifted > to Z = -0.4 > > I know that I can just plot the line, but that would destroy the > layout, which I would have to reconfigure. What do you mean? That you don't want gca().data_bounds being updated? > > Similary to that I also would like xstring-Text in such a manner. xstring(x, y, text) gce().data(3) = z_coordinate; works. > > Is something like this possible?....xpoly3D() ? Isn't param3d() right for that? Samuel From p.muehlmann at gmail.com Wed Feb 17 21:28:37 2021 From: p.muehlmann at gmail.com (P M) Date: Wed, 17 Feb 2021 21:28:37 +0100 Subject: [Scilab-users] xpoly in x-y-z coordinates In-Reply-To: References: Message-ID: Hi Samuel, please see my answers below in blue. Thank you, Philipp Am Mi., 17. Feb. 2021 um 13:09 Uhr schrieb Samuel Gougeon : > Hello Philipp, > > Le 08/02/2021 ? 21:36, P M a ?crit : > > Dear Users, > > > > I have a 3D-plot. > > > > Onto that, I would like to add a xpoly-line with the following specs: > > > > xpoly ( [0 1], [0 0], [-0.4 -0.4], 'lines' 0) > > > > in other words: The polyline should be at the X-Y Plane, but shifted > > to Z = -0.4 > > > > I know that I can just plot the line, but that would destroy the > > layout, which I would have to reconfigure. > > > *What do you mean? That you don't want gca().data_bounds being updated?* > > Consider a 3D-plot with following settings: - view is rotated other than it's standard view. - box is "off" - axes are "off" - labels are "off" I found that adding afterwards a new line with plot3D8X,Y,Z) would - rotate everything back into standard view - switch box "on" again - switch axes "on" again - switch labels "on" again So I would have to reconfigure the 3D-plot appearance . Using xpoly, xarrow, xsegs allowes to just add a line, while the original plot appearance does not change. This is very comfortable. > > > > Similary to that I also would like xstring-Text in such a manner. > > > *xstring(x, y, text) gce().data(3) = z_coordinate;* > > *works.* > --> Thank you, I was not aware of that. Since xstring has only X-Y as input I didn't check for gce().data(3) > > > > > Is something like this possible?....xpoly3D() ? > > > *Isn't param3d() right for that?* --> Yes, you are right. but still a : gca().data_bounds is necessary afterwards. > > Samuel > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 99andrei at mail.ru Thu Feb 18 10:59:40 2021 From: 99andrei at mail.ru (=?UTF-8?B?QW5kcmVpIExvbW92?=) Date: Thu, 18 Feb 2021 12:59:40 +0300 Subject: [Scilab-users] =?utf-8?q?Scilab_5=2E5=2E2_in_Debian_10_-_segmenta?= =?utf-8?q?tion_fault?= Message-ID: <1613642380.494905850@f547.i.mail.ru> Hi All, In order to use Scilab? parallel_run in Debian 10 (x86_64), i download https://www.scilab.org/download/5.5.2/scilab-5.5.2.bin.linux-x86_64.tar.gz unpack it to ~/foo/scilab-5.5.2 then cd ~/foo/scilab-5.5.2/bin and run ? ? $./scilab ? Segmentation fault :(( ? ? What am I doing wrong ... ? -- WBR, Andrei ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jean-Yves.Baudais at insa-rennes.fr Thu Feb 18 15:19:55 2021 From: Jean-Yves.Baudais at insa-rennes.fr (Jean-Yves Baudais) Date: Thu, 18 Feb 2021 15:19:55 +0100 (CET) Subject: [Scilab-users] Scilab 5.5.2 in Debian 10 - segmentation fault In-Reply-To: <1613642380.494905850@f547.i.mail.ru> References: <1613642380.494905850@f547.i.mail.ru> Message-ID: <2122781931.223239.1613657995620.JavaMail.zimbra@insa-rennes.fr> Hi, > From: "Andrei Lomov" <99andrei at mail.ru> > https://www.scilab.org/download/5.5.2/scilab-5.5.2.bin.linux-x86_64.tar.gz > $./scilab > Segmentation fault I faced segfault problem with really basic matrix use in Scilab 5.3 and I guessed mismatch somewhere (Scilab, Java, OS?) in multicore system, but I was not able to investigate more. My solution was to use scilab 6.1... It works now with complex matrix use. --Jean-Yves From antoine.monmayrant at laas.fr Thu Feb 18 15:23:09 2021 From: antoine.monmayrant at laas.fr (Antoine Monmayrant) Date: Thu, 18 Feb 2021 15:23:09 +0100 Subject: [Scilab-users] Scilab 5.5.2 in Debian 10 - segmentation fault In-Reply-To: <1613642380.494905850@f547.i.mail.ru> References: <1613642380.494905850@f547.i.mail.ru> Message-ID: Hello Andrei, I think this is a dead end. As far as I remember, parallel_run only works on Windows, on 1 core and is an ugly hack. From https://help.scilab.org/doc/5.5.2/en_US/parallel_run.html : "In this current version of Scilab, |parallel_run| uses only one core on Windows platforms." Can you tell us a bit more about what you try to do? Cheers, Antoine On 18/02/2021 10:59, Andrei Lomov wrote: > Hi All, > In order to use Scilab? parallel_run in Debian 10 (x86_64), > i download > https://www.scilab.org/download/5.5.2/scilab-5.5.2.bin.linux-x86_64.tar.gz > unpack it to > ~/foo/scilab-5.5.2 > then > cd ~/foo/scilab-5.5.2/bin > and run ? > $./scilab > Segmentation fault > :(( > ? What am I doing wrong ... > -- > WBR, > Andrei > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jean-Yves.Baudais at insa-rennes.fr Thu Feb 18 15:27:46 2021 From: Jean-Yves.Baudais at insa-rennes.fr (Jean-Yves Baudais) Date: Thu, 18 Feb 2021 15:27:46 +0100 (CET) Subject: [Scilab-users] End of stack! Message-ID: <235958687.223883.1613658466434.JavaMail.zimbra@insa-rennes.fr> Hi, > for i=1:10 mprintf("%d \r",i); end 1 2 3 4 5 6 7 8 9 10 It's not really what I expected. So I tested > for i=1:10 mprintf("\r %i",i); end and Scilab-6.1.0 crashes with a shell message "terminate called after throwing an instance of 'GiwsException::JniCallMethodException' [...] End of stack" Is it a bug? -- Jean-Yves From fmiyara at fceia.unr.edu.ar Thu Feb 18 19:34:39 2021 From: fmiyara at fceia.unr.edu.ar (Federico Miyara) Date: Thu, 18 Feb 2021 15:34:39 -0300 Subject: [Scilab-users] convert vector to list Message-ID: <74b8f5a5-693c-86be-0045-293bf5393f4c@fceia.unr.edu.ar> Dear All, Is there a Scilab function to convert a vector to a list? If x is a vector, this code L = list(); for n=1:length(x) ??? L(n) = x(n); end seems to work, but it would be nice to have a primitive doing this more efficiently. I don't seem to be able to find it. Regards, Federico Miyara -- El software de antivirus Avast ha analizado este correo electr?nico en busca de virus. https://www.avast.com/antivirus -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephane.mottelet at utc.fr Thu Feb 18 19:37:39 2021 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Thu, 18 Feb 2021 19:37:39 +0100 Subject: [Scilab-users] convert vector to list In-Reply-To: <74b8f5a5-693c-86be-0045-293bf5393f4c@fceia.unr.edu.ar> References: <74b8f5a5-693c-86be-0045-293bf5393f4c@fceia.unr.edu.ar> Message-ID: <5306da34-0df1-88da-eaac-3cb1e8b6a68a@utc.fr> vec2list() ? Le 18/02/2021 ? 19:34, Federico Miyara a ?crit?: > > Dear All, > > Is there a Scilab function to convert a vector to a list? > > If x is a vector, this code > > L = list(); > for n=1:length(x) > ??? L(n) = x(n); > end > > seems to work, but it would be nice to have a primitive doing this > more efficiently. I don't seem to be able to find it. > > Regards, > > Federico Miyara > > > Libre de virus. www.avast.com > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > _______________________________________________ > users mailing list > users at lists.scilab.org > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users -- St?phane Mottelet Ing?nieur de recherche EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable D?partement G?nie des Proc?d?s Industriels Sorbonne Universit?s - Universit? de Technologie de Compi?gne CS 60319, 60203 Compi?gne cedex Tel : +33(0)344234688 http://www.utc.fr/~mottelet -------------- next part -------------- An HTML attachment was scrubbed... URL: From cfuttrup at gmail.com Thu Feb 18 19:48:18 2021 From: cfuttrup at gmail.com (Claus Futtrup) Date: Thu, 18 Feb 2021 19:48:18 +0100 Subject: [Scilab-users] convert vector to list In-Reply-To: <5306da34-0df1-88da-eaac-3cb1e8b6a68a@utc.fr> References: <74b8f5a5-693c-86be-0045-293bf5393f4c@fceia.unr.edu.ar> <5306da34-0df1-88da-eaac-3cb1e8b6a68a@utc.fr> Message-ID: <6ed7433d-9b76-8d4d-44b4-8b624f14feef@gmail.com> He he Sometimes the answer is so 'obvious' ... it's just that the user never heard about it before. Myself included. /Claus On 18-02-2021 19:37, St?phane Mottelet wrote: > > vec2list() ? > > Le 18/02/2021 ? 19:34, Federico Miyara a ?crit?: >> >> Dear All, >> >> Is there a Scilab function to convert a vector to a list? >> >> If x is a vector, this code >> >> L = list(); >> for n=1:length(x) >> ??? L(n) = x(n); >> end >> >> seems to work, but it would be nice to have a primitive doing this >> more efficiently. I don't seem to be able to find it. >> >> Regards, >> >> Federico Miyara >> >> >> Libre de virus. www.avast.com >> >> >> >> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >> >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users > -- > St?phane Mottelet > Ing?nieur de recherche > EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable > D?partement G?nie des Proc?d?s Industriels > Sorbonne Universit?s - Universit? de Technologie de Compi?gne > CS 60319, 60203 Compi?gne cedex > Tel : +33(0)344234688 > http://www.utc.fr/~mottelet > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From parravicini.anna at gmail.com Fri Feb 19 09:25:01 2021 From: parravicini.anna at gmail.com (anna28) Date: Fri, 19 Feb 2021 01:25:01 -0700 (MST) Subject: [Scilab-users] plot(x) - define color Message-ID: <1613723101816-0.post@n3.nabble.com> Hi all, I would need a help to improve my plot. I must graph the trend of 20 variables with the function plot(x); I would like to assign a different color/mark to each variable in order to make graph understanding immedaite. At the moment, I do like that and it works: colour=['.r-','.g-','.k-','.b-','.m-','.r:','.g:','.k:','.b:','.m:','.r--','.g--','.k--','.b--','.m--','.r-.','.g-.','.k-.','.b-.','.m-.']; for j=1:20 plot(TestPH(j,:),colour(j)); end but the plot is not very clear. I would like to add different color and to reduce line styles, that are difficult to recognize in the plot. Is there any way to add colors in the "coulour" array? (I cannot use white, yellow and cyan because difficult to see with white background). thanks! Anna -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From Jean-Yves.Baudais at insa-rennes.fr Fri Feb 19 10:37:17 2021 From: Jean-Yves.Baudais at insa-rennes.fr (Jean-Yves Baudais) Date: Fri, 19 Feb 2021 10:37:17 +0100 (CET) Subject: [Scilab-users] plot(x) - define color In-Reply-To: <1613723101816-0.post@n3.nabble.com> References: <1613723101816-0.post@n3.nabble.com> Message-ID: <537605742.290572.1613727437757.JavaMail.zimbra@insa-rennes.fr> Hi, > colour=['.r-','.g-','.k-','.b-','.m-','.r:','.g:','.k:','.b:','.m:','.r--','.g--','.k--','.b--','.m--','.r-.','.g-.','.k-.','.b-.','.m-.']; > for j=1:20 > plot(TestPH(j,:),colour(j)); > end > > but the plot is not very clear. I would like to add different color and to > reduce line styles, that are difficult to recognize in the plot. I don't if there is a dedicated function, but colour=["red","blue","chocolate1",...]; // help color_list for j=1:20 plot(TestPH(j,:)) gcf().children.children.children(1).foreground=color(colour(j)); end gives a solution. --Jean-Yves From stephane.mottelet at utc.fr Fri Feb 19 10:53:20 2021 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Fri, 19 Feb 2021 10:53:20 +0100 Subject: [Scilab-users] plot(x) - define color In-Reply-To: <537605742.290572.1613727437757.JavaMail.zimbra@insa-rennes.fr> References: <1613723101816-0.post@n3.nabble.com> <537605742.290572.1613727437757.JavaMail.zimbra@insa-rennes.fr> Message-ID: <77b2301c-875f-9cdb-a50c-ece5bc65c434@utc.fr> Hi, Since 6.1 version, plot() yields the handles of created polyline entities, allowing to improve the piece of code which has been proposed, like this: colour=["red","blue","chocolate1",...]; // help color_list for j=1:20 ? h = plot(TestPH(j,:)) ? h.foreground=color(colour(j)); end S. Le 19/02/2021 ? 10:37, Jean-Yves Baudais a ?crit?: > Hi, > > >> colour=['.r-','.g-','.k-','.b-','.m-','.r:','.g:','.k:','.b:','.m:','.r--','.g--','.k--','.b--','.m--','.r-.','.g-.','.k-.','.b-.','.m-.']; >> for j=1:20 >> plot(TestPH(j,:),colour(j)); >> end >> >> but the plot is not very clear. I would like to add different color and to >> reduce line styles, that are difficult to recognize in the plot. > > I don't if there is a dedicated function, but > > colour=["red","blue","chocolate1",...]; // help color_list > for j=1:20 > plot(TestPH(j,:)) > gcf().children.children.children(1).foreground=color(colour(j)); > end > > gives a solution. > > --Jean-Yves > _______________________________________________ > users mailing list > users at lists.scilab.org > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users -- St?phane Mottelet Ing?nieur de recherche EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable D?partement G?nie des Proc?d?s Industriels Sorbonne Universit?s - Universit? de Technologie de Compi?gne CS 60319, 60203 Compi?gne cedex Tel : +33(0)344234688 http://www.utc.fr/~mottelet From p.muehlmann at gmail.com Fri Feb 19 15:16:15 2021 From: p.muehlmann at gmail.com (P M) Date: Fri, 19 Feb 2021 15:16:15 +0100 Subject: [Scilab-users] plot(x) - define color In-Reply-To: <77b2301c-875f-9cdb-a50c-ece5bc65c434@utc.fr> References: <1613723101816-0.post@n3.nabble.com> <537605742.290572.1613727437757.JavaMail.zimbra@insa-rennes.fr> <77b2301c-875f-9cdb-a50c-ece5bc65c434@utc.fr> Message-ID: ..because the question also mentions the line style: in addition to: colour=["red","blue","chocolate1",...]; // help color_list you can also create lineStyle = [ 1, 2, 3, 4, 2, 1 , ......] // help polyline and do: for j=1:20 h = plot(TestPH(j,:)) h.foreground=color(colour(j)); h.line_style = lineStyle(j) end BR Philipp Am Fr., 19. Feb. 2021 um 10:53 Uhr schrieb St?phane Mottelet < stephane.mottelet at utc.fr>: > Hi, > > Since 6.1 version, plot() yields the handles of created polyline > entities, allowing to improve the piece of code which has been proposed, > like this: > > colour=["red","blue","chocolate1",...]; // help color_list > for j=1:20 > h = plot(TestPH(j,:)) > h.foreground=color(colour(j)); > end > > S. > > Le 19/02/2021 ? 10:37, Jean-Yves Baudais a ?crit : > > Hi, > > > > > >> > colour=['.r-','.g-','.k-','.b-','.m-','.r:','.g:','.k:','.b:','.m:','.r--','.g--','.k--','.b--','.m--','.r-.','.g-.','.k-.','.b-.','.m-.']; > >> for j=1:20 > >> plot(TestPH(j,:),colour(j)); > >> end > >> > >> but the plot is not very clear. I would like to add different color and > to > >> reduce line styles, that are difficult to recognize in the plot. > > > > I don't if there is a dedicated function, but > > > > colour=["red","blue","chocolate1",...]; // help color_list > > for j=1:20 > > plot(TestPH(j,:)) > > gcf().children.children.children(1).foreground=color(colour(j)); > > end > > > > gives a solution. > > > > --Jean-Yves > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users > > -- > St?phane Mottelet > Ing?nieur de recherche > EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable > D?partement G?nie des Proc?d?s Industriels > Sorbonne Universit?s - Universit? de Technologie de Compi?gne > CS 60319, 60203 Compi?gne cedex > Tel : +33(0)344234688 > http://www.utc.fr/~mottelet > > _______________________________________________ > 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 Fri Feb 19 16:50:31 2021 From: sgougeon at free.fr (Samuel Gougeon) Date: Fri, 19 Feb 2021 16:50:31 +0100 Subject: [Scilab-users] plot(x) - define color In-Reply-To: <1613723101816-0.post@n3.nabble.com> References: <1613723101816-0.post@n3.nabble.com> Message-ID: <2cd372e3-438b-bca0-e230-1c9ff906206a@free.fr> Le 19/02/2021 ? 09:25, anna28 a ?crit?: > Hi all, > > I would need a help to improve my plot. > I must graph the trend of 20 variables with the function plot(x); I would > like to assign a different color/mark to each variable in order to make > graph understanding immedaite. > > At the moment, I do like that and it works: > > colour=['.r-','.g-','.k-','.b-','.m-','.r:','.g:','.k:','.b:','.m:','.r--','.g--','.k--','.b--','.m--','.r-.','.g-.','.k-.','.b-.','.m-.']; > for j=1:20 > plot(TestPH(j,:),colour(j)); > end > > but the plot is not very clear. I would like to add different color and to > reduce line styles, that are difficult to recognize in the plot. > > Is there any way to add colors in the "coulour" array? (I cannot use white, > yellow and cyan because difficult to see with white background). > > thanks! > Anna > Example of plot() post-processing "vectorized" over curves: x = linspace(0,10,100); phases = 0:0.15:1.5; [X,P] = ndgrid(x, phases); h = plot(x, sin(X+P)); // No explicit loop over curves is required: h.foreground = 10:2:30; // indexed colors // check for some curves h(1).foreground h(10).foreground // Until color() is vectorized, we could also use named colors as in colors = ["blue" "scilabcyan4" "pink" "orange" "red" "green" "magenta" "gray50" "slateblue" "peru" "sienna"]; // named colors =>help color_list h.foreground = addcolor(name2rgb(colors)/255); Actually using named colors in linespec out of the 8 special ones could be useful, since Scilab's set of named colored is quite rich. Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Fri Feb 19 16:50:57 2021 From: sgougeon at free.fr (Samuel Gougeon) Date: Fri, 19 Feb 2021 16:50:57 +0100 Subject: [Scilab-users] End of stack! In-Reply-To: <235958687.223883.1613658466434.JavaMail.zimbra@insa-rennes.fr> References: <235958687.223883.1613658466434.JavaMail.zimbra@insa-rennes.fr> Message-ID: <4fe2ca06-420a-a73d-0efc-2d1bd4f1d406@free.fr> Le 18/02/2021 ? 15:27, Jean-Yves Baudais a ?crit?: > Hi, > >> for i=1:10 mprintf("%d \r",i); end > 1 2 3 4 5 6 7 8 9 10 > > It's not really what I expected. So I tested > >> for i=1:10 mprintf("\r %i",i); end > and Scilab-6.1.0 crashes with a shell message > > "terminate called after throwing an instance of 'GiwsException::JniCallMethodException' > [...] > End of stack" > > Is it a bug? > Yes it was. It isalready fixed for Scilab 6.1.1. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Fri Feb 19 16:53:04 2021 From: sgougeon at free.fr (Samuel Gougeon) Date: Fri, 19 Feb 2021 16:53:04 +0100 Subject: [Scilab-users] convert vector to list In-Reply-To: <74b8f5a5-693c-86be-0045-293bf5393f4c@fceia.unr.edu.ar> References: <74b8f5a5-693c-86be-0045-293bf5393f4c@fceia.unr.edu.ar> Message-ID: <2ea0470d-2d41-7a3f-de19-022147ac34ac@free.fr> Le 18/02/2021 ? 19:34, Federico Miyara a ?crit?: > > Dear All, > > Is there a Scilab function to convert a vector to a list? > > If x is a vector, this code > > L = list(); > for n=1:length(x) > ??? L(n) = x(n); > end > > seems to work, but it would be nice to have a primitive doing this > more efficiently. I don't seem to be able to find it. vec2list()? is a macro instead of a built-in, but it aims to do the job: --> n = 3; --> v = rand(1,n) ?v? = ?? 0.2113249?? 0.7560439?? 0.0002211 --> vec2list(v,ones(n,2)) ?ans? = ??? (1) = 0.2113249 ????? (2) = 0.7560439 ????? (3) = 0.0002211 https://help.scilab.org/docs/6.1.0/en_US/vec2list.html Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From fmiyara at fceia.unr.edu.ar Sat Feb 20 01:29:05 2021 From: fmiyara at fceia.unr.edu.ar (Federico Miyara) Date: Fri, 19 Feb 2021 21:29:05 -0300 Subject: [Scilab-users] Some details on the documentation of log(), log10(), etc. Message-ID: <3a72f7ad-e0ad-0ae9-a4a2-cc0d4189c382@fceia.unr.edu.ar> Dear all, In an old script where I needed to apply log10 to an hyperarray I had implemented it as log(A)/log(10) with a comment indicating that in that version log10() didn't work for hyperarrays (unfortunately I don't recall what version it was). In Version 6.1.0 it does work for hyperarrays, but the documentation still says that it applies to vectors or matrices: https://help.scilab.org/docs/6.1.0/en_US/log10.html In some contexts "matrix" may be interpreted as an hyperarray or hypermatrix (for instance when speaking of N-D matrices), but for Scilab a matrix is formally a two-dimensional array: https://help.scilab.org/docs/6.1.0/en_US/matrices.html I think the documentation should indicate that it applies to vectors, matrices and hypermatrices Another problem is regarding log(). It says that the input argument is a "constant vector or constant matrix": https://help.scilab.org/docs/6.1.0/en_US/log.html However, it seems that "constant" has a specific meaning in Scilab as a predefined variable: https://help.scilab.org/docs/6.1.0/en_US/section_421ab29126e21a1e1e403ee27a18fda4.html As it is worded, it seems that log() is applied to predefined variables. I think it should refer more clearly to the type double (it doesn't work, for instance, for integer types such as int16(2)). In the case of log2() the description of arguments is even stranger: https://help.scilab.org/docs/6.1.0/en_US/log2.html It confuses the argument section with the description, and it specifies decimal numbers which isn't a recognized type. The function exp(), on the other hand, doesn't indicate an output argument. I think these functions are very similar and their documentation pages should be consistent with one another Regards, Federico Miyara -- El software de antivirus Avast ha analizado este correo electr?nico en busca de virus. https://www.avast.com/antivirus -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephane.mottelet at utc.fr Sat Feb 20 17:21:41 2021 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Sat, 20 Feb 2021 17:21:41 +0100 Subject: [Scilab-users] Some details on the documentation of log(), log10(), etc. In-Reply-To: <3a72f7ad-e0ad-0ae9-a4a2-cc0d4189c382@fceia.unr.edu.ar> References: <3a72f7ad-e0ad-0ae9-a4a2-cc0d4189c382@fceia.unr.edu.ar> Message-ID: <2b315ede-b290-133b-27b5-32560225c430@utc.fr> Hi Frederico, In almost all other numerical software the object defined in Scilab by a=zeros(3,3,3) is called an "array", m=zeros(3,3) a "matrix" and x=zeros(1,3) or y=zeros(3,1) "vectors", and all of them are called "arrays". BTW, now the "hyper" prefix sounds like when it is used in "hyperspace"... To me, the documentation should be revamped to always use "array" when the denoted object can have any number of dimensions and use "matrix" only when the array has to be a matrix. Concerning your remark about the "constant vector or constant matrix", yes, this should be changed by something more explicit, like "array of double". We already use similar terms in error messages, i.e. "%s: Wrong type for input argument #%d: A matrix of double expected.\n" Hence we could synchonize the uses of localized messages with the documentation. When I say "we" it also includes "you", Frederico. If you feel that Scilab could be improved by a better documentation, please contribute. If you need some help to start using the relevant tools (git, codereview) I would be glad to help you. S. Le 20/02/2021 ? 01:29, Federico Miyara a ?crit?: > > Dear all, > > In an old script where I needed to apply log10 to an hyperarray I had > implemented it as log(A)/log(10) with a comment indicating that in > that version log10() didn't work for hyperarrays (unfortunately I > don't recall what version it was). > > In Version 6.1.0 it does work for hyperarrays, but the documentation > still says that it applies to vectors or matrices: > > https://help.scilab.org/docs/6.1.0/en_US/log10.html > > In some contexts "matrix" may be interpreted as an hyperarray or > hypermatrix (for instance when speaking of N-D matrices), but for > Scilab a matrix is formally a two-dimensional array: > > https://help.scilab.org/docs/6.1.0/en_US/matrices.html > > I think the documentation should indicate that it applies to vectors, > matrices and hypermatrices > > Another problem is regarding log(). It says that the input argument is > a "constant vector or constant matrix": > > https://help.scilab.org/docs/6.1.0/en_US/log.html > > However, it seems that "constant" has a specific meaning in Scilab as > a predefined variable: > > https://help.scilab.org/docs/6.1.0/en_US/section_421ab29126e21a1e1e403ee27a18fda4.html > > As it is worded, it seems that log() is applied to predefined > variables. I think it should refer more clearly to the type double (it > doesn't work, for instance, for integer types such as int16(2)). > > In the case of log2() the description of arguments is even stranger: > > https://help.scilab.org/docs/6.1.0/en_US/log2.html > > It confuses the argument section with the description, and it > specifies decimal numbers which isn't a recognized type. > > The function exp(), on the other hand, doesn't indicate an output > argument. > > I think these functions are very similar and their documentation pages > should be consistent with one another > > Regards, > > Federico Miyara > > > Libre de virus. www.avast.com > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > _______________________________________________ > users mailing list > users at lists.scilab.org > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users -- St?phane Mottelet Ing?nieur de recherche EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable D?partement G?nie des Proc?d?s Industriels Sorbonne Universit?s - Universit? de Technologie de Compi?gne CS 60319, 60203 Compi?gne cedex Tel : +33(0)344234688 http://www.utc.fr/~mottelet -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephane.mottelet at utc.fr Sat Feb 20 17:34:36 2021 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Sat, 20 Feb 2021 17:34:36 +0100 Subject: [Scilab-users] Some details on the documentation of log(), log10(), etc. In-Reply-To: <2b315ede-b290-133b-27b5-32560225c430@utc.fr> References: <3a72f7ad-e0ad-0ae9-a4a2-cc0d4189c382@fceia.unr.edu.ar> <2b315ede-b290-133b-27b5-32560225c430@utc.fr> Message-ID: <10a85e38-ac2f-6e7a-a354-63085b081650@utc.fr> By looking into the documentation messages I realized that we already use "array" : ./locale/de_DE/LC_MESSAGES/scilab.po-e:msgid "%s: Wrong type for input argument #%d: Array of double expected.\n" S. Le 20/02/2021 ? 17:21, St?phane Mottelet a ?crit?: > > Hi Frederico, > > In almost all other numerical software the object defined in Scilab by > a=zeros(3,3,3) is called an "array", m=zeros(3,3) a "matrix" and > x=zeros(1,3) or y=zeros(3,1) "vectors", and all of them are called > "arrays". BTW, now the "hyper" prefix sounds like when it is used in > "hyperspace"... To me, the documentation should be revamped to always > use "array" when the denoted object can have any number of dimensions > and use "matrix" only when the array has to be a matrix. Concerning > your remark about the "constant vector or constant matrix", yes, this > should be changed by something more explicit, like "array of double". > We already use similar terms in error messages, i.e. > > "%s: Wrong type for input argument #%d: A matrix of double expected.\n" > > Hence we could synchonize the uses of localized messages with the > documentation. When I say "we" it also includes "you", Frederico. If > you feel that Scilab could be improved by a better documentation, > please contribute. If you need some help to start using the relevant > tools (git, codereview) I would be glad to help you. > > S. > > Le 20/02/2021 ? 01:29, Federico Miyara a ?crit?: >> >> Dear all, >> >> In an old script where I needed to apply log10 to an hyperarray I had >> implemented it as log(A)/log(10) with a comment indicating that in >> that version log10() didn't work for hyperarrays (unfortunately I >> don't recall what version it was). >> >> In Version 6.1.0 it does work for hyperarrays, but the documentation >> still says that it applies to vectors or matrices: >> >> https://help.scilab.org/docs/6.1.0/en_US/log10.html >> >> In some contexts "matrix" may be interpreted as an hyperarray or >> hypermatrix (for instance when speaking of N-D matrices), but for >> Scilab a matrix is formally a two-dimensional array: >> >> https://help.scilab.org/docs/6.1.0/en_US/matrices.html >> >> I think the documentation should indicate that it applies to vectors, >> matrices and hypermatrices >> >> Another problem is regarding log(). It says that the input argument >> is a "constant vector or constant matrix": >> >> https://help.scilab.org/docs/6.1.0/en_US/log.html >> >> However, it seems that "constant" has a specific meaning in Scilab as >> a predefined variable: >> >> https://help.scilab.org/docs/6.1.0/en_US/section_421ab29126e21a1e1e403ee27a18fda4.html >> >> As it is worded, it seems that log() is applied to predefined >> variables. I think it should refer more clearly to the type double >> (it doesn't work, for instance, for integer types such as int16(2)). >> >> In the case of log2() the description of arguments is even stranger: >> >> https://help.scilab.org/docs/6.1.0/en_US/log2.html >> >> It confuses the argument section with the description, and it >> specifies decimal numbers which isn't a recognized type. >> >> The function exp(), on the other hand, doesn't indicate an output >> argument. >> >> I think these functions are very similar and their documentation >> pages should be consistent with one another >> >> Regards, >> >> Federico Miyara >> >> >> Libre de virus. www.avast.com >> >> >> >> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >> >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users > -- > St?phane Mottelet > Ing?nieur de recherche > EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable > D?partement G?nie des Proc?d?s Industriels > Sorbonne Universit?s - Universit? de Technologie de Compi?gne > CS 60319, 60203 Compi?gne cedex > Tel : +33(0)344234688 > http://www.utc.fr/~mottelet > > _______________________________________________ > users mailing list > users at lists.scilab.org > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users -- St?phane Mottelet Ing?nieur de recherche EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable D?partement G?nie des Proc?d?s Industriels Sorbonne Universit?s - Universit? de Technologie de Compi?gne CS 60319, 60203 Compi?gne cedex Tel : +33(0)344234688 http://www.utc.fr/~mottelet -------------- next part -------------- An HTML attachment was scrubbed... URL: From Clement.David at esi-group.com Mon Feb 22 09:43:55 2021 From: Clement.David at esi-group.com (=?utf-8?B?Q2zDqW1lbnQgRGF2aWQ=?=) Date: Mon, 22 Feb 2021 08:43:55 +0000 Subject: [Scilab-users] Some details on the documentation of log(), log10(), etc. In-Reply-To: <10a85e38-ac2f-6e7a-a354-63085b081650@utc.fr> References: <3a72f7ad-e0ad-0ae9-a4a2-cc0d4189c382@fceia.unr.edu.ar> <2b315ede-b290-133b-27b5-32560225c430@utc.fr> <10a85e38-ac2f-6e7a-a354-63085b081650@utc.fr> Message-ID: Hello all, Thanks for opening the discussion on this ?new user?-related topic, this is always good to improve our help for existing user and new comers ; to let them havie a clear understanding of Scilab-lingua. One important point to me is to have a proper distinction between ?array? (as values organized in multiple dimensions) and more precise terms with more constraints on dimensions ?horizontal vector?, ?matrix?, etc? For keeping the rationale up to date, I suggest you to edit the Localization wiki page [1]. In term of code update, I can help you finding duplicated messages but keep in mind that the build-system create .pot files from the source code. To look for duplicate, the more important is to upgrade the source code. [1]: https://wiki.scilab.org/Localization in English - Standard messages Note: AFAK the ?constant? term has been removed on 6.0.0 documentation/error message as this is the default datatype, in case of advanced type management the term ?decimal? can be used instead. Regards, Cl?ment From: users On Behalf Of St?phane Mottelet Sent: Saturday, February 20, 2021 5:35 PM To: users at lists.scilab.org Subject: Re: [Scilab-users] Some details on the documentation of log(), log10(), etc. By looking into the documentation messages I realized that we already use "array" : ./locale/de_DE/LC_MESSAGES/scilab.po-e:msgid "%s: Wrong type for input argument #%d: Array of double expected.\n" S. Le 20/02/2021 ? 17:21, St?phane Mottelet a ?crit : Hi Frederico, In almost all other numerical software the object defined in Scilab by a=zeros(3,3,3) is called an "array", m=zeros(3,3) a "matrix" and x=zeros(1,3) or y=zeros(3,1) "vectors", and all of them are called "arrays". BTW, now the "hyper" prefix sounds like when it is used in "hyperspace"... To me, the documentation should be revamped to always use "array" when the denoted object can have any number of dimensions and use "matrix" only when the array has to be a matrix. Concerning your remark about the "constant vector or constant matrix", yes, this should be changed by something more explicit, like "array of double". We already use similar terms in error messages, i.e. "%s: Wrong type for input argument #%d: A matrix of double expected.\n" Hence we could synchonize the uses of localized messages with the documentation. When I say "we" it also includes "you", Frederico. If you feel that Scilab could be improved by a better documentation, please contribute. If you need some help to start using the relevant tools (git, codereview) I would be glad to help you. S. Le 20/02/2021 ? 01:29, Federico Miyara a ?crit : Dear all, In an old script where I needed to apply log10 to an hyperarray I had implemented it as log(A)/log(10) with a comment indicating that in that version log10() didn't work for hyperarrays (unfortunately I don't recall what version it was). In Version 6.1.0 it does work for hyperarrays, but the documentation still says that it applies to vectors or matrices: https://help.scilab.org/docs/6.1.0/en_US/log10.html In some contexts "matrix" may be interpreted as an hyperarray or hypermatrix (for instance when speaking of N-D matrices), but for Scilab a matrix is formally a two-dimensional array: https://help.scilab.org/docs/6.1.0/en_US/matrices.html I think the documentation should indicate that it applies to vectors, matrices and hypermatrices Another problem is regarding log(). It says that the input argument is a "constant vector or constant matrix": https://help.scilab.org/docs/6.1.0/en_US/log.html However, it seems that "constant" has a specific meaning in Scilab as a predefined variable: https://help.scilab.org/docs/6.1.0/en_US/section_421ab29126e21a1e1e403ee27a18fda4.html As it is worded, it seems that log() is applied to predefined variables. I think it should refer more clearly to the type double (it doesn't work, for instance, for integer types such as int16(2)). In the case of log2() the description of arguments is even stranger: https://help.scilab.org/docs/6.1.0/en_US/log2.html It confuses the argument section with the description, and it specifies decimal numbers which isn't a recognized type. The function exp(), on the other hand, doesn't indicate an output argument. I think these functions are very similar and their documentation pages should be consistent with one another Regards, Federico Miyara [Image removed by sender.] Libre de virus. www.avast.com _______________________________________________ users mailing list users at lists.scilab.org https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users -- St?phane Mottelet Ing?nieur de recherche EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable D?partement G?nie des Proc?d?s Industriels Sorbonne Universit?s - Universit? de Technologie de Compi?gne CS 60319, 60203 Compi?gne cedex Tel : +33(0)344234688 http://www.utc.fr/~mottelet _______________________________________________ users mailing list users at lists.scilab.org https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users -- St?phane Mottelet Ing?nieur de recherche EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable D?partement G?nie des Proc?d?s Industriels Sorbonne Universit?s - Universit? de Technologie de Compi?gne CS 60319, 60203 Compi?gne cedex Tel : +33(0)344234688 http://www.utc.fr/~mottelet -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 350 bytes Desc: image001.jpg URL: From stephane.mottelet at utc.fr Mon Feb 22 10:12:23 2021 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Mon, 22 Feb 2021 10:12:23 +0100 Subject: [Scilab-users] Some details on the documentation of log(), log10(), etc. In-Reply-To: References: <3a72f7ad-e0ad-0ae9-a4a2-cc0d4189c382@fceia.unr.edu.ar> <2b315ede-b290-133b-27b5-32560225c430@utc.fr> <10a85e38-ac2f-6e7a-a354-63085b081650@utc.fr> Message-ID: Hi, Le 22/02/2021 ? 09:43, Cl?ment David a ?crit?: > > Hello all, > > Thanks for opening the discussion on this ?new user?-related topic, > this is always good to improve our help for existing user and new > comers ; to let them havie a clear understanding of Scilab-lingua. > > One important point to me is to have a proper distinction between > ?array? (as values organized in multiple dimensions) and more precise > terms with more constraints on dimensions ?horizontal vector?, > ?matrix?, etc? For keeping the rationale up to date, I suggest you to > edit the Localization wiki page [1]. > > In term of code update, I can help you finding duplicated messages but > keep in mind that the build-system create .pot files from the source > code. To look for duplicate, the more important is to upgrade the > source code. > > [1]: https://wiki.scilab.org/Localization in English - Standard messages > > Note: AFAK the ?constant? term has been removed on 6.0.0 > documentation/error message as this is the default datatype, in case > of advanced type management the term ?decimal? can be used instead. > I think that the "decimal" term has to be discussed. In no way the default number type in Scilab is decimal (https://en.wikipedia.org/wiki/Decimal). Scilab actually displays rounded decimal approximations but internally they are IEEE754 double-precision floating point numbers. I think that the "floating point numbers" instead of "decimal" would be more suitable as is does not make any mention of the basis. As far as I am concerned, I don't have any problem with "array of floating point numbers" In some contexts, typically when describing the type of arguments in the documentation of functions, we could be more precise by making reference to the actual internal object type, i.e. "double" or "Double", i.e. array of type double array of double Scilab users are mature enough to accept a bit of technical (but precise) terms. But this is my personal opinion... S. > Regards, > > Cl?ment > > *From:* users *On Behalf Of *St?phane > Mottelet > *Sent:* Saturday, February 20, 2021 5:35 PM > *To:* users at lists.scilab.org > *Subject:* Re: [Scilab-users] Some details on the documentation of > log(), log10(), etc. > > By looking into the documentation messages I realized that we already > use "array" : > > ./locale/de_DE/LC_MESSAGES/scilab.po-e:msgid "%s: Wrong type for input > argument #%d: Array of double expected.\n" > > S. > > Le 20/02/2021 ? 17:21, St?phane Mottelet a ?crit?: > > Hi Frederico, > > In almost all other numerical software the object defined in > Scilab by a=zeros(3,3,3) is called an "array", m=zeros(3,3) a > "matrix" and x=zeros(1,3) or y=zeros(3,1) "vectors", and all of > them are called "arrays". BTW, now the "hyper" prefix sounds like > when it is used in "hyperspace"... To me, the documentation should > be revamped to always use "array" when the denoted object can have > any number of dimensions and use "matrix" only when the array has > to be a matrix. Concerning your remark about the "constant vector > or constant matrix", yes, this should be changed by something more > explicit, like "array of double". We already use similar terms in > error messages, i.e. > > "%s: Wrong type for input argument #%d: A matrix of double > expected.\n" > > Hence we could synchonize the uses of localized messages with the > documentation. When I say "we" it also includes "you", Frederico. > If you feel that Scilab could be improved by a better > documentation, please contribute. If you need some help to start > using the relevant tools (git, codereview) I would be glad to help > you. > > S. > > Le 20/02/2021 ? 01:29, Federico Miyara a ?crit?: > > > Dear all, > > In an old script where I needed to apply log10 to an > hyperarray I had implemented it as log(A)/log(10) with a > comment indicating that in that version log10() didn't work > for hyperarrays (unfortunately I don't recall what version it > was). > > In Version 6.1.0 it does work for hyperarrays, but the > documentation still says that it applies to vectors or matrices: > > https://help.scilab.org/docs/6.1.0/en_US/log10.html > > > In some contexts "matrix" may be interpreted as an hyperarray > or hypermatrix (for instance when speaking of N-D matrices), > but for Scilab a matrix is formally a two-dimensional array: > > https://help.scilab.org/docs/6.1.0/en_US/matrices.html > > > I think the documentation should indicate that it applies to > vectors, matrices and hypermatrices > > Another problem is regarding log(). It says that the input > argument is a "constant vector or constant matrix": > > https://help.scilab.org/docs/6.1.0/en_US/log.html > > > However, it seems that "constant" has a specific meaning in > Scilab as a predefined variable: > > https://help.scilab.org/docs/6.1.0/en_US/section_421ab29126e21a1e1e403ee27a18fda4.html > > > As it is worded, it seems that log() is applied to predefined > variables. I think it should refer more clearly to the type > double (it doesn't work, for instance, for integer types such > as int16(2)). > > In the case of log2() the description of arguments is even > stranger: > > https://help.scilab.org/docs/6.1.0/en_US/log2.html > > > It confuses the argument section with the description, and it > specifies decimal numbers which isn't a recognized type. > > The function exp(), on the other hand, doesn't indicate an > output argument. > > I think these functions are very similar and their > documentation pages should be consistent with one another > > Regards, > > Federico Miyara > > Image removed by sender. > > > > > Libre de virus. www.avast.com > > > > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users > > -- > > St?phane Mottelet > > Ing?nieur de recherche > > EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable > > D?partement G?nie des Proc?d?s Industriels > > Sorbonne Universit?s - Universit? de Technologie de Compi?gne > > CS 60319, 60203 Compi?gne cedex > > Tel : +33(0)344234688 > > http://www.utc.fr/~mottelet > > > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users > > -- > St?phane Mottelet > Ing?nieur de recherche > EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable > D?partement G?nie des Proc?d?s Industriels > Sorbonne Universit?s - Universit? de Technologie de Compi?gne > CS 60319, 60203 Compi?gne cedex > Tel : +33(0)344234688 > http://www.utc.fr/~mottelet > > _______________________________________________ > users mailing list > users at lists.scilab.org > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users -- St?phane Mottelet Ing?nieur de recherche EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable D?partement G?nie des Proc?d?s Industriels Sorbonne Universit?s - Universit? de Technologie de Compi?gne CS 60319, 60203 Compi?gne cedex Tel : +33(0)344234688 http://www.utc.fr/~mottelet -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 350 bytes Desc: not available URL: From antoine.monmayrant at laas.fr Mon Feb 22 14:04:09 2021 From: antoine.monmayrant at laas.fr (Antoine Monmayrant) Date: Mon, 22 Feb 2021 14:04:09 +0100 Subject: [Scilab-users] Some details on the documentation of log(), log10(), etc. In-Reply-To: References: <3a72f7ad-e0ad-0ae9-a4a2-cc0d4189c382@fceia.unr.edu.ar> <2b315ede-b290-133b-27b5-32560225c430@utc.fr> <10a85e38-ac2f-6e7a-a354-63085b081650@utc.fr> Message-ID: <7785e8e2-556f-78dc-4871-5b5e8c0ce289@laas.fr> Hello all, On 22/02/2021 10:12, St?phane Mottelet wrote: > > Hi, > > Le 22/02/2021 ? 09:43, Cl?ment David a ?crit?: >> >> Hello all, >> >> Thanks for opening the discussion on this ?new user?-related topic, >> this is always good to improve our help for existing user and new >> comers ; to let them havie a clear understanding of Scilab-lingua. >> >> One important point to me is to have a proper distinction between >> ?array? (as values organized in multiple dimensions) and more precise >> terms with more constraints on dimensions ?horizontal vector?, >> ?matrix?, etc? For keeping the rationale up to date, I suggest you to >> edit the Localization wiki page [1]. >> >> In term of code update, I can help you finding duplicated messages >> but keep in mind that the build-system create .pot files from the >> source code. To look for duplicate, the more important is to upgrade >> the source code. >> >> [1]: https://wiki.scilab.org/Localization in English - Standard messages >> >> Note: AFAK the ?constant? term has been removed on 6.0.0 >> documentation/error message as this is the default datatype, in case >> of advanced type management the term ?decimal? can be used instead. >> > I think that the "decimal" term has to be discussed. In no way the > default number type in Scilab is decimal > (https://en.wikipedia.org/wiki/Decimal). Scilab actually displays > rounded decimal approximations but internally they are IEEE754 > double-precision floating point numbers. I think that the "floating > point numbers" instead of "decimal" would be more suitable as is does > not make any mention of the basis. As far as I am concerned, I don't > have any problem with > > "array of floating point numbers" > I agree with St?phane here, "decimal" does not make sense. It is even deceiving as some languages implement proper base10 "decimal" data type, whereas scilab is defaulting to double (float64) data representation. But I think we should go further: "array of double" is even better. > > In some contexts, typically when describing the type of arguments in > the documentation of functions, we could be more precise by making > reference to the actual internal object type, i.e. "double" or > "Double", i.e. > > array of type double > array of double > Yes, that's exactly what I find best. For comparison, python3 mentions "float" and julia "float64" when inquiring about the default type of "a=1.1". > > Scilab users are mature enough to accept a bit of technical (but > precise) terms. But this is my personal opinion... > I agree, I don't see the point in mentioning something vague that a true beginner will have to learn anyway: it's better to start right away with learning the proper term to name the default datatype of scilab... Antoine > S. > >> Regards, >> >> Cl?ment >> >> *From:* users *On Behalf Of >> *St?phane Mottelet >> *Sent:* Saturday, February 20, 2021 5:35 PM >> *To:* users at lists.scilab.org >> *Subject:* Re: [Scilab-users] Some details on the documentation of >> log(), log10(), etc. >> >> By looking into the documentation messages I realized that we already >> use "array" : >> >> ./locale/de_DE/LC_MESSAGES/scilab.po-e:msgid "%s: Wrong type for >> input argument #%d: Array of double expected.\n" >> >> S. >> >> Le 20/02/2021 ? 17:21, St?phane Mottelet a ?crit?: >> >> Hi Frederico, >> >> In almost all other numerical software the object defined in >> Scilab by a=zeros(3,3,3) is called an "array", m=zeros(3,3) a >> "matrix" and x=zeros(1,3) or y=zeros(3,1) "vectors", and all of >> them are called "arrays". BTW, now the "hyper" prefix sounds like >> when it is used in "hyperspace"... To me, the documentation >> should be revamped to always use "array" when the denoted object >> can have any number of dimensions and use "matrix" only when the >> array has to be a matrix. Concerning your remark about the >> "constant vector or constant matrix", yes, this should be changed >> by something more explicit, like "array of double". We already >> use similar terms in error messages, i.e. >> >> "%s: Wrong type for input argument #%d: A matrix of double >> expected.\n" >> >> Hence we could synchonize the uses of localized messages with the >> documentation. When I say "we" it also includes "you", Frederico. >> If you feel that Scilab could be improved by a better >> documentation, please contribute. If you need some help to start >> using the relevant tools (git, codereview) I would be glad to >> help you. >> >> S. >> >> Le 20/02/2021 ? 01:29, Federico Miyara a ?crit?: >> >> >> Dear all, >> >> In an old script where I needed to apply log10 to an >> hyperarray I had implemented it as log(A)/log(10) with a >> comment indicating that in that version log10() didn't work >> for hyperarrays (unfortunately I don't recall what version it >> was). >> >> In Version 6.1.0 it does work for hyperarrays, but the >> documentation still says that it applies to vectors or matrices: >> >> https://help.scilab.org/docs/6.1.0/en_US/log10.html >> >> >> In some contexts "matrix" may be interpreted as an hyperarray >> or hypermatrix (for instance when speaking of N-D matrices), >> but for Scilab a matrix is formally a two-dimensional array: >> >> https://help.scilab.org/docs/6.1.0/en_US/matrices.html >> >> >> I think the documentation should indicate that it applies to >> vectors, matrices and hypermatrices >> >> Another problem is regarding log(). It says that the input >> argument is a "constant vector or constant matrix": >> >> https://help.scilab.org/docs/6.1.0/en_US/log.html >> >> >> However, it seems that "constant" has a specific meaning in >> Scilab as a predefined variable: >> >> https://help.scilab.org/docs/6.1.0/en_US/section_421ab29126e21a1e1e403ee27a18fda4.html >> >> >> As it is worded, it seems that log() is applied to predefined >> variables. I think it should refer more clearly to the type >> double (it doesn't work, for instance, for integer types such >> as int16(2)). >> >> In the case of log2() the description of arguments is even >> stranger: >> >> https://help.scilab.org/docs/6.1.0/en_US/log2.html >> >> >> It confuses the argument section with the description, and it >> specifies decimal numbers which isn't a recognized type. >> >> The function exp(), on the other hand, doesn't indicate an >> output argument. >> >> I think these functions are very similar and their >> documentation pages should be consistent with one another >> >> Regards, >> >> Federico Miyara >> >> Image removed by sender. >> >> >> >> >> Libre de virus. www.avast.com >> >> >> >> >> _______________________________________________ >> >> users mailing list >> >> users at lists.scilab.org >> >> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users >> >> -- >> >> St?phane Mottelet >> >> Ing?nieur de recherche >> >> EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable >> >> D?partement G?nie des Proc?d?s Industriels >> >> Sorbonne Universit?s - Universit? de Technologie de Compi?gne >> >> CS 60319, 60203 Compi?gne cedex >> >> Tel : +33(0)344234688 >> >> http://www.utc.fr/~mottelet >> >> >> >> _______________________________________________ >> >> users mailing list >> >> users at lists.scilab.org >> >> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users >> >> -- >> St?phane Mottelet >> Ing?nieur de recherche >> EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable >> D?partement G?nie des Proc?d?s Industriels >> Sorbonne Universit?s - Universit? de Technologie de Compi?gne >> CS 60319, 60203 Compi?gne cedex >> Tel : +33(0)344234688 >> http://www.utc.fr/~mottelet >> >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users > -- > St?phane Mottelet > Ing?nieur de recherche > EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable > D?partement G?nie des Proc?d?s Industriels > Sorbonne Universit?s - Universit? de Technologie de Compi?gne > CS 60319, 60203 Compi?gne cedex > Tel : +33(0)344234688 > http://www.utc.fr/~mottelet > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 350 bytes Desc: not available URL: From Clement.David at esi-group.com Thu Feb 25 16:10:34 2021 From: Clement.David at esi-group.com (=?utf-8?B?Q2zDqW1lbnQgRGF2aWQ=?=) Date: Thu, 25 Feb 2021 15:10:34 +0000 Subject: [Scilab-users] Scilab 5.5.2 in Debian 10 - segmentation fault In-Reply-To: <1613642380.494905850@f547.i.mail.ru> References: <1613642380.494905850@f547.i.mail.ru> Message-ID: Hello Andrei, To launch the Scilab 5.5.2 binary on new Linux version, you might need to remove some libraries (so files) provided by your system. Especially, you could remove the scilab-5.5.2/lib/thirdparty/libz.so.1 file which is provided by your system. Regards, Cl?ment From: users On Behalf Of Andrei Lomov Sent: Thursday, February 18, 2021 11:00 AM To: users at lists.scilab.org Subject: [Scilab-users] Scilab 5.5.2 in Debian 10 - segmentation fault Hi All, In order to use Scilab? parallel_run in Debian 10 (x86_64), i download https://www.scilab.org/download/5.5.2/scilab-5.5.2.bin.linux-x86_64.tar.gz unpack it to ~/foo/scilab-5.5.2 then cd ~/foo/scilab-5.5.2/bin and run ? $./scilab Segmentation fault :(( ? What am I doing wrong ... -- WBR, Andrei -------------- next part -------------- An HTML attachment was scrubbed... URL: From antoine.monmayrant at laas.fr Thu Feb 25 16:24:38 2021 From: antoine.monmayrant at laas.fr (Antoine Monmayrant) Date: Thu, 25 Feb 2021 16:24:38 +0100 Subject: [Scilab-users] Scilab 5.5.2 in Debian 10 - segmentation fault In-Reply-To: References: <1613642380.494905850@f547.i.mail.ru> Message-ID: <13ca9aaf-4a5e-de60-dddf-eba0f432d329@laas.fr> Hello Cl?ment, I forgot that detail. But this will not help Andrei use parallel_run, as it does not work under linux, right? Cheers, Antoine On 25/02/2021 16:10, Cl?ment David wrote: > > Hello Andrei, > > To launch the Scilab 5.5.2 binary on new Linux version, you might need > to remove some libraries (so files) provided by your system. > Especially, you could remove the scilab-5.5.2/lib/thirdparty/libz.so.1 > file which is provided by your system. > > Regards, > > Cl?ment > > *From:* users *On Behalf Of *Andrei Lomov > *Sent:* Thursday, February 18, 2021 11:00 AM > *To:* users at lists.scilab.org > *Subject:* [Scilab-users] Scilab 5.5.2 in Debian 10 - segmentation fault > > Hi All, > > In order to use Scilab? parallel_run in Debian 10 (x86_64), > > i download > > https://www.scilab.org/download/5.5.2/scilab-5.5.2.bin.linux-x86_64.tar.gz > > unpack it to > > ~/foo/scilab-5.5.2 > > then > > cd ~/foo/scilab-5.5.2/bin > > and run ? > > $./scilab > > Segmentation fault > > :(( > > ? What am I doing wrong ... > > -- > WBR, > > Andrei > > > _______________________________________________ > 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 esi-group.com Thu Feb 25 16:29:29 2021 From: Clement.David at esi-group.com (=?utf-8?B?Q2zDqW1lbnQgRGF2aWQ=?=) Date: Thu, 25 Feb 2021 15:29:29 +0000 Subject: [Scilab-users] Scilab 5.5.2 in Debian 10 - segmentation fault In-Reply-To: <13ca9aaf-4a5e-de60-dddf-eba0f432d329@laas.fr> References: <1613642380.494905850@f547.i.mail.ru> <13ca9aaf-4a5e-de60-dddf-eba0f432d329@laas.fr> Message-ID: Hello Antoine, It should run on Linux using 5.5.2 (as fork() is available) however if parallel work is needed I suggest you to use Scilab MPI rather than parallel_run. The former is process based with explicit variable transfer whereas the latter is implicit. See https://help.scilab.org/docs/5.5.2/en_US/MPI_Recv.html for more information. Thanks, Cl?ment From: users On Behalf Of Antoine Monmayrant Sent: Thursday, February 25, 2021 4:25 PM To: users at lists.scilab.org Subject: Re: [Scilab-users] Scilab 5.5.2 in Debian 10 - segmentation fault Hello Cl?ment, I forgot that detail. But this will not help Andrei use parallel_run, as it does not work under linux, right? Cheers, Antoine On 25/02/2021 16:10, Cl?ment David wrote: Hello Andrei, To launch the Scilab 5.5.2 binary on new Linux version, you might need to remove some libraries (so files) provided by your system. Especially, you could remove the scilab-5.5.2/lib/thirdparty/libz.so.1 file which is provided by your system. Regards, Cl?ment From: users On Behalf Of Andrei Lomov Sent: Thursday, February 18, 2021 11:00 AM To: users at lists.scilab.org Subject: [Scilab-users] Scilab 5.5.2 in Debian 10 - segmentation fault Hi All, In order to use Scilab? parallel_run in Debian 10 (x86_64), i download https://www.scilab.org/download/5.5.2/scilab-5.5.2.bin.linux-x86_64.tar.gz unpack it to ~/foo/scilab-5.5.2 then cd ~/foo/scilab-5.5.2/bin and run ? $./scilab Segmentation fault :(( ? What am I doing wrong ... -- WBR, Andrei _______________________________________________ users mailing list users at lists.scilab.org http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephane.mottelet at utc.fr Thu Feb 25 16:33:59 2021 From: stephane.mottelet at utc.fr (=?utf-8?Q?St=C3=A9phane_Mottelet?=) Date: Thu, 25 Feb 2021 16:33:59 +0100 Subject: [Scilab-users] Scilab 5.5.2 in Debian 10 - segmentation fault In-Reply-To: <13ca9aaf-4a5e-de60-dddf-eba0f432d329@laas.fr> References: <13ca9aaf-4a5e-de60-dddf-eba0f432d329@laas.fr> Message-ID: <8D144D62-6E89-4A9C-981D-2181B9B0F422@utc.fr> It?s exactly the opposite. It does work with 5.5.2 under Linux but does not with 5.5.2 under Windows. S. > Le 25 f?vr. 2021 ? 16:25, Antoine Monmayrant a ?crit : > > ? > Hello Cl?ment, > > I forgot that detail. > But this will not help Andrei use parallel_run, as it does not work under linux, right? > > Cheers, > > Antoine > > On 25/02/2021 16:10, Cl?ment David wrote: >> Hello Andrei, >> >> To launch the Scilab 5.5.2 binary on new Linux version, you might need to remove some libraries (so files) provided by your system. Especially, you could remove the scilab-5.5.2/lib/thirdparty/libz.so.1 file which is provided by your system. >> >> Regards, >> >> Cl?ment >> >> From: users On Behalf Of Andrei Lomov >> Sent: Thursday, February 18, 2021 11:00 AM >> To: users at lists.scilab.org >> Subject: [Scilab-users] Scilab 5.5.2 in Debian 10 - segmentation fault >> >> Hi All, >> In order to use Scilab? parallel_run in Debian 10 (x86_64), >> i download >> https://www.scilab.org/download/5.5.2/scilab-5.5.2.bin.linux-x86_64.tar.gz >> unpack it to >> ~/foo/scilab-5.5.2 >> then >> cd ~/foo/scilab-5.5.2/bin >> and run ? >> >> $./scilab >> >> Segmentation fault >> :(( >> >> ? What am I doing wrong ... >> >> -- >> WBR, >> Andrei >> >> >> >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> http://lists.scilab.org/mailman/listinfo/users > _______________________________________________ > users mailing list > users at lists.scilab.org > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephane.mottelet at utc.fr Fri Feb 26 14:38:54 2021 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Fri, 26 Feb 2021 14:38:54 +0100 Subject: [Scilab-users] Variable scope in Scilab Message-ID: Hi all, In Scilab the scope of variables is quite permissive but even in Julia (really strict rules) we can have the following behavior: function y=f(x) ?y=x+a; end a=1; f(2) a=2; f(3) -> a=1; --> f(2) ?ans? = ?? 3. --> a=2; --> f(3) ?ans? = ?? 5. Yesterday afternoon I was my students for a Scilab beginners tutorial, and by accident one of them had "x" defined before in the main workspace and tried to call f without arguments. I reproduce the experiment here by explicitely defining x before the call: x=1; f --> x=1; --> f ?ans? = ?? 3. Allowing the function inner scope to see variables of the outer scope is one thing, you may or may not agree this is not the point here, but allowing to call f without arguments just because the formal input parameter has the same symbol as an outer scope symbol is another thing. I knew this was possible even if i never used such a feature, but my students were so puzzled by this, particularly those who already learned other low-level languages, that I decided to propose the suppression of this, that I consider as a serious potential source of many bugs. Don't tell me that this would break some user code because I frankly have no consideration for this kind of crappy shortcut and, sorry if it may sound rude, for programmers who use it... S. -- St?phane Mottelet Ing?nieur de recherche EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable D?partement G?nie des Proc?d?s Industriels Sorbonne Universit?s - Universit? de Technologie de Compi?gne CS 60319, 60203 Compi?gne cedex Tel : +33(0)344234688 http://www.utc.fr/~mottelet From fmiyara at fceia.unr.edu.ar Sat Feb 27 01:33:34 2021 From: fmiyara at fceia.unr.edu.ar (Federico Miyara) Date: Fri, 26 Feb 2021 21:33:34 -0300 Subject: [Scilab-users] Variable scope in Scilab In-Reply-To: References: Message-ID: <8ad002b5-ddc8-30b2-943f-5177d85adea7@fceia.unr.edu.ar> St?phane, I agree it shouldn't happen, but the same moment access to outer variables is granted you can't prevent such thing to happen since inside the function all variables have a name which is more than just a symbol or a mute variable, and this includes undefined arguments. This scoping feature is dangerous and I don't think it would be advisable to create a macro for general use exploiting it. May be someone can provide an example where it has been used with profit or explain why it was originally introduced Regards, Federico Miyara On 26/02/2021 10:38, St?phane Mottelet wrote: > Hi all, > > In Scilab the scope of variables is quite permissive but even in Julia > (really strict rules) we can have the following behavior: > > function y=f(x) > ?y=x+a; > end > > a=1; > f(2) > a=2; > f(3) > > -> a=1; > > --> f(2) > ?ans? = > > ?? 3. > > --> a=2; > > --> f(3) > ?ans? = > > ?? 5. > > Yesterday afternoon I was my students for a Scilab beginners tutorial, > and by accident one of them had "x" defined before in the main > workspace and tried to call f without arguments. I reproduce the > experiment here by explicitely defining x before the call: > > x=1; > f > > --> x=1; > > --> f > ?ans? = > > ?? 3. > > Allowing the function inner scope to see variables of the outer scope > is one thing, you may or may not agree this is not the point here, but > allowing to call f without arguments just because the formal input > parameter has the same symbol as an outer scope symbol is another > thing. I knew this was possible even if i never used such a feature, > but my students were so puzzled by this, particularly those who > already learned other low-level languages, that I decided to propose > the suppression of this, that I consider as a serious potential source > of many bugs. Don't tell me that this would break some user code > because I frankly have no consideration for this kind of crappy > shortcut and, sorry if it may sound rude, for programmers who use it... > > S. > -- El software de antivirus Avast ha analizado este correo electr?nico en busca de virus. https://www.avast.com/antivirus -------------- next part -------------- An HTML attachment was scrubbed... URL: From johan.lafitte at gmail.com Sun Feb 28 12:55:46 2021 From: johan.lafitte at gmail.com (johan64) Date: Sun, 28 Feb 2021 04:55:46 -0700 (MST) Subject: [Scilab-users] xcos_simulate() In-Reply-To: References: Message-ID: <1614513346933-0.post@n3.nabble.com> Hi, I am sorry, there is a mistake in my first post. Please, don't care about the script described in italic. My need is to compile my xcos diagram one time, simulate, then change context parameters and run other simulations (in order to perform parametric optimization on a large xcos model with many parameters and about 10-15 state variables). I did some research and tests. To sum up : 1/xcos_simulate(scs_m,needcompile) : According to the Scilab Help, needcompil is "DEPRECATED". Therefore, compilation is needed each times. ////////////////////////////// 2/scicos_simulate(scs_m,Info). I tried the PID optimization example method. https://wiki.scilab.org/Xcos/Examples/PID Execute my model with ///Lancement de la simulation disp("lancement") tic(); Info=scicos_simulate(scs_m,list()) disp( "Dur?e simulation1",toc()); tic(); Info=scicos_simulate(scs_m,Info) disp( "Dur?e simulation2",toc())/ Gives /"lancement" "Dur?e simulation1" 83.604448 "Dur?e simulation2" 81.738820/ Therefore, I win just 2 seconds with this method ///////////////////////////////////////////////////// 3/scicosim(); It seems to be the holy grail. / disp("lancement") tic(); cpr=xcos_simulate(scs_m,4) //cpr = xcos_compile(scs_m); disp( "Simulation time 1 =",toc()); //Exploitation des donn?es de compilation state0=cpr.state; // cpr variable came from the compilation sim=cpr.sim; //Param?tre de simulation tf=111; atol=1.e-6; rtol=1.e-6; ttol=1.e-10; deltat=tf; scale=0; solver=0; hmax=0.1; tol=[atol,rtol,ttol,deltat,scale,solver,hmax]; //Enregistrement des r?sultats //save(pathu_result); tic(); // initialisation [state,t]=scicosim(state0,0,tf,sim,'start',tol); // run [state,t]=scicosim(state,t,tf,sim,'run',tol) //end [state,t]=scicosim(state,t,tf,sim,'finish',tol); disp("Simulation time 2"+" = ",toc()); / Gives / "Simulation time 1 =" 83.815849 "Simulation time 2 = " 0.9816021 / I win about 83 seconds!!! Unfortunately, after running xcos_simulate one time, I don't find simple way to change context parameters without launch xcos_simulate again (using scs_m.props.context...) which wastes simulation time. cpr.sim.rpar seems to contain block parameters but without symbolic expression. does anyone have an idea? Thank you for your help -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html