Re: [Scilab-users] Can I program a table into a diagram?

[Heinz Nabielek]

Hi Samuel:

mytab = ["Turbine Power" "Turbine hub height" "Turbine radius";
"WT=12 MW" "150 m" "110 m";
"WT= 7 MW" "100 m" "82 m";
"WT= 2 MW" "70 m" "40 m"];
Lat = prettyprint(mytab,,"");   // "" is to remove overall parentheses
Lat = strsubst(Lat, "${", "$\large{");
xstring(0.0015, 12, Lat)

works just fine with me. Absolutely great. And great many thanks.
Heinz

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/



Bird survival depends on avoidance, turbine power and wind speed.pdf
Description: Adobe PDF document


> On 27.02.2023, at 20:26, Samuel Gougeon  wrote:
> 
> Hello Heinz,
> 
> Le 25/02/2023 à 00:13, Heinz Nabielek a écrit :
>> Colleagues:
>> 
>> can I program a table like below into a Scilab generated diagram?
> 
> Sending some HTML-ized code to xstring() would have been the more versatile 
> and tunable way to proceed, to get a styled table, with colored backgrounds, 
> etc. Unfortunately, unlike for the GUI, xstring() does not interpret HTML and 
> renders it as is.
> 
> The first actual way might be to use an editable uitable (uicontrol 
> style="table") in a figure.
> Then you will need gui2bitmap to export the figure as an image, including the 
> uitable, and cells won't be filled with individual background colors.
> 
> The second way might be to use a LaTeX table,
> that can be prepared with prettyprint(), then be a bit customized, and 
> finally be sent to xstring():
> 
> mytab = ["Turbine Power" "Turbine hub height" "Turbine radius"
> ;
> 
> "7 MW" "100 m" "82 m";
> "12 MW" "150 m" "110 m"
> ;
> 
> "2 MW" "70 m" "40 m"];
> Lat = prettyprint(mytab,,"");   // ""
>  is to remove overall parentheses
> 
> Lat = strsubst(Lat, "${", "$\large{");
> clf, xstring(0.1, 0.1, Lat
> )
> 
> 
> 
> 
> You can tune the size of the text rendered in the table by changing \large 
> into \Large or \LARGE etc.
> You can add some row and column  frames by switching to a {tabular} object 
> instead of a {matrix} one:
> 
> mytab = ["Turbine Power" "Turbine hub height" "Turbine radius"
> "7 MW" "100 m" "82 m"
> "12 MW" "150 m" "110 m"
> "2 MW" "70 m" "40 m"];
> Lat = prettyprint(mytab,,"");   // "" is to remove overall parentheses
> Lat = strsubst(Lat, "${", "$\large{");
> Lat = strsubst(Lat, "begin{matrix}", "begin{tabular}{|c|c|c|}\hline");
> Lat = strsubst(Lat, "end{matrix}", "end{tabular}");
> Lat = strsubst(Lat, "\cr", "\cr\hline");
> I have not found any trivial direct way to split titles on 2 rows in cells:
> since strsubst() does not handle groups replacement,  the Lat string can be 
> processed by hand:
> In it, you may replace "Turbine Power" with "\substack{Turbine\\Power}", etc. 
> Then you get a string rendered as
> 
> 
> 
> ... that you can pass to xstring().
> 
> Regards
> Samuel
> 
> PS : Since in the figure you get the displayed legend is quite tall, it might 
> be worth to try the mc_legends() macro available in the FileExchange, to get 
> a 2-column legend.
> 
> PS2:  IMHO, prettyprint() would deserve getting more LaTeX-related options, 
> to output a matrix through the {tabular} environment instead of the {matrix} 
> one, to pass some {|c|l|c...} justification and border options, \hline 
> options, process in-cell line breaks, etc.
> 
> 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: 
> 

Re: [Scilab-users] Can I program a table into a diagram?

[Samuel Gougeon]

Hello Heinz,

Le 25/02/2023 à 00:13, Heinz Nabielek a écrit :
Colleagues:

can I program a table like below into a Scilab generated diagram?

Sending some HTML-ized code to xstring() would have been the more versatile and 
tunable way to proceed, to get a styled table, with colored backgrounds, etc. 
Unfortunately, unlike for the GUI, xstring() does not interpret HTML and 
renders it as is.

The first actual way might be to use an editable uitable (uicontrol 
style="table") in a figure.
Then you will need gui2bitmap to 
export the figure as an image, including the uitable, and cells won't be filled with 
individual background colors.


The second way might be to use a LaTeX table,
that can be prepared with 
prettyprint(), then 
be a bit customized, and finally be sent to xstring():

mytab = ["Turbine Power" "Turbine hub height" "Turbine radius";
"7 MW" "100 m" "82 m";
"12 MW" "150 m" "110 m";
"2 MW" "70 m" "40 m"];
Lat = prettyprint(mytab,,"");   // "" is to remove overall parentheses
Lat = strsubst(Lat, "${", "$\large{");
clf, xstring(0.1, 0.1, Lat)


[cid:part1.SxVGIIDw.TF4Le16q@free.fr]

You can tune the size of the text rendered in the table by changing \large into 
\Large or \LARGE etc.
You can add some row and column  frames by switching to a {tabular} object 
instead of a {matrix} one:

mytab = ["Turbine Power" "Turbine hub height" "Turbine radius"
"7 MW" "100 m" "82 m"
"12 MW" "150 m" "110 m"
"2 MW" "70 m" "40 m"];
Lat = prettyprint(mytab,,"");   // "" is to remove overall parentheses
Lat = strsubst(Lat, "${", "$\large{");
Lat = strsubst(Lat, "begin{matrix}", "begin{tabular}{|c|c|c|}\hline");
Lat = strsubst(Lat, "end{matrix}", "end{tabular}");
Lat = strsubst(Lat, "\cr", "\cr\hline");

I have not found any trivial direct way to split titles on 2 rows in cells:
since strsubst() does not handle groups 
replacement,  the Lat string 
can be processed by hand:
In it, you may replace "Turbine Power" with "\substack{Turbine\\Power}", etc. 
Then you get a string rendered as

[cid:part2.0OpHeCHn.5rotaSG1@free.fr]

... that you can pass to xstring().

Regards
Samuel

PS : Since in the figure you get the displayed legend is quite tall, it might be 
worth to try the mc_legends() 
macro available in the 
FileExchange, to get a 2-column legend.

PS2:  IMHO, prettyprint() would deserve getting more LaTeX-related options, to 
output a matrix through the {tabular} environment instead of the {matrix} one, 
to pass some {|c|l|c...} justification and border options, \hline options, 
process in-cell line breaks, etc.

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] unexpected syntax errors

[Samuel Gougeon]

Hello,

In Scilab 6.1.1
--> uman netcdf @
--> uman netcdf &

work as expected,
while in the nightly built version scilab-branch-6.1-7fc2e691
some syntax errors are yielded :

--> uman netcdf @
uman netcdf @
   ^^
Error : syntax error, unexpected ~ or @, expecting end of file

--> uman netcdf &
uman netcdf &
   ^^
Error: syntax error, unexpected &, expecting end of file

What is going on?

Samuel


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

[COUVERT Vincent]

Hello Lester,

About netCDF, did you try https://atoms.scilab.org/toolboxes/scinetcdf/1.2 ?

Vincent



From: users  On Behalf Of Lester Anderson
Sent: Friday, February 24, 2023 8:58 AM
To: International users mailing list for Scilab. 
Subject: Re: [Scilab-users] Scilab releases schedule / End of Windows 32-bit 
support

Hello all,

I await with interest the new version of Scilab. I only use the 64-bit version 
so have no issues with the 32-bit version being cut. Most people will be 
working on 64-bit systems anyway, and so makes sense to reduce or cut support 
for the 32-bit architecture.

With regard to versioning, I see no issue with the proposed change to 
year-based (X.Y.Z). However, I do feel that internally one should be able to 
see the "old-style" version like 6.1.2 etc, that should not be a big problem to 
keep in place.

For the developers, can we please get native support for the netCDF format in 
versions 6.x as this is widely used in the scientific community.

Lester

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

[Lester Anderson]

Hello all,

I await with interest the new version of Scilab. I only use the 64-bit version 
so have no issues with the 32-bit version being cut. Most people will be 
working on 64-bit systems anyway, and so makes sense to reduce or cut support 
for the 32-bit architecture.

With regard to versioning, I see no issue with the proposed change to 
year-based (X.Y.Z). However, I do feel that internally one should be able to 
see the "old-style" version like 6.1.2 etc, that should not be a big problem to 
keep in place.

For the developers, can we please get native support for the netCDF format in 
versions 6.x as this is widely used in the scientific community.

Lester

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