From perrichon.pierre at wanadoo.fr Sun Mar 1 20:37:57 2020 From: perrichon.pierre at wanadoo.fr (Perrichon) Date: Sun, 1 Mar 2020 20:37:57 +0100 Subject: [Scilab-users] Isoview in GUI - Scilab 6.1.0 In-Reply-To: References: Message-ID: Hello Samuel It?s OK. I get exactly the same shape Thanks you so much Pierre P. De : users De la part de Samuel Gougeon Envoy? : jeudi 27 f?vrier 2020 15:35 ? : users at lists.scilab.org Objet : Re: [Scilab-users] Isoview in GUI - Scilab 6.1.0 Hello Pierre, The former isoview() implementation mixed some poor isometrical tuning, with some unrelated rebounding action. This is why both types of actions have been split: * isoview deals only with the isometrical view, in a richer way than formerly: Please see history sections and compare synopses https://help.scilab.org/docs/6.0.0/en_US/isoview.html with the former https://help.scilab.org/docs/5.5.2/en_US/isoview.html * replot(), whose dedicated action is to rebound axes, has also been extended a lot in Scilab: Please compare https://help.scilab.org/docs/6.0.0/en_US/replot.html with the former https://help.scilab.org/docs/5.5.2/en_US/replot.html Users were warned about this isoview change for 3 years. So, the replacement for the former isoview([xmin,xmax,ymin,ymax]) is simply isoview replot([xmin,ymin,xmax,ymax]) with extended features with bounds values. Maybe you think that replot() is not a nice name, not describing the actual action of replot(). I would definitively agree. But reframing axes has aways been its dedicated action. And isoview() wasn't the right name to support (poor) rebounding features, either I hope you will appreciate and use recent isoview and replot features, separately. Best regards Samuel Le 27/02/2020 ? 12:18, Perrichon a ?crit : Hello, I?ve seen that syntax change for the isoview in scilab 6.1.0 : isoview(gcf(), "on") // Scilab 6.1.0 In that case I must take a new time bounds in Nyquist and positionning 0 dB, 3 dB and so on In my GUI, I personnaly prefer this fonction in scilab 5.5.2, where I can fixe limits for the drawing isoview(-1.0,1.0,-1.0,1.0); // Scilab 5.5.2 So I?ve done a copy of isoview Scilab 5.5.2, call Isoview, and automaticcaly load at scilab 6.1.0 in the scilab.ini of SCIHOME I hope this solution will be sustainable Isoview in GUI - Scilab 5.5.2 Best regards _______________________________________________ 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: image002.jpg Type: image/jpeg Size: 38383 bytes Desc: not available URL: From Clement.David at esi-group.com Mon Mar 2 10:17:38 2020 From: Clement.David at esi-group.com (=?iso-8859-1?Q?Cl=E9ment_David?=) Date: Mon, 2 Mar 2020 09:17:38 +0000 Subject: [Scilab-users] Context error in Xcos Scilab 6.1.0 In-Reply-To: References: <0e66dc9d-2f68-8446-919b-22125b535294@free.fr> Message-ID: Hello Pierre, Samuel, First, did you opened a bug on that issue? Second, to me, the bug is located on the script2var() function which resolves the context and output a struct of `variable=value` that are defined for the diagram (and its parents). For example, when I explicitly define A=100 in the context, the A variable is found and resolved as 100 in the diagram. However, defining A=50 inside the A.ctx file and using the schema A610.zcos, where the A.ctx file is passed to exec(), failed. Regards, -- Cl?ment > -----Original Message----- > From: users On Behalf Of Perrichon > Sent: Saturday, February 29, 2020 7:35 PM > To: 'Users mailing list for Scilab' > Subject: Re: [Scilab-users] Context error in Xcos Scilab 6.1.0 > > Hello Samuel, > > > > Glad to see you confirm this bug > > > > Context is executed at line 26 of the A.sce file, and not before : > > ---> xcos_simulate(scs_m, 4); > > > > So in scilab 6.1.0, the A.ctx is executed. > > I also add in A610.zcos the instruction > > * mprintf("Running context in xcos. ...So A=%i\n",A) > > > > And then here is the track in my PC when running A.sce in xcos 6.1.0 : > > > > > > --> exec('C:\0 - tampon\A.sce', -1) > > Chargement du contexte d'ex?cution A.ctx > > > > Running context in xcos. ...So A=50 > > > > Where we can see that A=50 inside A610.zcos. > > > > We also can see that A is lost a the end of the context execution > > > > > > This bad behavior also explains that my projects don't migrate from xcos 5.5.2 > to 6.1.0 > > > > Be sure that in my projects, the ct xis a set of a lot of scilab instructions who > generate variables. > > These variables are use in any bloscks and under blocks of my main shemes > > > > > > BR > > > > > > De : users De la part de Samuel Gougeon > Envoy? : samedi 29 f?vrier 2020 17:53 ? : users at lists.scilab.org Objet : Re: > [Scilab-users] Context error in Xcos Scilab 6.1.0 > > > > Le 29/02/2020 ? 17:41, Samuel Gougeon a ?crit : > > Hello Pierre, > > > > Le 29/02/2020 ? 11:32, Perrichon a ?crit : > > Hello, > > > > I try to understand and find a reason why my projects done with > xcos scilab 5.5.2 not run i 6.1.0 > > So I isolate at least one reason in a basic test program (see > attached files) > > > > Here, zcos file are lunched into scilab 5.5.2 or 6.10, with the > A.sce file which test the version > > > > A.ctx is a context file. Here is a simple variable definition A=50 > in that case. > > > > Every zcos file contains in its simulation contexte, the > instruction ? exec("A.ctx") ? ; accessible with simulation-> context modifying > > > > To run this program, make a directory, a copy of the attached > files, and change eventually line 4 in A.sce : > > Root="c:\0 - tampon" // > R?pertoire de travail pour le test > > > > So run A.sce inside xcos scilab 5.5.2 or 6.1.0 > > > > Scilab 5.5.2 run correctly : > > > > > > > Scilab 6.1.0 is bugged : > > > > > > Apparently, the problem is that the context is not executed when the > diagram is loaded. > Despite what the context message indicates: > > > > Indeed, the message mprintf("Chargement du contexte d''ex?cution > %s\n\n",FichierContexte) > set in the context is not displayed when the diagram is loaded in 6.1.0 ; > only when the context > is updated (or simply edited and revalidated). > > With Scilab 5.5, the context is not executed when loading the > diagram,but when running it. > > So, to me, there are apparently 2 issues: > > 1. The Set Context message should be fixed: "... and every time > the diagram is run" (not loaded) > 2. The fact that the context is executed when the diagram is run > should be restored in Scilab 6. > > Sorry, i don't know what occurred with my first trial, but now it works: > In 6.0.2 and 6.1.0, the message is well displayed when the diagram is run. > The error message displayed on the icon is the following: > > > > > > Samuel > > From perrichon.pierre at wanadoo.fr Mon Mar 2 11:08:45 2020 From: perrichon.pierre at wanadoo.fr (Perrichon) Date: Mon, 2 Mar 2020 11:08:45 +0100 Subject: [Scilab-users] Xcos 6.1.0 - benchmark time test In-Reply-To: References: Message-ID: Hello Cl?ment, Yes, I have some function blocks and expression blocks. Must I understand that I have to write CBLOCK for scilab function or scilab expression or both ? Here are other results for a more complex project name PELT1 Time request : 100 s Results : Xcos Scilab 5.5.2 : Dur?e de la simulation : 258.3 s Xcos Sciab 6.1.0 : Dur?e de la simulation : 4353.4 s So the ratio is 16.8 for PELT1 Other information : Scilab 5.5.2 : time between click go and first scope on the screen = 5 s Scilab 6.1.0 : time between click go and first scope on the screen = 95 s Ratio=19 and I also have other projects more complex Pelt1 is for 1 needle (2 positonning loop) Perlt6 for 6 !!! (7 positonning loop) BR De : users De la part de Cl?ment David Envoy? : vendredi 28 f?vrier 2020 10:10 ? : Users mailing list for Scilab Objet : Re: [Scilab-users] Xcos 6.1.0 - benchmark time test Hello Pierre, Are you using a block with its simulation function implemented in Scilab? Any C/C++ implemented block might perform the same at simulation time. In 6.0.2, implementing Xcos blocks using the Scilab language had some performance issues. In 6.1.0, I tried to speed up things a little bit by reusing some allocated data structure during simulation time [1] ; more work might still be needed here. [1]: http://cgit.scilab.org/scilab/commit/?id=bfe4f25275dc0d889817d10b63e10c9a064 1ef32 Regards, -- Cl?ment From: users > On Behalf Of Perrichon Sent: Friday, February 28, 2020 8:51 AM To: 'Users mailing list for Scilab' > Subject: [Scilab-users] Xcos 6.1.0 - benchmark time test Hello, Here I test a PELTON basic algorithm under xcos, and record with tic-toc the simulation real time. These programs have been set for 120 s (scope) Results : Xcos Scilab 5.5.2 : Dur?e de la simulation : 45.4 s Xcos Sciab 6.1.0 : Dur?e de la simulation : 65.2 s So the ratio is 1.44 for a basic sheme Any explaination ? Can that be improved ? BR -------------- next part -------------- An HTML attachment was scrubbed... URL: From Clement.David at esi-group.com Mon Mar 2 12:25:09 2020 From: Clement.David at esi-group.com (=?iso-8859-1?Q?Cl=E9ment_David?=) Date: Mon, 2 Mar 2020 11:25:09 +0000 Subject: [Scilab-users] Xcos 6.1.0 - benchmark time test In-Reply-To: References: Message-ID: Hello Pierre, Thanks for the numbers, I will try to describe what can be down to work around the time to results. >From when you start the simulation to the first scope popup, the schema is converted to a list of functions to be called in a specific order and passed to a solver that will iterate on time to "run" the simulation. There might be a difference between Scilab 5 and Scilab 6 as this transformation is written using the Scilab language. It is the 5s to 95s ratio. While the simulation is running, each block's simulation function is called a number of times. The solver/simulator/function API did not change between Scilab 5 and Scilab 6, this should perform the same way. However, some functions, especially sciblk2 and sciblk4 are wrappers from C to Scilab functions and have been re-written to behave very differently. It is the 253s (258-5) to 4258s (4353-95) ratio (lower ratio but much more impact). Could you please file a bug with some representative example (same number of blocks, similar Scilab function) for further investigation ? Note: having "costly" sciblk2 and sciblk4 also highly depends on your schema, for example having them on a continuous loop will make the solver call them on each timestep. Regards, -- Cl?ment From: Perrichon Sent: Monday, March 2, 2020 11:09 AM To: 'Users mailing list for Scilab' ; Cl?ment David Subject: RE: [Scilab-users] Xcos 6.1.0 - benchmark time test Hello Cl?ment, Yes, I have some function blocks and expression blocks. Must I understand that I have to write CBLOCK for scilab function or scilab expression or both ? Here are other results for a more complex project name PELT1 Time request : 100 s Results : Xcos Scilab 5.5.2 : Dur?e de la simulation : 258.3 s Xcos Sciab 6.1.0 : Dur?e de la simulation : 4353.4 s So the ratio is 16.8 for PELT1 Other information : Scilab 5.5.2 : time between click go and first scope on the screen = 5 s Scilab 6.1.0 : time between click go and first scope on the screen = 95 s Ratio=19 ...and I also have other projects more complex Pelt1 is for 1 needle (2 positonning loop) Perlt6 for 6 !!! (7 positonning loop) BR De : users > De la part de Cl?ment David Envoy? : vendredi 28 f?vrier 2020 10:10 ? : Users mailing list for Scilab > Objet : Re: [Scilab-users] Xcos 6.1.0 - benchmark time test Hello Pierre, Are you using a block with its simulation function implemented in Scilab? Any C/C++ implemented block might perform the same at simulation time. In 6.0.2, implementing Xcos blocks using the Scilab language had some performance issues. In 6.1.0, I tried to speed up things a little bit by reusing some allocated data structure during simulation time [1] ; more work might still be needed here. [1]: http://cgit.scilab.org/scilab/commit/?id=bfe4f25275dc0d889817d10b63e10c9a0641ef32 Regards, -- Cl?ment From: users > On Behalf Of Perrichon Sent: Friday, February 28, 2020 8:51 AM To: 'Users mailing list for Scilab' > Subject: [Scilab-users] Xcos 6.1.0 - benchmark time test Hello, Here I test a PELTON basic algorithm under xcos, and record with tic-toc the simulation real time. These programs have been set for 120 s (scope) Results : Xcos Scilab 5.5.2 : Dur?e de la simulation : 45.4 s Xcos Sciab 6.1.0 : Dur?e de la simulation : 65.2 s So the ratio is 1.44 for a basic sheme Any explaination ? Can that be improved ? BR -------------- next part -------------- An HTML attachment was scrubbed... URL: From perrichon.pierre at wanadoo.fr Mon Mar 2 12:55:52 2020 From: perrichon.pierre at wanadoo.fr (Perrichon) Date: Mon, 2 Mar 2020 12:55:52 +0100 Subject: [Scilab-users] Zoom and datatips no longer work in Xcos version 6.1.0 during runtime Message-ID: Hello, Zoom and datatips no longer work in Xcos version 6.1.0 during runtime It well run with Scilab 5.5.2 See also bugzilla #16353 Best regard Pierre P. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 12408 bytes Desc: not available URL: From perrichon.pierre at wanadoo.fr Mon Mar 2 14:52:27 2020 From: perrichon.pierre at wanadoo.fr (Perrichon) Date: Mon, 2 Mar 2020 14:52:27 +0100 Subject: [Scilab-users] strange sounds repeated over and over in scilab 6.1.0 Message-ID: Hello Few years ago, I got routines producing sounds in threads With Scilab 5.5.2, sounds are produced once. With Scilab 6.1.0, sounds are repeated endlessly. Best regards W10 x64 function Sound1() // by Gary Scavone, McGill University, 2004 // Bell-like sound fs = 22050; T = 1/fs; dur = 4; t = 0:T:dur; T60 = 0.5; env = 0.95*exp(-t/T60); // FM parameters fc = 200; fm = 280; Imax = 10; I = Imax.*env; y = env.*sin(2*%pi*fc*t + I.*sin(2*%pi*fm*t)); sound(y, fs); endfunction function Sound3() x=1e2:1e4; b=0.6; y=window('hm',length(x)).*sin(x.^b.*log(x)); sound(y,9944) endfunction -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Mon Mar 2 16:15:14 2020 From: sgougeon at free.fr (Samuel Gougeon) Date: Mon, 2 Mar 2020 16:15:14 +0100 Subject: [Scilab-users] strange sounds repeated over and over in scilab 6.1.0 In-Reply-To: References: Message-ID: <9dadd81e-95ac-4326-258d-2ff06c6e7f99@free.fr> Le 02/03/2020 ? 14:52, Perrichon a ?crit?: > > Hello > > Few years ago, I got routines producing sounds in threads > > With Scilab 5.5.2, sounds are produced once. > > With Scilab 6.1.0, sounds are repeated endlessly. > No no, "only" 16 times :-) You can stop it with playsnd([]) or CTRL+C. I have proposed to remove sound(), that is a duplicate of playsnd() and brings nothing. But finally this has not been done for 6.1.0. playsnd() has been upgraded. In the change, its nbits argument has been removed. But we have forgotten to update sound() calling playsnd(). So you hear the sound the default nbits=16 times. You must directly use playsnd() instead. Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From perrichon.pierre at wanadoo.fr Mon Mar 2 16:45:40 2020 From: perrichon.pierre at wanadoo.fr (Perrichon) Date: Mon, 2 Mar 2020 16:45:40 +0100 Subject: [Scilab-users] strange sounds repeated over and over in scilab 6.1.0 In-Reply-To: <9dadd81e-95ac-4326-258d-2ff06c6e7f99@free.fr> References: <9dadd81e-95ac-4326-258d-2ff06c6e7f99@free.fr> Message-ID: Ok but this is a strange way to handle backward compatibility De : users De la part de Samuel Gougeon Envoy? : lundi 2 mars 2020 16:15 ? : users at lists.scilab.org Objet : Re: [Scilab-users] strange sounds repeated over and over in scilab 6.1.0 Le 02/03/2020 ? 14:52, Perrichon a ?crit : Hello Few years ago, I got routines producing sounds in threads With Scilab 5.5.2, sounds are produced once. With Scilab 6.1.0, sounds are repeated endlessly. No no, "only" 16 times :-) You can stop it with playsnd([]) or CTRL+C. I have proposed to remove sound(), that is a duplicate of playsnd() and brings nothing. But finally this has not been done for 6.1.0. playsnd() has been upgraded. In the change, its nbits argument has been removed. But we have forgotten to update sound() calling playsnd(). So you hear the sound the default nbits=16 times. You must directly use playsnd() instead. Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Mon Mar 2 17:03:53 2020 From: sgougeon at free.fr (Samuel Gougeon) Date: Mon, 2 Mar 2020 17:03:53 +0100 Subject: [Scilab-users] strange sounds repeated over and over in scilab 6.1.0 In-Reply-To: References: <9dadd81e-95ac-4326-258d-2ff06c6e7f99@free.fr> Message-ID: Le 02/03/2020 ? 16:45, Perrichon a ?crit?: > > Ok but this is a strange way to handle backward compatibility > I agree. This is why i asked for confirmation to a second reviewer before removing nbits, when the first reviewer asked me to remove it. nbits was never implemented (never actually used in the function), just present as a dead input. But it was not disturbing. Now, i guess that sometimes it's useful to clean the code. I think that the next input argument "aplay" after nbits is (very) rarely used (it addresses "only" Linux and MacOS users (15%), and only if its default value is not convenient (? 5% of 15% ?). Most often, only the first 2 arguments are used. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ayrat.khalimov at gmail.com Mon Mar 2 17:40:06 2020 From: ayrat.khalimov at gmail.com (Ayrat Khalimov) Date: Mon, 2 Mar 2020 17:40:06 +0100 Subject: [Scilab-users] Algebraic loop when using Modelica but not with original Xcos Message-ID: hi all, What can cause the following behaviour: there are two "circuits", one is built entirely of the original xcos components, another one uses a mix of coselica and xcos. The circuit with coselica reports "Algebraic loop", whereas the pure xcos does not. The two schemes are attached. The figures are below. *Pure xcos, no algebraic loop* [image: image.png] *Coselica, algebraic loop error:* [image: image.png] [image: image.png] I also tried to insert the delay into the feedback connection, to no avail. thanks, ayrat -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 18829 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 25552 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 15177 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: coselica_alg_loop.zcos Type: application/octet-stream Size: 4904 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pure_xcos_no_loop.zcos Type: application/octet-stream Size: 4076 bytes Desc: not available URL: From fmiyara at fceia.unr.edu.ar Tue Mar 3 06:29:09 2020 From: fmiyara at fceia.unr.edu.ar (Federico Miyara) Date: Tue, 3 Mar 2020 02:29:09 -0300 Subject: [Scilab-users] strange sounds repeated over and over in scilab 6.1.0 In-Reply-To: References: <9dadd81e-95ac-4326-258d-2ff06c6e7f99@free.fr> Message-ID: <48044b91-b787-c4db-9aa6-b93aff257644@fceia.unr.edu.ar> Just a thought: nbits should never have been an input argument of a playback function, since the precision of the internal data is much higher than even 24 bit, the higher bit resolution usually found in audio playback systems (not to be confused with the internal representation of many digital signal processors; I mean D/A converters). By the way, 24 bit means 144 dB signal/noise ratio, much higher than currently attainable analog performance. The only situation where that could be of some interest would be to demonstrate in the classroom the effects of reducing the number of bits per sample. But as such case is very specific and quite rare, it would be better just to requantize de original signal getting entire control of the situation, being able to measure noise and /or distortion, plot the stair-like waveform and listen to the result. Federico Miyara On 02/03/2020 13:03, Samuel Gougeon wrote: > Le 02/03/2020 ? 16:45, Perrichon a ?crit?: >> >> Ok but this is a strange way to handle backward compatibility >> > > I agree. This is why i asked for confirmation to a second reviewer > before removing nbits, > when the first reviewer asked me to remove it. > nbits was never implemented (never actually used in the function), > just present as a dead input. > But it was not disturbing. > Now, i guess that sometimes it's useful to clean the code. I think > that the next input argument "aplay" > after nbits is (very) rarely used (it addresses "only" Linux and MacOS > users (15%), and only if > its default value is not convenient (? 5% of 15% ?). Most often, only > the first 2 arguments are used. > > > > > _______________________________________________ > 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 Tue Mar 3 13:57:17 2020 From: sgougeon at free.fr (Samuel Gougeon) Date: Tue, 3 Mar 2020 13:57:17 +0100 Subject: [Scilab-users] Context error in Xcos Scilab 6.1.0 In-Reply-To: References: <0e66dc9d-2f68-8446-919b-22125b535294@free.fr> Message-ID: <4bd1d67d-49b8-950e-3bb7-56ebe09d8a5e@free.fr> Le 02/03/2020 ? 10:17, Cl?ment David a ?crit?: > Hello Pierre, Samuel, > > First, did you opened a bug on that issue? > > Second, to me, the bug is located on the script2var() function which resolves the context and output a struct of `variable=value` that are defined for the diagram (and its parents). For example, when I explicitly define A=100 in the context, the A variable is found and resolved as 100 in the diagram. However, defining A=50 inside the A.ctx file and using the schema A610.zcos, where the A.ctx file is passed to exec(), failed. Thanks Cl?ment for the indication and the report . Pierre, A solution is available => there . How to install it: * Download and unzip the file. Rename it script2var.sci * Put script2var.sci in its SCI/scicos/macros/scicos_scicos directory * Run the following Scilab code in the console, /with some full read/write rights/: cd SCI/scicos/macros/scicos_scicos predef clear genlib scicos_scicoslib clear script2var Then things should work for your session and any following ones. If you get some error when running genlib(), it is most probably because you don't have enough rights to overwrite the library with its update. BR Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From perrichon.pierre at wanadoo.fr Tue Mar 3 16:23:17 2020 From: perrichon.pierre at wanadoo.fr (Perrichon) Date: Tue, 3 Mar 2020 16:23:17 +0100 Subject: [Scilab-users] Context error in Xcos Scilab 6.1.0 In-Reply-To: <4bd1d67d-49b8-950e-3bb7-56ebe09d8a5e@free.fr> References: <0e66dc9d-2f68-8446-919b-22125b535294@free.fr> <4bd1d67d-49b8-950e-3bb7-56ebe09d8a5e@free.fr> Message-ID: Hello Samuel : 1. The correct pathname of script2var.sci is rather SCI/modules/scicos/macros/scicos_scicos 2. If I launch your instructions with the correct directory, I get : --> cd SCI/modules/scicos/macros/scicos_scicos ans = "C:\Program Files\scilab-6.1.0\modules\scicos\macros\scicos_scicos" --> predef clear --> genlib scicos_scicoslib genlib : Impossible d'ouvrir le fichier "C:\Program Files\scilab-6.1.0\modules\scicos\macros\scicos_scicos\lib". ans = F --> clear script2var To read you Best regards De : users De la part de Samuel Gougeon Envoy? : mardi 3 mars 2020 13:57 ? : users at lists.scilab.org Objet : Re: [Scilab-users] Context error in Xcos Scilab 6.1.0 Le 02/03/2020 ? 10:17, Cl?ment David a ?crit : Hello Pierre, Samuel, First, did you opened a bug on that issue? Second, to me, the bug is located on the script2var() function which resolves the context and output a struct of `variable=value` that are defined for the diagram (and its parents). For example, when I explicitly define A=100 in the context, the A variable is found and resolved as 100 in the diagram. However, defining A=50 inside the A.ctx file and using the schema A610.zcos, where the A.ctx file is passed to exec(), failed. Thanks Cl?ment for the indication and the report . Pierre, A solution is available => there . How to install it: * Download and unzip the file. Rename it script2var.sci * Put script2var.sci in its SCI/scicos/macros/scicos_scicos directory * Run the following Scilab code in the console, with some full read/write rights: cd SCI/scicos/macros/scicos_scicos predef clear genlib scicos_scicoslib clear script2var Then things should work for your session and any following ones. If you get some error when running genlib(), it is most probably because you don't have enough rights to overwrite the library with its update. BR Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From perrichon.pierre at wanadoo.fr Tue Mar 3 20:06:23 2020 From: perrichon.pierre at wanadoo.fr (Perrichon) Date: Tue, 3 Mar 2020 20:06:23 +0100 Subject: [Scilab-users] Context error in Xcos Scilab 6.1.0 References: <0e66dc9d-2f68-8446-919b-22125b535294@free.fr> <4bd1d67d-49b8-950e-3bb7-56ebe09d8a5e@free.fr> Message-ID: PS I have full read/write rights on my machine De : Perrichon Envoy? : mardi 3 mars 2020 16:23 ? : 'Users mailing list for Scilab' ; 'Samuel Gougeon' Objet : RE: [Scilab-users] Context error in Xcos Scilab 6.1.0 Hello Samuel : 1. The correct pathname of script2var.sci is rather SCI/modules/scicos/macros/scicos_scicos 2. If I launch your instructions with the correct directory, I get : --> cd SCI/modules/scicos/macros/scicos_scicos ans = "C:\Program Files\scilab-6.1.0\modules\scicos\macros\scicos_scicos" --> predef clear --> genlib scicos_scicoslib genlib : Impossible d'ouvrir le fichier "C:\Program Files\scilab-6.1.0\modules\scicos\macros\scicos_scicos\lib". ans = F --> clear script2var To read you Best regards De : users > De la part de Samuel Gougeon Envoy? : mardi 3 mars 2020 13:57 ? : users at lists.scilab.org Objet : Re: [Scilab-users] Context error in Xcos Scilab 6.1.0 Le 02/03/2020 ? 10:17, Cl?ment David a ?crit : Hello Pierre, Samuel, First, did you opened a bug on that issue? Second, to me, the bug is located on the script2var() function which resolves the context and output a struct of `variable=value` that are defined for the diagram (and its parents). For example, when I explicitly define A=100 in the context, the A variable is found and resolved as 100 in the diagram. However, defining A=50 inside the A.ctx file and using the schema A610.zcos, where the A.ctx file is passed to exec(), failed. Thanks Cl?ment for the indication and the report . Pierre, A solution is available => there . How to install it: * Download and unzip the file. Rename it script2var.sci * Put script2var.sci in its SCI/scicos/macros/scicos_scicos directory * Run the following Scilab code in the console, with some full read/write rights: cd SCI/scicos/macros/scicos_scicos predef clear genlib scicos_scicoslib clear script2var Then things should work for your session and any following ones. If you get some error when running genlib(), it is most probably because you don't have enough rights to overwrite the library with its update. BR Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Tue Mar 3 22:49:16 2020 From: sgougeon at free.fr (Samuel Gougeon) Date: Tue, 3 Mar 2020 22:49:16 +0100 Subject: [Scilab-users] Context error in Xcos Scilab 6.1.0 In-Reply-To: References: <0e66dc9d-2f68-8446-919b-22125b535294@free.fr> <4bd1d67d-49b8-950e-3bb7-56ebe09d8a5e@free.fr> Message-ID: Le 03/03/2020 ? 20:06, Perrichon a ?crit?: > > PS > > I have full read/write rights on my machine > This is the same issue as with Jan for bitget() last week. I never install Scilab in the default directory C:\Program Files\.... I think this is why i do not get this message. If you had strictly no admin rights, you could even not copy the file in its directory. But maybe there is an intermediate level of administration... Sometimes when we put such a copy in a "System" directory, we are prompted for confirmation, while theoretically being full rights admin. One thing is sure: This is a Windows issue, not a Scilab one. I will try installing Scilab in its default directory, and see how Windows can be tuned to accept compiling Scilab libs. Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From chinluh.tan at bytecode-asia.com Wed Mar 4 00:48:57 2020 From: chinluh.tan at bytecode-asia.com (Chin Luh Tan) Date: Wed, 04 Mar 2020 07:48:57 +0800 Subject: [Scilab-users] Context error in Xcos Scilab 6.1.0 In-Reply-To: References: <0e66dc9d-2f68-8446-919b-22125b535294@free.fr> <4bd1d67d-49b8-950e-3bb7-56ebe09d8a5e@free.fr> Message-ID: <170a2cd6e8f.dfb28001175538.5843115524182560433@bytecode-asia.com> hi, sorry to interrupt half way to just give some idea, have you tried to right click on the Scilab and run it as administrator?? I was facing similar issue on write access even I am the admin for win10, local acc, but still I need to run Scilab as admin by? above mentioned method to write to certain folder.? hope this helps. rgds, CL ---- On Wed, 04 Mar 2020 05:49:16 +0800 Samuel Gougeon wrote ---- Le 03/03/2020 ? 20:06, Perrichon a ?crit?: PS I have full read/write rights on my machine This is the same issue as with Jan for bitget() last week. I never install Scilab in the default directory C:\Program Files\.... I think this is why i do not get this message. If you had strictly no admin rights, you could even not copy the file in its directory. But maybe there is an intermediate level of administration... Sometimes when we put such a copy in a "System" directory, we are prompted for confirmation, while theoretically being full rights admin. One thing is sure: This is a Windows issue, not a Scilab one. I will try installing Scilab in its default directory, and see how Windows can be tuned to accept compiling Scilab libs. 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 perrichon.pierre at wanadoo.fr Wed Mar 4 08:54:17 2020 From: perrichon.pierre at wanadoo.fr (Perrichon) Date: Wed, 4 Mar 2020 08:54:17 +0100 Subject: [Scilab-users] Context error in Xcos Scilab 6.1.0 - Bugzilla #16357 Message-ID: Hello Samuel ; I?ve taken into account Chin Luh Tan?s remark to open scilab in administrator mode with a right click on scilab icon : , and run a new time your patch with the replace file ? script2var.sci ? Then --> cd SCI/modules/scicos/macros/scicos_scicos ans = "C:\Program Files\scilab-6.1.0\modules\scicos\macros\scicos_scicos" --> predef clear --> genlib scicos_scicoslib ans = T --> clear script2var Basic and trial tests program are available in Bugzilla #16357. Before the modification : And now Samuel, I let you close the bufgzilla with resolved fix ? Are a merge version foreseen and a nightlybuild , ? When ? Thanks a lot Also thank to Chin Luh Tan for his help. Pierre P. De : users De la part de Samuel Gougeon Envoy? : mardi 3 mars 2020 22:49 ? : 'Users mailing list for Scilab' Objet : Re: [Scilab-users] Context error in Xcos Scilab 6.1.0 Le 03/03/2020 ? 20:06, Perrichon a ?crit : PS I have full read/write rights on my machine This is the same issue as with Jan for bitget() last week. I never install Scilab in the default directory C:\Program Files\.... I think this is why i do not get this message. If you had strictly no admin rights, you could even not copy the file in its directory. But maybe there is an intermediate level of administration... Sometimes when we put such a copy in a "System" directory, we are prompted for confirmation, while theoretically being full rights admin. One thing is sure: This is a Windows issue, not a Scilab one. I will try installing Scilab in its default directory, and see how Windows can be tuned to accept compiling Scilab libs. Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 9760 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.jpg Type: image/jpeg Size: 5448 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.jpg Type: image/jpeg Size: 4216 bytes Desc: not available URL: From jdb61858 at suoox.com Wed Mar 4 09:35:49 2020 From: jdb61858 at suoox.com (RolandB) Date: Wed, 4 Mar 2020 01:35:49 -0700 (MST) Subject: [Scilab-users] Extraction with $ inside brackets together with other elements Message-ID: <1583310949302-0.post@n3.nabble.com> Hi, somehow extraction with $ inside brackets seems not to work as I think it should. plot(sin(0:0.1:2*%pi*0.5)); axes=gca(); axes.zoom_box;// working 0.1147541 -0.9971014 69.73224 0.9913043 -1. 1. axes.zoom_box();// working 0.1147541 -0.9971014 69.73224 0.9913043 -1. 1. axes.zoom_box(1:$);// working 0.1147541 -0.9971014 69.73224 0.9913043 -1. 1. axes.zoom_box([1:4]);// working 0.1147541 -0.9971014 69.73224 0.9913043 axes.zoom_box([1 3 2 4]);// working 0.1147541 69.73224 -0.9971014 0.9913043 axes.zoom_box([1 3 2 4:6]);// working 0.1147541 69.73224 -0.9971014 0.9913043 -1. 1. axes.zoom_box([1 3 2 4:$]);// not working Undefined operation for the given operands. check or define function %s_c_ip for overloading. It seems that the $ symbol does only work if it is not combined with other vector elements that are not directly dependent on it. Is this how it is intended? Should it be changed? Could it be changed? Is there another way to do what I want to do without having to first check the size and assign it to a variable that I would use instead of the dollar symbol? I know, zoom_box is always a 6 element vector. I wanted to use the extraction on data_bounds, which does not always have 6 elements, hence the use of 4:$ after 1 3 2. Regards, Roland -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From j-lan at online.no Wed Mar 4 10:15:03 2020 From: j-lan at online.no (=?UTF-8?Q?Jan_=c3=85ge_Langeland?=) Date: Wed, 4 Mar 2020 10:15:03 +0100 Subject: [Scilab-users] Context error in Xcos Scilab 6.1.0 In-Reply-To: <170a2cd6e8f.dfb28001175538.5843115524182560433@bytecode-asia.com> References: <0e66dc9d-2f68-8446-919b-22125b535294@free.fr> <4bd1d67d-49b8-950e-3bb7-56ebe09d8a5e@free.fr> <170a2cd6e8f.dfb28001175538.5843115524182560433@bytecode-asia.com> Message-ID: <2fac63d6-6c24-4bda-03d0-858b26368a8e@online.no> Yes! Thank you. J? On 2020-03-04 0:48 AM, Chin Luh Tan wrote: > hi, sorry to interrupt half way to just give some idea, have you tried > to right click on the Scilab and run it as administrator? > > I was facing similar issue on write access even I am the admin for > win10, local acc, but still I need to run Scilab as admin by? above > mentioned method to write to certain folder. > > hope this helps. > > rgds, > CL > > > ---- On Wed, 04 Mar 2020 05:49:16 +0800 *Samuel Gougeon > * wrote ---- > > Le 03/03/2020 ? 20:06, Perrichon a ?crit?: > > PS > > I have full read/write rights on my machine > > This is the same issue as with Jan for bitget() last week. > I never install Scilab in the default directory C:\Program Files\.... > I think this is why i do not get this message. > > If you had strictly no admin rights, you could even not copy the > file in its directory. > But maybe there is an intermediate level of administration... > Sometimes when we put such a copy in a "System" directory, we are > prompted for confirmation, > while theoretically being full rights admin. > > One thing is sure: This is a Windows issue, not a Scilab one. > > I will try installing Scilab in its default directory, and see how > Windows can be tuned to accept compiling Scilab libs. > > Samuel > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > > > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdb61858 at suoox.com Wed Mar 4 10:49:51 2020 From: jdb61858 at suoox.com (RolandB) Date: Wed, 4 Mar 2020 02:49:51 -0700 (MST) Subject: [Scilab-users] Extraction with $ inside brackets together with other elements In-Reply-To: <1583310949302-0.post@n3.nabble.com> References: <1583310949302-0.post@n3.nabble.com> Message-ID: <1583315391210-0.post@n3.nabble.com> Hi, I found bug 11021 , which is about this issue. Seems it's already known and not easily fixable. Regards, Roland -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From perrichon.pierre at wanadoo.fr Wed Mar 4 11:05:05 2020 From: perrichon.pierre at wanadoo.fr (Perrichon) Date: Wed, 4 Mar 2020 11:05:05 +0100 Subject: [Scilab-users] Scilab 6.1.0 - Benchmark time test terribly worrisome - ratio 20 with Scilab 6.1.0 and scilab 5.5.2 - bugzilla 16359 Message-ID: Hello Cl?ment, As you requested, see bugzilla #16359 Best regards Pierre P. De : Cl?ment David Envoy? : lundi 2 mars 2020 12:25 ? : Perrichon ; 'Users mailing list for Scilab' Cc : Cl?ment David Objet : RE: [Scilab-users] Xcos 6.1.0 - benchmark time test Hello Pierre, Thanks for the numbers, I will try to describe what can be down to work around the time to results. >From when you start the simulation to the first scope popup, the schema is converted to a list of functions to be called in a specific order and passed to a solver that will iterate on time to ?run? the simulation. There might be a difference between Scilab 5 and Scilab 6 as this transformation is written using the Scilab language. It is the 5s to 95s ratio. While the simulation is running, each block?s simulation function is called a number of times. The solver/simulator/function API did not change between Scilab 5 and Scilab 6, this should perform the same way. However, some functions, especially sciblk2 and sciblk4 are wrappers from C to Scilab functions and have been re-written to behave very differently. It is the 253s (258-5) to 4258s (4353-95) ratio (lower ratio but much more impact). Could you please file a bug with some representative example (same number of blocks, similar Scilab function) for further investigation ? Note: having ?costly? sciblk2 and sciblk4 also highly depends on your schema, for example having them on a continuous loop will make the solver call them on each timestep. Regards, -- Cl?ment From: Perrichon > Sent: Monday, March 2, 2020 11:09 AM To: 'Users mailing list for Scilab' >; Cl?ment David > Subject: RE: [Scilab-users] Xcos 6.1.0 - benchmark time test Hello Cl?ment, Yes, I have some function blocks and expression blocks. Must I understand that I have to write CBLOCK for scilab function or scilab expression or both ? Here are other results for a more complex project name PELT1 Time request : 100 s Results : Xcos Scilab 5.5.2 : Dur?e de la simulation : 258.3 s Xcos Sciab 6.1.0 : Dur?e de la simulation : 4353.4 s So the ratio is 16.8 for PELT1 Other information : Scilab 5.5.2 : time between click go and first scope on the screen = 5 s Scilab 6.1.0 : time between click go and first scope on the screen = 95 s Ratio=19 and I also have other projects more complex Pelt1 is for 1 needle (2 positonning loop) Perlt6 for 6 !!! (7 positonning loop) BR De : users > De la part de Cl?ment David Envoy? : vendredi 28 f?vrier 2020 10:10 ? : Users mailing list for Scilab > Objet : Re: [Scilab-users] Xcos 6.1.0 - benchmark time test Hello Pierre, Are you using a block with its simulation function implemented in Scilab? Any C/C++ implemented block might perform the same at simulation time. In 6.0.2, implementing Xcos blocks using the Scilab language had some performance issues. In 6.1.0, I tried to speed up things a little bit by reusing some allocated data structure during simulation time [1] ; more work might still be needed here. [1]: http://cgit.scilab.org/scilab/commit/?id=bfe4f25275dc0d889817d10b63e10c9a064 1ef32 Regards, -- Cl?ment From: users > On Behalf Of Perrichon Sent: Friday, February 28, 2020 8:51 AM To: 'Users mailing list for Scilab' > Subject: [Scilab-users] Xcos 6.1.0 - benchmark time test Hello, Here I test a PELTON basic algorithm under xcos, and record with tic-toc the simulation real time. These programs have been set for 120 s (scope) Results : Xcos Scilab 5.5.2 : Dur?e de la simulation : 45.4 s Xcos Sciab 6.1.0 : Dur?e de la simulation : 65.2 s So the ratio is 1.44 for a basic sheme Any explaination ? Can that be improved ? BR -------------- next part -------------- An HTML attachment was scrubbed... URL: From f.s.farimani at gmail.com Fri Mar 6 14:31:40 2020 From: f.s.farimani at gmail.com (farimani) Date: Fri, 6 Mar 2020 06:31:40 -0700 (MST) Subject: [Scilab-users] Where is the best place for Scilab - xcos / ScicosLab - scicos questions and bug report? In-Reply-To: <1571130392121-0.post@n3.nabble.com> References: <1550825509208-0.post@n3.nabble.com> <1571130392121-0.post@n3.nabble.com> Message-ID: <1583501500539-0.post@n3.nabble.com> There are more StackExchange forums where Scilab is quite popular: - math.stackexchange.com newest questions - stats.stackexchange.com newest questions - scicomp.stackexchange.com newest questions - dsp.stackexchange.com newest questions - electronics.stackexchange.com newest questions ----- Foad Sojoodi Farimani Twitter https://twitter.com/fsfarimani LinkedIn https://www.linkedin.com/in/fsfarimani/ -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From kopac.jakub at gmail.com Fri Mar 6 19:31:15 2020 From: kopac.jakub at gmail.com (kjubo) Date: Fri, 6 Mar 2020 11:31:15 -0700 (MST) Subject: [Scilab-users] isreal question Message-ID: <1583519475010-0.post@n3.nabble.com> Dear all, consider this code: ==start of code clc clear a3 = 1 a2 = -1 a1 = 0.106865 a0 = -0.002212 mode(0) sol = roots([a3 a2 a1 a0]) isreal(sol(1)) isreal(sol(2)) isreal(sol(3)) ==end of code i get this print in console: sol = 0.8816333 0.0907062 0.0276605 ans = F ans = F ans = F I do not understand, why the isreal return false flag, if all roots are real with no imaginary part. I am missing something? Or it is bug? using Scilab 6.0.2 x64 thank you BR J.K. -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From stephane.mottelet at utc.fr Fri Mar 6 20:10:53 2020 From: stephane.mottelet at utc.fr (=?utf-8?Q?St=C3=A9phane_Mottelet?=) Date: Fri, 6 Mar 2020 20:10:53 +0100 Subject: [Scilab-users] isreal question In-Reply-To: <1583519475010-0.post@n3.nabble.com> References: <1583519475010-0.post@n3.nabble.com> Message-ID: <506C8935-0C7D-47BC-B293-6D664AB85CC9@utc.fr> Hello, This has been fixed in Scilab 6.1. S. > Le 6 mars 2020 ? 19:31, kjubo a ?crit : > > ?Dear all, > > consider this code: > > ==start of code > clc > clear > > a3 = 1 > a2 = -1 > a1 = 0.106865 > a0 = -0.002212 > mode(0) > sol = roots([a3 a2 a1 a0]) > isreal(sol(1)) > isreal(sol(2)) > isreal(sol(3)) > ==end of code > > i get this print in console: > > sol = > > 0.8816333 > 0.0907062 > 0.0276605 > ans = > > F > ans = > > F > ans = > > F > > I do not understand, why the isreal return false flag, if all roots are real > with no imaginary part. > > I am missing something? Or it is bug? > > using Scilab 6.0.2 x64 > > thank you > > BR > > J.K. > > > > -- > Sent from: https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html > _______________________________________________ > users mailing list > users at lists.scilab.org > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users From sgougeon at free.fr Fri Mar 6 21:51:33 2020 From: sgougeon at free.fr (Samuel Gougeon) Date: Fri, 6 Mar 2020 21:51:33 +0100 Subject: [Scilab-users] isreal question In-Reply-To: <1583519475010-0.post@n3.nabble.com> References: <1583519475010-0.post@n3.nabble.com> Message-ID: <0026757c-2b7d-fa02-cc6e-8a688b951073@free.fr> Le 06/03/2020 ? 19:31, kjubo a ?crit?: > Dear all, > > consider this code: > > ==start of code > clc > clear > > a3 = 1 > a2 = -1 > a1 = 0.106865 > a0 = -0.002212 > mode(0) > sol = roots([a3 a2 a1 a0]) > isreal(sol(1)) > isreal(sol(2)) > isreal(sol(3)) > ==end of code > > i get this print in console: > > sol = > > 0.8816333 > 0.0907062 > 0.0276605 > ans = > > F > ans = > > F > ans = > > F > > I do not understand, why the isreal return false flag, if all roots are real > with no imaginary part. > > I am missing something? Or it is bug? isreal() tests the encoding as complex, not the mathematical realness. If you wish to test the realness, then you have to use isreal(x, 0) Then, isreal(,0) still looks awkward, because we expect an element-wise answer, while only one scalar boolean is returned when x is a vector or a matrix. Samuel From antoine.monmayrant at laas.fr Sun Mar 8 09:51:06 2020 From: antoine.monmayrant at laas.fr (Antoine Monmayrant) Date: Sun, 08 Mar 2020 09:51:06 +0100 Subject: [Scilab-users] =?utf-8?q?scilab_6=2E1_does_not_start_on_linux_ubu?= =?utf-8?q?ntu_19=2E04__64bits?= Message-ID: <114c-5e64b200-21-f270400@85644651> Hello, The latest scilab does not work on ?linux ubuntu 19.04 64bits: tar -xvf scilab-6.1.0.bin.linux-x86_64.tar.gz ./scilab-6.1.0/bin/scilab scilab-bin: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory On the same machine, a fresh install of 6.0.2 works OK. Antoine ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From antoine.monmayrant at laas.fr Sun Mar 8 10:17:22 2020 From: antoine.monmayrant at laas.fr (Antoine Monmayrant) Date: Sun, 08 Mar 2020 10:17:22 +0100 Subject: [Scilab-users] =?utf-8?q?Which_module_to_use_for_hassle-free_imag?= =?utf-8?q?e_processing_with_scilab_=3F?= Message-ID: <2be7-5e64b800-b-3486e200@24161703> Hi all, This mail might sound like a rant, but it is an honest question: which image processing toolbox is usable with scilab and actively maintained? I tried many of them and honestly I did not find one that is just working, easy to instal and that can be installed and used reliably on different platforms: - IPCV : the installation is quite difficult (at least under linux). I just installed it under ubuntu 19.04 and it required manual installation of dependencies (apt install ...) and a patch. Some functions are half documented and in fact not implemented (imhoughc for example). I also had trouble in the past where the install proved impossible during several months on some OSes I use at work (can't remember which flavour of linux or windows it was). - scicv: installs without any issue and as reported by Samuel ( http://forge.scilab.org/index.php/p/scicv/issues/1944/ http://forge.scilab.org/index.php/p/scicv/issues/1946/ ), overwrites 'write' and 'read' which breaks many native functions in scilab together with other useful modules (ie uman). This is a blocking issue that has not been fixed in the past 6 months. Moreover, many opencv functions are not available and it is not clear how to access them. - sip : I used it at some point but it seems that it's no longer supported. Is this the case? - many others, like sip which have not been updated for years (IPT, SIVP...) Well, it's a bit of a mess and I am a bit lost. Any of you have some piece of advice on which toolbox I should invest into and how I can? help improve this situation? Thanks in advance, Antoine ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Sun Mar 8 14:10:07 2020 From: sgougeon at free.fr (Samuel Gougeon) Date: Sun, 8 Mar 2020 14:10:07 +0100 Subject: [Scilab-users] scilab 6.1 does not start on linux ubuntu 19.04 64bits In-Reply-To: <114c-5e64b200-21-f270400@85644651> References: <114c-5e64b200-21-f270400@85644651> Message-ID: <65f62ca1-2361-a337-de98-027d8aaadfce@free.fr> Hello Le 08/03/2020 ? 09:51, Antoine Monmayrant a ?crit?: > Hello, > > The latest scilab does not work on ?linux ubuntu 19.04 64bits: > > tar -xvf scilab-6.1.0.bin.linux-x86_64.tar.gz > ./scilab-6.1.0/bin/scilab > scilab-bin: error while loading shared libraries: libtinfo.so.5: > cannot open shared object file: No such file or directory I have got the same error with the master on Fedora 24, a few days before the release. I did not try with the 6.1.0 official. Samuel From sgougeon at free.fr Sun Mar 8 14:35:21 2020 From: sgougeon at free.fr (Samuel Gougeon) Date: Sun, 8 Mar 2020 14:35:21 +0100 Subject: [Scilab-users] Which module to use for hassle-free image processing with scilab ? In-Reply-To: <2be7-5e64b800-b-3486e200@24161703> References: <2be7-5e64b800-b-3486e200@24161703> Message-ID: <00eefdbe-d488-e9ea-221d-6fa329e89ce1@free.fr> Le 08/03/2020 ? 10:17, Antoine Monmayrant a ?crit?: > Hi all, > > This mail might sound like a rant, but it is an honest question: which > image processing toolbox is usable with scilab and actively maintained? > > I tried many of them and honestly I did not find one that is just > working, easy to instal and that can be installed and used reliably on > different platforms: > > - IPCV : the installation is quite difficult (at least under linux). I > just installed it under ubuntu 19.04 and it required manual > installation of dependencies (apt install ...) and a patch. Some > functions are half documented and in fact not implemented (imhoughc > for example). I also had trouble in the past where the install proved > impossible during several months on some OSes I use at work (can't > remember which flavour of linux or windows it was). > > - scicv: installs without any issue and as reported by Samuel ( > http://forge.scilab.org/index.php/p/scicv/issues/1944/ > http://forge.scilab.org/index.php/p/scicv/issues/1946/ ), overwrites > 'write' and 'read' which breaks many native functions in scilab > together with other useful modules (ie uman). Actually, this issue was first reported 2 years ago , as ATOMS comments. And, indeed, no progress since then. By the way, as far as i could see, scicv is *not* open source. Regards Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From chinluh.tan at bytecode-asia.com Sun Mar 8 14:48:35 2020 From: chinluh.tan at bytecode-asia.com (Chin Luh Tan) Date: Sun, 08 Mar 2020 21:48:35 +0800 Subject: [Scilab-users] Which module to use for hassle-free image processing with scilab ? In-Reply-To: <2be7-5e64b800-b-3486e200@24161703> References: <2be7-5e64b800-b-3486e200@24161703> Message-ID: <170ba6793cf.f621739c608622.9132414223650921075@bytecode-asia.com> Hi?Antoine, This is a very valid point and I afraid to say that there will not be any absolute answer for this question. I encounter the very same issue with you 10 years back when I need to replace Matlab with Scilab especially in Image Processing and Neural Network domain. I came across SIP, which I believe it was one of the earliest Image Processing module for Scilab, but if I remember correctly, it was only for much older version of Scilab and only for linux platform. Then the SIVP toolbox appeared from China Yearly Scilab Module competition back then and it was a very first module based on OPENCV library. However, it did not cover much functions such as morphology. By then, IPD released to cover these missing functions. The combination of these 2 modules under Scilab 5.x version could cover most what I needed during that time. (Initial version if IPD ridding on top of SIVP to use the OPENCV lib, after that it maintained its own lib) However, there are some issues with this method (using 2 modules together), both modules were written in very different way. SIVP very much following Matlab syntax, while IPD is very "computer science" way. For example, function reading an image into SIVP is "imread", IPD is "ReadImage". Also, the IPD will load a lot of global variable into workspace which is not in my favor. Then I tried to work on SIVP and add in some functionalities and tried to contact the author but no reply from him. In return, some US company approached us and would like to "buy" the enhanced version. However, I insist to remained it as OSS and we came out with some other collaboration form and re-brand it to AIVP (Advance Image and Video Processing). The module was not released in public that time. The US company gone after a few years, and I decided to make the AIVP public, the first thing I did is to make it Scilab 6 compatible, and release it with the new name, and this is how IPCV born. IPCV is currently independent module, using OPENCV 4.1.2. Half of the functions are from SIVP, others are newly added via either Scilab functions or OpenCV lib. Each of the function which call the OpenCV lib will need to have a C/C++ gateway in which it will call the OpenCV lib. In order to make the module run in an OS, the OpenCV libs are required for that OS, for windows, it is pretty simple. For Linux, if we were to package it for all Linux distro, I guess there will be a lot of dependencies. (unless we restrict the number of libs used, then the packaging is more likely) The source codes of IPCV are published in github https://github.com/tanchinluh/IPCV, infact we welcome anyone who wish to help in improving this module. There are a lot of fields which could be improve, I name a few: 1. Convert the gateway to use new Scilab 6 gateway. (for future release) 2. To help package the module for all Linux (despite the size) , or any other suggestion welcome. 3. To build extra functions in Image processing using the gateway. 4. Documentation There are still a lot of half cooked functions in the module, which really need contributions from any of us here. It is hard for a module to survived in OSS world, w/o much support from the community. After all, If we were to launch a kickstarter project for IPCV, would anyone back us? ? Have a nice day! Regards, Chin Luh (IPCV Dev) ? ---- On Sun, 08 Mar 2020 17:17:22 +0800 Antoine Monmayrant wrote ---- Hi all, This mail might sound like a rant, but it is an honest question: which image processing toolbox is usable with scilab and actively maintained? I tried many of them and honestly I did not find one that is just working, easy to instal and that can be installed and used reliably on different platforms: - IPCV : the installation is quite difficult (at least under linux). I just installed it under ubuntu 19.04 and it required manual installation of dependencies (apt install ...) and a patch. Some functions are half documented and in fact not implemented (imhoughc for example). I also had trouble in the past where the install proved impossible during several months on some OSes I use at work (can't remember which flavour of linux or windows it was). - scicv: installs without any issue and as reported by Samuel ( http://forge.scilab.org/index.php/p/scicv/issues/1944/ http://forge.scilab.org/index.php/p/scicv/issues/1946/ ), overwrites 'write' and 'read' which breaks many native functions in scilab together with other useful modules (ie uman). This is a blocking issue that has not been fixed in the past 6 months. Moreover, many opencv functions are not available and it is not clear how to access them. - sip : I used it at some point but it seems that it's no longer supported. Is this the case? - many others, like sip which have not been updated for years (IPT, SIVP...) Well, it's a bit of a mess and I am a bit lost. Any of you have some piece of advice on which toolbox I should invest into and how I can? help improve this situation? Thanks in advance, Antoine ? _______________________________________________ users mailing list mailto: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 Sun Mar 8 20:08:31 2020 From: p.muehlmann at gmail.com (P M) Date: Sun, 8 Mar 2020 20:08:31 +0100 Subject: [Scilab-users] Which module to use for hassle-free image processing with scilab ? In-Reply-To: <170ba6793cf.f621739c608622.9132414223650921075@bytecode-asia.com> References: <2be7-5e64b800-b-3486e200@24161703> <170ba6793cf.f621739c608622.9132414223650921075@bytecode-asia.com> Message-ID: Hi Chin Luh, thank you very much for the historical insight. I've been working with this US-company and AIVP for 2 or 3 years...interesting to see how it is all connected. Best regards, Philipp Am So., 8. M?rz 2020 um 14:49 Uhr schrieb Chin Luh Tan < chinluh.tan at bytecode-asia.com>: > Hi Antoine, > > This is a very valid point and I afraid to say that there will not be any > absolute answer for this question. > > I encounter the very same issue with you 10 years back when I need to > replace Matlab with Scilab especially in Image Processing and Neural > Network domain. > > I came across SIP, which I believe it was one of the earliest Image > Processing module for Scilab, but if I remember correctly, it was only for > much older version of Scilab and only for linux platform. > > Then the SIVP toolbox appeared from China Yearly Scilab Module competition > back then and it was a very first module based on OPENCV library. However, > it did not cover much functions such as morphology. By then, IPD released > to cover these missing functions. The combination of these 2 modules under > Scilab 5.x version could cover most what I needed during that time. > (Initial version if IPD ridding on top of SIVP to use the OPENCV lib, after > that it maintained its own lib) > > However, there are some issues with this method (using 2 modules > together), both modules were written in very different way. SIVP very much > following Matlab syntax, while IPD is very "computer science" way. For > example, function reading an image into SIVP is "imread", IPD is > "ReadImage". Also, the IPD will load a lot of global variable into > workspace which is not in my favor. > > Then I tried to work on SIVP and add in some functionalities and tried to > contact the author but no reply from him. In return, some US company > approached us and would like to "buy" the enhanced version. However, I > insist to remained it as OSS and we came out with some other collaboration > form and re-brand it to AIVP (Advance Image and Video Processing). The > module was not released in public that time. > > The US company gone after a few years, and I decided to make the AIVP > public, the first thing I did is to make it Scilab 6 compatible, and > release it with the new name, and this is how IPCV born. > > IPCV is currently independent module, using OPENCV 4.1.2. Half of the > functions are from SIVP, others are newly added via either Scilab functions > or OpenCV lib. Each of the function which call the OpenCV lib will need to > have a C/C++ gateway in which it will call the OpenCV lib. > > In order to make the module run in an OS, the OpenCV libs are required for > that OS, for windows, it is pretty simple. For Linux, if we were to package > it for all Linux distro, I guess there will be a lot of dependencies. > (unless we restrict the number of libs used, then the packaging is more > likely) > > The source codes of IPCV are published in github > https://github.com/tanchinluh/IPCV, infact we welcome anyone who wish to > help in improving this module. There are a lot of fields which could be > improve, I name a few: > 1. Convert the gateway to use new Scilab 6 gateway. (for future release) > 2. To help package the module for all Linux (despite the size) , or any > other suggestion welcome. > 3. To build extra functions in Image processing using the gateway. > 4. Documentation > > There are still a lot of half cooked functions in the module, which really > need contributions from any of us here. It is hard for a module to survived > in OSS world, w/o much support from the community. > > After all, If we were to launch a kickstarter project for IPCV, would > anyone back us? ? > > Have a nice day! > > Regards, > Chin Luh (IPCV Dev) > > > > > > > > > > > > > ---- On Sun, 08 Mar 2020 17:17:22 +0800 *Antoine Monmayrant > >* wrote ---- > > Hi all, > > This mail might sound like a rant, but it is an honest question: which > image processing toolbox is usable with scilab and actively maintained? > > I tried many of them and honestly I did not find one that is just working, > easy to instal and that can be installed and used reliably on different > platforms: > > - IPCV : the installation is quite difficult (at least under linux). I > just installed it under ubuntu 19.04 and it required manual installation of > dependencies (apt install ...) and a patch. Some functions are half > documented and in fact not implemented (imhoughc for example). I also had > trouble in the past where the install proved impossible during several > months on some OSes I use at work (can't remember which flavour of linux or > windows it was). > > - scicv: installs without any issue and as reported by Samuel ( > http://forge.scilab.org/index.php/p/scicv/issues/1944/ > http://forge.scilab.org/index.php/p/scicv/issues/1946/ ), overwrites > 'write' and 'read' which breaks many native functions in scilab together > with other useful modules (ie uman). This is a blocking issue that has not > been fixed in the past 6 months. Moreover, many opencv functions are not > available and it is not clear how to access them. > > - sip : I used it at some point but it seems that it's no longer > supported. Is this the case? > > - many others, like sip which have not been updated for years (IPT, > SIVP...) > > Well, it's a bit of a mess and I am a bit lost. > Any of you have some piece of advice on which toolbox I should invest into > and how I can help improve this situation? > > Thanks in advance, > > Antoine > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From amonmayr at laas.fr Mon Mar 9 09:58:39 2020 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Mon, 09 Mar 2020 09:58:39 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ICBXaGljaCBtb2R1bGUgdG8g?= =?utf-8?q?use_for_hassle-free_image_processing_with_scilab_=3F?= In-Reply-To: <170ba6793cf.f621739c608622.9132414223650921075@bytecode-asia.com> Message-ID: <21c1-5e660500-11-687d2200@235970351> Hello Chin Luh, Thanks for this detailled answer. For me, the biggest issue with IPCV is the difficulty of getting the install right and to ensure it will work on a given platform. (anecdote time: I just received an email from a colleague asking for help to install IPCV on his computer because he got lost at some point and cannot make sense of the error message). Is there any significant difference in the underlying libraries and packaging strategies that make scicv way easier to install? Could some change be made in the packaging of IPCV to get the same install experience? Or is the brute for approach (ie a case on the platform and then a big case on the distro if the platform is linux) this only viable approach? I am by no mean an expert on this kind of things, I can just try to help make it work on the platforms I use (mainly the ubuntu LTS of the moment and the latest Windows). Cheers, Antoine Le Dimanche, Mars 08, 2020 14:48 CET, Chin Luh Tan a ?crit: ??Hi?Antoine,?This is a very valid point and I afraid to say that there will not be any absolute answer for this question.?I encounter the very same issue with you 10 years back when I need to replace Matlab with Scilab especially in Image Processing and Neural Network domain.?I came across SIP, which I believe it was one of the earliest Image Processing module for Scilab, but if I remember correctly, it was only for much older version of Scilab and only for linux platform.?Then the SIVP toolbox appeared from China Yearly Scilab Module competition back then and it was a very first module based on OPENCV library. However, it did not cover much functions such as morphology. By then, IPD released to cover these missing functions. The combination of these 2 modules under Scilab 5.x version could cover most what I needed during that time. (Initial version if IPD ridding on top of SIVP to use the OPENCV lib, after that it maintained its own lib)?However, there are some issues with this method (using 2 modules together), both modules were written in very different way. SIVP very much following Matlab syntax, while IPD is very "computer science" way. For example, function reading an image into SIVP is "imread", IPD is "ReadImage". Also, the IPD will load a lot of global variable into workspace which is not in my favor.?Then I tried to work on SIVP and add in some functionalities and tried to contact the author but no reply from him. In return, some US company approached us and would like to "buy" the enhanced version. However, I insist to remained it as OSS and we came out with some other collaboration form and re-brand it to AIVP (Advance Image and Video Processing). The module was not released in public that time.?The US company gone after a few years, and I decided to make the AIVP public, the first thing I did is to make it Scilab 6 compatible, and release it with the new name, and this is how IPCV born.?IPCV is currently independent module, using OPENCV 4.1.2. Half of the functions are from SIVP, others are newly added via either Scilab functions or OpenCV lib. Each of the function which call the OpenCV lib will need to have a C/C++ gateway in which it will call the OpenCV lib.?In order to make the module run in an OS, the OpenCV libs are required for that OS, for windows, it is pretty simple. For Linux, if we were to package it for all Linux distro, I guess there will be a lot of dependencies. (unless we restrict the number of libs used, then the packaging is more likely)?The source codes of IPCV are published in github https://github.com/tanchinluh/IPCV, infact we welcome anyone who wish to help in improving this module. There are a lot of fields which could be improve, I name a few:1. Convert the gateway to use new Scilab 6 gateway. (for future release)2. To help package the module for all Linux (despite the size) , or any other suggestion welcome.3. To build extra functions in Image processing using the gateway.4. Documentation?There are still a lot of half cooked functions in the module, which really need contributions from any of us here. It is hard for a module to survived in OSS world, w/o much support from the community.?After all, If we were to launch a kickstarter project for IPCV, would anyone back us? ??Have a nice day!?Regards,Chin Luh (IPCV Dev)????????????---- On Sun, 08 Mar 2020 17:17:22 +0800 Antoine Monmayrant wrote ----?Hi all, This mail might sound like a rant, but it is an honest question: which image processing toolbox is usable with scilab and actively maintained? I tried many of them and honestly I did not find one that is just working, easy to instal and that can be installed and used reliably on different platforms: - IPCV : the installation is quite difficult (at least under linux). I just installed it under ubuntu 19.04 and it required manual installation of dependencies (apt install ...) and a patch. Some functions are half documented and in fact not implemented (imhoughc for example). I also had trouble in the past where the install proved impossible during several months on some OSes I use at work (can't remember which flavour of linux or windows it was). - scicv: installs without any issue and as reported by Samuel ( http://forge.scilab.org/index.php/p/scicv/issues/1944/ http://forge.scilab.org/index.php/p/scicv/issues/1946/ ), overwrites 'write' and 'read' which breaks many native functions in scilab together with other useful modules (ie uman). This is a blocking issue that has not been fixed in the past 6 months. Moreover, many opencv functions are not available and it is not clear how to access them. - sip : I used it at some point but it seems that it's no longer supported. Is this the case? - many others, like sip which have not been updated for years (IPT, SIVP...) Well, it's a bit of a mess and I am a bit lost. Any of you have some piece of advice on which toolbox I should invest into and how I can? help improve this situation? Thanks in advance, Antoine ? _______________________________________________ users mailing list users at lists.scilab.org http://lists.scilab.org/mailman/listinfo/users? ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From fmiyara at fceia.unr.edu.ar Mon Mar 9 10:36:45 2020 From: fmiyara at fceia.unr.edu.ar (Federico Miyara) Date: Mon, 9 Mar 2020 06:36:45 -0300 Subject: [Scilab-users] problem with matrix of polynomials Message-ID: <2d3bb505-2b0a-d026-58a2-b5e9ede470bf@fceia.unr.edu.ar> Dear all, I wonder if the inversion of a matrix of polynomials is working properly. I have the following code from the direct resolution of a two-section constant resistance electrical network:: // Data R1 = 600; R2 = 600; R3 = 600; R4 = 600; R5 = 10070; R6 = 2774; R7 = 36; R8 = 130; R9 = 600; L1 = 2.65; L2 = 0.0318; L3 = 0.00669; L4 = 0.00795; C1 = 18.4e-9; C2 = 22.1e-9; C3 = 7.3e-6; C4 = 88.4e-9; // Series and parallel impedances Z1 = R7 + L3*%s + 1/(C3*%s); Z2 = 1/(1/R5 + 1/(L1*%s) + C1*%s); Z3 = R8 + L4*%s + 1/(C4*%s); Z4 = 1/(1/R6 + 1/(L2*%s) + C2*%s); // System matrix (node potentials) A = [ 1/R1+1/Z1+1/R2, -1/R2, 0, 0; ... -1/R2, 1/R2+1/Z2+1/R3+1/Z4, -1/R3, -1/Z4; ... 0, -1/R3, 1/R3+1/Z3+1/R4, -1/R4; ... ?? ?? 0, -1/Z4, -1/R4, 1/R4+1/Z4+1/R9]; The code goes further, but the point is I need to compute inv(A). When multiplied by A, i.e. A*inv(A) we should get eye(A). Of course, since both A and inv(A) are rationals, we don't get exactly eye(A), but we should anyway get rationals very close to exact num/den cancellation on the diagonal, and orders of magnitude less outside the diagonal. However, it may be a bit tricky to recognize these things in a cluttered output such s the console's, so I attempted replacing values horner(A*inv(A), %i*2*%pi*1000) I get the following ? -894.25452 - 52.256219i?? 22.488572 - 53.503625i?? 13.243845 - 53.503625i?? 13.247333 - 53.503625i ?? 55.248428 - 45.072952i? -905.16326 + 55.026768i? -882.83336 - 2.1937054i? -882.84581 - 2.1939413i ?? 22.907079 - 0.7699342i?? 877.83532 - 1.5398684i?? 855.90863 + 56.312642i?? 878.89745 - 1.5491077i ? -64.456283 + 100.49087i? -877.84725 + 1.5398684i? -878.89717 + 1.5491052i? -901.87337 + 59.410849i It doesn't resemble eye(A) at all. Now I tried replacing before inverting: B = horner(inv(A), %i*2*%pi*1000); C = inv(B); Now I compute B*C The result is much closer to eye(A): ?? 1.?????????????????????? 2.845D-16??????????????? 0. 0. ? -7.216D-16 + 1.332D-15i?? 1. - 3.886D-16i????????? 1.221D-15i 1.159D-15 + 2.220D-16i ?? 1.249D-16??????????????? 0.?????????????????????? 1. -1.366D-16i ? -2.776D-16??????????????? 3.775D-15 - 1.665D-16i?? 0. 1. A last experiment: I replace in the inverse: D = horner(inv(A), %i*2*%pi*1000); Then, computing B*D yields this completely insane result: ?? 1.039D+09 + 7.084D+08i?? 8.026D+09 + 3.899D+09i?? 8.103D+09 + 3.626D+09i?? 8.038D+09 + 3.900D+09i ?? 4.565D+09 - 7.139D+09i?? 1.425D+11 - 2.222D+10i?? 1.411D+11 - 2.677D+10i?? 1.426D+11 - 2.231D+10i ? -3.751D+08 - 5.719D+08i? -3.656D+08 - 8.904D+09i? -9.535D+08 - 8.891D+09i? -3.712D+08 - 8.916D+09i ?? 5.187D+09 - 6.874D+09i?? 1.429D+11 - 2.215D+10i?? 1.415D+11 - 2.671D+10i?? 1.431D+11 - 2.225D+10i Am I doing anything wrong? Regards, Federico Miyara -------------- next part -------------- An HTML attachment was scrubbed... URL: From Clement.David at esi-group.com Mon Mar 9 10:52:20 2020 From: Clement.David at esi-group.com (=?utf-8?B?Q2zDqW1lbnQgRGF2aWQ=?=) Date: Mon, 9 Mar 2020 09:52:20 +0000 Subject: [Scilab-users] Which module to use for hassle-free image processing with scilab ? In-Reply-To: <2be7-5e64b800-b-3486e200@24161703> References: <2be7-5e64b800-b-3486e200@24161703> Message-ID: Hello Antoine, > - scicv: installs without any issue and as reported by Samuel ( > http://forge.scilab.org/index.php/p/scicv/issues/1944/ > http://forge.scilab.org/index.php/p/scicv/issues/1946/ ), overwrites 'write' and > 'read' which breaks many native functions in scilab together with other useful > modules (ie uman). This is a blocking issue that has not been fixed in the past 6 > months. Moreover, many opencv functions are not available and it is not clear > how to access them. About sciCV, the idea was to use SWIG [1] and OpenCV [2] as an easy to use (and simple to develop) toolbox for manipulating images and videos using Scilab scripts. Here we don't have Scilab scripts at all, just a bunch of SWIG rules to generate the Scilab C gateways from the OpenCV C API. We have a focus on keeping the data in the OpenCV world and "accessing" them from Scilab. The two reported bugs have been fixed in 0.5 (sorry I did not close them) and the latest 0.6 version is built for Scilab 6.1.0 after a customer request. Note: the code is not open-source but SWIG for Scilab and OpenCV are! -- Cl?ment From stephane.mottelet at utc.fr Mon Mar 9 10:57:00 2020 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Mon, 9 Mar 2020 10:57:00 +0100 Subject: [Scilab-users] Which module to use for hassle-free image processing with scilab ? In-Reply-To: References: <2be7-5e64b800-b-3486e200@24161703> Message-ID: <78bb89f3-86d0-17d1-c7d7-f6cca0e3dd41@utc.fr> Hello, Le 09/03/2020 ? 10:52, Cl?ment David a ?crit?: > Hello Antoine, > >> - scicv: installs without any issue and as reported by Samuel ( >> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/forge.scilab.org/index.php/p/scicv/issues/1944/ >> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/forge.scilab.org/index.php/p/scicv/issues/1946/ ), overwrites 'write' and >> 'read' which breaks many native functions in scilab together with other useful >> modules (ie uman). This is a blocking issue that has not been fixed in the past 6 >> months. Moreover, many opencv functions are not available and it is not clear >> how to access them. > About sciCV, the idea was to use SWIG [1] and OpenCV [2] as an easy to use (and simple to develop) toolbox for manipulating images and videos using Scilab scripts. Here we don't have Scilab scripts at all, just a bunch of SWIG rules to generate the Scilab C gateways from the OpenCV C API. We have a focus on keeping the data in the OpenCV world and "accessing" them from Scilab. IMHO this is very confusing for people migrating image processing applications from Matlab (this is my case). For example accessing rgb images directly as (n,m,3) hypermatrices is very handy. S. > > The two reported bugs have been fixed in 0.5 (sorry I did not close them) and the latest 0.6 version is built for Scilab 6.1.0 after a customer request. > > Note: the code is not open-source but SWIG for Scilab and OpenCV are! > > -- > Cl?ment > _______________________________________________ > 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 Clement.David at esi-group.com Mon Mar 9 13:32:42 2020 From: Clement.David at esi-group.com (=?utf-8?B?Q2zDqW1lbnQgRGF2aWQ=?=) Date: Mon, 9 Mar 2020 12:32:42 +0000 Subject: [Scilab-users] Which module to use for hassle-free image processing with scilab ? In-Reply-To: <78bb89f3-86d0-17d1-c7d7-f6cca0e3dd41@utc.fr> References: <2be7-5e64b800-b-3486e200@24161703> <78bb89f3-86d0-17d1-c7d7-f6cca0e3dd41@utc.fr> Message-ID: Hello St?phane, >> We have a focus on keeping the data in the OpenCV world and "accessing" them from Scilab. > > IMHO this is very confusing for people migrating image processing applications > from Matlab (this is my case). For example, accessing rgb images directly as > (n,m,3) hypermatrices are very handy. The extraction/insertion should be handled correctly as well as converting n,m,3 uint8 back to OpenCV Mat images. Do you have a specific code sample that fail? Thanks for your input, -- Cl?ment From sgougeon at free.fr Mon Mar 9 13:36:26 2020 From: sgougeon at free.fr (sgougeon at free.fr) Date: Mon, 9 Mar 2020 13:36:26 +0100 (CET) Subject: [Scilab-users] =?utf-8?q?Re=C2=A0=3A__problem_with_matrix_of_poly?= =?utf-8?q?nomials?= In-Reply-To: <2d3bb505-2b0a-d026-58a2-b5e9ede470bf@fceia.unr.edu.ar> Message-ID: <1349770032.280045122.1583757386978.JavaMail.root@zimbra75-e12.priv.proxad.net> Hello Federico, cond() and rcond() do not accept rationals, but the determinant of A is very close to 0: --> det(A) ans = 3.573D-10 ------------------------ 0.0000027s? +7.433D-10s? This likely explains that the inversion is not reliable. Regards Samuel From stephane.mottelet at utc.fr Mon Mar 9 14:04:12 2020 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Mon, 9 Mar 2020 14:04:12 +0100 Subject: [Scilab-users] =?utf-8?q?Re=C2=A0=3A_problem_with_matrix_of_polyn?= =?utf-8?q?omials?= In-Reply-To: <1349770032.280045122.1583757386978.JavaMail.root@zimbra75-e12.priv.proxad.net> References: <1349770032.280045122.1583757386978.JavaMail.root@zimbra75-e12.priv.proxad.net> Message-ID: <1138b79a-75c5-e485-c8b4-0b10e044b53f@utc.fr> Maybe an inversion made in state-space could me more reliable ? S. Le 09/03/2020 ? 13:36, sgougeon at free.fr a ?crit?: > Hello Federico, > > cond() and rcond() do not accept rationals, but the determinant of A is very close to 0: > --> det(A) > ans = > > 3.573D-10 > ------------------------ > 0.0000027s? +7.433D-10s? > > This likely explains that the inversion is not reliable. > > 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 From amonmayr at laas.fr Mon Mar 9 14:34:08 2020 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Mon, 09 Mar 2020 14:34:08 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ICBXaGljaCBtb2R1bGUgdG8g?= =?utf-8?q?use_for_hassle-free_image_processing_with_scilab_=3F?= In-Reply-To: Message-ID: <2a7c-5e664600-41-260775c0@93357681> Hello Cl?ment, Thanks for your answer. It's still not clear to me whether I should use scicv or not. First, many features are missing and it's not clear to me how I can implement or discover them (hough transforms for example). Is there a list of the opencv functions that you expose through swig and the one that are not implemented? Also, I'm a bit surprised by your statement: Note: the code is not open-source but SWIG for Scilab and OpenCV are!Why is it not open-source? Is this some transient situation due to the way the code was developped (like for a client)? Do you plan to make it open source in the near future? For many reasons and lots of lessons learned the hard way, I don't feel like investing my time on non open-source software... Antoine Le Lundi, Mars 09, 2020 10:52 CET, Cl?ment David a ?crit: ?Hello Antoine, > - scicv: installs without any issue and as reported by Samuel ( > http://forge.scilab.org/index.php/p/scicv/issues/1944/ > http://forge.scilab.org/index.php/p/scicv/issues/1946/ ), overwrites 'write' and > 'read' which breaks many native functions in scilab together with other useful > modules (ie uman). This is a blocking issue that has not been fixed in the past 6 > months. Moreover, many opencv functions are not available and it is not clear > how to access them. About sciCV, the idea was to use SWIG [1] and OpenCV [2] as an easy to use (and simple to develop) toolbox for manipulating images and videos using Scilab scripts. Here we don't have Scilab scripts at all, just a bunch of SWIG rules to generate the Scilab C gateways from the OpenCV C API. We have a focus on keeping the data in the OpenCV world and "accessing" them from Scilab. The two reported bugs have been fixed in 0.5 (sorry I did not close them) and the latest 0.6 version is built for Scilab 6.1.0 after a customer request. Note: the code is not open-source but SWIG for Scilab and OpenCV are! -- Cl?ment _______________________________________________ users mailing list users at lists.scilab.org http://lists.scilab.org/mailman/listinfo/users ? ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From chinluh.tan at bytecode-asia.com Mon Mar 9 15:11:43 2020 From: chinluh.tan at bytecode-asia.com (Chin Luh Tan) Date: Mon, 09 Mar 2020 22:11:43 +0800 Subject: [Scilab-users] =?utf-8?q?Re=C2=A0=3A_problem_with_matrix_of_polyn?= =?utf-8?q?omials?= In-Reply-To: <1138b79a-75c5-e485-c8b4-0b10e044b53f@utc.fr> References: <1349770032.280045122.1583757386978.JavaMail.root@zimbra75-e12.priv.proxad.net> <1138b79a-75c5-e485-c8b4-0b10e044b53f@utc.fr> Message-ID: <170bfa31df1.df4ebe1b18591.9003660211809807661@bytecode-asia.com> initially I thought could it be possible the number is too small (or too large) to be handled? by double?? after trying scaling down the problem, I notice that in Scilab 6.0.2 onwards: --> 2e-20*%i ans? = ?? 0.? in Scilab 5.5.2 -->2e-20*%i ans? = ??? 2.000D-20i? Could this be the issue? thanks. rgds, CL ---- On Mon, 09 Mar 2020 21:04:12 +0800 St?phane Mottelet wrote ---- Maybe an inversion made in state-space could me more reliable ? S. Le 09/03/2020 ? 13:36, mailto:sgougeon at free.fr a ?crit?: > Hello Federico, > > cond() and rcond() do not accept rationals, but the determinant of A is very close to 0: > --> det(A) > ans = > > 3.573D-10 > ------------------------ > 0.0000027s? +7.433D-10s? > > This likely explains that the inversion is not reliable. > > Regards > Samuel > _______________________________________________ > users mailing list > mailto: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 mailto:users at lists.scilab.org http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From chinluh.tan at bytecode-asia.com Mon Mar 9 15:17:29 2020 From: chinluh.tan at bytecode-asia.com (Chin Luh Tan) Date: Mon, 09 Mar 2020 22:17:29 +0800 Subject: [Scilab-users] =?utf-8?b?Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7UmXCoDog?= =?utf-8?q?problem_with_matrix_of_polynomials?= In-Reply-To: <170bfa31df1.df4ebe1b18591.9003660211809807661@bytecode-asia.com> References: <1349770032.280045122.1583757386978.JavaMail.root@zimbra75-e12.priv.proxad.net> <1138b79a-75c5-e485-c8b4-0b10e044b53f@utc.fr> <170bfa31df1.df4ebe1b18591.9003660211809807661@bytecode-asia.com> Message-ID: <170bfa867b2.ae3d700119794.8037106841640869514@bytecode-asia.com> sorry, ignore the previous finding, turn out to be it seems like just a display issue.? However, I think my initial thought of the precision might be the issue? some number are too small (first case) and giving error during computation? thx rgds, CL ---- On Mon, 09 Mar 2020 22:11:43 +0800 Chin Luh Tan wrote ---- initially I thought could it be possible the number is too small (or too large) to be handled? by double?? after trying scaling down the problem, I notice that in Scilab 6.0.2 onwards: --> 2e-20*%i ans? = ?? 0.? in Scilab 5.5.2 -->2e-20*%i ans? = ??? 2.000D-20i? Could this be the issue? thanks. rgds, CL ---- On Mon, 09 Mar 2020 21:04:12 +0800 St?phane Mottelet wrote ---- _______________________________________________ users mailing list users at lists.scilab.org http://lists.scilab.org/mailman/listinfo/users Maybe an inversion made in state-space could me more reliable ? S. Le 09/03/2020 ? 13:36, mailto:sgougeon at free.fr a ?crit?: > Hello Federico, > > cond() and rcond() do not accept rationals, but the determinant of A is very close to 0: > --> det(A) > ans = > > 3.573D-10 > ------------------------ > 0.0000027s? +7.433D-10s? > > This likely explains that the inversion is not reliable. > > Regards > Samuel > _______________________________________________ > users mailing list > mailto: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 mailto:users at lists.scilab.org http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From amonmayr at laas.fr Mon Mar 9 15:20:38 2020 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Mon, 09 Mar 2020 15:20:38 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ID89PT91dGYtOD9xPyBSZcKg?= =?utf-8?q?=3A__problem_with_matrix_of_polynomials?= In-Reply-To: <170bfa31df1.df4ebe1b18591.9003660211809807661@bytecode-asia.com> Message-ID: <4c5c-5e665080-5b-7ae8e900@253433816> Hello, It seems that this value is below %eps==2.2e-16, so I though that once encoded in double the difference between 2e-20 and 0 is too small to be properly taken into account. Am I missing something? Antoine Le Lundi, Mars 09, 2020 15:11 CET, Chin Luh Tan a ?crit: ??initially I thought could it be possible the number is too small (or too large) to be handled? by double???after trying scaling down the problem, I notice that in Scilab 6.0.2 onwards:?--> 2e-20*%ians? =??? 0.??in Scilab 5.5.2?-->2e-20*%ians? =???? 2.000D-20i???Could this be the issue??thanks.?rgds,CL?---- On Mon, 09 Mar 2020 21:04:12 +0800 St?phane Mottelet wrote ----?Maybe an inversion made in state-space could me more reliable ? S. Le 09/03/2020 ? 13:36, sgougeon at free.fr a ?crit?: > Hello Federico, > > cond() and rcond() do not accept rationals, but the determinant of A is very close to 0: > --> det(A) > ans = > > 3.573D-10 > ------------------------ > 0.0000027s? +7.433D-10s? > > This likely explains that the inversion is not reliable. > > 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 _______________________________________________ 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 Mon Mar 9 15:29:16 2020 From: Clement.David at esi-group.com (=?utf-8?B?Q2zDqW1lbnQgRGF2aWQ=?=) Date: Mon, 9 Mar 2020 14:29:16 +0000 Subject: [Scilab-users] ?==?utf-8?q? Which module to use for hassle-free image processing with scilab ? In-Reply-To: <2a7c-5e664600-41-260775c0@93357681> References: <2a7c-5e664600-41-260775c0@93357681> Message-ID: About the feature set, I suggest you take a look at SIVP which is much more complete and target a wider audience. The available functions are the documented ones and we might add more if customers requested more. Currently, this toolbox is used by some customers and we only mapped the feature requested by them to have an associated minimal OpenCV build. It targets customers and we will probably not open-source it as we don?t want to maintain it ?for free?. Again if you want to co-develop, take a look at SIVP ; Chin Luh did a good job and it is open-source ! Regards, Cl?ment From: users On Behalf Of Antoine Monmayrant Sent: Monday, March 9, 2020 2:34 PM To: Users mailing list for Scilab Subject: Re: [Scilab-users] ?==?utf-8?q? Which module to use for hassle-free image processing with scilab ? Hello Cl?ment, Thanks for your answer. It's still not clear to me whether I should use scicv or not. First, many features are missing and it's not clear to me how I can implement or discover them (hough transforms for example). Is there a list of the opencv functions that you expose through swig and the one that are not implemented? Also, I'm a bit surprised by your statement: Note: the code is not open-source but SWIG for Scilab and OpenCV are! Why is it not open-source? Is this some transient situation due to the way the code was developped (like for a client)? Do you plan to make it open source in the near future? For many reasons and lots of lessons learned the hard way, I don't feel like investing my time on non open-source software... Antoine Le Lundi, Mars 09, 2020 10:52 CET, Cl?ment David > a ?crit: Hello Antoine, > - scicv: installs without any issue and as reported by Samuel ( > http://forge.scilab.org/index.php/p/scicv/issues/1944/ > http://forge.scilab.org/index.php/p/scicv/issues/1946/ ), overwrites 'write' and > 'read' which breaks many native functions in scilab together with other useful > modules (ie uman). This is a blocking issue that has not been fixed in the past 6 > months. Moreover, many opencv functions are not available and it is not clear > how to access them. About sciCV, the idea was to use SWIG [1] and OpenCV [2] as an easy to use (and simple to develop) toolbox for manipulating images and videos using Scilab scripts. Here we don't have Scilab scripts at all, just a bunch of SWIG rules to generate the Scilab C gateways from the OpenCV C API. We have a focus on keeping the data in the OpenCV world and "accessing" them from Scilab. The two reported bugs have been fixed in 0.5 (sorry I did not close them) and the latest 0.6 version is built for Scilab 6.1.0 after a customer request. Note: the code is not open-source but SWIG for Scilab and OpenCV are! -- Cl?ment _______________________________________________ users mailing list users at lists.scilab.org http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From amonmayr at laas.fr Mon Mar 9 15:44:15 2020 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Mon, 09 Mar 2020 15:44:15 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ID89PT91dGYtOD9xPyA/PSBX?= =?utf-8?q?hich_module_to_use_for_hassle-free_image_processing_with_scilab?= In-Reply-To: Message-ID: <52f6-5e665600-35-7302ea00@217435952> Hello Cl?ment, Thanks for your answer. I think it clarifies the situation somehow. I still don't get your point of not open-sourcing it and maintaining it "for free". I think it's the other way round: if you open-source it, it might happen that some members of the community contribute to extend it and maintain it "for free". >From the info you gave me, scicv should be avoided by any one not being that particular client of your group. Moreover, scicv is adding noise and confusion to the atoms library. Antoine Le Lundi, Mars 09, 2020 15:29 CET, Cl?ment David a ?crit: ?? About the feature set, I suggest you take a look at SIVP which is much more complete and target a wider audience. The available functions are the documented ones and we might add more if customers requested more. ? Currently, this toolbox is used by some customers and we only mapped the feature requested by them to have an associated minimal OpenCV build. It targets customers and we will probably not open-source it as we don?t want to maintain it ?for free?. Again if you want to co-develop, take a look at SIVP ; Chin Luh did a good job and it is open-source ! ? Regards, ? Cl?ment ? ? From: users On Behalf Of Antoine Monmayrant Sent: Monday, March 9, 2020 2:34 PM To: Users mailing list for Scilab Subject: Re: [Scilab-users] ?==?utf-8?q? Which module to use for hassle-free image processing with scilab ? ? Hello Cl?ment, Thanks for your answer. It's still not clear to me whether I should use scicv or not. First, many features are missing and it's not clear to me how I can implement or discover them (hough transforms for example). Is there a list of the opencv functions that you expose through swig and the one that are not implemented? Also, I'm a bit surprised by your statement: Note: the code is not open-source but SWIG for Scilab and OpenCV are! Why is it not open-source? Is this some transient situation due to the way the code was developped (like for a client)? Do you plan to make it open source in the near future? For many reasons and lots of lessons learned the hard way, I don't feel like investing my time on non open-source software... Antoine Le Lundi, Mars 09, 2020 10:52 CET, Cl?ment David a ?crit: ? Hello Antoine, > - scicv: installs without any issue and as reported by Samuel ( > http://forge.scilab.org/index.php/p/scicv/issues/1944/ > http://forge.scilab.org/index.php/p/scicv/issues/1946/ ), overwrites 'write' and > 'read' which breaks many native functions in scilab together with other useful > modules (ie uman). This is a blocking issue that has not been fixed in the past 6 > months. Moreover, many opencv functions are not available and it is not clear > how to access them. About sciCV, the idea was to use SWIG [1] and OpenCV [2] as an easy to use (and simple to develop) toolbox for manipulating images and videos using Scilab scripts. Here we don't have Scilab scripts at all, just a bunch of SWIG rules to generate the Scilab C gateways from the OpenCV C API. We have a focus on keeping the data in the OpenCV world and "accessing" them from Scilab. The two reported bugs have been fixed in 0.5 (sorry I did not close them) and the latest 0.6 version is built for Scilab 6.1.0 after a customer request. Note: the code is not open-source but SWIG for Scilab and OpenCV are! -- Cl?ment _______________________________________________ users mailing list users at lists.scilab.org http://lists.scilab.org/mailman/listinfo/users ? ? ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From chinluh.tan at bytecode-asia.com Mon Mar 9 16:48:59 2020 From: chinluh.tan at bytecode-asia.com (Chin Luh Tan) Date: Mon, 09 Mar 2020 23:48:59 +0800 Subject: [Scilab-users] =?utf-8?b?Pz0gPT91dGYtOD9xPyBSZcKgOiAgcHJvYmxlbSB3?= =?utf-8?q?ith_matrix_of_polynomials?= In-Reply-To: <4c5c-5e665080-5b-7ae8e900@253433816> References: <4c5c-5e665080-5b-7ae8e900@253433816> Message-ID: <170bffc2b46.d855246737750.4965631307156628552@bytecode-asia.com> Hi,? sorry for this misleading finding, infact I've second message to turn it down. ****************** ignore the previous finding, turn out to be it seems like just a display issue.? However, I think my initial thought of the precision might be the issue? some number are too small (first case) and giving error during computation? ****************** Back to the possible reason of causing this issue when u substitute a value into the %s? into A*inv(A) Assume a = A*inv(A), a(1,1) which suppose to be ~ 1 is :? --> a(1,1) ans? = ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? 1.630D-38 + 1.586D-40s + 4.110D-43s^2 + 1.120D-46s^3 + 1.998D-50s^4 + 3.586D-55s^5? ?? ---------------------------------------------------------------------------? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? ????????????????????? 1.630D-38 + 4.283D-42s + 7.960D-46s^2 the coefficients in numerator and denominator are very small value and with complex number involve, there might be come kind of limitation in the numerical software.? this could be shown if you subs with smaller number:? --> horner(A*inv(A), %i*2*%pi*1) ans? = ?? 0.9991047 + 0.0595012i?? 0.0000225 - 5.350D-08i?? 0.0000132 - 5.350D-08i?? 0.0000132 - 5.350D-08i ?? 0.0000552 - 0.1037974i?? 0.9990938 + 0.0595013i? -0.0008828 - 2.194D-09i? -0.0008828 - 2.194D-09i ?? 0.0000229 - 7.699D-10i?? 0.0008778 - 1.540D-09i?? 1.0008549 + 0.0595013i?? 0.0008789 - 1.549D-09i ? -0.0000645 + 0.1025666i? -0.0008778 + 1.540D-09i? -0.0008789 + 1.549D-09i?? 0.9990971 + 0.0595013i you get the correct answer This is so far I could go, further details such as how the a double precision real or complex number handled in numerical software are beyond my knowledge. thanks. Regards, Chin Luh ---- On Mon, 09 Mar 2020 22:20:38 +0800 Antoine Monmayrant wrote ---- Hello, It seems that this value is below %eps==2.2e-16, so I though that once encoded in double the difference between 2e-20 and 0 is too small to be properly taken into account. Am I missing something? Antoine Le Lundi, Mars 09, 2020 15:11 CET, Chin Luh Tan a ?crit: ? ? initially I thought could it be possible the number is too small (or too large) to be handled? by double?? ? after trying scaling down the problem, I notice that in Scilab 6.0.2 onwards: ? --> 2e-20*%i ans? = ? ?? 0.? ? in Scilab 5.5.2 ? -->2e-20*%i ans? = ? ??? 2.000D-20i? ? ? Could this be the issue? ? thanks. ? rgds, CL ? ---- On Mon, 09 Mar 2020 21:04:12 +0800 St?phane Mottelet wrote ---- ? Maybe an inversion made in state-space could me more reliable ? S. Le 09/03/2020 ? 13:36, mailto:sgougeon at free.fr a ?crit?: > Hello Federico, > > cond() and rcond() do not accept rationals, but the determinant of A is very close to 0: > --> det(A) > ans = > > 3.573D-10 > ------------------------ > 0.0000027s? +7.433D-10s? > > This likely explains that the inversion is not reliable. > > Regards > Samuel > _______________________________________________ > users mailing list > mailto: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 mailto:users at lists.scilab.org http://lists.scilab.org/mailman/listinfo/users ? ? _______________________________________________ users mailing list mailto: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: smile.png Type: image/png Size: 1470 bytes Desc: not available URL: From chinluh.tan at bytecode-asia.com Mon Mar 9 17:24:12 2020 From: chinluh.tan at bytecode-asia.com (Chin Luh Tan) Date: Tue, 10 Mar 2020 00:24:12 +0800 Subject: [Scilab-users] ?= Which module to use for hassle-free image processing with scilab In-Reply-To: <52f6-5e665600-35-7302ea00@217435952> References: <52f6-5e665600-35-7302ea00@217435952> Message-ID: <170c01c6aba.f680c48644416.5122330159478952041@bytecode-asia.com> tHi,? Just a little bit correction, the module currently I am working on is IPCV, not SIVP. I overlooked the scicv in comparison previously as I was "intoxicated" in telling history of the modules related to IPCV. In fact I was trying to work on scicv as well, as it is almost a complete set to link to the opencv library. As mentioned by Clement, the link to the opencv is generated by SWIG, and since it is automatic, there could be a lot of crashed in name.? On top of that, the syntax of the function are very similar to python, so it makes sense to for those switching from python to Scilab.? As it is just too much datatype in OpenCV, it is almost impossible to map each of everyone to Scilab. Hence, then only way is to leave the output of a function to be in "OpenCV space" and computation goes on until the final result which is then convert back to Scilab for the result.? For example, look at this tutorial :?https://www.scilab.org/tutorials/computer-vision-%E2%80%93-structural-analysis somewhere in the middle of the codes we have: cont?=?contours(maxI); hull?=?convexHull(cont); hulld?=?double(hull(:)); this cont, hull are not Scilab variable, but cont required as the input for the convexHull function. If we convert it to Scilab var, then it will need to convert back to the opencv var to be accepted in the next function. hulld is the last result to convert to double. About the opensource, from technical point of view, if I understand correctly, the whole module is generated by SWIG, and having the source is just... useless? or at least, once u have modified the source to fix some bugs, wait...this is provided the generated codes are readable. And once you modified it, the whole thing need to be maintained manually from that point onward? Else when the dev move to new version of OpenCV, the whole source will be refreshed again... (I could be wrong). Let's switch to the coding style: Let's compare if one need to implement function Hough transform: in opencv, you can find the example of python, then follow the similar flow? to get to the end result.? https://docs.opencv.org/4.1.2/d9/db0/tutorial_hough_lines.html in IPCV, you can find the example in C/C++, then create a new gateway file under IPCV gateway folder, and add some lines in the source code from the example.? #include "Whatever" int main(int argc, char** argv) { ??? // Declare the output variables ? ? GetImage() ??? ? ? Mat dst, cdst, cdstP; ? ? ? ..... ??? HoughLines(dst, lines, 1, CV_PI/180, 150, 0, 0 ); // runs the actual detection ? ? ..... ? ? SetImage() ??? return 0; } The "GetImage" and "SetImage" is just an example of sending and passing the images/date to the gateway for computation, so this will create a function like:? out= imhough(S,m,n) ...? Which to choose is a preference of choice, at least, for me. Hope this helps.? Regards, Chin Luh ---- On Mon, 09 Mar 2020 22:44:15 +0800 Antoine Monmayrant wrote ---- Hello Cl?ment, Thanks for your answer. I think it clarifies the situation somehow. I still don't get your point of not open-sourcing it and maintaining it "for free". I think it's the other way round: if you open-source it, it might happen that some members of the community contribute to extend it and maintain it "for free". >From the info you gave me, scicv should be avoided by any one not being that particular client of your group. Moreover, scicv is adding noise and confusion to the atoms library. Antoine Le Lundi, Mars 09, 2020 15:29 CET, Cl?ment David a ?crit: ? ? About the feature set, I suggest you take a look at SIVP which is much more complete and target a wider audience. The available functions are the documented ones and we might add more if customers requested more. ? Currently, this toolbox is used by some customers and we only mapped the feature requested by them to have an associated minimal OpenCV build. It targets customers and we will probably not open-source it as we don?t want to maintain it ?for free?. Again if you want to co-develop, take a look at SIVP ; Chin Luh did a good job and it is open-source ! ? Regards, ? Cl?ment ? ? From: users On Behalf Of Antoine Monmayrant Sent: Monday, March 9, 2020 2:34 PM To: Users mailing list for Scilab Subject: Re: [Scilab-users] ?==?utf-8?q? Which module to use for hassle-free image processing with scilab ? ? Hello Cl?ment, Thanks for your answer. It's still not clear to me whether I should use scicv or not. First, many features are missing and it's not clear to me how I can implement or discover them (hough transforms for example). Is there a list of the opencv functions that you expose through swig and the one that are not implemented? Also, I'm a bit surprised by your statement: Note: the code is not open-source but SWIG for Scilab and OpenCV are! Why is it not open-source? Is this some transient situation due to the way the code was developped (like for a client)? Do you plan to make it open source in the near future? For many reasons and lots of lessons learned the hard way, I don't feel like investing my time on non open-source software... Antoine Le Lundi, Mars 09, 2020 10:52 CET, Cl?ment David a ?crit: ? Hello Antoine, > - scicv: installs without any issue and as reported by Samuel ( > http://forge.scilab.org/index.php/p/scicv/issues/1944/ > http://forge.scilab.org/index.php/p/scicv/issues/1946/ ), overwrites 'write' and > 'read' which breaks many native functions in scilab together with other useful > modules (ie uman). This is a blocking issue that has not been fixed in the past 6 > months. Moreover, many opencv functions are not available and it is not clear > how to access them. About sciCV, the idea was to use SWIG [1] and OpenCV [2] as an easy to use (and simple to develop) toolbox for manipulating images and videos using Scilab scripts. Here we don't have Scilab scripts at all, just a bunch of SWIG rules to generate the Scilab C gateways from the OpenCV C API. We have a focus on keeping the data in the OpenCV world and "accessing" them from Scilab. The two reported bugs have been fixed in 0.5 (sorry I did not close them) and the latest 0.6 version is built for Scilab 6.1.0 after a customer request. Note: the code is not open-source but SWIG for Scilab and OpenCV are! -- Cl?ment _______________________________________________ users mailing list mailto:users at lists.scilab.org http://lists.scilab.org/mailman/listinfo/users ? ? ? _______________________________________________ users mailing list mailto: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: smile.png Type: image/png Size: 1470 bytes Desc: not available URL: From fmiyara at fceia.unr.edu.ar Mon Mar 9 20:03:41 2020 From: fmiyara at fceia.unr.edu.ar (Federico Miyara) Date: Mon, 9 Mar 2020 16:03:41 -0300 Subject: [Scilab-users] =?utf-8?q?Re=C2=A0=3A_problem_with_matrix_of_polyn?= =?utf-8?q?omials?= In-Reply-To: <1349770032.280045122.1583757386978.JavaMail.root@zimbra75-e12.priv.proxad.net> References: <1349770032.280045122.1583757386978.JavaMail.root@zimbra75-e12.priv.proxad.net> Message-ID: <34f7f129-1559-e7eb-6a46-68b057959c7f@fceia.unr.edu.ar> Samuel, Thanks for your answer. Simply being the determinant small doesn't seem a problem when using floating point. Probably the bigger problem is the presence, somewhere, of very dissimile orders of magnitude. One curious detail in my example is that the solution of the system when adding these lines (input vector and multiplication by the inverse matrix): V1 = 1; B = [V1/R1, V1/Z2, 0, 0]'; phi = inv(A) * B; the denominator of the resulting node potentials in vector phi should be of degree 8 but they happen to be just scalars (degree 0) as if the coefficients were below %eps Regards, Federico On 09/03/2020 09:36, sgougeon at free.fr wrote: > Hello Federico, > > cond() and rcond() do not accept rationals, but the determinant of A is very close to 0: > --> det(A) > ans = > > 3.573D-10 > ------------------------ > 0.0000027s? +7.433D-10s? > > This likely explains that the inversion is not reliable. > > 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 fmiyara at fceia.unr.edu.ar Tue Mar 10 00:40:37 2020 From: fmiyara at fceia.unr.edu.ar (Federico Miyara) Date: Mon, 9 Mar 2020 20:40:37 -0300 Subject: [Scilab-users] =?utf-8?b?RndkOiBSZTogID89ID0/dXRmLTg/cT8gUmXCoDog?= =?utf-8?q?problem_with_matrix_of_polynomials?= In-Reply-To: References: Message-ID: I'll keep thinking about it, but in the meantime, I noticed that when displaying a = A*inv(A) we get the customary list of columns as the total width exceeds the available horizontal space. However, we get one "column 1" header and three "column 2" headers instead of "column 1", ..., "column 4". Seemingly it is not only the header which is repeated, but aldo the columns, i.e., column 2 appears three times. This seems to be a display bug. Regards, Federico Miyara > Back to the possible reason of causing this issue when u substitute a > value into the %s? into A*inv(A) > > Assume a = A*inv(A), a(1,1) which suppose to be ~ 1 is : > > --> a(1,1) > ans? = > > > ?? 1.630D-38 + 1.586D-40s + 4.110D-43s^2 + 1.120D-46s^3 + 1.998D-50s^4 > + 3.586D-55s^5 > --------------------------------------------------------------------------- > > > ????????????????????? 1.630D-38 + 4.283D-42s + 7.960D-46s^2 > > the coefficients in numerator and denominator are very small value and > with complex number involve, there might be come kind of limitation in > the numerical software. > > this could be shown if you subs with smaller number: > > --> horner(A*inv(A), %i*2*%pi*1) > ans? = > > ?? 0.9991047 + 0.0595012i?? 0.0000225 - 5.350D-08i 0.0000132 - > 5.350D-08i?? 0.0000132 - 5.350D-08i > ?? 0.0000552 - 0.1037974i?? 0.9990938 + 0.0595013i -0.0008828 - > 2.194D-09i? -0.0008828 - 2.194D-09i > ?? 0.0000229 - 7.699D-10i?? 0.0008778 - 1.540D-09i 1.0008549 + > 0.0595013i?? 0.0008789 - 1.549D-09i > ? -0.0000645 + 0.1025666i? -0.0008778 + 1.540D-09i -0.0008789 + > 1.549D-09i?? 0.9990971 + 0.0595013i > > you get the correct answer > > This is so far I could go, further details such as how the a double > precision real or complex number handled in numerical software are > beyond my knowledge. [Smile] > thanks. > > Regards, > Chin Luh > > > > > ---- On Mon, 09 Mar 2020 22:20:38 +0800 *Antoine Monmayrant > * wrote ---- > > Hello, > > It seems that this value is below %eps==2.2e-16, so I though that > once encoded in double the difference between 2e-20 and 0 is too > small to be properly taken into account. > Am I missing something? > > Antoine > > > Le Lundi, Mars 09, 2020 15:11 CET, Chin Luh Tan > > a ?crit: > > > initially I thought could it be possible the number is too small > (or too large) to be handled? by double? > > after trying scaling down the problem, I notice that in Scilab > 6.0.2 onwards: > > --> 2e-20*%i > ans? = > > ?? 0. > > in Scilab 5.5.2 > > -->2e-20*%i > ans? = > > ??? 2.000D-20i > > > Could this be the issue? > > thanks. > > rgds, > CL > > ---- On Mon, 09 Mar 2020 21:04:12 +0800 *St?phane Mottelet > >* > wrote ---- > > Maybe an inversion made in state-space could me more reliable ? > > S. > > Le 09/03/2020 ? 13:36, sgougeon at free.fr > a ?crit?: > > Hello Federico, > > > > cond() and rcond() do not accept rationals, but the > determinant of A is very close to 0: > > --> det(A) > > ans = > > > > 3.573D-10 > > ------------------------ > > 0.0000027s? +7.433D-10s? > > > > This likely explains that the inversion is not reliable. > > > > 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 > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > > > > ? _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smile.png Type: image/png Size: 1470 bytes Desc: not available URL: From sgougeon at free.fr Tue Mar 10 01:44:15 2020 From: sgougeon at free.fr (Samuel Gougeon) Date: Tue, 10 Mar 2020 01:44:15 +0100 Subject: [Scilab-users] =?utf-8?b?RndkOiBSZTogPz0gPT91dGYtOD9xPyBSZcKgOiBw?= =?utf-8?q?roblem_with_matrix_of_polynomials?= In-Reply-To: References: Message-ID: <680dca3b-1279-1754-bbbe-dd077af82925@free.fr> Le 10/03/2020 ? 00:40, Federico Miyara a ?crit?: > > I'll keep thinking about it, but in the meantime, I noticed that when > displaying > > a = A*inv(A) > > we get the customary list of columns as the total width exceeds the > available horizontal space. However, we get one "column 1" header and > three "column 2" headers instead of "column 1", ..., "column 4". > Seemingly it is not only the header which is repeated, but aldo the > columns, i.e., column 2 appears three times. > > This seems to be a display bug. Please upgrade to 6.1.0, where this is fixed. From amonmayr at laas.fr Tue Mar 10 09:32:22 2020 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Tue, 10 Mar 2020 09:32:22 +0100 Subject: [Scilab-users] New function for scilab to matlab conversion Message-ID: <110a-5e675080-15-23cf918@249198479> Hi all, I am trying to convert some old matlab code to scilab. Running m2sci, I noticed that some simple functions were not available in scilab (pol2car for example). I just did a small clean-room reimplementation of pol2car and tested on the official examples that it behaves like the matlab one. (nothing fancy at all!). Here are my questions: (1) Is there any official way to propose the addition of pol2car to scilab ? (Not sure this is worth a SEP) (2) Is there some official coding style or additional test that I should provide? Thank you in advance, Antoine -------------- next part -------------- An HTML attachment was scrubbed... URL: From Clement.David at esi-group.com Tue Mar 10 10:07:28 2020 From: Clement.David at esi-group.com (=?utf-8?B?Q2zDqW1lbnQgRGF2aWQ=?=) Date: Tue, 10 Mar 2020 09:07:28 +0000 Subject: [Scilab-users] New function for scilab to matlab conversion In-Reply-To: <110a-5e675080-15-23cf918@249198479> References: <110a-5e675080-15-23cf918@249198479> Message-ID: Hi Antoine, Did you already setup a git repository and its pushurl to codereview.scilab.org ? If not, please follow https://wiki.scilab.org/gerrit . If yes, for small changes like pol2cart(), you could simply push the macro, the help page and a unit test ; we will then start the discussion on the code and merge it. For more important changes (multiple functions, modules, Scilab global behavior, etc...) it should be good to write a SEP for better, long-term, information. Note: I did not look for any equivalent function but it looks strange to me to not already have it. Thanks, -- Cl?ment > -----Original Message----- > From: users On Behalf Of Antoine > Monmayrant > Sent: Tuesday, March 10, 2020 9:32 AM > To: Users mailing list for Scilab > Subject: [Scilab-users] New function for scilab to matlab conversion > > Hi all, > > I am trying to convert some old matlab code to scilab. > Running m2sci, I noticed that some simple functions were not available in scilab > (pol2car for example). > I just did a small clean-room reimplementation of pol2car and tested on the > official examples that it behaves like the matlab one. > (nothing fancy at all!). > > Here are my questions: > (1) Is there any official way to propose the addition of pol2car to scilab ? (Not > sure this is worth a SEP) > (2) Is there some official coding style or additional test that I should provide? > > Thank you in advance, > > Antoine From amonmayr at laas.fr Tue Mar 10 10:16:47 2020 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Tue, 10 Mar 2020 10:16:47 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ICBOZXcgZnVuY3Rpb24gZm9y?= =?utf-8?q?_scilab_to_matlab_conversion?= In-Reply-To: Message-ID: <13e1-5e675b00-33-3854d380@200179556> Le Mardi, Mars 10, 2020 10:07 CET, Cl?ment David a ?crit: > Hi Antoine, > > Did you already setup a git repository and its pushurl to codereview.scilab.org ? If not, please follow https://wiki.scilab.org/gerrit . > OK, thanks for the pointer. > If yes, for small changes like pol2cart(), you could simply push the macro, the help page and a unit test ; we will then start the discussion on the code and merge it. For more important changes (multiple functions, modules, Scilab global behavior, etc...) it should be good to write a SEP for better, long-term, information. > That makes sense. Is there any wiki/doc documenting the whole process? > Note: I did not look for any equivalent function but it looks strange to me to not already have it. Well, I first relied on what m2sci said. I had a quick glance but did not find anything. I'll have another look, it's maybe that m2sci is not aware of such a function. Thank you, Antoine > > Thanks, > > -- > Cl?ment > > > -----Original Message----- > > From: users On Behalf Of Antoine > > Monmayrant > > Sent: Tuesday, March 10, 2020 9:32 AM > > To: Users mailing list for Scilab > > Subject: [Scilab-users] New function for scilab to matlab conversion > > > > Hi all, > > > > I am trying to convert some old matlab code to scilab. > > Running m2sci, I noticed that some simple functions were not available in scilab > > (pol2car for example). > > I just did a small clean-room reimplementation of pol2car and tested on the > > official examples that it behaves like the matlab one. > > (nothing fancy at all!). > > > > Here are my questions: > > (1) Is there any official way to propose the addition of pol2car to scilab ? (Not > > sure this is worth a SEP) > > (2) Is there some official coding style or additional test that I should provide? > > > > Thank you in advance, > > > > Antoine > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > From Clement.David at esi-group.com Tue Mar 10 10:43:05 2020 From: Clement.David at esi-group.com (=?utf-8?B?Q2zDqW1lbnQgRGF2aWQ=?=) Date: Tue, 10 Mar 2020 09:43:05 +0000 Subject: [Scilab-users] ?==?utf-8?q? New function for scilab to matlab conversion In-Reply-To: <13e1-5e675b00-33-3854d380@200179556> References: <13e1-5e675b00-33-3854d380@200179556> Message-ID: > > If yes, for small changes like pol2cart(), you could simply push the macro, the > help page and a unit test ; we will then start the discussion on the code and > merge it. For more important changes (multiple functions, modules, Scilab > global behavior, etc...) it should be good to write a SEP for better, long-term, > information. > > > > That makes sense. > Is there any wiki/doc documenting the whole process? No, not really, there are some pages on the wiki but it slightly depends on the kind of function you developed. As we validate the commits with a review, the codereview let us iterate and discuss changes very easily. -- Cl?ment From fmiyara at fceia.unr.edu.ar Thu Mar 12 21:06:20 2020 From: fmiyara at fceia.unr.edu.ar (Federico Miyara) Date: Thu, 12 Mar 2020 17:06:20 -0300 Subject: [Scilab-users] Some inconsistency during installation o 6.1 Message-ID: <930cb2bd-dc20-d1a0-e149-bf8e0fbd57b3@fceia.unr.edu.ar> Dear all, I've just installed version 6.1. When installing it there is a button "About modules...". Clicking on it opens the following link in the browser: https://wiki.scilab.org/howto/install/windows However, it refers to Scilab 5.5.2, not even 6.0.2, so may be this already happened for the preceding versions. It is not important, but considering that the link is there, it should point to an updated link. I didn't test it too much yet, but the new really compact version of mode(1) is most welcome, especially for those of us who use small-screen laptops. Also welcome is the single-line presentation of polynomials, with in-line exponents using superscripts. However, full compactness doesn't seem to work with rationals, since a blank line is still appearing before the result, for instance, --> q = (1-%s)/(1+%s^2) ?q? = ?? 1 -s ?? ----- ?? 1 +s? while with polynomials it works fine: --> q = 1+%s^2 ?q? = ? 1 +s? Regards, Federico Miyara -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephane.mottelet at utc.fr Thu Mar 12 22:21:45 2020 From: stephane.mottelet at utc.fr (stephane.mottelet at utc.fr) Date: Thu, 12 Mar 2020 22:21:45 +0100 Subject: [Scilab-users] Some inconsistency during installation o 6.1 In-Reply-To: <930cb2bd-dc20-d1a0-e149-bf8e0fbd57b3@fceia.unr.edu.ar> Message-ID: <20200312222145.Horde.P3RWL9PzyomgvfbDE9w_ITb@webmail.utc.fr> Hello Frederico, Thank you for your posiitve feedback on 6.1 display improvements. I think you are the only user who did so on the ML. Concerning the problem of rationals display, which is done in %r_p.sci,? for the moment it is impossible to respect the actual mode() value, because overloads?are systematically evaluated with mode() == -1. This a current limitation of overlading mechanism and fixing it is doable but not trivial (at least from my point of view). Best, S. Quoting Federico Miyara : > Dear all, > > I've just installed version 6.1. When installing it there is a > button "About modules...". Clicking on it opens the following link > in the browser: ? > > https://wiki.scilab.org/howto/install/windows[1] > > However, it refers to Scilab 5.5.2, not even 6.0.2, so may be this > already happened for the preceding versions. It is not important, > but considering that the link is there, it should point to an > updated link. > > I didn't test it too much yet, but the new really compact version of > mode(1) is most welcome, especially for those of us who use > small-screen laptops. Also welcome is the single-line presentation > of polynomials, with in-line exponents using superscripts. > However, full compactness doesn't seem to work with rationals, since > a blank line is still appearing before the result, for instance, > > --> q = (1-%s)/(1+%s^2) > ?q? = > ????????? > ?? 1 -s?? > ?? -----? > ?? 1 +s? > > while with polynomials it works fine: > > --> q = 1+%s^2 > ?q? = > ? 1 +s? > > Regards, > > Federico Miyara? ? Links: ------ [1] https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/wiki.scilab.org/howto/install/windows -------------- next part -------------- An HTML attachment was scrubbed... URL: From p.muehlmann at gmail.com Fri Mar 13 21:05:14 2020 From: p.muehlmann at gmail.com (P M) Date: Fri, 13 Mar 2020 21:05:14 +0100 Subject: [Scilab-users] read database file (sqlite) Message-ID: Dear Experts, I try to read a database file (*.db). The file is obviously written with SQLite format 3...at least a online viewer can show me the file content....and at the file beginning it's written: sqlite format 3.... Any chance, that I can read/view this file with Scilab? Thank you, Philipp -------------- next part -------------- An HTML attachment was scrubbed... URL: From perrichon.pierre at wanadoo.fr Mon Mar 16 08:10:51 2020 From: perrichon.pierre at wanadoo.fr (Perrichon) Date: Mon, 16 Mar 2020 08:10:51 +0100 Subject: [Scilab-users] Impossibility to open a scg file with datatips recorded with scilab 5.5.2 - Bugzilla #16374 Message-ID: Hello, It's no more possible to open a scg file with datatips recorded coming from Scilab 5.5.2 to Scilab 6.1.0 Should it be possible to get a translater for scg coming from 5.5.2 to 6.1.0 ? I've more than hundred of scg figures in scilab 5.5.2 See attached file Test.scg Bugzilla #16374 to test the bug ERROR LOG: ---------- --> load('C:\0 - tampon\Test.scg') ? la ligne 14 de la fonction createDatatip ? la ligne 42 de la fonction createSingleHandle ? la ligne 9 de la fonction createMatrixHandle ? la ligne 42 de la fonction createPolyline ? la ligne 8 de la fonction createSingleHandle ? la ligne 9 de la fonction createMatrixHandle ? la ligne 39 de la fonction createAxes ? la ligne 6 de la fonction createSingleHandle ? la ligne 69 de la fonction createFigure ? la ligne 4 de la fonction createSingleHandle ? la ligne 9 de la fonction createMatrixHandle ? la ligne 4 de la fonction %__convertVariable__ ? la ligne 955 de la fonction %_sodload ( C:\Program Files\scilab-6.1.0\modules\io\macros\%_sodload.sci ligne 968 ) dans la fonction native load La propri?t? 'z_component' est obsol?te et sera supprim?e, utilisez 'display_components' ? la place. Best regards Pierre P. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 5830 bytes Desc: not available URL: From perrichon.pierre at wanadoo.fr Mon Mar 16 12:38:55 2020 From: perrichon.pierre at wanadoo.fr (Perrichon) Date: Mon, 16 Mar 2020 12:38:55 +0100 Subject: [Scilab-users] Datatips display are incoherent with the Y-axes scaning using scilab 6.1.0 - Bugzilla #16376 Message-ID: Hello, BUG DESCRIPTION: ---------------- datatips display are incoherent with the Y-axes scaning using scilab 6.1.0 It was not the case with Scilab 5.5.2 At least datatips display should respect precision of the y-axis ERROR LOG: ---------- None HOW TO REPRODUCE THE BUG: ------------------------- Open attached file Test2.scg and zoom in up to the bug OTHER INFORMATION: ------------------ It was correct Scilab 5.5.2 See Bugzilla #16376 for attached files Sample time = 0.1s Best regard -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 30680 bytes Desc: not available URL: From amonmayr at laas.fr Mon Mar 16 17:06:38 2020 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Mon, 16 Mar 2020 17:06:38 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ID89PT91dGYtOD9xPyA/PSBO?= =?utf-8?q?ew_function_for_scilab_to_matlab_conversio?= In-Reply-To: Message-ID: <7acf-5e6fa400-53-8fc81b0@151636173> Cl?ment, I had a look at gerrit, it's a bit overwhelming. I don't want to add unnecessary noise to the git log. I am not even sure about: (1) the number / nature of the files I am supposed to make. So far, I though about: - the macro itself 'pol2cart.sci' - the xml file to describe the help page 'pol2cart.xml' - some test files. (2) the hierarchical structure of the contribution: which file goes where. If any of you can share any piece of advice about the two points above, I'll appreciate greatly. Do you think making a dumb atoms module around this simple function could help me get all the required files and sorted as expected? Antoine Le Mardi, Mars 10, 2020 10:43 CET, Cl?ment David a ?crit: > > > If yes, for small changes like pol2cart(), you could simply push the macro, the > > help page and a unit test ; we will then start the discussion on the code and > > merge it. For more important changes (multiple functions, modules, Scilab > > global behavior, etc...) it should be good to write a SEP for better, long-term, > > information. > > > > > > > That makes sense. > > Is there any wiki/doc documenting the whole process? > > No, not really, there are some pages on the wiki but it slightly depends on the kind of function you developed. As we validate the commits with a review, the codereview let us iterate and discuss changes very easily. > > -- > Cl?ment > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > From j.s.strom at hslmg.de Mon Mar 16 22:46:05 2020 From: j.s.strom at hslmg.de (Jens Simon Strom) Date: Mon, 16 Mar 2020 22:46:05 +0100 Subject: [Scilab-users] xtitle hides figure cintent Message-ID: <0da4db6c-c71f-2f59-e8e7-f1c7a69a0343@hslmg.de> Hallo Scilab family, After two decades of using Scilab I was not able to fix the following problem. fig=figure('visible','off'); plot(0:5,0:5) //xtitle('xtitle hides the figure content.') set(fig,'visible','on'); The script does what I expect. However when uncommenting xtitle the figure is blank (Version 5.5.2*). What can I do? The background of this question is a script which creates some 10 figures which are filled with polylines in a loop. Whithout the visible off/on there is a nervous flicker of graphics which I want to avoid. Butxtitle is a must. *) I cannat go to Version 6 because most of my earlier scripts would not run. Regards Jens -------------- next part -------------- An HTML attachment was scrubbed... URL: From fmiyara at fceia.unr.edu.ar Tue Mar 17 01:46:17 2020 From: fmiyara at fceia.unr.edu.ar (Federico Miyara) Date: Mon, 16 Mar 2020 21:46:17 -0300 Subject: [Scilab-users] xtitle hides figure cintent In-Reply-To: <0da4db6c-c71f-2f59-e8e7-f1c7a69a0343@hslmg.de> References: <0da4db6c-c71f-2f59-e8e7-f1c7a69a0343@hslmg.de> Message-ID: Jens, I've tried this in Scilab 6.1 and it works fine. I understand the problem of backwards compatibility. I really do, since I had about 1000 Matlab fully working scripts and functions when I decided to migrate to Scilab. Most of them need much more than cosmetic changes like // for %. But it was worth the effort. The successive changes from 5.5.2 through 6.1 were much smoother than changing? application altoghether In your case, unless you don't plan ever to benefit from improvements of new Scilab versions (including knonw bugs which no one will fix for earlier versions), you should try 6.1. There is no problem to keep 5.5.2 installed and start working in 6.1. If you need to run an older script and don't want to update it, you just open it in 5.5.2. Regards, Federico On 16/03/2020 18:46, Jens Simon Strom wrote: > > Hallo Scilab family, > > After two decades of using Scilab I was not able to fix the following > problem. > > fig=figure('visible','off'); > plot(0:5,0:5) > //xtitle('xtitle hides the figure content.') > set(fig,'visible','on'); The script does what I expect. However when > uncommenting xtitle the figure is blank (Version 5.5.2*). What can I > do? The background of this question is a script which creates some 10 > figures which are filled with polylines in a loop. Whithout the > visible off/on there is a nervous flicker of graphics which I want to > avoid. Butxtitle is a must. *) I cannat go to Version 6 because most > of my earlier scripts would not run. Regards Jens > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From amonmayr at laas.fr Tue Mar 17 03:37:30 2020 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Tue, 17 Mar 2020 03:37:30 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ICB4dGl0bGUgaGlkZXMgZmln?= =?utf-8?q?ure_cintent?= In-Reply-To: <0da4db6c-c71f-2f59-e8e7-f1c7a69a0343@hslmg.de> Message-ID: <6841-5e703800-1d-66a58580@156971220> Hello Jens, I'm sorry, I cannot try your code on scilab-5.5.2 : I just downloaded and installed it but it segfaults whenever using graphics (ie only scilab-cli works). BTW, should I report this or development/bug fixes are over on 5.5.2? If I remember correctly, updating graphics content and properties in a loop was a bit of a problem with 5.5.2 with some race conditions. Results depended on the timing and for example something that worked OK when selecting + Ctrl+E in the editor was not behaving the same when using F5! In particular, I had different results when outputting to a file (ie png driver or equivalent) or to an interactive plot. Here are a couple of thinks to try that I had to resort to with 5.5.2: - try to run your code by using selection + Ctrl+E, maybe by running small chunks at a time. If you get the intended results, it confirms you are facing a race condition. - try different syntaxes that should be equivalent like fig.children.x_label.text='foo' instead of xtitle('foo') or fig.visible='on' instead of set(fig,'visible','on'). - add some pauses, ie sleep(10) between some of the graphics changes. - try again: like repeat the set(fig,'visible','on'); twice. Hope it helps, let us know whether it works or not. Cheers, Antoine Le Lundi, Mars 16, 2020 22:46 CET, Jens Simon Strom a ?crit: > Hallo Scilab family, > > After two decades of using Scilab I was not able to fix the following > problem. > > fig=figure('visible','off'); > plot(0:5,0:5) > //xtitle('xtitle hides the figure content.') > set(fig,'visible','on'); The script does what I expect. However when > uncommenting xtitle the figure is blank (Version 5.5.2*). What can I do? > The background of this question is a script which creates some 10 > figures which are filled with polylines in a loop. Whithout the visible > off/on there is a nervous flicker of graphics which I want to avoid. > Butxtitle is a must. *) I cannat go to Version 6 because most of my > earlier scripts would not run. Regards Jens > From amonmayr at laas.fr Tue Mar 17 04:38:20 2020 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Tue, 17 Mar 2020 04:38:20 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ICB4dGl0bGUgaGlkZXMgZmln?= =?utf-8?q?ure_cinten?= In-Reply-To: <6841-5e703800-1d-66a58580@156971220> Message-ID: <67a0-5e704600-33-61922580@220273604> > - try different syntaxes that should be equivalent like fig.children.x_label.text='foo' instead of xtitle('foo') or fig.visible='on' instead of set(fig,'visible','on'). Sorry, I meant fig.children.title.text='foo' instead of xtitle('foo') Antoine From fmiyara at fceia.unr.edu.ar Tue Mar 17 10:30:43 2020 From: fmiyara at fceia.unr.edu.ar (Federico Miyara) Date: Tue, 17 Mar 2020 06:30:43 -0300 Subject: [Scilab-users] Strange behaviour of prod on rationals Message-ID: Dear all, Look at this code (the coefficients are actually the result of pevious calculations): NUM = [5.858D-09 + 2.011D-08*%s + 4.884D-08*%s^2 ... 5.858D-09 + 8.796D-10*%s + 7.028D-10*%s^2] DEN = [0.1199597 + 7.2765093*%s + %s^2 ... ?????? 8.336136 + 7.0282601*%s + %s^2] q = NUM./DEN Running it yields ?? 5.858D-09 +2.011D-08s +4.884D-08s?? 5.858D-09 +8.796D-10s +7.028D-10s? ?? ---------------------------------- ---------------------------------- ?????? 0.1199597 +7.2765093s +s???????????? 8.336136 +7.0282601s +s? This is, correctly, a two-component rational vector with the expected numerators and denominators. Now let's evaluate q = prod(NUM./DEN) The prod documantation sys that the argument may be "an array of reals, complex, booleans, polynomials or rational fractions". It should provide the rational obtained by multiplying the twonumrators and the two denominators. However, we get ?? 3.432D-17 +1.230D-16s +3.079D-16s? +5.709D-17s? +3.432D-17s? ?? ------------------------------------------------------------ ??????????????????????????????? 1 The numeratoris right, but the expected denominator has been just replaced by 1 However, rewriting the command as prod(NUM)/prod(DEN) we get the expected result: ?? 3.432D-17 +1.230D-16s +3.079D-16s? +5.709D-17s? +3.432D-17s? ?? ------------------------------------------------------------ ?????? 1.0000004 +61.501079s +59.597296s? +14.304769s? +s? This is quite strange! Now we repeat with simpler polynomials: NUM = [1-%s 2-%s] DEN = [1+%s 2+%s] q = NUM./DEN We get ?? 1 -s? 2 -s ?? ----? ---- ?? 1 +s? 2 +s Now evaluate prod(NUM./DEN) The result is the expected one! ?? 2 -3s +s? ?? --------- ?? 2 +3s +s? The behavior seems to depend on the type of polynomials. Is this a bug or there is something I'm not interpreting correctly? Regards, Federico Miyara -------------- next part -------------- An HTML attachment was scrubbed... URL: From perrichon.pierre at wanadoo.fr Tue Mar 17 10:48:36 2020 From: perrichon.pierre at wanadoo.fr (Perrichon) Date: Tue, 17 Mar 2020 10:48:36 +0100 Subject: [Scilab-users] Strange behaviour of prod on rationals In-Reply-To: References: Message-ID: Hello Federico I have met few months or years ago this problem when i was developping my ? OPTSIM Solution ? software to fix parameters of a PID for turbines (30 mw to 2 gw) in Nyquist and Bode Plans with hydraulic parameters site So I?ve seen instability of the denominator, witch damage calculus. I don ?t remember what I?ve done to get a cool solution, but it has been a hard and severe problem with syslin, tf2ss and ss2tf instructions Sincerely Pierre P. De : users De la part de Federico Miyara Envoy? : mardi 17 mars 2020 10:31 ? : Users mailing list for Scilab Objet : [Scilab-users] Strange behaviour of prod on rationals Dear all, Look at this code (the coefficients are actually the result of pevious calculations): NUM = [5.858D-09 + 2.011D-08*%s + 4.884D-08*%s^2 ... 5.858D-09 + 8.796D-10*%s + 7.028D-10*%s^2] DEN = [0.1199597 + 7.2765093*%s + %s^2 ... 8.336136 + 7.0282601*%s + %s^2] q = NUM./DEN Running it yields 5.858D-09 +2.011D-08s +4.884D-08s? 5.858D-09 +8.796D-10s +7.028D-10s? ---------------------------------- ---------------------------------- 0.1199597 +7.2765093s +s? 8.336136 +7.0282601s +s? This is, correctly, a two-component rational vector with the expected numerators and denominators. Now let's evaluate q = prod(NUM./DEN) The prod documantation sys that the argument may be "an array of reals, complex, booleans, polynomials or rational fractions". It should provide the rational obtained by multiplying the twonumrators and the two denominators. However, we get 3.432D-17 +1.230D-16s +3.079D-16s? +5.709D-17s? +3.432D-17s? ------------------------------------------------------------ 1 The numeratoris right, but the expected denominator has been just replaced by 1 However, rewriting the command as prod(NUM)/prod(DEN) we get the expected result: 3.432D-17 +1.230D-16s +3.079D-16s? +5.709D-17s? +3.432D-17s? ------------------------------------------------------------ 1.0000004 +61.501079s +59.597296s? +14.304769s? +s? This is quite strange! Now we repeat with simpler polynomials: NUM = [1-%s 2-%s] DEN = [1+%s 2+%s] q = NUM./DEN We get 1 -s 2 -s ---- ---- 1 +s 2 +s Now evaluate prod(NUM./DEN) The result is the expected one! 2 -3s +s? --------- 2 +3s +s? The behavior seems to depend on the type of polynomials. Is this a bug or there is something I'm not interpreting correctly? Regards, Federico Miyara -------------- next part -------------- An HTML attachment was scrubbed... URL: From perrichon.pierre at wanadoo.fr Tue Mar 17 11:42:23 2020 From: perrichon.pierre at wanadoo.fr (Perrichon) Date: Tue, 17 Mar 2020 11:42:23 +0100 Subject: [Scilab-users] Strange behaviour of prod on rationals References: Message-ID: Here are examples of my process in Open loop (FTBO) or Close loop (FTBF) Depending of managemat, D can have s14 ? De : Perrichon Envoy? : mardi 17 mars 2020 10:49 ? : 'Users mailing list for Scilab' Objet : RE: [Scilab-users] Strange behaviour of prod on rationals Hello Federico I have met few months or years ago this problem when i was developping my ? OPTSIM Solution ? software to fix parameters of a PID for turbines (30 mw to 2 gw) in Nyquist and Bode Plans with hydraulic parameters site So I?ve seen instability of the denominator, witch damage calculus. I don ?t remember what I?ve done to get a cool solution, but it has been a hard and severe problem with syslin, tf2ss and ss2tf instructions Sincerely Pierre P. De : users > De la part de Federico Miyara Envoy? : mardi 17 mars 2020 10:31 ? : Users mailing list for Scilab > Objet : [Scilab-users] Strange behaviour of prod on rationals Dear all, Look at this code (the coefficients are actually the result of pevious calculations): NUM = [5.858D-09 + 2.011D-08*%s + 4.884D-08*%s^2 ... 5.858D-09 + 8.796D-10*%s + 7.028D-10*%s^2] DEN = [0.1199597 + 7.2765093*%s + %s^2 ... 8.336136 + 7.0282601*%s + %s^2] q = NUM./DEN Running it yields 5.858D-09 +2.011D-08s +4.884D-08s? 5.858D-09 +8.796D-10s +7.028D-10s? ---------------------------------- ---------------------------------- 0.1199597 +7.2765093s +s? 8.336136 +7.0282601s +s? This is, correctly, a two-component rational vector with the expected numerators and denominators. Now let's evaluate q = prod(NUM./DEN) The prod documantation sys that the argument may be "an array of reals, complex, booleans, polynomials or rational fractions". It should provide the rational obtained by multiplying the twonumrators and the two denominators. However, we get 3.432D-17 +1.230D-16s +3.079D-16s? +5.709D-17s? +3.432D-17s? ------------------------------------------------------------ 1 The numeratoris right, but the expected denominator has been just replaced by 1 However, rewriting the command as prod(NUM)/prod(DEN) we get the expected result: 3.432D-17 +1.230D-16s +3.079D-16s? +5.709D-17s? +3.432D-17s? ------------------------------------------------------------ 1.0000004 +61.501079s +59.597296s? +14.304769s? +s? This is quite strange! Now we repeat with simpler polynomials: NUM = [1-%s 2-%s] DEN = [1+%s 2+%s] q = NUM./DEN We get 1 -s 2 -s ---- ---- 1 +s 2 +s Now evaluate prod(NUM./DEN) The result is the expected one! 2 -3s +s? --------- 2 +3s +s? The behavior seems to depend on the type of polynomials. Is this a bug or there is something I'm not interpreting correctly? Regards, Federico Miyara -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 45551 bytes Desc: not available URL: From amonmayr at laas.fr Tue Mar 17 15:28:59 2020 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Tue, 17 Mar 2020 15:28:59 +0100 Subject: [Scilab-users] =?utf-8?q?Bug_report_etiquette_=3A_memory_leaks_in?= =?utf-8?q?_graphics?= Message-ID: <19b5-5e70de80-af-405ecb00@213462403> Hi all, I know that it's usually bad practice to duplicate an already existing bug. But it's also good practice to make one report per specific bug. I've just waisted two days on a nasty memory leak when plotting/clearing a graph in a loop (50 iterations were enough to kill scilab). Looking at reports of bugzilla, I see plethora of memory leak bugs for graphics (eg #14310, #14508, #14977 to name just a few) that are most probably all related. Should I report a new bug or comment on these ones, being slightly off topic? Antoine From amonmayr at laas.fr Tue Mar 17 18:07:36 2020 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Tue, 17 Mar 2020 18:07:36 +0100 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ICBCdWcgcmVwb3J0IGV0aXF1?= =?utf-8?q?ette_=3A_memory_leaks_in_graphics?= In-Reply-To: <19b5-5e70de80-af-405ecb00@213462403> Message-ID: <7df3-5e710400-65-77bbf300@60371140> Hello, Following a private discussion with Samuel, I submitted a bug report on a memory leak in Matplot(): http://bugzilla.scilab.org/show_bug.cgi?id=16377 Cheers, Antoine Le Mardi, Mars 17, 2020 15:28 CET, "Antoine Monmayrant" a ?crit: > Hi all, > > I know that it's usually bad practice to duplicate an already existing bug. > But it's also good practice to make one report per specific bug. > I've just waisted two days on a nasty memory leak when plotting/clearing a graph in a loop (50 iterations were enough to kill scilab). > Looking at reports of bugzilla, I see plethora of memory leak bugs for graphics (eg #14310, #14508, #14977 to name just a few) that are most probably all related. > > Should I report a new bug or comment on these ones, being slightly off topic? > > Antoine > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > From fmiyara at fceia.unr.edu.ar Tue Mar 17 19:27:36 2020 From: fmiyara at fceia.unr.edu.ar (Federico Miyara) Date: Tue, 17 Mar 2020 15:27:36 -0300 Subject: [Scilab-users] Strange behaviour of prod on rationals In-Reply-To: References: Message-ID: <70a32a21-fad5-d5e9-442c-cf305d3f300a@fceia.unr.edu.ar> Pierre, Thanks for your answer. However, I believe no involved computatins are required to get the correct result. The multiplication of the two polynomials from the denominators is straightforward, no need to solve any system, no risk of ill-conditioned or badly-scaled matrices. This must be another kind of problem. Regards, Federico Miyara On 17/03/2020 06:48, Perrichon wrote: > > Hello Federico > > I have met few months or years ago this problem when i was developping > my ???OPTSIM Solution?? software to fix parameters of a PID for > turbines (30 mw to 2 gw) in Nyquist and Bode Plans with hydraulic > parameters site > > So I?ve seen instability of the denominator, witch damage calculus. > > I don??t remember what I?ve done to get a cool solution, but it ?has > been a hard and severe problem with syslin, tf2ss and ss2tf instructions > > Sincerely > > Pierre P. > > *De?:*users *De la part de* Federico > Miyara > *Envoy??:* mardi 17 mars 2020 10:31 > *??:* Users mailing list for Scilab > *Objet?:* [Scilab-users] Strange behaviour of prod on rationals > > > Dear all, > > Look at this code (the coefficients are actually the result of pevious > calculations): > > NUM = [5.858D-09 + 2.011D-08*%s + 4.884D-08*%s^2 ... > 5.858D-09 + 8.796D-10*%s + 7.028D-10*%s^2] > DEN = [0.1199597 + 7.2765093*%s + %s^2 ... > ?????? 8.336136 + 7.0282601*%s + %s^2] > q = NUM./DEN > > Running it yields > > ?? 5.858D-09 +2.011D-08s +4.884D-08s?? 5.858D-09 +8.796D-10s +7.028D-10s? > ?? ---------------------------------- ---------------------------------- > ?????? 0.1199597 +7.2765093s +s???????????? 8.336136 +7.0282601s +s? > > This is, correctly, a two-component rational vector with the expected > numerators and denominators. > > Now let's evaluate > > q = prod(NUM./DEN) > > The prod documantation sys that the argument may be "an array of > reals, complex, booleans, polynomials or rational fractions". It > should provide the rational obtained by multiplying the twonumrators > and the two denominators. However, we get > > ?? 3.432D-17 +1.230D-16s +3.079D-16s? +5.709D-17s? +3.432D-17s? > ------------------------------------------------------------ > 1 > > The numeratoris right, but the expected denominator has been just > replaced by 1 > > However, rewriting the command as > > prod(NUM)/prod(DEN) > > we get the expected result: > > ?? 3.432D-17 +1.230D-16s +3.079D-16s? +5.709D-17s? +3.432D-17s? > ------------------------------------------------------------ > ?????? 1.0000004 +61.501079s +59.597296s? +14.304769s? +s? > > This is quite strange! > > Now we repeat with simpler polynomials: > > NUM = [1-%s 2-%s] > DEN = [1+%s 2+%s] > q = NUM./DEN > > We get > > ?? 1 -s? 2 -s > ?? ----? ---- > ?? 1 +s? 2 +s > > Now evaluate > > prod(NUM./DEN) > > The result is the expected one! > > ?? 2 -3s +s? > ?? --------- > ?? 2 +3s +s? > > The behavior seems to depend on the type of polynomials. > > Is this a bug or there is something I'm not interpreting correctly? > > Regards, > > Federico Miyara > > > _______________________________________________ > 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 Fri Mar 20 14:10:02 2020 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Fri, 20 Mar 2020 14:10:02 +0100 Subject: [Scilab-users] Strange behaviour of prod on rationals In-Reply-To: References: Message-ID: <575e8cc6-3691-a1b9-b641-76e9e12f6c76@utc.fr> Hello Frederico, The problem is in simp() : ---> rlist(prod(a.num),prod(a.den),a.dt) ?ans? = ????????????????????????????????????? 2??????????? 3??????????? 4 ?? 3.432D-17 + 1.230D-16s + 3.079D-16s + 5.709D-17s + 3.432D-17s ?? -------------------------------------------------------------- ????????????????????????????????????????? 2??????????? 3?? 4 ?????? 1.0000004 + 61.501079s + 59.597296s + 14.304769s + s ---> simp(rlist(prod(a.num),prod(a.den),a.dt)) ?ans? = ????????????????????????????????????? 2??????????? 3??????????? 4 ?? 3.432D-17 + 1.230D-16s + 3.079D-16s + 5.709D-17s + 3.432D-17s ?? -------------------------------------------------------------- ???????????????????????????????? 1 S. Le 17/03/2020 ? 10:30, Federico Miyara a ?crit?: > > Dear all, > > Look at this code (the coefficients are actually the result of pevious > calculations): > > NUM = [5.858D-09 + 2.011D-08*%s + 4.884D-08*%s^2 ... > 5.858D-09 + 8.796D-10*%s + 7.028D-10*%s^2] > DEN = [0.1199597 + 7.2765093*%s + %s^2 ... > ?????? 8.336136 + 7.0282601*%s + %s^2] > q = NUM./DEN > > Running it yields > > ?? 5.858D-09 +2.011D-08s +4.884D-08s?? 5.858D-09 +8.796D-10s +7.028D-10s? > ?? ---------------------------------- ---------------------------------- > ?????? 0.1199597 +7.2765093s +s???????????? 8.336136 +7.0282601s +s? > > This is, correctly, a two-component rational vector with the expected > numerators and denominators. > > Now let's evaluate > > q = prod(NUM./DEN) > > The prod documantation sys that the argument may be "an array of > reals, complex, booleans, polynomials or rational fractions". It > should provide the rational obtained by multiplying the twonumrators > and the two denominators. However, we get > > ?? 3.432D-17 +1.230D-16s +3.079D-16s? +5.709D-17s? +3.432D-17s? > ?? ------------------------------------------------------------ > ??????????????????????????????? 1 > > The numeratoris right, but the expected denominator has been just > replaced by 1 > > However, rewriting the command as > > prod(NUM)/prod(DEN) > > we get the expected result: > > ?? 3.432D-17 +1.230D-16s +3.079D-16s? +5.709D-17s? +3.432D-17s? > ?? ------------------------------------------------------------ > ?????? 1.0000004 +61.501079s +59.597296s? +14.304769s? +s? > > This is quite strange! > > Now we repeat with simpler polynomials: > > NUM = [1-%s 2-%s] > DEN = [1+%s 2+%s] > q = NUM./DEN > > We get > > ?? 1 -s? 2 -s > ?? ----? ---- > ?? 1 +s? 2 +s > > Now evaluate > > prod(NUM./DEN) > > The result is the expected one! > > ?? 2 -3s +s? > ?? --------- > ?? 2 +3s +s? > > The behavior seems to depend on the type of polynomials. > > Is this a bug or there is something I'm not interpreting correctly? > > Regards, > > Federico Miyara > > _______________________________________________ > 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 Fri Mar 20 14:42:09 2020 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Fri, 20 Mar 2020 14:42:09 +0100 Subject: [Scilab-users] Strange behaviour of prod on rationals In-Reply-To: <575e8cc6-3691-a1b9-b641-76e9e12f6c76@utc.fr> References: <575e8cc6-3691-a1b9-b641-76e9e12f6c76@utc.fr> Message-ID: <80458f49-e6d8-e414-1618-8f1e99f2fe6a@utc.fr> (num,den) calling style seems to be OK: --> [a,b]=simp(prod(q.num),prod(q.den)) ?a? = ??????????????????????????????????? 2??????????? 3??????????? 4 ?? 3.432D-17 +1.230D-16s +3.079D-16s? +5.709D-17s? +3.432D-17s ?b? = ??????????????????????????????????? 2??????????? 3?? 4 ?? 1.0000004 +61.501079s +59.597296s? +14.304769s? +s The problem is in %r_simp code, which does a cleaning, but not a complete one. If fact we should have the same result when the cleaning is done afterwards : --> clean(a/b) ?ans? = ?? 0 ?? -- ?? 1 which is OK to me when you see this: --> w=10^(1:6); abs(horner(a/b,%i*w)) ?ans? = ?? 2.224D-17?? 3.415D-17?? 3.432D-17?? 3.432D-17?? 3.432D-17 3.432D-17 S. Le 20/03/2020 ? 14:10, St?phane Mottelet a ?crit?: > > Hello Frederico, > > The problem is in simp() : > > ---> rlist(prod(a.num),prod(a.den),a.dt) > ?ans? = > > ????????????????????????????????????? 2??????????? 3 4 > ?? 3.432D-17 + 1.230D-16s + 3.079D-16s + 5.709D-17s + 3.432D-17s > -------------------------------------------------------------- > ????????????????????????????????????????? 2??????????? 3 4 > ?????? 1.0000004 + 61.501079s + 59.597296s + 14.304769s + s > > > ---> simp(rlist(prod(a.num),prod(a.den),a.dt)) > ?ans? = > > ????????????????????????????????????? 2??????????? 3 4 > ?? 3.432D-17 + 1.230D-16s + 3.079D-16s + 5.709D-17s + 3.432D-17s > -------------------------------------------------------------- > > ???????????????????????????????? 1 > > S. > > Le 17/03/2020 ? 10:30, Federico Miyara a ?crit?: >> >> Dear all, >> >> Look at this code (the coefficients are actually the result of >> pevious calculations): >> >> NUM = [5.858D-09 + 2.011D-08*%s + 4.884D-08*%s^2 ... >> 5.858D-09 + 8.796D-10*%s + 7.028D-10*%s^2] >> DEN = [0.1199597 + 7.2765093*%s + %s^2 ... >> ?????? 8.336136 + 7.0282601*%s + %s^2] >> q = NUM./DEN >> >> Running it yields >> >> ?? 5.858D-09 +2.011D-08s +4.884D-08s?? 5.858D-09 +8.796D-10s >> +7.028D-10s? >> ?? ---------------------------------- ---------------------------------- >> ?????? 0.1199597 +7.2765093s +s???????????? 8.336136 +7.0282601s +s? >> >> This is, correctly, a two-component rational vector with the expected >> numerators and denominators. >> >> Now let's evaluate >> >> q = prod(NUM./DEN) >> >> The prod documantation sys that the argument may be "an array of >> reals, complex, booleans, polynomials or rational fractions". It >> should provide the rational obtained by multiplying the twonumrators >> and the two denominators. However, we get >> >> ?? 3.432D-17 +1.230D-16s +3.079D-16s? +5.709D-17s? +3.432D-17s? >> ?? ------------------------------------------------------------ >> ??????????????????????????????? 1 >> >> The numeratoris right, but the expected denominator has been just >> replaced by 1 >> >> However, rewriting the command as >> >> prod(NUM)/prod(DEN) >> >> we get the expected result: >> >> ?? 3.432D-17 +1.230D-16s +3.079D-16s? +5.709D-17s? +3.432D-17s? >> ?? ------------------------------------------------------------ >> ?????? 1.0000004 +61.501079s +59.597296s? +14.304769s? +s? >> >> This is quite strange! >> >> Now we repeat with simpler polynomials: >> >> NUM = [1-%s 2-%s] >> DEN = [1+%s 2+%s] >> q = NUM./DEN >> >> We get >> >> ?? 1 -s? 2 -s >> ?? ----? ---- >> ?? 1 +s? 2 +s >> >> Now evaluate >> >> prod(NUM./DEN) >> >> The result is the expected one! >> >> ?? 2 -3s +s? >> ?? --------- >> ?? 2 +3s +s? >> >> The behavior seems to depend on the type of polynomials. >> >> Is this a bug or there is something I'm not interpreting correctly? >> >> Regards, >> >> Federico Miyara >> >> _______________________________________________ >> 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 arctica1963 at gmail.com Fri Mar 20 15:14:55 2020 From: arctica1963 at gmail.com (arctica1963) Date: Fri, 20 Mar 2020 07:14:55 -0700 (MST) Subject: [Scilab-users] Polar plot query Message-ID: <1584713695030-0.post@n3.nabble.com> Hi all, Very basic query. I have a polar plot and I want to just have the data points visible but not the graticule of the polar plot. I have the figure defined as f=gcf() with axes a=gca(). Is there a quick way to just turn it off? According to the figure properties it is all under the Axes property with the graticule represented by arc, segs and text, with the data points/symbols as a compound element. Sorry for a really basic question! I am sure it is very obvious. Thanks Lester -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From stephane.mottelet at utc.fr Fri Mar 20 15:20:13 2020 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Fri, 20 Mar 2020 15:20:13 +0100 Subject: [Scilab-users] Polar plot query In-Reply-To: <1584713695030-0.post@n3.nabble.com> References: <1584713695030-0.post@n3.nabble.com> Message-ID: You can hide the graticule with : gca().children(1:$-1).visible=%f S. Le 20/03/2020 ? 15:14, arctica1963 a ?crit?: > Hi all, > > Very basic query. I have a polar plot and I want to just have the data > points visible but not the graticule of the polar plot. I have the figure > defined as f=gcf() with axes a=gca(). > > Is there a quick way to just turn it off? According to the figure properties > it is all under the Axes property with the graticule represented by arc, > segs and text, with the data points/symbols as a compound element. > > Sorry for a really basic question! I am sure it is very obvious. > > Thanks > Lester > > > > -- > Sent from: https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html > _______________________________________________ > 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 chinluh.tan at bytecode-asia.com Fri Mar 20 15:36:51 2020 From: chinluh.tan at bytecode-asia.com (Chin Luh Tan) Date: Fri, 20 Mar 2020 22:36:51 +0800 Subject: [Scilab-users] Scilab Atoms Issue Message-ID: <170f8601763.f6881f93999554.208941967613132517@bytecode-asia.com> Hi,? There is a little issue always bugging me, whenever an atoms module has been installed, it will be kept in "archives" folder, either in SCI or SCIHOME respective folder.? Under some circumstances if the developer update some patch in the portal and and remain the same version, atomsSystemUpdate followed by atomsInstall the module will pick up the archived module instead of the latest one from the web. User need to manually delete them from the folder in order to get the latest one.? Is there any function in atoms* which I might have miss out which could clear the archives? It sounds redundant to developers or advance user but it makes sense for normal Scilab user.? ? Thanks. Regards. Chin Luh -------------- next part -------------- An HTML attachment was scrubbed... URL: From arctica1963 at gmail.com Fri Mar 20 16:16:01 2020 From: arctica1963 at gmail.com (arctica1963) Date: Fri, 20 Mar 2020 08:16:01 -0700 (MST) Subject: [Scilab-users] Polar plot query In-Reply-To: References: <1584713695030-0.post@n3.nabble.com> Message-ID: <1584717361248-0.post@n3.nabble.com> Many thanks! -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From fmiyara at fceia.unr.edu.ar Sun Mar 22 05:33:46 2020 From: fmiyara at fceia.unr.edu.ar (Federico Miyara) Date: Sun, 22 Mar 2020 01:33:46 -0300 Subject: [Scilab-users] Strange behaviour of prod on rationals In-Reply-To: <80458f49-e6d8-e414-1618-8f1e99f2fe6a@utc.fr> References: <575e8cc6-3691-a1b9-b641-76e9e12f6c76@utc.fr> <80458f49-e6d8-e414-1618-8f1e99f2fe6a@utc.fr> Message-ID: St?phane, In the meantime, a workaround is to toggle simplification off: simp_mode(%f). This inhibits simplification. Regards, Federico Miyara On 20/03/2020 10:42, St?phane Mottelet wrote: > > (num,den) calling style seems to be OK: > > --> [a,b]=simp(prod(q.num),prod(q.den)) > ?a? = > > ??????????????????????????????????? 2??????????? 3??????????? 4 > ?? 3.432D-17 +1.230D-16s +3.079D-16s? +5.709D-17s? +3.432D-17s > > ?b? = > > ??????????????????????????????????? 2??????????? 3?? 4 > ?? 1.0000004 +61.501079s +59.597296s? +14.304769s? +s > > The problem is in %r_simp code, which does a cleaning, but not a > complete one. If fact we should have the same result when the cleaning > is done afterwards : > > --> clean(a/b) > ?ans? = > > > ?? 0 > ?? -- > > ?? 1 > > which is OK to me when you see this: > > --> w=10^(1:6); abs(horner(a/b,%i*w)) > ?ans? = > > ?? 2.224D-17?? 3.415D-17?? 3.432D-17?? 3.432D-17?? 3.432D-17 3.432D-17 > > S. > > > Le 20/03/2020 ? 14:10, St?phane Mottelet a ?crit?: >> >> Hello Frederico, >> >> The problem is in simp() : >> >> ---> rlist(prod(a.num),prod(a.den),a.dt) >> ?ans? = >> >> ????????????????????????????????????? 2 3??????????? 4 >> ?? 3.432D-17 + 1.230D-16s + 3.079D-16s + 5.709D-17s + 3.432D-17s >> -------------------------------------------------------------- >> ????????????????????????????????????????? 2??????????? 3 4 >> ?????? 1.0000004 + 61.501079s + 59.597296s + 14.304769s + s >> >> >> ---> simp(rlist(prod(a.num),prod(a.den),a.dt)) >> ?ans? = >> >> ????????????????????????????????????? 2 3??????????? 4 >> ?? 3.432D-17 + 1.230D-16s + 3.079D-16s + 5.709D-17s + 3.432D-17s >> -------------------------------------------------------------- >> >> ???????????????????????????????? 1 >> >> S. >> >> Le 17/03/2020 ? 10:30, Federico Miyara a ?crit?: >>> >>> Dear all, >>> >>> Look at this code (the coefficients are actually the result of >>> pevious calculations): >>> >>> NUM = [5.858D-09 + 2.011D-08*%s + 4.884D-08*%s^2 ... >>> 5.858D-09 + 8.796D-10*%s + 7.028D-10*%s^2] >>> DEN = [0.1199597 + 7.2765093*%s + %s^2 ... >>> ?????? 8.336136 + 7.0282601*%s + %s^2] >>> q = NUM./DEN >>> >>> Running it yields >>> >>> ?? 5.858D-09 +2.011D-08s +4.884D-08s?? 5.858D-09 +8.796D-10s >>> +7.028D-10s? >>> ?? ---------------------------------- >>> ---------------------------------- >>> ?????? 0.1199597 +7.2765093s +s???????????? 8.336136 +7.0282601s +s? >>> >>> This is, correctly, a two-component rational vector with the >>> expected numerators and denominators. >>> >>> Now let's evaluate >>> >>> q = prod(NUM./DEN) >>> >>> The prod documantation sys that the argument may be "an array of >>> reals, complex, booleans, polynomials or rational fractions". It >>> should provide the rational obtained by multiplying the twonumrators >>> and the two denominators. However, we get >>> >>> ?? 3.432D-17 +1.230D-16s +3.079D-16s? +5.709D-17s? +3.432D-17s? >>> ------------------------------------------------------------ >>> 1 >>> >>> The numeratoris right, but the expected denominator has been just >>> replaced by 1 >>> >>> However, rewriting the command as >>> >>> prod(NUM)/prod(DEN) >>> >>> we get the expected result: >>> >>> ?? 3.432D-17 +1.230D-16s +3.079D-16s? +5.709D-17s? +3.432D-17s? >>> ------------------------------------------------------------ >>> ?????? 1.0000004 +61.501079s +59.597296s? +14.304769s? +s? >>> >>> This is quite strange! >>> >>> Now we repeat with simpler polynomials: >>> >>> NUM = [1-%s 2-%s] >>> DEN = [1+%s 2+%s] >>> q = NUM./DEN >>> >>> We get >>> >>> ?? 1 -s? 2 -s >>> ?? ----? ---- >>> ?? 1 +s? 2 +s >>> >>> Now evaluate >>> >>> prod(NUM./DEN) >>> >>> The result is the expected one! >>> >>> ?? 2 -3s +s? >>> ?? --------- >>> ?? 2 +3s +s? >>> >>> The behavior seems to depend on the type of polynomials. >>> >>> Is this a bug or there is something I'm not interpreting correctly? >>> >>> Regards, >>> >>> Federico Miyara >>> >>> _______________________________________________ >>> 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: From Clement.David at esi-group.com Wed Mar 25 11:04:47 2020 From: Clement.David at esi-group.com (=?utf-8?B?Q2zDqW1lbnQgRGF2aWQ=?=) Date: Wed, 25 Mar 2020 10:04:47 +0000 Subject: [Scilab-users] =?utf-8?b?Pz0gID89PT91dGYtOD9xPyBOZXcgZnVuY3Rpb24g?= =?utf-8?q?for_scilab_to_matlab_conversio?= In-Reply-To: <7acf-5e6fa400-53-8fc81b0@151636173> References: <7acf-5e6fa400-53-8fc81b0@151636173> Message-ID: Hello Antoine, Don't worry to iterate on the codereview, this is the way to go to add simple function like pol2cart. Even if you are using git, this is not the final git log until validation! About the sub-directory (eg. module) to put your macro into, I suggest you use "elementary_functions": 1. Put the pol2cart.sci file into SCI/modules/elementary_functions/macros 2. Put the pol2cart.xml English help page into SCI/modules/elementary_functions/help/en_US/trigonometry 3. Put the pol2cart.tst unit test file into SCI/modules/elementary_functions/tests/unit_tests/ And that's it for the files! For the review, git add the new files and git push to the codereview. Note: creating a dedicated ATOMS toolbox will involve more work ? Note2: a default xml help file could be generated from Scilab code comments using help_from_sci() -- Cl?ment > -----Original Message----- > From: users On Behalf Of Antoine > Monmayrant > Sent: Monday, March 16, 2020 5:07 PM > To: Users mailing list for Scilab > Subject: Re: [Scilab-users] ?==?utf-8?q? ?==?utf-8?q? ?= New function for scilab > to matlab conversio > > Cl?ment, > > I had a look at gerrit, it's a bit overwhelming. > I don't want to add unnecessary noise to the git log. > I am not even sure about: > (1) the number / nature of the files I am supposed to make. So far, I though > about: > - the macro itself 'pol2cart.sci' > - the xml file to describe the help page 'pol2cart.xml' > - some test files. > (2) the hierarchical structure of the contribution: which file goes where. > > If any of you can share any piece of advice about the two points above, I'll > appreciate greatly. > > Do you think making a dumb atoms module around this simple function could > help me get all the required files and sorted as expected? > > Antoine > > Le Mardi, Mars 10, 2020 10:43 CET, Cl?ment David group.com> a ?crit: > > > > > If yes, for small changes like pol2cart(), you could simply push the macro, > the > > > help page and a unit test ; we will then start the discussion on the code and > > > merge it. For more important changes (multiple functions, modules, Scilab > > > global behavior, etc...) it should be good to write a SEP for better, long-term, > > > information. > > > > > > > > > > That makes sense. > > > Is there any wiki/doc documenting the whole process? > > > > No, not really, there are some pages on the wiki but it slightly depends on the > kind of function you developed. As we validate the commits with a review, the > codereview let us iterate and discuss changes very easily. > > > > -- > > Cl?ment > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/users > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From fmiyara at fceia.unr.edu.ar Sun Mar 29 11:59:11 2020 From: fmiyara at fceia.unr.edu.ar (Federico Miyara) Date: Sun, 29 Mar 2020 06:59:11 -0300 Subject: [Scilab-users] Question Message-ID: Dear all, Some t?ime ago I observed fo a previous version, that the function filter() required that polynomials, when expressed as vectors, have the coefficients in decreasing power order while poly() required them in increasing order. I'm asking whether this has been modified or not (the documentation is still as it was), since in an application case it seems to work as if now the required order were the same as in poly. Regards, Federico -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephane.mottelet at utc.fr Sun Mar 29 13:56:21 2020 From: stephane.mottelet at utc.fr (=?utf-8?Q?St=C3=A9phane_Mottelet?=) Date: Sun, 29 Mar 2020 13:56:21 +0200 Subject: [Scilab-users] Question In-Reply-To: References: Message-ID: <8439E143-483E-4E3F-86EB-FDF3BC659DF9@utc.fr> Hello, filter() has the same api as Matlab?s filter() ans uses Matlab convention for polynomial coefficients, which is the reverse of Scilab convention. S. > Le 29 mars 2020 ? 12:00, Federico Miyara a ?crit : > > ? > Dear all, > > Some t?ime ago I observed fo a previous version, that the function filter() required that polynomials, when expressed as vectors, have the coefficients in decreasing power order while poly() required them in increasing order. > > I'm asking whether this has been modified or not (the documentation is still as it was), since in an application case it seems to work as if now the required order were the same as in poly. > > Regards, > > Federico > > _______________________________________________ > 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 heinznabielek at me.com Mon Mar 30 02:14:52 2020 From: heinznabielek at me.com (Heinz Nabielek) Date: Mon, 30 Mar 2020 02:14:52 +0200 Subject: [Scilab-users] Corona modelling Message-ID: <61797769-8CEB-4391-8C95-A5C56438B43B@me.com> Colleagues: is there an straightforward Scilab approach for solving the three coupled nonlinear differential equations of first order given by the Standard Model of Epidemics? S= number Susceptible: S'=-aSI I= number Infected: I'=aSI - bI R= number Recovered: R'=bI whereby 'a' is the transmission coefficient, 'b' the recovery factor (after Reed-Frost 1928). Initial values for S, I, R are available. Thank you Heinz From tim at wescottdesign.com Mon Mar 30 02:51:17 2020 From: tim at wescottdesign.com (Tim Wescott) Date: Sun, 29 Mar 2020 17:51:17 -0700 Subject: [Scilab-users] Corona modelling In-Reply-To: <61797769-8CEB-4391-8C95-A5C56438B43B@me.com> References: <61797769-8CEB-4391-8C95-A5C56438B43B@me.com> Message-ID: <0d77f6b0a68dd71a5b05fad90bb9969c3d56b9d9.camel@wescottdesign.com> This will be a straightforward application of the ODE solver. Type "help ode" for more detail. You'll make a function that takes the vector x = [S; I; R] as an argument and returns [S'; I'; R']. Then you'll call that function with some starting x and let it play out. You can speed up computation if you provide the Jacobian of f as a function -- if you don't, the solver will calculate it at each time step. On Mon, 2020-03-30 at 02:14 +0200, Heinz Nabielek wrote: > Colleagues: > > is there an straightforward Scilab approach for solving the three > coupled nonlinear differential equations of first order given by the > Standard Model of Epidemics? > > > S= number Susceptible: S'=-aSI > I= number Infected: I'=aSI - bI > R= number Recovered: R'=bI > whereby 'a' is the transmission coefficient, 'b' the recovery factor > (after Reed-Frost 1928). > Initial values for S, I, R are available. > > Thank you > Heinz > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > > -- Tim Wescott www.wescottdesign.com Control & Communications systems, circuit & software design. Phone: 503.631.7815 Cell: 503.349.8432 From stephane.mottelet at utc.fr Mon Mar 30 08:13:40 2020 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Mon, 30 Mar 2020 08:13:40 +0200 Subject: [Scilab-users] Corona modelling In-Reply-To: <61797769-8CEB-4391-8C95-A5C56438B43B@me.com> References: <61797769-8CEB-4391-8C95-A5C56438B43B@me.com> Message-ID: Hello Heinz, Here is an interactive version (made for my children last week...) : // Confinement COVID-19 ! // Stephane MOTTELET, UTC // Tue Mar 24 08:55:03 CET 2020 // function dydt=sir(t, y, bet, gam, N) dydt=[-bet/N*y(1)*y(2) bet/N*y(1)*y(2)-gam*y(2) gam*y(2)]; endfunction function draw(bet, gam) t=0:1:360; N=6e7; if exists("gcbo") && is_handle_valid(gcbo) sb = gcbo; if sb.tag=="beta" bet=sb.value; gam=findobj("gamma").value else gam=sb.value; bet=findobj("beta").value end y=ode('stiff',[N-1;1;0],0,t,list(sir,bet,gam,N)); curves = findobj("curves"); curves.children(1).data(:,2)=y(3,:); curves.children(2).data(:,2)=y(2,:); curves.children(3).data(:,2)=y(1,:); else y=ode('stiff',[N-1;1;0],0,t,list(sir,bet,gam,N)); scf(0) clf plot(t,y) gce().tag="curves"; gce().children.thickness=2; legend("Susceptible","Infected","Recovered",-1) sb1 = uicontrol("style","slider",... "units","normalized",... "Position", [0.85,0.2,0.05,0.48],... "BackgroundColor", [1,1,1],... "Callback_Type",12,... "sliderstep",[1/1000,1/10],... "min",0.15,"max",0.3,"value",bet,... "Callback","draw","tag","beta"); uicontrol("style","text",... "string","$\beta$",... "units","normalized",... "Position", [0.85,0.125,0.05,0.08],... "BackgroundColor", [1,1,1],... "HorizontalAlignment","center"); sb1 = uicontrol("style","slider",... "units","normalized",... "Position", [0.90,0.2,0.05,0.48],... "BackgroundColor", [1,1,1],... "Callback_Type",12,... "sliderstep",[1/1000,1/10],... "min",0,"max",1/15,"value",gam,... "Callback","draw","tag","gamma"); uicontrol("style","text",... "string","$\gamma$",... "units","normalized",... "Position", [0.9,0.125,0.05,0.08],... "BackgroundColor", [1,1,1],... "HorizontalAlignment","center"); end end clf draw(0.3,1/15) Le 30/03/2020 ? 02:14, Heinz Nabielek a ?crit?: > Colleagues: > > is there an straightforward Scilab approach for solving the three coupled nonlinear differential equations of first order given by the Standard Model of Epidemics? > > > S= number Susceptible: S'=-aSI > I= number Infected: I'=aSI - bI > R= number Recovered: R'=bI > whereby 'a' is the transmission coefficient, 'b' the recovery factor (after Reed-Frost 1928). > Initial values for S, I, R are available. > > Thank you > Heinz > _______________________________________________ > 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 jrafaelbguerra at hotmail.com Mon Mar 30 11:42:36 2020 From: jrafaelbguerra at hotmail.com (Rafael Guerra) Date: Mon, 30 Mar 2020 09:42:36 +0000 Subject: [Scilab-users] Corona modelling In-Reply-To: References: <61797769-8CEB-4391-8C95-A5C56438B43B@me.com> Message-ID: Merci St?phane, for the very interesting code and Heinz for the reference to the math behind the epidemy ?curve?, or one of its models. From: users On Behalf Of St?phane Mottelet Sent: Monday, March 30, 2020 9:14 AM To: users at lists.scilab.org Subject: Re: [Scilab-users] Corona modelling Hello Heinz, Here is an interactive version (made for my children last week...) : // Confinement COVID-19 ! // Stephane MOTTELET, UTC // Tue Mar 24 08:55:03 CET 2020 // function dydt=sir(t, y, bet, gam, N) dydt=[-bet/N*y(1)*y(2) bet/N*y(1)*y(2)-gam*y(2) gam*y(2)]; endfunction function draw(bet, gam) t=0:1:360; N=6e7; if exists("gcbo") && is_handle_valid(gcbo) sb = gcbo; if sb.tag=="beta" bet=sb.value; gam=findobj("gamma").value else gam=sb.value; bet=findobj("beta").value end y=ode('stiff',[N-1;1;0],0,t,list(sir,bet,gam,N)); curves = findobj("curves"); curves.children(1).data(:,2)=y(3,:); curves.children(2).data(:,2)=y(2,:); curves.children(3).data(:,2)=y(1,:); else y=ode('stiff',[N-1;1;0],0,t,list(sir,bet,gam,N)); scf(0) clf plot(t,y) gce().tag="curves"; gce().children.thickness=2; legend("Susceptible","Infected","Recovered",-1) sb1 = uicontrol("style","slider",... "units","normalized",... "Position", [0.85,0.2,0.05,0.48],... "BackgroundColor", [1,1,1],... "Callback_Type",12,... "sliderstep",[1/1000,1/10],... "min",0.15,"max",0.3,"value",bet,... "Callback","draw","tag","beta"); uicontrol("style","text",... "string","$\beta$",... "units","normalized",... "Position", [0.85,0.125,0.05,0.08],... "BackgroundColor", [1,1,1],... "HorizontalAlignment","center"); sb1 = uicontrol("style","slider",... "units","normalized",... "Position", [0.90,0.2,0.05,0.48],... "BackgroundColor", [1,1,1],... "Callback_Type",12,... "sliderstep",[1/1000,1/10],... "min",0,"max",1/15,"value",gam,... "Callback","draw","tag","gamma"); uicontrol("style","text",... "string","$\gamma$",... "units","normalized",... "Position", [0.9,0.125,0.05,0.08],... "BackgroundColor", [1,1,1],... "HorizontalAlignment","center"); end end clf draw(0.3,1/15) Le 30/03/2020 ? 02:14, Heinz Nabielek a ?crit : Colleagues: is there an straightforward Scilab approach for solving the three coupled nonlinear differential equations of first order given by the Standard Model of Epidemics? S= number Susceptible: S'=-aSI I= number Infected: I'=aSI - bI R= number Recovered: R'=bI whereby 'a' is the transmission coefficient, 'b' the recovery factor (after Reed-Frost 1928). Initial values for S, I, R are available. Thank you Heinz _______________________________________________ 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 fmiyara at fceia.unr.edu.ar Mon Mar 30 11:56:32 2020 From: fmiyara at fceia.unr.edu.ar (Federico Miyara) Date: Mon, 30 Mar 2020 06:56:32 -0300 Subject: [Scilab-users] Scilab 6.1 too slow to list large vectors Message-ID: Dear All, I have observed that Scilab 6.1 seems to have a regression respect to 6.0.2. Sometimes one forgets to put semicolon after the coputation of a vector with tens of thousands components. Scilab 6.0.2 listed all the components very fast. That was nice because one hadn't to cancel the computation, it took about 1 s. With 6.1 it takes much longer. For instance Fs = 44100 T = 2.5 t = [0:T*Fs]/Fs; ximp = exp(-t/0.3).*rand(t,"normal") + 0.004*rand(t,"normal"); tic ximp = ximp(:) toc This takes 1.36 s in 6.0.2 The same code in 6.1 takes 182 s Any idea why? I know I can cancel at any moment the script execution, but if there were a process that took a lot of time one wouldn't be willing to stop it... Regards, Federico Miyara -------------- next part -------------- An HTML attachment was scrubbed... URL: From amonmayr at laas.fr Mon Mar 30 14:05:14 2020 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Mon, 30 Mar 2020 14:05:14 +0200 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ICBTY2lsYWIgNi4xICB0b28g?= =?utf-8?q?slow_to_list_large_vectors?= In-Reply-To: Message-ID: <26db-5e81e080-27-4ac42000@30312977> Hello Frederico, I can confirm this (6.0.2 vs 6.1) on linux Ubuntu 18.04 64bits: 6.0.2 -> ~1s 6.1.0 -> ~50s Could you fill a bug report? Antoine Le Lundi, Mars 30, 2020 11:56 CEST, Federico Miyara a ?crit: > > Dear All, > > I have observed that Scilab 6.1 seems to have a regression respect to > 6.0.2. Sometimes one forgets to put semicolon after the coputation of a > vector with tens of thousands components. Scilab 6.0.2 listed all the > components very fast. That was nice because one hadn't to cancel the > computation, it took about 1 s. With 6.1 it takes much longer. For instance > > Fs = 44100 > T = 2.5 > t = [0:T*Fs]/Fs; > ximp = exp(-t/0.3).*rand(t,"normal") + 0.004*rand(t,"normal"); > > tic > ximp = ximp(:) > toc > > This takes 1.36 s in 6.0.2 > > The same code in 6.1 takes 182 s > > Any idea why? > > I know I can cancel at any moment the script execution, but if there > were a process that took a lot of time one wouldn't be willing to stop it... > > Regards, > > Federico Miyara From amonmayr at laas.fr Mon Mar 30 14:08:05 2020 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Mon, 30 Mar 2020 14:08:05 +0200 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ICBTY2lsYWIgNi4xICB0b28g?= =?utf-8?q?slow_to_list_large_vectors?= In-Reply-To: Message-ID: <9aa-5e81e100-73-7f5bee80@235086209> Hi again, Just tested using the cli (no window, no java): it's even more : 0.34s vs 46s. Antoine Le Lundi, Mars 30, 2020 11:56 CEST, Federico Miyara a ?crit: > > Dear All, > > I have observed that Scilab 6.1 seems to have a regression respect to > 6.0.2. Sometimes one forgets to put semicolon after the coputation of a > vector with tens of thousands components. Scilab 6.0.2 listed all the > components very fast. That was nice because one hadn't to cancel the > computation, it took about 1 s. With 6.1 it takes much longer. For instance > > Fs = 44100 > T = 2.5 > t = [0:T*Fs]/Fs; > ximp = exp(-t/0.3).*rand(t,"normal") + 0.004*rand(t,"normal"); > > tic > ximp = ximp(:) > toc > > This takes 1.36 s in 6.0.2 > > The same code in 6.1 takes 182 s > > Any idea why? > > I know I can cancel at any moment the script execution, but if there > were a process that took a lot of time one wouldn't be willing to stop it... > > Regards, > > Federico Miyara From heinznabielek at me.com Mon Mar 30 14:38:21 2020 From: heinznabielek at me.com (Heinz Nabielek) Date: Mon, 30 Mar 2020 14:38:21 +0200 Subject: [Scilab-users] Corona modelling In-Reply-To: References: <61797769-8CEB-4391-8C95-A5C56438B43B@me.com> Message-ID: <8F119C47-20CC-4A2E-A732-B049E1DA916D@me.com> > On 30.03.2020, at 08:13, St?phane Mottelet wrote: > > Hello Heinz, > > Here is an interactive version (made for my children last week...) : > > // Confinement COVID-19 ! > // Stephane MOTTELET, UTC > // Tue Mar 24 08:55:03 CET 2020.... Great many thanks: o The SIR model is great and can be readily understood. o Scilab is great: one line of code where big EXCEL sheet produced a mess. o Scilab friends and colleagues are great: instantaneous and real help. If the modelling is anywhere near to right, it will soon be over in Austria (cyan circles are recorded infections). But this is likely over-optimistic..... Heinz ______________ Dr Heinz Nabielek Sch?ttelstrasse 77A/11 A-1020 Wien, ?sterreich Tel +43 1 276 56 13 cell +43 677 616 349 22 heinznabielek at me.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-1.png Type: image/png Size: 16116 bytes Desc: not available URL: From vvp at tu-sofia.bg Mon Mar 30 16:12:33 2020 From: vvp at tu-sofia.bg (Vesela Pasheva) Date: Mon, 30 Mar 2020 17:12:33 +0300 Subject: [Scilab-users] Corona modelling In-Reply-To: <8F119C47-20CC-4A2E-A732-B049E1DA916D@me.com> References: <61797769-8CEB-4391-8C95-A5C56438B43B@me.com> <8F119C47-20CC-4A2E-A732-B049E1DA916D@me.com> Message-ID: <50bc6c4cd367b06a3a314832255faddc@tu-sofia.bg> Hello colleagues, I would like to know whether the variable D of dead persons could be included in the model considered. Up till now the model considers the variables S - susceptible, I - infected and R - recovered. Where do the Dead persons D go. Of course i such case the system will be of four differential equations. Best regards Vesela ?? 30-03-2020 15:38, Heinz Nabielek ??????: >> On 30.03.2020, at 08:13, St?phane Mottelet >> wrote: > >> Hello Heinz, >> >> Here is an interactive version (made for my children last week...) : >> >> // Confinement COVID-19 ! >> // Stephane MOTTELET, UTC >> // Tue Mar 24 08:55:03 CET 2020.... > > Great many thanks: > > o The SIR model is great and can be readily understood. > > o Scilab is great: one line of code where big EXCEL sheet produced a > mess. > > o Scilab friends and colleagues are great: instantaneous and real > help. > > If the modelling is anywhere near to right, it will soon be over in > Austria (cyan circles are recorded infections). But this is likely > over-optimistic..... > Heinz > > ______________ > Dr Heinz Nabielek > Sch?ttelstrasse 77A/11 > A-1020 Wien, ?sterreich > Tel +43 1 276 56 13 > cell +43 677 616 349 22 > heinznabielek at me.com > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From jrafaelbguerra at hotmail.com Mon Mar 30 18:46:35 2020 From: jrafaelbguerra at hotmail.com (Rafael Guerra) Date: Mon, 30 Mar 2020 16:46:35 +0000 Subject: [Scilab-users] Corona modelling In-Reply-To: <50bc6c4cd367b06a3a314832255faddc@tu-sofia.bg> References: <61797769-8CEB-4391-8C95-A5C56438B43B@me.com> <8F119C47-20CC-4A2E-A732-B049E1DA916D@me.com> <50bc6c4cd367b06a3a314832255faddc@tu-sofia.bg> Message-ID: Hi, In Wikipedia article " Mathematical modelling of infectious disease " it says that people counted in R have been infected and removed from the disease due to immunization or death. I am not an expert but the fatality ratio could be defined as a percentage of the people infected 'I'. Regards, Rafael -----Original Message----- From: users On Behalf Of Vesela Pasheva Sent: Monday, March 30, 2020 5:13 PM To: Users mailing list for Scilab Subject: Re: [Scilab-users] Corona modelling Hello colleagues, I would like to know whether the variable D of dead persons could be included in the model considered. Up till now the model considers the variables S - susceptible, I - infected and R - recovered. Where do the Dead persons D go. Of course i such case the system will be of four differential equations. Best regards Vesela ?? 30-03-2020 15:38, Heinz Nabielek ??????: >> On 30.03.2020, at 08:13, St?phane Mottelet >> wrote: > >> Hello Heinz, >> >> Here is an interactive version (made for my children last week...) : >> >> // Confinement COVID-19 ! >> // Stephane MOTTELET, UTC >> // Tue Mar 24 08:55:03 CET 2020.... > > Great many thanks: > > o The SIR model is great and can be readily understood. > > o Scilab is great: one line of code where big EXCEL sheet produced a > mess. > > o Scilab friends and colleagues are great: instantaneous and real > help. > > If the modelling is anywhere near to right, it will soon be over in > Austria (cyan circles are recorded infections). But this is likely > over-optimistic..... > Heinz > > ______________ > Dr Heinz Nabielek > Sch?ttelstrasse 77A/11 > A-1020 Wien, ?sterreich > Tel +43 1 276 56 13 > cell +43 677 616 349 22 > heinznabielek at me.com > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users _______________________________________________ users mailing list users at lists.scilab.org http://lists.scilab.org/mailman/listinfo/users From heinznabielek at me.com Mon Mar 30 18:57:11 2020 From: heinznabielek at me.com (Heinz Nabielek) Date: Mon, 30 Mar 2020 18:57:11 +0200 Subject: [Scilab-users] Corona modelling In-Reply-To: <50bc6c4cd367b06a3a314832255faddc@tu-sofia.bg> References: <61797769-8CEB-4391-8C95-A5C56438B43B@me.com> <8F119C47-20CC-4A2E-A732-B049E1DA916D@me.com> <50bc6c4cd367b06a3a314832255faddc@tu-sofia.bg> Message-ID: It is generally assumed that 1% of the infected will die. But that would not be part of the modelling, depends mainly on local health services. Heinz > On 30.03.2020, at 16:12, Vesela Pasheva wrote: > > Hello colleagues, > > I would like to know whether the variable D of dead persons could be included in the model considered. Up till now the model considers the variables S - susceptible, I - infected and R - recovered. Where do the Dead persons D go. > Of course i such case the system will be of four differential equations. > > Best regards > > Vesela > > ?? 30-03-2020 15:38, Heinz Nabielek ??????: >>> On 30.03.2020, at 08:13, St?phane Mottelet >>> wrote: >>> Hello Heinz, >>> Here is an interactive version (made for my children last week...) : >>> // Confinement COVID-19 ! >>> // Stephane MOTTELET, UTC >>> // Tue Mar 24 08:55:03 CET 2020.... >> Great many thanks: >> o The SIR model is great and can be readily understood. >> o Scilab is great: one line of code where big EXCEL sheet produced a >> mess. >> o Scilab friends and colleagues are great: instantaneous and real >> help. >> If the modelling is anywhere near to right, it will soon be over in >> Austria (cyan circles are recorded infections). But this is likely >> over-optimistic..... >> Heinz >> ______________ >> Dr Heinz Nabielek >> Sch?ttelstrasse 77A/11 >> A-1020 Wien, ?sterreich >> Tel +43 1 276 56 13 >> cell +43 677 616 349 22 >> heinznabielek at me.com >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> http://lists.scilab.org/mailman/listinfo/users > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From p.muehlmann at gmail.com Mon Mar 30 20:04:33 2020 From: p.muehlmann at gmail.com (P M) Date: Mon, 30 Mar 2020 20:04:33 +0200 Subject: [Scilab-users] Corona modelling In-Reply-To: References: <61797769-8CEB-4391-8C95-A5C56438B43B@me.com> <8F119C47-20CC-4A2E-A732-B049E1DA916D@me.com> <50bc6c4cd367b06a3a314832255faddc@tu-sofia.bg> Message-ID: R = recovered = people who can not infect others anymore...this includes the dead people... (or not?) there are some nice introducton videos at YouTube about this....even showing the mentioned model... numberphile: https://www.youtube.com/watch?v=k6nLfCbAzgo 3brown1blue: https://www.youtube.com/watch?v=gxAaO2rsdIs Best regards, Philipp Am Mo., 30. M?rz 2020 um 18:57 Uhr schrieb Heinz Nabielek < heinznabielek at me.com>: > It is generally assumed that 1% of the infected will die. But that would > not be part of the modelling, depends mainly on local health services. > > Heinz > > > On 30.03.2020, at 16:12, Vesela Pasheva wrote: > > > > Hello colleagues, > > > > I would like to know whether the variable D of dead persons could be > included in the model considered. Up till now the model considers the > variables S - susceptible, I - infected and R - recovered. Where do the > Dead persons D go. > > Of course i such case the system will be of four differential equations. > > > > Best regards > > > > Vesela > > > > ?? 30-03-2020 15:38, Heinz Nabielek ??????: > >>> On 30.03.2020, at 08:13, St?phane Mottelet > >>> wrote: > >>> Hello Heinz, > >>> Here is an interactive version (made for my children last week...) : > >>> // Confinement COVID-19 ! > >>> // Stephane MOTTELET, UTC > >>> // Tue Mar 24 08:55:03 CET 2020.... > >> Great many thanks: > >> o The SIR model is great and can be readily understood. > >> o Scilab is great: one line of code where big EXCEL sheet produced a > >> mess. > >> o Scilab friends and colleagues are great: instantaneous and real > >> help. > >> If the modelling is anywhere near to right, it will soon be over in > >> Austria (cyan circles are recorded infections). But this is likely > >> over-optimistic..... > >> Heinz > >> ______________ > >> Dr Heinz Nabielek > >> Sch?ttelstrasse 77A/11 > >> A-1020 Wien, ?sterreich > >> Tel +43 1 276 56 13 > >> cell +43 677 616 349 22 > >> heinznabielek at me.com > >> _______________________________________________ > >> users mailing list > >> users at lists.scilab.org > >> http://lists.scilab.org/mailman/listinfo/users > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/users > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim at wescottdesign.com Mon Mar 30 20:37:44 2020 From: tim at wescottdesign.com (Tim Wescott) Date: Mon, 30 Mar 2020 11:37:44 -0700 Subject: [Scilab-users] Corona modelling In-Reply-To: <50bc6c4cd367b06a3a314832255faddc@tu-sofia.bg> References: <61797769-8CEB-4391-8C95-A5C56438B43B@me.com> <8F119C47-20CC-4A2E-A732-B049E1DA916D@me.com> <50bc6c4cd367b06a3a314832255faddc@tu-sofia.bg> Message-ID: <57611cfb8420333b0d08c9f1adc6e510033fb054.camel@wescottdesign.com> Someone was tagging "R" as "removed", which works if it's the aggregate of "live and no longer contagious" and "dead". Actually assessing the proportion of R depends on the local health system, and, to some extent, the size of the peak -- the main reason we're quarantining is to bring the peak down by broadening it. The percentage of 'R' that's dead people is going to depend on how burdened the health care system is in any locality. In cold-blooded mathematical terms it's just another dimension to the modeling, but it's on the output side of the differential equation; it doesn't have a great impact (as modeled) on the actual dynamics of those three variables. On Mon, 2020-03-30 at 17:12 +0300, Vesela Pasheva wrote: > Hello colleagues, > > I would like to know whether the variable D of dead persons could be > included in the model considered. Up till now the model considers > the > variables S - susceptible, I - infected and R - recovered. Where do > the > Dead persons D go. > Of course i such case the system will be of four differential > equations. > > Best regards > > Vesela > > ?? 30-03-2020 15:38, Heinz Nabielek ??????: > > > On 30.03.2020, at 08:13, St?phane Mottelet > > > wrote: > > > Hello Heinz, > > > > > > Here is an interactive version (made for my children last > > > week...) : > > > > > > // Confinement COVID-19 ! > > > // Stephane MOTTELET, UTC > > > // Tue Mar 24 08:55:03 CET 2020.... > > > > Great many thanks: > > > > o The SIR model is great and can be readily understood. > > > > o Scilab is great: one line of code where big EXCEL sheet produced > > a > > mess. > > > > o Scilab friends and colleagues are great: instantaneous and real > > help. > > > > If the modelling is anywhere near to right, it will soon be over in > > Austria (cyan circles are recorded infections). But this is likely > > over-optimistic..... > > Heinz > > > > ______________ > > Dr Heinz Nabielek > > Sch?ttelstrasse 77A/11 > > A-1020 Wien, ?sterreich > > Tel +43 1 276 56 13 > > cell +43 677 616 349 22 > > heinznabielek at me.com > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/users > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -- Tim Wescott www.wescottdesign.com Control & Communications systems, circuit & software design. Phone: 503.631.7815 Cell: 503.349.8432 From heinznabielek at me.com Mon Mar 30 21:05:00 2020 From: heinznabielek at me.com (Heinz Nabielek) Date: Mon, 30 Mar 2020 21:05:00 +0200 Subject: [Scilab-users] Corona modelling In-Reply-To: <57611cfb8420333b0d08c9f1adc6e510033fb054.camel@wescottdesign.com> References: <61797769-8CEB-4391-8C95-A5C56438B43B@me.com> <8F119C47-20CC-4A2E-A732-B049E1DA916D@me.com> <50bc6c4cd367b06a3a314832255faddc@tu-sofia.bg> <57611cfb8420333b0d08c9f1adc6e510033fb054.camel@wescottdesign.com> Message-ID: <9219BCF9-E0C5-4202-A837-F39598BA7F33@me.com> > On 30.03.2020, at 20:37, Tim Wescott wrote: > > Someone was tagging "R" as "removed", which works if it's the aggregate > of "live and no longer contagious" and "dead". > > Actually assessing the proportion of R depends on the local health > system, and, to some extent, the size of the peak -- the main reason > we're quarantining is to bring the peak down by broadening it. The usual display of the INFECTED population as a series of normal distributions is not quite right, but a good enough approximation. It is correct, that the reduction of the transmission coefficient delays the peak and makes it smaller...... Heinz > The > percentage of 'R' that's dead people is going to depend on how burdened > the health care system is in any locality. > > In cold-blooded mathematical terms it's just another dimension to the > modeling, but it's on the output side of the differential equation; it > doesn't have a great impact (as modeled) on the actual dynamics of > those three variables. > > On Mon, 2020-03-30 at 17:12 +0300, Vesela Pasheva wrote: >> Hello colleagues, >> >> I would like to know whether the variable D of dead persons could be >> included in the model considered. Up till now the model considers >> the >> variables S - susceptible, I - infected and R - recovered. Where do >> the >> Dead persons D go. >> Of course i such case the system will be of four differential >> equations. >> >> Best regards >> >> Vesela >> >> ?? 30-03-2020 15:38, Heinz Nabielek ??????: >>>> On 30.03.2020, at 08:13, St?phane Mottelet >>>> wrote: >>>> Hello Heinz, >>>> >>>> Here is an interactive version (made for my children last >>>> week...) : >>>> >>>> // Confinement COVID-19 ! >>>> // Stephane MOTTELET, UTC >>>> // Tue Mar 24 08:55:03 CET 2020.... >>> >>> Great many thanks: >>> >>> o The SIR model is great and can be readily understood. >>> >>> o Scilab is great: one line of code where big EXCEL sheet produced >>> a >>> mess. >>> >>> o Scilab friends and colleagues are great: instantaneous and real >>> help. >>> >>> If the modelling is anywhere near to right, it will soon be over in >>> Austria (cyan circles are recorded infections). But this is likely >>> over-optimistic..... >>> Heinz >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-4.png Type: image/png Size: 46440 bytes Desc: not available URL: From fmiyara at fceia.unr.edu.ar Mon Mar 30 23:22:45 2020 From: fmiyara at fceia.unr.edu.ar (Federico Miyara) Date: Mon, 30 Mar 2020 18:22:45 -0300 Subject: [Scilab-users] ?==?utf-8?q? Scilab 6.1 too slow to list large vectors In-Reply-To: <26db-5e81e080-27-4ac42000@30312977> References: <26db-5e81e080-27-4ac42000@30312977> Message-ID: <44349a13-6061-4a58-d903-239f967bc6a7@fceia.unr.edu.ar> Antoine, Thank you for testing. I have filed bug 16397: https://bugzilla.scilab.org/show_bug.cgi?id=16397 Regards, Federico Miyara On 30/03/2020 09:05, Antoine Monmayrant wrote: > Hello Frederico, > > I can confirm this (6.0.2 vs 6.1) on linux Ubuntu 18.04 64bits: > > 6.0.2 -> ~1s > 6.1.0 -> ~50s > > Could you fill a bug report? > > Antoine > > > Le Lundi, Mars 30, 2020 11:56 CEST, Federico Miyara a ?crit: > >> Dear All, >> >> I have observed that Scilab 6.1 seems to have a regression respect to >> 6.0.2. Sometimes one forgets to put semicolon after the coputation of a >> vector with tens of thousands components. Scilab 6.0.2 listed all the >> components very fast. That was nice because one hadn't to cancel the >> computation, it took about 1 s. With 6.1 it takes much longer. For instance >> >> Fs = 44100 >> T = 2.5 >> t = [0:T*Fs]/Fs; >> ximp = exp(-t/0.3).*rand(t,"normal") + 0.004*rand(t,"normal"); >> >> tic >> ximp = ximp(:) >> toc >> >> This takes 1.36 s in 6.0.2 >> >> The same code in 6.1 takes 182 s >> >> Any idea why? >> >> I know I can cancel at any moment the script execution, but if there >> were a process that took a lot of time one wouldn't be willing to stop it... >> >> Regards, >> >> Federico Miyara > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > > From jdb61858 at suoox.com Tue Mar 31 00:18:26 2020 From: jdb61858 at suoox.com (RolandB) Date: Mon, 30 Mar 2020 15:18:26 -0700 (MST) Subject: [Scilab-users] Corona modelling In-Reply-To: <9219BCF9-E0C5-4202-A837-F39598BA7F33@me.com> References: <61797769-8CEB-4391-8C95-A5C56438B43B@me.com> <8F119C47-20CC-4A2E-A732-B049E1DA916D@me.com> <50bc6c4cd367b06a3a314832255faddc@tu-sofia.bg> <57611cfb8420333b0d08c9f1adc6e510033fb054.camel@wescottdesign.com> <9219BCF9-E0C5-4202-A837-F39598BA7F33@me.com> Message-ID: <1585606706577-0.post@n3.nabble.com> As there have already been some cases where persons have been infected twice, you would have to take into account that only a finite percentage of infected people become immune and that this immunity might also only last some finite time. Another thought experiment would be to randomly test some percentage of people every some days and remove them by isolation in case they are infected. Further, after someone becomes ill or is tested positive, you could determine the people he was in contact with (to a certain percentage, because they would not remember everyone they had been in contact with) and have them tested too. Aside from the mathematical problem, I think in order to be able to return to a somewhat normal life without a high risk of provoking another wave (maybe several of them), we need tests that detect the virus directly (antigen or DNA tests, as antibodies take too long to rise) and we need them ridiculously cheap. We need to be able to test everyone at least twice a week, preferably every other day or even every day. I think I have seen Influenza rapid antigen tests for about 3,5 Euro in some tens quantities. If one were to produce them in hundreds of millions per day (you know how fast the Chinese can ramp up factories if there is a demand), such a test should be able to be produced for less than an Euro. Combined with an app that tracks everyone's path (I know, protection of privacy is important, but there should be a way to ensure privacy while allowing to be able to detect if one has been in close vicinity of an infected person), that should allow us to avoid an oscillating cycle of reinfection waves. -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From stephane.mottelet at utc.fr Tue Mar 31 10:23:43 2020 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Tue, 31 Mar 2020 10:23:43 +0200 Subject: [Scilab-users] Scilab 6.1 too slow to list large vectors In-Reply-To: References: Message-ID: Hi Frederico, Thanks for reporting. Can you test if the regression also holds for matrices ? S. Le 30/03/2020 ? 11:56, Federico Miyara a ?crit?: > > Fs = 44100 > T = 2.5 > t = [0:T*Fs]/Fs; > ximp = exp(-t/0.3).*rand(t,"normal") + 0.004*rand(t,"normal"); > > tic > ximp = ximp(:) > toc -- 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 fmiyara at fceia.unr.edu.ar Tue Mar 31 11:36:02 2020 From: fmiyara at fceia.unr.edu.ar (Federico Miyara) Date: Tue, 31 Mar 2020 06:36:02 -0300 Subject: [Scilab-users] Scilab 6.1 too slow to list large vectors In-Reply-To: References: Message-ID: <1e4b1837-7346-2d94-87b7-5bfb7a8f72b8@fceia.unr.edu.ar> St?phane, I simplified and diversified the test: tic u = rand(100,1000) toc takes 16 s in 6.1 10 s in 6.0.2 tic u = u(:)' toc takes 66 s in 6.1 1.29 s in 6.0.2 tic u = u(:) toc takes 107 s in 6.1 1.52 s in 6.0.2 tic u = matrix(u,1000,100) toc takes 16 s in 6.1 10 s in 6.0.2 tic u = matrix(u,100, 100, 10) toc takes 0.5 s in 6.1 0.5 s in 6.0.2 Seems as if vertical (many line feeds) print took more time than horizontal print. Regards, Federico Miyara On 31/03/2020 05:23, St?phane Mottelet wrote: > > Hi Frederico, > > Thanks for reporting. Can you test if the regression also holds for > matrices ? > > S. > > Le 30/03/2020 ? 11:56, Federico Miyara a ?crit?: >> >> Fs = 44100 >> T = 2.5 >> t = [0:T*Fs]/Fs; >> ximp = exp(-t/0.3).*rand(t,"normal") + 0.004*rand(t,"normal"); >> >> tic >> ximp = ximp(:) >> toc > -- > 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 amonmayr at laas.fr Tue Mar 31 11:55:18 2020 From: amonmayr at laas.fr (Antoine Monmayrant) Date: Tue, 31 Mar 2020 11:55:18 +0200 Subject: [Scilab-users] =?utf-8?b?Pz09P3V0Zi04P3E/ICBTY2lsYWIgNi4xICB0b28g?= =?utf-8?q?slow_to_list_large_vectors?= In-Reply-To: <1e4b1837-7346-2d94-87b7-5bfb7a8f72b8@fceia.unr.edu.ar> Message-ID: <263b-5e831380-f-5086e980@69288983> Hello, I also ran some tests and it seems that the regression is clearly line-based: ie the regression is worse for vector than for matrix because there more lines to print to display a vector than a matrix of similar length. See my test code below. n1=300; n2=100; mat=rand(n1,n2); tn=[]; /* Ctrl+E the code below several times*/ tic mat // matrix //mat(:) // vector t=toc() tn=[tn,t]; disp('---------') disp('N_run = '+string(length(tn))) disp('T='+string(mean(tn))+'+/-'+string(stdev(tn))); /* 6.0.2 matrix N_run = 20 T=0.6392742+/-0.056698 1.6x slower but plotting 4 values per line ie 4x less lines to plot than for the matrix version 6.1.0 matrix N_run = 10 T=1.0335109+/-0.0317414 6.0.2 vector mat(:) N_run = 20 T=0.4943449+/-0.0662727 6.1.0 vector mat(:) N_run = 10 T=3.800698+/-0.1121251 7.7x slower ie same slow down per line than for the vector version as we plot 4 values per line so 4x more lines */ Le Mardi, Mars 31, 2020 11:36 CEST, Federico Miyara a ?crit: > > St?phane, > > I simplified and diversified the test: > > tic > u = rand(100,1000) > toc > > takes > 16 s in 6.1 > 10 s in 6.0.2 > > tic > u = u(:)' > toc > > takes > 66 s in 6.1 > 1.29 s in 6.0.2 > > tic > u = u(:) > toc > > takes > 107 s in 6.1 > 1.52 s in 6.0.2 > > tic > u = matrix(u,1000,100) > toc > > takes > 16 s in 6.1 > 10 s in 6.0.2 > > tic > u = matrix(u,100, 100, 10) > toc > > takes > 0.5 s in 6.1 > 0.5 s in 6.0.2 > > Seems as if vertical (many line feeds) print took more time than > horizontal print. > > Regards, > > Federico Miyara > > > > On 31/03/2020 05:23, St?phane Mottelet wrote: > > > > Hi Frederico, > > > > Thanks for reporting. Can you test if the regression also holds for > > matrices ? > > > > S. > > > > Le 30/03/2020 ? 11:56, Federico Miyara a ?crit?: > >> > >> Fs = 44100 > >> T = 2.5 > >> t = [0:T*Fs]/Fs; > >> ximp = exp(-t/0.3).*rand(t,"normal") + 0.004*rand(t,"normal"); > >> > >> tic > >> ximp = ximp(:) > >> toc > > -- > > 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 > From heinznabielek at me.com Tue Mar 31 12:03:37 2020 From: heinznabielek at me.com (Heinz Nabielek) Date: Tue, 31 Mar 2020 12:03:37 +0200 Subject: [Scilab-users] Scilab 6.1 too slow to list large vectors In-Reply-To: <1e4b1837-7346-2d94-87b7-5bfb7a8f72b8@fceia.unr.edu.ar> References: <1e4b1837-7346-2d94-87b7-5bfb7a8f72b8@fceia.unr.edu.ar> Message-ID: On my iMac macOS Catalina 10.15.3 Processor Name: Quad-Core Intel Core i7 Processor Speed: 3.1 GHz Darwin Kernel Version 19.3.0: Thu Jan 9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64 x86_64 Should anybody be interested.... Heinz 2.107417 0.564745 tic u = u(:) toc 0.557869 tic u = matrix(u,1000,100) toc 2.194178 tic u = matrix(u,100, 100, 10) toc 0.069732 > On 31.03.2020, at 11:36, Federico Miyara wrote: > > > St?phane, > > I simplified and diversified the test: > > tic > u = rand(100,1000) > toc > > takes > 16 s in 6.1 > 10 s in 6.0.2 > > tic > u = u(:)' > toc > > takes > 66 s in 6.1 > 1.29 s in 6.0.2 > > tic > u = u(:) > toc > > takes > 107 s in 6.1 > 1.52 s in 6.0.2 > > tic > u = matrix(u,1000,100) > toc > > takes > 16 s in 6.1 > 10 s in 6.0.2 > > tic > u = matrix(u,100, 100, 10) > toc > > takes > 0.5 s in 6.1 > 0.5 s in 6.0.2 > > Seems as if vertical (many line feeds) print took more time than horizontal print. > > Regards, > > Federico Miyara > > > > On 31/03/2020 05:23, St?phane Mottelet wrote: >> Hi Frederico, >> >> Thanks for reporting. Can you test if the regression also holds for matrices ? >> >> S. >> >> Le 30/03/2020 ? 11:56, Federico Miyara a ?crit : >>> >>> Fs = 44100 >>> T = 2.5 >>> t = [0:T*Fs]/Fs; >>> ximp = exp(-t/0.3).*rand(t,"normal") + 0.004*rand(t,"normal"); >>> >>> >>> >>> tic >>> ximp = ximp(:) >>> toc >>> >>> From perrichon.pierre at wanadoo.fr Tue Mar 31 12:05:00 2020 From: perrichon.pierre at wanadoo.fr (Perrichon) Date: Tue, 31 Mar 2020 12:05:00 +0200 Subject: [Scilab-users] ?==?utf-8?q? Scilab 6.1 too slow to list large vectors In-Reply-To: <263b-5e831380-f-5086e980@69288983> References: <1e4b1837-7346-2d94-87b7-5bfb7a8f72b8@fceia.unr.edu.ar> <263b-5e831380-f-5086e980@69288983> Message-ID: Hello, On another way, see bugzilla #16359 in Xcos I've provided the program to ESI Results : Xcos Scilab 5.5.2 : Dur?e de la simulation : 258.3 s Xcos Sciab 6.1.0 : Dur?e de la simulation : 4353.4 s Stack? Mallloc ? Regards Before printing, think about ENVIRONMENTAL responsabity -----Message d'origine----- De : users De la part de Antoine Monmayrant Envoy? : mardi 31 mars 2020 11:55 ? : Users mailing list for Scilab Objet : Re: [Scilab-users] ?==?utf-8?q? Scilab 6.1 too slow to list large vectors Hello, I also ran some tests and it seems that the regression is clearly line-based: ie the regression is worse for vector than for matrix because there more lines to print to display a vector than a matrix of similar length. See my test code below. n1=300; n2=100; mat=rand(n1,n2); tn=[]; /* Ctrl+E the code below several times*/ tic mat // matrix //mat(:) // vector t=toc() tn=[tn,t]; disp('---------') disp('N_run = '+string(length(tn))) disp('T='+string(mean(tn))+'+/-'+string(stdev(tn))); /* 6.0.2 matrix N_run = 20 T=0.6392742+/-0.056698 1.6x slower but plotting 4 values per line ie 4x less lines to plot than for the matrix version 6.1.0 matrix N_run = 10 T=1.0335109+/-0.0317414 6.0.2 vector mat(:) N_run = 20 T=0.4943449+/-0.0662727 6.1.0 vector mat(:) N_run = 10 T=3.800698+/-0.1121251 7.7x slower ie same slow down per line than for the vector version as we plot 4 values per line so 4x more lines */ Le Mardi, Mars 31, 2020 11:36 CEST, Federico Miyara a ?crit: > > St?phane, > > I simplified and diversified the test: > > tic > u = rand(100,1000) > toc > > takes > 16 s in 6.1 > 10 s in 6.0.2 > > tic > u = u(:)' > toc > > takes > 66 s in 6.1 > 1.29 s in 6.0.2 > > tic > u = u(:) > toc > > takes > 107 s in 6.1 > 1.52 s in 6.0.2 > > tic > u = matrix(u,1000,100) > toc > > takes > 16 s in 6.1 > 10 s in 6.0.2 > > tic > u = matrix(u,100, 100, 10) > toc > > takes > 0.5 s in 6.1 > 0.5 s in 6.0.2 > > Seems as if vertical (many line feeds) print took more time than > horizontal print. > > Regards, > > Federico Miyara > > > > On 31/03/2020 05:23, St?phane Mottelet wrote: > > > > Hi Frederico, > > > > Thanks for reporting. Can you test if the regression also holds for > > matrices ? > > > > S. > > > > Le 30/03/2020 ? 11:56, Federico Miyara a ?crit : > >> > >> Fs = 44100 > >> T = 2.5 > >> t = [0:T*Fs]/Fs; > >> ximp = exp(-t/0.3).*rand(t,"normal") + 0.004*rand(t,"normal"); > >> > >> tic > >> ximp = ximp(:) > >> toc > > -- > > 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 > _______________________________________________ users mailing list users at lists.scilab.org http://lists.scilab.org/mailman/listinfo/users From Clement.David at esi-group.com Tue Mar 31 13:41:00 2020 From: Clement.David at esi-group.com (=?utf-8?B?Q2zDqW1lbnQgRGF2aWQ=?=) Date: Tue, 31 Mar 2020 11:41:00 +0000 Subject: [Scilab-users] ?==?utf-8?q? Scilab 6.1 too slow to list large vectors In-Reply-To: References: <1e4b1837-7346-2d94-87b7-5bfb7a8f72b8@fceia.unr.edu.ar> <263b-5e831380-f-5086e980@69288983> Message-ID: Hello Pierre, FYI your reported issue is probably not related at all to the matrix printing in the console. The Xcos simulation engine is kind of a gateway from the Scilab interpreter point of view (like optim() for instance), let's keep them separate issues. Thanks, -- Cl?ment > -----Original Message----- > From: users On Behalf Of Perrichon > Sent: Tuesday, March 31, 2020 12:05 PM > To: 'Users mailing list for Scilab' > Subject: Re: [Scilab-users] ?==?utf-8?q? Scilab 6.1 too slow to list large vectors > > Hello, > > On another way, see bugzilla #16359 in Xcos > > I've provided the program to ESI > > Results : > Xcos Scilab 5.5.2 : > Dur?e de la simulation : 258.3 s > > Xcos Sciab 6.1.0 : > Dur?e de la simulation : 4353.4 s > > Stack? Mallloc ? > > Regards > > > > Before printing, think about ENVIRONMENTAL responsabity > > > -----Message d'origine----- > De : users De la part de Antoine Monmayrant > Envoy? : mardi 31 mars 2020 11:55 ? : Users mailing list for Scilab > Objet : Re: [Scilab-users] ?==?utf-8?q? Scilab 6.1 too > slow to list large vectors > > Hello, > > I also ran some tests and it seems that the regression is clearly line-based: ie the > regression is worse for vector than for matrix because there more lines to print > to display a vector than a matrix of similar length. > See my test code below. > > > n1=300; > n2=100; > mat=rand(n1,n2); > tn=[]; > > /* Ctrl+E the code below several times*/ > > tic > mat // matrix > //mat(:) // vector > t=toc() > tn=[tn,t]; > > disp('---------') > disp('N_run = '+string(length(tn))) > disp('T='+string(mean(tn))+'+/-'+string(stdev(tn))); > > > /* > 6.0.2 matrix > N_run = 20 > T=0.6392742+/-0.056698 > 1.6x slower but plotting 4 values per line ie 4x less lines to plot than for the > matrix version > > 6.1.0 matrix > N_run = 10 > T=1.0335109+/-0.0317414 > > 6.0.2 vector mat(:) > N_run = 20 > T=0.4943449+/-0.0662727 > > 6.1.0 vector mat(:) > N_run = 10 > T=3.800698+/-0.1121251 > 7.7x slower ie same slow down per line than for the vector version as we plot 4 > values per line so 4x more lines > > */ > > > > Le Mardi, Mars 31, 2020 11:36 CEST, Federico Miyara > a ?crit: > > > > > St?phane, > > > > I simplified and diversified the test: > > > > tic > > u = rand(100,1000) > > toc > > > > takes > > 16 s in 6.1 > > 10 s in 6.0.2 > > > > tic > > u = u(:)' > > toc > > > > takes > > 66 s in 6.1 > > 1.29 s in 6.0.2 > > > > tic > > u = u(:) > > toc > > > > takes > > 107 s in 6.1 > > 1.52 s in 6.0.2 > > > > tic > > u = matrix(u,1000,100) > > toc > > > > takes > > 16 s in 6.1 > > 10 s in 6.0.2 > > > > tic > > u = matrix(u,100, 100, 10) > > toc > > > > takes > > 0.5 s in 6.1 > > 0.5 s in 6.0.2 > > > > Seems as if vertical (many line feeds) print took more time than > > horizontal print. > > > > Regards, > > > > Federico Miyara > > > > > > > > On 31/03/2020 05:23, St?phane Mottelet wrote: > > > > > > Hi Frederico, > > > > > > Thanks for reporting. Can you test if the regression also holds for > > > matrices ? > > > > > > S. > > > > > > Le 30/03/2020 ? 11:56, Federico Miyara a ?crit : > > >> > > >> Fs = 44100 > > >> T = 2.5 > > >> t = [0:T*Fs]/Fs; > > >> ximp = exp(-t/0.3).*rand(t,"normal") + 0.004*rand(t,"normal"); > > >> > > >> tic > > >> ximp = ximp(:) > > >> toc > > > -- > > > 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 > > > > _______________________________________________ > 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