date:20230220

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

2023-02-20 Thread Claus Futtrup


Dear Scilabers

I'm not a professional software developer, but a user of Scilab for more
than 10 years.

I am positive to a 6-month release schedule. I am also a bit surprised,
since last Scilab release was almost two years ago and I'm wondering how
the planned frequent release schedule can be kept.

I am in favor of keeping the versioning the way it has been for many
years, such that a version 7 is only expected for a major release, and
it might be many years in the future before it happens.

Personally I would like to see some releases that make major steps
(leaps) forward, not only bug fixes and minor updates. Incompatible
updates is allowed with major releases, if it serves a purpose.

Best regards,
Claus Futtrup

P.S. I haven't received any email from this mailing list since end of
April 2022.

___
users mailing list - users@lists.scilab.org
Click here to unsubscribe: 
https://lists.scilab.org/mailman/listinfo/users
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/

Re: [Scilab-users] how to convert a scilab 2.5.5 into a 2.6.x script

2023-02-20 Thread Wolfgang Engelmann




Am 20.02.23 um 19:31 schrieb Wolfgang Engelmann:

Hallo, Samuel,

sorry, I was talking about 5.5.2 and 6.1.0

I did not receive the previous answer, but was told that I was not
subscribed to the list. Thanks to whoever managed to get me into the list.

I include a zcos file which was produced with Scilab 5.5.2
If opened with 6.1.0 a short text is shown in the left upper part
outside the actual model.*** This happens with other zcos files produced
with 5.5.2

Wolfgang


ps *** not in the left upper part, but at the right. The text "gain 1"
was below the clock symbol which contains "text" instead of "gain 1"
Wolfgang



Am 20.02.23 um 18:48 schrieb Samuel Gougeon:

Hello Wolfgang,

Didn't you receive this previous answer:
https://www.mail-archive.com/users@lists.scilab.org/msg11008.html ?
I am taking the opportunity of your reminder to ask for more details
about this unusual request:

You write that you are using Scilab 6.1.0, but that you run your 2.5.5
script and get an error under Scilab 2.6.1, which is 22-year old [1].

So, are you using Scilab 6 or Scilab 2?
About

if run under 2.6.1, produce outputs with errors (e.g. changing the
text under items leads to  the text being somewhere outside the model).


what do you mean: which item? Why under it? Which model? Why outside it?
Are you speaking about an Xcos (formerly scicos) file?

It is most often more helpful to share a minimal code (and data)
enabling to directly reproduce the issue, and the full actual error
message, than some abstract or comment about it.

BR
Samuel

[1]  https://www.scilab.org/scilab-version-history

Le 20/02/2023 à 18:21, Wolfgang Engelmann a écrit :
I am new here and hope it is the adequate place to ask this question:

I have a number of scilab 2.5.5 scripts which, if run under 2.6.1,
produce outputs with errors (e.g. changing the text under items leads to
the text being somewhere outside the model).

What can be done in this case?

I use Scilab 6.1.0 and Debian 5.10.162-1
and could supply an example if wanted/appropriate

Wolfgang


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

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

___
users mailing list - users@lists.scilab.org
Click here to unsubscribe: 
https://lists.scilab.org/mailman/listinfo/users
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

Re: [Scilab-users] how to convert a scilab 2.5.5 into a 2.6.x script

2023-02-20 Thread Wolfgang Engelmann


Hallo, Samuel,

sorry, I was talking about 5.5.2 and 6.1.0

I did not receive the previous answer, but was told that I was not
subscribed to the list. Thanks to whoever managed to get me into the list.

I include a zcos file which was produced with Scilab 5.5.2
If opened with 6.1.0 a short text is shown in the left upper part
outside the actual model. This happens with other zcos files produced
with 5.5.2

Wolfgang


Am 20.02.23 um 18:48 schrieb Samuel Gougeon:

Hello Wolfgang,

Didn't you receive this previous answer:
https://www.mail-archive.com/users@lists.scilab.org/msg11008.html ?
I am taking the opportunity of your reminder to ask for more details
about this unusual request:

You write that you are using Scilab 6.1.0, but that you run your 2.5.5
script and get an error under Scilab 2.6.1, which is 22-year old [1].

So, are you using Scilab 6 or Scilab 2?
About

if run under 2.6.1, produce outputs with errors (e.g. changing the
text under items leads to  the text being somewhere outside the model).


what do you mean: which item? Why under it? Which model? Why outside it?
Are you speaking about an Xcos (formerly scicos) file?

It is most often more helpful to share a minimal code (and data)
enabling to directly reproduce the issue, and the full actual error
message, than some abstract or comment about it.

BR
Samuel

[1]  https://www.scilab.org/scilab-version-history

Le 20/02/2023 à 18:21, Wolfgang Engelmann a écrit :
I am new here and hope it is the adequate place to ask this question:

I have a number of scilab 2.5.5 scripts which, if run under 2.6.1,
produce outputs with errors (e.g. changing the text under items leads to
the text being somewhere outside the model).

What can be done in this case?

I use Scilab 6.1.0 and Debian 5.10.162-1
and could supply an example if wanted/appropriate

Wolfgang


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

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/



JOHNSSON-KARLSSON-KHW.zcos
Description: application/scilab-zcos
___
users mailing list - users@lists.scilab.org
Click here to unsubscribe: 
https://lists.scilab.org/mailman/listinfo/users

[Scilab-users] how to convert a scilab 2.5.5 into a 2.6.x script

2023-02-20 Thread Wolfgang Engelmann


I am new here and hope it is the adequate place to ask this question:

I have a number of scilab 2.5.5 scripts which, if run under 2.6.1,
produce outputs with errors (e.g. changing the text under items leads to
the text being somewhere outside the model).

What can be done in this case?

I use Scilab 6.1.0 and Debian 5.10.162-1
and could supply an example if wanted/appropriate

Wolfgang
___
users mailing list - users@lists.scilab.org
Click here to unsubscribe: 
https://lists.scilab.org/mailman/listinfo/users
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/

Re: [Scilab-users] The trajectory of a vector sequence

2023-02-20 Thread Samuel Gougeon


Hello,

Could you check the param3d() function ?
https://help.scilab.org/docs/6.1.1/en_US/param3d.html

x = 0:0.1:4;
y = (x-2).^2;
clf

param3d(x',y',y')

gca().rotation_angles = [60 -60];
set(gce(), "fill_mode","on", "background",color("cyan"))

[cid:part1.KrHaYv5t.sL7d7RpE@free.fr]

Samuel

Le 18/02/2023 à 21:03, 藤本記事 a écrit :
Please tell me how to draw the trajectory of a vector sequence {x(t), 
1<=t<=115} of 3-dimensional row vectors in 3-dimensional space using scilab.
The formula for x(t) is complex, so I store the result of the calculation in a 
115 x 3-dimensional matrix x_M.
x_M(t,:) means x(t).
The command below will create a graph enclosed by a line connecting x_M(1,:) 
and x_M(115,:).
I don't know what to use, if it is correct to use something other than plot3d.
plot3d(x_M(:1),x_M(:,2),x_M(:,3),leg="x1@x2@x3")


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

[Scilab-users] The trajectory of a vector sequence

2023-02-20 Thread 藤本記事

Please tell me how to draw the trajectory of a vector sequence {x(t), 
1<=t<=115} of 3-dimensional row vectors in 3-dimensional space using scilab.
The formula for x(t) is complex, so I store the result of the calculation in a 
115 x 3-dimensional matrix x_M.
x_M(t,:) means x(t).
The command below will create a graph enclosed by a line connecting x_M(1,:) 
and x_M(115,:).
I don't know what to use, if it is correct to use something other than plot3d.
plot3d(x_M(:1),x_M(:,2),x_M(:,3),leg="x1@x2@x3")

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] [Scilab-Dev] Scilab releases schedule / End of Windows 32-bit support

2023-02-20 Thread CHEZE David 227480

Dear all,

I’m not professional software developers while I develop a few Scilab modules 
for internal use in research organization (mostly around energy technologies 
and systems, at building and energy network scale), Stephane’s proposal sounds 
reasonable to cope with various perspectives around Scilab uses and 
developments: while having the year based version is nice to animate the Scilab 
community by raising users curiosity about new features and improvements (++, 
also to promote Scilab to new users and students), regarding previous Scilab 
developments and compatibility issues I feel it is required to keep the ‘true 
version‘ based on technical development requirements (++).
My two cents…

David



De : dev  De la part de Stephane Mottelet
Envoyé : samedi 18 février 2023 16:30
À : List dedicated to the development of Scilab ; Users 
mailing list for Scilab 
Objet : Re: [Scilab-Dev] Scilab releases schedule / End of Windows 32-bit 
support


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

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

Re: [Scilab-users] how to convert a scilab 2.5.5 into a 2.6.x script

Re: [Scilab-users] how to convert a scilab 2.5.5 into a 2.6.x script

[Scilab-users] how to convert a scilab 2.5.5 into a 2.6.x script

Re: [Scilab-users] The trajectory of a vector sequence

[Scilab-users] The trajectory of a vector sequence

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

7 matches

Site Navigation

Mail list logo

Footer information