From samuel.enibe at unn.edu.ng Tue Sep 1 11:53:40 2020 From: samuel.enibe at unn.edu.ng (Samuel Enibe) Date: Tue, 1 Sep 2020 10:53:40 +0100 Subject: [Scilab-users] genlib crashes in SCILAB 6.1.0 under UBUNTU 18.04 Message-ID: I have been able to solve the problem. A particular function that was not well formatted was detected and edited. Thank you very much. Samuel Enibe On Mon, 31 Aug 2020, 18:33 Samuel Enibe, wrote: > > I start SCILAB 6.1.0 under the UBUNTU 18.04 OPERATING SYSTEM from the > console. This is because invoking it otherwise does not work. > > Each time I execute the SCILAB function genlib, the SCILAB crashes after > generating the binaries for some of the user defined functions. I will > have to restart the SCILAB again.to proceed. The problem does not occur > when I execute the same genlib in the same way with SCILAB 5.5.2 under the > same operating system. > > Any solution to this problem will be appreciated. > > Samuel Enibe > > > > On Mon, 31 Aug 2020, 17:23 Samuel Enibe, wrote: > >> I start SCILAB 6.1.0 under the UBUNTU 18.04 OPERATING SYSTEM from the >> console. This is because invoking it otherwise does not work. >> >> Each time I execute the SCILAB function genlib, the SCILAB crashes and I >> will have to restart it again. >> >> Any solution to this problem will be appreciated. >> >> Samuel Enibe >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephane.mottelet at utc.fr Tue Sep 1 13:07:21 2020 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Tue, 1 Sep 2020 13:07:21 +0200 Subject: [Scilab-users] [Scilab-Dev] readxlsx In-Reply-To: References: Message-ID: Hello Eric, I finally created an atoms module name "xlreadwrite". As it is based on a Java library, it will never be integrated in Scilab, as the provided features (read/write xls and xlsx files in a transparent way) should be available in -nwni mode. But in the meantime I think that this module can help some of us. You can give it a try with --> atomsInstall xlreadwrite and experiment the help examples and your own files, especially xlsx ones.? For the records, this module fixes the following bugs and/or feature requests: http://bugzilla.scilab.org/show_bug.cgi?id=7063 http://bugzilla.scilab.org/show_bug.cgi?id=7963 http://bugzilla.scilab.org/show_bug.cgi?id=13948 http://bugzilla.scilab.org/show_bug.cgi?id=14216 S. Le 25/08/2019 ? 17:05, ?ric Dubois a ?crit?: > Hello > > Is there a plan to update readxls to a readxlsx programm that coulb > bne suitabel to the (not so) recent xlsx format? > > Rega > > > > Garanti sans virus. www.avast.com > > > > > _______________________________________________ > dev mailing list > dev at lists.scilab.org > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/dev -- 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 stepan.podhorsky at gmail.com Wed Sep 9 12:55:28 2020 From: stepan.podhorsky at gmail.com (Steve) Date: Wed, 9 Sep 2020 03:55:28 -0700 (MST) Subject: [Scilab-users] How to correctly simulate sample and hold process? Message-ID: <1599648928679-0.post@n3.nabble.com> Hello, I have been developing a simulation in Scilab/Xcos 5.5.2. The simulation basically consists of two main superblocks: a) /state space model of a dynamic system in the continuous time domain/ - block is based on the EXPRESSION blocks b) /discrete observer for the dynamic system from point a)/ - block is based on the CBLOCK block The input signals for the discrete observer are the outputs of the dynamic system from a) passing through the SAMPLEHOLD_m blocks. The solver has following setting: I have encountered following behavior which I don't understand: 1) In case I use one clock source (SampleCLK with Sample time set to 1 us and Offset set to 0) for the timing of the SAMPLEHOLD_m blocks and another clock source (CLOCK_c with period set to 100 us and Initialization time set to 0) for the timing of the CSCOPE blocks the output of the observer follows the outputs of the model very well. 2) In case I use both the clock sources from 1) but the sample time in the SampleCLK is increased to 10 us and setting of the CLOCK_c block remains the same the observer gives outputs with large estimation error. 3) In case I use one common clock source (CLOCK_c with period set to sampling period) for the timing of the SAMPLEHOLD_m blocks and for controlling of the CSCOPE blocks the observer outputs follow the outputs of the model again very well despite the fact that the sampling period is set to 10 us (which gives large estimation error in configuration in 2)). I would like to ask you for answering following questions: I. What is the cause of my observation? II. What is the correct approach for timing of the SAMPLEHOLD_m blocks in hybrid simulations? Thank you in advance for your answers. -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From danielstringarita at gmail.com Thu Sep 10 00:03:29 2020 From: danielstringarita at gmail.com (Daniel Stringari) Date: Wed, 9 Sep 2020 15:03:29 -0700 (MST) Subject: [Scilab-users] Read file (.txt) Message-ID: <1599689009071-0.post@n3.nabble.com> Good evening everyone, I'm integrating scilab with other software, so I need to read an output file (.txt), like the one attached (output). It is worth mentioning that this file does not always have the same dimensions (matrix), so I am trying to find something robust that can deal with this particularity. I tried to use the 'csvread' function and the 'read' function, but I still haven't been successful ... Any suggestions? output.txt -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From antoine.elias at scilab-enterprises.com Thu Sep 10 00:25:12 2020 From: antoine.elias at scilab-enterprises.com (antoine.elias at scilab-enterprises.com) Date: Thu, 10 Sep 2020 00:25:12 +0200 Subject: [Scilab-users] Read file (.txt) In-Reply-To: <1599689009071-0.post@n3.nabble.com> References: <1599689009071-0.post@n3.nabble.com> Message-ID: <3091a2e4-c32e-bf9a-c47e-16bb4c27161e@scilab-enterprises.com> Hello Daniel, Do you have try with "evstr" function ? data = evstr(mgetl("output.txt")); Regards, Antoine From j-lan at online.no Thu Sep 10 06:39:17 2020 From: j-lan at online.no (=?UTF-8?Q?Jan_=c3=85ge_Langeland?=) Date: Thu, 10 Sep 2020 06:39:17 +0200 Subject: [Scilab-users] Read file (.txt) In-Reply-To: <1599689009071-0.post@n3.nabble.com> References: <1599689009071-0.post@n3.nabble.com> Message-ID: <922f8707-67bc-41e8-821b-4be3b71de28b@online.no> Hi Daniel I made my own csvread, it seems to read your file OK with exec('JcsvRead3.sce', -1); M=JcsvRead3('output.txt','?? '); Brgds Jan On 2020-09-10 0:03 AM, Daniel Stringari wrote: > Good evening everyone, > > I'm integrating scilab with other software, so I need to read an output file > (.txt), like the one attached (output). > > It is worth mentioning that this file does not always have the same > dimensions (matrix), so I am trying to find something robust that can deal > with this particularity. I tried to use the 'csvread' function and the > 'read' function, but I still haven't been successful ... Any suggestions? > > output.txt > > > > > > -- > Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html > _______________________________________________ > 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 -------------- //Read CSV file -J? 2020 function M=JcsvRead3(filename,varargin) linestoread=-1;// -1 for all, argument 6 headerlines=0;//argument 7 footerlines=0;//argument 8 separator=";"//default, can be changed by argument 2. Several separators accepted decimal="."; //default, can be changed to , by argument 3 num_asc="double" // default , can be changed to "ascii" by argument 4 if argn(2)>1 t1=type(varargin(1)); if t1==10 then separator=varargin(1); else mprintf("Default separator\n") end end if argn(2)>2 t2=type(varargin(2)); if t2==10 && varargin(2)=="," then decimal="," elseif t2>0 && varargin(2)~="." mprintf("Decimal, select . or, \n"); err=return(varargin(2)) ; end; end if argn(2)>3 t3=type(varargin(3)); if t3>0 then num_asc=varargin(3) end; end if argn(2)>6 t6=type(varargin(6)); if t6>0 && varargin(6)~=[] then linestoread=varargin(6) end; end if argn(2)>7 t7=type(varargin(7)); if t7>0 && varargin(7)~=[] then headerlines=varargin(7) end; end if argn(2)>8 t8=type(varargin(8)); if t8==1 && varargin(8)~=[] then footerlines=varargin(8) end; end fid = mopen(filename,'rt'); csvline=mgetl(fid,linestoread); mclose(fid); n=size(csvline,1); select num_asc; case "double" then M(1)=1; for k=headerlines+1:n-footerlines datatemp=strtod(strsplit(csvline(k),separator),decimal); M(k-headerlines,1:length(datatemp))=datatemp'; end case "string" then M(1)=" " for k=headerlines+1:n-footerlines datatemp=strsplit(csvline(k),separator); datatemp2=datatemp M((k-headerlines),1:size(datatemp',2))=datatemp'; end else mprintf("Conversion double or string\n") err=return(num_asc); end endfunction From p.muehlmann at gmail.com Thu Sep 10 10:46:45 2020 From: p.muehlmann at gmail.com (P M) Date: Thu, 10 Sep 2020 10:46:45 +0200 Subject: [Scilab-users] Read file (.txt) In-Reply-To: <3091a2e4-c32e-bf9a-c47e-16bb4c27161e@scilab-enterprises.com> References: <1599689009071-0.post@n3.nabble.com> <3091a2e4-c32e-bf9a-c47e-16bb4c27161e@scilab-enterprises.com> Message-ID: I think csvRead is just fine. [data header] = csvRead(fname, ' ', '.', 'string', [], [], [], 0); As you may notice the data Matrix contains a lot of empty columns. This is due to the many white spaces in the text file anyways, after reading the dta in you may use evstr() to convert into doubles. BR Philipp Am Do., 10. Sept. 2020 um 04:03 Uhr schrieb < antoine.elias at scilab-enterprises.com>: > Hello Daniel, > > Do you have try with "evstr" function ? > > data = evstr(mgetl("output.txt")); > > Regards, > 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 j-lan at online.no Thu Sep 10 11:30:54 2020 From: j-lan at online.no (=?UTF-8?Q?Jan_=c3=85ge_Langeland?=) Date: Thu, 10 Sep 2020 11:30:54 +0200 Subject: [Scilab-users] Read file (.txt) In-Reply-To: References: <1599689009071-0.post@n3.nabble.com> <3091a2e4-c32e-bf9a-c47e-16bb4c27161e@scilab-enterprises.com> Message-ID: <61b10a61-a4b8-2b9a-7833-86e8c445edcf@online.no> The main problem I ran into with csvRead was reading files with a variable number of separators in each row. Then my suggested solution pads with 0. It could be changed to pad with NaN also. Using strsplit in each row allows for several separators in the same conversion.? It may still be useful to use evstr row by row instead, if the number of spaces between numbers vary. J On 2020-09-10 10:46 AM, P M wrote: > I think csvRead is just fine. > > [data header] = csvRead(fname, '', '.', 'string', [], [], [], 0); > As you may notice the data Matrix contains a lot of empty columns. > This is due to the many white spaces in the text file > anyways, after reading the dta in you may use evstr() to convert into > doubles. > BR > Philipp > > Am Do., 10. Sept. 2020 um 04:03?Uhr schrieb > >: > > Hello Daniel, > > Do you have try with "evstr" function ? > > data = evstr(mgetl("output.txt")); > > Regards, > 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 sgougeon at free.fr Thu Sep 10 22:42:01 2020 From: sgougeon at free.fr (Samuel Gougeon) Date: Thu, 10 Sep 2020 22:42:01 +0200 Subject: [Scilab-users] Read file (.txt) In-Reply-To: <1599689009071-0.post@n3.nabble.com> References: <1599689009071-0.post@n3.nabble.com> Message-ID: <659cc189-fd55-7852-2317-d2dddf61c62b@free.fr> Hello Daniel, In addition to Antoine simple and efficient solution, the following works as well (and may be a bit faster for big files. To be confirmed): File = "output.txt"; m = read(File,-1, size(evstr(mgetl(File,1)),2)); Regards Le 10/09/2020 ? 00:03, Daniel Stringari a ?crit?: > Good evening everyone, > > I'm integrating scilab with other software, so I need to read an output file > (.txt), like the one attached (output). > > It is worth mentioning that this file does not always have the same > dimensions (matrix), so I am trying to find something robust that can deal > with this particularity. I tried to use the 'csvread' function and the > 'read' function, but I still haven't been successful ... Any suggestions? > > output.txt -------------- next part -------------- An HTML attachment was scrubbed... URL: From fla.muff at hotmail.com Fri Sep 11 16:10:06 2020 From: fla.muff at hotmail.com (FMuff) Date: Fri, 11 Sep 2020 07:10:06 -0700 (MST) Subject: [Scilab-users] Scilab - Xcos In-Reply-To: References: <1598259568064-0.post@n3.nabble.com> Message-ID: <1599833406317-0.post@n3.nabble.com> Hi Cl?ment Thank you much for the answer. I saw this bug - but didnt find any solution for this problem. You have an idea how to find a solution for that? (Sorry - how to sign up for the Cc list?) Thank you much. Regards Flavio -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From sdr at durietz.se Fri Sep 11 16:51:36 2020 From: sdr at durietz.se (Stefan Du Rietz) Date: Fri, 11 Sep 2020 16:51:36 +0200 Subject: [Scilab-users] Read file (.txt) In-Reply-To: <659cc189-fd55-7852-2317-d2dddf61c62b@free.fr> References: <1599689009071-0.post@n3.nabble.com> <659cc189-fd55-7852-2317-d2dddf61c62b@free.fr> Message-ID: <6ca9c9c0-fdbc-87b1-1302-8f48769d5632@durietz.se> Hello Samuel, read() never works OK with m = -1, see your own comment in Bug 15075! This prevented me from upgrading to Scilab 6 until I found out how to do it with fscanfMat(). But then I had to remove all blank lines in my files (which I had to quickly find different parts of my data). --> tic(), M = fscanfMat(myfile.txt); toc() ans = 0.125278 --> size(M) ans = 13702. 9. --> tic(), M = mgetl(myfile.txt); toc() ans = 0.050891 --> tic(), M = evstr(M); toc() ans = 1.854611 evstr is slow with large text vectors, compared to file reading. --> size(evstr(mgetl(myfile, 1)), 2) ans = 9. --> tic(), M = read(myfile.txt, -1, 9); toc() ans = 17.418157 So you have to know the file size completely (and when do you?)! --> tic(), M = read(myfile.txt", 13702, 9); toc() ans = 0.085636 Regards Stefan On 2020-09-10 22:42, Samuel Gougeon wrote: > Hello Daniel, > > In addition to Antoine simple and efficient solution, the following > works as well (and may be a bit faster for big files. To be confirmed): > > File = "output.txt"; > m = read(File,-1, size(evstr(mgetl(File,1)),2)); > Regards > > > Le 10/09/2020 ? 00:03, Daniel Stringari a ?crit?: >> Good evening everyone, >> >> I'm integrating scilab with other software, so I need to read an output file >> (.txt), like the one attached (output). >> >> It is worth mentioning that this file does not always have the same >> dimensions (matrix), so I am trying to find something robust that can deal >> with this particularity. I tried to use the 'csvread' function and the >> 'read' function, but I still haven't been successful ... Any suggestions? >> >> output.txt > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > From sdr at durietz.se Fri Sep 11 17:20:31 2020 From: sdr at durietz.se (Stefan Du Rietz) Date: Fri, 11 Sep 2020 17:20:31 +0200 Subject: [Scilab-users] Read file (.txt) In-Reply-To: <659cc189-fd55-7852-2317-d2dddf61c62b@free.fr> References: <1599689009071-0.post@n3.nabble.com> <659cc189-fd55-7852-2317-d2dddf61c62b@free.fr> Message-ID: <40c1e39c-4f71-3da0-d57a-5edcdf7128ef@durietz.se> Please replace my latest e-mail with this. Hello Samuel, read() never works OK with m = -1, see your own comment in Bug 15075! This prevented me from upgrading to Scilab 6 until I found out how to do it with fscanfMat(). But then I had to remove all blank lines in my files (which I had to quickly find different parts of my data). --> tic(), M = fscanfMat(myfile); toc() ans = 0.125278 --> size(M) ans = 13702. 9. --> tic(), M = mgetl(myfile); toc() ans = 0.050891 --> tic(), M = evstr(M); toc() ans = 1.854611 evstr is slow with large text vectors, compared to file reading. --> size(evstr(mgetl(myfile, 1)), 2) ans = 9. --> tic(), M = read(myfile, -1, 9); toc() ans = 17.418157 So you have to know the file size completely (and when do you?)! --> tic(), M = read(myfile", 13702, 9); toc() ans = 0.085636 Regards Stefan On 2020-09-10 22:42, Samuel Gougeon wrote: > Hello Daniel, > > In addition to Antoine simple and efficient solution, the following > works as well (and may be a bit faster for big files. To be confirmed): > > File = "output.txt"; > m = read(File,-1, size(evstr(mgetl(File,1)),2)); > Regards > > > Le 10/09/2020 ? 00:03, Daniel Stringari a ?crit?: >> Good evening everyone, >> >> I'm integrating scilab with other software, so I need to read an output file >> (.txt), like the one attached (output). >> >> It is worth mentioning that this file does not always have the same >> dimensions (matrix), so I am trying to find something robust that can deal >> with this particularity. I tried to use the 'csvread' function and the >> 'read' function, but I still haven't been successful ... Any suggestions? >> >> output.txt > > > _______________________________________________ > 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 sgougeon at free.fr Fri Sep 11 19:32:00 2020 From: sgougeon at free.fr (Samuel Gougeon) Date: Fri, 11 Sep 2020 19:32:00 +0200 Subject: [Scilab-users] Read file (.txt) In-Reply-To: <6ca9c9c0-fdbc-87b1-1302-8f48769d5632@durietz.se> References: <1599689009071-0.post@n3.nabble.com> <659cc189-fd55-7852-2317-d2dddf61c62b@free.fr> <6ca9c9c0-fdbc-87b1-1302-8f48769d5632@durietz.se> Message-ID: <4de6e23e-8642-4c1b-1b40-11a648d2d4de@free.fr> Le 11/09/2020 ? 16:51, Stefan Du Rietz a ?crit?: > Hello Samuel, > > read() never works OK with m = -1, see your own comment in Bug 15075! > > This prevented me from upgrading to Scilab 6 until I found out how to > do it with fscanfMat(). But then I had to remove all blank lines in my > files (which I had to quickly find different parts of my data). For me, it perfectly works for Daniel's file, with 6.0.2 as well as with 6.1.0. May be the 15075's report could be retested and updated. From sdr at durietz.se Sat Sep 12 00:06:03 2020 From: sdr at durietz.se (Stefan Du Rietz) Date: Sat, 12 Sep 2020 00:06:03 +0200 Subject: [Scilab-users] Read file (.txt) In-Reply-To: <4de6e23e-8642-4c1b-1b40-11a648d2d4de@free.fr> References: <1599689009071-0.post@n3.nabble.com> <659cc189-fd55-7852-2317-d2dddf61c62b@free.fr> <6ca9c9c0-fdbc-87b1-1302-8f48769d5632@durietz.se> <4de6e23e-8642-4c1b-1b40-11a648d2d4de@free.fr> Message-ID: <26109868-359d-e9ec-b7e1-6843273a864d@durietz.se> On 2020-09-11 19:32, Samuel Gougeon wrote: > Le 11/09/2020 ? 16:51, Stefan Du Rietz a ?crit?: >> Hello Samuel, >> >> read() never works OK with m = -1, see your own comment in Bug 15075! >> >> This prevented me from upgrading to Scilab 6 until I found out how to >> do it with fscanfMat(). But then I had to remove all blank lines in my >> files (which I had to quickly find different parts of my data). > > > For me, it perfectly works for Daniel's file, with 6.0.2 as well as with > 6.1.0. > May be the 15075's report could be retested and updated. With which OS? I am only using Linux (Ubuntu). As a workaround, in Linux, you can quickly get the number of lines: --> m = evstr(strtok(unix_g("wc -l " + filename), " ")); I will add to the bug report. /Stefan From danielstringarita at gmail.com Sat Sep 12 01:29:59 2020 From: danielstringarita at gmail.com (Daniel Stringari) Date: Fri, 11 Sep 2020 16:29:59 -0700 (MST) Subject: [Scilab-users] Read file (.txt) In-Reply-To: <26109868-359d-e9ec-b7e1-6843273a864d@durietz.se> References: <1599689009071-0.post@n3.nabble.com> <659cc189-fd55-7852-2317-d2dddf61c62b@free.fr> <6ca9c9c0-fdbc-87b1-1302-8f48769d5632@durietz.se> <4de6e23e-8642-4c1b-1b40-11a648d2d4de@free.fr> <26109868-359d-e9ec-b7e1-6843273a864d@durietz.se> Message-ID: <1599866999291-0.post@n3.nabble.com> Good evening everyone, I appreciate everyone's availability. Great solutions! -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From sdr at durietz.se Sat Sep 12 16:55:27 2020 From: sdr at durietz.se (Stefan Du Rietz) Date: Sat, 12 Sep 2020 16:55:27 +0200 Subject: [Scilab-users] Read file (.txt) In-Reply-To: <26109868-359d-e9ec-b7e1-6843273a864d@durietz.se> References: <1599689009071-0.post@n3.nabble.com> <659cc189-fd55-7852-2317-d2dddf61c62b@free.fr> <6ca9c9c0-fdbc-87b1-1302-8f48769d5632@durietz.se> <4de6e23e-8642-4c1b-1b40-11a648d2d4de@free.fr> <26109868-359d-e9ec-b7e1-6843273a864d@durietz.se> Message-ID: <2e9ac0c7-1f06-04a9-e859-fb9e62c45da5@durietz.se> On 2020-09-12 00:06, Stefan Du Rietz wrote: > On 2020-09-11 19:32, Samuel Gougeon wrote: >> Le 11/09/2020 ? 16:51, Stefan Du Rietz a ?crit?: >>> Hello Samuel, >>> >>> read() never works OK with m = -1, see your own comment in Bug 15075! >>> >>> This prevented me from upgrading to Scilab 6 until I found out how to >>> do it with fscanfMat(). But then I had to remove all blank lines in >>> my files (which I had to quickly find different parts of my data). >> >> >> For me, it perfectly works for Daniel's file, with 6.0.2 as well as >> with 6.1.0. >> May be the 15075's report could be retested and updated. > > > With which OS? I am only using Linux (Ubuntu). > > As a workaround, in Linux, you can quickly get the number of lines: > --> m = evstr(strtok(unix_g("wc -l " + filename), " ")); > > I will add to the bug report. > > /Stefan That does not work if the file contains empty lines because the argument m to read() is the number of not empty lines to read! So one must subtract the number of empty lines from m above ... Why on earth was read() changed from the excellent previous version to one of no use??? From Serge.Steer at laposte.net Sat Sep 12 22:32:15 2020 From: Serge.Steer at laposte.net (Steer Serge) Date: Sat, 12 Sep 2020 22:32:15 +0200 Subject: [Scilab-users] Scilab-6.1 fails on OpenSuse Leap 15.2 Message-ID: <09004ad4-f4bd-96f9-033a-c2b2455f5bef@laposte.net> When Scilab 6.1.0 is launched one gets the error message "scilab-bin: error while loading shared libraries: libldap-2.4.so.2: cannot open shared object file: No such file or directory" There is no libldap-2.4.so.2 in /usr/lib but a libldap_*r*-2.4.so.2 I was not able to find a way to install the libldap-2.4.so.2 for openSuse Leap 15.2 Serge Steer -------------- next part -------------- An HTML attachment was scrubbed... URL: From f.s.farimani at gmail.com Sun Sep 13 11:50:33 2020 From: f.s.farimani at gmail.com (farimani) Date: Sun, 13 Sep 2020 02:50:33 -0700 (MST) Subject: [Scilab-users] Where is the best place for Scilab - xcos / ScicosLab - scicos questions and bug report? In-Reply-To: <1550825509208-0.post@n3.nabble.com> References: <1550825509208-0.post@n3.nabble.com> Message-ID: <1599990633210-0.post@n3.nabble.com> Dear All, To help the Scilab community find each other better I have created a Discord channel for Scilab on the Modelica server: https://discord.gg/XCAxqUQ Would be great to also have you all over there. P.S. There are also channels for Octave, Nelson, Maxima, and scicos-xcos, Julia... Best, ----- 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 sdr at durietz.se Sun Sep 13 14:35:14 2020 From: sdr at durietz.se (Stefan Du Rietz) Date: Sun, 13 Sep 2020 14:35:14 +0200 Subject: [Scilab-users] Read file (.txt) In-Reply-To: <2e9ac0c7-1f06-04a9-e859-fb9e62c45da5@durietz.se> References: <1599689009071-0.post@n3.nabble.com> <659cc189-fd55-7852-2317-d2dddf61c62b@free.fr> <6ca9c9c0-fdbc-87b1-1302-8f48769d5632@durietz.se> <4de6e23e-8642-4c1b-1b40-11a648d2d4de@free.fr> <26109868-359d-e9ec-b7e1-6843273a864d@durietz.se> <2e9ac0c7-1f06-04a9-e859-fb9e62c45da5@durietz.se> Message-ID: <1dfee7a3-2e24-15d1-1cce-84961b394288@durietz.se> On 2020-09-12 16:55, Stefan Du Rietz wrote: > > > On 2020-09-12 00:06, Stefan Du Rietz wrote: >> On 2020-09-11 19:32, Samuel Gougeon wrote: >>> Le 11/09/2020 ? 16:51, Stefan Du Rietz a ?crit?: >>>> Hello Samuel, >>>> >>>> read() never works OK with m = -1, see your own comment in Bug 15075! >>>> >>>> This prevented me from upgrading to Scilab 6 until I found out how >>>> to do it with fscanfMat(). But then I had to remove all blank lines >>>> in my files (which I had to quickly find different parts of my data). >>> >>> >>> For me, it perfectly works for Daniel's file, with 6.0.2 as well as >>> with 6.1.0. >>> May be the 15075's report could be retested and updated. >> >> >> With which OS? I am only using Linux (Ubuntu). >> >> As a workaround, in Linux, you can quickly get the number of lines: >> --> m = evstr(strtok(unix_g("wc -l " + filename), " ")); >> >> I will add to the bug report. >> >> /Stefan > > > That does not work if the file contains empty lines because the argument > m to read() is the number of not empty lines to read! So one must > subtract the number of empty lines from m above ... > > Why on earth was read() changed from the excellent previous version to > one of no use??? But this does work (m is the number of not empty lines) and is about as fast: --> m = evstr(unix_g("grep -vc ^$ " + filename)); So, together with --> n = size(evstr(mgetl(filename, 1)), 2); --> M = read(filename, m, n); Daniel can get what he wants. /Stefan From anick.islam92 at gmail.com Sun Sep 13 23:06:43 2020 From: anick.islam92 at gmail.com (EnigmaVoidX) Date: Sun, 13 Sep 2020 14:06:43 -0700 (MST) Subject: [Scilab-users] issue building Scilab 6.1.0 arm64 on Ubuntu 19.10 running inside Termux Proot Container Message-ID: <1600031203136-0.post@n3.nabble.com> I have been spending a few days compiling Scilab 6.1.0 git on my Ubuntu 19.10 arm64 OS running inside a proot container. After patching for the newer jogl2 packages and getting a few more extra dependencies I have managed to configure and make up to this point: ``` make[1]: Entering directory '/opt/Scilab/scilab/scilab' /bin/bash ./libtool --tag=CXX --mode=link g++ -std=c++17 -DNDEBUG -g1 -O2 -fno-stack-protector -lstdc++ -lgfortran -Wl,--no-as-needed -o scilab-bin modules/startup/src/cpp/scilab_bin-scilab.o ./modules/libscilab.la ./modules/libscilab-cli.la -lxml2 -L/usr/lib/aarch64-linux-gnu/valgrind -lcoregrind-arm64-linux -lvex-arm64-linux -lgcc -L/usr/lib/gcc/aarch64-linux-gnu/9 -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib -L/lib/aarch64-linux-gnu -L/lib/../lib -L/usr/lib/aarch64-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/aarch64-linux-gnu/9/../../.. -lpthread -ldl -lcurses -lgfortran -lm ./modules/console/libsciconsole.la ./modules/jvm/libscijvm.la ./modules/commons/libscicommons.la ./modules/libscilab.la -lopenblas -L/usr/lib/gcc/aarch64-linux-gnu/9 -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib -L/lib/aarch64-linux-gnu -L/lib/../lib -L/usr/lib/aarch64-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/aarch64-linux-gnu/9/../../.. -lpthread -ldl -lcurses -lgfortran -lm -lpthread -ldl -lcurses -lm libtool: link: g++ -std=c++17 -DNDEBUG -g1 -O2 -fno-stack-protector -Wl,--no-as-needed -o .libs/scilab-bin modules/startup/src/cpp/scilab_bin-scilab.o -lstdc++ -L/usr/lib/jvm/java-8-openjdk-arm64/jre/lib/aarch64 -L/usr/lib/jvm/java-8-openjdk-arm64/jre/lib/aarch64/server -L/usr/lib/aarch64-linux-gnu -L/usr/lib/gcc/aarch64-linux-gnu/9 -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib -L/lib/aarch64-linux-gnu -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/aarch64-linux-gnu/9/../../.. ./modules/.libs/libscilab-cli.so -L/usr/lib/aarch64-linux-gnu/valgrind -lcoregrind-arm64-linux -lvex-arm64-linux -lgcc ./modules/console/.libs/libsciconsole.so ./modules/jvm/.libs/libscijvm.so ./modules/commons/.libs/libscicommons.so ./modules/.libs/libscilab.so /opt/Scilab/scilab/scilab/modules/gui/.libs/libscigui.so /opt/Scilab/scilab/scilab/modules/renderer/.libs/libscirenderer.so /opt/Scilab/scilab/scilab/modules/graphics/.libs/libscigraphics.so /opt/Scilab/scilab/scilab/modules/graphic_export/.libs/libscigraphic_export.so /opt/Scilab/scilab/scilab/modules/console/.libs/libsciconsole.so /opt/Scilab/scilab/scilab/modules/action_binding/.libs/libsciaction_binding.so /opt/Scilab/scilab/scilab/modules/graphic_objects/.libs/libscigraphic_objects.so /opt/Scilab/scilab/scilab/modules/scinotes/.libs/libsciscinotes.so /opt/Scilab/scilab/scilab/modules/ui_data/.libs/libsciui_data.so /opt/Scilab/scilab/scilab/modules/history_browser/.libs/libscihistory_browser.so /opt/Scilab/scilab/scilab/modules/types/.libs/libscitypes-java.so /opt/Scilab/scilab/scilab/modules/preferences/.libs/libscipreferences.so /opt/Scilab/scilab/scilab/modules/external_objects_java/.libs/libsciexternal_objects_java.so /opt/Scilab/scilab/scilab/modules/jvm/.libs/libscijvm.so -ljava -lverify -ljvm /opt/Scilab/scilab/scilab/modules/helptools/.libs/libscihelptools.so /opt/Scilab/scilab/scilab/modules/commons/.libs/libscicommons.so /opt/Scilab/scilab/scilab/modules/tclsci/.libs/libscitclsci.so -ltk8.6 -ltcl8.6 /opt/Scilab/scilab/scilab/modules/.libs/libscilab-cli.so /usr/lib/aarch64-linux-gnu/libcurl-gnutls.so /opt/Scilab/scilab/scilab/modules/functions/.libs/libscifunctions.so /opt/Scilab/scilab/scilab/modules/call_scilab/.libs/libscicall_scilab.so /opt/Scilab/scilab/scilab/modules/localization/.libs/libscilocalization.so /opt/Scilab/scilab/scilab/modules/special_functions/.libs/libscispecial_functions.so /opt/Scilab/scilab/scilab/modules/completion/.libs/libscicompletion.so /opt/Scilab/scilab/scilab/modules/history_manager/.libs/libscihistory_manager.so -lpcreposix -lpcre /opt/Scilab/scilab/scilab/modules/hdf5/.libs/libscihdf5.so -lhdf5_serial -lhdf5_serial_hl -lfftw3 /opt/Scilab/scilab/scilab/modules/statistics/.libs/libscistatistics.so /opt/Scilab/scilab/scilab/modules/ast/.libs/libsciast.so /opt/Scilab/scilab/scilab/modules/functions_manager/.libs/libscifunctions_manager.so /opt/Scilab/scilab/scilab/modules/xml/.libs/libscixml.so /opt/Scilab/scilab/scilab/modules/external_objects/.libs/libsciexternal_objects.so /opt/Scilab/scilab/scilab/modules/slint/.libs/libscislint.so /opt/Scilab/scilab/scilab/modules/coverage/.libs/libscicoverage.so -lxml2 /opt/Scilab/scilab/scilab/modules/gui/.libs/libscigui-disable.so /opt/Scilab/scilab/scilab/modules/graphics/.libs/libscigraphics-disable.so /opt/Scilab/scilab/scilab/modules/graphic_export/.libs/libscigraphic_export-disable.so /opt/Scilab/scilab/scilab/modules/console/.libs/libsciconsole-minimal.so /opt/Scilab/scilab/scilab/modules/action_binding/.libs/libsciaction_binding-disable.so /opt/Scilab/scilab/scilab/modules/jvm/.libs/libscijvm-disable.so /opt/Scilab/scilab/scilab/modules/xcos/.libs/libscixcos-disable.so /opt/Scilab/scilab/scilab/modules/graphic_objects/.libs/libscigraphic_objects-disable.so /opt/Scilab/scilab/scilab/modules/scinotes/.libs/libsciscinotes-disable.so /opt/Scilab/scilab/scilab/modules/ui_data/.libs/libsciui_data-disable.so /opt/Scilab/scilab/scilab/modules/history_browser/.libs/libscihistory_browser-disable.so /opt/Scilab/scilab/scilab/modules/commons/.libs/libscicommons-disable.so /opt/Scilab/scilab/scilab/modules/preferences/.libs/libscipreferences-cli.so /opt/Scilab/scilab/scilab/modules/tclsci/.libs/libscitclsci-disable.so -lstdc++fs -lopenblas -lgfortran -lpthread -ldl -lcurses -lm -pthread -Wl,-rpath -Wl,/usr/local/lib/scilab /bin/ld: /usr/lib/aarch64-linux-gnu/valgrind/libcoregrind-arm64-linux.a(libnolto_coregrind_arm64_linux_a-m_main.o): in function `_start': (.text+0x0): multiple definition of `_start'; /usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu/Scrt1.o:(.text+0x0): first defined here /bin/ld: /usr/lib/aarch64-linux-gnu/valgrind/libcoregrind-arm64-linux.a(libnolto_coregrind_arm64_linux_a-m_main.o): in function `valgrind_main': (.text+0x18ac): undefined reference to `vgPlain_tl_pre_clo_init' /bin/ld: (.text+0x18b0): undefined reference to `vgPlain_tl_pre_clo_init' collect2: error: ld returned 1 exit status make[1]: *** [Makefile:1216: scilab-bin] Error 1 make[1]: Leaving directory '/opt/Scilab/scilab/scilab' make: *** [Makefile:1608: all-recursive] Error 1 ``` I have installed the latest Valgrind for my distro, version 1:3.15.0-1ubuntu3.1. Anyone can enlighten me why it's failing with undefined reference to vgPlain_tl_pre_clo_init? I can't directly access the valgrind main class either. My only guess is either my valgrind is to old or new. I know scilab 6.0.1 works on ubuntu 20 on arm64 so I dont think its an architecture limitation. Have compiled openfoam, elmerfem, gmsh, getdp, freecad, paraview and su2 no issues, so what am I missing for scilab? -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From Clement.David at esi-group.com Mon Sep 14 08:45:52 2020 From: Clement.David at esi-group.com (=?utf-8?B?Q2zDqW1lbnQgRGF2aWQ=?=) Date: Mon, 14 Sep 2020 06:45:52 +0000 Subject: [Scilab-users] Scilab-6.1 fails on OpenSuse Leap 15.2 In-Reply-To: <09004ad4-f4bd-96f9-033a-c2b2455f5bef@laposte.net> References: <09004ad4-f4bd-96f9-033a-c2b2455f5bef@laposte.net> Message-ID: Hello Serge, This is known issue, reported as https://bugzilla.scilab.org/show_bug.cgi?id=16368 . To "fix" it, use your system libcurl.so by removing some files (listed on the bug comments) from the Scilab binary. Thanks, Cl?ment DAVID > -----Original Message----- > From: users On Behalf Of Steer Serge > Sent: Saturday, September 12, 2020 10:32 PM > To: users at lists.scilab.org > Subject: [Scilab-users] Scilab-6.1 fails on OpenSuse Leap 15.2 > > When Scilab 6.1.0 is launched one gets the error message > > > "scilab-bin: error while loading shared libraries: libldap-2.4.so.2: cannot open > shared object file: No such file or directory" > > There is no libldap-2.4.so.2 in /usr/lib but a libldap_r-2.4.so.2 > > I was not able to find a way to install the libldap-2.4.so.2 for openSuse Leap > 15.2 > > Serge Steer > From Clement.David at esi-group.com Mon Sep 14 09:00:10 2020 From: Clement.David at esi-group.com (=?iso-8859-1?Q?Cl=E9ment_David?=) Date: Mon, 14 Sep 2020 07:00:10 +0000 Subject: [Scilab-users] issue building Scilab 6.1.0 arm64 on Ubuntu 19.10 running inside Termux Proot Container In-Reply-To: <1600031203136-0.post@n3.nabble.com> References: <1600031203136-0.post@n3.nabble.com> Message-ID: Hello, As a first build, I suggest you to compile without valgrind support as this is an optional dependency. This can be done using : $ ./configure VALGRIND_CFLAGS="" VALGRIND_LIBS="" Otherwise, your analysis looks good. Either your valgrind installation provide an extra library we need to link against, either we don't need to link against the coregrind library. Thanks, Cl?ment DAVID > -----Original Message----- > From: users On Behalf Of EnigmaVoidX > Sent: Sunday, September 13, 2020 11:07 PM > To: users at lists.scilab.org > Subject: [Scilab-users] issue building Scilab 6.1.0 arm64 on Ubuntu 19.10 > running inside Termux Proot Container > > I have been spending a few days compiling Scilab 6.1.0 git on my Ubuntu > 19.10 > arm64 OS running inside a proot container. > > After patching for the newer jogl2 packages and getting a few more extra > dependencies I have managed to configure and make up to this point: > > ``` > make[1]: Entering directory '/opt/Scilab/scilab/scilab' > /bin/bash ./libtool --tag=CXX --mode=link g++ -std=c++17 -DNDEBUG -g1 - > O2 > -fno-stack-protector -lstdc++ -lgfortran -Wl,--no-as-needed -o > scilab-bin modules/startup/src/cpp/scilab_bin-scilab.o > ./modules/libscilab.la ./modules/libscilab-cli.la -lxml2 -L/usr/lib/aarch64- > linux-gnu/valgrind -lcoregrind-arm64-linux -lvex-arm64-linux -lgcc - > L/usr/lib/gcc/aarch64-linux-gnu/9 > -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu > -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib -L/lib/aarch64-linux-gnu - > L/lib/../lib -L/usr/lib/aarch64-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/aarch64- > linux-gnu/9/../../.. -lpthread -ldl -lcurses -lgfortran -lm > ./modules/console/libsciconsole.la ./modules/jvm/libscijvm.la > ./modules/commons/libscicommons.la ./modules/libscilab.la -lopenblas > -L/usr/lib/gcc/aarch64-linux-gnu/9 > -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu > -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib -L/lib/aarch64-linux-gnu - > L/lib/../lib -L/usr/lib/aarch64-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/aarch64- > linux-gnu/9/../../.. -lpthread -ldl -lcurses -lgfortran -lm -lpthread -ldl -lcurses > -lm > libtool: link: g++ -std=c++17 -DNDEBUG -g1 -O2 -fno-stack-protector -Wl,-- > no-as-needed -o .libs/scilab-bin modules/startup/src/cpp/scilab_bin-scilab.o > -lstdc++ > -L/usr/lib/jvm/java-8-openjdk-arm64/jre/lib/aarch64 > -L/usr/lib/jvm/java-8-openjdk-arm64/jre/lib/aarch64/server > -L/usr/lib/aarch64-linux-gnu -L/usr/lib/gcc/aarch64-linux-gnu/9 > -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu > -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib -L/lib/aarch64-linux-gnu - > L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/aarch64-linux-gnu/9/../../.. > ./modules/.libs/libscilab-cli.so -L/usr/lib/aarch64-linux-gnu/valgrind > -lcoregrind-arm64-linux -lvex-arm64-linux -lgcc > ./modules/console/.libs/libsciconsole.so ./modules/jvm/.libs/libscijvm.so > ./modules/commons/.libs/libscicommons.so ./modules/.libs/libscilab.so > /opt/Scilab/scilab/scilab/modules/gui/.libs/libscigui.so > /opt/Scilab/scilab/scilab/modules/renderer/.libs/libscirenderer.so > /opt/Scilab/scilab/scilab/modules/graphics/.libs/libscigraphics.so > /opt/Scilab/scilab/scilab/modules/graphic_export/.libs/libscigraphic_export. > so > /opt/Scilab/scilab/scilab/modules/console/.libs/libsciconsole.so > /opt/Scilab/scilab/scilab/modules/action_binding/.libs/libsciaction_binding.s > o > /opt/Scilab/scilab/scilab/modules/graphic_objects/.libs/libscigraphic_objects > .so > /opt/Scilab/scilab/scilab/modules/scinotes/.libs/libsciscinotes.so > /opt/Scilab/scilab/scilab/modules/ui_data/.libs/libsciui_data.so > /opt/Scilab/scilab/scilab/modules/history_browser/.libs/libscihistory_brows > er.so > /opt/Scilab/scilab/scilab/modules/types/.libs/libscitypes-java.so > /opt/Scilab/scilab/scilab/modules/preferences/.libs/libscipreferences.so > /opt/Scilab/scilab/scilab/modules/external_objects_java/.libs/libsciexternal > _objects_java.so > /opt/Scilab/scilab/scilab/modules/jvm/.libs/libscijvm.so -ljava -lverify -ljvm > /opt/Scilab/scilab/scilab/modules/helptools/.libs/libscihelptools.so > /opt/Scilab/scilab/scilab/modules/commons/.libs/libscicommons.so > /opt/Scilab/scilab/scilab/modules/tclsci/.libs/libscitclsci.so -ltk8.6 > -ltcl8.6 /opt/Scilab/scilab/scilab/modules/.libs/libscilab-cli.so > /usr/lib/aarch64-linux-gnu/libcurl-gnutls.so > /opt/Scilab/scilab/scilab/modules/functions/.libs/libscifunctions.so > /opt/Scilab/scilab/scilab/modules/call_scilab/.libs/libscicall_scilab.so > /opt/Scilab/scilab/scilab/modules/localization/.libs/libscilocalization.so > /opt/Scilab/scilab/scilab/modules/special_functions/.libs/libscispecial_functi > ons.so > /opt/Scilab/scilab/scilab/modules/completion/.libs/libscicompletion.so > /opt/Scilab/scilab/scilab/modules/history_manager/.libs/libscihistory_manag > er.so > -lpcreposix -lpcre > /opt/Scilab/scilab/scilab/modules/hdf5/.libs/libscihdf5.so -lhdf5_serial - > lhdf5_serial_hl -lfftw3 > /opt/Scilab/scilab/scilab/modules/statistics/.libs/libscistatistics.so > /opt/Scilab/scilab/scilab/modules/ast/.libs/libsciast.so > /opt/Scilab/scilab/scilab/modules/functions_manager/.libs/libscifunctions_ > manager.so > /opt/Scilab/scilab/scilab/modules/xml/.libs/libscixml.so > /opt/Scilab/scilab/scilab/modules/external_objects/.libs/libsciexternal_obje > cts.so > /opt/Scilab/scilab/scilab/modules/slint/.libs/libscislint.so > /opt/Scilab/scilab/scilab/modules/coverage/.libs/libscicoverage.so -lxml2 > /opt/Scilab/scilab/scilab/modules/gui/.libs/libscigui-disable.so > /opt/Scilab/scilab/scilab/modules/graphics/.libs/libscigraphics-disable.so > /opt/Scilab/scilab/scilab/modules/graphic_export/.libs/libscigraphic_export- > disable.so > /opt/Scilab/scilab/scilab/modules/console/.libs/libsciconsole-minimal.so > /opt/Scilab/scilab/scilab/modules/action_binding/.libs/libsciaction_binding- > disable.so > /opt/Scilab/scilab/scilab/modules/jvm/.libs/libscijvm-disable.so > /opt/Scilab/scilab/scilab/modules/xcos/.libs/libscixcos-disable.so > /opt/Scilab/scilab/scilab/modules/graphic_objects/.libs/libscigraphic_objects > -disable.so > /opt/Scilab/scilab/scilab/modules/scinotes/.libs/libsciscinotes-disable.so > /opt/Scilab/scilab/scilab/modules/ui_data/.libs/libsciui_data-disable.so > /opt/Scilab/scilab/scilab/modules/history_browser/.libs/libscihistory_brows > er-disable.so > /opt/Scilab/scilab/scilab/modules/commons/.libs/libscicommons-disable.so > /opt/Scilab/scilab/scilab/modules/preferences/.libs/libscipreferences-cli.so > /opt/Scilab/scilab/scilab/modules/tclsci/.libs/libscitclsci-disable.so > -lstdc++fs -lopenblas -lgfortran -lpthread -ldl -lcurses -lm -pthread > -Wl,-rpath -Wl,/usr/local/lib/scilab > /bin/ld: > /usr/lib/aarch64-linux-gnu/valgrind/libcoregrind-arm64- > linux.a(libnolto_coregrind_arm64_linux_a-m_main.o): > in function `_start': > (.text+0x0): multiple definition of `_start'; > /usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux- > gnu/Scrt1.o:(.text+0x0): > first defined here > /bin/ld: > /usr/lib/aarch64-linux-gnu/valgrind/libcoregrind-arm64- > linux.a(libnolto_coregrind_arm64_linux_a-m_main.o): > in function `valgrind_main': > (.text+0x18ac): undefined reference to `vgPlain_tl_pre_clo_init' > /bin/ld: (.text+0x18b0): undefined reference to `vgPlain_tl_pre_clo_init' > collect2: error: ld returned 1 exit status > make[1]: *** [Makefile:1216: scilab-bin] Error 1 > make[1]: Leaving directory '/opt/Scilab/scilab/scilab' > make: *** [Makefile:1608: all-recursive] Error 1 ``` I have installed the latest > Valgrind for my distro, version 1:3.15.0-1ubuntu3.1. > > Anyone can enlighten me why it's failing with undefined reference to > vgPlain_tl_pre_clo_init? I can't directly access the valgrind main class either. > My only guess is either my valgrind is to old or new. > > I know scilab 6.0.1 works on ubuntu 20 on arm64 so I dont think its an > architecture limitation. Have compiled openfoam, elmerfem, gmsh, getdp, > freecad, paraview and su2 no issues, so what am I missing for scilab? > > > > -- > Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives- > f2602246.html > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From stepan.podhorsky at gmail.com Mon Sep 14 16:13:05 2020 From: stepan.podhorsky at gmail.com (Steve) Date: Mon, 14 Sep 2020 07:13:05 -0700 (MST) Subject: [Scilab-users] Hybrid simulation in Scilab/Xcos Message-ID: <1600092785963-0.post@n3.nabble.com> Hello, I have been facing a problem how to develop a hybrid simulation in the Scilab/Xcos. The simulation consists of a SISO (single input single output) system in continuous time domain and a discrete PID controller. The PID controller is a CBLOCK containing the code in the C programmin language. Interface between the "analog world" and the "discrete world" consists of two SAMPLEHOLD blocks. My problem is that I don't know how to achieve a state when the CBLOCK is calculated in synchronism with the sample and hold process realized in the SAMPLEHOLD blocks. Can anybody give me an advice or recommend me some tutorial? Thanks in advance. -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From antoine.monmayrant at laas.fr Mon Sep 14 16:14:29 2020 From: antoine.monmayrant at laas.fr (Antoine Monmayrant) Date: Mon, 14 Sep 2020 16:14:29 +0200 Subject: [Scilab-users] plot(x,y,':') & dotted line : is this a bug? Message-ID: Hello all, For some reason, I don't understand the output of: ??? plot(rand(1:10),':') This should be a 'dotted line', as explained on the page: ??? https://help.scilab.org/docs/6.1.0/en_US/LineSpec.html But I get a line_style==5 which is some kind of 1dash-2dots line. Looking at what's on page: https://help.scilab.org/docs/6.1.0/en_US/polyline_properties.html I think it would make more sense to get line_style==7, 9 or 10, no? I have the same behaviour with 5.5.2. Do you think this is worth a bug report? Antoine From heinznabielek at me.com Mon Sep 14 16:23:05 2020 From: heinznabielek at me.com (Heinz Nabielek) Date: Mon, 14 Sep 2020 16:23:05 +0200 Subject: [Scilab-users] plot(x,y,':') & dotted line : is this a bug? In-Reply-To: References: Message-ID: > On 14.09.2020, at 16:14, Antoine Monmayrant wrote: > > plot(rand(1:10),':') I get a perfect dotted line. Heinz "Scilab Version: " "6.1.1.0" "Operating System: " "Mac OS X 10.15.6" "Java version: " "1.8.0_51" From antoine.monmayrant at laas.fr Mon Sep 14 16:28:31 2020 From: antoine.monmayrant at laas.fr (Antoine Monmayrant) Date: Mon, 14 Sep 2020 16:28:31 +0200 Subject: [Scilab-users] plot(x,y,':') & dotted line : is this a bug? In-Reply-To: References: Message-ID: Le 14/09/2020 ? 16:23, Heinz Nabielek a ?crit?: > > I get a perfect dotted line. What? I tested this under linux (ubuntu 18.04) & Windows10, with both 5.5.2 and the 6.1 and I don't get a dotted line... I attached the output of: ??? scf();plot(1:10,':') Antoine -------------- next part -------------- A non-text attachment was scrubbed... Name: dotted.png Type: image/png Size: 5135 bytes Desc: not available URL: From heinznabielek at me.com Mon Sep 14 16:34:45 2020 From: heinznabielek at me.com (Heinz Nabielek) Date: Mon, 14 Sep 2020 16:34:45 +0200 Subject: [Scilab-users] plot(x,y,':') & dotted line : is this a bug? In-Reply-To: References: Message-ID: <215A932E-9235-46DD-8870-94B79C96EE02@me.com> Ok: perhaps not perfect dots.... scf();plot(1:10,':'); scf();plot(1:100,':'); > On 14.09.2020, at 16:28, Antoine Monmayrant wrote: > > scf();plot(1:10,':') -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-2.png Type: image/png Size: 47211 bytes Desc: not available URL: From sdr at durietz.se Mon Sep 14 17:41:46 2020 From: sdr at durietz.se (Stefan Du Rietz) Date: Mon, 14 Sep 2020 17:41:46 +0200 Subject: [Scilab-users] plot(x,y,':') & dotted line : is this a bug? In-Reply-To: References: Message-ID: <18044cd9-9050-c0d9-9307-5fc7d4eaf400@durietz.se> On 2020-09-14 16:28, Antoine Monmayrant wrote: > > Le 14/09/2020 ? 16:23, Heinz Nabielek a ?crit?: >> >> I get a perfect dotted line. > > > What? > I tested this under linux (ubuntu 18.04) & Windows10, with both 5.5.2 > and the 6.1 and I don't get a dotted line... > > I attached the output of: > > ??? scf();plot(1:10,':') > > > > Antoine Antoine, I get the same erroneous line as you! Scilab 6.0.2 Linux, Ubuntu 18.04 LTS /Stefan From chinluh.tan at bytecode-asia.com Mon Sep 14 17:42:20 2020 From: chinluh.tan at bytecode-asia.com (Chin Luh Tan) Date: Mon, 14 Sep 2020 23:42:20 +0800 Subject: [Scilab-users] Hybrid simulation in Scilab/Xcos In-Reply-To: <1600092785963-0.post@n3.nabble.com> References: <1600092785963-0.post@n3.nabble.com> Message-ID: <1748d47ffd5.11ce77d42362671.412388770989212371@bytecode-asia.com> Hi,? you might want to use the discrete block "DLR" instead.? first you could convert the PID in s-domain into z domain using the dscr function in the Scilab, and then use the value in DLR block for hybrid simulation. make sure the clock u use for the block is same as the sampling rate in the dscr function.? hope this helps. rgds, CL ---- On Mon, 14 Sep 2020 22:13:05 +0800 Steve wrote ---- Hello, I have been facing a problem how to develop a hybrid simulation in the Scilab/Xcos. The simulation consists of a SISO (single input single output) system in continuous time domain and a discrete PID controller. The PID controller is a CBLOCK containing the code in the C programmin language. Interface between the "analog world" and the "discrete world" consists of two SAMPLEHOLD blocks. My problem is that I don't know how to achieve a state when the CBLOCK is calculated in synchronism with the sample and hold process realized in the SAMPLEHOLD blocks. Can anybody give me an advice or recommend me some tutorial? Thanks in advance. -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html _______________________________________________ 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 anick.islam92 at gmail.com Mon Sep 14 21:13:44 2020 From: anick.islam92 at gmail.com (EnigmaVoidX) Date: Mon, 14 Sep 2020 12:13:44 -0700 (MST) Subject: [Scilab-users] issue building Scilab 6.1.0 arm64 on Ubuntu 19.10 running inside Termux Proot Container In-Reply-To: References: <1600031203136-0.post@n3.nabble.com> Message-ID: <1600110824324-0.post@n3.nabble.com> I'm trying that, currently in the process of make, however the configure log still shows valgrind path even with the configure options you have given me, hopefully that won't cause any issues. Cl?ment David-3 wrote > Hello, > > As a first build, I suggest you to compile without valgrind support as > this is an optional dependency. This can be done using : > $ ./configure VALGRIND_CFLAGS="" VALGRIND_LIBS="" > > Otherwise, your analysis looks good. Either your valgrind installation > provide an extra library we need to link against, either we don't need to > link against the coregrind library. > > Thanks, > > Cl?ment DAVID > >> -----Original Message----- >> From: users < > users-bounces at .scilab > > On Behalf Of EnigmaVoidX >> Sent: Sunday, September 13, 2020 11:07 PM >> To: > users at .scilab >> Subject: [Scilab-users] issue building Scilab 6.1.0 arm64 on Ubuntu 19.10 >> running inside Termux Proot Container >> >> I have been spending a few days compiling Scilab 6.1.0 git on my Ubuntu >> 19.10 >> arm64 OS running inside a proot container. >> >> After patching for the newer jogl2 packages and getting a few more extra >> dependencies I have managed to configure and make up to this point: >> >> ``` >> make[1]: Entering directory '/opt/Scilab/scilab/scilab' >> /bin/bash ./libtool --tag=CXX --mode=link g++ -std=c++17 -DNDEBUG -g1 >> - >> O2 >> -fno-stack-protector -lstdc++ -lgfortran -Wl,--no-as-needed -o >> scilab-bin modules/startup/src/cpp/scilab_bin-scilab.o >> ./modules/libscilab.la ./modules/libscilab-cli.la -lxml2 >> -L/usr/lib/aarch64- >> linux-gnu/valgrind -lcoregrind-arm64-linux -lvex-arm64-linux -lgcc - >> L/usr/lib/gcc/aarch64-linux-gnu/9 >> -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu >> -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib >> -L/lib/aarch64-linux-gnu - >> L/lib/../lib -L/usr/lib/aarch64-linux-gnu -L/usr/lib/../lib >> -L/usr/lib/gcc/aarch64- >> linux-gnu/9/../../.. -lpthread -ldl -lcurses -lgfortran -lm >> ./modules/console/libsciconsole.la ./modules/jvm/libscijvm.la >> ./modules/commons/libscicommons.la ./modules/libscilab.la -lopenblas >> -L/usr/lib/gcc/aarch64-linux-gnu/9 >> -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu >> -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib >> -L/lib/aarch64-linux-gnu - >> L/lib/../lib -L/usr/lib/aarch64-linux-gnu -L/usr/lib/../lib >> -L/usr/lib/gcc/aarch64- >> linux-gnu/9/../../.. -lpthread -ldl -lcurses -lgfortran -lm -lpthread >> -ldl -lcurses >> -lm >> libtool: link: g++ -std=c++17 -DNDEBUG -g1 -O2 -fno-stack-protector >> -Wl,-- >> no-as-needed -o .libs/scilab-bin >> modules/startup/src/cpp/scilab_bin-scilab.o >> -lstdc++ >> -L/usr/lib/jvm/java-8-openjdk-arm64/jre/lib/aarch64 >> -L/usr/lib/jvm/java-8-openjdk-arm64/jre/lib/aarch64/server >> -L/usr/lib/aarch64-linux-gnu -L/usr/lib/gcc/aarch64-linux-gnu/9 >> -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu >> -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib >> -L/lib/aarch64-linux-gnu - >> L/lib/../lib -L/usr/lib/../lib >> -L/usr/lib/gcc/aarch64-linux-gnu/9/../../.. >> ./modules/.libs/libscilab-cli.so -L/usr/lib/aarch64-linux-gnu/valgrind >> -lcoregrind-arm64-linux -lvex-arm64-linux -lgcc >> ./modules/console/.libs/libsciconsole.so ./modules/jvm/.libs/libscijvm.so >> ./modules/commons/.libs/libscicommons.so ./modules/.libs/libscilab.so >> /opt/Scilab/scilab/scilab/modules/gui/.libs/libscigui.so >> /opt/Scilab/scilab/scilab/modules/renderer/.libs/libscirenderer.so >> /opt/Scilab/scilab/scilab/modules/graphics/.libs/libscigraphics.so >> /opt/Scilab/scilab/scilab/modules/graphic_export/.libs/libscigraphic_export. >> so >> /opt/Scilab/scilab/scilab/modules/console/.libs/libsciconsole.so >> /opt/Scilab/scilab/scilab/modules/action_binding/.libs/libsciaction_binding.s >> o >> /opt/Scilab/scilab/scilab/modules/graphic_objects/.libs/libscigraphic_objects >> .so >> /opt/Scilab/scilab/scilab/modules/scinotes/.libs/libsciscinotes.so >> /opt/Scilab/scilab/scilab/modules/ui_data/.libs/libsciui_data.so >> /opt/Scilab/scilab/scilab/modules/history_browser/.libs/libscihistory_brows >> er.so >> /opt/Scilab/scilab/scilab/modules/types/.libs/libscitypes-java.so >> /opt/Scilab/scilab/scilab/modules/preferences/.libs/libscipreferences.so >> /opt/Scilab/scilab/scilab/modules/external_objects_java/.libs/libsciexternal >> _objects_java.so >> /opt/Scilab/scilab/scilab/modules/jvm/.libs/libscijvm.so -ljava -lverify >> -ljvm >> /opt/Scilab/scilab/scilab/modules/helptools/.libs/libscihelptools.so >> /opt/Scilab/scilab/scilab/modules/commons/.libs/libscicommons.so >> /opt/Scilab/scilab/scilab/modules/tclsci/.libs/libscitclsci.so -ltk8.6 >> -ltcl8.6 /opt/Scilab/scilab/scilab/modules/.libs/libscilab-cli.so >> /usr/lib/aarch64-linux-gnu/libcurl-gnutls.so >> /opt/Scilab/scilab/scilab/modules/functions/.libs/libscifunctions.so >> /opt/Scilab/scilab/scilab/modules/call_scilab/.libs/libscicall_scilab.so >> /opt/Scilab/scilab/scilab/modules/localization/.libs/libscilocalization.so >> /opt/Scilab/scilab/scilab/modules/special_functions/.libs/libscispecial_functi >> ons.so >> /opt/Scilab/scilab/scilab/modules/completion/.libs/libscicompletion.so >> /opt/Scilab/scilab/scilab/modules/history_manager/.libs/libscihistory_manag >> er.so >> -lpcreposix -lpcre >> /opt/Scilab/scilab/scilab/modules/hdf5/.libs/libscihdf5.so -lhdf5_serial >> - >> lhdf5_serial_hl -lfftw3 >> /opt/Scilab/scilab/scilab/modules/statistics/.libs/libscistatistics.so >> /opt/Scilab/scilab/scilab/modules/ast/.libs/libsciast.so >> /opt/Scilab/scilab/scilab/modules/functions_manager/.libs/libscifunctions_ >> manager.so >> /opt/Scilab/scilab/scilab/modules/xml/.libs/libscixml.so >> /opt/Scilab/scilab/scilab/modules/external_objects/.libs/libsciexternal_obje >> cts.so >> /opt/Scilab/scilab/scilab/modules/slint/.libs/libscislint.so >> /opt/Scilab/scilab/scilab/modules/coverage/.libs/libscicoverage.so -lxml2 >> /opt/Scilab/scilab/scilab/modules/gui/.libs/libscigui-disable.so >> /opt/Scilab/scilab/scilab/modules/graphics/.libs/libscigraphics-disable.so >> /opt/Scilab/scilab/scilab/modules/graphic_export/.libs/libscigraphic_export- >> disable.so >> /opt/Scilab/scilab/scilab/modules/console/.libs/libsciconsole-minimal.so >> /opt/Scilab/scilab/scilab/modules/action_binding/.libs/libsciaction_binding- >> disable.so >> /opt/Scilab/scilab/scilab/modules/jvm/.libs/libscijvm-disable.so >> /opt/Scilab/scilab/scilab/modules/xcos/.libs/libscixcos-disable.so >> /opt/Scilab/scilab/scilab/modules/graphic_objects/.libs/libscigraphic_objects >> -disable.so >> /opt/Scilab/scilab/scilab/modules/scinotes/.libs/libsciscinotes-disable.so >> /opt/Scilab/scilab/scilab/modules/ui_data/.libs/libsciui_data-disable.so >> /opt/Scilab/scilab/scilab/modules/history_browser/.libs/libscihistory_brows >> er-disable.so >> /opt/Scilab/scilab/scilab/modules/commons/.libs/libscicommons-disable.so >> /opt/Scilab/scilab/scilab/modules/preferences/.libs/libscipreferences-cli.so >> /opt/Scilab/scilab/scilab/modules/tclsci/.libs/libscitclsci-disable.so >> -lstdc++fs -lopenblas -lgfortran -lpthread -ldl -lcurses -lm -pthread >> -Wl,-rpath -Wl,/usr/local/lib/scilab >> /bin/ld: >> /usr/lib/aarch64-linux-gnu/valgrind/libcoregrind-arm64- >> linux.a(libnolto_coregrind_arm64_linux_a-m_main.o): >> in function `_start': >> (.text+0x0): multiple definition of `_start'; >> /usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux- >> gnu/Scrt1.o:(.text+0x0): >> first defined here >> /bin/ld: >> /usr/lib/aarch64-linux-gnu/valgrind/libcoregrind-arm64- >> linux.a(libnolto_coregrind_arm64_linux_a-m_main.o): >> in function `valgrind_main': >> (.text+0x18ac): undefined reference to `vgPlain_tl_pre_clo_init' >> /bin/ld: (.text+0x18b0): undefined reference to `vgPlain_tl_pre_clo_init' >> collect2: error: ld returned 1 exit status >> make[1]: *** [Makefile:1216: scilab-bin] Error 1 >> make[1]: Leaving directory '/opt/Scilab/scilab/scilab' >> make: *** [Makefile:1608: all-recursive] Error 1 ``` I have installed the >> latest >> Valgrind for my distro, version 1:3.15.0-1ubuntu3.1. >> >> Anyone can enlighten me why it's failing with undefined reference to >> vgPlain_tl_pre_clo_init? I can't directly access the valgrind main class >> either. >> My only guess is either my valgrind is to old or new. >> >> I know scilab 6.0.1 works on ubuntu 20 on arm64 so I dont think its an >> architecture limitation. Have compiled openfoam, elmerfem, gmsh, getdp, >> freecad, paraview and su2 no issues, so what am I missing for scilab? >> >> >> >> -- >> Sent from: >> http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives- >> f2602246.html >> _______________________________________________ >> users mailing list >> > users at .scilab >> http://lists.scilab.org/mailman/listinfo/users > _______________________________________________ > users mailing list > users at .scilab > http://lists.scilab.org/mailman/listinfo/users -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From anick.islam92 at gmail.com Tue Sep 15 02:34:05 2020 From: anick.islam92 at gmail.com (EnigmaVoidX) Date: Mon, 14 Sep 2020 17:34:05 -0700 (MST) Subject: [Scilab-users] issue building Scilab 6.1.0 arm64 on Ubuntu 19.10 running inside Termux Proot Container In-Reply-To: References: <1600031203136-0.post@n3.nabble.com> Message-ID: <1600130045280-0.post@n3.nabble.com> It still fails even with the configure flag: make[1]: Entering directory '/opt/Scilab/scilab/scilab' /bin/bash ./libtool --tag=CXX --mode=link g++ -std=c++17 -DNDEBUG -g1 -O2 -fno-stack-protector -lstdc++ -lgfortran -Wl,--no-as-needed -o scilab-bin modules/startup/src/cpp/scilab_bin-scilab.o ./modules/libscilab.la ./modules/libscilab-cli.la -lxml2 -L/usr/local/lib/valgrind -lcoregrind-arm64-linux -lvex-arm64-linux -lgcc -L/usr/lib/gcc/aarch64-linux-gnu/9 -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib -L/lib/aarch64-linux-gnu -L/lib/../lib -L/usr/lib/aarch64-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/aarch64-linux-gnu/9/../../.. -lpthread -ldl -lcurses -lgfortran -lm ./modules/console/libsciconsole.la ./modules/jvm/libscijvm.la ./modules/commons/libscicommons.la ./modules/libscilab.la -lopenblas -L/usr/lib/gcc/aarch64-linux-gnu/9 -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib -L/lib/aarch64-linux-gnu -L/lib/../lib -L/usr/lib/aarch64-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/aarch64-linux-gnu/9/../../.. -lpthread -ldl -lcurses -lgfortran -lm -lpthread -ldl -lcurses -lm libtool: link: g++ -std=c++17 -DNDEBUG -g1 -O2 -fno-stack-protector -Wl,--no-as-needed -o .libs/scilab-bin modules/startup/src/cpp/scilab_bin-scilab.o -lstdc++ -L/usr/lib/jvm/java-8-openjdk-arm64/jre/lib/aarch64 -L/usr/lib/jvm/java-8-openjdk-arm64/jre/lib/aarch64/server -L/usr/lib/aarch64-linux-gnu -L/usr/lib/gcc/aarch64-linux-gnu/9 -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu -L/usr/lib/gcc/aarch64-linux-gnu/9/../../../../lib -L/lib/aarch64-linux-gnu -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/aarch64-linux-gnu/9/../../.. ./modules/.libs/libscilab-cli.so -L/usr/local/lib/valgrind -lcoregrind-arm64-linux -lvex-arm64-linux -lgcc ./modules/console/.libs/libsciconsole.so ./modules/jvm/.libs/libscijvm.so ./modules/commons/.libs/libscicommons.so ./modules/.libs/libscilab.so /opt/Scilab/scilab/scilab/modules/gui/.libs/libscigui.so /opt/Scilab/scilab/scilab/modules/renderer/.libs/libscirenderer.so /opt/Scilab/scilab/scilab/modules/graphics/.libs/libscigraphics.so /opt/Scilab/scilab/scilab/modules/graphic_export/.libs/libscigraphic_export.so /opt/Scilab/scilab/scilab/modules/console/.libs/libsciconsole.so /opt/Scilab/scilab/scilab/modules/action_binding/.libs/libsciaction_binding.so /opt/Scilab/scilab/scilab/modules/graphic_objects/.libs/libscigraphic_objects.so /opt/Scilab/scilab/scilab/modules/scinotes/.libs/libsciscinotes.so /opt/Scilab/scilab/scilab/modules/ui_data/.libs/libsciui_data.so /opt/Scilab/scilab/scilab/modules/history_browser/.libs/libscihistory_browser.so /opt/Scilab/scilab/scilab/modules/types/.libs/libscitypes-java.so /opt/Scilab/scilab/scilab/modules/preferences/.libs/libscipreferences.so /opt/Scilab/scilab/scilab/modules/external_objects_java/.libs/libsciexternal_objects_java.so /opt/Scilab/scilab/scilab/modules/jvm/.libs/libscijvm.so -ljava -lverify -ljvm /opt/Scilab/scilab/scilab/modules/helptools/.libs/libscihelptools.so /opt/Scilab/scilab/scilab/modules/commons/.libs/libscicommons.so /opt/Scilab/scilab/scilab/modules/tclsci/.libs/libscitclsci.so -ltk8.6 -ltcl8.6 /opt/Scilab/scilab/scilab/modules/.libs/libscilab-cli.so /usr/lib/aarch64-linux-gnu/libcurl-gnutls.so /opt/Scilab/scilab/scilab/modules/functions/.libs/libscifunctions.so /opt/Scilab/scilab/scilab/modules/call_scilab/.libs/libscicall_scilab.so /opt/Scilab/scilab/scilab/modules/localization/.libs/libscilocalization.so /opt/Scilab/scilab/scilab/modules/special_functions/.libs/libscispecial_functions.so /opt/Scilab/scilab/scilab/modules/completion/.libs/libscicompletion.so /opt/Scilab/scilab/scilab/modules/history_manager/.libs/libscihistory_manager.so -lpcreposix -lpcre /opt/Scilab/scilab/scilab/modules/hdf5/.libs/libscihdf5.so -lhdf5_serial -lhdf5_serial_hl -lfftw3 /opt/Scilab/scilab/scilab/modules/statistics/.libs/libscistatistics.so /opt/Scilab/scilab/scilab/modules/ast/.libs/libsciast.so /opt/Scilab/scilab/scilab/modules/functions_manager/.libs/libscifunctions_manager.so /opt/Scilab/scilab/scilab/modules/xml/.libs/libscixml.so /opt/Scilab/scilab/scilab/modules/external_objects/.libs/libsciexternal_objects.so /opt/Scilab/scilab/scilab/modules/slint/.libs/libscislint.so /opt/Scilab/scilab/scilab/modules/coverage/.libs/libscicoverage.so -lxml2 /opt/Scilab/scilab/scilab/modules/gui/.libs/libscigui-disable.so /opt/Scilab/scilab/scilab/modules/graphics/.libs/libscigraphics-disable.so /opt/Scilab/scilab/scilab/modules/graphic_export/.libs/libscigraphic_export-disable.so /opt/Scilab/scilab/scilab/modules/console/.libs/libsciconsole-minimal.so /opt/Scilab/scilab/scilab/modules/action_binding/.libs/libsciaction_binding-disable.so /opt/Scilab/scilab/scilab/modules/jvm/.libs/libscijvm-disable.so /opt/Scilab/scilab/scilab/modules/xcos/.libs/libscixcos-disable.so /opt/Scilab/scilab/scilab/modules/graphic_objects/.libs/libscigraphic_objects-disable.so /opt/Scilab/scilab/scilab/modules/scinotes/.libs/libsciscinotes-disable.so /opt/Scilab/scilab/scilab/modules/ui_data/.libs/libsciui_data-disable.so /opt/Scilab/scilab/scilab/modules/history_browser/.libs/libscihistory_browser-disable.so /opt/Scilab/scilab/scilab/modules/commons/.libs/libscicommons-disable.so /opt/Scilab/scilab/scilab/modules/preferences/.libs/libscipreferences-cli.so /opt/Scilab/scilab/scilab/modules/tclsci/.libs/libscitclsci-disable.so -lstdc++fs -lopenblas -lgfortran -lpthread -ldl -lcurses -lm -pthread -Wl,-rpath -Wl,/usr/local/lib/scilab /bin/ld: /usr/local/lib/valgrind/libcoregrind-arm64-linux.a(libcoregrind_arm64_linux_a-m_main.o): in function `_start': m_main.c:(.text+0x0): multiple definition of `_start'; /usr/lib/gcc/aarch64-linux-gnu/9/../../../aarch64-linux-gnu/Scrt1.o:(.text+0x0): first defined here /bin/ld: /usr/local/lib/valgrind/libcoregrind-arm64-linux.a(libcoregrind_arm64_linux_a-m_main.o): in function `valgrind_main': /root/Desktop/valgrind-3.12.0/coregrind/m_main.c:2081: undefined reference to `vgPlain_tl_pre_clo_init' /bin/ld: /root/Desktop/valgrind-3.12.0/coregrind/m_main.c:2081: undefined reference to `vgPlain_tl_pre_clo_init' collect2: error: ld returned 1 exit status make[1]: *** [Makefile:1216: scilab-bin] Error 1 make[1]: Leaving directory '/opt/Scilab/scilab/scilab' make: *** [Makefile:1608: all-recursive] Error 1 root at localhost:/opt/Scilab/scilab/scilab# I even deleted the valgrind files and even make clean before attempting this? The config still try to link valgrind. -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From sgougeon at free.fr Tue Sep 15 07:32:11 2020 From: sgougeon at free.fr (Samuel Gougeon) Date: Tue, 15 Sep 2020 07:32:11 +0200 Subject: [Scilab-users] plot(x,y,':') & dotted line : is this a bug? In-Reply-To: References: Message-ID: <19f003de-96d6-5b4c-21df-5a4426e277c7@free.fr> Le 14/09/2020 ? 16:14, Antoine Monmayrant a ?crit?: > Hello all, > > For some reason, I don't understand the output of: > > ??? plot(rand(1:10),':') > > This should be a 'dotted line', as explained on the page: > ??? https://help.scilab.org/docs/6.1.0/en_US/LineSpec.html > > But I get a line_style==5 which is some kind of 1dash-2dots line. > Looking at what's on page: > https://help.scilab.org/docs/6.1.0/en_US/polyline_properties.html > I think it would make more sense to get line_style==7, 9 or 10, no? > > I have the same behaviour with 5.5.2. > Do you think this is worth a bug report? Please see http://bugzilla.scilab.org/16366 The bug was fixed on last April 16th, for 6.1.1 Samuel From antoine.monmayrant at laas.fr Tue Sep 15 07:58:11 2020 From: antoine.monmayrant at laas.fr (Antoine Monmayrant) Date: Tue, 15 Sep 2020 07:58:11 +0200 Subject: [Scilab-users] plot(x,y,':') & dotted line : is this a bug? In-Reply-To: <19f003de-96d6-5b4c-21df-5a4426e277c7@free.fr> References: <19f003de-96d6-5b4c-21df-5a4426e277c7@free.fr> Message-ID: <8acbb9f2-793f-7b8f-3645-a8ae9f5cfc07@laas.fr> On 15/09/2020 07:32, Samuel Gougeon wrote: > Le 14/09/2020 ? 16:14, Antoine Monmayrant a ?crit?: >> Hello all, >> >> For some reason, I don't understand the output of: >> >> ??? plot(rand(1:10),':') >> >> This should be a 'dotted line', as explained on the page: >> ??? https://help.scilab.org/docs/6.1.0/en_US/LineSpec.html >> >> But I get a line_style==5 which is some kind of 1dash-2dots line. >> Looking at what's on page: >> https://help.scilab.org/docs/6.1.0/en_US/polyline_properties.html >> I think it would make more sense to get line_style==7, 9 or 10, no? >> >> I have the same behaviour with 5.5.2. >> Do you think this is worth a bug report? > > > Please see http://bugzilla.scilab.org/16366 > The bug was fixed on last April 16th, for 6.1.1 Thanks a lot Samuel. Antoine > > Samuel > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > From anick.islam92 at gmail.com Wed Sep 16 09:44:37 2020 From: anick.islam92 at gmail.com (EnigmaVoidX) Date: Wed, 16 Sep 2020 00:44:37 -0700 (MST) Subject: [Scilab-users] Install of Scilab 6.2.Git on Arm64 success but few parts showing errors Message-ID: <1600242277870-0.post@n3.nabble.com> Hello everyone, After disabling valgrind I was able to succesfully make Scilab 6.2.git. Running it in gui works, scinotes, xcos works. atoms works to, initiates download of atom files. However a few things don't work. 1). Plot shows black window, but if I export the plot to a png, you can see the graphs 2). benchmark for linear algebra fails with segmentation for some, however utilizing examples of the linear algebra functions from scilab wiki work. 3). test run pass the first 2 modules, ast and atoms have some issues, throwing out an error "slave scilab exit with code 1. I downloaded a few examples from scilab,in which has downloadable scripts from engineering books and they all work fine, showing correct answers, so I assume the install is working? I have attached a text file logging these errors for you: scilab_arm64.txt Hopefully I can find some clarification on these errors. Thanks -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From Jean-Yves.Baudais at insa-rennes.fr Wed Sep 16 12:19:16 2020 From: Jean-Yves.Baudais at insa-rennes.fr (Jean-Yves Baudais) Date: Wed, 16 Sep 2020 12:19:16 +0200 Subject: [Scilab-users] Install of Scilab 6.2.Git on Arm64 success but few parts showing errors In-Reply-To: <1600242277870-0.post@n3.nabble.com> References: <1600242277870-0.post@n3.nabble.com> Message-ID: <1b89d17d-e641-03ac-a0ae-cb3bf428d2a6@insa-rennes.fr> Hi, Le 16/09/2020 ? 09:44, EnigmaVoidX a ?crit?: > 1). Plot shows black window, but if I export the plot to a png, you can see > the graphs I faced similar problem. It was solved by changing the graphics driver. -- Jean-Yves From stepan.podhorsky at gmail.com Wed Sep 16 12:43:04 2020 From: stepan.podhorsky at gmail.com (Steve) Date: Wed, 16 Sep 2020 03:43:04 -0700 (MST) Subject: [Scilab-users] PID controller simulation in Scilab/Xcos Message-ID: <1600252984695-0.post@n3.nabble.com> Hello, I have been attempting to resolve following issue related to the simulation in Scilab/Xcos. I have been developing a control software and at the time being I have been developing a library of the building blocks. One of the building blocks is a PID controller. I have written the C code of the PID controller in velocity form and my idea was to verify its behavior via simulation in Scilab/Xcos with the CBLOCK usage. For that purpose I have developed following simulation in Scilab/Xcos The internal details of the PID Controller super block: the code inside the CBLOCK: #include #include #include #include FILE *f; // U(k-1) double U1 = 0.0; // E(k-1) double E1 = 0.0; // E(k-2) double E2 = 0.0; // Ud(k-1) double Ud1 = 0.0; // Ud(k-2) double Ud2 = 0.0; // act(k-1) double A1 = 0.0; // act(k-2) double A2 = 0.0; void PID_controller(scicos_block *block,int flag) { /* int block->nevprt; int block->nz; double* block->z; int block->nx; double* block->x; double* block->xd; double* block->res; int block->nin; int *block->insz; double **block->inptr; int block->nout; int *block->outsz; double **block->outptr; int block->nevout; int block->nrpar; double *block->rpar; int block->nipar; int *block->ipar; int block->ng; double *block->g; int *block->jroot; char block->label[41]; */ if (flag == 4) { /* initialization */ PID_controller_bloc_init(block,flag); } else if(flag == 1) { /* output computation*/ set_block_error(PID_controller_bloc_outputs(block,flag)); } else if(flag == 2) { /* computation of next discrte state*/ set_block_error(PID_controller_bloc_states(block,flag)); } else if (flag == 5) { /* ending */ set_block_error(PID_controller_bloc_ending(block,flag)); } } int PID_controller_bloc_init(scicos_block *block,int flag) { f = fopen("PID.txt", "w"); fprintf(f, "R A2 A1 A E2 E1 E DUp DUi DUd U1 U SatU\n"); fprintf(f, "==============================================================================================================================================================================================================\n"); return 0; } int PID_controller_bloc_outputs(scicos_block *block,int flag) { // block parameters double Kp; double Ti; double Td; double N; double Umin; double Umax; double T; // reference value double R; // actual value double A; // control error double E; // control value double U; double SatU; // increment of proportional part double DUp; // increment of integration part double DUi; // increment of derivative part double DUd; // derivative part double Ud; // increment of control value double DU; // reading in of the block inputs R = block->inptr[0][0]; A = block->inptr[1][0]; // reading in of the block parameters Kp = block->rpar[0]; Ti = block->rpar[1]; Td = block->rpar[2]; N = block->rpar[3]; Umin = block->rpar[4]; Umax = block->rpar[5]; T = block->rpar[6]; // current control error E = R - A; DUp = Kp*(E - E1); // increment of proportional part DUi = (Kp*T)/(2*Ti)*(E + E1); // increment of integration part DUd = (Td)/(Td + N*T)*(Ud1 - Ud2) - (Kp*Td*N)/(Td + N*T)*(A - 2*A1 + A2); // increment of derivative part with filtering pole Ud = Ud1 + DUd; // derivative part DU = DUp + DUi + DUd; // increment of control value U = U1 + DU; // control value // saturation of the control value according to the limits of the actuator if(U > Umax) { SatU = Umax; } else if(U < Umin) { SatU = Umin; } else { SatU = U; } U1 = SatU; // writing at the outputs block->outptr[0][0] = SatU; fprintf(f, "%f, %f, %f, %f, %f, %f, %f %f %f %f %f %f %f \n", R, A2, A1, A, E2, E1, E, DUp, DUi, DUd, U1, U, SatU); // memory refresh E2 = E1; E1 = E; A2 = A1; A1 = A; Ud2 = Ud1; Ud1 = Ud; return 0; } int PID_controller_bloc_states(scicos_block *block,int flag) { return 0; } int PID_controller_bloc_ending(scicos_block *block,int flag) { fclose(f); return 0; } I have run the simulation with below given setup and I have received following outcomes The outcomes seemed strange to me. So I have decided to develop the whole simulation in C language in parallel. The C code of my simulation: #include #include #include // random noise in <-0.01; +0.01> #define RANDOM_NOISE (0.02*((double)rand()/(double)RAND_MAX) - 0.01) FILE *f; typedef struct { float T; float tau; float out1; }FilterLP_t; typedef struct { float T; float Kp; float Ti; float Td; float N; float OutMin; float OutMax; float Ud1; float Ud2; float U1; float Err1; float Err2; float Act1; float Act2; }PID_t; void filter(float *in, float *out, FilterLP_t *instance); void pid(float *ref, float *act, float *out, PID_t *instance); /* * */ int main(int argc, char** argv) { f = fopen("PID_Sim.txt", "w"); FilterLP_t sysModel; sysModel.T = 0.01; sysModel.tau = 10.0; sysModel.out1= 0.0; PID_t controller; controller.T = 0.01; controller.Kp = 3.0; controller.Ti = 0.125; controller.Td = 2.0; controller.N = 2.0; controller.OutMin = 0.0; controller.OutMax = 1.5; controller.Ud1 = 0.0; controller.Ud2 = 0.0; controller.U1 = 0.0; controller.Err1 = 0.0; controller.Err2 = 0.0; controller.Act1 = 0.0; controller.Act2 = 0.0; float ref = 1.0; float sysIn; float sysOut = 0.0; float sysOutMeasured = 0.0; fprintf(f, "r(k), u(k), y(k)\n"); fprintf(f, "====================\n"); uint16_t i; for(i = 0; i < 3000; i++) { pid(&ref, &sysOutMeasured, &sysIn, &controller); filter(&sysIn, &sysOut, &sysModel); sysOutMeasured = sysOut; fprintf(f, "%f, %f, %f \n", ref, sysIn, sysOut); } fclose(f); return (EXIT_SUCCESS); } void filter(float *in, float *out, FilterLP_t *instance) { float tmp; tmp = instance->out1 + (instance->T/(instance->T + instance->tau))*(*in - instance->out1); instance->out1 = tmp; *out = tmp; } void pid(float *ref, float *act, float *out, PID_t *instance) { double Ki, Ad, Bd; double Err, DUp, DUi, DUd, Ud, DU, U, SatU; Ki = (instance->Kp*instance->T)/(2*instance->Ti); Ad = instance->Td/(instance->Td + instance->N*instance->T); Bd = (instance->Kp*instance->Td*instance->N)/(instance->Td + instance->N*instance->T); Err = *ref - *act; DUp = instance->Kp*(Err - instance->Err1); DUi = Ki*(Err + instance->Err1); DUd = Ad*(instance->Ud1 - instance->Ud2) - Bd*(*act - 2*instance->Act1 + instance->Act2); Ud = instance->Ud1 + DUd; DU = DUp + DUi + DUd; U = instance->U1 + DU; if(U > instance->OutMax) { SatU = instance->OutMax; } else if(U < instance->OutMin) { SatU = instance->OutMin; } else { SatU = U; } instance->U1 = SatU; *out = SatU; instance->Err2 = instance->Err1; instance->Err1 = Err; instance->Act2 = instance->Act1; instance->Act1 = *act; instance->Ud2 = instance->Ud1; instance->Ud1 = Ud; } I have run the simulation with exactly the same PID controller settings and I have received these outcomes There are obvious differences between what the Scilab/Xcos gives and what gives my simulation in C language. I trust more the C language simulation. So I would say that there is some problem in my simulation in the Scilab/Xcos. Unfortunatelly I don't know what is wrong. It seems that the control loop in the Scilab/Xcos has lower damping than in the C language simulation. Does anybody have any idea why this behavior occurs? -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From anick.islam92 at gmail.com Wed Sep 16 21:58:04 2020 From: anick.islam92 at gmail.com (EnigmaVoidX) Date: Wed, 16 Sep 2020 12:58:04 -0700 (MST) Subject: [Scilab-users] Install of Scilab 6.2.Git on Arm64 success but few parts showing errors In-Reply-To: <1b89d17d-e641-03ac-a0ae-cb3bf428d2a6@insa-rennes.fr> References: <1600242277870-0.post@n3.nabble.com> <1b89d17d-e641-03ac-a0ae-cb3bf428d2a6@insa-rennes.fr> Message-ID: <1600286284303-0.post@n3.nabble.com> Hello, Is there away to use software acceletation? I'm running this inside a proot environment in termux, so there isn't any hardware acceleration. All the mesa drivers are up to date. Thanks. -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From stepan.podhorsky at gmail.com Mon Sep 21 16:23:12 2020 From: stepan.podhorsky at gmail.com (Steve) Date: Mon, 21 Sep 2020 07:23:12 -0700 (MST) Subject: [Scilab-users] Hybrid simulation in Scilab/Xcos In-Reply-To: <1748d47ffd5.11ce77d42362671.412388770989212371@bytecode-asia.com> References: <1600092785963-0.post@n3.nabble.com> <1748d47ffd5.11ce77d42362671.412388770989212371@bytecode-asia.com> Message-ID: <1600698192594-0.post@n3.nabble.com> Hello Tan Chin Luh, thank you for your reaction. My problem is not in the discretization process itself. I have the difference equation of the PID controller. So I have attempted to develop the simulation and I have hit a problem which I have attempted to describe in another question (please see the link: http://mailinglists.scilab.org/Scilab-users-PID-controller-simulation-in-Scilab-Xcos-td4041014.html.). I have found that the problem mentioned in the link vanishes in case I use one clock source for whole simulation (the only one used clock source is the one which controls the S/H blocks). Do you have any idea why this behavior occurs? (I think that it could be caused by the aliasing phenomenon). Do you think that the simulation mentioned in the link (with one clock source) is correct? -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From Clement.David at esi-group.com Mon Sep 21 17:26:09 2020 From: Clement.David at esi-group.com (=?iso-8859-1?Q?Cl=E9ment_David?=) Date: Mon, 21 Sep 2020 15:26:09 +0000 Subject: [Scilab-users] forge.scilab.org retirement Message-ID: Dear users, toolbox contributors, We started to provide forge.scilab.org eight years ago intending to maintain Scilab toolboxes as projects with source code and bug reports. This was supposed to ease the maintenance and delivery of high-quality toolboxes. This required us to provide a reliable service and extra IT work out of Scilab development. After Github.com and Gitlab.com successes, the needs of a forge dedicated to Scilab are not present anymore. Projects can be hosted and referenced with ease; these websites have high availability and extra services that we cannot provide. Beginning today, all projects are migrated to a GitLab sub-project [1] and will remain accessible from there. If needed, request the access to write on your repository (from the GitLab interface) or migrate it somewhere else. The forge server is still up for now but will be discarded soon. [1]: https://gitlab.com/esi-group/scilab/forge -- Cl?ment DAVID Scilab Team From radia.feddag at gmail.com Thu Sep 17 21:16:43 2020 From: radia.feddag at gmail.com (Radia fd) Date: Thu, 17 Sep 2020 21:16:43 +0200 Subject: [Scilab-users] Unable to download Scilab on my computer Message-ID: Madam, Sir, I contact you to inform you that I have been unable to download Scilab on my MacBook Pro for a few weeks. Indeed, as soon as I try to open it, I am asked to download JAVA SE 6, which I do ... But, once JAVA is downloaded, it still doesn't open because the JAVA 6 version is too obsolete for Mac today, how can I solve this problem ? because it is a necessary software for my computer courses. Thank you in advance, -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephane.mottelet at utc.fr Mon Sep 21 17:54:51 2020 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Mon, 21 Sep 2020 17:54:51 +0200 Subject: [Scilab-users] Unable to download Scilab on my computer In-Reply-To: References: Message-ID: Hi, You will find instructions there: https://www.utc.fr/~mottelet/scilab_for_macOS.html S. Le 17/09/2020 ? 21:16, Radia fd a ?crit?: > Madam, Sir, > > I contact you to inform you that I have been unable to download Scilab > on my MacBook Pro for a few weeks. Indeed, as soon as I try to open > it, I am asked to download JAVA SE 6, which I do ... But, once JAVA is > downloaded, it still doesn't open because the JAVA 6 version is too > obsolete for Mac today, how can I solve this problem ? because it is a > necessary software for my computer courses. > > Thank you in advance, > > > _______________________________________________ > 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 stepan.podhorsky at gmail.com Sat Sep 26 09:03:21 2020 From: stepan.podhorsky at gmail.com (Steve) Date: Sat, 26 Sep 2020 00:03:21 -0700 (MST) Subject: [Scilab-users] C code in Xcos simulation Message-ID: <1601103801079-0.post@n3.nabble.com> Hello, I have hit a problem regarding the Xcos c_block usage. I have developed a c_block with following C code: #include #include void Ramp(flag,nevprt,t,xd,x,nx,z,nz,tvec, ntvec,rpar,nrpar,ipar,nipar ,u1,nu1,y1,ny1) double *t,xd[],x[],z[],tvec[]; int *flag,*nevprt,*nx,*nz,*ntvec,*nrpar,ipar[],*nipar,*nu1,*ny1; double rpar[],u1[],y1[]; /* modify below this line */ { static double target = 0; static double inputDelta = 0; static double out = 0; if(u1[0] != target) { target = u1[0]; if(target - y1[0] < 0) { inputDelta = y1[0] - target; } else { inputDelta = target - y1[0]; } } if(target > y1[0]) { out += inputDelta*rpar[2]/rpar[0]; if(out > target) { out = target; } } else if(target < y1[0]) { out -= inputDelta*rpar[2]/rpar[1]; if(out < target) { out = target; } } y1[0] = out; } Xcos simulation containing this block works but my problem is that I need to have multiple instances of this block in one Xcos simulation (each instance with different set of parameters). I have tried to make several copies of this block and set different values of parameters for each copy. This naive approach resulted in wrong behavior of all the instances (all the instances gave exactly the same output but this output did not correspond to any set of parameters). My question is whether it is ever possible to have multiple instances of one c_block in one simulation? If so, can anybody give me an advice how to do that? -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From antoine.monmayrant at laas.fr Mon Sep 28 11:05:56 2020 From: antoine.monmayrant at laas.fr (Antoine Monmayrant) Date: Mon, 28 Sep 2020 11:05:56 +0200 Subject: [Scilab-users] scilab -f file : can it uses an existing instance of scilab? Message-ID: <3a98b1af-d431-c56f-f49f-dbbcc88eeb95@laas.fr> Hello all, During teaching, I usually run a bunch of scilab demos using "scilab -f demofile1", "scilab -f demofile2", etc ... Sadly, every call to "scilab -f file" opens a new instance of scilab. Is this possible to reuse an existing instance of scilab? Or even better: reuse an instance of scilab or open scilab if none exists? Cheers, Antoine From stephane.mottelet at utc.fr Mon Sep 28 16:34:35 2020 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Mon, 28 Sep 2020 16:34:35 +0200 Subject: [Scilab-users] Sci-IPOpt updated Message-ID: <7cf98655-af74-4544-8edb-41d0cdff7173@utc.fr> Hello, The Sci-IPOpt toolbox has been updated and now work (smoothly) for Scilab 6.1. Users needing a serious tool for doing optimization with general nonlinear constraint should give it a try. There is no Windows version for the moment but I hope we will have one before Christmas ! Enjoy ! -- 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 jrafaelbguerra at hotmail.com Mon Sep 28 16:40:55 2020 From: jrafaelbguerra at hotmail.com (Rafael Guerra) Date: Mon, 28 Sep 2020 14:40:55 +0000 Subject: [Scilab-users] scilab -f file : can it uses an existing instance of scilab? Message-ID: Hi Antoine, >From an existing Scilab console doing: exec("filepath\filename",-1), is not good enough? Regards, Rafael -----Original Message----- From: users On Behalf Of Antoine Monmayrant Sent: Monday, September 28, 2020 12:06 PM To: users at lists.scilab.org Subject: [Scilab-users] scilab -f file : can it uses an existing instance of scilab? Hello all, During teaching, I usually run a bunch of scilab demos using "scilab -f demofile1", "scilab -f demofile2", etc ... Sadly, every call to "scilab -f file" opens a new instance of scilab. Is this possible to reuse an existing instance of scilab? Or even better: reuse an instance of scilab or open scilab if none exists? Cheers, Antoine From antoine.monmayrant at laas.fr Mon Sep 28 17:20:08 2020 From: antoine.monmayrant at laas.fr (Antoine Monmayrant) Date: Mon, 28 Sep 2020 17:20:08 +0200 Subject: [Scilab-users] xsave or save Message-ID: <6c42c750-7959-1a15-e462-e9a07b8ae880@laas.fr> Hello all, Just wondering what is the normal way to save graphics nowadays. I just had a look at 'help xsave' to see whether it is deprecated or whether this is the official way to do it. This page reads: "For graphics xsave(file_name,win_num) use preferably save(file_name,scf(win_num))." Hmm, I don't get it. Does it mean that I should better use "save(file_name,scf(win_num))" for graphics objects? If it's the case, what is the point of xsave? I'm a bit lost... Antoine From stephane.mottelet at utc.fr Tue Sep 29 21:59:19 2020 From: stephane.mottelet at utc.fr (stephane.mottelet at utc.fr) Date: Tue, 29 Sep 2020 21:59:19 +0200 Subject: [Scilab-users] Sci-IPOpt updated Message-ID: <20200929215919.Horde.EPILtwMaWXa7KD33mo6iZVJ@webmail.utc.fr> Hello, This year Christmas arrived in september: although Windows really sucks, I managed with the help of Antoine to build a version of the toolbox for this operating system. Windows users should be able to install sci_ipopt from the atoms GUI (Optimization category). However, there is a little glitch because the Intel Fortran runtime bundled with Scilab is a little bit outdated and this is a problem for the thirdparty ipopt DLL. Hence, once you have installed the toolbox, loading it after a restart will fail. Hopefully there is an easy fix and I have bundled a little script dedicated to this. Hence, after the Scilab restart and the failing Sci-IPOpt load, just type the following at Scilab's prompt: --> cd(atomsGetInstalledPath("sci_ipopt")) --> exec windows_ifort_fix.sce then restart Scilab: the toolbox should load just fine (run one of the demos to make sure that everything works). The Intel Fortran runtime will surely be updated for the next Scilab release and this fix won't be anymore necessary. S. St?phane Mottelet a ?crit?: > Hello, > > The Sci-IPOpt toolbox has been updated and now work (smoothly) for > Scilab 6.1. Users needing a serious tool for doing optimization with > general nonlinear constraint should give it a try. There is no > Windows version for the moment but I hope we will have one before > Christmas ! > > Enjoy ! > > -- > 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 > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/www.utc.fr/~mottelet > > _______________________________________________ > users mailing list > users at lists.scilab.orghttps://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.cheze at cea.fr Wed Sep 30 09:51:22 2020 From: david.cheze at cea.fr (CHEZE David 227480) Date: Wed, 30 Sep 2020 07:51:22 +0000 Subject: [Scilab-users] Sci-IPOpt updated In-Reply-To: <20200929215919.Horde.EPILtwMaWXa7KD33mo6iZVJ@webmail.utc.fr> References: <20200929215919.Horde.EPILtwMaWXa7KD33mo6iZVJ@webmail.utc.fr> Message-ID: Hello St?phane, I?ve just make an attempt to install the Sci-IPOpt toolbox from atoms on windows_10_64bits OS, following your recommendations below. I got message that the fix (after exec windows_ifort_fix.sce) was successfully applied but once I restart Scilab (6.1.0 release), the module fails to load with the message: Start SciIPOpt Load gateways atomsLoad : Une erreur est survenue au cours du chargement de 'sci_ipopt-1.0': exec: error on line #18: "link : La biblioth?que partag?e n'a pas ?t? charg?e: Unknown Error" nb: I?ve quite recent Intel visual fortran composer xe (2018) installed on this machine which may interfere with the fix ? Regards, David De : users De la part de stephane.mottelet at utc.fr Envoy? : mardi 29 septembre 2020 21:59 ? : Users mailing list for Scilab Objet : Re: [Scilab-users] Sci-IPOpt updated Hello, This year Christmas arrived in september: although Windows really sucks, I managed with the help of Antoine to build a version of the toolbox for this operating system. Windows users should be able to install sci_ipopt from the atoms GUI (Optimization category). However, there is a little glitch because the Intel Fortran runtime bundled with Scilab is a little bit outdated and this is a problem for the thirdparty ipopt DLL. Hence, once you have installed the toolbox, loading it after a restart will fail. Hopefully there is an easy fix and I have bundled a little script dedicated to this. Hence, after the Scilab restart and the failing Sci-IPOpt load, just type the following at Scilab's prompt: --> cd(atomsGetInstalledPath("sci_ipopt")) --> exec windows_ifort_fix.sce then restart Scilab: the toolbox should load just fine (run one of the demos to make sure that everything works). The Intel Fortran runtime will surely be updated for the next Scilab release and this fix won't be anymore necessary. S. St?phane Mottelet > a ?crit : Hello, The Sci-IPOpt toolbox has been updated and now work (smoothly) for Scilab 6.1. Users needing a serious tool for doing optimization with general nonlinear constraint should give it a try. There is no Windows version for the moment but I hope we will have one before Christmas ! Enjoy ! -- 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 https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/www.utc.fr/~mottelet _______________________________________________ users mailing list users at lists.scilab.orghttps://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From perrichon.pierre at wanadoo.fr Wed Sep 30 11:28:15 2020 From: perrichon.pierre at wanadoo.fr (perrichon.pierre at wanadoo.fr) Date: Wed, 30 Sep 2020 11:28:15 +0200 Subject: [Scilab-users] Sci-IPOpt updated In-Reply-To: References: <20200929215919.Horde.EPILtwMaWXa7KD33mo6iZVJ@webmail.utc.fr> Message-ID: <000001d6970c$0d5081f0$27f185d0$@wanadoo.fr> Hello, Same error for me on Win10 x64b Regards Pierre De : users De la part de CHEZE David 227480 Envoy? : mercredi 30 septembre 2020 09:51 ? : Users mailing list for Scilab Objet : Re: [Scilab-users] Sci-IPOpt updated Hello St?phane, I?ve just make an attempt to install the Sci-IPOpt toolbox from atoms on windows_10_64bits OS, following your recommendations below. I got message that the fix (after exec windows_ifort_fix.sce) was successfully applied but once I restart Scilab (6.1.0 release), the module fails to load with the message: Start SciIPOpt Load gateways atomsLoad : Une erreur est survenue au cours du chargement de 'sci_ipopt-1.0': exec: error on line #18: "link : La biblioth?que partag?e n'a pas ?t? charg?e: Unknown Error" nb: I?ve quite recent Intel visual fortran composer xe (2018) installed on this machine which may interfere with the fix ? Regards, David De : users > De la part de stephane.mottelet at utc.fr Envoy? : mardi 29 septembre 2020 21:59 ? : Users mailing list for Scilab > Objet : Re: [Scilab-users] Sci-IPOpt updated Hello, This year Christmas arrived in september: although Windows really sucks, I managed with the help of Antoine to build a version of the toolbox for this operating system. Windows users should be able to install sci_ipopt from the atoms GUI (Optimization category). However, there is a little glitch because the Intel Fortran runtime bundled with Scilab is a little bit outdated and this is a problem for the thirdparty ipopt DLL. Hence, once you have installed the toolbox, loading it after a restart will fail. Hopefully there is an easy fix and I have bundled a little script dedicated to this. Hence, after the Scilab restart and the failing Sci-IPOpt load, just type the following at Scilab's prompt: --> cd(atomsGetInstalledPath("sci_ipopt")) --> exec windows_ifort_fix.sce then restart Scilab: the toolbox should load just fine (run one of the demos to make sure that everything works). The Intel Fortran runtime will surely be updated for the next Scilab release and this fix won't be anymore necessary. S. St?phane Mottelet > a ?crit : Hello, The Sci-IPOpt toolbox has been updated and now work (smoothly) for Scilab 6.1. Users needing a serious tool for doing optimization with general nonlinear constraint should give it a try. There is no Windows version for the moment but I hope we will have one before Christmas ! Enjoy ! -- 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 https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/www.utc.fr/~mottelet _______________________________________________ users mailing list users at lists.scilab .orghttps://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephane.mottelet at utc.fr Wed Sep 30 12:14:14 2020 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Wed, 30 Sep 2020 12:14:14 +0200 Subject: [Scilab-users] Sci-IPOpt updated In-Reply-To: References: <20200929215919.Horde.EPILtwMaWXa7KD33mo6iZVJ@webmail.utc.fr> Message-ID: <5152cd50-9956-f1e1-aa6e-7345e294c8d1@utc.fr> Hi, Can you restart Scilab but in console mode ? You should have a dialog box giving more information about the link problem) S. Le 30/09/2020 ? 09:51, CHEZE David 227480 a ?crit?: > > Hello St?phane, > > I?ve just make an attempt to install the Sci-IPOpt toolbox from atoms > on windows_10_64bits OS, following your recommendations below. I got > message that the fix (after exec windows_ifort_fix.sce) was > successfully applied but once I restart Scilab (6.1.0 release), the > module fails to load with the message: > > Start SciIPOpt > > Load gateways > > atomsLoad : Une erreur est survenue au cours du chargement de > 'sci_ipopt-1.0': > > exec: error on line #18: "link : La biblioth?que partag?e n'a pas ?t? > charg?e: Unknown Error" > > nb: I?ve quite recent Intel visual fortran composer xe (2018) > installed on this machine which may interfere with the fix ? > > Regards, > > David > > *De?:*users *De la part de* > stephane.mottelet at utc.fr > *Envoy??:* mardi 29 septembre 2020 21:59 > *??:* Users mailing list for Scilab > *Objet?:* Re: [Scilab-users] Sci-IPOpt updated > > Hello, > > This year Christmas arrived in september: although Windows really > sucks, I managed with the help of Antoine to build a version of the > toolbox for this operating system. Windows users should be able to > install sci_ipopt from the atoms GUI (Optimization category). However, > there is a little glitch because the Intel Fortran runtime bundled > with Scilab is a little bit outdated and this is a problem for the > thirdparty ipopt DLL. Hence, once you have installed the toolbox, > loading it after a restart will fail. Hopefully there is an easy fix > and I have bundled a little script dedicated to this. Hence, after the > Scilab restart and the failing Sci-IPOpt load, just type the following > at Scilab's prompt: > > --> cd(atomsGetInstalledPath("sci_ipopt")) > --> exec windows_ifort_fix.sce > > then restart Scilab: the toolbox should load just fine (run one of the > demos to make sure that everything works). The Intel Fortran runtime > will surely be updated for the next Scilab release and this fix won't > be anymore necessary. > > S. > > St?phane Mottelet > a ?crit?: > > Hello, > > The Sci-IPOpt toolbox has been updated and now work (smoothly) for > Scilab 6.1. Users needing a serious tool for doing optimization > with general nonlinear constraint should give it a try. There is > no Windows version for the moment but I hope we will have one > before Christmas ! > > Enjoy ! > > -- > 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 > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/www.utc.fr/~mottelet > > > _______________________________________________ > users mailing list > users at lists.scilab > .orghttps://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users > > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users -- 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 david.cheze at cea.fr Wed Sep 30 15:41:05 2020 From: david.cheze at cea.fr (CHEZE David 227480) Date: Wed, 30 Sep 2020 13:41:05 +0000 Subject: [Scilab-users] Sci-IPOpt updated In-Reply-To: <5152cd50-9956-f1e1-aa6e-7345e294c8d1@utc.fr> References: <20200929215919.Horde.EPILtwMaWXa7KD33mo6iZVJ@webmail.utc.fr> <5152cd50-9956-f1e1-aa6e-7345e294c8d1@utc.fr> Message-ID: Hi, It fails equally with the following windows error message box : Scilex.exe Point d?entr?e introuvable Le point d?entr?e de proc?dure for_realloc_lhs est introuvable dans la biblioth?que de liens dynamiques \AppData\Local\scilab-6.1.0\contrib\sci_ipopt\1.0\thirdparty\Windows\bin\ipopt-3.dll Let me know if I can help further in any way. Regards, David De : users De la part de St?phane Mottelet Envoy? : mercredi 30 septembre 2020 12:14 ? : users at lists.scilab.org Objet : Re: [Scilab-users] Sci-IPOpt updated Hi, Can you restart Scilab but in console mode ? You should have a dialog box giving more information about the link problem) S. Le 30/09/2020 ? 09:51, CHEZE David 227480 a ?crit : Hello St?phane, I?ve just make an attempt to install the Sci-IPOpt toolbox from atoms on windows_10_64bits OS, following your recommendations below. I got message that the fix (after exec windows_ifort_fix.sce) was successfully applied but once I restart Scilab (6.1.0 release), the module fails to load with the message: Start SciIPOpt Load gateways atomsLoad : Une erreur est survenue au cours du chargement de 'sci_ipopt-1.0': exec: error on line #18: "link : La biblioth?que partag?e n'a pas ?t? charg?e: Unknown Error" nb: I?ve quite recent Intel visual fortran composer xe (2018) installed on this machine which may interfere with the fix ? Regards, David De : users De la part de stephane.mottelet at utc.fr Envoy? : mardi 29 septembre 2020 21:59 ? : Users mailing list for Scilab Objet : Re: [Scilab-users] Sci-IPOpt updated Hello, This year Christmas arrived in september: although Windows really sucks, I managed with the help of Antoine to build a version of the toolbox for this operating system. Windows users should be able to install sci_ipopt from the atoms GUI (Optimization category). However, there is a little glitch because the Intel Fortran runtime bundled with Scilab is a little bit outdated and this is a problem for the thirdparty ipopt DLL. Hence, once you have installed the toolbox, loading it after a restart will fail. Hopefully there is an easy fix and I have bundled a little script dedicated to this. Hence, after the Scilab restart and the failing Sci-IPOpt load, just type the following at Scilab's prompt: --> cd(atomsGetInstalledPath("sci_ipopt")) --> exec windows_ifort_fix.sce then restart Scilab: the toolbox should load just fine (run one of the demos to make sure that everything works). The Intel Fortran runtime will surely be updated for the next Scilab release and this fix won't be anymore necessary. S. St?phane Mottelet > a ?crit : Hello, The Sci-IPOpt toolbox has been updated and now work (smoothly) for Scilab 6.1. Users needing a serious tool for doing optimization with general nonlinear constraint should give it a try. There is no Windows version for the moment but I hope we will have one before Christmas ! Enjoy ! -- 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 https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/www.utc.fr/~mottelet _______________________________________________ users mailing list users at lists.scilab.orghttps://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users _______________________________________________ users mailing list users at lists.scilab.org https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users -- 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 Wed Sep 30 16:48:15 2020 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Wed, 30 Sep 2020 16:48:15 +0200 Subject: [Scilab-users] Sci-IPOpt updated In-Reply-To: References: <20200929215919.Horde.EPILtwMaWXa7KD33mo6iZVJ@webmail.utc.fr> <5152cd50-9956-f1e1-aa6e-7345e294c8d1@utc.fr> Message-ID: That's what the windows_ifort_fix.sce script is supposed to fix. Can you verify the libifcoremd.dll (date, size) in the bin/ folder of your Scilab ? Le 30/09/2020 ? 15:41, CHEZE David 227480 a ?crit?: > > Hi, > > It fails equally with the following windows error message box : > > Scilex.exe Point d?entr?e introuvable > > Le point d?entr?e de proc?dure for_realloc_lhs est introuvable > ??????????????? dans la biblioth?que de liens dynamiques > \AppData\Local\scilab-6.1.0\contrib\sci_ipopt\1.0\thirdparty\Windows\bin\ipopt-3.dll > > Let me know if I can help further in any way. > > Regards, > > David > > *De?:*users *De la part de* St?phane > Mottelet > *Envoy??:* mercredi 30 septembre 2020 12:14 > *??:* users at lists.scilab.org > *Objet?:* Re: [Scilab-users] Sci-IPOpt updated > > Hi, > > Can you restart Scilab but in console mode ? You should have a dialog > box giving more information about the link problem) > > S. > > Le 30/09/2020 ? 09:51, CHEZE David 227480 a ?crit?: > > Hello St?phane, > > I?ve just make an attempt to install the Sci-IPOpt toolbox from > atoms on windows_10_64bits OS, following your recommendations > below. I got message that the fix (after exec > windows_ifort_fix.sce) was successfully applied but once I restart > Scilab (6.1.0 release), the module fails to load with the message: > > Start SciIPOpt > > Load gateways > > atomsLoad : Une erreur est survenue au cours du chargement de > 'sci_ipopt-1.0': > > exec: error on line #18: "link : La biblioth?que partag?e n'a pas > ?t? charg?e: Unknown Error" > > nb: I?ve quite recent Intel visual fortran composer xe (2018) > installed on this machine which may interfere with the fix ? > > Regards, > > David > > *De?:*users > *De la part de* > stephane.mottelet at utc.fr > *Envoy??:* mardi 29 septembre 2020 21:59 > *??:* Users mailing list for Scilab > > *Objet?:* Re: [Scilab-users] Sci-IPOpt updated > > Hello, > > This year Christmas arrived in september: although Windows really > sucks, I managed with the help of Antoine to build a version of > the toolbox for this operating system. Windows users should be > able to install sci_ipopt from the atoms GUI (Optimization > category). However, there is a little glitch because the Intel > Fortran runtime bundled with Scilab is a little bit outdated and > this is a problem for the thirdparty ipopt DLL. Hence, once you > have installed the toolbox, loading it after a restart will fail. > Hopefully there is an easy fix and I have bundled a little script > dedicated to this. Hence, after the Scilab restart and the failing > Sci-IPOpt load, just type the following at Scilab's prompt: > > --> cd(atomsGetInstalledPath("sci_ipopt")) > --> exec windows_ifort_fix.sce > > then restart Scilab: the toolbox should load just fine (run one of > the demos to make sure that everything works). The Intel Fortran > runtime will surely be updated for the next Scilab release and > this fix won't be anymore necessary. > > S. > > St?phane Mottelet > a ?crit?: > > Hello, > > The Sci-IPOpt toolbox has been updated and now work (smoothly) > for Scilab 6.1. Users needing a serious tool for doing > optimization with general nonlinear constraint should give it > a try. There is no Windows version for the moment but I hope > we will have one before Christmas ! > > Enjoy ! > > -- > 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 > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/www.utc.fr/~mottelet > > > _______________________________________________ > users mailing list > users at lists.scilab > .orghttps://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users > > > > > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users > > -- > 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 p.muehlmann at gmail.com Wed Sep 30 16:50:26 2020 From: p.muehlmann at gmail.com (P M) Date: Wed, 30 Sep 2020 16:50:26 +0200 Subject: [Scilab-users] Fwd: plotting dots vs xfarc In-Reply-To: References: Message-ID: Dear community, I need to create images, which includes exact dot-coordinates, drawn as filled circles. All pixel coordinates of such an area would have to have exactly one single pixel value. The resulting graphic right now is stored via: xs2bmp. to create the dots I naturally would use: plot (x,y,'o') Issues here: - It seems that the resulting pixels of the dot in the final image are not equally colored. - Especially pixels at the right lower "corner" seem to be off-colored. So I tried: xfarc: Issue here: - xfarc() seems not always to find the correct x-y-location. See example attached. - The dots by plot() are colored white. - The xfarc is colored blue. I left some dots without xfarc() to demonstrate the issue of plot(). I think I could "brute-force" pixel values of the underlying image (not black for real purpose) to correct pixel values. But actually I wanted to avoid that. Any hint? Used: Scilab 6.1.0 Best regards, Philipp -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: randomDistribution.png Type: image/png Size: 7788 bytes Desc: not available URL: From david.cheze at cea.fr Wed Sep 30 17:57:16 2020 From: david.cheze at cea.fr (CHEZE David 227480) Date: Wed, 30 Sep 2020 15:57:16 +0000 Subject: [Scilab-users] Sci-IPOpt updated In-Reply-To: References: <20200929215919.Horde.EPILtwMaWXa7KD33mo6iZVJ@webmail.utc.fr> <5152cd50-9956-f1e1-aa6e-7345e294c8d1@utc.fr> Message-ID: libifcoremd.dll, intel fortan comiler RTL (thread-safe), 27/10/2017 17:32, version fichier 14.0.103.103,produit intel visual fortran compiler, version produit 14.0 update A De : users De la part de St?phane Mottelet Envoy? : mercredi 30 septembre 2020 16:48 ? : users at lists.scilab.org Objet : Re: [Scilab-users] Sci-IPOpt updated That's what the windows_ifort_fix.sce script is supposed to fix. Can you verify the libifcoremd.dll (date, size) in the bin/ folder of your Scilab ? Le 30/09/2020 ? 15:41, CHEZE David 227480 a ?crit : Hi, It fails equally with the following windows error message box : Scilex.exe Point d?entr?e introuvable Le point d?entr?e de proc?dure for_realloc_lhs est introuvable dans la biblioth?que de liens dynamiques \AppData\Local\scilab-6.1.0\contrib\sci_ipopt\1.0\thirdparty\Windows\bin\ipopt-3.dll Let me know if I can help further in any way. Regards, David De : users De la part de St?phane Mottelet Envoy? : mercredi 30 septembre 2020 12:14 ? : users at lists.scilab.org Objet : Re: [Scilab-users] Sci-IPOpt updated Hi, Can you restart Scilab but in console mode ? You should have a dialog box giving more information about the link problem) S. Le 30/09/2020 ? 09:51, CHEZE David 227480 a ?crit : Hello St?phane, I?ve just make an attempt to install the Sci-IPOpt toolbox from atoms on windows_10_64bits OS, following your recommendations below. I got message that the fix (after exec windows_ifort_fix.sce) was successfully applied but once I restart Scilab (6.1.0 release), the module fails to load with the message: Start SciIPOpt Load gateways atomsLoad : Une erreur est survenue au cours du chargement de 'sci_ipopt-1.0': exec: error on line #18: "link : La biblioth?que partag?e n'a pas ?t? charg?e: Unknown Error" nb: I?ve quite recent Intel visual fortran composer xe (2018) installed on this machine which may interfere with the fix ? Regards, David De : users De la part de stephane.mottelet at utc.fr Envoy? : mardi 29 septembre 2020 21:59 ? : Users mailing list for Scilab Objet : Re: [Scilab-users] Sci-IPOpt updated Hello, This year Christmas arrived in september: although Windows really sucks, I managed with the help of Antoine to build a version of the toolbox for this operating system. Windows users should be able to install sci_ipopt from the atoms GUI (Optimization category). However, there is a little glitch because the Intel Fortran runtime bundled with Scilab is a little bit outdated and this is a problem for the thirdparty ipopt DLL. Hence, once you have installed the toolbox, loading it after a restart will fail. Hopefully there is an easy fix and I have bundled a little script dedicated to this. Hence, after the Scilab restart and the failing Sci-IPOpt load, just type the following at Scilab's prompt: --> cd(atomsGetInstalledPath("sci_ipopt")) --> exec windows_ifort_fix.sce then restart Scilab: the toolbox should load just fine (run one of the demos to make sure that everything works). The Intel Fortran runtime will surely be updated for the next Scilab release and this fix won't be anymore necessary. S. St?phane Mottelet > a ?crit : Hello, The Sci-IPOpt toolbox has been updated and now work (smoothly) for Scilab 6.1. Users needing a serious tool for doing optimization with general nonlinear constraint should give it a try. There is no Windows version for the moment but I hope we will have one before Christmas ! Enjoy ! -- 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 https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/www.utc.fr/~mottelet _______________________________________________ users mailing list users at lists.scilab.orghttps://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users _______________________________________________ users mailing list users at lists.scilab.org https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users -- 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 jrafaelbguerra at hotmail.com Wed Sep 30 19:11:45 2020 From: jrafaelbguerra at hotmail.com (Rafael Guerra) Date: Wed, 30 Sep 2020 17:11:45 +0000 Subject: [Scilab-users] Fwd: plotting dots vs xfarc In-Reply-To: References: Message-ID: Hi, Type in help: pixel_drawing_mode Could this help for your problem? Regards, Rafael From: users On Behalf Of P M Sent: Wednesday, September 30, 2020 5:50 PM To: International users mailing list for Scilab. Subject: [Scilab-users] Fwd: plotting dots vs xfarc Dear community, I need to create images, which includes exact dot-coordinates, drawn as filled circles. All pixel coordinates of such an area would have to have exactly one single pixel value. The resulting graphic right now is stored via: xs2bmp. to create the dots I naturally would use: plot (x,y,'o') Issues here: - It seems that the resulting pixels of the dot in the final image are not equally colored. - Especially pixels at the right lower "corner" seem to be off-colored. So I tried: xfarc: Issue here: - xfarc() seems not always to find the correct x-y-location. See example attached. - The dots by plot() are colored white. - The xfarc is colored blue. I left some dots without xfarc() to demonstrate the issue of plot(). I think I could "brute-force" pixel values of the underlying image (not black for real purpose) to correct pixel values. But actually I wanted to avoid that. Any hint? Used: Scilab 6.1.0 Best regards, Philipp -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephane.mottelet at utc.fr Wed Sep 30 19:27:07 2020 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Wed, 30 Sep 2020 19:27:07 +0200 Subject: [Scilab-users] Sci-IPOpt updated In-Reply-To: References: <20200929215919.Horde.EPILtwMaWXa7KD33mo6iZVJ@webmail.utc.fr> <5152cd50-9956-f1e1-aa6e-7345e294c8d1@utc.fr> Message-ID: <5fd09fd5-ebc3-c30b-4b96-7e2f7c0f700d@utc.fr> Ok. I am sorry for this mistake, the identifier is wrong in the windows_ifort_fix.sce script. I have updated the binary package at the Atoms portal but you should be fine after replacing atomsGetInstalledPath('Sci-IPopt') by atomsGetInstalledPath('sci_ipopt') in the script. S. Le 30/09/2020 ? 17:57, CHEZE David 227480 a ?crit?: > > libifcoremd.dll, intel fortan comiler RTL (thread-safe), 27/10/2017 > 17:32, version fichier 14.0.103.103,produit ?intel visual fortran > compiler, version produit 14.0 update A > > *De?:*users *De la part de* St?phane > Mottelet > *Envoy??:* mercredi 30 septembre 2020 16:48 > *??:* users at lists.scilab.org > *Objet?:* Re: [Scilab-users] Sci-IPOpt updated > > That's what the windows_ifort_fix.sce script is supposed to fix. Can > you verify the libifcoremd.dll (date, size) in the bin/ folder of your > Scilab ? > > Le 30/09/2020 ? 15:41, CHEZE David 227480 a ?crit?: > > Hi, > > It fails equally with the following windows error message box : > > Scilex.exe Point d?entr?e introuvable > > Le point d?entr?e de proc?dure for_realloc_lhs est introuvable > ??????????????? dans la biblioth?que de liens dynamiques > \AppData\Local\scilab-6.1.0\contrib\sci_ipopt\1.0\thirdparty\Windows\bin\ipopt-3.dll > > Let me know if I can help further in any way. > > Regards, > > David > > *De?:*users > *De la part de* St?phane > Mottelet > *Envoy??:* mercredi 30 septembre 2020 12:14 > *??:* users at lists.scilab.org > *Objet?:* Re: [Scilab-users] Sci-IPOpt updated > > Hi, > > Can you restart Scilab but in console mode ? You should have a > dialog box giving more information about the link problem) > > S. > > Le 30/09/2020 ? 09:51, CHEZE David 227480 a ?crit?: > > Hello St?phane, > > I?ve just make an attempt to install the Sci-IPOpt toolbox > from atoms on windows_10_64bits OS, following your > recommendations below. I got message that the fix (after exec > windows_ifort_fix.sce) was successfully applied but once I > restart Scilab (6.1.0 release), the module fails to load with > the message: > > Start SciIPOpt > > Load gateways > > atomsLoad : Une erreur est survenue au cours du chargement de > 'sci_ipopt-1.0': > > exec: error on line #18: "link : La biblioth?que partag?e n'a > pas ?t? charg?e: Unknown Error" > > nb: I?ve quite recent Intel visual fortran composer xe (2018) > installed on this machine which may interfere with the fix ? > > Regards, > > David > > *De?:*users > *De la part de* > stephane.mottelet at utc.fr > *Envoy??:* mardi 29 septembre 2020 21:59 > *??:* Users mailing list for Scilab > > *Objet?:* Re: [Scilab-users] Sci-IPOpt updated > > Hello, > > This year Christmas arrived in september: although Windows > really sucks, I managed with the help of Antoine to build a > version of the toolbox for this operating system. Windows > users should be able to install sci_ipopt from the atoms GUI > (Optimization category). However, there is a little glitch > because the Intel Fortran runtime bundled with Scilab is a > little bit outdated and this is a problem for the thirdparty > ipopt DLL. Hence, once you have installed the toolbox, loading > it after a restart will fail. Hopefully there is an easy fix > and I have bundled a little script dedicated to this. Hence, > after the Scilab restart and the failing Sci-IPOpt load, just > type the following at Scilab's prompt: > > --> cd(atomsGetInstalledPath("sci_ipopt")) > --> exec windows_ifort_fix.sce > > then restart Scilab: the toolbox should load just fine (run > one of the demos to make sure that everything works). The > Intel Fortran runtime will surely be updated for the next > Scilab release and this fix won't be anymore necessary. > > S. > > St?phane Mottelet > a ?crit?: > > Hello, > > The Sci-IPOpt toolbox has been updated and now work > (smoothly) for Scilab 6.1. Users needing a serious tool > for doing optimization with general nonlinear constraint > should give it a try. There is no Windows version for the > moment but I hope we will have one before Christmas ! > > Enjoy ! > > -- > 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 > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/www.utc.fr/~mottelet > > > _______________________________________________ > users mailing list > users at lists.scilab > .orghttps://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users > > > > > > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users > > -- > > St?phane Mottelet > > Ing?nieur de recherche > > EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable > > D?partement G?nie des Proc?d?s Industriels > > Sorbonne Universit?s - Universit? de Technologie de Compi?gne > > CS 60319, 60203 Compi?gne cedex > > Tel : +33(0)344234688 > > http://www.utc.fr/~mottelet > > > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users > > -- > St?phane Mottelet > Ing?nieur de recherche > EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable > D?partement G?nie des Proc?d?s Industriels > Sorbonne Universit?s - Universit? de Technologie de Compi?gne > CS 60319, 60203 Compi?gne cedex > Tel : +33(0)344234688 > http://www.utc.fr/~mottelet > > _______________________________________________ > users mailing list > users at lists.scilab.org > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users -- St?phane Mottelet Ing?nieur de recherche EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable D?partement G?nie des Proc?d?s Industriels Sorbonne Universit?s - Universit? de Technologie de Compi?gne CS 60319, 60203 Compi?gne cedex Tel : +33(0)344234688 http://www.utc.fr/~mottelet -------------- next part -------------- An HTML attachment was scrubbed... URL: