Re: [Scilab-users] Graphics: Current figure and current entity

[Clément David]

Hello Denis,

I don’t think Scilab provide a function to retrieve the parent figure of an 
entity ; could you open a bug with this wish ?

Note: internally, there is already a non-iterative O(1) way to retrieve it.

Regards,
Clément

From: users  On Behalf Of CRETE Denis
Sent: Tuesday, June 7, 2022 11:39 AM
To: Users mailing list for Scilab 
Subject: [Scilab-users] Graphics: Current figure and current entity

Hello,

I have several graphic windows and in some of them, there are several “Axes” 
(and several curves for each “Axes”).
I can’t find in “Scilab Help” if the “current axes” is always in the hierarchy 
of the “current entity”, and similarly if the “current figure” is always in the 
hierarchy of the “current axes”.
If this was true, I suggest to mention it in the “Graphics Entities” section.
If not, is there a simple way to obtain the handle of the figure where the 
“current entity” is ?
I tried the following, which seems to work :
G_f=gce().parent;
while get(G_f,”type”)~=”Figure”,
  G_f= G_f.parent;
end;

Did I reinvent the wheel ?-)

Thank you in advance
Denis
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Scilab crashes on x_choose_modeless

[Clément David]

Hello,

Yep I was able to reproduce, it looks that's a known bug 
https://bugzilla.scilab.org/show_bug.cgi?id=14905

Thanks,
Clément

> -Original Message-
> From: users  On Behalf Of Stefan Du Rietz
> Sent: Monday, October 25, 2021 9:34 AM
> To: users@lists.scilab.org
> Subject: Re: [Scilab-users] Scilab crashes on x_choose_modeless
> 
> Hello, I get the same result (nothing but the title: "Scilab Choose
> Message") with Scilab 6.1.1 under Linux. And Scilab hangs ...
> 
> Stefan
> 
> 
> On 2021-10-25 09:06, Stéphane Mottelet wrote:
> > Hi,
> >
> > Let us see if someone reacts to/cares about  this message...
> >
> > S.
> >
> > Le 24/10/2021 à 22:58, P M a écrit :
> >> Hi,
> >>
> >> What is the expected behaviour of x_choose_modeless ?
> >>
> >> Executing the help example
> >>
> >> grafik.png
> >>
> >>
> >> I get the window below and Scilab does not react to anything.
> >>
> >> Experienced under Scilab 6.1.0 (64-bit) on a Win10 PC.
> >>
> >> grafik.png
> >>
> >> Philipp
> >>
> >> ___
> >> users mailing list
> >> users@lists.scilab.org
> >> http://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@lists.scilab.org
> > http://lists.scilab.org/mailman/listinfo/users
> >
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] 6.1.1 startup error

[Clément David]

Hi Stéphane, hi Samuel, hi all,

The idea behind SCIHOME is to have a version specific directory to avoid any 
issues when upgrading from Scilab versions to Scilab versions ; IMHO 
implementing an upgrade for files stored into this directory is for me a 
non-sense ; the upgrade could be done manually (as Samuel described) for the 
few users that copy the files between SCIHOMEs.

Clément

From: users  On Behalf Of Stéphane Mottelet
Sent: Wednesday, September 22, 2021 5:19 PM
To: users@lists.scilab.org
Subject: Re: [Scilab-users] 6.1.1 startup error


Hi,

The version of Scilab which generated the configuration.xml should be contained 
in some attribute of the top level element, i.e.



This would allow to trigger a proper upgrade of the file when the Scilab 
version differs or a regeneration if the file cannot be upgraded.

S.
Le 22/09/2021 à 17:10, Samuel Gougeon a écrit :
Hello Stefan,

This kind of error might arise when the content of the SCIHOME directory of a 
previous scilab version is copied into the SCIHOME of the current 6.1.1 
version, for instance to avoid respecifying all users preferences.
Unfortunately, when the template of some configuration file is changed from one 
version to the next one, the file must be regenerated.

The issue should be fixed either by deleting the SCIHOME/configuration.xml 
file, and regenerating it automatically from scratch (quit Scilab and rerun it),
or by editing it and changing or adding the line just before the  
one, for instance with




Regards
Samuel

Le 22/09/2021 à 12:08, Stefan Du Rietz a écrit :
Hello,
when starting Scilab 6.1.1 with

  $ /usr/local/scilab/scilab-6.1.1/bin/scilab

I get the message:

Startup execution:
  loading initial environment
at line81 of function xmlGetValues   ( 
/usr/local/scilab/scilab-6.1.1/share/scilab/modules/xml/macros/xmlGetValues.sci 
line 94 )
at line22 of function help   ( 
/usr/local/scilab/scilab-6.1.1/share/scilab/modules/helptools/macros/help.sci 
line 34 )
at line14 of function helpbrowser_update ( 
/usr/local/scilab/scilab-6.1.1/share/scilab/modules/helptools/macros/helpbrowser_update.sci
 line 25 )

xmlGetValues: Invalid attribute name: lang.

in Ubuntu Linux after a successful (apart from this) installation from
scilab-6.1.1.bin.linux-x86_64.tar.gz

What can I do?

Regards
Stefan




___

users mailing list

users@lists.scilab.org

http://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@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Is http://mailinglists.scilab.org over?

[Clément David]

Hello Stephane, hello all,

Thank you for finding this ML archive ; it looks to be a reliable source to 
find old mails. 

Clément

> -Original Message-
> From: users  On Behalf Of Stéphane
> Mottelet
> Sent: Tuesday, September 7, 2021 3:13 PM
> To: users@lists.scilab.org
> Subject: Re: [Scilab-users] Is http://mailinglists.scilab.org over?
> 
> Hi,
> 
> is https://www.mail-archive.com/users@lists.scilab.org/ the new place to
> look for the list archives ?
> 
> S.
> 
> Le 21/07/2021 à 15:37, Clément David a écrit :
> > Hello Samuel, hello all,
> >
> > Indeed we noticed that but where in a hurry delivering the 6.1.1 release.
> The Nabble maintainers stopped the development [1] and started some
> action to stop the service [2]. IMHO we need to switch to another service for
> archiving and searching the Scilab mailing lists. We investigated on Discourse
> a while ago but the operating cost is too costly for us ; there is also an 
> option
> to have a full switch to Mailman v3 hosted services.
> >
> > Currently there is no free equivalent to Nabble so the mailinglists archive
> might not be available for a time. Hopefully we can ask Nabble maintainers to
> restore the access but it really is a temporary solution.
> >
> > [1]: https://support.nabble.com/The-Future-of-Nabble-tt7605923.html
> > [2]: https://support.nabble.com/Downsizing-Nabble-tt7609715.html
> >
> > Regards,
> >
> > Clément
> >
> >
> >
> >> -Original Message-
> >> From: users  On Behalf Of Samuel
> >> Gougeon
> >> Sent: Wednesday, July 21, 2021 3:03 PM
> >> To: International users mailing list for Scilab.
> >> 
> >> Subject: [Scilab-users] Is http://mailinglists.scilab.org over?
> >>
> >> Le 19/07/2021 à 09:56, Dang Ngoc Chan, Christophe a écrit :
> >>> Hello Samuel,
> >>>
> >>>> De : users  De la part de Samuel
> >>>> Gougeon Envoyé : jeudi 8 juillet 2021 08:01
> >>>>
> >>>> That's strange : do you confirm that this thread and following ones
> >>>> (*) look no longer archived @
> >>>> http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-
> >>>> f2
> >>>> 602246.html
> >>> I confirm I don't see the topic "Native arm64 build for Mac M1" in
> >>> the list
> >> either.
> >>
> >>
> >> Thanks Christophe.
> >> The same applies to the users-fr@ list, on which last messages posted
> >> on 8th and 9th of July about "newaxes et subplot" were not archived.
> >>
> >> Finally, since yesterday, the whole http://mailinglists.scilab.org
> >> website is unreachable.
> >> We can't ignore the coincidence with the release of 6.1.1 the same day.
> >>
> >> Scilab has no longer official truly public mailing lists, and former
> >> archives as a knowledge database for 25 years and all corresponding
> >> existing cross- references look over.
> >>
> >> Samuel
> >>
> >> ___
> >> users mailing list
> >> users@lists.scilab.org
> >> http://lists.scilab.org/mailman/listinfo/users
> > ___
> > users mailing list
> > users@lists.scilab.org
> > http://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@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Adding library in Win10

[Clément David]

Hello,

SCI and SCIHOME values will depend on the installation you made. To view the 
values, just display them on the Scilab console as they are regular Scilab 
variables.

Regards,

Clément

From: users  On Behalf Of Izabela Wójcik-Grząba
Sent: Friday, September 3, 2021 3:38 PM
To: users@lists.scilab.org
Subject: [Scilab-users] Adding library in Win10


Hello,

Till now I have been using Scilab on Win7 and had my library added with the use 
of this procedure:

1. genlib ("Moja_biblioteka","C:/Program Files/mojabiblioteka_scilab")

2. created a scilab.ini file in SCIHOME with a line: Moja_biblioteka = 
lib("C:/Program Files/mojabiblioteka_scilab")

Now I have Win10 and don't know how to do the same on this OS. Especially I 
can't find SCIHOME.

I would be grateful for any help.

Regards,

Iza
--
Izabela Wójcik-Grząba
Zespół Konstrukcji Metalowych
ZKBiM IIB WIL Politechnika Warszawska
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] fullpath * crashes 6.1.1

[Clément David]

Hello all,

Thanks for the early report, could you please report the issue on 
bugzilla.scilab.org to allow a quick fix with a non-regression test ?

Regards,
Clément

From: users  On Behalf Of Stéphane Mottelet
Sent: Friday, July 23, 2021 9:46 PM
To: users@lists.scilab.org
Subject: Re: [Scilab-users] fullpath * crashes 6.1.1


Hi,

It seems specific to Windows (the following test is done on macOS) :

--> fullpath("SCI\modules\core\macros\*.sci")
 ans  =

  
"/Applications/scilab-6.1.1.app/Contents/share/scilab/modules/core/macros/*.sci"

Really weird, since now we have exactly the same code for Windows and others.

S.
Le 23/07/2021 à 18:54, Samuel Gougeon a écrit :
Hello,

Le 10/07/2021 à 23:37, Samuel Gougeon a écrit :
Le 10/07/2021 à 16:11, Samuel Gougeon a écrit :

Hello Federico,

I confirm this issue. It appeared in Scilab 6.1.0 and  occurs only when pwd() 
and the filename are on the same disk.
It comes from a change of behavior of mopen(), and so may occurs for many other 
functions using mopen().

Regards
Samuel


fullpath() -- that was changed in january 2020 -- is the final guilty:

--> pwd
 ans  =
  "D:\Softs"

--> fullpath("D:\test.wav")
 ans  =
  "D:\Softs\test.wav"



unlike Scilab 6.1.0, Scilab 6.1.1 on Windows crashes with

fullpath("SCI\modules\core\macros\*.sci")

The crash occurs only a) when the path exists, AND b) * is used in the filename.
It was still not the case with the dev branch of 2021-07-07, that is the last 
build available for windows, 7 days before fullpath was fixed for the hereabove 
issue.

This noticeably kills uman(), at least its refresh "r" option that is also run 
automatically at initialization and every change of the local ATOMS list.

And i guess many other codes.

Samuel





___

users mailing list

users@lists.scilab.org

http://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@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Two issues in 6.1.1

[Clément David]

Dear Federico,

Thanks for the reports, could you post bugs to https://bugzilla.scilab.org this 
will let us track the issue and write them into the CHANGES.md document.

Regards,
Clément

From: users  On Behalf Of Federico Miyara
Sent: Thursday, July 22, 2021 4:43 PM
To: Users mailing list for Scilab 
Subject: [Scilab-users] Two issues in 6.1.1


Dear all,

I've found two issues in Scilab 6.1.1. The first is that sometimes (I can't 
replicate this all the times) the DOS window that opens when running scilex 
doesn't close properly after launching so we have two items on the task bar the 
bottom of the screen. The only way to close it is to close the program and hope 
that next time it will close.

The second happens when in a comment the string "todo" appears followed by a 
space or a colon: the color turns from green to orange:

// el método manual

// la metodología manual

// todo:

// TODO:

// Todo:

// ToDo:

// TO do:
According to the color settings this is an expected result when at the 
beginning of a line (I guess it means "things left to do"), but it is not 
adequate when "todo" is part of another word (like in the Spanish word "método" 
in the first line). I can confirm this happens only in Scilab 6.1.1. In 6.1.0 
it didn't happen, actually in no case the orange highlighting were honoured.

Regards.

Federico Miyara

[https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif]
Libre de virus. 
www.avast.com

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Is http://mailinglists.scilab.org over?

[Clément David]

Hello Samuel, hello all,

Indeed we noticed that but where in a hurry delivering the 6.1.1 release. The 
Nabble maintainers stopped the development [1] and started some action to stop 
the service [2]. IMHO we need to switch to another service for archiving and 
searching the Scilab mailing lists. We investigated on Discourse a while ago 
but the operating cost is too costly for us ; there is also an option to have a 
full switch to Mailman v3 hosted services.

Currently there is no free equivalent to Nabble so the mailinglists archive 
might not be available for a time. Hopefully we can ask Nabble maintainers to 
restore the access but it really is a temporary solution.

[1]: https://support.nabble.com/The-Future-of-Nabble-tt7605923.html
[2]: https://support.nabble.com/Downsizing-Nabble-tt7609715.html

Regards,

Clément



> -Original Message-
> From: users  On Behalf Of Samuel Gougeon
> Sent: Wednesday, July 21, 2021 3:03 PM
> To: International users mailing list for Scilab. 
> Subject: [Scilab-users] Is http://mailinglists.scilab.org over?
> 
> Le 19/07/2021 à 09:56, Dang Ngoc Chan, Christophe a écrit :
> > Hello Samuel,
> >
> >> De : users  De la part de Samuel
> >> Gougeon Envoyé : jeudi 8 juillet 2021 08:01
> >>
> >> That's strange : do you confirm that this thread and following ones
> >> (*) look no longer archived @
> >> http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2
> >> 602246.html
> > I confirm I don't see the topic "Native arm64 build for Mac M1" in the list
> either.
> 
> 
> Thanks Christophe.
> The same applies to the users-fr@ list, on which last messages posted on 8th
> and 9th of July about "newaxes et subplot" were not archived.
> 
> Finally, since yesterday, the whole http://mailinglists.scilab.org website is
> unreachable.
> We can't ignore the coincidence with the release of 6.1.1 the same day.
> 
> Scilab has no longer official truly public mailing lists, and former archives 
> as a
> knowledge database for 25 years and all corresponding existing cross-
> references look over.
> 
> Samuel
> 
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

[Scilab-users] Scilab 6.1.1 release

[Clément David]

Dear Scilab users,

We are pleased to announce the release of Scilab 6.1.1 as a joint effort 
between Scilab contributors and the Scilab team at ESI Group. 

Scilab 6.1.1 is the first revision of the 6.1 development branch and is 
compatible with the 6.1.0 release. It fixes 156 bugs and implements missing 
features from the 6.1.0 version especially:

* Improve readability on plot's title and displayed values
* Fix crashes and slow behaviors on functions
* Add missing arguments and behaviors to existing functions
* Reword and add examples on many help pages

For the complete list of changes and bugs fixed, please take a look at the 
CHANGES file https://help.scilab.org/CHANGES

Download this brand new version at https://www.scilab.org/download/6.1.1

--
Clément DAVID on behalf of the Scilab team.
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

[Scilab-users] Scilab 6.1.1 release

[Clément David]

Dear Scilab users,

We are pleased to announce the release of Scilab 6.1.1 as a joint effort 
between Scilab contributors and the Scilab team at ESI Group. 

Scilab 6.1.1 is the first revision of the 6.1 development branch and is 
compatible with the 6.1.0 release. It fixes 156 bugs and implements missing 
features from the 6.1.0 version especially:

* Improve readability on plot's title and displayed values
* Fix crashes and slow behaviors on functions
* Add missing arguments and behaviors to existing functions
* Reword and add examples on many help pages

For the complete list of changes and bugs fixed, please take a look at the 
CHANGES file https://help.scilab.org/CHANGES

Download this brand new version at https://www.scilab.org/download/6.1.1

--
Clément DAVID on behalf of the Scilab team.
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] fmincon toolbox update

[Clément David]

Hi,

Nice, thanks.

Clément

From: users  On Behalf Of Stéphane Mottelet
Sent: Tuesday, June 8, 2021 8:49 AM
To: users@lists.scilab.org
Subject: Re: [Scilab-users] fmincon toolbox update


Hi,

These problems are now  fixed in version 1.3.1. For the Windows version, if the 
update of libifcoremd.dll is necessary, the writeability of SCI/bin is tested 
in order to run the update script with admin rights only if needed.

S.
Le 07/06/2021 à 10:01, Clément David a écrit :
Hello all,

I try to install to check fmincon to check on my machine and give you a fresh 
eye on the basic install/usage. I have a few remarks:


1.  My Scilab and all atoms packages are installed in user directories but 
the library check at startup on sci_ipopt ask for administrator access to 
update. That’s a pity to require that.

2.  The message “This program contains Ipopt, a library for large-scale 
nonlinear optimization.” looks strange to me, this function is named ipopt and 
I think the references are written in the documentation and on the DESCRIPTION 
file. There is no need to display that at runtime.

Otherwise basic examples are running even if it change the toolbox loading 
order (sci_ipopt after fmincon, scicolpack after sci_ipopt, etc…).

Clément

From: users 
<mailto:users-boun...@lists.scilab.org> On 
Behalf Of CHEZE David 227480
Sent: Monday, June 7, 2021 9:20 AM
To: Users mailing list for Scilab 
<mailto:users@lists.scilab.org>
Subject: Re: [Scilab-users] fmincon toolbox update

Hi all,

I installed both SciPOpt and fmincon from ATOMS on Scilab 6.1.0 WIN10-64bits, a 
few weeks ago and the demos are running properly. I had some minor dependencies 
issues while installing, I don’t remember exactly , probably the SciIPopt 
version was not aligned with the one required by fmincon.
My 2 cents

David



De : users 
<mailto:users-boun...@lists.scilab.org> De la 
part de Stéphane Mottelet
Envoyé : samedi 5 juin 2021 22:17
À : Users mailing list for Scilab 
<mailto:users@lists.scilab.org>
Objet : Re: [Scilab-users] fmincon toolbox update

May I ask if there are there some Windows users who read this post and who 
successfully installed sci_ipopt or fmincon ?

S.

Le 5 juin 2021 à 15:21, Éric Dubois 
mailto:grocer.tool...@gmail.com>> a écrit :

Thanks Stéphane for your quick answer

I have tried installing fmincon first, then scicolpack (it works), then 
sci_ipopt  and it does not work: only file sci_ipopt_1.3.bin.x64.Windows.zipis 
downloaded. So it seems:
- first that dependencies are not deal with for the fmincon distribution that 
Atoms uses;
- second, that there is some problem using Atoms for loading  sci_ipopt

Maybe I should not use Atoms, but when it works it is the most convenient way 
to download a module.

Éric

[Image removed by 
sender.]<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
Garanti sans virus. 
www.avast.com<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>

Le sam. 5 juin 2021 à 14:06, Stéphane Mottelet 
mailto:stephane.motte...@utc.fr>> a écrit :
Hi Eric,

Could you be more precise ? I have I installed fmincon on at least 10 different 
machines for testing purposes  (mostly under Windows 10) and did not encounter 
any problem. Atoms is, I must say, a very unstable (not to say crappy) piece of 
software and in particular very hard to use smoothly when your are developing 
some modules and play e.g. with offline mode.

What I would do first is to uninstall every module then install fmincon. If 
problem is still here please help me by debugging a bit...

S.

Le 5 juin 2021 à 11:29, Éric Dubois 
mailto:grocer.tool...@gmail.com>> a écrit :

Hello Stéphane

This seems very interesting, but download through Atoms does not work (at least 
for me: I use Scilab 6.1.0 under Windows 10): dependencies (Sci-colpac, 
Sci-IPOt, for those I have noticed) are not dealt with. Moreover, trying to 
install Sci-IPOt with Atoms fails. By the way it makes also make fail lthe 
oading of  any module that could have been installed with Atoms, which reveals 
an undesirable feature of Atoms: failure to load a module should not prevent 
the loading of other ones.

Best regards,

Éric

[Image removed by 
sender.]<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
Garanti sans virus. 
www.avast.com<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>

Le mar. 1 juin 2021 à 12:21, Stéphane Mottelet 
mailto:stephane.motte...@utc.fr>> a écrit :
Hi,

Le 01/06/2021 à 09:53, CHEZE David 227480 a écrit :
> Dear Stephane,
>
> Thank you for offering these enhanced capabilities in Scilab, fmincon and 
> SciIPOpt. I'm about giving a try in comparison with leastsq(), on dynamic 
> model parameter (~5-10) calibration purpose, based on measurement deviation, 
> as

Re: [Scilab-users] fmincon toolbox update

[Clément David]

Hello all,

I try to install to check fmincon to check on my machine and give you a fresh 
eye on the basic install/usage. I have a few remarks:


  1.  My Scilab and all atoms packages are installed in user directories but 
the library check at startup on sci_ipopt ask for administrator access to 
update. That’s a pity to require that.
  2.  The message “This program contains Ipopt, a library for large-scale 
nonlinear optimization.” looks strange to me, this function is named ipopt and 
I think the references are written in the documentation and on the DESCRIPTION 
file. There is no need to display that at runtime.

Otherwise basic examples are running even if it change the toolbox loading 
order (sci_ipopt after fmincon, scicolpack after sci_ipopt, etc…).

Clément

From: users  On Behalf Of CHEZE David 227480
Sent: Monday, June 7, 2021 9:20 AM
To: Users mailing list for Scilab 
Subject: Re: [Scilab-users] fmincon toolbox update

Hi all,

I installed both SciPOpt and fmincon from ATOMS on Scilab 6.1.0 WIN10-64bits, a 
few weeks ago and the demos are running properly. I had some minor dependencies 
issues while installing, I don’t remember exactly , probably the SciIPopt 
version was not aligned with the one required by fmincon.
My 2 cents

David



De : users  De la part de Stéphane Mottelet
Envoyé : samedi 5 juin 2021 22:17
À : Users mailing list for Scilab 
Objet : Re: [Scilab-users] fmincon toolbox update

May I ask if there are there some Windows users who read this post and who 
successfully installed sci_ipopt or fmincon ?

S.

Le 5 juin 2021 à 15:21, Éric Dubois 
mailto:grocer.tool...@gmail.com>> a écrit :

Thanks Stéphane for your quick answer

I have tried installing fmincon first, then scicolpack (it works), then 
sci_ipopt  and it does not work: only file sci_ipopt_1.3.bin.x64.Windows.zipis 
downloaded. So it seems:
- first that dependencies are not deal with for the fmincon distribution that 
Atoms uses;
- second, that there is some problem using Atoms for loading  sci_ipopt

Maybe I should not use Atoms, but when it works it is the most convenient way 
to download a module.

Éric

[Image removed by 
sender.]
Garanti sans virus. 
www.avast.com

Le sam. 5 juin 2021 à 14:06, Stéphane Mottelet 
mailto:stephane.motte...@utc.fr>> a écrit :
Hi Eric,

Could you be more precise ? I have I installed fmincon on at least 10 different 
machines for testing purposes  (mostly under Windows 10) and did not encounter 
any problem. Atoms is, I must say, a very unstable (not to say crappy) piece of 
software and in particular very hard to use smoothly when your are developing 
some modules and play e.g. with offline mode.

What I would do first is to uninstall every module then install fmincon. If 
problem is still here please help me by debugging a bit...

S.

Le 5 juin 2021 à 11:29, Éric Dubois 
mailto:grocer.tool...@gmail.com>> a écrit :

Hello Stéphane

This seems very interesting, but download through Atoms does not work (at least 
for me: I use Scilab 6.1.0 under Windows 10): dependencies (Sci-colpac, 
Sci-IPOt, for those I have noticed) are not dealt with. Moreover, trying to 
install Sci-IPOt with Atoms fails. By the way it makes also make fail lthe 
oading of  any module that could have been installed with Atoms, which reveals 
an undesirable feature of Atoms: failure to load a module should not prevent 
the loading of other ones.

Best regards,

Éric

[Image removed by 
sender.]
Garanti sans virus. 
www.avast.com

Le mar. 1 juin 2021 à 12:21, Stéphane Mottelet 
mailto:stephane.motte...@utc.fr>> a écrit :
Hi,

Le 01/06/2021 à 09:53, CHEZE David 227480 a écrit :
> Dear Stephane,
>
> Thank you for offering these enhanced capabilities in Scilab, fmincon and 
> SciIPOpt. I'm about giving a try in comparison with leastsq(), on dynamic 
> model parameter (~5-10) calibration purpose, based on measurement deviation, 
> as time series (250 to >1000 samples). In general for fmincon and SciIPOpt, 
> may I provide the objective function with inputs argument through the list() 
> syntax like objf=list(myofunction,x,in1,in2,..) ?

Yes, you have such an example in the fitting demo ;

https://gitlab.com/esi-group/scilab/forge/fmincont/-/blob/master/demos/fmincon_fit.sce

S.

>
> Thank you for your advice,
>
> David
>
>
> -Message d'origine-
> De : users 
> mailto:users-boun...@lists.scilab.org>> De la 
> part de Stéphane Mottelet
> Envoyé : lundi 19 avril 2021 10:43
> À : Users mailing list for Scilab 
> mailto:users@lists.scilab.org>>
> Objet : [Scilab-users] fmincon toolbox update
>
> Hi all,
>
> I would like to inform you 

Re: [Scilab-users] Scilab compilation from scratch (was Re: spec can crash scilab)

[Clément David]

> -Original Message-
> From: users  On Behalf Of Antoine
> Monmayrant
> Sent: Monday, May 10, 2021 1:02 PM
> To: users@lists.scilab.org
> Subject: Re: [Scilab-users] Scilab compilation from scratch (was Re: spec can
> crash scilab)
> 
> 
> Le 10/05/2021 à 09:12, Clément David a écrit :
> > To fix, remove libstdc++.so and libgfortran.so on the Prerequirements;
> Er, OK, I'm glad to do that, but I don't see what you are talking about.
> Where are those 'Prerequirements' defined?
> 
> (I'm really not versed into compiling, I just barely know the basics...)

What we called Prerequirements (or thirdparties) are binaries used for the 
Scilab compilation but coming from external sources (for example, libxml2 or 
curl). At configure time, a detection is performed to use them rather than 
using the system's ones. If you used the cheatsheet, they are delivered with 
the svn command and should be located on the  "usr" directory.

Clément
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Scilab compilation from scratch (was Re: spec can crash scilab)

[Clément David]

This one is less obvious and will require more explanation.
In Scilab 6, we use modern C++ (C++11 and later) on our codebase which requires 
to have modern compilers and runtime libraries (libstdc++ libgfortran). For the 
compilation chain, we build gcc 8 on an old centos 6 distribution so runtimes 
are available. For people using Scilab, to avoid clashing between the system 
libstdc++/libgfortran and Scilab libstdc++/libgfortran, the Scilab runtime 
libraries are renamed to libscistdc++/libscigfortran.  

For building toolboxes against the Scilab runtime libraries and their 
libstdc++.so and libgfortran.so development libraries are provided on the 
Prerequirements. This is the source of your issue as the Prerequirements 
LDFLAGS are detected and used at configure-time. To fix, remove libstdc++.so 
and libgfortran.so on the Prerequirements; this will make your Scilab-build 
tied to your system; this is good for development purposes.

Regards,

Clément

> -Original Message-
> From: users  On Behalf Of Antoine
> Monmayrant
> Sent: Sunday, May 9, 2021 4:39 PM
> To: users@lists.scilab.org
> Subject: Re: [Scilab-users] Scilab compilation from scratch (was Re: spec can
> crash scilab)
> 
> Hello all,
> 
> Just a quick update:
> (1) I installed & configured as default : openjdk-8 gcc-8 g++8
> (2) I had to rm everything and restart from scratch: somehow, my first try at
> compiling with openjdk-11 had left some *.class files behind (with the wrong
> version) that make clean is not removing
> (3) Now I am stuck at libscigfortran not being found. I'm pretty sure I miss
> some mystery -lrandomlibame flag or someLD_* stuff... :
>      /usr/bin/ld: warning: libscigfortran.so.5, needed by
> /home/amonmayr/softs/scilab-
> recompile/scilab_master/scilab/usr/lib/liblapack.so,
> not found (try using -rpath or -rpath-link)
> 
> If anyone who knows more than me about ld flags wants to chime in, I could
> do with a bit of help...
> 
> Cheers,
> 
> 
> Antoine
> PS: I tried to join config.log but the email got too big for the mailing 
> list...
> 
> On 07/05/2021 18:18, Clément David wrote:
> > Hello Antoine,
> >
> > This issue might comes from a wrong jdk version, you should have
> > openjdk8 installed on your machine and it should be listed at
> > configure time. Could you post the config.log file for further
> > investigation ?
> >
> > Thanks,
> >
> > Clément
> >
> > -Original Message-
> > From: users  On Behalf Of Antoine
> > Monmayrant
> > Sent: Friday, May 7, 2021 5:40 PM
> > To: users@lists.scilab.org
> > Subject: [Scilab-users] Scilab compilation from scratch (was Re: spec
> > can crash scilab)
> >
> > Hello all,
> >
> > In order to try to mitigate bug 15330, I try to compile scilab from
> > source on Linux Ubuntu 18.04 64bits.
> > I follow the explanations from
> > https://wiki.scilab.org/Compilation%20of%20Scilab [Linux x86_64 cheat
> > sheet].
> > Sadly, I don't go really far as the prebuild of java fails:
> >
> >
> >     Makefile:756: recipe for target 'java' failed
> >
> > Am I missing something?
> > Are there other infos somewhere, in particular concerning the
> > dependencies ?
> > Is there a more detailed tutorial for building scilab?
> >
> > Cheers,
> >
> > Antoine
> >
> >
> > ___
> > users mailing list
> > users@lists.scilab.org
> > http://lists.scilab.org/mailman/listinfo/users
> > ___
> > users mailing list
> > users@lists.scilab.org
> > http://lists.scilab.org/mailman/listinfo/users
> >
> 
> 
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Scilab compilation from scratch (was Re: spec can crash scilab)

[Clément David]

Hello Antoine,

This issue might comes from a wrong jdk version, you should have openjdk8 
installed on your machine and it should be listed at configure time. Could you 
post the config.log file for further investigation ?

Thanks,

Clément

-Original Message-
From: users  On Behalf Of Antoine Monmayrant
Sent: Friday, May 7, 2021 5:40 PM
To: users@lists.scilab.org
Subject: [Scilab-users] Scilab compilation from scratch (was Re: spec can crash 
scilab)

Hello all,

In order to try to mitigate bug 15330, I try to compile scilab from source on 
Linux Ubuntu 18.04 64bits.
I follow the explanations from
https://wiki.scilab.org/Compilation%20of%20Scilab [Linux x86_64 cheat sheet].
Sadly, I don't go really far as the prebuild of java fails:


     Makefile:756: recipe for target 'java' failed

Am I missing something?
Are there other infos somewhere, in particular concerning the dependencies ?
Is there a more detailed tutorial for building scilab?

Cheers,

Antoine


___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] How to list the content of the recursion stack?

[Clément David]

Hello Samuel,

If I remember correctly, this message comes without any information as this is 
a regular Scilab error and should be trap through debug(). However on the 
latest Scilab dev build it seems to crash my Scilab. Could you post a bug on 
that please ?

Thanks,

Clément 

-Original Message-
From: users  On Behalf Of Samuel Gougeon
Sent: Tuesday, May 4, 2021 3:01 PM
To: International users mailing list for Scilab. 
Subject: [Scilab-users] How to list the content of the recursion stack?

Dear all,

When we get a Recursion limit reached (1000) message, does anyone know how to 
know more about which recursive calls are filling and overflowing the recursion 
stack?

Noticeably, the message does not tell anything about the last instruction that 
yielded the error.
This makes debugging quite hard.

Using debug() to follow 1000 nested calls is just not possible.
The debug page says "launch execution with stop on error". But then, in debug 
mode,  "e whereami" does not display anything, as in normal mode.

Thanks
Regards
Samuel

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Toolboxes startup

[Clément David]

It is not documented but there is some reference to it on atomsLoad and 
etc/Scilab.start . IMHO we can make it widely available and document it for 
this usage.

Clément

From: users  On Behalf Of Stéphane Mottelet
Sent: Monday, April 26, 2021 11:38 AM
To: users@lists.scilab.org
Subject: Re: [Scilab-users] Toolboxes startup


Is %toolboxes already used ? If so where is it documented ?

S.
Le 26/04/2021 à 10:57, Clément David a écrit :
Hi all,

Thanks for the proposal Stephane, this is a good idea!

As a reminder, currently each toolbox is free to display anything at startup 
and the toolbox skeleton provides a default “Start ” + TOOLBOX_NAME then 
display information that ease development (gateways, help and so on). Migrating 
to another display is only a matter of convention, for example by checking if 
the global %toolboxes variable is available than do not display anything.

Clément

From: users 
<mailto:users-boun...@lists.scilab.org> On 
Behalf Of Stéphane Mottelet
Sent: Monday, April 26, 2021 9:42 AM
To: Users mailing list for Scilab 
<mailto:users@lists.scilab.org>
Subject: [Scilab-users] Toolboxes startup


Hi all,

I just made available for macOS and Linux the toolboxes stixbox depends upon 
for macOS (distfun and linalg) and my remark is that when a lot of modules are 
loaded at startup then the output can become very long and sometimes messy, 
since we don't impose a normalized output:

Scilab branch-6.1 (Apr 19 2021, 23:19:29)

Start Distfun

Start Helptbx

Start Specfun

Start Makematrix

Start Apifun
Load macros
Type "help apifun_overview" for a quick start.

Start Linalg

Start Stixbox

I would rather expect something like:



Scilab branch-6.1 (Apr 19 2021, 23:19:29)

Start modules: Distfun, Helptbx, Specfun, Makematrix, Apifun, Linalg, Stixbox.

-->

The verbosity level of the output (with the above default)  could be defined in 
user preferences, and checked in module startup script in order to output the 
required amount of information.

That's just a propostion to be discussed, of course.

S.

--

Stéphane Mottelet

Ingénieur de recherche

EA 4297 Transformations Intégrées de la Matière Renouvelable

Département Génie des Procédés Industriels

Sorbonne Universités - Université de Technologie de Compiègne

CS 60319, 60203 Compiègne cedex

Tel : +33(0)344234688

http://www.utc.fr/~mottelet<https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/www.utc.fr/~mottelet>



___

users mailing list

users@lists.scilab.org<mailto:users@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@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Toolboxes startup

[Clément David]

Hi all,

Thanks for the proposal Stephane, this is a good idea!

As a reminder, currently each toolbox is free to display anything at startup 
and the toolbox skeleton provides a default “Start ” + TOOLBOX_NAME then 
display information that ease development (gateways, help and so on). Migrating 
to another display is only a matter of convention, for example by checking if 
the global %toolboxes variable is available than do not display anything.

Clément

From: users  On Behalf Of Stéphane Mottelet
Sent: Monday, April 26, 2021 9:42 AM
To: Users mailing list for Scilab 
Subject: [Scilab-users] Toolboxes startup


Hi all,

I just made available for macOS and Linux the toolboxes stixbox depends upon 
for macOS (distfun and linalg) and my remark is that when a lot of modules are 
loaded at startup then the output can become very long and sometimes messy, 
since we don't impose a normalized output:

Scilab branch-6.1 (Apr 19 2021, 23:19:29)

Start Distfun

Start Helptbx

Start Specfun

Start Makematrix

Start Apifun
Load macros
Type "help apifun_overview" for a quick start.

Start Linalg

Start Stixbox

I would rather expect something like:



Scilab branch-6.1 (Apr 19 2021, 23:19:29)

Start modules: Distfun, Helptbx, Specfun, Makematrix, Apifun, Linalg, Stixbox.

-->

The verbosity level of the output (with the above default)  could be defined in 
user preferences, and checked in module startup script in order to output the 
required amount of information.

That's just a propostion to be discussed, of course.

S.

--

Stéphane Mottelet

Ingénieur de recherche

EA 4297 Transformations Intégrées de la Matière Renouvelable

Département Génie des Procédés Industriels

Sorbonne Universités - Université de Technologie de Compiègne

CS 60319, 60203 Compiègne cedex

Tel : +33(0)344234688

http://www.utc.fr/~mottelet
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Precedence rules for concurrent native and external builtin homonymous functions?

[Clément David]

Hi all,

From my usage, the precedence rule is simple and act similarly as function 
re-definition: the last function wins. In practice it depends on the loading 
order, custom code execution order and so on.

Regards,

Clément

From: users  On Behalf Of Stéphane Mottelet
Sent: Friday, April 9, 2021 6:16 PM
To: users@lists.scilab.org
Subject: Re: [Scilab-users] Precedence rules for concurrent native and external 
builtin homonymous functions?


Samuel, I think the problem is about gateways not user macros right ?

What I experienced is that the new gateways have precedence over the previously 
linked gateways with the same name.

Hence, there is no conflict is the API is respected...

S.
Le 09/04/2021 à 17:57, Samuel Gougeon a écrit :

Dear all,

I am wondering about precedence rules when a user's defined builtin (possibly 
from an ATOMS external module) has the same name than a native Scilab builtin 
function.
The case appeared (and maybe still) when using the scicv external module, that 
redefined a write() function that already exists in Scilab.

Does anyone know how such conflicts are managed by Scilab?
Thanks

Samuel



___

users mailing list

users@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@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] xcos_simulate()

[Clément David]

Hi Johan,

First, sorry for the delay I tagged your mails to be read later but took some 
time to reach them . Your last mail bumped the full conversation.

To better understand the simulation time, let me describe you what happens when 
you click play. After creating the schema you basically have a set of blocks 
with parameter values set at edition time and a set of links that connect 
blocks. Before simulation happens there is still work to do:
 1. As parameters can change the structure of blocks, we need to 
refresh/evaluate all blocks to set a parameters to the current values.
 2. A flatten copy is created to resolve inputs/outputs ports on subsystem
 3. The schedule of the graph is computed and a "compiled" cpr structure is 
created

On the simulation phase, you can only use this cpr structure to run ODE solvers 
on your system and produce results.

If you want to do multiple simulation of the same system changing only 
parameters *and* keeping the same diagram structure, I suggest you to use `Info 
= scicos_simulate(scs_m, Info)` where Info is defined as : Info = list(%tcur, 
%cpr, alreadyran, needstart, needcompile, %state0) . This seems not documented 
enough.

You can update parameters on Info(2) , the cpr, or Info(6) , the states, by 
yourself. This will remove all "compilation time" without using the internal 
scicosim  and let you change final time or filter parameters for example. For 
customers, we used this approach to do some optimization on filter coefficient.

Hope this will help you,
Regards,

Clément


-Original Message-
From: users  On Behalf Of johan64
Sent: Sunday, February 28, 2021 12:56 PM
To: users@lists.scilab.org
Subject: Re: [Scilab-users] xcos_simulate()

Hi,

I am sorry, there is a mistake in my first post. Please, don't care about the 
script described in italic.

My need is to compile my xcos diagram one time, simulate, then change context 
parameters and run other simulations (in order to perform parametric 
optimization on a large xcos model with many parameters and about 10-15 state 
variables).

I did some research and tests. To sum up :

1/xcos_simulate(scs_m,needcompile) : According to the Scilab Help, needcompil 
is "DEPRECATED". Therefore, compilation is needed each times.

//
2/scicos_simulate(scs_m,Info). I tried the PID optimization example method.
https://wiki.scilab.org/Xcos/Examples/PID
  

Execute my model with
///Lancement de la simulation
disp("lancement")
 tic();
Info=scicos_simulate(scs_m,list())
disp( "Durée simulation1",toc());
tic();
Info=scicos_simulate(scs_m,Info)
 disp( "Durée simulation2",toc())/

Gives

/"lancement"
"Durée simulation1" 83.604448
"Durée simulation2" 81.738820/
Therefore, I win just 2 seconds with this method

/
3/scicosim(); It seems to be the holy grail.
/
disp("lancement")
tic();
cpr=xcos_simulate(scs_m,4)
//cpr = xcos_compile(scs_m);
disp( "Simulation time 1 =",toc());
//Exploitation des données de compilation state0=cpr.state; // cpr variable 
came from the compilation sim=cpr.sim; //Paramètre de simulation tf=111; 
atol=1.e-6; rtol=1.e-6; ttol=1.e-10; deltat=tf; scale=0; solver=0; hmax=0.1;

tol=[atol,rtol,ttol,deltat,scale,solver,hmax];

//Enregistrement des résultats
//save(pathu_result);

tic();
// initialisation
[state,t]=scicosim(state0,0,tf,sim,'start',tol);
// run
[state,t]=scicosim(state,t,tf,sim,'run',tol)
//end
[state,t]=scicosim(state,t,tf,sim,'finish',tol);
disp("Simulation time 2"+" = ",toc());
/
Gives
/
"Simulation time 1 ="

   83.815849

  "Simulation time 2 = "

   0.9816021
/ 

I win about 83 seconds!!! 

Unfortunately, after running xcos_simulate one time, I don't find simple way to 
change context parameters without launch xcos_simulate again (using
scs_m.props.context...) which wastes simulation time.
cpr.sim.rpar seems to contain block parameters but without symbolic expression.

does anyone have an idea?

Thank you for your help






--
Sent from: 
http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] xcos_simulate()

[Clément David]

Hi (again Johan),

For your information, we track/fix issue on big models by testing them in 
internal workbench. If you have simulation issue, we can add your model on this 
non-opensource set to try to improve the compilation time for it. Don’t 
hesitate to mail it to me (might be a partial or without parameter knowledge).

Regards,

Clément

From: users  On Behalf Of Johan Lafitte
Sent: Wednesday, February 10, 2021 6:41 PM
To: users@lists.scilab.org
Subject: [Scilab-users] xcos_simulate()

Hi,

My xcos model becomes quite large and takes time to compile. In order to launch 
batches and optimisation process, it seems possible to compile the model juste 
one time.
However, I meet the same difficulties as described in this post :

http://mailinglists.scilab.org/xcos-xcos-simulate-scs-m-1-or-xcos-simulate-scs-m-4-td4031207.html#a4031274;>http://mailinglists.scilab.org/xcos-xcos-simulate-scs-m-1-or-xcos-simulate-scs-m-4-td4031207.html#a4031274

Indeed, the following script...
  ___
loadXcosLibs;
importXcosDiagram("C:\Users\johan\OneDrive\Micro entreprise\Technique\Kayak 
guide\Modélisation\Scilab\optimisation"+"\modèle physique et commande 
simple_10_opti.zcos");
tic();
xcos_simulate(scs_m, 4);
disp("méthode 2",toc());

tic();
%cpr = xcos_compile(scs_m);
disp( "Durée compilation",toc());

tic();
xcos_simulate(scs_m,1)
disp( "méthode 1",toc());
  ___

...gives the following results :
 ___
"scicos_simulate step 1"
   50.813412 s

  "scicos_simulate step 2"
   57.440604 s

  "xcos_simulate(scs_m, 4) méthode 2"
   58.808546 s

  "Compilation duration"
   55.615238 s

  "xcos_simulate(scs_m,1) méthode 1"
   61.133700 s
 __

It seems the compilation step is done in all these cases.

Thank you for your time and for your help

Johan

note 1 : when the final time of the simulation is set from 20s to 200s, the 
execution time increases about 15s

note 2 : according to the windows task manager, CPUs seem to be used about 30% 
during compilation and about 100% during simulation which takes few seconds
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] plotplots() in Scilab

[Clément David]

Hello Samuel, hello all,

First thanks for the request for inclusion, that’s always good to have more 
features into Scilab itself. However, I have a few remarks regarding this 
function.


  1.  The function name plotplots() does not seem well known nor easy to find ; 
after a few research I found similar behavior for Matlab and Matplotlib worded 
as “zoomed” or “zoomed_inset_axes” which better represent the behavior.

  *   
https://stackoverflow.com/questions/13583153/how-to-zoomed-a-portion-of-image-and-insert-in-the-same-plot-in-matplotlib
  *   https://fr.mathworks.com/matlabcentral/fileexchange/59857-zoomplot
  *   
https://fr.mathworks.com/matlabcentral/answers/349042-zoomed-plot-in-the-same-figure

What about using `plot_zoomed()`, `plot_inset()` or `plot_inside()` ?


  1.  I found the need to have a second axe (example 1) different to recompute 
ticks (example 2). I might have miss something, could you clarify these two 
usage ?

Thanks,

Clément


From: users  On Behalf Of Samuel Gougeon
Sent: Thursday, April 1, 2021 10:07 PM
To: International users mailing list for Scilab. 
Subject: [Scilab-users] plotplots() in Scilab


Dear all,
I would like to propose to include the plotplots() graphical function into 
Scilab.

For now 3 years, plotplots() is distributed alone in its own external 
module, with a fair number of 
downloads for a single function.

Its embedded documentation is as well provided online as PDF, in 
english
 and in 
french.

As soon as a function has a local singularity or/and an asymptotical behavior 
(that's quite common), plotplots() is very helpful to illustrate its specific 
behaviors without masking more "regular" features with a crushing graphical 
scale.

Every comment is welcome about the current plotplots status, and about the 
proposal to include it as a native Scilab function.

Hope reading you,

Best regards

Samuel
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] find and locate local maxima

[Clément David]

Hello David,

I merged the change, it is now available on Scilab nightly build and on all CI 
builds after scilab-6.1-windows-64 #4595 
[Jenkins]<https://build.scilab.org/view/Scilab%206.1/job/scilab-6.1-windows-64/4595/>
 . Feel free to open bugs or reply on this thread if you have comments on this 
new feature.

Thanks,

Clément

From: users  On Behalf Of CHEZE David 227480
Sent: Thursday, March 18, 2021 12:44 PM
To: Users mailing list for Scilab 
Subject: Re: [Scilab-users] find and locate local maxima

Hi all,

I’d be glad obviously to download the whole package to test it and report my 
experience :  I’m not use with the ‘review interface’ is there any way to 
download the whole package or I just retrieve files one by one ?

Thanks,

David



De : users 
mailto:users-boun...@lists.scilab.org>> De la 
part de Stéphane Mottelet
Envoyé : mercredi 17 mars 2021 10:40
À : users@lists.scilab.org<mailto:users@lists.scilab.org>
Objet : Re: [Scilab-users] find and locate local maxima


Thanks Clément.

Interested users can readily download the files if they want to test the 
implementation even if it has not been reviewed. Particularly, it has not been 
discussed if we want to stick to the Matlab's implementation and API for this 
particular feature. Comments are welcome.

S.
Le 17/03/2021 à 10:19, Clément David a écrit :
Hello all,

I take your question as a way to explain / remind how we validate user 
contributions into the Scilab source code. Any change to the source code should 
be pushed to the codereview.scilab.org website (this is a gerrit instant, a git 
server that help reviewing changes). This help testing on multiple 
machines/OS/compilers and review the content ; any user can comment and give 
+1/-1 on a change. After there is no disagreement, we merge it into the Scilab 
source code.

The “Cannot merge” error is an alert to the reviewer, this commit need to be 
rebase (refreshed) against the latest source code ; this is not a blocker for 
the review but rather for a one-click merge .

Regards,

Clément

From: users 
<mailto:users-boun...@lists.scilab.org> On 
Behalf Of Claus Futtrup
Sent: Tuesday, March 16, 2021 7:40 PM
To: users@lists.scilab.org<mailto:users@lists.scilab.org>
Subject: Re: [Scilab-users] find and locate local maxima

Hi Stéphane

It looks very nice and I hope it will be added to Scilab as proposed by your 
code review. Why does it say in red print "Cannot Merge" ?

/Claus

On 16-03-2021 17:45, Stéphane Mottelet wrote:

Hi

For real life signals you should rather use something like this (Savitsky-Golay 
filters)

https://codereview.scilab.org/#/c/21499/<https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/codereview.scilab.org/#/c/21499/>

S.
Le 16/03/2021 à 17:09, CHEZE David 227480 a écrit :
Hi Clément,

Thank you for your quick reply and solution ! Actually it’s working for simple 
data but with noisy experimental timeseries, some filtering is required to get 
perfect regular signal (between the ‘true’ extrema) that could be then managed 
by the routine. I suppose this is something the Matlab/Octave is handling 
internally, with some parameters as function’s argument to tune it, maybe it’s 
not the case .

Regards,

David


De : users 
<mailto:users-boun...@lists.scilab.org> De la 
part de Clément David
Envoyé : mardi 16 mars 2021 16:27
À : Users mailing list for Scilab 
<mailto:users@lists.scilab.org>
Objet : Re: [Scilab-users] find and locate local maxima

Hello David,

After reading the Matlab documentation page, it seems pretty simple to 
implement using Scilab : and $ symbols:

function [pks, locs]=findpeaks(data)
ii = find(d(1:$-2) < d(2:$-1) & d(2:$-1) >= d(3:$));
pks = data(ii+2);
locs = ii + 2;
endfunction

data = [25 8 15 5 6 10 10 3 1 20 7];
plot(data)

[pks,locs] = findpeaks(data);
plot(locs, pks, 'xr');

Note: using oct2py and pims might also be an option for simple cases but these 
wrappers are complex to use and data need to be copied at language boundaries.

Regards,

Clément

From: users 
mailto:users-boun...@lists.scilab.org>> On 
Behalf Of CHEZE David 227480
Sent: Tuesday, March 16, 2021 2:53 PM
To: Users mailing list for Scilab 
mailto:users@lists.scilab.org>>
Subject: [Scilab-users] find and locate local maxima

Hi all,

I’m looking for function that could find and locate every local maxima of any 
discrete time signal (timeseries), similar to Matlab or Octave function 
findpeaks(), scipy find_peaks(). Is anyone aware if something similar is 
already available in Scilab ? (I already browsed a little bit and it don’t seem 
so…)
If not in Scilab macros, any hint to use the Octave or scipy function directly 
from Scilab?
More globally it seems that Octave Forge could be linked with Python (from 
oct2py import octave
# Load the Octage-Forge signal package.
octave.eval("pkg load signal")), does someone ever tried to bridge similarly in 
Scilab 

Re: [Scilab-users] find and locate local maxima

[Clément David]

Hello all,

I take your question as a way to explain / remind how we validate user 
contributions into the Scilab source code. Any change to the source code should 
be pushed to the codereview.scilab.org website (this is a gerrit instant, a git 
server that help reviewing changes). This help testing on multiple 
machines/OS/compilers and review the content ; any user can comment and give 
+1/-1 on a change. After there is no disagreement, we merge it into the Scilab 
source code.

The “Cannot merge” error is an alert to the reviewer, this commit need to be 
rebase (refreshed) against the latest source code ; this is not a blocker for 
the review but rather for a one-click merge .

Regards,

Clément

From: users  On Behalf Of Claus Futtrup
Sent: Tuesday, March 16, 2021 7:40 PM
To: users@lists.scilab.org
Subject: Re: [Scilab-users] find and locate local maxima

Hi Stéphane

It looks very nice and I hope it will be added to Scilab as proposed by your 
code review. Why does it say in red print "Cannot Merge" ?

/Claus

On 16-03-2021 17:45, Stéphane Mottelet wrote:

Hi

For real life signals you should rather use something like this (Savitsky-Golay 
filters)

https://codereview.scilab.org/#/c/21499/

S.
Le 16/03/2021 à 17:09, CHEZE David 227480 a écrit :
Hi Clément,

Thank you for your quick reply and solution ! Actually it’s working for simple 
data but with noisy experimental timeseries, some filtering is required to get 
perfect regular signal (between the ‘true’ extrema) that could be then managed 
by the routine. I suppose this is something the Matlab/Octave is handling 
internally, with some parameters as function’s argument to tune it, maybe it’s 
not the case .

Regards,

David


De : users 
<mailto:users-boun...@lists.scilab.org> De la 
part de Clément David
Envoyé : mardi 16 mars 2021 16:27
À : Users mailing list for Scilab 
<mailto:users@lists.scilab.org>
Objet : Re: [Scilab-users] find and locate local maxima

Hello David,

After reading the Matlab documentation page, it seems pretty simple to 
implement using Scilab : and $ symbols:

function [pks, locs]=findpeaks(data)
ii = find(d(1:$-2) < d(2:$-1) & d(2:$-1) >= d(3:$));
pks = data(ii+2);
locs = ii + 2;
endfunction

data = [25 8 15 5 6 10 10 3 1 20 7];
plot(data)

[pks,locs] = findpeaks(data);
plot(locs, pks, 'xr');

Note: using oct2py and pims might also be an option for simple cases but these 
wrappers are complex to use and data need to be copied at language boundaries.

Regards,

Clément

From: users 
mailto:users-boun...@lists.scilab.org>> On 
Behalf Of CHEZE David 227480
Sent: Tuesday, March 16, 2021 2:53 PM
To: Users mailing list for Scilab 
mailto:users@lists.scilab.org>>
Subject: [Scilab-users] find and locate local maxima

Hi all,

I’m looking for function that could find and locate every local maxima of any 
discrete time signal (timeseries), similar to Matlab or Octave function 
findpeaks(), scipy find_peaks(). Is anyone aware if something similar is 
already available in Scilab ? (I already browsed a little bit and it don’t seem 
so…)
If not in Scilab macros, any hint to use the Octave or scipy function directly 
from Scilab?
More globally it seems that Octave Forge could be linked with Python (from 
oct2py import octave
# Load the Octage-Forge signal package.
octave.eval("pkg load signal")), does someone ever tried to bridge similarly in 
Scilab ? oct2sci

Kind regards,

David




___

users mailing list

users@lists.scilab.org<mailto:users@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@lists.scilab.org<mailto:users@lists.scilab.org>

http://lists.scilab.org/mailman/listinfo/users


___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] find and locate local maxima

[Clément David]

Hello David,

After reading the Matlab documentation page, it seems pretty simple to 
implement using Scilab : and $ symbols:

function [pks, locs]=findpeaks(data)
ii = find(d(1:$-2) < d(2:$-1) & d(2:$-1) >= d(3:$));
pks = data(ii+2);
locs = ii + 2;
endfunction

data = [25 8 15 5 6 10 10 3 1 20 7];
plot(data)

[pks,locs] = findpeaks(data);
plot(locs, pks, 'xr');

Note: using oct2py and pims might also be an option for simple cases but these 
wrappers are complex to use and data need to be copied at language boundaries.

Regards,

Clément

From: users  On Behalf Of CHEZE David 227480
Sent: Tuesday, March 16, 2021 2:53 PM
To: Users mailing list for Scilab 
Subject: [Scilab-users] find and locate local maxima

Hi all,

I'm looking for function that could find and locate every local maxima of any 
discrete time signal (timeseries), similar to Matlab or Octave function 
findpeaks(), scipy find_peaks(). Is anyone aware if something similar is 
already available in Scilab ? (I already browsed a little bit and it don't seem 
so...)
If not in Scilab macros, any hint to use the Octave or scipy function directly 
from Scilab?
More globally it seems that Octave Forge could be linked with Python (from 
oct2py import octave
# Load the Octage-Forge signal package.
octave.eval("pkg load signal")), does someone ever tried to bridge similarly in 
Scilab ? oct2sci

Kind regards,

David

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Scilab 5.5.2 in Debian 10 - segmentation fault

[Clément David]

Hello Antoine,

It should run on Linux using 5.5.2 (as fork() is available) however if parallel 
work is needed I suggest you to use Scilab MPI rather than parallel_run. The 
former is process based with explicit variable transfer whereas the latter is 
implicit.

See https://help.scilab.org/docs/5.5.2/en_US/MPI_Recv.html for more information.

Thanks,

Clément

From: users  On Behalf Of Antoine Monmayrant
Sent: Thursday, February 25, 2021 4:25 PM
To: users@lists.scilab.org
Subject: Re: [Scilab-users] Scilab 5.5.2 in Debian 10 - segmentation fault


Hello Clément,

I forgot that detail.
But this will not help Andrei use parallel_run, as it does not work under 
linux, right?

Cheers,

Antoine
On 25/02/2021 16:10, Clément David wrote:
Hello Andrei,

To launch the Scilab 5.5.2 binary on new Linux version, you might need to 
remove some libraries (so files) provided by your system. Especially, you could 
remove the scilab-5.5.2/lib/thirdparty/libz.so.1 file which is provided by your 
system.

Regards,

Clément

From: users 
<mailto:users-boun...@lists.scilab.org> On 
Behalf Of Andrei Lomov
Sent: Thursday, February 18, 2021 11:00 AM
To: users@lists.scilab.org<mailto:users@lists.scilab.org>
Subject: [Scilab-users] Scilab 5.5.2 in Debian 10 - segmentation fault

Hi All,
In order to use Scilab’ parallel_run in Debian 10 (x86_64),
i download
https://www.scilab.org/download/5.5.2/scilab-5.5.2.bin.linux-x86_64.tar.gz
unpack it to
~/foo/scilab-5.5.2
then
cd ~/foo/scilab-5.5.2/bin
and run …

$./scilab

Segmentation fault
:((

? What am I doing wrong ...

--
WBR,
Andrei




___

users mailing list

users@lists.scilab.org<mailto:users@lists.scilab.org>

http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Scilab 5.5.2 in Debian 10 - segmentation fault

[Clément David]

Hello Andrei,

To launch the Scilab 5.5.2 binary on new Linux version, you might need to 
remove some libraries (so files) provided by your system. Especially, you could 
remove the scilab-5.5.2/lib/thirdparty/libz.so.1 file which is provided by your 
system.

Regards,

Clément

From: users  On Behalf Of Andrei Lomov
Sent: Thursday, February 18, 2021 11:00 AM
To: users@lists.scilab.org
Subject: [Scilab-users] Scilab 5.5.2 in Debian 10 - segmentation fault

Hi All,
In order to use Scilab’ parallel_run in Debian 10 (x86_64),
i download
https://www.scilab.org/download/5.5.2/scilab-5.5.2.bin.linux-x86_64.tar.gz
unpack it to
~/foo/scilab-5.5.2
then
cd ~/foo/scilab-5.5.2/bin
and run …

$./scilab

Segmentation fault
:((

? What am I doing wrong ...

--
WBR,
Andrei

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Some details on the documentation of log(), log10(), etc.

[Clément David]

Hello all,

Thanks for opening the discussion on this “new user”-related topic, this is 
always good to improve our help for existing user and new comers ; to let them 
havie a clear understanding of Scilab-lingua.

One important point to me is to have a proper distinction between “array” (as 
values organized in multiple dimensions) and more precise terms with more 
constraints on dimensions “horizontal vector”, “matrix”, etc… For keeping the 
rationale up to date, I suggest you to edit the Localization wiki page [1].

In term of code update, I can help you finding duplicated messages but keep in 
mind that the build-system create .pot files from the source code. To look for 
duplicate, the more important is to upgrade the source code.

[1]: https://wiki.scilab.org/Localization in English - Standard messages

Note: AFAK the “constant” term has been removed on 6.0.0 documentation/error 
message as this is the default datatype, in case of advanced type management 
the term “decimal” can be used instead.

Regards,
Clément



From: users  On Behalf Of Stéphane Mottelet
Sent: Saturday, February 20, 2021 5:35 PM
To: users@lists.scilab.org
Subject: Re: [Scilab-users] Some details on the documentation of log(), 
log10(), etc.


By looking into the documentation messages I realized that we already use 
"array" :

./locale/de_DE/LC_MESSAGES/scilab.po-e:msgid "%s: Wrong type for input argument 
#%d: Array of double expected.\n"

S.
Le 20/02/2021 à 17:21, Stéphane Mottelet a écrit :

Hi Frederico,

In almost all other numerical software the object defined in Scilab by 
a=zeros(3,3,3) is called an "array", m=zeros(3,3) a "matrix" and x=zeros(1,3) 
or y=zeros(3,1) "vectors", and all of them are called "arrays". BTW, now the 
"hyper" prefix sounds like when it is used in "hyperspace"... To me, the 
documentation should be revamped to always use "array" when the denoted object 
can have any number of dimensions and use "matrix" only when the array has to 
be a matrix. Concerning your remark about the "constant vector or constant 
matrix", yes, this should be changed by something more explicit, like "array of 
double". We already use similar terms in error messages, i.e.

"%s: Wrong type for input argument #%d: A matrix of double expected.\n"

Hence we could synchonize the uses of localized messages with the 
documentation. When I say "we" it also includes "you", Frederico. If you feel 
that Scilab could be improved by a better documentation, please contribute. If 
you need some help to start using the relevant tools (git, codereview) I would 
be glad to help you.

S.
Le 20/02/2021 à 01:29, Federico Miyara a écrit :

Dear all,

In an old script where I needed to apply log10 to an hyperarray I had 
implemented it as log(A)/log(10) with a comment indicating that in that version 
log10() didn't work for hyperarrays (unfortunately I don't recall what version 
it was).

In Version 6.1.0 it does work for hyperarrays, but the documentation still says 
that it applies to vectors or matrices:

https://help.scilab.org/docs/6.1.0/en_US/log10.html

In some contexts "matrix" may be interpreted as an hyperarray or hypermatrix 
(for instance when speaking of N-D matrices), but for Scilab a matrix is 
formally a two-dimensional array:

https://help.scilab.org/docs/6.1.0/en_US/matrices.html

I think the documentation should indicate that it applies to vectors, matrices 
and hypermatrices

Another problem is regarding log(). It says that the input argument is a 
"constant vector or constant matrix":

https://help.scilab.org/docs/6.1.0/en_US/log.html

However, it seems that "constant" has a specific meaning in Scilab as a 
predefined variable:

https://help.scilab.org/docs/6.1.0/en_US/section_421ab29126e21a1e1e403ee27a18fda4.html

As it is worded, it seems that log() is applied to predefined variables. I 
think it should refer more clearly to the type double (it doesn't work, for 
instance, for integer types such as int16(2)).

In the case of log2() the description of arguments is even stranger:

https://help.scilab.org/docs/6.1.0/en_US/log2.html

It confuses the argument section with 

Re: [Scilab-users] scicv - CV_FOURCC

[Clément David]

Hello Philipp,


Question 1: What other formats are possible for "CV_FOURCC"?

https://www.fourcc.org/ describes what exist and might be supported by our 
binary. The codecs are only the ones supported by ffmpeg (included as a DLLs) 
or your system ones.



Question 2: What format should - ideally - the input images have? Currently I 
use BMP's, created with xs2bmp.

Yes BMP is fine. The rational are ; for a better encoding, use lossless image 
format ; for speed use non-compressed ones.
Thanks,

Clément

From: users  On Behalf Of P M
Sent: Wednesday, February 10, 2021 7:45 PM
To: International users mailing list for Scilab. 
Subject: [Scilab-users] scicv - CV_FOURCC

Dear ,

from the scicv toolbox I use the new_VideoWriter - function:

videoWriter = new_VideoWriter(filename, fourcc, fps, frameSize)


Everything fine so far, except:

There are artefacts in the final video., which I guess are connected to 
compression.

Here are some lines from my code:

videoWriter = new_VideoWriter(outPath, CV_FOURCC('M', 'P', '4', '2'), 
frameRate, size(img));



if ~VideoWriter_isOpened(videoWriter) then

disp("Cannot create video file: " + outPath);

end



for i = 1:nrOfFiles

img = imread(inPath(i));

VideoWriter_write(videoWriter, img);

disp(i)

end



delete_VideoWriter(videoWriter);

Question 1: What other formats are possible for "CV_FOURCC"?
I just used'M', 'P', '4', '2'  , because it's the only mentioned in the 
help.



Question 2: What format should - ideally - the input images have? Currently I 
use BMP's, created with xs2bmp.

Thank you,

Philipp


___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Scilab & cdf-file format

[Clément David]

Hello,

From my knowledge there is no existing toolbox to manage this CDF format. 
However conversion tools exists [1] that can convert CDF to HDF4 and HDF4 to 
HDF5 (natively supported by Scilab) ; IMHO this will be the simpler way to 
handle that format.

You could also :

  1.  use SWIG to create your own toolbox mapping the C API to Scilab

OR

  1.  the CDFj package to call CDF function using Java from Scilab (there might 
be some dataset copies)

[1]: https://cdf.gsfc.nasa.gov/html/faq.html#conversion

Regards,

Clément

From: users  On Behalf Of P M
Sent: Wednesday, February 10, 2021 7:19 PM
To: International users mailing list for Scilab. 
Subject: [Scilab-users] Scilab & cdf-file format

Dear Users,

Is there any Scilab toolbox available, handling the cdf-file-format?

cdf = "common data file", which was original developed by NASA :   
https://cdf.gsfc.nasa.gov/

Thank you,
Philipp

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] slight bug in exists()

[Clément David]

Hello all,

Indeed this would probably break some code. We should carefully check the 
exist() usage within Scilab to ensure the output value is not passed to 
macros/gateways checking for a “double” datatype. Code using exists() output 
value as index or as condition might not be affected.

Don’t hesitate to push such a change on the master branch I will review it.

Thanks,

Clément

From: users  On Behalf Of Antoine Monmayrant
Sent: Tuesday, February 9, 2021 4:28 AM
To: users@lists.scilab.org
Subject: Re: [Scilab-users] slight bug in exists()


Hello Federico,

I agree with you that this would make more sense.
Could such a change be implemented for a point release?
I assume it would introduce some bugs in existing code relying on the (unusual) 
double output...

Antoine
On 09/02/2021 03:24, Federico Miyara wrote:

Dear all,

I had already mentioned this a while ago 
(http://mailinglists.scilab.org/Scilab-users-exists-yields-double-tt4039853.html),
 but as I guess we are in the update season, it would be good opportunity to 
fix this (if there isn't strong opposition, or a good reason for this behavior, 
of course).

I'm referring to the fact that the function exists() should by nature yield a 
Boolean result such as T or F. However, it yields 1 or 0. While this is not a 
big deal, similar functions performing a binary decision on their arguments, 
such as isreal(), isvector(), isfile() and many others, yield Boolean results.

Regards,

Federico Miyara

[Image removed by 
sender.]
Libre de virus. 
www.avast.com



___

users mailing list

users@lists.scilab.org

http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] How to read profileGetInfo().LineCoverage results correctly?

[Clément David]

Hello Samuel, hello all,

As a reminder and behind the introduction of profile-prefixed functions the 
idea is to implement functions similar to the ones available within Scilab-5 to:

  1.  instrument a specific function
  2.  get the counters in a Scilab structure
  3.  de-instrument a specific function

So depending on your use you can covStart()/profileEnable() then 
profileGetInfo() then covStop() /profileDisable() to retrieve information about 
your execution. covStart() will clear previous instrumented information whereas 
profileEnable() allow to append functions (same difference between covStop() 
and profileDisable()). In term of arguments, covStart() allow string arguments 
(function names) whereas profileEnable() only take functions or libraries.

About numbers, well I think you get it right and I agree the lines 2,3 and 4 
are not obvious ; there might be a bug there. 638ms for getting / setting a 
double scalar is not correct as well as the cumulated time `sum( prof(4)(1), 
'r')` does not look like being in seconds (as stated in the documentation).

Clément

From: users  On Behalf Of Samuel Gougeon
Sent: Thursday, January 28, 2021 2:44 PM
To: International users mailing list for Scilab. 
Subject: [Scilab-users] How to read profileGetInfo().LineCoverage results 
correctly?


Dear all,

Still about new Scilab 6 profiling capabilities:
The first so-called ""Basic example" given in the documentation of  the 
profiling features
@ https://help.scilab.org/docs/6.1.0/en_US/profile.html  is the following:

// Function to be profiled

function x=foo(n)

  if n > 0 then

x = 0;

for k = 1:n

  s = svd(rand(n, n));

  x = x + s(1);

end

  else

x = [];

  end

endfunction



// Enables the profiling of the function

profileEnable(foo);



// Executes the function

foo(200);



// Returns the function profiling results

prof = profileGetInfo();





Now, after https://help.scilab.org/docs/6.1.0/en_US/profileGetInfo.html we can 
get
--> prof.LineCoverage(1)
 ans  =
  -1. 0.// function ...
   1. 0.6385544// if ...  Why so long time ??
   1. 0.6385513// x = 0;638 ms for a single 
execution ??
   1. 0.6385467// idem
   200.   1.2763477 // OK, quite expected. The strange thing is 
that the "x=0" time is almost the half of this time..
   200.   0.0005116 // OK, a result more understandable than 
for x=0 above.
  -1. 0.   // OK (end for)
  -1. 0.   // OK (else)
   0. 0.// OK : never met
  -1. 0.
  -1. 0.

Since it is presented as a basic example, it is likely error-proof.
So what am i missing about how to read or interpret these results ?

Thanks for any clarification. Without it, it quite hard to trust and use this 
important tool.
Best regards
Samuel Gougeon
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] {EXT} New constant %chars to get sets of symbols

[Clément David]

Hello all,

For your information, this proposal has been merged and will be available on 
the next release. Thanks Samuel for this idea and for the code !

Regards,

Clément 

-Original Message-
From: users  On Behalf Of Dang Ngoc Chan, 
Christophe
Sent: Monday, January 4, 2021 9:30 AM
To: sgoug...@free.fr; Users mailing list for Scilab 
Subject: Re: [Scilab-users] {EXT} New constant %chars to get sets of symbols

Hello to all

(and best wishes for the new year)

> De : Samuel Gougeon
> Envoyé : mardi 29 décembre 2020 16:40
>
> So, i would like to propose to add this new constant to Scilab, for the 
> benefit of all users.
> In this respect, you will find
> http://bugzilla.scilab.org/attachment.cgi?id=5206

That suits me.
For the time being, I'm using my personal Wikipedia page in exactly the same 
way 
https://fr.wikipedia.org/wiki/Utilisateur:Cdang/bo%C3%AEte_%C3%A0_outils#Caract%C3%A8res_sp%C3%A9ciaux
so that's perfect for me.

Best regards

--
Christophe Dang Ngoc Chan
Mechanical calculation engineer

General
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error), please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden.
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] atomsLoad

[Clément David]

Hello,

>From the source directory, you could use `exec builder.sce` [1]. Atoms 
>toolboxes only rely on Scilab scripts to describe and execute the build 
>(Makefiles are used behind the scene) ; for just rebuilding the toolbox, it 
>should be as simple as executing the builder, bumping the version and zip the 
>directory.

[1]: https://wiki.scilab.org/howto/Create%20a%20toolbox#Build_and_load_a_module
howto/Create a toolbox - Scilab 
Wiki
Creating an ATOMS toolbox. This page describes the usual method to create, 
package, and distribute a Scilab external module (ATOMS Toolbox). In the first 
part, we show how to structure the module by creating directories, 
sub-directories and files at the right place.
wiki.scilab.org
Thanks,

Clément

De : users  de la part de Jean-Yves Baudais 

Envoyé : mardi 22 décembre 2020 16:12
À : Users mailing list for Scilab 
Objet : Re: [Scilab-users] atomsLoad

Hi,

> It is quite easy (a 10 min. job). I made the needed modifications and it
> compiles and loads under OSX. If you give me the rights on Gitlab I can commit
> the modifications this afternoon.

Ok, but I don't how to do this, but I'm ready to learn :-) So, could you give 
me the step starting with "stftb" source? 
https://atoms.scilab.org/toolboxes/stftb/2.0.2/files/stftb-2.0.2-src.zip (I'm 
regular with Linux command-line, not too much with makefile)

Or, maybe there already exists a document explaining the steps?

--
Jean-Yves Baudais
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] atomsLoad

[Clément David]

Hello,

It looks like the scilab 5.5.2 binary is not compatible with your system 
(nc_putchar version error). IMHO it should be better to use the latest Scilab 
version and try to build dependencies by hand ; regarding the toolboxes:
 * http://forge.scilab.org/index.php/p/stftb/ is not published for 6.1 but 
might compile on it ; get the sources and try to build on your own machine.
 * https://atoms.scilab.org/toolboxes/emd_toolbox/ already uses the pvApiCtx 
symbol ; it might be possible to port it to scilab 6.1 without a big 
refactoring.

Thanks,

Clément

De : users  de la part de Jean-Yves Baudais 

Envoyé : mardi 22 décembre 2020 12:36
À : Users mailing list for Scilab 
Objet : Re: [Scilab-users] atomsLoad

Hi,

> You must use Scilab 5.5.2 and install the 1.2 version of the toolbox. It
> should run out of the box.

Ok. I installed it. "scilab" command and "scilab -nw" or "-nb" or "-ns" or 
"-noatomsautoload" give the so funny "Segmentation fault" :-( Hopefully, 
"scilab -nwni" works, but I only have the head_comments help and no plot. So, 
not so funny, but I can juggle between scilab-5.5.2 and scilab-6.1.0

"scilab -debug" does not work anymore (but I not able to use gdb!)

gdb: SCI/lib/thirdparty/libtinfo.so.5: no version information available 
(required by gdb)
gdb: SCI/lib/thirdparty/libtinfo.so.5: no version information available 
(required by /lib/x86_64-linux-gnu/libreadline.so.7)
[...]
gdb: relocation error: /lib/x86_64-linux-gnu/libncursesw.so.5: symbol 
_nc_putchar version NCURSES_TINFO_5.9.20150530 not defined in file 
libtinfo.so.5 with link time reference

and "scilab -nogui" gives (maybe more informative)

Scilab startup function detected that the function proposed to the engine is 
the wrong one. Usually, it comes from a linker problem in your distribution/OS.
Here, Scilab should have 'libscijvm-disable' defined but gets 'libscijvm' 
instead.
If you do not know what it means, please report a bug on 
http://bugzilla.scilab.org/. If you do, you probably know that you should 
change the link order in SCI/modules/Makefile.am

Is there a simple way to solve this JVM problem? (Note that the default 
scilab-6.0 installed in my Unbuntu has a JVM problem also and does not work. 
Maybe I will try to solve it another time.)

--
Jean-Yves Baudais
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

[Scilab-users] forge.scilab.org retirement

[Clément David]

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
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] issue building Scilab 6.1.0 arm64 on Ubuntu 19.10 running inside Termux Proot Container

[Clément David]

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@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
> o

Re: [Scilab-users] Scilab-6.1 fails on OpenSuse Leap 15.2

[Clément David]

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@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
> 

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Scilab - Xcos

[Clément David]

Hello,

There is some bugs already reported for the mask feature, for example the bug 
#14155 [1] looks similar to what you describe here. Feel free to register on 
the CC List to be notified on change.

Thanks,

Clément

> -Original Message-
> From: users  On Behalf Of FMuff
> Sent: Monday, August 24, 2020 10:59 AM
> To: users@lists.scilab.org
> Subject: Re: [Scilab-users] Scilab - Xcos
> 
>  is there anyone who has an answer for this problem?
> 
> 1.) Is it in general not possible to create masked superblocks in Scilab
> 6.0.0 or higher?
> 2.) If this is not possible, which version is recommend for Windows 10 (I 
> tried
> 5.5.2, masking superblock works but this version crashes when I want "save
> as"... --> are there specific requiremnts which I dont know? Specific Visual 
> Studio
> version which has to be installed or what ever??
> 
> I would be really glad if someone could give me some inputs (wish to have one
> stable running Scilab-Xcos version on my Win10/64bits!
> 
> Thanks much in advance
> FMuff
> 
> 
> 
> --
> Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-
> f2602246.html
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Toolbox for calling external C++ libraries

[Clément David]

Hi,

Scilab 6 has an internal C++ API that you could use if you wish to be full C++, 
it might change from release to release and is not ABI stable. I suggest you 
use the C API to target a stable API/ABI even if you are developing your code 
in C++. Each time you wish to send data to Scilab, write them into a Scilab 
datatype; each time you wish to receive data, read them from a Scilab datatype.

If you prefer to map C++ objects, I suggest you to use SWIG [1] to generate the 
Scilab C API for you for a specific subset of your code. It will be easy to 
write a clean C/C++ interface and the generated code is only using the Scilab C 
API.

[1]: http://www.swig.org/

Thanks,

Clément

> -Original Message-
> From: users  On Behalf Of ejonah
> Sent: Friday, August 14, 2020 4:53 PM
> To: users@lists.scilab.org
> Subject: [Scilab-users] Toolbox for calling external C++ libraries
> 
> Hi,
> 
> I want to be able to import C++ functions using Scipy api. The examples in the
> documentation are for C or Fortran. Can anyone help me with a simply guide as
> to how to do this with C++? An example will be helpful.
> 
> Second question: What version of modern C++ does Scilab support?
> 
> Thanks
> 
> NB: I am running Scilab 6.1.0 on Windows 10.
> 
> 
> 
> --
> Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-
> f2602246.html
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] bvode example broken?

[Clément David]

Hello Rene, hello all,

After an investigation on the code, there is an issue storing the initial guess 
of the bvode() call; latter calls will get a zeros vector as guess and failed 
to converge. The bug 12418 [1] already report the issue, please comment here. 
IMHO this behavior might be handled without pushing the guessed values back to 
Scilab thus preserving the prototype.

 [1]: https://bugzilla.scilab.org/show_bug.cgi?id=12418

Thanks,

Clément

> -Original Message-
> From: users  On Behalf Of Rene Djack
> Sent: Thursday, July 16, 2020 2:05 PM
> To: Users mailing list for Scilab 
> Subject: Re: [Scilab-users] bvode example broken?
> 
> Also tested on linux/scilab 5.5.2 --> no error I will post in scilab bugzilla.
> Thanks for your answers
> Rgds
> René
> 
> 
> 
> 
> 
> Le mer. 15 juil. 2020 à 21:20, Stéphane Mottelet   > a écrit :
> 
> 
>   Hi,
> 
>   Same error on OSX since 6.0.2 version. I cannot test for 5.5.2 version
> because bvode was broken (it was fixed by desactivating  optimization
> compilation  flags).
> 
> 
>   S.
> 
> 
>   Le 15/07/2020 à 20:24, Rafael Guerra a écrit :
> 
> 
>   Hi,
> 
>   Face same error in Win10 Scilab 6.1.0.
> 
>   But no such error in Win10 Scilab 5.5.2.
> 
>   Rgds,
> 
>   Rafael
> 
> 
> 
>   From: users   boun...@lists.scilab.org>  On Behalf Of Rene Djack
>   Sent: Wednesday, July 15, 2020 8:39 PM
>   To: users@lists.scilab.org 
>   Subject: [Scilab-users] bvode example broken?
> 
> 
> 
>   Hello,
> 
>   I' m new to this list and to scilab too!
> 
>   Working on bvode, I try the example "Quantum Neumann
> equation" found in the scilab help and i get the error message
> 
>   "Collocation matrix is singular"
> 
>   Is this example broken?
> 
>   Somebody have the same message?
> 
> 
> 
>   I'm using scilab 6.10 from scilab-6.10.bin.linux-x86-64.tar.gz 
> on
> Ubuntu 20.4
> 
> 
> 
>   Tanks for reading
> 
>   Regards
> 
> 
> 
> 
> 
> 
> 
>   ___
>   users mailing list
>   users@lists.scilab.org 
> 
>   https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLm
> Zy/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@lists.scilab.org 
>   http://lists.scilab.org/mailman/listinfo/users
> 

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] %mlistType_clear overloading of clear() for mlist custom types

[Clément David]

Hello all,

Indeed this introduction was made to fulfill the needs for external objects to 
be clear as any other Scilab variables. I made some early prototypes for hdf5 
and xml but failed to push them further. IMHO this is feasible but there are 
some specific needs for each overloading (clearing the H5objects table with -1 
to make the slot available for HDF5; dereferencing the element on the general 
doc instance for XML).

Thanks,

Clément DAVID

> -Original Message-
> From: users  On Behalf Of Stéphane Mottelet
> Sent: Wednesday, July 1, 2020 6:59 PM
> To: users@lists.scilab.org
> Subject: Re: [Scilab-users] %mlistType_clear overloading of clear() for mlist
> custom types
> 
> 
> 
> 
> Le 01/07/2020 à 18:52, Samuel Gougeon a écrit :
> 
> 
>   Le 01/07/2020 à 13:47, Stéphane Mottelet a écrit :
> 
> 
>   Right, sorry for my previous message.
> 
> 
>   But, at the user level there are very few use cases: the clear
> overload is only useful if some mlist fields contain some pointers to 
> allocated
> data. For example sparse LU  factors or Java objects.
> 
> 
> 
> 
>   The auto-clearing of the Java side of Java objects is already
> implemented (and it's documented).
> 
> 
> I am not sure it worked perfectly before. Clement's patch is essentially 
> dealing
> with this case, see e.g.:
> 
> https://codereview.scilab.org/#/c/20679/14/scilab/modules/external_objects/s
> ci_gateway/cpp/sci_percent_EObj_clear.cpp
> 
> https://codereview.scilab.org/#/c/20679/14/scilab/modules/external_objects/s
> rc/cpp/clear.cpp
> 
> 
> S.
> 
> 
> 
> 
> 
> 
>   I am wondering if a similar native auto-clearing could be implemented
> for xml and hdf5 objects.
>   I guess that using clear before h5close() or xmlDelete() could make
> memory leaking.
> 
>   Samuel
> 
> 
> 
> 
>   ___
>   users mailing list
>   users@lists.scilab.org <mailto:users@lists.scilab.org>
>   https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLm
> Zy/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@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] scilab 6.1 crashes when trying to load big matfile (loadmatfile)

[Clément David]

Hello Antoine,

There might be some extra copies at loading time that overflow the memory ; 
what's the amount of memory you have available ?

And also, to investigate, could you please either share a script used to 
generate similar data or describe the used data structure ?

Thanks,

Clément 

> -Original Message-
> From: users  On Behalf Of Stéphane Mottelet
> Sent: Wednesday, June 17, 2020 1:52 PM
> To: users@lists.scilab.org
> Subject: Re: [Scilab-users] scilab 6.1 crashes when trying to load big matfile
> (loadmatfile)
> 
> Hello Antoine,
> 
> Did you to save a single "hypermatrix in a cell" in matlab and then load in 
> Scilab ?
> 
> S.
> 
> Le 17/06/2020 à 13:22, Antoine Monmayrant a écrit :
> > Hello All,
> >
> > I cannot open large matfile in scilab (~3.4Gb).
> > Scilab is always dying with an error message that is extremely
> > instructive: "Killed".
> >
> > It's a bit cumbersome to share this big fie, so do you have any idea
> > on how to investigate this issue and try to locate the root cause?
> >
> > As a side note, it might be a problem related to either the size of
> > the variables or their nature: cells containing hypermatrices.
> > The file itself is not corrupted (I managed to open it in matlab and
> > to save each hypermatrix into individual files that got imported in
> > scilab with no problem.
> >
> > Cheers,
> >
> > Antoine
> >
> > ___
> > users mailing list
> > users@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@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] BusCreator, BusSelector in Scilab ?

[Clément David]

Hi Tien and welcome,

The Simulink's BusCreator/BusSelector blocks are not available for 
heterogeneous datatypes (having a link composed of an integer and a double) but 
if you only have double values on your signals you could use MUX/DEMUX blocks.

Note: you could also use name=idx in the context to access the idx field by 
name where idx is the index in the MUX/DEMUX block.

--
Clement

> -Original Message-
> From: users  On Behalf Of tien.dang
> Sent: Thursday, May 21, 2020 5:29 AM
> To: users@lists.scilab.org
> Subject: [Scilab-users] BusCreator, BusSelector in Scilab ?
> 
> I'm doing project to convert model in Matlab Simulink to Scilab. I do not know
> the module BusCreator and BusSelector are supported in Scilab or Not. I just
> checked in Scilab Palette, don't have any module like this.
> How would I find that module in Scilab? BusCreator and BusSelector ?
> Thanks
> 
> 
> 
> 
> 
> --
> Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-
> f2602246.html
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Can Mux and Demux have more than 32 ports

[Clément David]

Hello Tien, and welcome 

Are you developing on Windows or Linux ? Did you follow the quick starts 
described in https://wiki.scilab.org/Compilation%20of%20Scilab ?

Thanks,

--
Clement

> -Original Message-
> From: users  On Behalf Of tien.dang
> Sent: Tuesday, May 19, 2020 12:26 PM
> To: users@lists.scilab.org
> Subject: [Scilab-users] Can Mux and Demux have more than 32 ports
> 
> Dear all,
> As title, Can I custom Mux and Demux block to have more than 32 ports, for
> example: 64 ports as I need.
> I try to re build source code base on Git repos but meet so many errors.
> Thanks
> Tien Dang
> 
> 
> 
> --
> Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-
> f2602246.html
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] CsvRead function

[Clément David]

Hello all, hello Daniel,

There has been some modification on the csvRead code to speed things up and 
there might be some issue in the new code. If you can reproduce with a reduced 
CSV file, could you open a bug with a sample of your code ?

Thanks,

--
Clément


From: users  On Behalf Of Jan Åge Langeland
Sent: Tuesday, May 12, 2020 1:41 PM
To: Users mailing list for Scilab ; Daniel Stringari 

Subject: Re: [Scilab-users] CsvRead function


csvRead is quite strict regarding column structure etc, but the associated 
error message is typical "can not read..". So when it reports "does not 
exist", it looks like the file is missing, or misplaced. If you still think the 
file is there, you may try this script that I have used to check csv files:

//Read CSV file -JÅ 2020

datafile="test.csv";

separators=[ascii(9),";"];

decimal=",";

headerlines=2;

linestoread=-1;// -1 for all

footerlines=2;

fid = mopen(datafile,'rb');

csvline=mgetl(fid,linestoread);

mclose(fid);

clear dataset;

n=size(csvline,1);

for k=1:n

if k>headerlines && k___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Windows 10 VS 2015 example under ilib_build fails pvApiCtx undeclared identifier

[Clément David]

Hello,

You are correct, the pvApiCtx global define available in Scilab 5 no more 
exists in Scilab 6 as described in [1] or [2]. The call_scilab might need to be 
updated to cover this change, could you please post a bug on that ?

[1]: https://cgit.scilab.org/scilab/tree/scilab/CHANGES.md?id=6.0.2#n374
[2]: https://help.scilab.org/docs/6.1.0/en_US/integerExample.html

In a sentence, you should add a variable `void* pvApiCtx` on each gateway 
declaration. This variable will be passed through the Scilab APIs as a context 
of execution.

Thanks,

--
Clément

> -Original Message-
> From: users  On Behalf Of Freddos
> Sent: Friday, May 8, 2020 11:19 AM
> To: users@lists.scilab.org
> Subject: Re: [Scilab-users] Windows 10 VS 2015 example under ilib_build fails
> pvApiCtx undeclared identifier
>
> How did it go with this one? I just upgraded to Scilab 6.1 (from 5.5.2) and 
> got the
> "pvApiCtx: undeclared indentifier" using the "Scilab Engine"
> (calling Scilab from my C++ application). All upgrade documentation (5 to 6) I
> have found only talks about the API using Gateways (not Scilab Engine), and 
> the
> documentation for the call scilab api still has code examples with the 
> pvApiCtx
> variable ("Double management" for example). But looking in the scilab headers
> it seems to have been removed. So either how do I get the pvApiCtx variable 
> (?)
> or how is the right way to read variables from the Scilab Engine in Scilab 
> 6.x?
>
>
>
> --
> Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-
> f2602246.html
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Really headless figure generation in scilab

[Clément David]

Hello,

Thanks for sharing the info Stéphane, it is documented on the scilab binary 
help page, on https://help.scilab.org/docs/6.1.0/en_US/scilab.html . However, 
this might not be clear enough. Maybe adding your usage as an example can help?

Thanks,

--
Clément

> -Original Message-
> From: users  On Behalf Of Stéphane Mottelet
> Sent: Wednesday, April 29, 2020 3:33 PM
> To: users@lists.scilab.org
> Subject: Re: [Scilab-users] Really headless figure generation in scilab
> 
> I don't think so. This is the way Scilab is launched to build the 
> documentation.
> 
> S.
> 
> Le 29/04/2020 à 15:28, Antoine Monmayrant a écrit :
> >
> > On 29/04/2020 15:18, Stéphane Mottelet wrote:
> >>
> >> SCI_DISABLE_TK=1 SCI_JAVA_ENABLE_HEADLESS=1
> >> _JAVA_OPTIONS='-Djava.awt.headless=true'
> >
> >
> > Thanks Stéphane for this dark magic!
> > It works.
> > Is this documented somewhere?
> >
> >
> > Antoine
> >
> > ___
> > users mailing list
> > users@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@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] question non datafit

[Clément David]

Hello Federico, hello all,

Thanks for pointing this, it looks like there is some missing URL redirect 
somewhere.

google "help scilab datafit" on a private navigation tab redirect to the 5.3.3 
help page whereas https://help.scilab.org/datafit looks OK. I will try to 
update the index to improve that, a related bug is #12746. See 
https://bugzilla.scilab.org/show_bug.cgi?id=12746 for more information and 
discussion on that topic, do not hesitate to contribute if you have some SEO 
knowledge.

Thanks,

--
Clément

> -Original Message-
> From: users  On Behalf Of Federico 
> Miyara
> Sent: Tuesday, April 7, 2020 2:28 AM
> To: users@lists.scilab.org
> Subject: Re: [Scilab-users] question non datafit
> 
> 
> Samuel:
> 
> Oh, this is embarrasing... I did a web search on non-linear fit and 
> somehow the top results always point at an outdated version (5.5.2) of 
> Scilab's documentation. I wonder why
> 
> Thanks, the new documentation is much better!
> 
> Regerds,
> 
> Federico Miyara
> 
> 
> 
> 
> On 04/04/2020 06:58, Samuel Gougeon wrote:
> 
> 
>   Le 04/04/2020 à 09:26, Federico Miyara a écrit :
> 
> 
> 
>   Dear All,
> 
>   I'm trying to understand the function datafit.
> 
>   The documentation says:
> 
> 
> 
>   datafit is used for fitting data to a model. For a 
> given function 
> G(p,z), this function finds the best vector of parameters p for 
> approximating G(p,z_i)=0 for a set of measurement vectors z_i. Vector 
> p is found by minimizing 
> G(p,z_1)'WG(p,z_1)+G(p,z_2)'WG(p,z_2)+...+G(p,z_n)'WG(p,z_n)
> 
> 
> 
>   I don't quite understand what is G(p,z_1)'WG(p,z_1). Are some 
> product signs * missing? Shouldn't it be G(p,z_1)'*W*G(p,z_1)? Are 
> these signs implied as in regular algebra notation?
> 
> 
> 
> 
> 
>   Hello Federico,
>   Please see the documentation of the latest scilab release:
>   https://help.scilab.org/docs/6.1.0/en_US/datafit.html
>   Regards
> 
> 
> 
> 
> 
> 
>   ___
>   users mailing list
>   users@lists.scilab.org 
>   http://lists.scilab.org/mailman/listinfo/users
> 

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Polynomial fitting

[Clément David]

Hello Frederico,

AFAIK there is a moc_polyfit function inside the Matlab/Octave Compatibility 
toolbox which might help you porting your code. Stixbox also provides a polyfit 
function which might be more generic toward Scilab datatypes.

Thanks,

--
Clément

> -Original Message-
> From: users  On Behalf Of Stéphane Mottelet
> Sent: Thursday, April 2, 2020 10:48 AM
> To: users@lists.scilab.org
> Subject: Re: [Scilab-users] Polynomial fitting
> 
> Hello Frederico,
> 
> 
> Le 02/04/2020 à 10:27, Federico Miyara a écrit :
> 
> 
> 
>   Dear All,
> 
>   Trying to convert an old Matlab script to Scilab I miss the function
> polyfit, which computes the coefficients of a polynomial that fits x-y data 
> using
> the least square method.
> 
>   I found the following thread http://mailinglists.scilab.org/Polynomic-
> regression-td4030799.html
>  inglists.scilab.org/Polynomic-regression-td4030799.html>  explaining that one
> can use the backslash, for instance for a 3rd degree polynomial, where x and y
> are column vectors:
> 
>   X = [ones(x), x, x.^2, x.^3]
>   A = X\y;
> 
>   (I changed the order of powers to get the coefficients ready for horner)
> 
>   I implemented a polyfit function using the basic theory of polynomial
> regression and I find it is faster by a factor of 1.5-2 than the previously
> mentioned method.
> 
> 
> Yeah, but really badly conditionned compared to the above method which is
> based on orthogonal tranformations (X=Q*R factorization). With your below
> method you solve a linear system with X'*X matrix which has a condition number
> which is the square of the condition number of the R matrix issued from the 
> Q*R
> factorization of X.
> 
> S.
> 
> 
> 
>   The basic algorithm I use is (n = desired degree):
> 
>   // Initialize matrix X
>   X = ones(length(x), n+1);
>   // Compute Vandermonde's matrix
>   for k =2:n+1
>  X(:,k) = X(:,k-1).*x;
>   end
>   // Apply the Moore-Penrose pseudoinverse matrix and
>   // multiply by the dependent data vector to get the
>   // least squares approximation of the polynomial
>   // coefficients
>   A = inv(X'*X)*X'*y;
> 
>   I've seen some discussion regarding the need for a polyfit function in
> Scilab. The main argument against such a function is that it is unnecessary 
> since
> it is a particular case of the backslash division. This is true, but the above
> example shows that users' implementations are not always optimized, and as it
> is such a frequent problem, it would be nice to have a native polyfit (or 
> whatever
> it may be called) function.
> 
>   Regards,
> 
>   Federico Miyara
> 
> 
>   ___
>   users mailing list
>   users@lists.scilab.org 
>   https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLm
> Zy/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@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] ?==?utf-8?q? Scilab 6.1 too slow to list large vectors

[Clément David]

Hello Pierre,

FYI your reported issue is probably not related at all to the matrix printing 
in the console. The Xcos simulation engine is kind of a gateway from the Scilab 
interpreter point of view (like optim() for instance), let's keep them separate 
issues.

Thanks,

--
Clément 

> -Original Message-
> From: users  On Behalf Of Perrichon
> Sent: Tuesday, March 31, 2020 12:05 PM
> To: 'Users mailing list for Scilab' 
> Subject: Re: [Scilab-users] ?==?utf-8?q? Scilab 6.1 too slow to list large 
> vectors
> 
> Hello,
> 
> On another way, see bugzilla #16359 in Xcos
> 
> I've provided the program to ESI
> 
> Results :
> Xcos Scilab 5.5.2 :
> Durée de la simulation : 258.3 s
> 
> Xcos Sciab 6.1.0 :
> Durée de la simulation : 4353.4 s
> 
> Stack? Mallloc ?
> 
> Regards
> 
> 
> 
> Before printing, think about ENVIRONMENTAL responsabity
> 
> 
> -Message d'origine-
> De : users  De la part de Antoine Monmayrant
> Envoyé : mardi 31 mars 2020 11:55 À : Users mailing list for Scilab
>  Objet : Re: [Scilab-users] ?==?utf-8?q? Scilab 6.1 
> too
> slow to list large vectors
> 
> Hello,
> 
> I also ran some tests and it seems that the regression is clearly line-based: 
> ie the
> regression is worse for vector than for matrix because there more lines to 
> print
> to display a vector than a matrix of similar length.
> See my test code below.
> 
> 
> n1=300;
> n2=100;
> mat=rand(n1,n2);
> tn=[];
> 
> /* Ctrl+E the code below several times*/
> 
> tic
> mat // matrix
> //mat(:) // vector
> t=toc()
> tn=[tn,t];
> 
> disp('-')
> disp('N_run = '+string(length(tn)))
> disp('T='+string(mean(tn))+'+/-'+string(stdev(tn)));
> 
> 
> /*
> 6.0.2 matrix
> N_run = 20
> T=0.6392742+/-0.056698
> 1.6x slower  but plotting 4 values per line ie 4x less lines to plot than for 
> the
> matrix version
> 
> 6.1.0 matrix
> N_run = 10
> T=1.0335109+/-0.0317414
> 
> 6.0.2 vector mat(:)
> N_run = 20
> T=0.4943449+/-0.0662727
> 
> 6.1.0 vector mat(:)
> N_run = 10
> T=3.800698+/-0.1121251
> 7.7x slower ie same slow down per line than for the vector version as we plot 
> 4
> values per line so 4x more lines
> 
> */
> 
> 
> 
> Le Mardi, Mars 31, 2020 11:36 CEST, Federico Miyara
>  a écrit:
> 
> >
> > Stéphane,
> >
> > I simplified and diversified the test:
> >
> > tic
> > u = rand(100,1000)
> > toc
> >
> > takes
> > 16 s in 6.1
> > 10 s in 6.0.2
> >
> > tic
> > u = u(:)'
> > toc
> >
> > takes
> > 66 s in 6.1
> > 1.29 s in 6.0.2
> >
> > tic
> > u = u(:)
> > toc
> >
> > takes
> > 107 s in 6.1
> > 1.52 s in 6.0.2
> >
> > tic
> > u = matrix(u,1000,100)
> > toc
> >
> > takes
> > 16 s in 6.1
> > 10 s in 6.0.2
> >
> > tic
> > u = matrix(u,100, 100, 10)
> > toc
> >
> > takes
> > 0.5 s in 6.1
> > 0.5 s in 6.0.2
> >
> > Seems as if vertical (many line feeds) print took more time than
> > horizontal print.
> >
> > Regards,
> >
> > Federico Miyara
> >
> >
> >
> > On 31/03/2020 05:23, Stéphane Mottelet wrote:
> > >
> > > Hi Frederico,
> > >
> > > Thanks for reporting. Can you test if the regression also holds for
> > > matrices ?
> > >
> > > S.
> > >
> > > Le 30/03/2020 à 11:56, Federico Miyara a écrit :
> > >>
> > >> Fs  =  44100
> > >> T  =  2.5
> > >> t  =  [0:T*Fs]/Fs;
> > >> ximp  =  exp(-t/0.3).*rand(t,"normal")  +  0.004*rand(t,"normal");
> > >>
> > >> tic
> > >> ximp  =  ximp(:)
> > >> toc
> > > --
> > > Stéphane Mottelet
> > > Ingénieur de recherche
> > > EA 4297 Transformations Intégrées de la Matière Renouvelable
> > > Département Génie des Procédés Industriels Sorbonne Universités -
> > > Université de Technologie de Compiègne CS 60319, 60203 Compiègne
> > > cedex Tel : +33(0)344234688 http://www.utc.fr/~mottelet
> > >
> > > ___
> > > users mailing list
> > > users@lists.scilab.org
> > > http://lists.scilab.org/mailman/listinfo/users
> >
> 
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
> 
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] ?= ?==?utf-8?q? New function for scilab to matlab conversio

[Clément David]

Hello Antoine,

Don't worry to iterate on the codereview, this is the way to go to add simple 
function like pol2cart. Even if you are using git, this is not the final git 
log until validation! 

About the sub-directory (eg. module) to put your macro into, I suggest you use 
"elementary_functions":
 1. Put the pol2cart.sci file into SCI/modules/elementary_functions/macros
 2. Put the pol2cart.xml English help page into 
SCI/modules/elementary_functions/help/en_US/trigonometry
 3. Put the pol2cart.tst unit test file into 
SCI/modules/elementary_functions/tests/unit_tests/

And that's it for the files! For the review, git add the new files and git push 
to the codereview.

Note: creating a dedicated ATOMS toolbox will involve more work 
Note2: a default xml help file could be generated from Scilab code comments 
using help_from_sci()

--
Clément

> -Original Message-
> From: users  On Behalf Of Antoine
> Monmayrant
> Sent: Monday, March 16, 2020 5:07 PM
> To: Users mailing list for Scilab 
> Subject: Re: [Scilab-users] ?==?utf-8?q? ?==?utf-8?q? ?= New function for 
> scilab
> to matlab conversio
> 
> Clément,
> 
> I had a look at gerrit, it's a bit overwhelming.
> I don't want to add unnecessary noise to the git log.
> I am not even sure about:
> (1) the number / nature of the files I am supposed to make. So far, I though
> about:
>   - the macro itself 'pol2cart.sci'
>   - the xml file to describe the help page 'pol2cart.xml'
>   - some test files.
> (2) the hierarchical structure of the contribution: which file goes where.
> 
> If any of you can share any piece of advice about the two points above, I'll
> appreciate greatly.
> 
> Do you think making a dumb atoms module around this simple function could
> help me get all the required files and sorted as expected?
> 
> Antoine
> 
> Le Mardi, Mars 10, 2020 10:43 CET, Clément David  group.com> a écrit:
> 
> > > > If yes, for small changes like pol2cart(), you could simply push the 
> > > > macro,
> the
> > > help page and a unit test ; we will then start the discussion on the code 
> > > and
> > > merge it. For more important changes (multiple functions, modules, Scilab
> > > global behavior, etc...) it should be good to write a SEP for better, 
> > > long-term,
> > > information.
> > > >
> > >
> > > That makes sense.
> > > Is there any wiki/doc documenting the whole process?
> >
> > No, not really, there are some pages on the wiki but it slightly depends on 
> > the
> kind of function you developed. As we validate the commits with a review, the
> codereview let us iterate and discuss changes very easily.
> >
> > --
> > Clément
> > ___
> > users mailing list
> > users@lists.scilab.org
> > http://lists.scilab.org/mailman/listinfo/users
> >
> 
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] ?==?utf-8?q? New function for scilab to matlab conversion

[Clément David]

> > If yes, for small changes like pol2cart(), you could simply push the macro, 
> > the
> help page and a unit test ; we will then start the discussion on the code and
> merge it. For more important changes (multiple functions, modules, Scilab
> global behavior, etc...) it should be good to write a SEP for better, 
> long-term,
> information.
> >
> 
> That makes sense.
> Is there any wiki/doc documenting the whole process?

No, not really, there are some pages on the wiki but it slightly depends on the 
kind of function you developed. As we validate the commits with a review, the 
codereview let us iterate and discuss changes very easily.

--
Clément
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] New function for scilab to matlab conversion

[Clément David]

Hi Antoine,

Did you already setup a git repository and its pushurl to codereview.scilab.org 
? If not, please follow https://wiki.scilab.org/gerrit .

If yes, for small changes like pol2cart(), you could simply push the macro, the 
help page and a unit test ; we will then start the discussion on the code and 
merge it. For more important changes (multiple functions, modules, Scilab 
global behavior, etc...) it should be good to write a SEP for better, 
long-term, information.

Note: I did not look for any equivalent function but it looks strange to me to 
not already have it.

Thanks,

--
Clément 

> -Original Message-
> From: users  On Behalf Of Antoine
> Monmayrant
> Sent: Tuesday, March 10, 2020 9:32 AM
> To: Users mailing list for Scilab 
> Subject: [Scilab-users] New function for scilab to matlab conversion
> 
> Hi all,
> 
> I am trying to convert some old matlab code to scilab.
> Running m2sci, I noticed that some simple functions were not available in 
> scilab
> (pol2car for example).
> I just did a small clean-room reimplementation of pol2car and tested on the
> official examples that it behaves like the matlab one.
> (nothing fancy at all!).
> 
> Here are my questions:
> (1) Is there any official way to propose the addition of pol2car to scilab ? 
> (Not
> sure this is worth a SEP)
> (2) Is there some official coding style or additional test that I should 
> provide?
> 
> Thank you in advance,
> 
> Antoine
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] ?==?utf-8?q? Which module to use for hassle-free image processing with scilab ?

[Clément David]

About the feature set, I suggest you take a look at SIVP which is much more 
complete and target a wider audience. The available functions are the 
documented ones and we might add more if customers requested more.

Currently, this toolbox is used by some customers and we only mapped the 
feature requested by them to have an associated minimal OpenCV build. It 
targets customers and we will probably not open-source it as we don’t want to 
maintain it “for free”. Again if you want to co-develop, take a look at SIVP ; 
Chin Luh did a good job and it is open-source !

Regards,

Clément


From: users  On Behalf Of Antoine Monmayrant
Sent: Monday, March 9, 2020 2:34 PM
To: Users mailing list for Scilab 
Subject: Re: [Scilab-users] ?==?utf-8?q? Which module to use for hassle-free 
image processing with scilab ?


Hello Clément,

Thanks for your answer.
It's still not clear to me whether I should use scicv or not.
First, many features are missing and it's not clear to me how I can implement 
or discover them (hough transforms for example).
Is there a list of the opencv functions that you expose through swig and the 
one that are not implemented?

Also, I'm a bit surprised by your statement:

Note: the code is not open-source but SWIG for Scilab and OpenCV are!
Why is it not open-source?
Is this some transient situation due to the way the code was developped (like 
for a client)?
Do you plan to make it open source in the near future?
For many reasons and lots of lessons learned the hard way, I don't feel like 
investing my time on non open-source software...

Antoine



Le Lundi, Mars 09, 2020 10:52 CET, Clément David 
mailto:clement.da...@esi-group.com>> a écrit:

Hello Antoine,

> - scicv: installs without any issue and as reported by Samuel (
> http://forge.scilab.org/index.php/p/scicv/issues/1944/
> http://forge.scilab.org/index.php/p/scicv/issues/1946/ ), overwrites 'write' 
> and
> 'read' which breaks many native functions in scilab together with other useful
> modules (ie uman). This is a blocking issue that has not been fixed in the 
> past 6
> months. Moreover, many opencv functions are not available and it is not clear
> how to access them.

About sciCV, the idea was to use SWIG [1] and OpenCV [2] as an easy to use (and 
simple to develop) toolbox for manipulating images and videos using Scilab 
scripts. Here we don't have Scilab scripts at all, just a bunch of SWIG rules 
to generate the Scilab C gateways from the OpenCV C API. We have a focus on 
keeping the data in the OpenCV world and "accessing" them from Scilab.

The two reported bugs have been fixed in 0.5 (sorry I did not close them) and 
the latest 0.6 version is built for Scilab 6.1.0 after a customer request.

Note: the code is not open-source but SWIG for Scilab and OpenCV are!


--
Clément
___
users mailing list
users@lists.scilab.org<mailto:users@lists.scilab.org>
http://lists.scilab.org/mailman/listinfo/users



___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Which module to use for hassle-free image processing with scilab ?

[Clément David]

Hello Stéphane,

>> We have a focus on keeping the data in the OpenCV world and "accessing" them 
>> from Scilab.
> 
> IMHO this is very confusing for people migrating image processing applications
> from Matlab (this is my case). For example, accessing rgb images directly as
> (n,m,3) hypermatrices are very handy.

The extraction/insertion should be handled correctly as well as converting 
n,m,3 uint8 back to OpenCV Mat images. Do you have a specific code sample that 
fail?

Thanks for your input,

--
Clément


___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Which module to use for hassle-free image processing with scilab ?

[Clément David]

Hello Antoine,

> - scicv: installs without any issue and as reported by Samuel (
> http://forge.scilab.org/index.php/p/scicv/issues/1944/
> http://forge.scilab.org/index.php/p/scicv/issues/1946/ ), overwrites 'write' 
> and
> 'read' which breaks many native functions in scilab together with other useful
> modules (ie uman). This is a blocking issue that has not been fixed in the 
> past 6
> months. Moreover, many opencv functions are not available and it is not clear
> how to access them.

About sciCV, the idea was to use SWIG [1] and OpenCV [2] as an easy to use (and 
simple to develop) toolbox for manipulating images and videos using Scilab 
scripts. Here we don't have Scilab scripts at all, just a bunch of SWIG rules 
to generate the Scilab C gateways from the OpenCV C API. We have a focus on 
keeping the data in the OpenCV world and "accessing" them from Scilab.

The two reported bugs have been fixed in 0.5 (sorry I did not close them) and 
the latest 0.6 version is built for Scilab 6.1.0 after a customer request.

Note: the code is not open-source but SWIG for Scilab and OpenCV are!

--
Clément
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Xcos 6.1.0 - benchmark time test

[Clément David]

Hello Pierre,

Thanks for the numbers, I will try to describe what can be down to work around 
the time to results.

>From when you start the simulation to the first scope popup, the schema is 
>converted to a list of functions to be called in a specific order and passed 
>to a solver that will iterate on time to "run" the simulation. There might be 
>a difference between Scilab 5 and Scilab 6 as this transformation is written 
>using the Scilab language. It is the 5s to 95s ratio.

While the simulation is running, each block's simulation function is called a 
number of times. The solver/simulator/function API did not change between 
Scilab 5 and Scilab 6, this should perform the same way. However, some 
functions, especially sciblk2 and sciblk4 are  wrappers from C to Scilab 
functions and have been re-written to behave very differently. It is the 253s 
(258-5) to 4258s (4353-95) ratio (lower ratio but much more impact).

Could you please file a bug with some representative example (same number of 
blocks, similar Scilab function) for further investigation ?

Note: having "costly" sciblk2 and sciblk4 also highly depends on your schema, 
for example having them on a continuous loop will make the solver call them on 
each timestep.

Regards,

--
Clément

From: Perrichon 
Sent: Monday, March 2, 2020 11:09 AM
To: 'Users mailing list for Scilab' ; Clément David 

Subject: RE: [Scilab-users] Xcos 6.1.0 - benchmark time test

Hello Clément,

Yes, I have some function blocks and expression blocks.
Must I understand that I have to write CBLOCK for scilab function or scilab 
expression or both ?

Here are other results for a more complex project name PELT1

Time request : 100 s

Results :
Xcos Scilab 5.5.2 :
Durée de la simulation : 258.3 s

Xcos Sciab 6.1.0 :
Durée de la simulation : 4353.4 s

So the ratio is 16.8 for PELT1

Other information :

Scilab 5.5.2 : time between click go and first scope on the screen = 5 s

Scilab 6.1.0 : time between click go and first scope on the screen = 95 s

Ratio=19

...and I also have other projects more complex

Pelt1 is for 1 needle (2 positonning loop)
Perlt6 for 6 !!! (7 positonning loop)


BR


De : users 
mailto:users-boun...@lists.scilab.org>> De la 
part de Clément David
Envoyé : vendredi 28 février 2020 10:10
À : Users mailing list for Scilab 
mailto:users@lists.scilab.org>>
Objet : Re: [Scilab-users] Xcos 6.1.0 - benchmark time test

Hello Pierre,

Are you using a block with its simulation function implemented in Scilab? Any 
C/C++ implemented block might perform the same at simulation time.

In 6.0.2, implementing Xcos blocks using the Scilab language had some 
performance issues. In 6.1.0, I tried to speed up things a little bit by 
reusing some allocated data structure during simulation time [1] ; more work 
might still be needed here.

[1]: 
http://cgit.scilab.org/scilab/commit/?id=bfe4f25275dc0d889817d10b63e10c9a0641ef32

Regards,

--
Clément

From: users 
mailto:users-boun...@lists.scilab.org>> On 
Behalf Of Perrichon
Sent: Friday, February 28, 2020 8:51 AM
To: 'Users mailing list for Scilab' 
mailto:users@lists.scilab.org>>
Subject: [Scilab-users] Xcos 6.1.0 - benchmark time test

Hello,

Here I test a PELTON basic algorithm under xcos, and record with tic-toc the 
simulation real time.
These programs have been set for 120 s (scope)

Results :
Xcos Scilab 5.5.2 :
Durée de la simulation : 45.4 s

Xcos Sciab 6.1.0 :
Durée de la simulation : 65.2 s

So the ratio is 1.44 for a basic sheme

Any explaination ?
Can that be improved ?

BR



___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Context error in Xcos Scilab 6.1.0

[Clément David]

Hello Pierre, Samuel,

First, did you opened a bug on that issue?

Second, to me, the bug is located on the script2var() function which resolves 
the context and output a struct of `variable=value` that are defined for the 
diagram (and its parents). For example, when I explicitly define A=100 in the 
context, the A variable is found and resolved as 100 in the diagram. However, 
defining A=50 inside the A.ctx file and using the schema A610.zcos, where the 
A.ctx file is passed to exec(), failed.

Regards,

--
Clément

> -Original Message-
> From: users  On Behalf Of Perrichon
> Sent: Saturday, February 29, 2020 7:35 PM
> To: 'Users mailing list for Scilab' 
> Subject: Re: [Scilab-users] Context error in Xcos Scilab 6.1.0
> 
> Hello Samuel,
> 
> 
> 
> Glad to see you confirm this bug
> 
> 
> 
> Context is executed at line 26 of the A.sce file, and not before :
> 
> ---> xcos_simulate(scs_m, 4);
> 
> 
> 
> So in scilab 6.1.0, the A.ctx is executed.
> 
> I also add in A610.zcos the instruction
> 
> * mprintf("Running context in xcos. ...So A=%i\n",A)
> 
> 
> 
> And then here is the track in my PC when running A.sce in xcos 6.1.0 :
> 
> 
> 
> 
> 
> --> exec('C:\0 - tampon\A.sce', -1)
> 
> Chargement du contexte d'exécution A.ctx
> 
> 
> 
> Running context in xcos. ...So A=50
> 
> 
> 
> Where we can see that A=50 inside A610.zcos.
> 
> 
> 
> We also can see that A is lost a the end of the context execution
> 
> 
> 
> 
> 
> This bad behavior also explains that my projects don't migrate from xcos 5.5.2
> to 6.1.0
> 
> 
> 
> Be sure that in my projects, the ct xis a set of a lot of scilab instructions 
> who
> generate variables.
> 
> These variables are use in any bloscks and under blocks of my main shemes
> 
> 
> 
> 
> 
> BR
> 
> 
> 
> 
> 
> De : users  De la part de Samuel Gougeon
> Envoyé : samedi 29 février 2020 17:53 À : users@lists.scilab.org Objet : Re:
> [Scilab-users] Context error in Xcos Scilab 6.1.0
> 
> 
> 
> Le 29/02/2020 à 17:41, Samuel Gougeon a écrit :
> 
>   Hello Pierre,
> 
> 
> 
>   Le 29/02/2020 à 11:32, Perrichon a écrit :
> 
>   Hello,
> 
> 
> 
>   I try to understand and find a reason why my projects done with
> xcos scilab 5.5.2 not run i 6.1.0
> 
>   So I isolate at least one reason in a basic test program (see
> attached files)
> 
> 
> 
>   Here, zcos file are lunched into scilab 5.5.2 or 6.10, with the
> A.sce file which test the version
> 
> 
> 
>   A.ctx is a context file. Here is a simple variable definition 
> A=50
> in that case.
> 
> 
> 
>   Every zcos file contains in its simulation contexte, the
> instruction « exec("A.ctx") » ; accessible with simulation-> context modifying
> 
> 
> 
>   To run this program, make a directory, a copy of the attached
> files, and change eventually line 4 in A.sce :
> 
>   Root="c:\0 - tampon"
> //
> Répertoire de travail pour le test
> 
> 
> 
>   So run A.sce inside xcos scilab 5.5.2 or 6.1.0
> 
> 
> 
>   Scilab 5.5.2 run correctly :
> 
>   
> 
> 
> 
> 
>   Scilab 6.1.0 is bugged :
> 
> 
> 
> 
> 
>   Apparently, the problem is that the context is not executed when the
> diagram is loaded.
>   Despite what the context message indicates:
> 
> 
> 
>   Indeed, the message mprintf("Chargement du contexte d''exécution
> %s\n\n",FichierContexte)
>   set in the context is not displayed when the diagram is loaded in 6.1.0 
> ;
> only when the context
>   is updated (or simply edited and revalidated).
> 
>   With Scilab 5.5, the context is not executed when loading the
> diagram,but when running it.
> 
>   So, to me, there are apparently 2 issues:
> 
>   1.  The Set Context message should be fixed: "... and every time
> the diagram is run" (not loaded)
>   2.  The fact that the context is executed when the diagram is run
> should be restored in Scilab 6.
> 
> Sorry, i don't know what occurred with my first trial, but now it works:
> In 6.0.2 and 6.1.0, the message is well displayed when the diagram is run.
> The error message displayed on the icon is the following:
> 
> 
> 
> 
> 
> Samuel
> 
> 

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Xcos 6.1.0 - benchmark time test

[Clément David]

Hello Pierre,

Are you using a block with its simulation function implemented in Scilab? Any 
C/C++ implemented block might perform the same at simulation time.

In 6.0.2, implementing Xcos blocks using the Scilab language had some 
performance issues. In 6.1.0, I tried to speed up things a little bit by 
reusing some allocated data structure during simulation time [1] ; more work 
might still be needed here.

[1]: 
http://cgit.scilab.org/scilab/commit/?id=bfe4f25275dc0d889817d10b63e10c9a0641ef32

Regards,

--
Clément

From: users  On Behalf Of Perrichon
Sent: Friday, February 28, 2020 8:51 AM
To: 'Users mailing list for Scilab' 
Subject: [Scilab-users] Xcos 6.1.0 - benchmark time test

Hello,

Here I test a PELTON basic algorithm under xcos, and record with tic-toc the 
simulation real time.
These programs have been set for 120 s (scope)

Results :
Xcos Scilab 5.5.2 :
Durée de la simulation : 45.4 s

Xcos Sciab 6.1.0 :
Durée de la simulation : 65.2 s

So the ratio is 1.44 for a basic sheme

Any explaination ?
Can that be improved ?

BR



___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Xcos Editor in Scilab 6.1.0 breaks diagrams

[Clément David]

Hello Pierre,

Could you please open a Bugzilla report with the attached diagram, Scilab/Xcos 
5.5.2 might set some positions incorrectly decoded in Scilab/Xcos 6.1.0 ?

Thanks,

--
Clément

> -Original Message-
> From: users  On Behalf Of Perrichon
> Sent: Thursday, February 27, 2020 7:35 PM
> To: 'Users mailing list for Scilab' 
> Subject: [Scilab-users] Xcos Editor in Scilab 6.1.0 breaks diagrams
> 
> Hello,
> 
> 
> 
> Xcos Editor in Scilab  6.1.0 breaks  diagrams. Number of failure is big.
> 
> Must I understand I've to rewrite all my projects in Scilab 6.1.0.
> 
> 
> 
> Here is an example (with  several minus zooms)
> 
> The big box in simply a MUX in the standard Palette, normaly drawn at the
> bottom of this diagram
> 
> 
> 
> Must I write a bugzilla ?
> 
> 
> 
> Best regards
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Personnal Palette : black component using drag and drop - Scilab 6.1.0

[Clément David]

Hello Pierre,

I confirmed it is a bug, setting the graphics.style of a block is supposed to 
work when allocating a block (on the "define" part of a block).

Thanks for the report,

--
Clément

> -Original Message-
> From: users  On Behalf Of Perrichon
> Sent: Wednesday, February 26, 2020 12:19 PM
> To: 'Users mailing list for Scilab' 
> Subject: [Scilab-users] Personnal Palette : black component using drag 
> and drop
> - Scilab 6.1.0
> 
> Hello
> 
> 
> 
> Using my personnal palette, I see that drag and drop a component in an 
> xcos screen is not drawn with Scilab 6.1.0
> 
> 
> 
> See bugzilla # for attached file "Photo of the Bug"
> 
> 
> 
> It was fine with scilab 5.5.2
> 
> 
> 
> So what to do in the  -case "define"- part of the sci files? See the 
> sci attached file
> 
> 
> 
> And why does it happen???
> 
> 
> 
> 
> 
> Best regards
> 
> Pierre P.
> 
> 
> 
> 

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] several problems with xcos scilab 6.1.0

[Clément David]

Hello Pierre,

This change was introduced 6 months ago and is coherent to the default scope 
window for a beginner. This is the default settings that apply only to any new 
schema, for any saved Xcos diagram the previous value should be preserved; if 
not please report a bug.

Note: while investigating your issue, I tested the Xcos preferences and it 
failed to set up a default final simulation time; this is a bug reported at 
http://bugzilla.scilab.org/show_bug.cgi?id=16336

Regards,

--
Clément

From: users  On Behalf Of Perrichon
Sent: Tuesday, February 25, 2020 5:04 PM
To: 'Users mailing list for Scilab' 
Subject: Re: [Scilab-users] several problems with xcos scilab 6.1.0

For Kaplan turbine time simulation is 600s at least. Why the default time is 30 
s ? Please program it at + infinity  that is 1000 s.


De : Perrichon mailto:perrichon.pie...@wanadoo.fr>>
Envoyé : mardi 25 février 2020 16:57
À : 'Users mailing list for Scilab' 
mailto:users@lists.scilab.org>>
Objet : several problems with xcos scilab 6.1.0

Hello,
Even if it is minor, apparently somebody has decided to define the time 
simulation to 30 s by default. Why ? I don't know
Before, it was 1.0E05 s and I stop the simulation with the END box in my main 
scheme. (to avoid user to go on this menu and choose another solver, at least). 
(choose is Newton for me , so the default one)
So I've hundred shemes to see

And this is not the first surprise.

Others tests don't work anymore

I can do tests to correct that, but it was not foreseen.

I still believe to go on with 6.1.0 but keep aware because not so clear with 
xcos

Pierre P.



___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Scilab 6.1.0 is available!

[Clément David]

Hello Heinz,

The macOS version is still in progress, we don't have any access to a macOS 
machine anymore and there are hard issues reported by Stephane (a hard crash in 
GUI mode, the required JVM installation, a non-signed packaging, at least...). 
So yes, we rely on the community (and especially Stephane) to ship a macOS 
binary; if you are willing to help, please contact him and keep in mind that it 
is a very complex task.

Note: this was also the case for Scilab 6.0.0 to 6.0.2.

Regards,

--
Clément

> -Original Message-
> From: Heinz Nabielek 
> Sent: Tuesday, February 25, 2020 4:52 PM
> To: Users mailing list for Scilab ; Clément David
> 
> Cc: List dedicated to the development of Scilab 
> Subject: Re: [Scilab-users] Scilab 6.1.0 is available!
> 
> And where is the Mac version?
> Heinz
> 
> 
> 
> 
> > On 25.02.2020, at 14:10, Clément David 
> wrote:
> >
> > Dear Scilab-ers,
> >
> > A brand new Scilab 6.1.0 is released today!
> >
> > This version includes further improvement atop Scilab 6.0 for better 
> > stability
> and increased algorithm performance. It also includes a reworked display for
> more compact and meaningful value printing; web tools for HTTP, JSON support;
> better debug support and various algorithm rewrite/extension.
> >
> > This first iteration of the 6.1 branch fixes up to 245 bugs and implements
> missing features from the 6.0.2 version. We would like to give a special 
> thanks
> to Samuel and Stephane who have been very active this year.
> >
> > If you find any critical issue or instability that might need a 6.1.x 
> > release please
> alert us. If you are a toolbox maintainer, please rebuild your code, upgrade 
> it
> when needed and publish it to atoms.scilab.org.
> >
> > For the complete list of changes and bugs fixed, please take a look at the
> CHANGES  file.
> >
> > --
> > Clément on behalf of the Scilab team
> > ___
> > users mailing list
> > users@lists.scilab.org
> > http://lists.scilab.org/mailman/listinfo/users

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

[Scilab-users] Scilab 6.1.0 is available!

[Clément David]

Dear Scilab-ers,



A brand new Scilab 6.1.0 is released 
today!



This version includes further improvement atop Scilab 6.0 for better stability 
and increased algorithm performance. It also includes a reworked display for 
more compact and meaningful value printing; web tools for HTTP, JSON support; 
better debug support and various algorithm rewrite/extension.



This first iteration of the 6.1 branch fixes up to 245 bugs and implements 
missing features from the 6.0.2 version. We would like to give a special thanks 
to Samuel and Stephane who have been very active this year.



If you find any critical issue or instability that might need a 6.1.x release 
please alert us. If you are a toolbox maintainer, 
please rebuild your code, upgrade it when needed and publish it to 
atoms.scilab.org.



For the complete list of changes and bugs fixed, please take a look at the 
CHANGES  file.



--

Clément on behalf of the Scilab team
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] [EXTERNAL] Count specific values in text file

[Clément DAVID]

Hi all,

Nice challenge, I have a simple answer to display an histogram (with 10
classes) of the PI digits stored in a pi.txt file (without any dot
separator):

F="pi.txt";
fd = mopen(F, 'r');
histplot(ascii(strcat(string(0:9))), mget(fileinfo(F)(1), "c", fd));
mclose(fd);

The idea is to read the file using mget() and store each ascii value into a
vector. These data are plot as a histogram of "0" to "9" ascii value.

--
Clément



--
Sent from: 
http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Still available memory on the Java heap

[Clément David]

Hello Samuel,

You can get memory information from the JVM using JIMS:

--> jimport java.lang.Runtime

--> Runtime.getRuntime().totalMemory()
 ans  =

  249036800


--> Runtime.getRuntime().freeMemory()
 ans  =

  175335480

Regards,

--
Clément DAVID

> -Original Message-
> From: users  On Behalf Of Samuel Gougeon
> Sent: Thursday, July 18, 2019 11:21 AM
> To: International users mailing list for Scilab. 
> Subject: [Scilab-users] Still available memory on the Java heap
> 
> Hello,
> 
> Is there a way equivalent to getmemory() to get the free memory on the
> reserved Scilab java heap?
> 
> xmlGetValues() can be used to get the total reserved java heap amount, but i
> would need to know the still free not yet used memory.
> 
> Thanks
> Samuel
> 
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Transition from Xcos 5.5 to 6.0

[Clément David]

Hello,

As we have ported our 5.5.2 files to 6.0.2 without issue, this is likely an 
issue within the zcos files you use. Could you please send these files (or 
report a bug and attach them) to check?

A potential issue might come from encoding, another by misrepresenting the 
diagram hierarchy (setting the wrong diagram root for exemple).

--
Clément

> -Original Message-
> From: users  On Behalf Of davegutz
> Sent: Tuesday, July 16, 2019 10:18 PM
> To: users@lists.scilab.org
> Subject: [Scilab-users] Transition from Xcos 5.5 to 6.0
> 
> Opening xcos drawn in 5.5.2 using 6.0.2 results in blank pages.
> 
> There are no special import functions I can find in the 6.0 help. There are no
> white papers I've found yet on the scilab website. I suspect that since
> 6.0 was a substantial rewrite that we need to substantially redraw our xcos
> diagrams to move from 5.5 to 6.0? Can anybody confirm?
> 
> I expected a v5.5x xcos diagram to open up in v6.0x, i.e. lots of block 
> diagrams
> and connectors. It is happily opened by v6.0.2 but it is blank except from 
> some
> annotations that got carried over.
> 
> I need a clue.
> 
> Thank you for your time.   Dave
> 
> 
> 
> --
> Sent from: http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-
> f2602246.html
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Saving

[Clément David]

Hello and welcome,

Scilab support a wide range of format (from the scripting language) but from my 
understanding you are asking for an autosave feature within Scinotes (the text 
editor) ? Yes, the text editor autosave each few minutes and this is 
configurable within the Preferences.

Thanks,

--
Clément

> -Original Message-
> From: users  On Behalf Of Tshego Masemola
> Sent: Friday, April 5, 2019 8:23 PM
> To: users@lists.scilab.org
> Subject: [Scilab-users] Saving
> 
> (Exercise 1.7)
> 
> In what format does Scilab save? Does it need to be saved continuously or is
> there an autosave option?
> 
> 
> 
> Regards,
> 
> Sana
> 
> 
> 
> Sent from Mail   for
> Windows 10
> 
> 
> 
> Disclaimer - University of Cape Town This email is subject to UCT policies and
> email disclaimer published on our website at http://www.uct.ac.za/main/email-
> disclaimer or obtainable from +27 21 650 9111. If this email is not related 
> to the
> business of UCT, it is sent by the sender in an individual capacity. Please 
> report
> security incidents or abuse via https://csirt.uct.ac.za/page/report-an-
> incident.php.
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Where is the Scilab source code and how one can contribute?

[Clément David]

Hi,

The Github repository is in read-only mode as our current infrastructure (git, 
gerrit, Bugzilla) provide similar services but cannot be synchronized easily 
with github issue and pull request services. Currently there is no plan to 
migrate to Github. If you prefer the Github flow, you could still fork, commit 
and push your changes ; I will be happy to import them into our codereview 
system.

Thanks,

--
Clément

> -Original Message-
> From: users  On Behalf Of Stéphane Mottelet
> Sent: Tuesday, April 2, 2019 11:55 PM
> To: users@lists.scilab.org
> Subject: Re: [Scilab-users] Where is the Scilab source code and how one can
> contribute?
> 
> Hi,
> 
> Have a look at this page:
> 
> https://wiki.scilab.org/gerrit
> 
> S.
> 
> Le 02/04/2019 à 23:46, farimani a écrit :
> > I was able to clone "a" source code using
> >
> > git clone git://git.scilab.org/scilab
> >
> > which I found here
> >
> >
> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/gitwe
> > b.scilab.org/?p=scilab.git;a=summary
> >
> > but I still don't know how I can send a pull request or if this is the
> > updated repository or a mirror.
> >
> > Moreover it seems that the GitHub repository
> >
> >
> https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/githu
> > b.com/scilab/scilab
> >
> > to be an official mirror as it appears in some documentations. However
> > many of the GitHub features have been deactivated including the issue
> request!
> >
> >
> >
> >
> >
> > -
> > Foad Sojoodi Farimani
> >
> > Twitter
> >
> https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/twitt
> > er.com/fsfarimani LinkedIn
> >
> https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/www
> .l
> > inkedin.com/in/fsfarimani/
> > --
> > Sent from:
> >
> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/maili
> > nglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html
> > ___
> > users mailing list
> > users@lists.scilab.org
> > https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists
> > .scilab.org/mailman/listinfo/users
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Check code on SCILAB``

[Clément David]

Hi Farimani,

You could check the syntax by "executing" the function definition while writing 
it. The interpreter will catch some simple syntax issues and redefine the 
function each time you execute it.

Using slint, might also help you to get more warnings.

--
Clément

-Original Message-
From: users  On Behalf Of farimani
Sent: Tuesday, March 12, 2019 7:20 PM
To: users@lists.scilab.org
Subject: Re: [Scilab-users] Check code on SCILAB``

I was wondering if there is any way to force the interpreter check all the 
syntax, including the ones inside the functions, while/for loops, if statement 
...?



--
Sent from: 
http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] scilab-branch-6.0 crashes when changing block parameters

[Clément David]

Hello Grzegorz,

Correct! There is some invalid read/write and memory leaks while using Xcos. 
There were some fixes already applied but still some work to do (see [1] for 
example). I will check your reported issue (double click on CLSS on windows 64) 
to check what is wrong. Thanks for your investigation, hope we will fix it for 
the release.

[1]: https://codereview.scilab.org/#/c/20796/

--
Clément

-Original Message-
From: users  On Behalf Of Grzegorz
Sent: Wednesday, February 6, 2019 12:59 PM
To: users@lists.scilab.org
Subject: [Scilab-users] scilab-branch-6.0 crashes when changing block parameters

Hello, 

I see that we are close to new Scilab release:) Thanks for your great work!

I've installed Scilab from 6.0 branch and having some problems with Xcos. It 
may be not an issue since 6.0 branch is still under development. Just letting 
you know :) 

Build #3904 of Revision f0a2a8124ad40c3d519fc5c8120bf5294fd38811 

When I use Xcos and e.g CLSS block, open its parameters and simply confirm with 
OK Scilab crashes.

After checking block code I've found that line with graphics object assignment 
crashes Scilab.

// code from Xcos block
.
graphics.exprs = exprs;
*x.graphics = graphics;*
x.model = model;


>From hs_err_pid11472.log I get

EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x50dad1cc, pid=11472, 
tid=0x32ac

Regards Grzegorz 





--
Sent from: 
http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] HDF5 save is super slow

[Clément DAVID]

> > Why is the code for structs (lines 242--74)  commented out ? Is it 
> > broken or else ?
> If var2vec() / vec2var() could be extended to provide a universal way to 
> serialize / deserialize really any scilab variable, that would be really nice.
> Could we make a SEP or fill a bug as a wish ?

Yep I have no problem to allocate a SEP for that, vec2var / var2vec might be 
used elsewhere but the format need to be documented for all managed types. 
Handle, for example, will probably not be stored at first. A SEP might even be 
good to define the real need for that "a Scilab variable dump for cheap and 
fast access" and to clearly state that this encoding might change across OS, 
hardware or Scilab versions.

Are you interested in writing it ?  

Thanks,

--
Clément
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] HDF5 save is super slow

[Clément DAVID]

Hello Stephane,

Probably commented out as we have no easy way to extract such data easily using 
only C constructs (from a Scicos block). It might be possible to uncomment and 
check the counterpart side (vec2var.cpp) to ensure it works correctly.

Thanks,

--
Clément 

-Original Message-
From: users  On Behalf Of Stéphane Mottelet
Sent: Thursday, October 18, 2018 3:01 PM
To: users@lists.scilab.org
Subject: Re: [Scilab-users] HDF5 save is super slow

Hello again,

Le 18/10/2018 à 14:56, Clément David a écrit :
> Hi Antoine,
>
> That one point, vec2var has been defined to pass some datatypes from Scilab 
> "ast" (C++ side, data pointers, refcounted) to Scilab "scicos" (C, raw memory 
> allocated once and passed around). Some data structures might not be handled 
> correctly, I was even surprised that mlists worked correctly.
>
> Scilab Struct (or Cell) are missing as they are more complex datatypes 
> to serialize. Handle are even harder (as you need to list the 
> properties somewhere). Feel free to take a look at the code [1],
>
> [1]: 
> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/cgit.
> scilab.org/scilab/tree/scilab/modules/scicos/src/cpp/var2vec.cpp?h=6.0
> #n243
Why is the code for structs (lines 242--74)  commented out ? Is it broken or 
else ?

> Cheers,
> --
> Clément
>
> -Original Message-----
> From: antoine monmayrant 
> Sent: Thursday, October 18, 2018 2:47 PM
> To: Clément DAVID ; Users 
> mailing list for Scilab 
> Cc: Clément David 
> Subject: Re: [Scilab-users] HDF5 save is super slow
>
>
>
> Le 18/10/2018 à 14:09, Clément DAVID a écrit :
>> Hello,
>>
>> My 2cents, this is probably a poor man’s approach but Xcos offers vec2var / 
>> var2vec functions that encode in a double vector any Scilab datatypes passed 
>> as arguments. The encoding duplicates the data in memory so there might be 
>> some overhead.
> Er, I tried var2vec, but it does not work with structures:
> --> typeof(t)
>    ans  =
>    st
>
> --> var2vec(t)
> var2vec: Wrong type for input argument #1: Double, Integer, Boolean, String 
> or List type.
>
> Arghh... so var2vec does not work for any datatype right?
>
> Antoine
>> On my machine, I have these timings using the attached script (Antoine’s one 
>> edited):
>> save list of syslins: 1.361704
>> save list of vec[]: 0.056788
>> save var2vec(list of syslins): 0.014411
>>
>> Discarding hdf5 groups creation is a huge performance win but remove any way 
>> to create clean hdf5 (eg. to address subgroups directly).
>>
>> Thanks,
>>
>> --
>> Clément
>>
>> From: users  On Behalf Of Arvid Rosén
>> Sent: Tuesday, October 16, 2018 1:01 PM
>> To: antoine.monmayr...@laas.fr; Users mailing list for Scilab 
>> 
>> Subject: Re: [Scilab-users] HDF5 save is super slow
>>
>> From: users
>> mailto:users-boun...@lists.scilab.org
>> >
>>> on behalf of "amonm...@laas.fr<mailto:amonm...@laas.fr>"
>> mailto:amonm...@laas.fr>>
>> Reply-To:
>> "antoine.monmayr...@laas.fr<mailto:antoine.monmayr...@laas.fr>"
>> mailto:antoine.monmayr...@laas.fr>>, 
>> Users mailing list for Scilab 
>> mailto:users@lists.scilab.org>>
>> Date: Tuesday, 16 October 2018 at 09:53
>> To: "users@lists.scilab.org<mailto:users@lists.scilab.org>"
>> mailto:users@lists.scilab.org>>
>> Subject: Re: [Scilab-users] HDF5 save is super slow
>>
>> Couldn't you create your own atom package that restore this raw memory dump 
>> for scilab 6.0?
>> I understand why we moved away from this model, but it seems to be key for 
>> you.
>> There is always a trade-off between portability (and robustness) and raw 
>> speed...
>>
>> Yeah, if that was possible, I would certainly do it. We already have a bunch 
>> of C/C++ binaries that we compile and link dynamically, but for that to be 
>> easy to implement, I guess the lists and structures need to be stored 
>> linearly in one consecutive chunk of memory. I don’t know if that is the 
>> case. Anyone? C++ integrations and gateways are very poorly documented at 
>> the moment.
>> Otherwise, I would need to do some recursive implementation, that handles a 
>> bunch of different object types. Sounds painful.
>>
>> Cheers,
>> Arvid
> ___
> users mailing list
> users@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@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] HDF5 save is super slow

[Clément DAVID]

Hello Stephane,

TL ;DR ; HDF5 is a cross-platform, cross-language, portable file format used in 
almost all scientific software these days. Please use this sane default !

Writing a custom serialization scheme (like the one provided by vec2var / 
var2vec) might not be complicated to implement however the hard part is 
maintaining and describing a serialization format to be used in the long term.

Using Scilab 5, the “stack” save and load functions were almost trivial as they 
are directly mapped from memory to disk; the format used is “the stack” so it 
is known and used everywhere (even for custom string encoding). This vec2var 
serialization is only used internally (to pass block parameters around), does 
not respect any described format nor validate against any documentation and is 
not portable; in the long term, I won’t promise it to be stable. Implementing 
your own serialization scheme will probably lead your software into trouble. 
Really, it isn’t easy in the long term! The HDF5 format is described, its 
serialized data are browsable (through hdfview) and does not cope with 
low-level requirements.

To me, the issue is really a performance bug. We might find a way to fix it 
within Scilab rather than provide a workaround (with custom encodings). The 
hdf5 library is a bug one, maybe with a clever understanding of its internal 
serialization, we might find a better execution path for this use-case (without 
changing the file format).

Thanks,

--
Clément

From: users  On Behalf Of Stéphane Mottelet
Sent: Thursday, October 18, 2018 2:39 PM
To: users@lists.scilab.org
Subject: Re: [Scilab-users] HDF5 save is super slow

Hello Clément,

Le 18/10/2018 à 14:09, Clément DAVID a écrit :
Hello,

My 2cents, this is probably a poor man’s approach but Xcos offers vec2var / 
var2vec functions that encode in a double vector any Scilab datatypes passed as 
arguments. The encoding duplicates the data in memory so there might be some 
overhead.
Do you think it would be complicated to continuously write the serialized data 
on the disk ?

On my machine, I have these timings using the attached script (Antoine’s one 
edited):
save list of syslins: 1.361704
save list of vec[]: 0.056788
save var2vec(list of syslins): 0.014411

Discarding hdf5 groups creation is a huge performance win but remove any way to 
create clean hdf5 (eg. to address subgroups directly).

Thanks,

--
Clément

From: users 
<mailto:users-boun...@lists.scilab.org> On 
Behalf Of Arvid Rosén
Sent: Tuesday, October 16, 2018 1:01 PM
To: antoine.monmayr...@laas.fr<mailto:antoine.monmayr...@laas.fr>; Users 
mailing list for Scilab <mailto:users@lists.scilab.org>
Subject: Re: [Scilab-users] HDF5 save is super slow

From: users 
mailto:users-boun...@lists.scilab.org>> on 
behalf of "amonm...@laas.fr<mailto:amonm...@laas.fr>" 
mailto:amonm...@laas.fr>>
Reply-To: "antoine.monmayr...@laas.fr<mailto:antoine.monmayr...@laas.fr>" 
mailto:antoine.monmayr...@laas.fr>>, Users mailing 
list for Scilab mailto:users@lists.scilab.org>>
Date: Tuesday, 16 October 2018 at 09:53
To: "users@lists.scilab.org<mailto:users@lists.scilab.org>" 
mailto:users@lists.scilab.org>>
Subject: Re: [Scilab-users] HDF5 save is super slow

Couldn't you create your own atom package that restore this raw memory dump for 
scilab 6.0?
I understand why we moved away from this model, but it seems to be key for you.
There is always a trade-off between portability (and robustness) and raw 
speed...

Yeah, if that was possible, I would certainly do it. We already have a bunch of 
C/C++ binaries that we compile and link dynamically, but for that to be easy to 
implement, I guess the lists and structures need to be stored linearly in one 
consecutive chunk of memory. I don’t know if that is the case. Anyone? C++ 
integrations and gateways are very poorly documented at the moment.
Otherwise, I would need to do some recursive implementation, that handles a 
bunch of different object types. Sounds painful.

Cheers,
Arvid




___

users mailing list

users@lists.scilab.org<mailto:users@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@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] HDF5 save is super slow

[Clément David]

Hi Antoine,

That one point, vec2var has been defined to pass some datatypes from Scilab 
"ast" (C++ side, data pointers, refcounted) to Scilab "scicos" (C, raw memory 
allocated once and passed around). Some data structures might not be handled 
correctly, I was even surprised that mlists worked correctly.

Scilab Struct (or Cell) are missing as they are more complex datatypes to 
serialize. Handle are even harder (as you need to list the properties 
somewhere). Feel free to take a look at the code [1],

[1]: 
http://cgit.scilab.org/scilab/tree/scilab/modules/scicos/src/cpp/var2vec.cpp?h=6.0#n243

Cheers,
--
Clément

-Original Message-
From: antoine monmayrant  
Sent: Thursday, October 18, 2018 2:47 PM
To: Clément DAVID ; Users mailing list 
for Scilab 
Cc: Clément David 
Subject: Re: [Scilab-users] HDF5 save is super slow



Le 18/10/2018 à 14:09, Clément DAVID a écrit :
> Hello,
>
> My 2cents, this is probably a poor man’s approach but Xcos offers vec2var / 
> var2vec functions that encode in a double vector any Scilab datatypes passed 
> as arguments. The encoding duplicates the data in memory so there might be 
> some overhead.
Er, I tried var2vec, but it does not work with structures:
--> typeof(t)
  ans  =
  st

--> var2vec(t)
var2vec: Wrong type for input argument #1: Double, Integer, Boolean, String or 
List type.

Arghh... so var2vec does not work for any datatype right?

Antoine
>
> On my machine, I have these timings using the attached script (Antoine’s one 
> edited):
> save list of syslins: 1.361704
> save list of vec[]: 0.056788
> save var2vec(list of syslins): 0.014411
>
> Discarding hdf5 groups creation is a huge performance win but remove any way 
> to create clean hdf5 (eg. to address subgroups directly).
>
> Thanks,
>
> --
> Clément
>
> From: users  On Behalf Of Arvid Rosén
> Sent: Tuesday, October 16, 2018 1:01 PM
> To: antoine.monmayr...@laas.fr; Users mailing list for Scilab 
> 
> Subject: Re: [Scilab-users] HDF5 save is super slow
>
> From: users 
> mailto:users-boun...@lists.scilab.org>
> > on behalf of "amonm...@laas.fr<mailto:amonm...@laas.fr>" 
> mailto:amonm...@laas.fr>>
> Reply-To: 
> "antoine.monmayr...@laas.fr<mailto:antoine.monmayr...@laas.fr>" 
> mailto:antoine.monmayr...@laas.fr>>, Users 
> mailing list for Scilab 
> mailto:users@lists.scilab.org>>
> Date: Tuesday, 16 October 2018 at 09:53
> To: "users@lists.scilab.org<mailto:users@lists.scilab.org>" 
> mailto:users@lists.scilab.org>>
> Subject: Re: [Scilab-users] HDF5 save is super slow
>
> Couldn't you create your own atom package that restore this raw memory dump 
> for scilab 6.0?
> I understand why we moved away from this model, but it seems to be key for 
> you.
> There is always a trade-off between portability (and robustness) and raw 
> speed...
>
> Yeah, if that was possible, I would certainly do it. We already have a bunch 
> of C/C++ binaries that we compile and link dynamically, but for that to be 
> easy to implement, I guess the lists and structures need to be stored 
> linearly in one consecutive chunk of memory. I don’t know if that is the 
> case. Anyone? C++ integrations and gateways are very poorly documented at the 
> moment.
> Otherwise, I would need to do some recursive implementation, that handles a 
> bunch of different object types. Sounds painful.
>
> Cheers,
> Arvid

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] HDF5 save is super slow

[Clément DAVID]

Hello,

My 2cents, this is probably a poor man’s approach but Xcos offers vec2var / 
var2vec functions that encode in a double vector any Scilab datatypes passed as 
arguments. The encoding duplicates the data in memory so there might be some 
overhead.

On my machine, I have these timings using the attached script (Antoine’s one 
edited):
save list of syslins: 1.361704
save list of vec[]: 0.056788
save var2vec(list of syslins): 0.014411

Discarding hdf5 groups creation is a huge performance win but remove any way to 
create clean hdf5 (eg. to address subgroups directly).

Thanks,

--
Clément

From: users  On Behalf Of Arvid Rosén
Sent: Tuesday, October 16, 2018 1:01 PM
To: antoine.monmayr...@laas.fr; Users mailing list for Scilab 

Subject: Re: [Scilab-users] HDF5 save is super slow

From: users 
mailto:users-boun...@lists.scilab.org>> on 
behalf of "amonm...@laas.fr" 
mailto:amonm...@laas.fr>>
Reply-To: "antoine.monmayr...@laas.fr" 
mailto:antoine.monmayr...@laas.fr>>, Users mailing 
list for Scilab mailto:users@lists.scilab.org>>
Date: Tuesday, 16 October 2018 at 09:53
To: "users@lists.scilab.org" 
mailto:users@lists.scilab.org>>
Subject: Re: [Scilab-users] HDF5 save is super slow

Couldn't you create your own atom package that restore this raw memory dump for 
scilab 6.0?
I understand why we moved away from this model, but it seems to be key for you.
There is always a trade-off between portability (and robustness) and raw 
speed...

Yeah, if that was possible, I would certainly do it. We already have a bunch of 
C/C++ binaries that we compile and link dynamically, but for that to be easy to 
implement, I guess the lists and structures need to be stored linearly in one 
consecutive chunk of memory. I don’t know if that is the case. Anyone? C++ 
integrations and gateways are very poorly documented at the moment.
Otherwise, I would need to do some recursive implementation, that handles a 
bunch of different object types. Sounds painful.

Cheers,
Arvid


sample.sce
Description: sample.sce
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] LIST ADMIN : Fwd: Non remis : Re: Unable to update ATOMS packages - Scilab 6.0.1

[Clément DAVID]

Hello Antoine,

Thanks, unsub-ed on the mailing list admin interface.

--
Clément

From: users  On Behalf Of 
antoine.monmayrant+sci...@laas.fr
Sent: Wednesday, October 17, 2018 8:47 AM
To: International users mailing list for Scilab. 
Subject: [Scilab-users] LIST ADMIN : Fwd: Non remis : Re: Unable to update 
ATOMS packages - Scilab 6.0.1


Hello,

Is there any admin of users@lists.scilab.org 
over here?
Could you deregister this email adress: 
ngro...@rms-signal.com .
I get an error message whenever I post something to 
users@lists.scilab.org and it's really annoying.

Thank you in advance,

Antoine


 Message transféré 
Sujet :

Non remis : Re: [Scilab-users] Unable to update ATOMS packages - Scilab 6.0.1

Date :

Wed, 17 Oct 2018 08:42:08 +0200

De :

postmas...@rms-sysma.fr

Pour :

amonm...@laas.fr



Échec de la remise pour ces destinataires ou groupes :

ngro...@rms-signal.com
L'adresse de messagerie que vous avez entrée est introuvable. Vérifiez 
l'adresse de messagerie du destinataire et essayez de renvoyer le message. Si 
le problème persiste, contactez le support technique de votre organisation.






Informations de diagnostic pour les administrateurs :

Serveur de génération : SERVEUR2012.ts.local

ngro...@rms-signal.com
Remote Server returned '550 5.1.1 RESOLVER.ADR.RecipNotFound; not found'

En-têtes de message d'origine :

Received: from SERVEUR2012.ts.local (192.168.13.2) by SERVEUR2012.ts.local

 (192.168.13.2) with Microsoft SMTP Server (TLS) id 15.0.847.32; Wed, 17 Oct

 2018 08:42:08 +0200

Received: from SERVEUR2012 (127.0.0.1) by SERVEUR2012.ts.local (127.0.0.1)

 with Microsoft SMTP Server id 15.0.847.32 via Frontend Transport; Wed, 17 Oct

 2018 08:42:08 +0200

Received: From ns0.ovh.net by SERVEUR2012 with POPtm; mer. 17 oct. 2018

 08:42:02

X-POPTM-SENDTO: ngro...@rms-signal.com

X-POPTM-BOXID: 1

Return-Path: 


Delivered-To: ngro...@rms-signal.com

Received: from localhost (HELO queue) (127.0.0.1)by localhost with SMTP; 17

 Oct 2018 08:39:22 +0200

Received: from unknown (HELO output55.mail.ovh.net) (10.108.97.112)  by

 mail150.ha.ovh.net with AES256-GCM-SHA384 encrypted SMTP; 17 Oct 2018

 08:39:22 +0200

Received: from vr49.mail.ovh.net (unknown [10.101.8.49]) by 
out55.mail.ovh.net

 (Postfix) with ESMTP id 42ZjFk5Wynz4fd8P for 
; Wed,

 17 Oct 2018 06:39:22 + (UTC)

Received: from in37.mail.ovh.net (unknown [10.101.4.37]) by 
vr49.mail.ovh.net

 (Postfix) with ESMTP id 42ZjFk4nYfz1vHlv for 
; Wed,

 17 Oct 2018 06:39:22 + (UTC)

Received-SPF: None (mailfrom) identity=mailfrom; client-ip=109.7.104.50; 
helo=corvo.scilab.org; 
envelope-from=users-boun...@lists.scilab.org;
 receiver=

Authentication-Results: in37.mail.ovh.net; dkim=none; dkim-atps=neutral

Received: from corvo.scilab.org (50.104.7.109.rev.sfr.net [109.7.104.50]) by

 in37.mail.ovh.net (Postfix) with ESMTPS id 42ZjFk4VSXzsBk7  for

 ; Wed, 17 Oct 2018 
06:39:22 + (UTC)

Received: by corvo.scilab.org (Postfix, from userid 999) id 61495126044; 
Wed,

 17 Oct 2018 08:38:46 +0200 (CEST)

X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on corvo.inria.fr

X-Spam-Level:

X-Spam-Status: No, score=-4.2 required=6.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,

SPF_PASS autolearn=unavailable version=3.3.2

Received: from corvo.inria.fr (localhost [IPv6:::1]) by corvo.scilab.org

 (Postfix) with ESMTP id 9649D1205CB; Wed, 17 Oct 2018 08:38:37 +0200 (CEST)

Received: by corvo.scilab.org (Postfix, from userid 999) id 730E81205CB; Wed,

 17 Oct 2018 08:38:25 +0200 (CEST)

Received-SPF: pass (laas.fr: 140.93.0.15 is authorized to use

 'amonm...@laas.fr' in 'mfrom' identity (mechanism 
'a:mail.laas.fr' matched))

 receiver=corvo.scilab.org; identity=mailfrom; 
envelope-from="amonm...@laas.fr";

 helo=laas.laas.fr; client-ip=140.93.0.15

Received: from laas.laas.fr (laas.laas.fr [140.93.0.15]) by corvo.scilab.org

 (Postfix) with ESMTPS id D901C1204B6 for 
; Wed, 17

 Oct 2018 08:38:12 +0200 (CEST)

Received: from [IPv6:2001:660:6602:4:6600:6aff:fe8b:a548] (tournois.laas.fr

 [IPv6:2001:660:6602:4:6600:6aff:fe8b:a548]) by laas.laas.fr

 (8.16.0.21/8.15.2) with ESMTPS id w9H6cBXe056744 (version=TLSv1.2

 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for

 ; Wed, 17 Oct 2018 
08:38:11 +0200 (CEST)

To: 

References: 

Re: [Scilab-users] HDF5 save is super slow

[Clément DAVID]

Hello all,

Correct, I experienced such a slowness while working with Xcos diagrams for 
Scilab 5. At first we considered HDF5 for this deep nested list / mlist 
data-structure storage however after some tests ; XML might be used for 
tree-like storage and HDF5 (or Java types serialization) for big matrices.

AFAIK currently there is no easy way to load/save specifying a format other 
than HDF5 ; maybe adding xmlSave/xmlLoad sci_gateway to let the user select an 
xml file format for any Scilab structure might provide better performance on 
your use-case. JSON might also be another candidate to look at for decent 
serialization support.

PS: Scilab 5.5.1 load/save are direct memory dump so this is really the fastest 
you can get from Scilab ; HDF5 binary format is good enough for matrices

--
Clément

From: users  On Behalf Of Stéphane Mottelet
Sent: Monday, October 15, 2018 2:36 PM
To: users@lists.scilab.org
Subject: Re: [Scilab-users] HDF5 save is super slow

Hello,

I looked a little bit in the sources: the evident bottleneck is the nested 
creation of an hdf5 group each time that a container variable is met.
For the given example, this is particularly evident. If you replace the syslin 
structure by the corresponding [A,B;C,D] matrix, then save is ten times faster:

N = 4;
n = 1000;
filters = list();
for i=1:n
  G=syslin('c', rand(N,N), rand(N,1), rand(1,N), rand(1,1));
  filters($+1) = G;
end
tic();
save('filters.dat', 'filters');
disp(toc());
--> disp(toc());

   0.724754

N = 4;
n = 1000;
filters = list()
for i=1:n
  G=syslin('c', rand(N,N), rand(N,1), rand(1,N), rand(1,1));
  filters($+1) = [G.a G.b;G.c G.d];
end
tic();
save('filters.dat', 'filters');
disp(toc());
--> disp(toc());

   0.082302

Serializing container objects seems to be the solution, but it goes towards an 
orthogonal direction w.r.t. the hdf5 portability spirit.

S.


Le 15/10/2018 à 12:22, Antoine Monmayrant a écrit :
Le 15/10/2018 à 11:55, Arvid Rosén a écrit :
Hi,

Thanks for getting back to me!

Unfortunately, we used Scilab’s pretty cool way of doing object orientation, so 
we have big nested tlist structures with multiple instances of various lists of 
filters and other structures, as in my example. Saving those structures in some 
explicit manual way would be extremely complicated. Or is there some way of 
writing explicit HDF5 saving/loading schemes using overloading? That would be 
great! I am sure we could find the main culprits and do something explicit for 
them, but as they can be located wherever in a big nested structure, it would 
be painful to do anything on the top level.

Another, related I guess, problem here is that the new file format uses about 
15 times as much disk space as the old format (for a typical ill-behaved nested 
structure). That adds to the save/load time too I guess, but is probably not 
the main source here.
Argh, yes, I tested it and in your example, I have a file x8.5 bigger.
I think that both increases in time and size are real issues and should be 
reported as bugs.

By the way, I rewrote your script to run it under both 6.0 and 5.5:

/
N = 4;
n = 1;
filters = list();

for i=1:n
  G=syslin('c', rand(N,N), rand(N,1), rand(1,N), rand(1,1));
  filters($+1) = G;
end

ver=getversion('scilab');

if ver(1)<6 then
tic();
save('filters_old.dat', filters);
ts1 = toc();
else
tic();
save('filters_new.dat', 'filters');
ts1 = toc();
end

printf("Time for save %.2fs\n", ts1);
/

Hope it helps,

Antoine



I think I might have reported this earlier using Bugzilla, but I’m not sure. 
I’ll check and report it if not.

Cheers,
Arvid

From: users 
 on 
behalf of "amonm...@laas.fr" 

Reply-To: "antoine.monmayr...@laas.fr" 
, Users mailing 
list for Scilab 
Date: Monday, 15 October 2018 at 11:08
To: "users@lists.scilab.org" 

Subject: Re: [Scilab-users] HDF5 save is super slow

Hello,

I tried your code in 5.5.1 and the last nightly-build of 6.0: I see a slowdown 
of around 175 between old save in 5.5.1 and new (and only) save in 6.0.
It's really related to the data structure, because we use hdf5 read/write a lot 
here and did not experience significant slowdowns using 6.0.
I think the overhead might come to the translation of your fairly complex 
variable (a long array of tlist) in the corresponding hdf5 structure.
In the old save, this translation was not necessary.
Maybe you could try to save your data in a different way.
For example:
3) you could save each element of "filters" in a separate file.
2) you could bypass save and directly write your data in a hdf5 file by using 
h5open(), h5write() directly. It means you need to write your own load() for 
your custom file 

Re: [Scilab-users] bugzilla.scilab.org is down

[Clément DAVID]

Hi all,

It seems OK to me now. Could you please recheck ? 
--
Clément

-Original Message-
From: users  On Behalf Of antoine monmayrant
Sent: Sunday, October 14, 2018 2:16 PM
To: users@lists.scilab.org
Subject: Re: [Scilab-users] bugzilla.scilab.org is down



Le 14/10/2018 à 09:49, Stéphane Mottelet a écrit :
> Hello
>
>> Le 14 oct. 2018 à 09:30, antoine monmayrant  a 
>> écrit :
>>
>> Hi all,
>>
>> bugzilla.scilab.org is down at the moment.
> codereview.scilab.org is also down.
>
atoms are also dead apparently: it must be some server issue at ESI.
We might have to wait Monday morning to see whether they can fix it.

Antoine
>
>> I checked and it seems that its not just me...
>> Can anyone fix this?
>>
>> Cheers,
>>
>> Antoine
>>
>> ___
>> users mailing list
>> users@lists.scilab.org
>> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
>

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Scilab takes forever to boot ... because of http://news.scilab.io/feed ???

[Clément DAVID]

Hello Antoine,

Yep there is a known bug #14592 that might trigger this kind of behavior. If 
you have custom hosts rules or a very restrictive firewall you will probably 
have some issues. 

Please comment on http://bugzilla.scilab.org/show_bug.cgi?id=14592 .

--
Clément

-Original Message-
From: users  On Behalf Of antoine monmayrant
Sent: Wednesday, September 19, 2018 3:20 PM
To: users@lists.scilab.org
Subject: Re: [Scilab-users] Scilab takes forever to boot ... because of 
http://news.scilab.io/feed ???



Le 19/09/2018 à 15:03, Stéphane Mottelet a écrit :
> Hi Antoine,
>
> I just tried to start teh latest Scilab-branch-6.0 build  after 
> deactivating my network connection and had the usual startup time. I 
> just have the following text appearing in the Newsfeed pane: " News 
> feed unavailable. "
Well, I just installed the latest nighly and managed to reproduce this bug at 
least once (ie on the first startup after install).
It seems that I cannot reach http://news.scilab.io/feed whereas my connection 
to other websites is OK.

Antoine
>
> S.
>
> Le 19/09/2018 à 14:55, antoine monmayrant a écrit :
>> Hi all,
>>
>> A recent nightly-build of scilab-6.0 just took more than a minute to 
>> start.
>> It seems due to a problem of connection to 
>> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/news
>> .scilab.io/feed
>> .
>> Here is the error I get on the terminal:
>>
>>     java.io.IOException: Server returned HTTP response code: 500 for
>> URL: 
>> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/news
>> .scilab.io/feed
>>
>> It raises 3 questions:
>>
>> 1) How do I disable this? Is closing the news feed docking window 
>> enough to prevent scilab from trying to connect to this server?
>>
>> 2) Am I this only one experiencing this problem?
>>
>> 3) Shouldn't this be considered a bug? Scilab should startup as fast 
>> possible even if there is a connection issue, right?
>>
>> Cheers,
>>
>> Antoine
>>
>> ___
>> users mailing list
>> users@lists.scilab.org
>> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/list
>> s.scilab.org/mailman/listinfo/users
>>
>
>

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] export to Excel with several sheets

[Clément DAVID]

Dear Paul,

XLS_link [1] could be used to interact with Excel. This basically offer you the 
Excel OLE Automation API inside Scilab [2] and let you drive an Excel runtime 
using Scilab functions. Drawbacks : it requires an Excel licence and is Windows 
only.

[1] : https://atoms.scilab.org/toolboxes/xls_link/
[2] 
https://support.microsoft.com/en-us/help/219151/how-to-automate-microsoft-excel-from-visual-basic

Thanks,

--
Clément

From: users  On Behalf Of Carrico, Paul
Sent: Monday, October 1, 2018 11:20 AM
To: International users mailing list for Scilab. (users@lists.scilab.org) 

Subject: [Scilab-users] export to Excel with several sheets

Dear All

I'm wondering if we can export matrixes from Scilab into Excel, in a single 
file but with several sheets? Obviously the csv format cannot be used here.

Not sure that the (quite old now) XLL project answers to it (I've not seen any 
doc)

Thanks

Paul


EXPORT CONTROL :
Cet email ne contient pas de données techniques
This email does not contain technical data

___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Scilab 6.0.1 extremely slow on new (high-end) laptop

[Clément DAVID]

Hello,

>From my knowledge, windows builds should be faster in the general case as the 
>MKL shipped with it has better optimizations (especially on Intel processors) 
>for numerical computing[1]. However, depending on your script there might be a 
>difference. For example, `host()` (process spawning) might be slower as it is 
>related to the way the OS work.

[1]: https://wiki.scilab.org/Linalg%20performances

Thanks,

--
Clément

-Original Message-
From: users  On Behalf Of Orbeaman
Sent: Saturday, September 29, 2018 11:54 AM
To: users@lists.scilab.org
Subject: [Scilab-users] Scilab 6.0.1 extremely slow on new (high-end) laptop

Hello,

I received my new laptop a few days ago and found out that Scilab 6.0.1 is
extremely slow. I would say that it takes about twice the time in comparison
to my previous laptop

- New laptop (available since since June 2018)
I9-8950HK GTX 1080 with 1 x 16GB RAM SSD RAID 0 Windows 10 Home Version 1803

- Old laptop (purcharsed in 2009)
I7-720QM GT 240M with 2 x 2GB RAM Linux 19.1 Mint

Basically, I would expect my new laptop to run Scilab much faster (it is
also almost 4 times more expensive).. I'm really disappointed!! Is it
possible that Scilab is not optimised for I9 CPU or Windows 10?

Does anyone encounter similar issues?

Many thanks 



--
Sent from: 
http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] ATOMS error (Scilab 6.0.1)

[Clément David]

Hello,

A server-side workaround have been implemented by using CRLF for the 
TOOLBOXES.gz windows files,
avoiding the mgetl() buggy behavior in 6.0.1

--
Clément

Le dimanche 22 juillet 2018 à 01:49 -0700, arctica1963 a écrit :
> Thanks for the update.
> 
> 
> 
> --
> Sent from: 
> http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] From Xcos model to DLL

[Clément David]

Hello Qian,

The most obvious solution is to use the Tools->Code generator that will 
generate C code for the
schema (the calls to the simulation functions) and using the simulation 
functions shipped with
Scilab (and freely available within Scilab source code).

If you want to target a specific hardware, the STM32 toolbox [1] (based on the 
same code generator)
will let you generate similar C code but optimized and with some blocks for 
hardware support !

[1]: https://atoms.scilab.org/toolboxes/xcos_stm32_toolbox

--
Clément

Le lundi 02 juillet 2018 à 15:58 -0700, qzhong a écrit :
> Dear all,
> 
> I am working on a controller model in Xcos which takes inputs from sensors
> and generates control decisions. The Xcos model has been built and compiled
> with no error. The issue I have is that I need to generate a .dll file from
> the Xcos model and use it in another simulation tool, similar to the process
> done in Simulink by the Real Time Workshop module. I am not quite sure
> whether similar packages exist for Scilab/Xcos. 
> 
> Does anyone have a similar experience when using Scilab/Xcos? Any comments
> would be much appreciated.
> 
> Qian
> 
> 
> 
> --
> Sent from: 
> http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Scilab Cloud App

[Clément David]

Hallo Jens,

Well, first the Scilab Cloud App service is not free, if you wish to test it 
please contact
t...@scilab.io !

A demonstation video is available as https://youtu.be/MaPKnUIEwoY ; as you 
might notice, the user
interaction is limited to uicontrol and plot management. There is no way to get 
the code out of the
web service if the application/toolbox/script does not allow that.

Technically speaking, this is not a web applet technology (Scilab running 
within the browser) but rather a 
web service technology (Scilab running within the cloud/servers).

Thanks,

--
Clément

Le samedi 23 juin 2018 à 19:53 +0200, Jens Simon Strom a écrit :
> Hallo,
> I happended to see the page Scilab Cloud App, and was attracted by the slogan 
> "Don’t waste your
> time in learning HTML/JS". 
> 
> I know web applets being availabe to the public via an URL and allowing some 
> mathematical
> calculations after some inputs. 
> 
> Given a functional Scilab script including a couple of functions, does the 
> associated Scilab Cloud
> App allow public acces to this script, when I publish the appropriate URL on 
> my webpage?
> Is there a Scilab Cloud App (any content is welcome) which I coud run as an 
> example?
> 
> Trying this one on Firefox lead to nothing.
> 
> 
> Kind regards
> Jens
>  ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Exclamation mark in variable names

[Clément David]

Hello,

Le dimanche 27 mai 2018 à 12:20 +0200, Samuel Gougeon a écrit :
> Le 27/05/2018 à 10:52, Jens Simon Strom a écrit :
> > Hi,
> > The `!` usage to recall a previous command is discussed here in detail. I 
> > don't miss it.  My
> > question was different.
>  
> I was answering to the "What's your opinion?" question by Clément.
> 
> Yes, i definitely agree on that both questions are completely independent, 
> and that since the fix
> for variables names is deemed easy, it should be applied ASAP and fastly made 
> available in the
> continuous built.

"Fixes Parser to Accept "!" in Variable Names
 " has been merged through
https://codereview.scilab.org/#/c/20069/ .

Thanks for your contribution !

--
Clément
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Exclamation mark in variable names

[Clément David]

Hi,

Thanks for your experimental work on that topic. I guess we could merge the 
parser fix easily
however the `!` usage to recall a previous command will remain problematic. 
This usage does not seem
to be documented somewhere in the help page, maybe we could discard it. What's 
your opinion on that
?

Thanks,

--
Clément

Le vendredi 25 mai 2018 à 01:17 -0700, Wozai a écrit :
> Hi,
> 
> I have had the same problem, and found a solution (at least if you build
> scilab by yourself), apply the following changes to the source and compile
> Scilab.
> 
> 1.  Changes Hotey "!" to ":" for Recalling History in Java Console
>   
> 
> 2.  Fixes Parser to Accept "!" in Variable Names
>   
> 
> Of course the downside of this fixing approach would be, that your code only
> works in "your" Scilab.
>  
> Cheers,
> 
> Wozai
> 
> 
> 
> 
> --
> Sent from: 
> http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] How to close/kill "messagebox"

[Clément David]

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, amonm...@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@lists.scilab.org
> > http://lists.scilab.org/mailman/listinfo/users
> > 
> 
> 
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Comments in a multiline literal array definition

[Clément David]

Hello Samuel,

This seems to be a regression on the parser, could you post a bug please ?

--
Clément

Le samedi 14 avril 2018 à 13:44 +0200, Samuel Gougeon a écrit :
> Hello,
> Before possibly posting a bug report, i would like to know if the following 
> change from Scilab
> 5.5.2 to 6.0.0 is an expected restriction, or an unexpected one -- so a bug.
> Scilab 5.5.2 accepts the following:
> -->a = [
> -->1  // line #1
> -->2, // line #2
> -->]
>  a  =
> 1.  
> 2.  
> while Scilab 6.0.0 does not:
> --> a = [
>   > 1 // line #1
>   > 2, // line #2
>   > ]
> 2, // line #2
>  ^
> Error: syntax error, unexpected line comment
> Please note that the appended comment passes if it does not follow a comma.
> And that an error is generated even if the last row does not end with a comma.
> --> a = [
>   > 1, // line #1
>   > 2]
> 1, // line #1
>  ^
> Error: syntax error, unexpected line comment
> 
> Regards
> Samuel
> 
> 
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] [SEP] [boolean integer_class] concatenations

[Clément David]

Hello Samuel,

Le dimanche 22 avril 2018 à 16:06 +0200, Samuel Gougeon a écrit :
> Le 17/04/2018 à 18:49, Samuel Gougeon a écrit :
> > Hello,
> > Surprisingly, as reported in http://bugzilla.scilab.org/15534, after 30 
> > years, Scilab still does
> > not know how to concatenate booleans with encoded integers.
> > For instance :
> > --> [%f int8(-3)]
> > 
> > Undefined operation for the given operands.
> > check or define function %b_c_i for overloading.
> > It is surprising, because 
> > For some languages like Octave, booleans are actually some numbers 
> > restricted to 0|1, and such
> > simple concatenations are available.
> > Implementing it in Scilab is trivial and does not really set any question, 
> > since both 0 and 1
> > are present in all Scilab integer classes.
> > An implementation is proposed for Scilab 6.1 (see the bugzilla report).
> > Comments are welcome.
>  
> No comments?
> 
> The only reason i have found to understand why this is still not implemented 
> would be to let the
> user define its own overloads. But which alternative to casting %f=>0 %t=>1 
> could we have?
> The first and may be only one we could imagine would be to cast integers into 
> booleans, as in
> [%t int8([0 -5])] => [%t %f %t]
> 
> Why not choosing this, instead of [%t int8([0 -5])] => int8([1 0 -5])?
> It's a poorer result, that can be obtained in a straightforward way as
> [%t int8([0 -5])]  =>  int8([1 0 -5])~=0

To me the whole remark is in the (still open) type conversion topic : promotion 
or coercion to
another type. Currently in Scilab most of the operations consume doubles and 
output doubles ; as
most of our users are not computer scientists I prefer to have promotion to 
double whenever possible
 as it is currently rather than complex type coercion rules per operations (see 
the current
implementation in modules/ast/src/cpp/operations).

For exemple, using your proposal I am not sure about user expectation on:

 [%f int8(-3)]
 [int8(0) %t]
 [%f 1.] // promotion to double !

Thanks,

--
Clément
 



___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Flatpak package

[Clément David]

Hello Martin,

Good idea ! I also have a first template of a Flatpak manifest with strong 
inspiration from the
Octave one [1] as dependencies are very similar. The bash script used to 
compile our thirdparties
[2] could also be a great source of inspiration.

For Eigen, the included files are prefixed like in `#include "Eigen/Eigen"`; 
you should probably
pass `--with-eigen-include=/app/include/` to make it work.

[1]: https://github.com/flathub/org.octave.Octave
[2]: 
https://github.com/scilab/scilab-prerequirements/blob/master/build-dependencies.sh

Regards,

--
Clément

Le mardi 03 avril 2018 à 21:37 +0200, Martin Marmsoler a écrit :
> Hello,
> 
> I'm trying to create a flatpak package of scilab. I try to compile scilab, 
> but I have a different
> folder where the Eigen files are stored. Because of this i get the following 
> error:
> 
> checking if Eigen is version 3.3.2 or later... configure: error: Version 
> 3.3.2 of Eigen expected
> (at least)
> 
> I tried to add the path with the with-eigen-include argument, but it does not 
> work:
> "./scilab/configure --prefix=/app --with-eigen-include=/app/include/Eigen",
> 
> is there anybody who know how I can add the path to the eigen .h files?
> 
> Here you can find the flatpak manifest. When it is finish I will put it on 
> github and create a
> pullrequest
> https://www.dropbox.com/sh/ezxzm748xs4a4jj/AAATpX_LACHp81hDUdEIz6y4a?dl=0
> 
> 
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] compilation with OCaml 4.06

[Clément David]

Hello Florian,

Please find attached a patch that fix this issue; it comes from a OCaml 4.0.4 
change which
distinguish String and Bytes implementations and the unsafe-string flag.

Quoting the documentation [1]:
> OCaml strings used to be modifiable in place, for instance via the String.set 
> and String.blit
> functions described below. This usage is deprecated and only possible when 
> the compiler is put 
> in "unsafe-string" mode by giving the -unsafe-string command-line option

[1]: https://caml.inria.fr/pub/docs/manual-ocaml/libref/String.html

Regards,

--
Clément

Le jeudi 22 février 2018 à 09:35 +0100, Florian Blachère a écrit :
> Hello Clément,
> 
> Thanks for the answer, I installed num and changed the compilation line to 
> use ocamlfind but now
> the compilation fails with : 
> 
> ocamlfind ocamlopt -package num -I ./src/modelica_compiler -I 
> ./src/xml2modelica -c
> src/modelica_compiler/optimization.ml
> File "src/modelica_compiler/optimization.ml", line 166, characters 21-22:
> Error: This expression has type string but an expression was expected of type
>  bytes
> 
> Is it link to the uodate to OCaml 4.06 ?
> 
> Florian
> 
> On 21/02/18 11:51, Clément David wrote:
> > Hello Florian,
> > 
> > The easier would be to depend on the external Num library for the 6.0.x 
> > family as far as this
> > library remains available; statically build against it is the way to go for 
> > OCaml code. Num
> > might
> > also be packaged in your system, use ocamlfind to look for it.
> > 
> > Thanks,
> > 
> > --
> > Clément
> > 
> > Le mercredi 21 février 2018 à 08:41 +0100, Florian Blachère a écrit :
> > > Hello,
> > > 
> > > Scilab 6.0.0 and 6.0.1 (and the master branch) cannot be build using 
> > > OCaml 4.06 because this release remove the Num library 
> > > (https://ocaml.org/releases/4.06.html#Changes class="Apple-tab-span" 
> > > style="white-space:pre">
> > >   , 
> > > https://github.com/ocaml/ocaml/pull/1178), do you have any advice to 
> > > build Scilab with recent OCaml: integrate Num in Scilab, build Num 
> > > oustside of Scilab and link against it, ... ?
> > > 
> > > Thanks by advance,
> > > 
> > > Florian
> > > 
> > > ___
> > > users mailing list
> > > users@lists.scilab.org
> > > http://lists.scilab.org/mailman/listinfo/users
> > 
> > ___
> > users mailing list
> > users@lists.scilab.org
> > http://lists.scilab.org/mailman/listinfo/users
> 
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/usersFrom 39662e94dca4d3c71ba0e7792de2d200f0ec7a08 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Cl=C3=A9ment=20DAVID?= <clement.da...@esi-group.com>
Date: Mon, 27 Mar 2017 17:45:41 +0200
Subject: [PATCH] Fix build with ocaml 4.0.4

Change-Id: I962fe026f1c44f7f76435db0b4838b0d936994c8
---
 scilab/modules/scicos/Makefile.in  | 12 ++---
 scilab/modules/scicos/Makefile.modelica.am |  2 +-
 scilab/modules/scicos/src/xml2modelica/linenum.mll | 56 --
 4 files changed, 11 insertions(+), 67 deletions(-)
 delete mode 100644 scilab/modules/scicos/src/xml2modelica/linenum.mll

Index: scilab-6.0.0/modules/scicos/src/modelica_compiler/optimization.ml
===
--- scilab-6.0.0.orig/modules/scicos/src/modelica_compiler/optimization.ml
+++ scilab-6.0.0/modules/scicos/src/modelica_compiler/optimization.ml
@@ -162,7 +162,7 @@ let num_of_float f =
   let num_of_positive_float f =
 let m, e = frexp f in
 let sm = string_of_float m in
-let s = String.make 16 '0' in
+let s = Bytes.make 16 '0' in
 String.blit sm 2 s 0 (String.length sm - 2);
 let e' = Num.power_num (Num.Int 2) (Num.num_of_int e) in
 Num.div_num (Num.mult_num (Num.num_of_string s) e') scaling_factor
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] compilation with OCaml 4.06

[Clément David]

Hello Florian,

The easier would be to depend on the external Num library for the 6.0.x family 
as far as this
library remains available; statically build against it is the way to go for 
OCaml code. Num might
also be packaged in your system, use ocamlfind to look for it.

Thanks,

--
Clément

Le mercredi 21 février 2018 à 08:41 +0100, Florian Blachère a écrit :
> Hello,
> 
> Scilab 6.0.0 and 6.0.1 (and the master branch) cannot be build using 
> OCaml 4.06 because this release remove the Num library 
> (https://ocaml.org/releases/4.06.html#Changes , 
> https://github.com/ocaml/ocaml/pull/1178), do you have any advice to 
> build Scilab with recent OCaml: integrate Num in Scilab, build Num 
> oustside of Scilab and link against it, ... ?
> 
> Thanks by advance,
> 
> Florian
> 
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Gsoc 2018 toolbox in scilab

[Clément David]

Hello Amit,

It would be nice to have a machine learning however you could start by taking a 
look at what's
already exists in http://atoms.scilab.org and on 
http://scilab.io/category/machine-learning . Could
you try to improve what's already existing ?

Thanks,

--
Clément

Le vendredi 16 février 2018 à 04:57 -0700, amit2rockon a écrit :
> Hello everyone, Myself Amit Kumar, new to this community, I have completed
> machine learning course by Andrew Ng and completed my assignment with
> Matlab. I think I could have done with Scilab. I want to contribute to this
> organization and also want to participate in GSoC 2018. So can anybody here
> help me from where i can start? i want to implement machine learning
> functions in toolboxes.
> 
> 
> 
> --
> Sent from: 
> http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

[Scilab-users] Release of Scilab 6.0.1

[Clément David]

Dear Scilab users,

We are pleased to announce the release of Scilab 6.0.1!

Scilab 6.0.1 is the first revision of the 6.0 development branch. It fixes bugs 
and implements missing features from the 5.5.2 version especially :

* fix crashes on corner cases (syntax, graphics, functions, etc..)
* improve Xcos model transformation and edition
* add help pages and demos

For the complete list of changes and bugs fixed, please take a look at the 
CHANGES file.

Download this brand new version at https://www.scilab.org/download/6.0.1
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Dump the output of a function

[Clément David]

Le mercredi 17 janvier 2018 à 20:36 +0100, Samuel Gougeon a écrit :
> Le 17/01/2018 à 20:26, Samuel Gougeon a écrit :
> > Le 17/01/2018 à 18:16, antoine monmayrant a écrit :
> > > Hello all, 
> > > 
> > > 
> > > I might say something really stupid, but can't we define a special 
> > > variable like %eps, %i, etc
> > > to act as a black hole ? 
> > > Something like %null (like piping to /dev/null or a null pointer) or a 
> > > better name
> > > (%blackhole, %lostforever, %byebye, ;-) ). 
> > > The idea being that no memory is allocated when someone try to affect 
> > > some value to it: 
> > > 
> > > [%null,%null,kb] = intersect(grand(1,10,"uin",0,9), 
> > > grand(1,10,"uin",0,9)); 
> >  
> > A true black hole has even no name :)
> > Otherwise, the shorter the better, and "_" would be nice after deprecating 
> > _() (*).
> > 
> > Anyway, IMO this black hole feature has a very low priority compared to 
> > some other ones, like
> > some big regressions (bug 13808 = 14881, sparse() with repeated indices, 
> > etc etc) or some very
> > and longly expected ones like a varprot()...
> > 
> > Samuel
> > 
> > (*) it could be renamed something like _tr() (standing for translate).
> > The number of occurrences of _() to be converted in the Scilab native code 
> > is very important,
> > but the conversion might be automated (since the gettext() scanner has a 
> > reliable detection
> > criterium, and only .sci, .sce, .tst and .dia.ref files are targeted
>  
> sorry, that's wrong. Other files in C, C++ etc, and xml have _() occurences 
> as well.
> But it's possible to parse them with no issue, since the scanner  does it.

Exact the `_ = gettext` has been stolen from the C usage of gettext. In C the 
'_' is defined as a
macro for gettext and is used for the same purpose: how to have the simplest 
identifier possible for
some hidden purpose ?

To me, Samuel proposition to deprecate "_" usage is really good; having "_" 
defined by default is
weird as there is two usage for this symbol (think from Go/Python users and 
from C users).

Thanks,

--
Clément
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] ?==?utf-8?q? Both scilab 5.5.2 & 6.0 stopped working (java issue under linux)

[Clément David]

Hello Antoine, Tim,

Yep, for such issue, having a cross posting between a scilab bug and the ubuntu 
bug is a good idea.
This issue are sometimes possible to fix on Scilab side (but not relying for 
some GL features).

--
Clément

Le mardi 23 janvier 2018 à 13:51 +0100, amonm...@laas.fr a écrit :
> Le 21/01/2018 à 21:31, Tim Wescott a écrit :
> > There's a known bug, at least in Ubuntu's bug base.
> 
> OK, do you have the link to the Ubuntu bug page?
> It's maybe still a good idea to open a scilab bug report, pointing at 
> the Ubuntu bug page and listing the workaround, no?
> 
> Antoine
> > It appears to vary by hardware -- it doesn't work on this machine, but
> > it works on at least one of my laptops.
> > 
> > On Sat, 2018-01-20 at 08:45 +0100, antoine monmayrant wrote:
> > > I just noticed that I did not fill a bug report for that.
> > > I have 3 of my colleagues running Scilab on Ubuntu 17.04 /17.10 that
> > > are
> > > also affected.
> > > Should I fill a bug report or it corresponds to a known one?
> > > 
> > > 
> > > Antoine
> > > 
> > > 
> > > Le 04/12/2017 à 17:05, Clément David a écrit :
> > > > Hi all,
> > > > 
> > > > Nice catch Antoine ! From my understanding of the crash and
> > > > depending on your graphic card, you
> > > > could switch the actual GL implementation to a well supported one
> > > > rather than relying on the latest
> > > > GL. For example, using mesa on my Intel i965 system, I can tweak
> > > > the used Profile through
> > > > MESA_GL_VERSION_OVERRIDE and MESA_EXTENSION_OVERRIDE [https://www.m
> > > > esa3d.org/envvars.html].
> > > > 
> > > > Regards,
> > > > 
> > > > --
> > > > Clément
> > > > 
> > > > Le lundi 04 décembre 2017 à 16:38 +0100, Antoine Monmayrant a écrit
> > > > :
> > > > > Hi all,
> > > > > 
> > > > > Answering my own post: it was a graphic driver issue, as usual.
> > > > > I switch to another driver and now scilab starts, but all the
> > > > > graphics windows are empty!
> > > > > 
> > > > > Antoine
> > > > >
> > > > >
> > > > > On Monday, December 04, 2017 16:12 CET, "Antoine Monmayrant"  > > > > nm...@laas.fr> wrote:
> > > > >
> > > > > > Hi everyone,
> > > > > > 
> > > > > > It seems that some automatic update have broken scilab on my
> > > > > > linux station (16.04.3 64bits).
> > > > > > Any java related feature is broken and only scilab-cli is
> > > > > > working.
> > > > > > As any of you any idea on how to investigate this issue?
> > > > > > 
> > > > > > Thanks in advance,
> > > > > > 
> > > > > > Antoine
> > > > > > 
> > > > > > PS: Here is the crash log:
> > > > > > 
> > > > > > 
> > > > > > $ scilab
> > > > > > Could not create a Scilab main class. Error:
> > > > > > Exception in thread "main" java.lang.InternalError: XXX0
> > > > > > profile[1]: GL3bc -> profileImpl GL4bc
> > > > > > !!! not mapped
> > > > > >   at
> > > > > > com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:20
> > > > > > 71)
> > > > > >   at
> > > > > > com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLPro
> > > > > > file.java:1954)
> > > > > >   at
> > > > > > com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.jav
> > > > > > a:1875)
> > > > > >   at
> > > > > > com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLPro
> > > > > > file.java:1842)
> > > > > >   at
> > > > > > com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
> > > > > >   at
> > > > > > com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
> > > > > >   at java.security.AccessController.doPrivileged(Native
> > > > > > Method)
> > > > > >   at
> > > > > > com.jogamp.opengl.GLProfile.initSingleton(GLPro

Re: [Scilab-users] OpenFEM

[Clément David]

Hello Paul,

May be at INRIA GForge [1] ?

[1]: https://gforge.inria.fr/projects/openfem/

--
Clément

Le vendredi 02 février 2018 à 08:59 +0100, paul.carr...@free.fr a écrit :
> Dear All,
> OpenFEM project seems to be dead ; the links do not work anymore 
> (http://www.openfem.net/t/ and ht
> tps://support.sdtools.com/gf/project/openfem).
> For my culture, does somebody has the latest release in its archives?
> Thanks
> Paul
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Atoms : "This account is not active"

[Clément David]

Hello Lucien,

Your account might have been deactivated for some reason. I will take a look, 
what's your username ?

--
Clément

Le mardi 06 février 2018 à 14:27 +0100, Povy Lucien a écrit :
> Hello
> 
> I have a account for "atoms", when i want to log on this account we have 
> a return :
> 
> "This account is not active". I cannot change the password, i cannot 
> delete this account.
> 
> What can i do ?
> 
> regards
> 
> 
> Lucien Povy
> 
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users