Re: [Scilab-users] Scilab 2024.0.0 on Linux Start up Shows OpenJDK 64-Bit Server VM warning

[Stephane Mottelet]

Hello,

I you really want to see *nothing*, invoke scilab with:

scilab > /dev/null 2>&1

---
Stephane Mottelet


Le 2023-12-08 09:01, COUVERT Vincent a écrit :

Dear user,



This warning (related to Java 17 migration done for Scilab 2024.0.0) has already been reported as an 
issue: 
https://gitlab.com/scilab/scilab/-/issues/17144<https://antiphishing.vadesecure.com/v4?f=S1Zkd042VWdrZG5qQUxxWktss9RtpldkB4NYx9rPqafc5sfxpMjZubx5rfbAIMTo=MlZSTzBhZFZ6Nzl4c3EyN5T6buDrCY0MsaGz9IPjCIg=F1is=cm1qVmRYUWk2WXhYZVFHWB8fXtbHbxv7pH8OXltXmDUJEy3WaeNcdG0AkmhM_kbl=97a85ec21f9c6252150147bca3fae740e4753c4a775d0b2bbdef6a1896b8aaf1=https%3A%2F%2Fgitlab.com%2Fscilab%2Fscilab%2F-%2Fissues%2F17144>



Best regards.







From: users  On Behalf Of ? ??
Sent: Friday, December 8, 2023 12:20 AM
To: users@lists.scilab.org
Subject: [Scilab-users] Scilab 2024.0.0 on Linux Start up Shows OpenJDK 64-Bit 
Server VM warning



Dear all
Scilab 2024.0.0 on Linux Starts up Shows
OpenJDK 64-Bit Server VM warning: Archived non-system classes are disabled because the 
java.system.class.loader property is specified (value = 
"org.scilab.modules.jvm.ScilabClassLoader"). To use archived non-system 
classes, this property must not be set



when Scilab 23.1.0 starts up,the warning didn't shows,

I don't wanna see the warning even if it does not affect its use

How to resolve this problem ?

This email and any attachments are intended solely for the use of the 
individual or entity to whom it is addressed and may be confidential and/or 
privileged.

If you are not one of the named recipients or have received this email in error,

(i) you should not read, disclose, or copy it,

(ii) please notify sender of your receipt by reply email and delete this email 
and all attachments,

(iii) Dassault Systèmes does not accept or assume any liability or 
responsibility for any use of or reliance on this email.


Please be informed that your personal data are processed according to our data privacy policy as 
described on our website. Should you have any questions related to personal data protection, please 
contact 3DS Data Protection Officer 
https://www.3ds.com/privacy-policy/contact/<https://antiphishing.vadesecure.com/v4?f=S1Zkd042VWdrZG5qQUxxWktss9RtpldkB4NYx9rPqafc5sfxpMjZubx5rfbAIMTo=MlZSTzBhZFZ6Nzl4c3EyN5T6buDrCY0MsaGz9IPjCIg=F1is=cm1qVmRYUWk2WXhYZVFHWB8fXtbHbxv7pH8OXltXmDUJEy3WaeNcdG0AkmhM_kbl=d706c7581397c33a2d7d0670be7670ea1c8c0e9c3d55a534c8ade3ac010ca95d=https%3A%2F%2Fwww.3ds.com%2Fprivacy-policy%2Fcontact%2F>



___
users mailing list - users@lists.scilab.org<mailto:users@lists.scilab.org>
Click here to unsubscribe: 
<mailto:users-unsubscr...@lists.scilab.org<mailto:users-unsubscr...@lists.scilab.org>>
https://antiphishing.vadesecure.com/v4?f=S1Zkd042VWdrZG5qQUxxWktss9RtpldkB4NYx9rPqafc5sfxpMjZubx5rfbAIMTo=MlZSTzBhZFZ6Nzl4c3EyN5T6buDrCY0MsaGz9IPjCIg=F1is=cm1qVmRYUWk2WXhYZVFHWB8fXtbHbxv7pH8OXltXmDUJEy3WaeNcdG0AkmhM_kbl=43edcbcfe8c2d04d3fcfbe4a167177f5ad71436caa18e674437a042f7829e3db=https%3A%2F%2Flists.scilab.org%2Fmailman%2Flistinfo%2Fusers

This email and any attachments are intended solely for the use of the 
individual or entity to whom it is addressed and may be confidential and/or 
privileged.

If you are not one of the named recipients or have received this email in error,

(i) you should not read, disclose, or copy it,

(ii) please notify sender of your receipt by reply email and delete this email 
and all attachments,

(iii) Dassault Systèmes does not accept or assume any liability or 
responsibility for any use of or reliance on this email.


Please be informed that your personal data are processed according to our data 
privacy policy as described on our website. Should you have any questions 
related to personal data protection, please contact 3DS Data Protection Officer 
https://www.3ds.com/privacy-policy/contact/

___
users mailing list - users@lists.scilab.org
Click here to unsubscribe: <mailto:users-unsubscr...@lists.scilab.org>
https://lists.scilab.org/mailman/listinfo/users

[Scilab-users] Sundials differential equations solvers features

[Stephane Mottelet]

(This message is a repost of a topic at 
https://discourse.scilab.utc.fr/t/sundials-differential-equations-solvers-features.
 Feel free to answer here or there).

Hello Scilab users,

We would like to have your impressions about forthcoming features. They are mainly about 
differential equations, differential-algebraic and non-linear systems of equations and their 
solvers as implemented by the recently awarded 
SUNDIALS solver suite. Preview builds of 
Scilab allowing to use all the solvers and their features are available at 
https://www.utc.fr/~mottelet/scilab_for_macOS.html 
1 (look for “Sundials/Colpack preview 
builds”). The help pages (available online 
1) and demos should give you a good idea of 
the user-friendly features that are available, which can be compared to the actual features of 
Scilab solvers such as ode() and dassl(). The underlying Sundials library also allows to consider 
large scale systems of stiff equations (typically coming from discretization of partial 
differential equations) by specifying sparse Jacobians or sparsity patterns allowing efficient 
estimation thereof.

This is the occasion of thinking about revamping the differential equations 
module, which could embrace theses new solvers and the actual ones, in a 
unified API, which could also propose new solvers. So let us start the 
discussion !

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

This email and any attachments are intended solely for the use of the 
individual or entity to whom it is addressed and may be confidential and/or 
privileged.

If you are not one of the named recipients or have received this email in error,

(i) you should not read, disclose, or copy it,

(ii) please notify sender of your receipt by reply email and delete this email 
and all attachments,

(iii) Dassault Systèmes does not accept or assume any liability or 
responsibility for any use of or reliance on this email.


Please be informed that your personal data are processed according to our data 
privacy policy as described on our website. Should you have any questions 
related to personal data protection, please contact 3DS Data Protection Officer 
https://www.3ds.com/privacy-policy/contact/

___
users mailing list - users@lists.scilab.org
Click here to unsubscribe: 
https://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Scatter plot with fixed marker dimension and overlap analysis

[Stephane Mottelet]

Hello,

I think we should let Charles explain what he wants. Particularly he should 
explain what is the heat map he is talking about. Concerning your claim about 
imread, you cannot compare it with wavread. There are far more different image 
formats than audio formats ! This explain why imread and imwrite are part of 
image processing packages. Concerning your claims about missing features, I 
found them legitimate, but they should be directed to the communit :  don't 
expect the core team to do everything ! For example, you have described a 
method to solve Charles problem. So before critisizing proposed method below 
(with a working code) you should propose a code implementing your solution, 
don't you think so ?

S.

---
Stephane Mottelet


Le 2023-03-17 22:23, Federico Miyara a écrit :

Stéphane,

There are two problems with this approach. The first one is that there is no way to know how many 
disks cover a given point so the "heat map" would have only two levels: a given point 
belongs or not to the impact area. Charles hasn't carified, but the term "heat map" he 
used suggests a graded plot. The second problem is that you need to resource to a function not 
directly available in Scilab so you need to install a toolbox. Moreover, you need to create an 
intermediate file.

By the way, I always wondered why imread() isn't part of Scilab's core, as is 
wavread(). Maybe image processing is a very specialized subject demanding a 
complete toolkit to deal with it, but some basic functions like imread() or 
imwrite() would be very handy to ensure easy interoperabilty with other 
software packages.

It is also a pity that xs2bmp() cannot provide an array output with the pixel 
data corresponding to the figure image (2x2x3 for color graphs).

Regards,

Federico Miyara


On 17/03/2023 12:17, Stéphane Mottelet wrote:

Hello,

I would propose this solution, inspired by my remark abour using xfarcs and the bitmap idea from 
Frederico. The idea is to plot the disks then export the graph under a bitmap format, the read the 
image back (needs "imread" e.g.from IPCV) then count the black pixels ("true" 
value in x below). The ratio between black pixels and total number of pixels gives you the 
proportion of covered area:

clf

n = 17;
xc = grand(1,n,"unf",0,5);
yc = grand(1,n,"unf",0,5);
radius = grand(1,n,"unf",0,1);

drawlater
arcs=[xc-radius
yc-radius
2*radius
2*radius
zeros(1,n)
   zeros(1,n)+360*64];
st=ones(1,n);
a1 = newaxes();
a1.margins=[0 0 0 0];
xfarcs(arcs,st);
a1.data_bounds = [0,5,0,5];
isoview on
s=gcf().axes_size;
gcf().axes_size=[400 400]
drawnow

xs2bmp(0,"im.bmp");
x=imread("im.bmp");

disp(sum(x)/size(x,"*"))

S.

Le 16/03/2023 à 18:43, Federico Miyara a écrit :

Charles,

I assume the area of each impact point is circular (but it could be abapted for 
other forms). Then you could start with a n*m matrix filled with zeros. Then, 
according to a convenient scale, each impact point is approximated by a 
component of the matrix. The horizontal and vertical positions (column and row) 
will represent quantized coordinates.

Then, if the coordinates of an impact point ar p (column) and q (row) and the 
radius of its impact area is R, expressed using the same scale, for column k = 
(p - R):(p + R) you add 1 to the rows from q - sqrt(R^2-k^2) to q + 
sqrt(R^2-k^2).

You repeat that for all impact points (with a for loop) and at the end you have 
that each component of the matrix (which represent pixels) will be exactly the 
number of overlapping areas at the location represented by the component. For 
instance, if at component u, v you have 7, that means 7 impact areas contain 
that component.

This could be adapted even to a graded impact area, replacing 1 by the result 
of a function with a maximum at the center fading down to 0 at the perimeter of 
the impact area

You must be careful near the boundary so that components don't exceed the 
limits (for instance, not smaller than 1 or greater than n or m)

This is not probably the most efficient way, but assuming the impact area is 
small it should work fine and reasonably fast for a few thousand impact points.

Regards.

Federico Miyara


On 16/03/2023 00:45, charles marcotte wrote:
Hello,

I have 2d scatter plot where each marker represents an impact point. The impact 
point has a defined area.
1.  I am trying to assign each point the impact area to visualize how much of 
the surface is impacted.
Defining the marker size does not work because I change the scale between 
simulations and I can't find a definition of the marker size vs diameter or 
perimeter.

2. is there a way to calculate the overlap on the area through the chart with a 
heat map for example?

Thank you
Charles

This email and any attachments are intended solely for the use of the 
individual or entity to whom it is addressed and may be confidential 

Re: [Scilab-users] [Scilab-Dev] Scilab releases schedule / End of Windows 32-bit support

[Stephane Mottelet]

Hello,

Thanks for your mesage.

Independently of the version numbering  the main interesting information is 
about the frequency of the releases, which is a good thing and shows the future 
investment of the 3DS Scilab team. I just hope that users will get used to 
trash their current version of Sclab to use the new one every 6 month, 
otherwise helping them will become very complicated. These days it was quite 
easy because people were using mainly 5.5.2 and 6.1.1 version ! Habits will 
have to change...

S.

---
Stephane Mottelet


Le 2023-02-25 14:33, A. Khorshidi a écrit :



Dear Stéphane,



I really appreciate you being so compassionate about making Scilab the best it 
can be.

There is no doubt that the points you make are absolutely valid, and I hope 
that Scilab's administration will make a wise decision to continue to maintain 
the project in the future.

Merci,
Mehran


From: Stéphane Mottelet 
Sent: Thursday, February 23, 2023 2:36 AM
To: Stéphane Mottelet 
Subject: Re: Scilab needs you

Hello,

Some of you have already answered and it is still time to express
yourself. Below are the links to the threads on the archive of the
mailing list :

original message:

https://www.mail-archive.com/users@lists.scilab.org/msg11014.html

my answer:

https://www.mail-archive.com/users@lists.scilab.org/msg11015.html

If you need to re-subscribe to the mailing list to be able to send your
message use the following link:

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

This is my last message sent to you directly about that subject.

S.

Le 20/02/2023 à 09:11, Stéphane Mottelet a écrit :

Dear Scilab users and developpers,

You have been using or are still using Scilab, as a user and/or a
toolbox author, maybe you are also packaging Scilab. These days
there's a hot topic on d...@lists.scilab.org  (look for the message
with title "Scilab releases schedule / End of Windows 32-bit support")
concerning a potential change of the versioning scheme which could
seriously dammage the relations between Scilab and the OSS community.
If you have some spare time and think that Scilab is worth it please
give your thoughts in the discussion thread. There is another thread
in us...@scilab.list.org you can express in any of the two.

Sincerely yours,


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


This email and any attachments are intended solely for the use of the 
individual or entity to whom it is addressed and may be confidential and/or 
privileged.

If you are not one of the named recipients or have received this email in error,

(i) you should not read, disclose, or copy it,

(ii) please notify sender of your receipt by reply email and delete this email 
and all attachments,

(iii) Dassault Systèmes does not accept or assume any liability or 
responsibility for any use of or reliance on this email.


Please be informed that your personal data are processed according to our data 
privacy policy as described on our website. Should you have any questions 
related to personal data protection, please contact 3DS Data Protection Officer 
https://www.3ds.com/privacy-policy/contact/

___
users mailing list - users@lists.scilab.org
Click here to unsubscribe: <mailto:users-unsubscr...@lists.scilab.org>
https://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] [Scilab-Dev] Scilab releases schedule / End of Windows 32-bit support

[Stephane Mottelet]

Hello,

Please allow me to react to these answers as I feel also very concerned with 
this potential evolution. The year-base major number won't ease a better 
visibility about API changes. It will force us to systematically add a a notice 
saying  something like :

"Don't worry about the major version increase because this time there will not be 
any API change"

or its contrary :

"Unlike previous year, there will be major API changes in this new major version so 
you will have to upgrade your toolboxes".

Moreover, the rationale about the "compatibility with other tools (Matlab, Office, 
Excel, ...)" has no sense because these tools are commercial and closed source 
software. However, I admit that having the year information can be valuable for all users 
as it will allow to know immediately when a given version of Scilab was released.

The ideal scenario would be to use both systems: keep the usual not year-based 
major.minor.patch version numbering (SCI_VERSION_MAJOR, 
SCILAB_VERSION_MINOR,SCILAB_VERSION_MAINTENANCE in our headers) together with a 
release name (SCILAB_VERSION_STRING in our headers).

Presently Scilab is already ready for that since we have the following 
different outputs, for example here with a CI (continuous integration) build:

--> getversion
ans  =

 "scilab-mr3-0237210d"

--> getversion("scilab")
ans  =

  6.   1.   2.   1.677D+09

Here SCILAB_VERSION_STRING="scilab-mr3-0237210d" has been given during the CI 
and is completely arbitrary and not related to the second output which gives the true 
information about changes at the code level.

Having a new release schedule half-year based is completely independent of this need of version numbering. I 
am fine with the fact that you may need a kind of "branding" since almost all of the developers of 
Scilab are employed by a private entity who "owns" at least the "Scilab" name (but a big 
part of Scilab code owns to individual authors) to me that's the main rationale. However you should be aware 
that open-source software never completely belongs to its authors but also to its numerous users.

Since it beginnings Scilab had a complicated story and its governance has 
always been a mystery for most people using it. But in the last 5 years the 
huge work of promoting Scilab and keeping it alive and kicking was made by the 
users themselves. So, this proposed unilateral change from your (3DS employees, 
at least you Vincent) side and my counter-proposition is the occasion to 
exhibit a bit of democracy.

I propose the aforementioned solution using the year-based numbering for the 
release name (SCILAB_VERSION_STRING) and keeping the usual numbering 
SCI_VERSION_MAJOR.SCILAB_VERSION_MINOR.SCILAB_VERSION_MAINTENANCE with its 
actual signification. Please note that yo refer to Matlab and that this 
software uses this dual numbering system !

Users and developers who feel concerned with this subject can express 
themselves in this thread.

S.

---
Stephane Mottelet


Le 2023-02-17 18:12, COUVERT Vincent a écrit :

Hi Sylvain,

The semantic meaning of major/minor/patch version is kept:

-  Major releases may have API changes:

o   There may be API changes between Scilab 2023.m.p and 2024.m'.p' but it is 
not mandatory

-  Minor releases are API compatible:

o   Changes between Scilab 2023.m.p and Scilab 2023.m'.p' cannot be related API 
changes

-  Patches are binary compatible:

o   Changes between Scilab 2023.m.p and Scilab 2023.m.p' will not involve binary change. 
Changes on p (patch) mostly concern "hot fixes".



Compatibility with other tools (Matlab, Office, Excel, ...) and even OS 
following the same calendar will be easier to follow and understand.



This new release schedule also allows us to give a better visibility to 
developers/contributors in order to anticipate:

-  API changes,

-  Function deprecation,

-  Maintenance periods,

-  Scilab evolutions.


From a user perspective,  it will be easier to identify how up-to-date or 
deprecated their Scilab could be.


Vincent



From: dev  On Behalf Of Sylvain Corlay
Sent: Friday, February 17, 2023 4:04 PM
To: List dedicated to the development of Scilab 
Subject: Re: [Scilab-Dev] Scilab releases schedule / End of Windows 32-bit 
support



Hi Vincent,



The problem with year-based versioning is that it removes any semantic meaning 
to minor and patch - especially with respect to relinking etc. What are the 
expected benefits of the proposed change ?



Best,







On Fri, Feb 17, 2023 at 4:01 PM COUVERT Vincent 
mailto:vincent.couv...@3ds.com>> wrote:

Hi Sylvain,



Thanks for your email, we completely agree with you about the meaning and 
contents of major, minor and patch versions.



As you say, "Major version updates may break API compatibility" but it is not 
mandatory for a major version.

As

Re: [Scilab-users] output buffer

[Stephane Mottelet]

Hello,

The buffer size is not set by Scilab and hence is always the default for 
a given platform (it can be different for macOS, Linux, Windows). I 
suppose you need to increase or decrease it for a given application ?


S.

---
Stephane Mottelet

Le 2022-06-17 14:41, Jean-Yves Baudais a écrit :

Hello,

In other words, how to use "setvbuf" in Scilab? Is there an equivalent
function that works with the mfprintf scilab function?

Thanks,

--Jean-Yves


Le 16/06/2022 à 10:39, Jean-Yves Baudais a écrit :

How to manage *the size*. Sorry.

Jean-Yves

Le 16/06/2022 à 10:38, Jean-Yves Baudais a écrit :

Hello,

How can we manage the output buffer when we write to a file? It seems 
that this buffer size is 4096.


Thanks,

Jean-Yves

___
users mailing list
users@lists.scilab.org
https://antispam.utc.fr/proxy/v3?i=SXVFem5DOGVpUU1rNjdmQuxbAYzjRE578NJDXO0bRW0=bWt1djZ5QzcyUms5R1Nzas4Pz4hn3S9_MEd_XcyeYzHsyKCVRtQ67N89rCt3q6Xy=Q3ZQNmU2SnpsRFlRbUF3dm35RmWaJxuoBVu42ymMGAK3JGu3n6Y8Xa7RPvcRg_db=http%3A//lists.scilab.org/mailman/listinfo/users=syJL

___
users mailing list
users@lists.scilab.org
https://antispam.utc.fr/proxy/v3?i=SXVFem5DOGVpUU1rNjdmQuxbAYzjRE578NJDXO0bRW0=bWt1djZ5QzcyUms5R1Nzas4Pz4hn3S9_MEd_XcyeYzHsyKCVRtQ67N89rCt3q6Xy=Q3ZQNmU2SnpsRFlRbUF3dm35RmWaJxuoBVu42ymMGAK3JGu3n6Y8Xa7RPvcRg_db=http%3A//lists.scilab.org/mailman/listinfo/users=syJL

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

Re: [Scilab-users] Cannot start Scilab 6.1.1

[Stephane Mottelet]

Can you try, on the command line :

_JAVA_OPTIONS="-Djogl.disable.openglarbcontext=1" ./bin/scilab &



---
Stephane Mottelet

Le 2022-03-29 21:43, Stefan Du Rietz a écrit :

Hi Stéphane,

Thank you very much, your command worked!
$ sudo apt install libtinfo5

Then Scilab started OK, but with many messages:

stefan@LenovoTS:/usr/local/scilab/scilab-6.1.1$ ./bin/scilab &
[1] 276737
stefan@LenovoTS:/usr/local/scilab/scilab-6.1.1$ X Error of failed
request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  152 (GLX)
  Minor opcode of failed request:  24 (X_GLXCreateNewContext)
  Value in failed request:  0x0
  Serial number of failed request:  110
  Current serial number in output stream:  111
javax.media.opengl.GLException: X11GLXDrawableFactory - Could not
initialize shared resources for :0.0
  at
jogamp.opengl.x11.glx.X11GLXDrawableFactory$SharedResourceImplementation.createSharedResource(X11GLXDrawableFactory.java:317)
  at 
jogamp.opengl.SharedResourceRunner.run(SharedResourceRunner.java:295)

  at java.lang.Thread.run(Thread.java:748)
Caused by: javax.media.opengl.GLException: main-SharedResourceRunner:
Unable to create temp OpenGL context(1)
  at 
jogamp.opengl.x11.glx.X11GLXContext.createImpl(X11GLXContext.java:343)
  at 
jogamp.opengl.GLContextImpl.makeCurrentWithinLock(GLContextImpl.java:696)

  at jogamp.opengl.GLContextImpl.makeCurrent(GLContextImpl.java:589)
  at jogamp.opengl.GLContextImpl.makeCurrent(GLContextImpl.java:539)
  at
jogamp.opengl.x11.glx.X11GLXDrawableFactory$SharedResourceImplementation.createSharedResource(X11GLXDrawableFactory.java:293)
  ... 2 more
[Fatal Error] :1:1: Premature end of file.

/Stefan


On 2022-03-29 16:02, Stéphane Mottelet wrote:

Hi Stefan,

Did you try to google with

"libtinfo.so.5: cannot open shared object file: No such file or 
directory"


There is a bunch of possible fixes. did you try :

sudo apt install libtinfo5

?

S.


___
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] xdel replaced by close()

[Stephane Mottelet]

However, the findobj() fix that has been recently merged by Clément 
restores only the speed of tags search. findbobj()  won't be further 
fixed as it provides many useful features which were missing to its 
(fast but poor) previous version.


Indeed, using findobj to get the handle of a figure knowing its id is 
the most complicated that one can imagine. It sounds to me like the 
affirmation: « why make it simple when it can be made complicated »... I 
mean, close() has to be fixed to use scf() as proposed in this thread.


Sometimes adding useful and needed features can degrade the speed of a 
function (you can't make an omelette without breaking eggs).  Finding 
handles given their tag has its original performance with this patch. 
But I repeat that h=findobj('figure_id",id) should be avoided in favour 
of h=scf(id), until findobj() is completely rewritten in C++ (which is 
planned).


Moreover nobody was complaining about xdel() and making it deprecated 
was never discussed by the community. Many people don't use Scilab any 
more because it misses features. So Scilab needs features, not 
absurde/arbitrary cleaning . A word to the wise...


S.

Le 2022-01-22 14:24, Stéphane Mottelet a écrit :


Hi,

This is fixed for the next release:

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

In the meantime, if you really need it you can download the patched 
version of findobj.


S.


Le 21 janv. 2022 à 23:54, Samuel Gougeon  a écrit :


Hello Claus,

Le 21/01/2022 à 20:58, Claus Futtrup a écrit : Hi Scilabers

Today I tried to replace xdel(winsid()) in one of my scripts with 
close(winsid()) because Scilab shows a warning in the console:


Warning: Feature xdel(...) is obsolete and will be permanently removed 
in Scilab 6.2


Warning: Please use close(...) instead.

I am negatively surprised that the close() command takes a long time to 
execute with 5-10 windows open (a few seconds per window). The xdel() 
command can do it in a split second.


The issue comes not from close() but from the change of findobj() that 
it calls [2], noticeably to perform findobj("figure_id",id) in 6.1.1.
It does not impact only [3] close() for this case, that was processed 
as a special accelerated case [4] in the former findobj().
This downgrading was reported [5] 7 months before releasing 6.1.1, and 
knowingly ignored, while it is perfectly fixable by restoring the fast 
special case.


What is the motivation for replacing xdel with close?
Both do the same thing. Scilab does not need duplicates.

Regards
Samuel

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


___
users mailing list
users@lists.scilab.org
https://antispam.utc.fr/proxy/v3?i=SGI0YVJGNmxZNE90Z2thMFYLWSxJOfIERJocpmb73Vs=SW5LV3JodE9QZkRVZ3JEYbCxfBpXCzNXFJI9eyEBCB_E8EQzXar_oWBGCSukLx6I=bnJjU3hQT3pQSmNQZVE3aPQ56ZBjot0Lu_H1dlHvp1727w_z78BVJc295PQlt99Z=http%3A//lists.scilab.org/mailman/listinfo/users=dFBm

Links:
--
[1] 
https://antispam.utc.fr/proxy/v3?i=SGI0YVJGNmxZNE90Z2thMFYLWSxJOfIERJocpmb73Vsr=SW5LV3JodE9QZkRVZ3JEYbCxfBpXCzNXFJI9eyEBCB_E8EQzXar_oWBGCSukLx6If=bnJjU3hQT3pQSmNQZVE3aPQ56ZBjot0Lu_H1dlHvp1727w_z78BVJc295PQlt99Zu=https%3A//codereview.scilab.org/%23/c/21803/k=dFBm
[2] 
https://antispam.utc.fr/proxy/v3?i=SGI0YVJGNmxZNE90Z2thMFYLWSxJOfIERJocpmb73Vsr=SW5LV3JodE9QZkRVZ3JEYbCxfBpXCzNXFJI9eyEBCB_E8EQzXar_oWBGCSukLx6If=bnJjU3hQT3pQSmNQZVE3aPQ56ZBjot0Lu_H1dlHvp1727w_z78BVJc295PQlt99Zu=http%3A//bugzilla.scilab.org/show_bug.cgi%3Fid%3D13738%23c4k=dFBm
[3] 
https://antispam.utc.fr/proxy/v3?i=SGI0YVJGNmxZNE90Z2thMFYLWSxJOfIERJocpmb73Vsr=SW5LV3JodE9QZkRVZ3JEYbCxfBpXCzNXFJI9eyEBCB_E8EQzXar_oWBGCSukLx6If=bnJjU3hQT3pQSmNQZVE3aPQ56ZBjot0Lu_H1dlHvp1727w_z78BVJc295PQlt99Zu=http%3A//bugzilla.scilab.org/16734k=dFBm
[4] 
https://antispam.utc.fr/proxy/v3?i=SGI0YVJGNmxZNE90Z2thMFYLWSxJOfIERJocpmb73Vsr=SW5LV3JodE9QZkRVZ3JEYbCxfBpXCzNXFJI9eyEBCB_E8EQzXar_oWBGCSukLx6If=bnJjU3hQT3pQSmNQZVE3aPQ56ZBjot0Lu_H1dlHvp1727w_z78BVJc295PQlt99Zu=https%3A//codereview.scilab.org/%23/c/20953/6/scilab/modules/gui/macros/findobj.scik=dFBm
[5] 
https://antispam.utc.fr/proxy/v3?i=SGI0YVJGNmxZNE90Z2thMFYLWSxJOfIERJocpmb73Vsr=SW5LV3JodE9QZkRVZ3JEYbCxfBpXCzNXFJI9eyEBCB_E8EQzXar_oWBGCSukLx6If=bnJjU3hQT3pQSmNQZVE3aPQ56ZBjot0Lu_H1dlHvp1727w_z78BVJc295PQlt99Zu=http%3A//bugzilla.scilab.org/show_bug.cgi%3Fid%3D7117%23c6k=dFBm___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Multiple regression on semi-log plot

[stephane . mottelet]

 Hello,

You just have to replace "x" by "wavelength" and "y" by "ln_power".  
The slopes are the first two component of the optimal vector "popt" :
clearclf()// Read data - wavelength (in km)), power, 1 standard  
deviation// Unknown data length; 3 columns -default space delimited //  
PSD_wavelength.dat from GMT grdfft radially averaged power spectra  
data = read('PSD_wavelength.dat',-1,3);  wavelength = data(:,1); power  
= data(:,2); std_dev1 = data(:,3);  ln_power = log(power);  wavenumber  
= 1./wavelength; f=gcf();  //plot(wavenumber, ln_power)  
scatter(wavenumber, ln_power,'marker','.') a=gce().children;  
a.mark_mode = "on"a.mark_style = 0a.mark_size_unit =  
"point"a.mark_size=3 xlabel ('wavenumber k (km-1)')ylabel ('Log  
(Power)') function y=fun(x, param)a = param(1); b = param(2);   
   theta = param(3); phi = param(4); c =  
(x=theta)*b; y = c.*(x-theta)+phi; endfunction  
function r=residual(param, x, y, f)r = sum((y-f(x,param)).^2);  
endfunction function [r, dr, ind]=costf(p, ind, x, y, f)r =  
residual(p,x,y,f); dr = numderivative(list(residual,x,y,fun),p);  
endfunction [ropt,popt] =  
optim(list(costf,wavenumber,ln_power,fun),[0,0,mean(wavenumber),mean(ln_power)]);   
plot(wavenumber,fun(wavenumber,popt),'r',popt(3),popt(4),'xr')


arctica1963  a écrit :


Hello,

Thanks for the idea and suggestions. Not too sure how to apply it, if you
could give some pointers on the attached data and code. The ultimate idea is
to get the slopes of the straight line segments. Many thanks, Lester

clear
clf()
// Read data - wavelength (in km)), power, 1 standard deviation
// Unknown data length; 3 columns -default space delimited

// PSD_wavelength.dat from GMT grdfft radially averaged power spectra

data = read('PSD_wavelength.dat',-1,3);

wavelength = data(:,1);
power = data(:,2);
std_dev1 = data(:,3);

ln_power = log(power);

wavenumber = 1./wavelength;
f=gcf();

//plot(wavenumber, ln_power)

scatter(wavenumber, ln_power,'marker','.')

a=gce().children;
a.mark_mode = "on"
a.mark_style = 0
a.mark_size_unit = "point"
a.mark_size=3

xlabel ('wavenumber k (km-1)')
ylabel ('Log (Power)')

PSD_wavelength.dat


--
Sent from:  
https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html

___
users mailing list
users@lists.scilab.orghttps://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

Re: [Scilab-users] Sci-IPOpt updated

[stephane . mottelet]

 Hello,

This year Christmas arrived in september: although Windows really  
sucks, I managed with the help of Antoine to build a version of the  
toolbox for this operating system. Windows users should be able to  
install sci_ipopt from the atoms GUI (Optimization category). However,  
there is a little glitch because the Intel Fortran runtime bundled  
with Scilab is a little bit outdated and this is a problem for the  
thirdparty ipopt DLL. Hence, once you have installed the toolbox,  
loading it after a restart will fail. Hopefully there is an easy fix  
and I have bundled a little script dedicated to this. Hence, after the  
Scilab restart and the failing Sci-IPOpt load, just type the following  
at Scilab's prompt:


--> cd(atomsGetInstalledPath("sci_ipopt"))
--> exec windows_ifort_fix.sce

then restart Scilab: the toolbox should load just fine (run one of the  
demos to make sure that everything works). The Intel Fortran runtime  
will surely be updated for the next Scilab release and this fix won't  
be anymore necessary.


S.

Stéphane Mottelet  a écrit :


Hello,

The Sci-IPOpt toolbox has been updated and now work (smoothly) for  
Scilab 6.1. Users needing a serious tool for doing optimization with  
general nonlinear constraint should give it a try. There is no  
Windows version for the moment but I hope we will have one before  
Christmas !


Enjoy !

--
Stéphane Mottelet
Ingénieur de recherche
EA 4297 Transformations Intégrées de la Matière Renouvelable
Département Génie des Procédés Industriels
Sorbonne Universités - Université de Technologie de Compiègne
CS 60319, 60203 Compiègne cedex
Tel : +33(0)344234688
https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/www.utc.fr/~mottelet

___
users mailing list
users@lists.scilab.orghttps://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

Re: [Scilab-users] Error in parameters determined in non-linear least-squares fitting

[stephane . mottelet]

 Hello Heinz,

You can have a look at pages 45-49 of my slides on least Squares :

http://www.utc.fr/~mottelet/mt94/leastSquares.pdf

Page 48 you have an example where the Covariance matrix is  
approximated for a fitting problem with an ode defined page 42.


S.

Quoting Heinz Nabielek :

Scilab friends: the power of Scilab is amazing and I have used it  
recently for non-linear least-squares fitting, below example from  
Scilab help function for "datafit". On occasions, I have also used  
"leastsq".

   
  Question: how do I derive the 1sigma standard error in the three  
parameters p(1), p(2), and p(3)? And, if it is not too complicated,  
covariances?

   
  I know this is written in dozens of textbooks, but I am always  
getting lost.

  Please provide a simple recipe written in Scilab.
  Best greetings
  Heinz
   
   
   
  // -- 04/04/2020 14:57:30 -- generate the datafunction y=FF(x,  
p)  y=p(1)*(x-p(2))+p(3)*x.*xendfunctionX=[]; Y=[]; pg=[34;12;14]  
//parameter used to generate datafor x=0:.1:3   
Y=[Y,FF(x,pg)+100*(rand()-.5)];   X=[X,x]; endZ=[Y;X]; //The  
criterion functionfunction e=G(p, z),   y=z(1),x=z(2);
e=y-FF(x,p), endfunction//Solve the  
problemp0=[3;5;10][p,err]=datafit(G,Z,p0);  
scf(0);clf()plot2d(X,FF(X,pg),5) //the curve without  
noiseplot2d(X,Y,-1)  // the noisy dataplot2d(X,FF(X,p),12) //the  
solutionxgrid();legend("the curve without noise"," the noisy data",  
"THE FINAL SOLUTION.",4); title("solution set   39.868419 
10.31205311.482521","fontsize",4);
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Some inconsistency during installation o 6.1

[stephane . mottelet]

 Hello Frederico,

Thank you for your posiitve feedback on 6.1 display improvements. I  
think you are the only user who did so on the ML.


Concerning the problem of rationals display, which is done in  
%r_p.sci,  for the moment it is impossible to respect the actual  
mode() value, because overloads are systematically evaluated with  
mode() == -1. This a current limitation of overlading mechanism and  
fixing it is doable but not trivial (at least from my point of view).


Best,

S.

Quoting Federico Miyara :


Dear all,

I've just installed version 6.1. When installing it there is a  
button "About modules...". Clicking on it opens the following link  
in the browser:  


https://wiki.scilab.org/howto/install/windows[1]

However, it refers to Scilab 5.5.2, not even 6.0.2, so may be this  
already happened for the preceding versions. It is not important,  
but considering that the link is there, it should point to an  
updated link.


I didn't test it too much yet, but the new really compact version of  
mode(1) is most welcome, especially for those of us who use  
small-screen laptops. Also welcome is the single-line presentation  
of polynomials, with in-line exponents using superscripts.
However, full compactness doesn't seem to work with rationals, since  
a blank line is still appearing before the result, for instance,


--> q = (1-%s)/(1+%s^2)
 q  =
 
   1 -s  
   - 
   1 +s²

while with polynomials it works fine:

--> q = 1+%s^2
 q  =
  1 +s²

Regards,

Federico Miyara   




Links:
--
[1]  
https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/wiki.scilab.org/howto/install/windows
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Scilab cannot work on macOS 10.15 Catalina: Any progress in sight?

[stephane . mottelet]

 There is a big difference in the inherited environment when scilab  
is launched from the command line and by clicking the icon.

In the past I solved a problem with the LANG variable

https://codereview.scilab.org/#/c/20787/
https://codereview.scilab.org/#/c/21069/

the second one is still not merged in master but has been included in  
19 august build of Scilab 6.0.2 for OSX (the one available from  
www.scilab.org), since it was really blocking for many users.


Just to say that the regexp problem may be due to a similar problem  
(locale, encoding, ...)


S.

Chin Luh Tan  a écrit :


ok, i did:
    
   1. Del both previous scilab and the scilab from your link  
installed just now to make it clean
   2. Totally remove the .Scilab folder under home folder by using  
sudo rm -R .Scilab

   3. Re-download the link 
   4. Double click and install (by dragging the scilab icon to  
application folder)

   5. run scilab from the app and type atomsList
    
   Same regexp error until i launch it from terminal, and then it is ok. 
    
   noted on the atoms issue for the modules with gateway, will try  
to look into it.

    
   p/s: will continue any extra testing tomorrow. 
    
   rgds,
CL
    
    
 On Tue, 05 Nov 2019 00:24:53 +0800   
 wrote 

 

Obviously, between points 3 and 4 I moved the Scilab app from the  
archive in the Appplication folder.


stephane.motte...@utc.fr a écrit :


Hello,

I don't have the regexp error. Here is my complete workflow:

1 - Delete the eventual previous Sciab 6.0.2 I had in the  
/Applications/ folder 

2 - Delete my .Scilab folder
3 - extract the .dmg I downloaded  
from http://www.utc.fr/~mottelet/scilab/download/6.0.2/scilab-6.0.2-x86_64-2019-11-04.dmg[1]
4 - double click the Scilab icon (with first launch usual but  
annoying details...)

5 - click the ATOMS gui icon or type atomsList at Scilab prompt

Concerning the problem with IPCV (and maybe other packages with  
gateways, I only tested IPCV), I did not address it in the above  
archive. I only modified the scilab script (I will create a commit  
on codereview.scilab.org) and removed the libcurl.dylib that was  
shipped in lib/thirdparty folder.


Best,

S.

   Chin Luh Tan  a écrit :


Hi, 
  
 from my end:
  
 1. The warning for the 10.15 gone. 
 2. First launch from the app still give the regexp error  
when running atomsList, but after running one time from terminal  
and get it run successfully, I could run it from the app as after  
all. 
 3. atomsInstall for the module with gateway folder still  
extracted to 2 separate folders which need to be manually move in  
order for it to run. No issue for macros only module. 

  
 Thanks for the great effort. Is is possible to share the  
compilation steps? 

  
 rgds,
 CL
  
    
   On Mon, 04 Nov 2019 22:40:20 +0800  
 wrote 

   


Did you test the Atoms stuff ?

Heinz Nabielek  a écrit :


On 04.11.2019, at 14:55, stephane.motte...@utc.fr wrote:

Thanks Samuel. So the regexp error can eventually have the  
same cause (libcurl version mismatch). I have packaged a  
scilab-6.0.2 without these libraries (and removing the 10.15  
warning) for OSX users at the following URL:


https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/www.utc.fr/~mottelet/scilab/download/6.0.2/scilab-6.0.2-x86_64-2019-11-04.dmg[2]

CL, Heinz, Willi can you test it ?


 Works to perfection and without this funny warning.
  
  

I recommend temporary renaming/moving your  
.Scilab/scilab-6.0.2 directory before testing


 Thanks. Very helpful. Great suggestion. I would  
not have thought of it…..

  
 Thanks for your dedication to this work.Heinz



 

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


  



 



 

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


    




Liens:
--
[1]  
https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/www.utc.fr/~mottelet/scilab/download/6.0.2/scilab-6.0.2-x86_64-2019-11-04.dmg
[2]  
https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/www.utc.fr/~mottelet/scilab/download/6.0.2/scilab-6.0.2-x86_64-2019-11-04.dmg
[3]  
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

Re: [Scilab-users] Scilab cannot work on macOS 10.15 Catalina: Any progress in sight?

[stephane . mottelet]

 Obviously, between points 3 and 4 I moved the Scilab app from the  
archive in the Appplication folder.


stephane.motte...@utc.fr a écrit :


Hello,

I don't have the regexp error. Here is my complete workflow:

1 - Delete the eventual previous Sciab 6.0.2 I had in the  
/Applications/ folder 

2 - Delete my .Scilab folder
3 - extract the .dmg I downloaded  
from http://www.utc.fr/~mottelet/scilab/download/6.0.2/scilab-6.0.2-x86_64-2019-11-04.dmg
4 - double click the Scilab icon (with first launch usual but  
annoying details...)

5 - click the ATOMS gui icon or type atomsList at Scilab prompt

Concerning the problem with IPCV (and maybe other packages with  
gateways, I only tested IPCV), I did not address it in the above  
archive. I only modified the scilab script (I will create a commit  
on codereview.scilab.org) and removed the libcurl.dylib that was  
shipped in lib/thirdparty folder.


Best,

S.

  Chin Luh Tan  a écrit :


Hi, 
 
from my end:
 
1. The warning for the 10.15 gone. 
2. First launch from the app still give the regexp error when  
running atomsList, but after running one time from terminal and get  
it run successfully, I could run it from the app as after all. 
3. atomsInstall for the module with gateway folder still  
extracted to 2 separate folders which need to be manually move in  
order for it to run. No issue for macros only module. 

 
Thanks for the great effort. Is is possible to share the  
compilation steps? 

 
rgds,
CL


  On Mon, 04 Nov 2019 22:40:20 +0800  
 wrote 



Did you test the Atoms stuff ?

Heinz Nabielek  a écrit :


On 04.11.2019, at 14:55, stephane.motte...@utc.fr wrote:

Thanks Samuel. So the regexp error can eventually have the same  
cause (libcurl version mismatch). I have packaged a scilab-6.0.2  
without these libraries (and removing the 10.15 warning) for OSX  
users at the following URL:


https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/www.utc.fr/~mottelet/scilab/download/6.0.2/scilab-6.0.2-x86_64-2019-11-04.dmg[1]

CL, Heinz, Willi can you test it ?


Works to perfection and without this funny warning.

I recommend temporary renaming/moving your .Scilab/scilab-6.0.2  
directory before testing


Thanks. Very helpful. Great suggestion. I would not have thought of it…..

Thanks for your dedication to this work.Heinz



 

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


 



 




Liens:
--
[1]  
https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/www.utc.fr/~mottelet/scilab/download/6.0.2/scilab-6.0.2-x86_64-2019-11-04.dmg
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Scilab cannot work on macOS 10.15 Catalina: Any progress in sight?

[stephane . mottelet]

 Hello,

I don't have the regexp error. Here is my complete workflow:

1 - Delete the eventual previous Sciab 6.0.2 I had in the  
/Applications/ folder 

2 - Delete my .Scilab folder
3 - extract the .dmg I downloaded  
from http://www.utc.fr/~mottelet/scilab/download/6.0.2/scilab-6.0.2-x86_64-2019-11-04.dmg
4 - double click the Scilab icon (with first launch usual but annoying  
details...)

5 - click the ATOMS gui icon or type atomsList at Scilab prompt

Concerning the problem with IPCV (and maybe other packages with  
gateways, I only tested IPCV), I did not address it in the above  
archive. I only modified the scilab script (I will create a commit on  
codereview.scilab.org) and removed the libcurl.dylib that was shipped  
in lib/thirdparty folder.


Best,

S.

 Chin Luh Tan  a écrit :


Hi, 
    
   from my end:
    
   1. The warning for the 10.15 gone. 
   2. First launch from the app still give the regexp error when  
running atomsList, but after running one time from terminal and get  
it run successfully, I could run it from the app as after all. 
   3. atomsInstall for the module with gateway folder still  
extracted to 2 separate folders which need to be manually move in  
order for it to run. No issue for macros only module. 

    
   Thanks for the great effort. Is is possible to share the  
compilation steps? 

    
   rgds,
   CL


 On Mon, 04 Nov 2019 22:40:20 +0800   
 wrote 



Did you test the Atoms stuff ?

Heinz Nabielek  a écrit :


On 04.11.2019, at 14:55, stephane.motte...@utc.fr wrote:

Thanks Samuel. So the regexp error can eventually have the same  
cause (libcurl version mismatch). I have packaged a scilab-6.0.2  
without these libraries (and removing the 10.15 warning) for OSX  
users at the following URL:


https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/www.utc.fr/~mottelet/scilab/download/6.0.2/scilab-6.0.2-x86_64-2019-11-04.dmg[1]

CL, Heinz, Willi can you test it ?


Works to perfection and without this funny warning.

I recommend temporary renaming/moving your .Scilab/scilab-6.0.2  
directory before testing


Thanks. Very helpful. Great suggestion. I would not have thought of it…..

Thanks for your dedication to this work.Heinz



 

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


    




Liens:
--
[1]  
https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/www.utc.fr/~mottelet/scilab/download/6.0.2/scilab-6.0.2-x86_64-2019-11-04.dmg
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Scilab cannot work on macOS 10.15 Catalina: Any progress in sight?

[stephane . mottelet]

 Did you test the Atoms stuff ?

Heinz Nabielek  a écrit :


On 04.11.2019, at 14:55, stephane.motte...@utc.fr wrote:
Thanks Samuel. So the regexp error can eventually have the same  
cause (libcurl version mismatch). I have packaged a scilab-6.0.2  
without these libraries (and removing the 10.15 warning) for OSX  
users at the following URL:


https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/www.utc.fr/~mottelet/scilab/download/6.0.2/scilab-6.0.2-x86_64-2019-11-04.dmg

CL, Heinz, Willi can you test it ?


Works to perfection and without this funny warning.

I recommend temporary renaming/moving your .Scilab/scilab-6.0.2  
directory before testing


Thanks. Very helpful. Great suggestion. I would not have thought of it…..

Thanks for your dedication to this work.Heinz
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Scilab cannot work on macOS 10.15 Catalina: Any progress in sight?

[stephane . mottelet]

 I made the test from the command line. However, I think the regexp  
problem (which I didn't have) has a different origin.


S.

Chin Luh Tan  a écrit :


hi,
    
   as willi suggested, hv u tried to launch the scilab from terminal  
and run the command again?

    
   thanks.
    
   rdgs,
CL


 On Mon, 04 Nov 2019 20:31:24 +0800   
 wrote 


Thanks Heinz, this is weird. In fact the problem comes from the  
libcurl which is bundled with Scilab. I think the lib was bundled  
for historical reasons (libcurl was likely needed for old OSX  
versions).


Since the problem occurs for a Catalina clean install, without any  
additionnal software such as Xcode, developper tools, command line  
tools (which could eventually install a different curl binary), I  
think we should remove these libraries from  
SCI/../../lib/thirdparty/, or at least change the order in the  
DYLD_LIBRARY_PATH in the bin/scilab script.


S.

Heinz Nabielek  a écrit :


On 04.11.2019, at 12:58, stephane.motte...@utc.fr wrote:


atomsList


Never used atoms nor do I know, what they are good for, but my  
6.02 in Catalina gives


--> atomsList
                       animaGIF - stand-alone creation of an  
animated GIF image from images files or from a live figure

                    ANN_Toolbox - Artificial Neural Network toolbox
                         apifun - Check input arguments in macros

Altogether 66 lines.

Is there something that I can check for you?Heinz



 

___
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 cannot work on macOS 10.15 Catalina: Any progress in sight?

[stephane . mottelet]

 Thanks Heinz, this is weird. In fact the problem comes from the  
libcurl which is bundled with Scilab. I think the lib was bundled for  
historical reasons (libcurl was likely needed for old OSX versions).


Since the problem occurs for a Catalina clean install, without any  
additionnal software such as Xcode, developper tools, command line  
tools (which could eventually install a different curl binary), I  
think we should remove these libraries from SCI/../../lib/thirdparty/,  
or at least change the order in the DYLD_LIBRARY_PATH in the  
bin/scilab script.


S.

Heinz Nabielek  a écrit :


On 04.11.2019, at 12:58, stephane.motte...@utc.fr wrote:

atomsList


Never used atoms nor do I know, what they are good for, but my 6.02  
in Catalina gives


--> atomsList
                       animaGIF - stand-alone creation of an  
animated GIF image from images files or from a live figure

                    ANN_Toolbox - Artificial Neural Network toolbox
                         apifun - Check input arguments in macros

Altogether 66 lines.

Is there something that I can check for you?Heinz
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Scilab cannot work on macOS 10.15 Catalina: Any progress in sight?

[stephane . mottelet]

 Hello,

Concerning the ATOMS problems with 6.0.2 on OSX Catalina (Windows  
users please stop reading further... ;-)), I have the following error  
on a freshly installed configuration (dedicated partition on my  
machine):


Scilab 6.0.2 (Aug 19 2019, 11:47:50)

  

 --> ATOMSLIST

 atomsDownload: The following file hasn't been downloaded:

 - URL      : 'http://atoms.scilab.org/6.0/TOOLBOXES/64/macosx.gz'

 - Local location :  
'/private/var/folders/pp/hrld62h917x_ccf55yzn78z0gn/T/SCI_TMP_1093_DIw7vR/.atoms/1_TOOLBOXES.gz'


 WARNING: error: Wrong type for input argument #1: string expected.

 Scanning repository http://atoms.scilab.org/6.0 ... Skipped

  

 at line   198 of function atomsDESCRIPTIONget (  
/Applications/scilab-6.0.2.app/Contents/MacOS/share/scilab/modules/atoms/macros/atoms_internals/atomsDESCRIPTIONget.sci line 217  
)


 at line    38 of function atomsList           (  
/Applications/scilab-6.0.2.app/Contents/MacOS/share/scilab/modules/atoms/macros/atomsList.sci line 54  
)


  

 All ATOMS repositories scan failed.

In fact the temp folder 

/private/var/folders/pp/hrld62h917x_ccf55yzn78z0gn/T/SCI_TMP_1093_DIw7vR/.atoms

is empty. This is not a network problem as the following command succeeds:
 

 --> GETURL HTTP://ATOMS.SCILAB.ORG/6.0/TOOLBOXES/64/MACOSX.GZ 

  ans  =

  

  

  /Users/mottelet/macosx.gz

 Samuel do you have an idea ?

S.

Chin Luh Tan  a écrit :


Hi Perrichon,
    
   Apologize in advance but I think the this conversation is  
actually solving quite some issues in MacOS and I felt that it could  
be helpful to continue in mailing list. However, I've no objection  
to bring it private as well, please keep me in the loop if it goes  
private. :)

    
   For MacOS users I think they are couple of issues which has been  
resolved (or some workaround) by this thread. Base on the  
conversation, I think we could come out with some guideline which  
could be helpful:

    
   1. for version before High Sierra (10.13), everything works fine,  
from scilab 6.0.1 to 6.0.2, and I could confirm that atomsInstall  
for modules such as IPCV works perfectly on this platform for both  
6.0.1 and 6.0.2

    
   2. with Stephen help, using the patch for Java, Scilab 6.0.2  
could launch on Catalina (10.15) successfully.

    
   3. Issues with atoms on MacOS arise since Majove (10.14),  
including Catalina,  the very same module during the installation  
gives issue, which has been reported here:

   http://forge.scilab.org/index.php/p/ipcv/issues/1919/[1] .
    
   4. This prompt us to explore further, and found out that modules  
with only macros seems ok, but the one with gateway will have this  
issues.

    
   5. We have to emphasis, the very same module works on Scilab  
6.0.2 MacOS High Sierra, It only broke since Majove where the  
extractions of modules seems to be very very different with previous  
version of Mac. I would not say it is MacOS or Scilab issue, but  
obviously it seems to be some changes in MacOS that caused this  
behavior?

    
   In summary, with Stephen's fix, the Scilab 6.0.2 could now run on  
MacOS Catalina, while with Willi finding on the modules folders  
disorganization and how to manually move them around, we could make  
the modules run as well. I think this is quite a great achievement  
so far to provide Mac users a workaround for current issues, and  
let's make it even better in coming release!

    
   Cheers!
    
   Thanks
    
   Regards,
   Chin Luh
    
    
    
    
 On Mon, 04 Nov 2019 06:54:30 +0800 PERRICHON  
 wrote 

 


Hello
Could you continue your conversion in private ?
Thanks for everybody
P.

Before printing, think about ENVIRONMENTAL responsabity

-Message d'origine-
De : users  De la part de Stéphane Mottelet
Envoyé : dimanche 3 novembre 2019 21:55
À : users@lists.scilab.org
Objet : Re: [Scilab-users] Scilab cannot work on macOS 10.15  
Catalina: Any progress in sight?


I meant

[version, opts] = getversion()

Le 03/11/2019 à 21:44, Stéphane Mottelet a écrit :



Le 3 nov. 2019 à 20:48, knobs  a écrit :

Hi,

I had worked on CelestLab and different CV packages and compiled them
in Sierra or High Sierra (not sure anymore). IPCV and SciCV. Both are
now readily available... No more need to compile them ;-)

I am not compiling SciLab from scratch. That would be beyond my
capabilities.

I only use Homebrew. No Fink no MacPorts. So far I am very happy
with what I can find on Homebrew.

There are still issues with ATOMS when start it through the Menu.
Starting scilab through the Terminal window helped populating and
downloading the list of package and categories. After that I can
start the ATOMS GUI when starting SciLab as an app. I can hence  
confirm Chin Luh Tan's experience.


E.g. CelestLab could be installed through the Menu and the GUI. No
issues at all. After the SciLab restart, I could not install IPCV or
other toolboxes this way. Different messages. Typically it cannot
find 

Re: [Scilab-users] c link (mingw)

[stephane . mottelet]

 I think that your installation of mingw toolbox is broken, as the error 
 

!C:\Users\jkopac\AppData\Roaming\Scilab\scilab-6.0.2\mingwlib_x64/liblibf2c.a: file not recognized: File format not recognized                                          
 !
!                                                                     
                     



looks like an architecture mismatch (32 vs 64 bits). When you install  
the gcc package *before* installing the mingw atoms package (it has to  
be done in that order) , when you exit the relauch Scilab, during the  
first startup of mingw package, some libraries are converted  
(transcript below):

 
 Mingw Compiler support for Scilab
 Load macros
 Converting Libraries.
 Build libblasplus.a
 Build liblibf2c.a
 Build libcore.a
 Build libcore_f.a
 Build liblapack.a
 Build liboutput_stream.a
 Build libdynamic_link.a
 Build libinteger.a
 Build liboptimization_f.a
 Build liblibjvm.a
 Build libscilocalization.a
 Build liblinpack_f.a
 Build libcall_scilab.a
 Build libtime.a
 Build libapi_scilab.a
 Build liblibintl.a
 Build libast.a
 Build libfileio.a
 Build libio.a
 Build libstring.a
 Build libthreads.a
 Build libsciconsole.a
 Build libscilab_windows.a
 Build liblibmex.a
 Build libscicos.a
 Build libscicos-cli.a
 Build libscicos_f.a
 Build libscicos_blocks.a
 Build libscicos_blocks-cli.a
 Build libscicos_blocks_f.a
 Load help

If you have never seen this, I think that there is something wrong.  
Please also check that you have a 64bit Scilab.


S.



Jakub Kopac  a écrit :


I tried example from the call help page.
   results from ilib_build help page:
    
       Generate a gateway file
   Generate a loader file
   Generate a Makefile
   Running the makefile
   Compilation of build_c.obj
   Compilation of build_c.obj
   Compilation of build_c.obj
   Compilation of fun1.obj
   Compilation of fun2.obj
   Compilation of sci_fun1.obj
   Building shared library (be patient)

!- Compile file build_c.cpp --                
                                                                     
                               !
!                                                                    
                                                                     
                                !
!x86_64-w64-mingw32-g++.exe -c -DWIN32 -DSTRICT -DFORDLL -D_MSC_VER  
-I"C:/NONINS~1/SCILAB~1.2/libs/MALLOC/includes"  
-I"C:/NONINS~1/SCILAB~1.2/libs/f2c" -I"C:/NONINS~1/S!
!CILAB~1.2/libs/intl"  
-I"C:/NONINS~1/SCILAB~1.2/modules/core/includes"  
-I"C:/NONINS~1/SCILAB~1.2/modules/api_scilab/includes"  
-I"C:/NONINS~1/SCILAB~1.2/modules/call_sci!
!lab/includes"  
-I"C:/NONINS~1/SCILAB~1.2/modules/output_stream/includes"  
-I"C:/NONINS~1/SCILAB~1.2/modules/jvm/includes"  
-I"C:/NONINS~1/SCILAB~1.2/modules/localization/!
!includes" -I"C:/NONINS~1/SCILAB~1.2/modules/dynamic_link/includes"  
-I"C:/NONINS~1/SCILAB~1.2/modules/mexlib/includes"  
-I"C:/NONINS~1/SCILAB~1.2/modules/time/includes" !
!-I"C:/NONINS~1/SCILAB~1.2/modules/windows_tools/includes"  
-I"C:/NONINS~1/SCILAB~1.2/modules/threads/includes"  
-I"C:/NONINS~1/SCILAB~1.2/modules/ast/includes/ast" -I"C:!
!/NONINS~1/SCILAB~1.2/modules/ast/includes/exps"  
-I"C:/NONINS~1/SCILAB~1.2/modules/ast/includes/operations"  
-I"C:/NONINS~1/SCILAB~1.2/modules/ast/includes/parse" -I"C:/!
!NONINS~1/SCILAB~1.2/modules/ast/includes/symbol"  
-I"C:/NONINS~1/SCILAB~1.2/modules/ast/includes/system_env"  
-I"C:/NONINS~1/SCILAB~1.2/modules/ast/includes/types" -I"C:!
!/NONINS~1/SCILAB~1.2/modules/ast/includes/analysis"  
-I"C:/NONINS~1/SCILAB~1.2/modules/string/includes"  
-I"C:/NONINS~1/SCILAB~1.2/modules/console/includes" -m64 -D__SCI!
!LAB_TOOLBOX__  -DNDEBUG  build_c.cpp                                
                                                                     
                                !
!                                                                    
                                                                     
                                !
!build_c.cpp: In function 'int build_c(wchar_t*)':                    
                                                                     
                               !
!                                                                    
                                                                     
                                !
!build_c.cpp:11:5: warning: 'int build_c(wchar_t*)' redeclared  
without dllimport attribute: previous dllimport ignored  
[-Wattributes]                                   !
!                                                                    
                                                                     
                                !
! int build_c(wchar_t* _pwstFuncName)                                
                                                                     
                                !
!                                                                    
                             

Re: [Scilab-users] c link (mingw)

[stephane . mottelet]

 With officially supported version 6.2.0 (download link on the atoms  
page of mingw toolbox), under Windows 7, I run without any problem all  
examples on ilib_build help page.


S.

Quoting Stéphane Mottelet :


Hello

Which version of gcc did you download from equation.com ?

S.


Le 25 sept. 2019 à 21:01, kjubo  a écrit :

Dear all,

I am trying to make a c code.
I instaled mingw (from equation.com) and MinGw toolbox from ATOMS.

When I try to use a example code from call help page, I get following error:
(full scilab console print)

   Generate a loader file
  Generate a Makefile
  Running the Makefile
  Compilation of fooc.obj
  Building shared library (be patient)

- Compile file fooc.c --
!

!
x86_64-w64-mingw32-gcc.exe -c -DWIN32 -DSTRICT -DFORDLL -D_MSC_VER
-I"C:/NONINS~1/SCILAB~1.2/libs/MALLOC/includes"!
-I"C:/NONINS~1/SCILAB~1.2/libs/f2c" -I"C:/NONINS~1/SCILAB~1.2/libs/intl"
-I"C:/NONINS~1/SCILAB~1.2/modules/core/i!
ncludes" -I"C:/NONINS~1/SCILAB~1.2/modules/api_scilab/includes"
-I"C:/NONINS~1/SCILAB~1.2/modules/call_scilab/incl!
udes" -I"C:/NONINS~1/SCILAB~1.2/modules/output_stream/includes"
-I"C:/NONINS~1/SCILAB~1.2/modules/jvm/includes" -I!
"C:/NONINS~1/SCILAB~1.2/modules/localization/includes"
-I"C:/NONINS~1/SCILAB~1.2/modules/dynamic_link/includes" -I!
"C:/NONINS~1/SCILAB~1.2/modules/mexlib/includes"
-I"C:/NONINS~1/SCILAB~1.2/modules/time/includes" -I"C:/NONINS~1/S!
CILAB~1.2/modules/windows_tools/includes"
-I"C:/NONINS~1/SCILAB~1.2/modules/threads/includes" -I"C:/NONINS~1/SCILA!
B~1.2/modules/ast/includes/ast"
-I"C:/NONINS~1/SCILAB~1.2/modules/ast/includes/exps"
-I"C:/NONINS~1/SCILAB~1.2/mod!
ules/ast/includes/operations"
-I"C:/NONINS~1/SCILAB~1.2/modules/ast/includes/parse"
-I"C:/NONINS~1/SCILAB~1.2/modu!
les/ast/includes/symbol"
-I"C:/NONINS~1/SCILAB~1.2/modules/ast/includes/system_env"
-I"C:/NONINS~1/SCILAB~1.2/modu!
les/ast/includes/types"
-I"C:/NONINS~1/SCILAB~1.2/modules/ast/includes/analysis"
-I"C:/NONINS~1/SCILAB~1.2/modules!
/string/includes" -I"C:/NONINS~1/SCILAB~1.2/modules/console/includes" -m64
-D__SCILAB_TOOLBOX__  -DNDEBUG  fooc.c !

!
- Link files --
!

!
x86_64-w64-mingw32-g++.exe --shared fooc.o -std=c++11 -L"c:\program
files\gcc\x86_64-w64-mingw32\lib" -LC:\Users\j!
kopac\AppData\Roaming\Scilab\scilab-6.0.2\mingwlib_x64 -lgfortran -lblasplus
-llibf2c -lcore -lcore_f -llapack -lo!
utput_stream -ldynamic_link -linteger -loptimization_f -llibjvm
-lscilocalization -llinpack_f -lcall_scilab -ltime!
-lapi_scilab -llibintl -last -lfileio -lio -lstring -lthreads -lsciconsole
-lscilab_windows -llibmex  -o libfooc.!
dll  -Wl,--out-implib=libfooc.a -Wl,--export-all-symbols
-Wl,--enable-auto-import                                 !

!
C:\Users\jkopac\AppData\Roaming\Scilab\scilab-6.0.2\mingwlib_x64/liblibf2c.a:
file not recognized: File format not!
recognized
!

!
collect2.exe: error: ld returned 1 exit status
!

!
Makelib:127: recipe for target 'libfooc.dll' failed
!

!
make: *** [libfooc.dll] Error 1
!
at line    25 of function dlwCompile    (
C:\NONINS~1\SCILAB~1.2\contrib\mingw\010~1.5\macros\windows\dlwCompile.sci
line 34 )
at line    70 of function ilib_compile  (
C:\NONINSTALL\scilab-6.0.2\modules\dynamic_link\macros\ilib_compile.sci line
86 )
at line   104 of function ilib_for_link (
C:\NONINSTALL\scilab-6.0.2\modules\dynamic_link\macros\ilib_for_link.sci
line 118 )
at line    18 of executed file C:\Users\XXX\Documents\SciLab\c experiment\z
helpu\test_help_call.sce

ilib_compile: Error while executing Makelib

Can anybody help, how to make it works?
(SciLab 6.0.2 on Win 7 PRO, 64 bit)

thanks!

BR
JK

--
Sent from:  
https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html

___
users mailing list
users@lists.scilab.org
https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users


___
users mailing list
users@lists.scilab.orghttps://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

Re: [Scilab-users] ?=Re: ?=Re: ?=Re: ?==?utf-8?q?

[stephane . mottelet]

 See http://bugzilla.scilab.org/show_bug.cgi?id=14486

Quoting Antoine Monmayrant :


OK, so it might not be os specific.
It might be a good idea to fill a bug report to say that  
parallel_run is not available, contrary to what's in the  
documentation.
If you fill a bug, I'll be happy to confirm it for the linux side of  
the world...


Antoine

Le Lundi, Septembre 23, 2019 18:03 CEST, fujimoto2005  
 a écrit:



Dear  Antoine

I am using  windows  7.

Best regards

--
Sent from:  
https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/mailinglists.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.orghttps://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

Re: [Scilab-users] ?= Re: ?= =?utf-8?q? parallel_run

[stephane . mottelet]

 Hello Antoine,

Before judging that some code is just a "dirty hack" you should first  
get into the code and see hows things are written. The implementation  
in 5.5.2 was using OpenMP so I don't see anything dirty here. The  
implementation was unstable under OSX and Linux, and under Windows  
parallel_run was just making calls sequentially. So no "dirty hack"  
under Windows but just a shortcut. Octave does also the same with  
Matlatb's parfor : it just does things sequentially. However, even  
unstable, parallel_run was very useful (I used it a lot under Linux to  
do some Monte Carlo estimation on a 40 processor machine). It is a  
pity that it's re-engineering for 6.0 familiy was not a priority. 


S. 

Quoting Antoine Monmayrant :


Hello,

Are you using Windows or anything else?
Because as far as I remember, parallel_run is just a dirty hack that  
only works under windows.

On my linux install of scilab 6.0.2, I also have:
--> parallel_run

Undefined variable: parallel_run

So it might be a bug in the documentation that should mention  
"windows only" like some other functions.


Antoine

Le Lundi, Septembre 23, 2019 15:46 CEST, fujimoto2005  
 a écrit:



I wanted to use "parallel_run" and tried the sample script in the help page.
But it did not work with the error message "undefined
variable:parallel_run".
Please teach me what is wrong?

The sample script I used is as follows
**
for i = 1:10
  res(i) = i*i;
end;
// for parallel_run, we need to have a function performing the computation
function a=g(arg1)
  a=arg1*arg1
endfunction

res = parallel_run(1:10, g);
// => res = [1  4  9  16  25  36  49  64  81  100];
*

--
Sent from:  
https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/mailinglists.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.orghttps://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

Re: [Scilab-users] Generating a boolean vector or matrix

[stephane . mottelet]

 When I say ineficient, I mean that kind of behavior:

--> tic;repmat(uint8(0),1,1);toc
 ans  =

   1.622535

compared to proposed implementation:

--> tic;a=zeros(1,1,"uint8");toc
 ans  =

   0.063472

S.

Quoting Stéphane Mottelet :


Le 05/09/2019 à 08:55, Lamy Alain a écrit :


Hi,

 

 

 

 

I’m not convinced the new syntax: ones(n, m, “boolean”) is a  
good idea or is necessary because it makes “integer” (“constant”)  
and “boolean” 2 identical types.


Sorry Alain can you explain it further ?


 

 

There is a simple way to do the same :

 

repmat(%t, n, m)


  Yeah, there are many other (ineficient) ways, but the average user  
would appreciate to have one and only one function (here "zeros") to  
initialize a matrix regardless is type.



 

 

 

 

 

Alain

 

 

 

 

   ___ users mailing  
list  
users@lists.scilab.orghttps://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users[1]


--  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[2]




Links:
--
[1]  
https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users
[2]  
https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/www.utc.fr/~mottelet
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] A possible bug with format(width)

[stephane . mottelet]

 Scilab 6.0.1 does it as follows:
  
  --> format(4); u=123.456
   u  = 
   
     1.0  D+02
  
 The display of Scilab 5.5.2 does not respect the format length  
either,  because " 123." has length 5 (blank sign +123 + dot)

  
 S.


Quoting Samuel Gougeon :


Le 05/06/2019 à 21:57, stephane.motte...@utc.fr a écrit :


 


 As MacOSX, Linux is not affected, this will help to solve this bug:

 Scilab 6.0.2 (Feb 14 2019, 10:11:47)

 --> OS_VERSION

  ans  =

  Linux 4.15.0-48-generic

 --> FORMAT(4); U=123.456

  u  = 

    1.D+02

  

 Are you in "v" format? This result looks like to be in "e" one, and  
anyway it does not comply with the required width.

On win7 with 5.5.2 we get in "v" format:
-->format(4); u=123.456
 u  =
   123. 
=> it does not switch to "e" format.
 
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] A possible bug with format(width)

[stephane . mottelet]

 As MacOSX, Linux is not affected, this will help to solve this bug:

 Scilab 6.0.2 (Feb 14 2019, 10:11:47)

  

 --> OS_VERSION

  ans  =

  

  Linux 4.15.0-48-generic

  

 --> FORMAT(4); U=123.456

  u  = 

  

    1.D+02

 S.

Quoting Samuel Gougeon :


Hello Izabela,
   
  Le 05/06/2019 à 16:38, Izabela Wójcik-Grząba a écrit :


.../...
With format(4) and attempt to display a variable u Scilab stops  
working. Does everyone have such behaviour and isn't it a bug?


  Confirmed behavior on win7 64 bits. Sure it is a bug, a serious one.
You would be kind to report it on bugzilla.

Regards
Samuel

PS : the bug 14653[1] may also be considered.
 




Links:
--
[1]  
https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/bugzilla.scilab.org/show_bug.cgi?id=14653
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

[Scilab-users] Scilab 6.0.1 and OSX Mojave

[stephane . mottelet]

 rickygz...@gmail.com a écrit :


I need your help, with the new Mojave update and running scilab,

I fully don´t understand what to do, please I really need to use  
this application, I have to go to the terminal, and then I couldn't  
do anything, it displays that this system may fail, and only  
supported by mountain lion to high sierra


Need your help ASAP

_Sent from  
https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/mailinglists.scilab.org


Hello,

You have to remove some libraries bundled with Scilab. In order that  
you just have to copy/paste the following commands, make sure that you  
have copied scilab 6.0.1 to the /Applications folder:


rm /Applications/scilab-6.0.1.app/Contents/MacOS/lib/thirdparty/libBLAS.dylib

 rm /Applications/scilab-6.0.1.app/Contents/MacOS/lib/thirdparty/libz.1.dylib

After removing these libraries, Scilab should start. However, you may  
be prompted to install an old Java version, which is available at the  
following url: 


https://support.apple.com/kb/dl1572

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

Re: [Scilab-users] Any chance SciLab 6 operational again under macOS 10.14?

[stephane . mottelet]

 Hello,

It seems that you still have a libBLAS.dylib file in /

Please confirm that with a

$ ls -l /

If confirmed, delete this file.

S.


Heinz Nabielek  a écrit :

I have the Scilab 6.0.1 icon in the dock, but still does not  
startup. Java 1.6 also a problem, because "newer version is already  
installed".


From the command line, I get the messages as below...

/Applications/scilab-6.0.1.app/Contents/MacOS/bin/scilab[1] -nw

dyld: Symbol not found: _double_general_add
Referenced from:  
/System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib

Expected in: /libBLAS.dylib
in  
/System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib
/Applications/scilab-6.0.1.app/Contents/MacOS/bin/scilab[1]: line  
972:  1137 Abort trap: 6           "$SCILABBIN" "$@"



On 30.08.2018, at 21:48, stephane.motte...@utc.fr wrote:

stephane.motte...@utc.fr a écrit :


Heinz Nabielek  a écrit :


System Version:        macOS 10.14 (18A377a)
Kernel Version:        Darwin 18.0.0
Darwin Kernel Version 18.0.0: Wed Aug 22 20:59:21 PDT 2018;  
root:xnu-4903.201.2~4/RELEASE_X86_64 x86_64

Apple LLVM version 9.1.0 (clang-902.0.39.2)
Target: x86_64-apple-darwin18.0.0
Thread model: posix
InstalledDir:  
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin[2]


Any chance SciLab 6 operational again under macOS 10.14?
Heinz
___
users mailing list
users@lists.scilab.orghttps://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users


Hello,

Tonight I installed the latest Mojave beta on a second partition  
of my Mac Book disk and were able to run Scilab. Here is how I  
proceeded:


1-The OS has been installed on a new partition without any old data import
2-I installed the command line tools (open a Terminal the type  
"make" to trigger the download/install)
3-Downloaded the official 6.0.1 for OSX from scilab.org and move  
the app in /Applications

4-Deleted some libraries bundled by Scilab:

$  rm  
/Applications/scilab-6.0.1.app/Contents/MacOS/lib/thirdparty/libBLAS.dylib[3]
$  rm  
/Applications/scilab-6.0.1.app/Contents/MacOS/lib/thirdparty/libz.*[4]


5-Commented out the line  774 in  
/Applications/scilab-6.0.1.app/Contents/MacOS/bin/scilab[1]


                    #fail_macosx_version

6-Launched Scilab from its icon. At first run, you will be asked  
to install Java 1.6


See the attached screenshot.

S.


I forgot to say something in step 5. Change Line 803 as follows  
(add 14, the OSX minor version number)


                10|11|12|13|14)

S.
___
users mailing list
users@lists.scilab.orghttps://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users


 




Liens:
--
[1] http://scilab-6.0.1.app/Contents/MacOS/bin/scilab
[2]  
http://Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

[3] http://scilab-6.0.1.app/Contents/MacOS/lib/thirdparty/libBLAS.dylib
[4] http://scilab-6.0.1.app/Contents/MacOS/lib/thirdparty/libz.*
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Any chance SciLab 6 operational again under macOS 10.14?

[stephane . mottelet]

 stephane.motte...@utc.fr a écrit :


Heinz Nabielek  a écrit :


System Version:        macOS 10.14 (18A377a)
Kernel Version:        Darwin 18.0.0
Darwin Kernel Version 18.0.0: Wed Aug 22 20:59:21 PDT 2018;  
root:xnu-4903.201.2~4/RELEASE_X86_64 x86_64

Apple LLVM version 9.1.0 (clang-902.0.39.2)
Target: x86_64-apple-darwin18.0.0
Thread model: posix
InstalledDir:  
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin[1]


Any chance SciLab 6 operational again under macOS 10.14?
Heinz
___
users mailing list
users@lists.scilab.orghttps://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users



Hello,

Tonight I installed the latest Mojave beta on a second partition of  
my Mac Book disk and were able to run Scilab. Here is how I proceeded:


1-The OS has been installed on a new partition without any old data import
2-I installed the command line tools (open a Terminal the type  
"make" to trigger the download/install)
3-Downloaded the official 6.0.1 for OSX from scilab.org and move the  
app in /Applications

4-Deleted some libraries bundled by Scilab:

$  rm  
/Applications/scilab-6.0.1.app/Contents/MacOS/lib/thirdparty/libBLAS.dylib

$  rm /Applications/scilab-6.0.1.app/Contents/MacOS/lib/thirdparty/libz.*

5-Commented out the line  774 in  
/Applications/scilab-6.0.1.app/Contents/MacOS/bin/scilab

   

                      #fail_macosx_version
 
  6-Launched Scilab from its icon. At first run, you will be asked  
to install Java 1.6


See the attached screenshot.

S.

   


I forgot to say something in step 5. Change Line 803 as follows (add  
14, the OSX minor version number)


                10|11|12|13|14) S.


Liens:
--
[1]  
https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Any chance SciLab 6 operational again under macOS 10.14?

[stephane . mottelet]

 Heinz Nabielek  a écrit :


System Version:        macOS 10.14 (18A377a)
Kernel Version:        Darwin 18.0.0
Darwin Kernel Version 18.0.0: Wed Aug 22 20:59:21 PDT 2018;  
root:xnu-4903.201.2~4/RELEASE_X86_64 x86_64

Apple LLVM version 9.1.0 (clang-902.0.39.2)
Target: x86_64-apple-darwin18.0.0
Thread model: posix
InstalledDir:  
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin[1]


Any chance SciLab 6 operational again under macOS 10.14?
Heinz
___
users mailing list
users@lists.scilab.orghttps://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users


Hello,

Tonight I installed the latest Mojave beta on a second partition of my  
Mac Book disk and were able to run Scilab. Here is how I proceeded:


1-The OS has been installed on a new partition without any old data import
2-I installed the command line tools (open a Terminal the type "make"  
to trigger the download/install)
3-Downloaded the official 6.0.1 for OSX from scilab.org and move the  
app in /Applications

4-Deleted some libraries bundled by Scilab:

$  rm  
/Applications/scilab-6.0.1.app/Contents/MacOS/lib/thirdparty/libBLAS.dylib

$  rm /Applications/scilab-6.0.1.app/Contents/MacOS/lib/thirdparty/libz.*

5-Commented out the line  774 in  
/Applications/scilab-6.0.1.app/Contents/MacOS/bin/scilab  

                    #fail_macosx_version

 6-Launched Scilab from its icon. At first run, you will be asked to  
install Java 1.6


See the attached screenshot.

S.



Liens:
--
[1]  
http://Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] More rapid calculation

[stephane . mottelet]

 Here is an example where 100% CPU is used (4 cores) with pure linear algebra.

S.

Quoting stephane.motte...@utc.fr:

If your program does not take advantage of the MKL Intel library, it  
means that its CPU usage is not dominated by linear algebra stuff.  
If you don't tell us more we won't be able to help...


S.

Quoting fujimoto2005 :


Dear Mottellet

But there is an explanation "If we use the Intel MKL on Windows, then Scilab
use all the cores available on the processor. "
https://wiki.scilab.org/Documentation/ParallelComputingInScilab

So I expected there are some ways to increase the usage of cpu.

--
Sent from:  
http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html

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



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

Re: [Scilab-users] More rapid calculation

[stephane . mottelet]

 Here is an example (pure linear algebra) using 100% cpu (4 cores) :

http://www.utc.fr/~mottelet/Images/cpu.png

S.

Quoting stephane.motte...@utc.fr:

If your program does not take advantage of the MKL Intel library, it  
means that its CPU usage is not dominated by linear algebra stuff.  
If you don't tell us more we won't be able to help...


S.

Quoting fujimoto2005 :


Dear Mottellet

But there is an explanation "If we use the Intel MKL on Windows, then Scilab
use all the cores available on the processor. "
https://wiki.scilab.org/Documentation/ParallelComputingInScilab

So I expected there are some ways to increase the usage of cpu.

--
Sent from:  
http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html

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



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

Re: [Scilab-users] More rapid calculation

[stephane . mottelet]

 If your program does not take advantage of the MKL Intel library, it  
means that its CPU usage is not dominated by linear algebra stuff. If  
you don't tell us more we won't be able to help...


S.

Quoting fujimoto2005 :


Dear Mottellet

But there is an explanation "If we use the Intel MKL on Windows, then Scilab
use all the cores available on the processor. "
https://wiki.scilab.org/Documentation/ParallelComputingInScilab

So I expected there are some ways to increase the usage of cpu.

--
Sent from:  
http://mailinglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html

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

Re: [Scilab-users] {EXT} need a more efficient and faster code: suggestions welcome

[stephane . mottelet]

 Hello,

Don't even think about using parallel_run under OSX. It used to work  
(with some tweaking) with scilab-5.5.1 under Mavericks, but since  
5.5.2 version, it has become completely unstable.


S.

Heinz  a écrit :


My latest tictoc is 366: would that be 6.1 minutes?
I am away from my 2 iMacs at home and running Scilab on a lowly  
Intel Pentium CPU N3540 @ 2.16GHz Win10 laptop. Your "2.498" for  
40,000 points are phenomenal regarding the fact that the running  
time increases with the square of the number of points.


The later iMac has a Quad-Core-i7 at 3.2 GHz: can I run your code  
version there under the older Scilab? Not that I understand how  
parallel processing works...

Heinz

-Original Message-
From: users [mailto:users-boun...@lists.scilab.org] On Behalf Of  
Stéphane Mottelet

Sent: 31 January 2018 16:12
To: users@lists.scilab.org
Subject: Re: [Scilab-users] {EXT} need a more efficient and faster  
code: suggestions welcome


Dear Heinz,

Here is what can be done in Scilab-5.5.2 to accelerate your  
computations on a multi-core architecture under Linux :


function out=distances(X)
    function out=distance(k)
        this=X(k,:);XX=X;XX(k,:)=[];
        DIFF=XX-ONE*this;
        out=sqrt(min((DIFF.*DIFF)*[1;1;1]));
    endfunction
    n=size(X,1);
    ONE=ones(n-1,1);
    out=parallel_run(1:n,distance);
endfunction

n=4;
r=23;
radius = r*grand(n,1,'def').^(1/3);
phi = 2*%pi*grand(n,1, 'def');
costheta = 1 - 2*grand(n,1, 'def');
radsintheta = radius.*sin(acos(costheta)); X =  
[radsintheta.*cos(phi),radsintheta.*sin(phi), radius.*costheta];


On a modest server (two 10-core/20-threads Intel(R) Xeon(R) CPU E5-2660
v2 @ 2.20GHz = 40 threads),

-->tic;distances(X);toc
ans  =

    13.063

On a smarter server (sixteen 6-core/6-threads Intel(R) Xeon(R) CPU  
X7542 @ 2.67GHz = 96 threads)


-->tic;d=distances(X);toc
ans  =

    2.498

I hope that parallel_run will be available again in the next version  
of scilab.


S.

Le 31/01/2018 à 10:53, Stéphane Mottelet a écrit :

Replacing

    MinDist=[MinDist sqrt(min(sum(DIFF.^2,2)))];

by

    MinDist=[MinDist sqrt(min(sum(DIFF.*DIFF,2)))];

will be at least twice faster. Crunching elapsed time could be done by
using parallel_run (with 5.5.2 version) if you have a multi-core
processor.

S.

Le 31/01/2018 à 09:36, Dang Ngoc Chan, Christophe a écrit :

Hello,

The following suggestions will probably not have a drastic influence
(I don't see how it could be more vectorised) but his a little thing
I see:


De : users [mailto:users-boun...@lists.scilab.org] De la part de
Heinz Nabielek Envoyé : mercredi 31 janvier 2018 00:13

    MinDist=[MinDist sqrt(min(sum(DIFF.^2,2)))];


Maybe you could concatenate the squares of the distance and then
compute the square root of the whole vector in the end:

sqMinDist=[sqMinDist min(sum(DIFF.^2,2))];

…

end

…

MinDist = sqrt(sqMinDist)

Hope this helps,

Regards

--
Christophe Dang Ngoc Chan
Mechanical calculation engineer
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


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

Re: [Scilab-users] Recognition of cursor key as input

[stephane . mottelet]

 Hello,

IMHO, the only way to trap a keypress and get the ascii (?) code is to use
the event_handler callback of a figure :

function handler(x,y,ibut)
//
endfunction

f=gcf();
f.event_handler='handler';
​f.event_handle_enable='on';

On my computer, I have the following mapping 

left arrow pressed : ibut=37 (released=-37)
up arrow : 38
right arrow 39
down arrow 40

The problem is that you need to have a figure opened, and that this figure
must have the focus.

S.

 Jens j.s.st...@hslmg.de a écrit :


Hi Samuel,
ASCII representation of up, down etc. would help me if I knew a Scilab
command which puts the ascii value into a variable. input() is definitely
unable to do so.

Jens

--
View this message in context:


http://mailinglists.scilab.org/Scilab-users-Recognition-of-cursor-key-as-input-tp4031013p4031026.html

Sent from the Scilab users - Mailing Lists Archives mailing list archive
at Nabble.com.
___
users mailing list
users@lists.scilab.orghttp://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Recognition of cursor key as input

[stephane . mottelet]

 Would this small example fit your needs ?

function handler(win,x,y,ibut)
    global _keypress
    if or(ibut==(37:40))
    _keypress=ibut;
    end
endfunction

function key=waitforkeypress()
    global _keypress
    set(gcf(),'event_handler','handler','event_handler_enable','on')
    _keypress=0;
    while ~_keypress
    sleep(1)
    end
    set(gcf(),'event_handler_enable','off')
    key=_keypress;
endfunction

while 1
    select waitforkeypress()
    case 37
    disp('left')
    case 38
    disp('up')
    case 39
    disp('right')
    case 40
    disp('down')   
    break
    end
end

S.

Jens j.s.st...@hslmg.de a écrit :


Hello,
My event_handler experiments with the Scilab help example in Event
handler functions (see below) led to nothing.  I can see the event at
the bottom of the graphic window but I cannot arrest it in a variable. I
tried this:

  function my_eventhandler(win, x, y, ibut)  if ibut==-1000 then
return,end  [x,y]=xchange[1](x,y,'i2f')  xinfo[2](msprintf[3]('Event
code %d at mouse position is (%f,%f)',ibut,x,y))endfunction
plot2d[4]()fig = gcf[5]() ;fig.event_handler = 'my_eventhandler'
;fig.event_handler_enable = on ;//now://   -  move the mouse over the
graphic window//   -  press and release keys shifted or not with Ctrl
pressed or not//   -  press button, wait a little release//   -  press
and release button//   -  double-click button fig.event_handler_enable =
off ; //suppress the event handler  a
href=scilab://scilab.execexample/   a
href=scilab://scilab.editexample/

I fear I must retire to 
m=evstr(x_dialog(...)  Jens






Am 13.08.2014 11:12, schrieb mottelet [via Scilab / Xcos - Mailing Lists
Archives]:


Hello,

IMHO, the only way to trap a keypress and get the ascii (?) code is to
use the event_handler callback of a figure :

function handler(x,y,ibut)
//
endfunction

f=gcf();
f.event_handler='handler';
​f.event_handle_enable='on';

On my computer, I have the following mapping 

left arrow pressed : ibut=37 (released=-37)
up arrow : 38
right arrow 39
down arrow 40

The problem is that you need to have a figure opened, and that this
figure must have the focus.

S.

   Jens [hidden email][6] a écrit :


Hi Samuel,
ASCII representation of up, down etc. would help me if I knew a Scilab
command which puts the ascii value into a variable. input() is
definitely
unable to do so.

Jens

--
View this message in context:


http://mailinglists.scilab.org/Scilab-users-Recognition-of-cursor-key-as-input-tp4031013p4031026.html

Sent from the Scilab users - Mailing Lists Archives mailing list
archive at Nabble.com.
___
users mailing list
[hidden email][7].a
href=orghttp://lists.scilab.org/mailman/listinfo/users;
target=_blankorghttp://lists.scilab.org/mailman/listinfo/users



 

___
users mailing list
[hidden email][8]
http://lists.scilab.org/mailman/listinfo/users

-
   If you reply to this email, your message will be added to the
discussion below:


http://mailinglists.scilab.org/Scilab-users-Recognition-of-cursor-key-as-input-tp4031013p4031030.html

   To unsubscribe from [Scilab-users] Recognition of cursor key as
input, click here[9].
NAML[10]



 

-

  View this message in context: Re: Recognition of cursor key as

input[11]

Sent from the Scilab users - Mailing Lists Archives mailing list
archive[12] at Nabble.com.




Liens:
--
[1] xchange.html
[2] xinfo.html
[3] msprintf.html
[4] plot2d.html
[5] gcf.html
[6] /user/SendEmail.jtp?type=nodenode=4031030i=0
[7] /user/SendEmail.jtp?type=nodenode=4031030i=1
[8] /user/SendEmail.jtp?type=nodenode=4031030i=2
[9]
[10]  
http://mailinglists.scilab.org/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
[11]  
http://mailinglists.scilab.org/Scilab-users-Recognition-of-cursor-key-as-input-tp4031013p4031031.html
[12]  
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