Re: [Scilab-users] Setting default axes / figure values

[Samuel Gougeon]

Le 01/08/2017 à 18:33, Richard llom a écrit :

Before my printing commands I'm setting up some defaults like this:
//  Visualization 
clf();
// Set some defaults
defaxh = get("default_axes");
defaxh.font_size = 3;
defaxh.title.font_size = 4;
defaxh.title.font_style = 9;
defaxh.x_label.font_size = 4;
defaxh.y_label.font_size = 4;

xtitle(desc);
...

However I noticed that these only take effect on the second run of the
script and not immediately.
This is obviously confusing and annoying when trying out different values.
Which command am I missing here?


None. After modifying the default parameters, only forthcoming figures 
take them into account. Already created figures stay as they are.


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

Re: [Scilab-users] Save figure as landscape DIN A4 PDF

[Samuel Gougeon]

Le 01/08/2017 à 18:24, Richard llom a écrit :

Hello All,
I want to save my figures automatically (from the script) as landscape DIN
A4.

xs2pdf(gcf(),'result','landscape');

Works fine so far, however I have problems defining the (paper) size. I
found only:
"figure_size:
This property controls the size in pixel of the screen's graphics window.
The size is the vector [width,height]."
But this seems unfit to me since this script is supposed to run on different
machines, where I don't know the screen resolution...


Have you tried printsetupbox() (for the default parameters) or 
printfigure(i) for printing parameters only for a given figure?




Secondly, after the file is saved, I want to present a link in the console
which the user can click on to open the file in his pdf-viewer.
Unfortunately I didn't found any command for links?


It is presently not possible in the console. But it is possible to do 
this through the Scilab file browser.


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

[Scilab-users] Setting default axes / figure values

[Richard llom]

Before my printing commands I'm setting up some defaults like this:
//  Visualization 
clf();
// Set some defaults
defaxh = get("default_axes");
defaxh.font_size = 3;
defaxh.title.font_size = 4;
defaxh.title.font_style = 9;
defaxh.x_label.font_size = 4;
defaxh.y_label.font_size = 4;

xtitle(desc);
...

However I noticed that these only take effect on the second run of the
script and not immediately.
This is obviously confusing and annoying when trying out different values.
Which command am I missing here?

TIA
richard



--
View this message in context: 
http://mailinglists.scilab.org/Setting-default-axes-figure-values-tp4036806.html
Sent from the Scilab users - Mailing Lists Archives mailing list archive at 
Nabble.com.
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

[Scilab-users] Save figure as landscape DIN A4 PDF

[Richard llom]

Hello All,
I want to save my figures automatically (from the script) as landscape DIN
A4.

xs2pdf(gcf(),'result','landscape');

Works fine so far, however I have problems defining the (paper) size. I
found only:
"figure_size:
This property controls the size in pixel of the screen's graphics window.
The size is the vector [width,height]."
But this seems unfit to me since this script is supposed to run on different
machines, where I don't know the screen resolution...

Secondly, after the file is saved, I want to present a link in the console
which the user can click on to open the file in his pdf-viewer.
Unfortunately I didn't found any command for links?

TIA
richard



--
View this message in context: 
http://mailinglists.scilab.org/Save-figure-as-landscape-DIN-A4-PDF-tp4036805.html
Sent from the Scilab users - Mailing Lists Archives mailing list archive at 
Nabble.com.
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Call for reviewer <= SEP: upgrading weekday()

[Richard llom]

Then I would go with just "US" (my opinion).

cheers




--
View this message in context: 
http://mailinglists.scilab.org/Scilab-users-SEP-upgrading-weekday-tp4036719p4036804.html
Sent from the Scilab users - Mailing Lists Archives mailing list archive at 
Nabble.com.
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Call for reviewer <= SEP: upgrading weekday()

[Samuel Gougeon]

Le 01/08/2017 à 15:45, Richard llom a écrit :

OK. So, instead of an option, we could use a prefix, that will be even
handier, like in "US7/24/2017". It could be specified just with
"US"+myDate
instead of myDate,"US", without having to think about the place of the
"US" option wrt the"long"
one.
We could use "US " (with a space) instead of "US", if a literal
readability is essential
(not my opinion). Anyway, the prefix must be fixed: either "US", xor "US
".
Any preference?

But doesn't weekday also accept a matrix of strings? How would this work
with the prefix?


As usual, in the same way, with "US" + myMatrixOfDates:

-->mydates = ["7/24/2017" "3/17/2015"];
-->"US"+mydates
 ans  =
!US7/24/2017  US3/17/2015  !

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

Re: [Scilab-users] Call for reviewer <= SEP: upgrading weekday()

[Richard llom]

> OK. So, instead of an option, we could use a prefix, that will be even
> handier, like in "US7/24/2017". It could be specified just with
> "US"+myDate
> instead of myDate,"US", without having to think about the place of the
> "US" option wrt the"long"
> one.
> We could use "US " (with a space) instead of "US", if a literal
> readability is essential
> (not my opinion). Anyway, the prefix must be fixed: either "US", xor "US
> ".
> Any preference? 

But doesn't weekday also accept a matrix of strings? How would this work
with the prefix?

I'm thinking more of data which is read-in (like from a log), and there a
prefix isn't a reasonable solution, but maybe thats just me...

richard



--
View this message in context: 
http://mailinglists.scilab.org/Scilab-users-SEP-upgrading-weekday-tp4036719p4036802.html
Sent from the Scilab users - Mailing Lists Archives mailing list archive at 
Nabble.com.
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Can this loop be avoided?

[Richard llom]

Thanks Jasper & Rafael, these solutions work great!



--
View this message in context: 
http://mailinglists.scilab.org/Can-this-loop-be-avoided-tp4036792p4036801.html
Sent from the Scilab users - Mailing Lists Archives mailing list archive at 
Nabble.com.
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Call for reviewer <= SEP: upgrading weekday()

[Samuel Gougeon]

Le 01/08/2017 à 14:24, Richard llom a écrit :

unless for instance using a distinct separator: MM\DD\. Not sure
that this would be actually ok.
Would it? IMO, a "US" optional flag would not be more handy.

IMO the "US" optional flag would be the only reasonable solution. Also for
someone who has his source date in US-format, this optional flag would
certainly be more handy than converting the date before / inline...


OK. So, instead of an option, we could use a prefix, that will be even 
handier,
like in "US7/24/2017". It could be specified just with "US"+myDate 
instead of myDate,"US",
without having to think about the place of the "US" option wrt the"long" 
one.
We could use "US " (with a space) instead of "US", if a literal 
readability is essential

(not my opinion). Anyway, the prefix must be fixed: either "US", xor "US ".
Any preference?

Samuel

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

Re: [Scilab-users] Call for reviewer <= SEP: upgrading weekday()

[Richard llom]

> Then, for a big subset of dates, there would not be any way to
> distinguish it from DD/MM/,

Yeah, thats the problem with this format (and not only in scilab).

> unless for instance using a distinct separator: MM\DD\. Not sure
> that this would be actually ok.
> Would it? IMO, a "US" optional flag would not be more handy.

IMO the "US" optional flag would be the only reasonable solution. Also for
someone who has his source date in US-format, this optional flag would
certainly be more handy than converting the date before / inline...

cheers
richard



--
View this message in context: 
http://mailinglists.scilab.org/Scilab-users-SEP-upgrading-weekday-tp4036719p4036799.html
Sent from the Scilab users - Mailing Lists Archives mailing list archive at 
Nabble.com.
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Linux: Console not working when starting from start menu

[Richard llom]

Hello Nikolay,
thanks for the prompt reply!

Under Plasma5 I can just check the "Run in terminal" option which also works
then.
However I also replied on the bug, hopefully it will be fixed soon...

cheers



--
View this message in context: 
http://mailinglists.scilab.org/Linux-Console-not-working-when-starting-from-start-menu-tp4036791p4036798.html
Sent from the Scilab users - Mailing Lists Archives mailing list archive at 
Nabble.com.
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Call for reviewer <= SEP: upgrading weekday()

[Samuel Gougeon]

Hello Richard,

Thanks for your input. I am answering in the body:

Le 01/08/2017 à 13:07, Richard llom a écrit :

I find it confusing that only "DD/MM/" doesn't require a leading zero,
while all others do...


Not all, just the -MM-DD... one, because this format is a 
normalized/standard one.

As documented, the DD-Mmm- like "12-Feb-2031" or "7-Jun-2024" does nor
require any mandatory leading zero.


Also there is no support at all for the us date format (MM/DD/). Not a
fan of it, but users from the USA might appreciate it.


Then, for a big subset of dates, there would not be any way to 
distinguish it from DD/MM/,
unless for instance using a distinct separator: MM\DD\. Not sure 
that this would be actually ok.

Would it? IMO, a "US" optional flag would not be more handy.

Best regards
Samuel

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

Re: [Scilab-users] Can this loop be avoided?

[jasper van baten]

try

index=1:size(log_data,'r')-1;
energy=(log_data(index+1,1)-log_data(index,1)).*log_data(index,2).*log_data(index,3);

Best wishes,

Jasper.



On 8/1/2017 13:00, Richard llom wrote:
> Hello All,
> I have this for loop:
> for i=1:size(log_data,'r')-1
> energy(i)=(log_data(i+1,1)-log_data(i,1))*log_data(i,2)*log_data(i,3);
> end
>
> The rows / loopsize are only a couple of thousands, so it is not that big of
> deal, still I was wondering: It is possible to do this w/o a loop?
>
> cheers
>
>
>
> --
> View this message in context: 
> http://mailinglists.scilab.org/Can-this-loop-be-avoided-tp4036792.html
> Sent from the Scilab users - Mailing Lists Archives mailing list archive at 
> Nabble.com.
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
>
>

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

Re: [Scilab-users] Call for reviewer <= SEP: upgrading weekday()

[Richard llom]

I find it confusing that only "DD/MM/" doesn't require a leading zero,
while all others do...

Also there is no support at all for the us date format (MM/DD/). Not a
fan of it, but users from the USA might appreciate it.

cheers
richard


Samuel GOUGEON wrote
> Hello,
> 
> The new implementation of weekday() is now pushed and available on the 
> CodeReview:
> https://codereview.scilab.org/#/c/19326/
> Its updated help page is attached.
> 
> It now expects to be reviewed before merging. Any contributor is welcome 
> to do so online.
> Thanks
> 
> Best regards
> Samuel Gougeon





--
View this message in context: 
http://mailinglists.scilab.org/Scilab-users-SEP-upgrading-weekday-tp4036719p4036793.html
Sent from the Scilab users - Mailing Lists Archives mailing list archive at 
Nabble.com.
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Linux: Console not working when starting from start menu

[Nikolay Strelkov]

Dear, Richard!

Yes, it is known issue - see http://bugzilla.scilab.org/
show_bug.cgi?id=14682 .
As temporary solution I created desktop launcher with command inside

env LC_ALL="en_US.UTF-8" xterm -e /home/nikolay/Software/scilab-6.0.0/bin/scilab

So Scilab starts with xterm terminal emulator. You may change xterm to
other terminal with corresponding options.

Hope this helps.


--

*With best regards,Ph.D., *


*associate professor at MPEI
,IEEE member,maintainer of
Mathieu functions toolbox for Scilab
,Nikolay Strelkov.*

2017-08-01 13:54 GMT+03:00 Richard llom :

> Hello,
> I have this problem that when I start scilab from my startmenu, the console
> doesn't accept any input and when I execute a script (from scinotes) scilab
> crashes.
> However when I start scilab from the terminal "scilab &" everything is
> fine.
>
> Any clues, is this a known issue?
>
> Scilab 6.0.0.
>
> System:Host: cray Kernel: 4.8.6-1-CHAKRA x86_64 (64 bit) Desktop: KDE
> Plasma 5.10.4 Distro: Chakra
> Machine:   Device: desktop Mobo: ASUSTeK model: A88XM-PLUS v: Rev X.0x
> UEFI:
> American Megatrends v: 3003 date: 03/04/2017
> CPU:   Dual core AMD A10-7850K Radeon R7 12 Compute Cores 4C+8G
> (-HT-MCP-) cache: 4096 KB
>clock speeds: max: 4200 MHz 1: 1700 MHz 2: 2400 MHz 3: 2400 MHz
> 4: 2400 MHz
> Graphics:  Card: Advanced Micro Devices [AMD/ATI] Fiji [Radeon R9 FURY /
> NANO Series]
>Display Server: x11 (X.Org 1.17.4) driver: amdgpu Resolution:
> 2560x1440@119.88hz
>OpenGL: renderer: Gallium 0.4 on AMD FIJI (DRM 3.3.0 /
> 4.8.6-1-CHAKRA, LLVM 3.9.1)
>version: 4.3 Mesa 13.0.2
> Audio: Card-1 Advanced Micro Devices [AMD] FCH Azalia Controller
> driver:
> snd_hda_intel
>Card-2 Advanced Micro Devices [AMD/ATI] Fiji HDMI/DP Audio
> Controller driver: snd_hda_intel
>Sound: Advanced Linux Sound Architecture v: k4.8.6-1-CHAKRA
> Sensors:   System Temperatures: cpu: 34.5C mobo: 35.0C gpu: 42.0
>Fan Speeds (in rpm): fan-1: 881 fan-2: 711 fan-3: 537
> Info:  Processes: 186 Uptime: 1:00 Memory: 2182.3/15994.7MB Client:
> Shell (bash) inxi: 2.3.23
>
>
>
> --
> View this message in context: http://mailinglists.scilab.org
> /Linux-Console-not-working-when-starting-from-start-menu-tp4036791.html
> Sent from the Scilab users - Mailing Lists Archives mailing list archive
> at Nabble.com.
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
>
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

[Scilab-users] Can this loop be avoided?

[Richard llom]

Hello All,
I have this for loop:
for i=1:size(log_data,'r')-1
energy(i)=(log_data(i+1,1)-log_data(i,1))*log_data(i,2)*log_data(i,3);
end

The rows / loopsize are only a couple of thousands, so it is not that big of
deal, still I was wondering: It is possible to do this w/o a loop?

cheers



--
View this message in context: 
http://mailinglists.scilab.org/Can-this-loop-be-avoided-tp4036792.html
Sent from the Scilab users - Mailing Lists Archives mailing list archive at 
Nabble.com.
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

[Scilab-users] Linux: Console not working when starting from start menu

[Richard llom]

Hello,
I have this problem that when I start scilab from my startmenu, the console
doesn't accept any input and when I execute a script (from scinotes) scilab
crashes.
However when I start scilab from the terminal "scilab &" everything is fine.

Any clues, is this a known issue?

Scilab 6.0.0.

System:Host: cray Kernel: 4.8.6-1-CHAKRA x86_64 (64 bit) Desktop: KDE
Plasma 5.10.4 Distro: Chakra
Machine:   Device: desktop Mobo: ASUSTeK model: A88XM-PLUS v: Rev X.0x UEFI:
American Megatrends v: 3003 date: 03/04/2017
CPU:   Dual core AMD A10-7850K Radeon R7 12 Compute Cores 4C+8G
(-HT-MCP-) cache: 4096 KB 
   clock speeds: max: 4200 MHz 1: 1700 MHz 2: 2400 MHz 3: 2400 MHz
4: 2400 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Fiji [Radeon R9 FURY /
NANO Series]
   Display Server: x11 (X.Org 1.17.4) driver: amdgpu Resolution:
2560x1440@119.88hz
   OpenGL: renderer: Gallium 0.4 on AMD FIJI (DRM 3.3.0 /
4.8.6-1-CHAKRA, LLVM 3.9.1)
   version: 4.3 Mesa 13.0.2
Audio: Card-1 Advanced Micro Devices [AMD] FCH Azalia Controller driver:
snd_hda_intel
   Card-2 Advanced Micro Devices [AMD/ATI] Fiji HDMI/DP Audio
Controller driver: snd_hda_intel
   Sound: Advanced Linux Sound Architecture v: k4.8.6-1-CHAKRA
Sensors:   System Temperatures: cpu: 34.5C mobo: 35.0C gpu: 42.0
   Fan Speeds (in rpm): fan-1: 881 fan-2: 711 fan-3: 537
Info:  Processes: 186 Uptime: 1:00 Memory: 2182.3/15994.7MB Client:
Shell (bash) inxi: 2.3.23



--
View this message in context: 
http://mailinglists.scilab.org/Linux-Console-not-working-when-starting-from-start-menu-tp4036791.html
Sent from the Scilab users - Mailing Lists Archives mailing list archive at 
Nabble.com.
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users