From delaleau at enib.fr Tue May 1 00:50:22 2018 From: delaleau at enib.fr (Emmanuel Delaleau) Date: Tue, 1 May 2018 00:50:22 +0200 Subject: [Scilab-users] Scliab 6.0.x compilation problem (jogl2) In-Reply-To: <87lgd5djln.wl-nomiya@galaxy.dti.ne.jp> References: <6b2a8014-6244-9c3f-3c74-1b25d79cbc64@enib.fr> <8736zd8llt.wl-nomiya@galaxy.dti.ne.jp> <87lgd5djln.wl-nomiya@galaxy.dti.ne.jp> Message-ID: <65f1016b-cc20-4d0d-1668-d6156c8e590b@enib.fr> I have all jogl2 and gluegen2 packages included in Debian/stable installed and still the same error message. Le 30/04/2018 ? 13:22, Masaru Nomiya a ?crit?: > Hello, > > In the Message; > > Subject : Re: [Scilab-users] Scliab 6.0.x compilation problem (jogl2) > Message-ID : > Date & Time: Mon, 30 Apr 2018 10:16:55 +0200 > > [ED] == Emmanuel Delaleau has written: > > ED> Dear Masaru Nomiya, thank you for your response. See result below (I am under > ED> Debian and I use dpkg instead of rpm) : > > ED> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > ED> delaleau at ed-lapt:~$ dpkg -L libjogl2-java > ED> /. > ED> /usr > ED> /usr/share > ED> /usr/share/doc > ED> /usr/share/doc/libjogl2-java > ED> /usr/share/doc/libjogl2-java/README.Debian > ED> /usr/share/doc/libjogl2-java/changelog.Debian.gz > ED> /usr/share/doc/libjogl2-java/changelog.gz > ED> /usr/share/doc/libjogl2-java/copyright > ED> /usr/share/java > ED> /usr/share/java/jogl2-2.3.2.jar > ED> /usr/share/maven-repo > ED> /usr/share/maven-repo/org > ED> /usr/share/maven-repo/org/jogamp > ED> /usr/share/maven-repo/org/jogamp/jogl > ED> /usr/share/maven-repo/org/jogamp/jogl/jogl-all > ED> /usr/share/maven-repo/org/jogamp/jogl/jogl-all/2.3.2 > ED> /usr/share/maven-repo/org/jogamp/jogl/jogl-all/2.3.2/jogl-all-2.3.2.pom > ED> /usr/share/maven-repo/org/jogamp/jogl/jogl-all/debian > ED> /usr/share/maven-repo/org/jogamp/jogl/jogl-all/debian/jogl-all-debian.pom > ED> /usr/share/java/jogl2.jar > ED> /usr/share/maven-repo/org/jogamp/jogl/jogl-all/2.3.2/jogl-all-2.3.2.jar > ED> /usr/share/maven-repo/org/jogamp/jogl/jogl-all/debian/jogl-all-debian.jar > > ED> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > ED> delaleau at ed-lapt:~$ dpkg -L libgluegen2-rt-java > ED> /. > ED> /usr > ED> /usr/share > ED> /usr/share/doc > ED> /usr/share/doc/libgluegen2-rt-java > ED> /usr/share/doc/libgluegen2-rt-java/changelog.Debian.gz > ED> /usr/share/doc/libgluegen2-rt-java/copyright > ED> /usr/share/java > ED> /usr/share/java/gluegen2-rt-2.3.2.jar > ED> /usr/share/maven-repo > ED> /usr/share/maven-repo/org > ED> /usr/share/maven-repo/org/jogamp > ED> /usr/share/maven-repo/org/jogamp/gluegen > ED> /usr/share/maven-repo/org/jogamp/gluegen/gluegen-rt > ED> /usr/share/maven-repo/org/jogamp/gluegen/gluegen-rt/2.3.2 > ED> /usr/share/maven-repo/org/jogamp/gluegen/gluegen-rt/2.3.2/gluegen-rt-2.3.2.pom > ED> /usr/share/maven-repo/org/jogamp/gluegen/gluegen-rt/debian > ED> /usr/share/maven-repo/org/jogamp/gluegen/gluegen-rt/debian/gluegen-rt-debian.pom > ED> /usr/share/java/gluegen2-rt.jar > ED> /usr/share/maven-repo/org/jogamp/gluegen/gluegen-rt/2.3.2/gluegen-rt-2.3.2.jar > ED> /usr/share/maven-repo/org/jogamp/gluegen/gluegen-rt/debian/gluegen-rt-debian.jar > > As you might know, gulegen2 and jogl2 ara key factors for building > scilab 6.0.x. > > You don't have gluegen2-rt.so, do you? > > This is strange. Without gluegen2-rt.so, you can't compile scilab. > > Another problem.?Do as follows; > > # mkdir /usr/lib64/java > # ln -s /usr/share/java/jogl2.jar /usr/lib64/java > > Regards, > > --- > ????? Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp > ???? > ???? "Bill! You married with Computers. > Not with Me!" > "No..., with money." > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users From heinznabielek at me.com Thu May 3 10:57:18 2018 From: heinznabielek at me.com (Heinz Nabielek) Date: Thu, 03 May 2018 10:57:18 +0200 Subject: [Scilab-users] needed: SciLab routine for generating Weibull random variables with prior given autocorrelation In-Reply-To: <65f1016b-cc20-4d0d-1668-d6156c8e590b@enib.fr> References: <6b2a8014-6244-9c3f-3c74-1b25d79cbc64@enib.fr> <8736zd8llt.wl-nomiya@galaxy.dti.ne.jp> <87lgd5djln.wl-nomiya@galaxy.dti.ne.jp> <65f1016b-cc20-4d0d-1668-d6156c8e590b@enib.fr> Message-ID: Friends: urgently needed: a SciLab routine for generating Weibull random variables with prior given autocorrelation. Uncorrelated is easy with vc*((-log(grand(1,5,"def"))).^(1/m)) producing 0.9666848 1.4646143 10.402793 5.9513675 3.3241823 with characteristic velocity vc=7 and modulus m=2. But I need Weibull deviates with given autocorrelation, say rho=0.80 Literature has dozen of references on the subject which either do not work or I do not know how to code. Any help here? Heinz From heinznabielek at me.com Thu May 3 11:15:29 2018 From: heinznabielek at me.com (Heinz Nabielek) Date: Thu, 03 May 2018 11:15:29 +0200 Subject: [Scilab-users] needed: SciLab routine for generating Weibull random variables with prior given autocorrelation In-Reply-To: References: <6b2a8014-6244-9c3f-3c74-1b25d79cbc64@enib.fr> <8736zd8llt.wl-nomiya@galaxy.dti.ne.jp> <87lgd5djln.wl-nomiya@galaxy.dti.ne.jp> <65f1016b-cc20-4d0d-1668-d6156c8e590b@enib.fr> Message-ID: Uniform U(0,1) random deviates with given autocorrelation would be good enough?... > On 03.05.2018, at 10:57, Heinz Nabielek wrote: > > Friends: > > urgently needed: a SciLab routine for generating Weibull random variables with prior given autocorrelation. > > Uncorrelated is easy with > vc*((-log(grand(1,5,"def"))).^(1/m)) producing > 0.9666848 1.4646143 10.402793 5.9513675 3.3241823 > with characteristic velocity vc=7 and modulus m=2. > > But I need Weibull deviates with given autocorrelation, say rho=0.80 > > Literature has dozen of references on the subject which either do not work or I do not know how to code. > > Any help here? > Heinz From stephane.mottelet at utc.fr Thu May 3 11:37:38 2018 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Thu, 3 May 2018 11:37:38 +0200 Subject: [Scilab-users] needed: SciLab routine for generating Weibull random variables with prior given autocorrelation In-Reply-To: References: <6b2a8014-6244-9c3f-3c74-1b25d79cbc64@enib.fr> <8736zd8llt.wl-nomiya@galaxy.dti.ne.jp> <87lgd5djln.wl-nomiya@galaxy.dti.ne.jp> <65f1016b-cc20-4d0d-1668-d6156c8e590b@enib.fr> Message-ID: <61156ad9-6c46-19fb-3460-1d624e87e586@utc.fr> Why don't start with a simple autoregressive process ? See e.g. https://en.wikipedia.org/wiki/Autoregressive_model Le 03/05/2018 ? 11:15, Heinz Nabielek a ?crit?: > Uniform U(0,1) random deviates with given autocorrelation would be good enough?... > > >> On 03.05.2018, at 10:57, Heinz Nabielek wrote: >> >> Friends: >> >> urgently needed: a SciLab routine for generating Weibull random variables with prior given autocorrelation. >> >> Uncorrelated is easy with >> vc*((-log(grand(1,5,"def"))).^(1/m)) producing >> 0.9666848 1.4646143 10.402793 5.9513675 3.3241823 >> with characteristic velocity vc=7 and modulus m=2. >> >> But I need Weibull deviates with given autocorrelation, say rho=0.80 >> >> Literature has dozen of references on the subject which either do not work or I do not know how to code. >> >> Any help here? >> Heinz > _______________________________________________ > users mailing list > users at lists.scilab.org > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users From heinznabielek at me.com Thu May 3 15:49:04 2018 From: heinznabielek at me.com (Heinz Nabielek) Date: Thu, 03 May 2018 15:49:04 +0200 Subject: [Scilab-users] needed: SciLab routine for generating Weibull random variables with prior given autocorrelation In-Reply-To: <61156ad9-6c46-19fb-3460-1d624e87e586@utc.fr> References: <6b2a8014-6244-9c3f-3c74-1b25d79cbc64@enib.fr> <8736zd8llt.wl-nomiya@galaxy.dti.ne.jp> <87lgd5djln.wl-nomiya@galaxy.dti.ne.jp> <65f1016b-cc20-4d0d-1668-d6156c8e590b@enib.fr> <61156ad9-6c46-19fb-3460-1d624e87e586@utc.fr> Message-ID: Many thanks. works fine on an originating normal distribution [where i would not need it, because we have grand(n, "mn", Mean, Cov) in SciLab]. With an initiating U(-0.5, 0,5), however, I get a triangle function, but not a autocorrelated uniform random distribution. What to do? Heinz > On 03.05.2018, at 11:37, St?phane Mottelet wrote: > > Why don't start with a simple autoregressive process ? See e.g. > > https://en.wikipedia.org/wiki/Autoregressive_model > > > Le 03/05/2018 ? 11:15, Heinz Nabielek a ?crit : >> Uniform U(0,1) random deviates with given autocorrelation would be good enough?... >> >> >>> On 03.05.2018, at 10:57, Heinz Nabielek wrote: >>> >>> Friends: >>> >>> urgently needed: a SciLab routine for generating Weibull random variables with prior given autocorrelation. >>> >>> Uncorrelated is easy with >>> vc*((-log(grand(1,5,"def"))).^(1/m)) producing >>> 0.9666848 1.4646143 10.402793 5.9513675 3.3241823 >>> with characteristic velocity vc=7 and modulus m=2. >>> >>> But I need Weibull deviates with given autocorrelation, say rho=0.80 >>> >>> Literature has dozen of references on the subject which either do not work or I do not know how to code. >>> >>> Any help here? >>> Heinz From stephane.mottelet at utc.fr Thu May 3 17:40:39 2018 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Thu, 3 May 2018 17:40:39 +0200 Subject: [Scilab-users] needed: SciLab routine for generating Weibull random variables with prior given autocorrelation In-Reply-To: References: <6b2a8014-6244-9c3f-3c74-1b25d79cbc64@enib.fr> <8736zd8llt.wl-nomiya@galaxy.dti.ne.jp> <87lgd5djln.wl-nomiya@galaxy.dti.ne.jp> <65f1016b-cc20-4d0d-1668-d6156c8e590b@enib.fr> <61156ad9-6c46-19fb-3460-1d624e87e586@utc.fr> Message-ID: <2bb062ce-3002-2581-10d9-d0172adfafc7@utc.fr> Le 03/05/2018 ? 15:49, Heinz Nabielek a ?crit?: > Many thanks. works fine on an originating normal distribution [where i would not need it, because we have grand(n, "mn", Mean, Cov) in SciLab]. grand(n, "mn", Mean, Cov) allows to generate realizations of a multi-normal variable, i.e. covariance matrix describes the covariance between each component? of the (vector) variable. AR processes are different stuff (random process <> random variable). For an AR process the non-idependance is w.r.t. to time (discrete or continuous) Your wind data is a random process. > With an initiating U(-0.5, 0,5), however, I get a triangle function, but not a autocorrelated uniform random distribution. what do you mean by " autocorrelated uniform random distribution" ? Here your triangle is just the distribution of a sum of two uniform vraiables. S. > What to do? > Heinz > > > > >> On 03.05.2018, at 11:37, St?phane Mottelet wrote: >> >> Why don't start with a simple autoregressive process ? See e.g. >> >> https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/en.wikipedia.org/wiki/Autoregressive_model >> >> >> Le 03/05/2018 ? 11:15, Heinz Nabielek a ?crit : >>> Uniform U(0,1) random deviates with given autocorrelation would be good enough?... >>> >>> >>>> On 03.05.2018, at 10:57, Heinz Nabielek wrote: >>>> >>>> Friends: >>>> >>>> urgently needed: a SciLab routine for generating Weibull random variables with prior given autocorrelation. >>>> >>>> Uncorrelated is easy with >>>> vc*((-log(grand(1,5,"def"))).^(1/m)) producing >>>> 0.9666848 1.4646143 10.402793 5.9513675 3.3241823 >>>> with characteristic velocity vc=7 and modulus m=2. >>>> >>>> But I need Weibull deviates with given autocorrelation, say rho=0.80 >>>> >>>> Literature has dozen of references on the subject which either do not work or I do not know how to code. >>>> >>>> Any help here? >>>> Heinz > _______________________________________________ > users mailing list > users at lists.scilab.org > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users From stephane.mottelet at utc.fr Thu May 3 18:29:42 2018 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Thu, 3 May 2018 18:29:42 +0200 Subject: [Scilab-users] needed: SciLab routine for generating Weibull random variables with prior given autocorrelation In-Reply-To: References: <6b2a8014-6244-9c3f-3c74-1b25d79cbc64@enib.fr> <8736zd8llt.wl-nomiya@galaxy.dti.ne.jp> <87lgd5djln.wl-nomiya@galaxy.dti.ne.jp> <65f1016b-cc20-4d0d-1668-d6156c8e590b@enib.fr> <61156ad9-6c46-19fb-3460-1d624e87e586@utc.fr> Message-ID: <9d5d4a61-c10b-9f45-8511-72fcad501ad1@utc.fr> Le 03/05/2018 ? 15:49, Heinz Nabielek a ?crit?: > Many thanks. works fine on an originating normal distribution [where i would not need it, because we have grand(n, "mn", Mean, Cov) in SciLab]. grand(n, "mn", Mean, Cov) allows to generate realizations of a multi-normal variable, i.e. covariance matrix describes the covariance between each component? of the (vector) variable. AR processes are different stuff (random process <> random variable). For an AR process the non-idependance is w.r.t. to time (discrete or continuous) Your wind data is a random process. > With an initiating U(-0.5, 0,5), however, I get a triangle function, but not a autocorrelated uniform random distribution. what do you mean by " autocorrelated uniform random distribution" ? Here your triangle is just the distribution of a sum of two uniform variables. S. > What to do? > Heinz > > > > >> On 03.05.2018, at 11:37, St?phane Mottelet wrote: >> >> Why don't start with a simple autoregressive process ? See e.g. >> >> https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/en.wikipedia.org/wiki/Autoregressive_model >> >> >> Le 03/05/2018 ? 11:15, Heinz Nabielek a ?crit : >>> Uniform U(0,1) random deviates with given autocorrelation would be good enough?... >>> >>> >>>> On 03.05.2018, at 10:57, Heinz Nabielek wrote: >>>> >>>> Friends: >>>> >>>> urgently needed: a SciLab routine for generating Weibull random variables with prior given autocorrelation. >>>> >>>> Uncorrelated is easy with >>>> vc*((-log(grand(1,5,"def"))).^(1/m)) producing >>>> 0.9666848 1.4646143 10.402793 5.9513675 3.3241823 >>>> with characteristic velocity vc=7 and modulus m=2. >>>> >>>> But I need Weibull deviates with given autocorrelation, say rho=0.80 >>>> >>>> Literature has dozen of references on the subject which either do not work or I do not know how to code. >>>> >>>> Any help here? >>>> Heinz > _______________________________________________ > users mailing list > users at lists.scilab.org > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users From heinznabielek at me.com Thu May 3 18:30:51 2018 From: heinznabielek at me.com (Heinz Nabielek) Date: Thu, 03 May 2018 18:30:51 +0200 Subject: [Scilab-users] needed: SciLab routine for generating Weibull random variables with prior given autocorrelation In-Reply-To: <2bb062ce-3002-2581-10d9-d0172adfafc7@utc.fr> References: <6b2a8014-6244-9c3f-3c74-1b25d79cbc64@enib.fr> <8736zd8llt.wl-nomiya@galaxy.dti.ne.jp> <87lgd5djln.wl-nomiya@galaxy.dti.ne.jp> <65f1016b-cc20-4d0d-1668-d6156c8e590b@enib.fr> <61156ad9-6c46-19fb-3460-1d624e87e586@utc.fr> <2bb062ce-3002-2581-10d9-d0172adfafc7@utc.fr> Message-ID: <66650484-E817-4E27-9BB2-0DA6E2304DB8@me.com> thanks. but still: how construct autocorrelated uniform randoms? Sent from Heinz Nabielek > On 03 May 2018, at 17:40, St?phane Mottelet wrote: > >> Le 03/05/2018 ? 15:49, Heinz Nabielek a ?crit : >> Many thanks. works fine on an originating normal distribution [where i would not need it, because we have grand(n, "mn", Mean, Cov) in SciLab]. > grand(n, "mn", Mean, Cov) allows to generate realizations of a multi-normal variable, i.e. covariance matrix describes the covariance between each component of the (vector) variable. > > AR processes are different stuff (random process <> random variable). For an AR process the non-idependance is w.r.t. to time (discrete or continuous) > > Your wind data is a random process. >> With an initiating U(-0.5, 0,5), however, I get a triangle function, but not a autocorrelated uniform random distribution. > what do you mean by " autocorrelated uniform random distribution" ? Here your triangle is just the distribution of a sum of two uniform vraiables. > > S. >> What to do? >> Heinz >> >> >> >> >>> On 03.05.2018, at 11:37, St?phane Mottelet wrote: >>> >>> Why don't start with a simple autoregressive process ? See e.g. >>> >>> https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/en.wikipedia.org/wiki/Autoregressive_model >>> >>> >>>> Le 03/05/2018 ? 11:15, Heinz Nabielek a ?crit : >>>> Uniform U(0,1) random deviates with given autocorrelation would be good enough?... >>>> >>>> >>>>> On 03.05.2018, at 10:57, Heinz Nabielek wrote: >>>>> >>>>> Friends: >>>>> >>>>> urgently needed: a SciLab routine for generating Weibull random variables with prior given autocorrelation. >>>>> >>>>> Uncorrelated is easy with >>>>> vc*((-log(grand(1,5,"def"))).^(1/m)) producing >>>>> 0.9666848 1.4646143 10.402793 5.9513675 3.3241823 >>>>> with characteristic velocity vc=7 and modulus m=2. >>>>> >>>>> But I need Weibull deviates with given autocorrelation, say rho=0.80 >>>>> >>>>> Literature has dozen of references on the subject which either do not work or I do not know how to code. >>>>> >>>>> Any help here? >>>>> Heinz >> _______________________________________________ >> users mailing list >> users at lists.scilab.org >> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/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 May 4 15:31:43 2018 From: sgougeon at free.fr (Samuel Gougeon) Date: Fri, 4 May 2018 15:31:43 +0200 Subject: [Scilab-users] [SEP] factorial() extension on [171, 10^14] In-Reply-To: <192586ac-7c55-8c6d-80a0-daba885f21f7@free.fr> References: <192586ac-7c55-8c6d-80a0-daba885f21f7@free.fr> Message-ID: <8749f83a-67e8-44af-f607-1c54008f6556@free.fr> Le 14/04/2018 ? 15:44, Samuel Gougeon a ?crit : > While fixing the bug 7562 about a bad memory usage by factorial(), > > i was wondering about the poor factorial() result, since currently > it can process only integers in [0, 170] before saturating and > returning %inf. > > This Scilab Enhancement Proposed (SEP) aims to extend factorial() > to all integers in [0, 10^4]. > The proposed extension goes up to n=10^14 (not 10^4) Samuel From jrafaelbguerra at hotmail.com Fri May 4 16:13:55 2018 From: jrafaelbguerra at hotmail.com (Rafael Guerra) Date: Fri, 4 May 2018 14:13:55 +0000 Subject: [Scilab-users] [SEP] factorial() extension on [171, 10^14] In-Reply-To: <8749f83a-67e8-44af-f607-1c54008f6556@free.fr> References: <192586ac-7c55-8c6d-80a0-daba885f21f7@free.fr> <8749f83a-67e8-44af-f607-1c54008f6556@free.fr> Message-ID: Hi Samuel, How are in the proposed extension the resulting very large numbers represented? In other words, how are the limitations of double precision overcome and can we do math with such very large integers? PS: In Scilab the gammaln() function allows computing the logarithm of the factorial for large integers. Regards, Rafael -----Original Message----- From: users [mailto:users-bounces at lists.scilab.org] On Behalf Of Samuel Gougeon Sent: Friday, May 04, 2018 3:32 PM To: International users mailing list for Scilab. Subject: Re: [Scilab-users] [SEP] factorial() extension on [171, 10^14] Le 14/04/2018 ? 15:44, Samuel Gougeon a ?crit : > While fixing the bug 7562 about a bad memory usage by factorial(), > > i was wondering about the poor factorial() result, since currently it > can process only integers in [0, 170] before saturating and returning > %inf. > > This Scilab Enhancement Proposed (SEP) aims to extend factorial() to > all integers in [0, 10^4]. > The proposed extension goes up to n=10^14 (not 10^4) Samuel _______________________________________________ users mailing list users at lists.scilab.org http://lists.scilab.org/mailman/listinfo/users From sgougeon at free.fr Fri May 4 16:23:43 2018 From: sgougeon at free.fr (Samuel Gougeon) Date: Fri, 4 May 2018 16:23:43 +0200 Subject: [Scilab-users] [SEP] factorial() extension on [171, 10^14] In-Reply-To: References: <192586ac-7c55-8c6d-80a0-daba885f21f7@free.fr> <8749f83a-67e8-44af-f607-1c54008f6556@free.fr> Message-ID: <057f169c-99c6-b4a5-e227-ac7d6fc6ac5a@free.fr> Le 04/05/2018 ? 16:13, Rafael Guerra a ?crit : > Hi Samuel, > > How are in the proposed extension the resulting very large numbers represented? > In other words, how are the limitations of double precision overcome and can we do math with such very large integers? > > PS: In Scilab the gammaln() function allows computing the logarithm of the factorial for large integers. Hello Rafael, Please see the link to the help page posted in my first message. It is documented in the page. The algorithm can be seen on CodeReview (ref in the message/bugzilla entry). It uses a careful processing with log(). It is more accurate than gammaln() by a factor of up to 100 (it is also documented in the test). Regards Samuel From sgougeon at free.fr Mon May 7 14:36:45 2018 From: sgougeon at free.fr (Samuel Gougeon) Date: Mon, 7 May 2018 14:36:45 +0200 Subject: [Scilab-users] gcf().anti_aliasing : Confirmation of (un)effect? Message-ID: <3e7e61f7-ff70-62d5-9a15-ab4a772e3ec0@free.fr> Hello, The gcf().anti_aliasing figure property was implemented many years ago (in the early Scilab 5.x versions). It aims to reduce the "staircase effect" for lines drawn very close to vertical or horizontal directions. Yet, has anyone ever seen an actual effect on graphic rendering, as expected and described in the related SEP#16 ? I never did, whatever were the computer and its graphic card i used. Still now with Scilab 6.0, i don't see any effect. The staircase effect can easily be seen with the following code: x = [0 1]; y = (0:0.02:1)'; y = [y y+0.02]'; clf plot2d(x,y) f = gcf(); f.anti_aliasing // should display "off" (by default) f = scf(); f.anti_aliasing = "8x"; plot2d(x,y) Then compare both figures. I get the following, whatever is the .anti_aliasing value. Does anyone get anything else, closer to the expected "dithered" rendering? Either it will be possible to better document the effect of this property, as requested in the bug report 6777 , or to reopen the bug 11311 reporting that it is out of work. Thanks Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: dbhpbgjbciobikhj.png Type: image/png Size: 7020 bytes Desc: not available URL: From amonmayr at laas.fr Mon May 7 15:09:24 2018 From: amonmayr at laas.fr (amonmayr at laas.fr) Date: Mon, 7 May 2018 15:09:24 +0200 Subject: [Scilab-users] gcf().anti_aliasing : Confirmation of (un)effect? In-Reply-To: <3e7e61f7-ff70-62d5-9a15-ab4a772e3ec0@free.fr> References: <3e7e61f7-ff70-62d5-9a15-ab4a772e3ec0@free.fr> Message-ID: Hello Samuel, With your example, I don't see any difference on the various computers I have. I think I used anti_aliasing in the past but I cannot find back a script where I used it. I think I used it on 3D plots (surf?), maybe for the export to graphic files but I am not sure. If I can find something I'll let you know. Antoine Le 07/05/2018 ? 14:36, Samuel Gougeon a ?crit?: > > Hello, > > The gcf().anti_aliasing figure property was implemented many years ago > (in the early Scilab 5.x versions). > > It aims to reduce the "staircase effect" for lines drawn very close to > vertical or horizontal directions. > > Yet, has anyone ever seen an actual effect on graphic rendering, as > expected and described in the related SEP#16 > > ? > I never did, whatever were the computer and its graphic card i used. > Still now with Scilab 6.0, i don't see any effect. > > The staircase effect can easily be seen with the following code: > > x = [0 1]; > y = (0:0.02:1)'; > y = [y y+0.02]'; > clf > plot2d(x,y) > f = gcf(); > f.anti_aliasing // should display "off" (by default) > > f = scf(); > f.anti_aliasing = "8x"; > plot2d(x,y) > Then compare both figures. > I get the following, whatever is the .anti_aliasing value. > > > Does anyone get anything else, closer to the expected "dithered" > rendering? > Either it will be possible to better document the effect of this property, > as requested in the bug report 6777 > , or to reopen the > bug 11311 reporting > that it is out of work. > > Thanks > Samuel > > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ Antoine Monmayrant LAAS - CNRS 7 avenue du Colonel Roche BP 54200 31031 TOULOUSE Cedex 4 FRANCE Tel:+33 5 61 33 64 59 email : antoine.monmayrant at laas.fr permanent email : antoine.monmayrant at polytechnique.org +++++++++++++++++++++++++++++++++++++++++++++++++++++++ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: dbhpbgjbciobikhj.png Type: image/png Size: 7020 bytes Desc: not available URL: From jrafaelbguerra at hotmail.com Mon May 7 16:23:42 2018 From: jrafaelbguerra at hotmail.com (Rafael Guerra) Date: Mon, 7 May 2018 07:23:42 -0700 (MST) Subject: [Scilab-users] gcf().anti_aliasing : Confirmation of (un)effect? In-Reply-To: <3e7e61f7-ff70-62d5-9a15-ab4a772e3ec0@free.fr> References: <3e7e61f7-ff70-62d5-9a15-ab4a772e3ec0@free.fr> Message-ID: <1525703022019-0.post@n3.nabble.com> Hi Samuel, Could not see any anti-aliasing being performed, either in Scilab 5 or Scilab 6. A quick trial on customizing the anti-aliasing settings in NVIDIA Quadro K4100M for the Scilab program did not help either: It may need more tweaking. Regards, Rafael -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From cfuttrup at gmail.com Mon May 7 20:45:11 2018 From: cfuttrup at gmail.com (Claus Futtrup) Date: Mon, 07 May 2018 18:45:11 +0000 Subject: [Scilab-users] GSOC 2018 Message-ID: Hi there Can Scilab confirm that there are four GSOC projects this year? I read from: https://summerofcode.withgoogle.com/organizations/4726304075677696/#! 1. About Machine Learning 2. MacOS signed app 3. Code Quality 4. Working demo for Matlab MEX modules ... and will anyone post any news about it? Maybe here: https://www.scilab.org/en/projects/gsoc Best regards, Claus -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Mon May 7 21:01:04 2018 From: sgougeon at free.fr (Samuel Gougeon) Date: Mon, 7 May 2018 21:01:04 +0200 Subject: [Scilab-users] GSOC 2018 In-Reply-To: References: Message-ID: <16a3bb71-9377-89e8-17a0-3735eded3e88@free.fr> Hello Claus, AFAIK, there is this portal on the wiki : https://wiki.scilab.org/GSoC_project_proposal and this dedicated and active mailing list : http://mailinglists.scilab.org/Scilab-GSOC-Mailing-Lists-Archives-f2646148.html But you are right : it would be worthwhile having official news here (on this list) about the selected projects and about their outcomes, status, and chances and schedule to see them available as ATOMS modules, or even afterwards being included in Scilab for some of them. Regards Samuel Le 07/05/2018 ? 20:45, Claus Futtrup a ?crit : > Hi there > > Can Scilab confirm that there are four GSOC projects this year? I read > from: > > https://summerofcode.withgoogle.com/organizations/4726304075677696/#! > > 1. About Machine Learning > 2. MacOS signed app > 3. Code Quality > 4. Working demo for Matlab MEX modules > > ... and will anyone post any news about it? Maybe here: > https://www.scilab.org/en/projects/gsoc > > Best regards, > Claus > > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From delaleau at enib.fr Fri May 11 09:42:27 2018 From: delaleau at enib.fr (Emmanuel Delaleau) Date: Fri, 11 May 2018 09:42:27 +0200 Subject: [Scilab-users] How to close/kill "messagebox" Message-ID: Hi, Does it exists a way to close/kill windows created by "messagebox". "close" or "delete" do not work as messageboxes do not have a handle. Thanks Emmanuel From amonmayr at laas.fr Fri May 11 10:26:14 2018 From: amonmayr at laas.fr (amonmayr at laas.fr) Date: Fri, 11 May 2018 10:26:14 +0200 Subject: [Scilab-users] How to close/kill "messagebox" In-Reply-To: References: Message-ID: Hello, Indeed, messagebox() seems to live outside the realm of figures and other graphic entities. It's a bit weird in my opinion. Maybe a workaround for you would be to emulate what messagebox() is doing by using a figure and a bunch of uicontrols and callbacks. That way you'll be able to treat this emulated version like any othe figure and close it using delete(winsid_of_said_figure). Hope it helps, Antoine Le 11/05/2018 ? 09:42, Emmanuel Delaleau a ?crit?: > Hi, > > > Does it exists a way to close/kill windows created by "messagebox". > > "close" or "delete" do not work as messageboxes do not have a handle. > > Thanks > > Emmanuel > > _______________________________________________ > users mailing list > users at lists.scilab.org > http://lists.scilab.org/mailman/listinfo/users > -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ Antoine Monmayrant LAAS - CNRS 7 avenue du Colonel Roche BP 54200 31031 TOULOUSE Cedex 4 FRANCE Tel:+33 5 61 33 64 59 email : antoine.monmayrant at laas.fr permanent email : antoine.monmayrant at polytechnique.org +++++++++++++++++++++++++++++++++++++++++++++++++++++++ From sgougeon at free.fr Fri May 11 11:30:05 2018 From: sgougeon at free.fr (Samuel Gougeon) Date: Fri, 11 May 2018 11:30:05 +0200 Subject: [Scilab-users] gcf().anti_aliasing : Confirmation of (un)effect? In-Reply-To: <3e7e61f7-ff70-62d5-9a15-ab4a772e3ec0@free.fr> References: <3e7e61f7-ff70-62d5-9a15-ab4a772e3ec0@free.fr> Message-ID: <25f10094-ccdf-9790-b03f-6ee496ca53ed@free.fr> Le 07/05/2018 ? 14:36, Samuel Gougeon a ?crit : > > Hello, > > The gcf().anti_aliasing figure property was implemented many years ago > (in the early Scilab 5.x versions). > > It aims to reduce the "staircase effect" for lines drawn very close to > vertical or horizontal directions. > > Yet, has anyone ever seen an actual effect on graphic rendering, as > expected and described in the related SEP#16 > > ? > I never did, whatever were the computer and its graphic card i used. > Still now with Scilab 6.0, i don't see any effect. > > The staircase effect can easily be seen with the following code: > > x = [0 1]; > y = (0:0.02:1)'; > y = [y y+0.02]'; > clf > plot2d(x,y) > f = gcf(); > f.anti_aliasing // should display "off" (by default) > > f = scf(); > f.anti_aliasing = "8x"; > plot2d(x,y) > Then compare both figures. > I get the following, whatever is the .anti_aliasing value. > > > Does anyone get anything else, closer to the expected "dithered" > rendering? > Either it will be possible to better document the effect of this property, > as requested in the bug report 6777 > , or to reopen the > bug 11311 reporting > that it is out of work. Thanks Rafael & Antoine. I have finally got it. It works * only with usecanvas(%t). The bug 11311 claimed that it was killed in usecanvas(%t) mode. Maybe fixing it has killed it in usecanvas(%f) mode... * only up to Scilab 5.4.1 included. Scilab 5.5.0 has killed any graphic rendering in usecanvas(%t) mode (and has changed the usecanvas() type of output from boolean to integer). With 5.4.1, usecanvas(%t) displays: which is the expected rendering. I am going to see what's on bugzilla about usecanvas()... Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jpndpeifadohoabc.png Type: image/png Size: 10769 bytes Desc: not available URL: From Clement.David at esi-group.com Tue May 15 17:36:38 2018 From: Clement.David at esi-group.com (=?utf-8?B?Q2zDqW1lbnQgRGF2aWQ=?=) Date: Tue, 15 May 2018 15:36:38 +0000 Subject: [Scilab-users] How to close/kill "messagebox" In-Reply-To: References: Message-ID: <1526398598.2108.4.camel@esi-group.com> Hello, Exactly messagebox() use a semi-hardcoded Java-based GUI that totally differs from the uicontrol code. If you want to mix messagebox() and regular figure(), you should (as Antoine suggested) implement a popup-like by yourself (should be ~20 lines of code). Thanks, -- Cl?ment Le vendredi 11 mai 2018 ? 10:26 +0200, amonmayr at laas.fr a ?crit : > Hello, > > > Indeed, messagebox() seems to live outside the realm of figures and > other graphic entities. > It's a bit weird in my opinion. > Maybe a workaround for you would be to emulate what messagebox() is > doing by using a figure and a bunch of uicontrols and callbacks. > That way you'll be able to treat this emulated version like any othe > figure and close it using delete(winsid_of_said_figure). > > Hope it helps, > > Antoine > > > > Le 11/05/2018 ? 09:42, Emmanuel Delaleau a ?crit : > > > > > Hi, > > > > > > Does it exists a way to close/kill windows created by "messagebox". > > > > "close" or "delete" do not work as messageboxes do not have a handle. > > > > Thanks > > > > Emmanuel > > > > _______________________________________________ > > users mailing list > > users at lists.scilab.org > > http://lists.scilab.org/mailman/listinfo/users > > > > From heinznabielek at me.com Wed May 16 00:20:16 2018 From: heinznabielek at me.com (Heinz Nabielek) Date: Wed, 16 May 2018 00:20:16 +0200 Subject: [Scilab-users] any suggestion to make my Scilab code faster would be welcome: In-Reply-To: <1526398598.2108.4.camel@esi-group.com> References: <1526398598.2108.4.camel@esi-group.com> Message-ID: <789033FA-02C6-4CAC-81EB-F6600C151760@me.com> Friends and colleagues: I have already a pretty efficient Scilab code, but any suggestion to make it faster would be welcome: I have position measurements of 20,000 objects in 3d space stored in column vectors X, Y, Z and want to explore the distribution of nearest neighbour distances. This works well like below, but an acceleration would help me a lot. Heinz n=length(X); d=[]; for i=1:n; x=X(i);y=Y(i);z=Z(i); SqDist=(X-x)^2 + (Y-y)^2 + (Z-z)^2; SqDist(i)=[]; d=[d; sqrt(min(SqDist))]; end; .. and 'd' gives me the desired distribution in a column vector of n elements From kopac.jakub at gmail.com Wed May 16 08:40:13 2018 From: kopac.jakub at gmail.com (kjubo) Date: Tue, 15 May 2018 23:40:13 -0700 (MST) Subject: [Scilab-users] any suggestion to make my Scilab code faster would be welcome: In-Reply-To: <789033FA-02C6-4CAC-81EB-F6600C151760@me.com> References: <1526398598.2108.4.camel@esi-group.com> <789033FA-02C6-4CAC-81EB-F6600C151760@me.com> Message-ID: <1526452813137-0.post@n3.nabble.com> Hello, d = zeros(n,1); for ii=1:n; // SqDist = (X-X(i))^2 + (Y-Y(i))^2 + (Z-Z(i))^2; SqDist = (X-X(ii)).*(X-X(ii)) + (Y-Y(ii)).*(Y-Y(ii)) + (Z-Z(ii)).*(Z-Z(ii)); SqDist(ii)= []; d(ii) = sqrt(min(SqDist)); end; some comments: * preallocate matrix * avoid unnecessary assign of variables (this slow down scilab more than expected) * as seen in previous meesages here, use X*X instead of X^2 for me speed up factor is ~10 Regards. -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From wozai at protonmail.ch Wed May 16 10:53:47 2018 From: wozai at protonmail.ch (Wozai) Date: Wed, 16 May 2018 01:53:47 -0700 (MST) Subject: [Scilab-users] any suggestion to make my Scilab code faster would be welcome: In-Reply-To: <789033FA-02C6-4CAC-81EB-F6600C151760@me.com> References: <1526398598.2108.4.camel@esi-group.com> <789033FA-02C6-4CAC-81EB-F6600C151760@me.com> Message-ID: <1526460827855-0.post@n3.nabble.com> Hi, A very similar problem was discussed here in length. You'll find there numerous hints how to make your code faster. Cheers Wozai -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From heinznabielek at me.com Wed May 16 19:44:18 2018 From: heinznabielek at me.com (Heinz Nabielek) Date: Wed, 16 May 2018 19:44:18 +0200 Subject: [Scilab-users] any suggestion to make my Scilab code faster would be welcome: In-Reply-To: <1526452813137-0.post@n3.nabble.com> References: <1526398598.2108.4.camel@esi-group.com> <789033FA-02C6-4CAC-81EB-F6600C151760@me.com> <1526452813137-0.post@n3.nabble.com> Message-ID: <1B2CD69D-63BD-41E0-81A0-E3B6BF07A13B@me.com> Yes- factor 10. Great many thanks for all the help. Heinz > On 16.05.2018, at 08:40, kjubo wrote: > > Hello, > > d = zeros(n,1); > for ii=1:n; > // SqDist = (X-X(i))^2 + (Y-Y(i))^2 + (Z-Z(i))^2; > SqDist = (X-X(ii)).*(X-X(ii)) + (Y-Y(ii)).*(Y-Y(ii)) + > (Z-Z(ii)).*(Z-Z(ii)); > SqDist(ii)= []; > d(ii) = sqrt(min(SqDist)); > end; > > some comments: > * preallocate matrix > * avoid unnecessary assign of variables (this slow down scilab more than > expected) > * as seen in previous meesages here, use X*X instead of X^2 > > for me speed up factor is ~10 > > Regards. From heinznabielek at me.com Wed May 16 19:58:03 2018 From: heinznabielek at me.com (Heinz Nabielek) Date: Wed, 16 May 2018 19:58:03 +0200 Subject: [Scilab-users] any suggestion to make my Scilab code faster would be welcome: In-Reply-To: <1B2CD69D-63BD-41E0-81A0-E3B6BF07A13B@me.com> References: <1526398598.2108.4.camel@esi-group.com> <789033FA-02C6-4CAC-81EB-F6600C151760@me.com> <1526452813137-0.post@n3.nabble.com> <1B2CD69D-63BD-41E0-81A0-E3B6BF07A13B@me.com> Message-ID: <9428E462-D562-4455-B87A-F48207E867C8@me.com> Histogram shows distribution of d and comparison with my model prediction. Heinz > On 16.05.2018, at 19:44, Heinz Nabielek wrote: > > Yes- factor 10. Great many thanks for all the help. > Heinz > >> On 16.05.2018, at 08:40, kjubo wrote: >> >> Hello, >> >> d = zeros(n,1); >> for ii=1:n; >> // SqDist = (X-X(i))^2 + (Y-Y(i))^2 + (Z-Z(i))^2; >> SqDist = (X-X(ii)).*(X-X(ii)) + (Y-Y(ii)).*(Y-Y(ii)) + >> (Z-Z(ii)).*(Z-Z(ii)); >> SqDist(ii)= []; >> d(ii) = sqrt(min(SqDist)); >> end; >> >> some comments: >> * preallocate matrix >> * avoid unnecessary assign of variables (this slow down scilab more than >> expected) >> * as seen in previous meesages here, use X*X instead of X^2 >> >> for me speed up factor is ~10 >> >> Regards. > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-1.tiff Type: image/tiff Size: 51494 bytes Desc: not available URL: From j.s.strom at hslmg.de Sat May 19 12:35:48 2018 From: j.s.strom at hslmg.de (Jens Simon Strom) Date: Sat, 19 May 2018 12:35:48 +0200 Subject: [Scilab-users] Exclamation mark in variable names Message-ID: <5AFFFE04.4030207@hslmg.de> Hallo Scilab intimates, Is *!a* a valid variable name in the latest version of Scilab? Vers. 6.0.1 sees an*Error: Unexpected token '!'* Kind regards Jens -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Sat May 19 13:19:21 2018 From: sgougeon at free.fr (Samuel Gougeon) Date: Sat, 19 May 2018 13:19:21 +0200 Subject: [Scilab-users] Exclamation mark in variable names In-Reply-To: <5AFFFE04.4030207@hslmg.de> References: <5AFFFE04.4030207@hslmg.de> Message-ID: Hello Jens, Le 19/05/2018 ? 12:35, Jens Simon Strom a ?crit : > Hallo Scilab intimates, > Is *!a* a valid variable name in the latest version of Scilab? > Vers. 6.0.1 sees an*Error: Unexpected token '!'* Yes it is. You have reported it as the bug 15126 , and Clement has confirmed to you that this naming should still be supported. Regards Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Mon May 21 14:10:19 2018 From: sgougeon at free.fr (Samuel Gougeon) Date: Mon, 21 May 2018 14:10:19 +0200 Subject: [Scilab-users] det([]) changed in Scilab 6.0 Message-ID: Hello, While updating "help empty" after changes in Scilab 6 about inequality comparisons with [], i have found that det([]) is changed: * 5.5: det([]) => 1 * 6.0: det([]) => 0 I don't know if this modification is intentional. I am wondering about the added value of this change: * If we consider the property for square matrices A & B: det(A*B) = det(A)*det(B) (1) setting det([])=0 better complies with it. Indeed, since []*B => [], we have now det([]*B) = det([])*det(B) = 0*k = 0 = det([]) : OK * In another hand, we should also have : det(1/A) = 1/det(A) (2) Since inv([]) => [], setting det([]) => 1 complied with (2), while det([]) => 0 no longer does it. Settingdet([]) => [] would comply with both (1) and (2). Let's note that Octave returns 1. So, shall we restore det([]) ==1, or keep 0, or set it to [] ? What's the improvement in changing det([]) to 0 ? Regards Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Mon May 21 15:46:21 2018 From: sgougeon at free.fr (Samuel Gougeon) Date: Mon, 21 May 2018 15:46:21 +0200 Subject: [Scilab-users] Is cond([]) 0 or 1 ? (bug 15579) Message-ID: Hello, Another case with []: The bug 15579 reports that *cond([])* returns *1*, while *cond([],2)* -- that computes the same 2-norm conditional number for any other matrix than [] -- returns *0*. Actually, *cond([], p)* returns 0 for any accepted p value. At least since Scilab 4, and likely since the beginning of Scilab, *cond([])* is set to 1 as a specific case. I am wondering why. In my opinion, the mismatch between *cond([])* and the equivalent *cond([],2)* must be fixed. There are at least two way to do it : * either keep *cond([])* to *1* and set all *cond([], p)* to 1 instead of 0 * or set *cond([])* to *0*. I don't see any clear reason enforcing a choice rather than the other. Do you? Let's note that * Octave returns 0 in both cond([]) and cond([],p) cases * Julia, Python, and R (with kappa()) yield an error Regards Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From jrafaelbguerra at hotmail.com Mon May 21 20:25:20 2018 From: jrafaelbguerra at hotmail.com (Rafael Guerra) Date: Mon, 21 May 2018 18:25:20 +0000 Subject: [Scilab-users] det([]) changed in Scilab 6.0 In-Reply-To: References: Message-ID: Hi Samuel, I am not a mathematician but I suspect that determinant rules you have enunciated do not hold for empty matrices. Fyi, the following Wikipedia?s entry states that det([]) should be 1 (see ?Empty matrices? paragraph): https://en.wikipedia.org/wiki/Matrix_(mathematics)#Empty_matrices Regards, Rafael From: users [mailto:users-bounces at lists.scilab.org] On Behalf Of Samuel Gougeon Sent: Monday, May 21, 2018 2:10 PM To: International users mailing list for Scilab. Subject: [Scilab-users] det([]) changed in Scilab 6.0 Hello, While updating "help empty" after changes in Scilab 6 about inequality comparisons with [], i have found that det([]) is changed: * 5.5: det([]) => 1 * 6.0: det([]) => 0 I don't know if this modification is intentional. I am wondering about the added value of this change: * If we consider the property for square matrices A & B: det(A*B) = det(A)*det(B) (1) setting det([])=0 better complies with it. Indeed, since []*B => [], we have now det([]*B) = det([])*det(B) = 0*k = 0 = det([]) : OK * In another hand, we should also have : det(1/A) = 1/det(A) (2) Since inv([]) => [], setting det([]) => 1 complied with (2), while det([]) => 0 no longer does it. Setting det([]) => [] would comply with both (1) and (2). Let's note that Octave returns 1. So, shall we restore det([]) ==1, or keep 0, or set it to [] ? What's the improvement in changing det([]) to 0 ? Regards Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From jrafaelbguerra at hotmail.com Mon May 21 20:58:51 2018 From: jrafaelbguerra at hotmail.com (Rafael Guerra) Date: Mon, 21 May 2018 18:58:51 +0000 Subject: [Scilab-users] Is cond([]) 0 or 1 ? (bug 15579) In-Reply-To: References: Message-ID: Hi Samuel, Please read the following article on this interesting topic of the algebra of empty matrices: https://pdfs.semanticscholar.org/0f3b/c36f19d5c6a761c19fbc3c4ebde2f31b0a10.pdf It states that the condition number of the empty matrix should be 0. Regards, Rafael From: users [mailto:users-bounces at lists.scilab.org] On Behalf Of Samuel Gougeon Sent: Monday, May 21, 2018 3:46 PM To: International users mailing list for Scilab. Subject: [Scilab-users] Is cond([]) 0 or 1 ? (bug 15579) Hello, Another case with []: The bug 15579 reports that cond([]) returns 1, while cond([],2) -- that computes the same 2-norm conditional number for any other matrix than [] -- returns 0. Actually, cond([], p) returns 0 for any accepted p value. At least since Scilab 4, and likely since the beginning of Scilab, cond([]) is set to 1 as a specific case. I am wondering why. In my opinion, the mismatch between cond([]) and the equivalent cond([],2) must be fixed. There are at least two way to do it : * either keep cond([]) to 1 and set all cond([], p) to 1 instead of 0 * or set cond([]) to 0. I don't see any clear reason enforcing a choice rather than the other. Do you? Let's note that * Octave returns 0 in both cond([]) and cond([],p) cases * Julia, Python, and R (with kappa()) yield an error Regards Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgougeon at free.fr Mon May 21 21:25:50 2018 From: sgougeon at free.fr (Samuel Gougeon) Date: Mon, 21 May 2018 21:25:50 +0200 Subject: [Scilab-users] det([]) changed in Scilab 6.0 In-Reply-To: References: Message-ID: Le 21/05/2018 ? 20:25, Rafael Guerra a ?crit : > > Hi Samuel, > > I am not a mathematician but I suspect that determinant rules you have > enunciated do not hold for empty matrices. > > Fyi, the following Wikipedia?s entry states that det([]) should be 1 > (see ?Empty matrices? paragraph): > > https://en.wikipedia.org/wiki/Matrix_(mathematics)#Empty_matrices > > Thanks Rafael! This bug is then reported as the bug 15580 . Regards Samuel -------------- next part -------------- An HTML attachment was scrubbed... URL: From j_holland at msn.com Tue May 22 12:28:40 2018 From: j_holland at msn.com (James Holland) Date: Tue, 22 May 2018 03:28:40 -0700 (MST) Subject: [Scilab-users] Plot2d and legends Message-ID: <1526984920350-0.post@n3.nabble.com> I am plotting three columns of data using plot2d and I'm adding a legend box using legends. I have declared the line colours for each plot to make the graph easier to view. The problem that I have is that the legends box shows all three of the lines in the same colour (blue). Is this an issue with the way my code is written? TIA James // plot data // the third column: -->m(:,3) x1 = M1(:,1); // frequency y1 = M1(:,2); // M1 Average y2 = M2(:,2); // M2 Average x2 = M3(:,1); // Limits frequency y3 = M3(:,2); // Limits - average plot2d(x1, y1, style= color('orange'), logflag = "ln"); plot2d(x1, y2, style= color('blue'), logflag = "ln"); plot2d(x2, y3, style= color('red'), logflag = "ln"); f = gca(); // get the current axes bg_color = color('lightgray'); f.background= bg_color; //RGB xtitle("EN55022 Conducted Emissions", "Frequency (MHz)", "dBuV"); legends(['uA7805';'7805SR'; 'EN55022B'],[2,2,2],opt="ur"); xgrid; -- Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html From stephane.mottelet at utc.fr Tue May 22 12:44:01 2018 From: stephane.mottelet at utc.fr (=?UTF-8?Q?St=c3=a9phane_Mottelet?=) Date: Tue, 22 May 2018 12:44:01 +0200 Subject: [Scilab-users] Plot2d and legends In-Reply-To: <1526984920350-0.post@n3.nabble.com> References: <1526984920350-0.post@n3.nabble.com> Message-ID: Hello, Le 22/05/2018 ? 12:28, James Holland a ?crit?: > I am plotting three columns of data using plot2d and I'm adding a legend box > using legends. I have declared the line colours for each plot to make the > graph easier to view. The problem that I have is that the legends box shows > all three of the lines in the same colour (blue). Is this an issue with the > way my code is written? > TIA James > > > // plot data > > // the third column: -->m(:,3) > x1 = M1(:,1); // frequency > y1 = M1(:,2); // M1 Average > y2 = M2(:,2); // M2 Average > x2 = M3(:,1); // Limits frequency > y3 = M3(:,2); // Limits - average > > > plot2d(x1, y1, style= color('orange'), logflag = "ln"); > plot2d(x1, y2, style= color('blue'), logflag = "ln"); > plot2d(x2, y3, style= color('red'), logflag = "ln"); > f = gca(); // get the current axes > bg_color = color('lightgray'); > f.background= bg_color; //RGB > xtitle("EN55022 Conducted Emissions", "Frequency (MHz)", "dBuV"); > legends(['uA7805';'7805SR'; 'EN55022B'],[2,2,2],opt="ur"); here [2 2 2] overwrites the colors you specified in the plot2d calls. I would suggest: legend('uA7805','7805SR','EN55022B','in_upper_right') S. > xgrid; > > > > > -- > Sent from: https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html > _______________________________________________ > users mailing list > users at lists.scilab.org > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users -- St?phane Mottelet Ing?nieur de recherche EA 4297 Transformations Int?gr?es de la Mati?re Renouvelable D?partement G?nie des Proc?d?s Industriels Sorbonne Universit?s - Universit? de Technologie de Compi?gne CS 60319, 60203 Compi?gne cedex Tel : +33(0)344234688 http://www.utc.fr/~mottelet From j_holland at msn.com Thu May 24 15:40:43 2018 From: j_holland at msn.com (James Holland) Date: Thu, 24 May 2018 06:40:43 -0700 (MST) Subject: [Scilab-users] Sockets in scilab 6.0 Message-ID: <1527169243922-0.post@n3.nabble.com> I want to communicate with an oscilloscope through an Ethernet connection. I have downloaded the files linked from the Atoms page. If I try to run the loader then I get the message 'lib: Old binary lib detected. Please recompile it for Scilab 6.' I don't see any files that aren't Scilab so I ran 'builder.sce'. I get the following message: '--> exec('C:\Users\James.Holland\Documents\Scilab\socket src\builder.sce',-1) Building macros... -- Creation of [socket_toolboxlib] (Macros) -- Building help... Building the master document: C:\Users\James.Holland\Documents\Scilab\socket src\help\en_US Building the manual file [javaHelp] in C:\Users\James.Holland\Documents\Scilab\socket src\help\en_US. Building the master document: C:\Users\James.Holland\Documents\Scilab\socket src\help\fr_FR Building the manual file [javaHelp] in C:\Users\James.Holland\Documents\Scilab\socket src\help\fr_FR. WARNING: tbx_build_loader: tbx_build_loader(name, path) is obsolete. Please use tbx_build_loader(path) instead. Generating loader.sce... Generating unloader.sce... WARNING: tbx_build_cleaner: tbx_build_cleaner(name, path) is obsolete. Please use tbx_build_cleaner(path) instead. Generating cleaner.sce... ' After that I ran the loader which returned: --> exec('C:\Users\James.Holland\Documents\Scilab\socket src\loader.sce',-1) Start Socket Toolbox Load macros Load help Load demos I then get the following error: --> exec('C:\Users\James.Holland\Documents\Scilab\socket src\demos\ex_1.sce',-1) [] Undefined variable: mat Undefined variable: mat Undefined variable: mat Undefined variable: mat Undefined variable: mat Undefined variable: mat Undefined variable: mat Undefined variable: mat Undefined variable: mat Undefined variable: mat Undefined variable: mat Undefined variable: mat Undefined variable: mat Undefined variable: mat mat=["Google