[Scilab-users] xload doesn't work with accented letters in file names on W10

[Perrichon]

Hello,

 

We get an error when loading a « scg » file which has accented letters in
its file name

 

Here is a script to reproduce this error

 

//--
-

Rep="TMPDIR\"

chdir(Rep)

 

 

NameFile1=Rep + "Test.scg";

NameFile2=Rep + "Test_xxx.scg";

NameFile3=Rep + "Test_ééé.scg";

 

f=scf(1);

plot2d();

 

xsave(NameFile1,1)

 

[status2, message2] = copyfile(NameFile1, NameFile2)

xload(NameFile2, 10)

 

[status3, message3] = copyfile(NameFile1, NameFile3)

xload(NameFile3, 11)

 

edit_error(%f)

//--
-

 

ERROR :

--> xload(NameFile3, 11)

at line 5 of function xloadFigure ( C:\Program
Files\scilab-6.1.0\modules\graphics\macros\xload.sci line 101 )

at line33 of function xload   ( C:\Program
Files\scilab-6.1.0\modules\graphics\macros\xload.sci line 45 )

 

xload: Given file is not a graphic one.

--> 

 

--> edit_error(%f)

ans  =

 

  "Opening file C:\Program
Files\scilab-6.1.0\modules\graphics\macros\xload.sci on line 101 of the
source file of the function xload"

 

 

Best Regards

Pierre

 

 

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

[Scilab-users] Erroneous file name for the "scg" file with accented characters when using xsave instruction

[Perrichon]

Hello,

 

xsave don't correctly save a "scg" file with accented characters in file
name

 

See the following script or buggzilla #16537

 

//--
-
Rep=TMPDIR
 
chdir(Rep)
Name=Rep + "\Test ùùééêë"
 
fd=mopen(Name + ".txt","w+")
mfprintf(fd,"Fichier %s + ".txt"\n",Name)
mclose(fd)
 
num=1
f=scf(num);
plot2d()
f.figure_name=Name
 
xsave(Name + ".scg",num)
 
//Erroneous file name for the "scg" file with accented characters
// W10 x64 - French AZERTY keyboard 
// Scilab 6.1.0 or 5.5.2
 
// Results : - File names :
//-
// Test ùùééêë.scg
// Test ùùééêë.txt
 
//--
--

 

Best regards

 

Pierre

 

 

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

Re: [Scilab-users] {EXT} Help for . operator

[Perrichon]

Hello, and so much thanks for your response.

Stéphane enlightened me

If a and b are simple floating 1x1 then a^b is sufficient. a.^b does not need 
the "dot" operator

Nice day
Pierre

Before printing, think about ENVIRONMENTAL responsabity


-Message d'origine-
De : users  De la part de Stéphane Mottelet
Envoyé : lundi 8 juin 2020 11:49
À : users@lists.scilab.org
Objet : Re: [Scilab-users] {EXT} Help for . operator

Hello,

The problem is the actual tolerance of Scilab which allows to omit the dot fot 
the power operator:

--> [1 2 3]^2
  ans  =

1.   4.   9.

although Matlab does not allow it:

 >> [1 2 3]^2
Error using  ^
Incorrect dimensions for raising a matrix to a power. Check that the matrix is 
square and the power is a scalar. To perform elementwise matrix powers, use 
'.^'.

S.

Le 08/06/2020 à 11:21, Dang Ngoc Chan, Christophe a écrit :
> Hello Pierre,
>
>> De : Perrichon
>> Envoyé : lundi 8 juin 2020 11:07
>>
>> I don't understand le role of the « point » operator '.'
> The dot is used to have an element-wise operation.
>
> The difference is when you work with matrices, e.g. the product * will 
> make a matrix product
>
> C = A*B -> C(i, j) = sum_k (A(i, k), B(k, j))
>
> but .* will make the elementwise product
>
> C = A.*B -> C(i, j) = A(i, j)*B(i, j)
>
> See 
> https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/help.
> scilab.org/docs/6.1.0/en_US/dot.html
>
> regards
>
> --
> Christophe Dang Ngoc Chan
> Mechanical calculation engineer
>
>
> General
> This e-mail may contain confidential and/or privileged information. If you 
> are not the intended recipient (or have received this e-mail in error), 
> please notify the sender immediately and destroy this e-mail. Any 
> unauthorized copying, disclosure or distribution of the material in this 
> e-mail is strictly forbidden.
> ___
> users mailing list
> users@lists.scilab.org
> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists
> .scilab.org/mailman/listinfo/users

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

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

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

[Scilab-users] Help for . operator

[Perrichon]

Hello

 

I got instruction coming from Matlab, and strictly reported in Scilab, like
for example :

 

ee=k1*(2*g*(sjt.^2)).^(-1); // Calcul de la perte de charge singulière
au niveau du vannage (en supposant que son coefficient multiplicateur est
égal à 1)

 

It works, but I don’t understand le role of the « point » operator ‘.’

 

Without the ‘.’, it gives the same result

 

ee=k1*(2*g*(sjt^2))^(-1); // Calcul de la perte de charge singulière au
niveau du vannage (en supposant que son coefficient multiplicateur est égal
à 1)

 

Any explanation.

 

Thank a lot for your response

 

All variables are simple flotting point in a sci routine

 

BR.

 

Pierre

 

 

 

 

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

Re: [Scilab-users] Scilab 6.1 too slow to list large vectors

[Perrichon]

Hello,

 


See also bugzilla  Scilab's Bug Tracker – Bug 16359



 

 

Time request : 100 s

 

Results :

Xcos Scilab 5.5.2 :

Durée de la simulation : 258.3 s

 

Xcos Scilab 6.1.0 :

Durée de la simulation : 4353.4 s

 

BR.

Pierre

 



 

Before printing, think about ENVIRONMENTAL responsabity

 

 

De : users  De la part de Samuel Gougeon
Envoyé : mercredi 20 mai 2020 16:50
À : users@lists.scilab.org
Objet : Re: [Scilab-users] Scilab 6.1 too slow to list large vectors

 

Le 30/03/2020 à 11:56, Federico Miyara a écrit :


Dear All,

I have observed that Scilab 6.1 seems to have a regression respect to 6.0.2. 
Sometimes one forgets to put semicolon after the coputation of a vector with 
tens of thousands components. Scilab 6.0.2 listed all the components very fast. 
That was nice because one hadn't to cancel the computation, it took about 1 s. 
With 6.1 it takes much longer. For instance

Fs = 44100
T = 2.5
t = [0:T*Fs]/Fs;
ximp = exp(-t/0.3).*rand(t,"normal") + 0.004*rand(t,"normal");
 
tic
ximp = ximp(:)
toc
 

This takes 1.36 s in 6.0.2

The same code in 6.1 takes 182 s

Any idea why?

I know I can cancel at any moment the script execution, but if there were a 
process that took a lot of time one wouldn't be willing to stop it...

 

Apparently, the maximum number N of lines of the console scroll buffer set in 
the user preferences (by default to 3000) is not taken into account to abstract 
the display in this kind of situation. Is it?

Yet, if there is no opened diary, displaying 10 "primary" rows looks 97% 
useless if the scroll buffer is 3000-row tall: 97000 rows will anyway become 
unreachable an lost, after the full display.

So, even without anticipating wrapping of long primary rows, that still 
multiplies the number of actual rows to display, wouldn't it be wise to limit 
the display to N primary lines, either the N last ones, or the N/2 first ones + 
"..." + the N/2 last ones ?

Even in the case of having so tall full diaries is required (that is a very 
specific and exceptional case), it is always possible to increase N through the 
preferences.

My two cents...

Samuel

 

 

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

Re: [Scilab-users] Corona modelling

[Perrichon]

Dear,

I understand Samuel, but not sure that this kind of example on C-19 is the most 
representative of a GUI with Scilab.

Confusion is done on what is on the screen, and ridiculus analysis when experts 
are always studing in the whole word !

Where is the message : scilab solve C-19 ??? I dream.

So this is is a bad example.

 

 

De : users  De la part de Samuel Gougeon
Envoyé : mercredi 20 mai 2020 15:50
À : users@lists.scilab.org
Objet : Re: [Scilab-users] Corona modelling

 

Hello,

 

Thank you Stéphane for this nice example of applied GUI.

The screenshot of the Xcos model from Hervé is also quite stimulating.

 

About the GUI run on Scilab 6.1.0, i have noticed that the Scilab filebrowser 
is blinking when using any of both sliders, as if it was updated/redisplayed 
for each slider step. It continues to blink for a while even after stopping 
using the control, likely until all queued steps are performed. This behavior 
can be seen when sliding with the mouse, as well as with arrows, but not with 
page_up and page_down keys. So, apparently only performing small steps triggers 
it.


Does anyone confirm this behavior, or is it only on my PC on Windows7 ?


Best regards
Samuel

 

Le 30/03/2020 à 08:13, Stéphane Mottelet a écrit :

Hello Heinz,

Here is an interactive version (made for my children last week...) :

// Confinement COVID-19 !
// Stephane MOTTELET, UTC
// Tue Mar 24 08:55:03 CET 2020
// 
function dydt=sir(t, y, bet, gam, N)
dydt=[-bet/N*y(1)*y(2)
   bet/N*y(1)*y(2)-gam*y(2)  
   gam*y(2)];
endfunction
 
function draw(bet, gam)
t=0:1:360;
N=6e7;
if exists("gcbo") && is_handle_valid(gcbo)
sb = gcbo;
if sb.tag=="beta"
bet=sb.value;
gam=findobj("gamma").value
else
gam=sb.value;
bet=findobj("beta").value
end
y=ode('stiff',[N-1;1;0],0,t,list(sir,bet,gam,N));
curves = findobj("curves");
curves.children(1).data(:,2)=y(3,:);
curves.children(2).data(:,2)=y(2,:);
curves.children(3).data(:,2)=y(1,:);
else
y=ode('stiff',[N-1;1;0],0,t,list(sir,bet,gam,N));
scf(0)
clf
plot(t,y)
gce().tag="curves";
gce().children.thickness=2;
legend("Susceptible","Infected","Recovered",-1)

sb1 = uicontrol("style","slider",...
"units","normalized",...
"Position", [0.85,0.2,0.05,0.48],...
"BackgroundColor", [1,1,1],...
"Callback_Type",12,...
"sliderstep",[1/1000,1/10],...
"min",0.15,"max",0.3,"value",bet,...
"Callback","draw","tag","beta");

uicontrol("style","text",...
"string","$\beta$",...
"units","normalized",...
"Position", [0.85,0.125,0.05,0.08],...
"BackgroundColor", [1,1,1],...
"HorizontalAlignment","center");

sb1 = uicontrol("style","slider",...
"units","normalized",...
"Position", [0.90,0.2,0.05,0.48],...
"BackgroundColor", [1,1,1],...
"Callback_Type",12,...
"sliderstep",[1/1000,1/10],...
"min",0,"max",1/15,"value",gam,...
"Callback","draw","tag","gamma");
 
uicontrol("style","text",...
"string","$\gamma$",...
"units","normalized",...
"Position", [0.9,0.125,0.05,0.08],...
"BackgroundColor", [1,1,1],...
"HorizontalAlignment","center");
 
end
end
 
clf
 
draw(0.3,1/15)
 

 

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

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

[Perrichon]

Good news !



Before printing, think about ENVIRONMENTAL responsabity


-Message d'origine-
De : users  De la part de tien.dang
Envoyé : mardi 19 mai 2020 12:26
À : users@lists.scilab.org
Objet : [Scilab-users] Can Mux and Demux have more than 32 ports

Dear all,
As title, Can I custom Mux and Demux block to have more than 32 ports, for
example: 64 ports as I need. 
I try to re build source code base on Git repos but meet so many errors.
Thanks
Tien Dang



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

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

Re: [Scilab-users] Non defined variable do not create error message within a superblock with HYSTERESIS

[Perrichon]

PS : see bugzilla 16411

 

 

De : Perrichon  
Envoyé : lundi 20 avril 2020 16:01
À : 'Users mailing list for Scilab' 
Objet : Non defined variable do not create error message within a superblock
with HYSTERESIS

 

Hello,

 

When importing superblock from complex diagrams, Errors are not detected if
variables are not declared inside a superblock.

They are only detected at the top diagram

 



 



 

This is a critical bug

 

Best regards

 

Pierre P.

 

 

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

[Scilab-users] Non defined variable do not create error message within a superblock with HYSTERESIS

[Perrichon]

Hello,

 

When importing superblock from complex diagrams, Errors are not detected if
variables are not declared inside a superblock.

They are only detected at the top diagram

 



 



 

This is a critical bug

 

Best regards

 

Pierre P.

 

 

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

Re: [Scilab-users] ?==?utf-8?q? Incorrect color in function

[Perrichon]

 

Indeed. Isn’t it, but :::

Coming fron 5.x to 6.x, logical and in 5x is « & » and, like in C « && » in 6x.

So a pass is needed in all hundred of files to provide to clients, 
phonecontact, documentation, and so on – great, thank you so much ; I think 
it’s more important than « then » instruction.

 

Regards

 

De : users  De la part de Federico Miyara
Envoyé : vendredi 10 avril 2020 18:16
À : users@lists.scilab.org
Objet : Re: [Scilab-users] ?==?utf-8?q? Incorrect color in function

 


Antoine,

I prefer the syntax without "then", it works, it is supported and the "then" 
seems redundant, but as you say, it is not related to that.

Thanks,

Federico Miyara 

On 10/04/2020 11:03, Antoine Monmayrant wrote:

Hello,
 
It seems that you're missing a "then" but nonetheless, the problem is really 
related to legend(), wich is weird.
I can reproduce your color bug with
 
function a()
if %t then
plot()
else
legend()
end
endfunction
 
 
but not with 
 
function a()
if %t then
plot()
else
legen()
end
endfunction
 
 (only difference legend()->legen()).
 
Antoine
 
Le Vendredi, Avril 10, 2020 15:28 CEST, Federico Miyara  
  a écrit: 
 

 
Dear all,
 
When writing the following script in SciNotes (v. 6.1):
 
function y = testcolor(t)
 if 1==1
 y = sinc(t)
 plot(t, y)
 legend("sinc")
 else
 y = 1
 end
endfunction
 
the end of the if structure appears with the same brownish color as the 
endfunction. Strangely, if copying and pasting here or into a word 
processor document, the color is the expected purple (that's why I 
removed all colors in this message).
 
It seems that the culprit is the legend clause.
 
Regards,
 
Federico Miyara
 
___
users mailing list
users@lists.scilab.org  
http://lists.scilab.org/mailman/listinfo/users
 

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

 

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

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

[Perrichon]

Hello,

On another way, see bugzilla #16359 in Xcos

I've provided the program to ESI

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

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

Stack? Mallloc ?

Regards



Before printing, think about ENVIRONMENTAL responsabity


-Message d'origine-
De : users  De la part de Antoine Monmayrant
Envoyé : mardi 31 mars 2020 11:55
À : Users mailing list for Scilab 
Objet : Re: [Scilab-users] ?==?utf-8?q? Scilab 6.1 too slow to list large 
vectors

Hello,

I also ran some tests and it seems that the regression is clearly line-based: 
ie the regression is worse for vector than for matrix because there more lines 
to print to display a vector than a matrix of similar length.
See my test code below.


n1=300;
n2=100;
mat=rand(n1,n2);
tn=[];

/* Ctrl+E the code below several times*/

tic
mat // matrix
//mat(:) // vector
t=toc()
tn=[tn,t];

disp('-')
disp('N_run = '+string(length(tn)))
disp('T='+string(mean(tn))+'+/-'+string(stdev(tn)));


/*
6.0.2 matrix
N_run = 20
T=0.6392742+/-0.056698
1.6x slower  but plotting 4 values per line ie 4x less lines to plot than for 
the matrix version

6.1.0 matrix
N_run = 10
T=1.0335109+/-0.0317414

6.0.2 vector mat(:)
N_run = 20
T=0.4943449+/-0.0662727

6.1.0 vector mat(:)
N_run = 10
T=3.800698+/-0.1121251
7.7x slower ie same slow down per line than for the vector version as we plot 4 
values per line so 4x more lines

*/
 
 
 
Le Mardi, Mars 31, 2020 11:36 CEST, Federico Miyara  
a écrit: 
 
> 
> Stéphane,
> 
> I simplified and diversified the test:
> 
> tic
> u = rand(100,1000)
> toc
> 
> takes
> 16 s in 6.1
> 10 s in 6.0.2
> 
> tic
> u = u(:)'
> toc
> 
> takes
> 66 s in 6.1
> 1.29 s in 6.0.2
> 
> tic
> u = u(:)
> toc
> 
> takes
> 107 s in 6.1
> 1.52 s in 6.0.2
> 
> tic
> u = matrix(u,1000,100)
> toc
> 
> takes
> 16 s in 6.1
> 10 s in 6.0.2
> 
> tic
> u = matrix(u,100, 100, 10)
> toc
> 
> takes
> 0.5 s in 6.1
> 0.5 s in 6.0.2
> 
> Seems as if vertical (many line feeds) print took more time than 
> horizontal print.
> 
> Regards,
> 
> Federico Miyara
> 
> 
> 
> On 31/03/2020 05:23, Stéphane Mottelet wrote:
> >
> > Hi Frederico,
> >
> > Thanks for reporting. Can you test if the regression also holds for 
> > matrices ?
> >
> > S.
> >
> > Le 30/03/2020 à 11:56, Federico Miyara a écrit :
> >>
> >> Fs  =  44100
> >> T  =  2.5
> >> t  =  [0:T*Fs]/Fs;
> >> ximp  =  exp(-t/0.3).*rand(t,"normal")  +  0.004*rand(t,"normal");
> >>
> >> tic
> >> ximp  =  ximp(:)
> >> toc
> > --
> > Stéphane Mottelet
> > Ingénieur de recherche
> > EA 4297 Transformations Intégrées de la Matière Renouvelable 
> > Département Génie des Procédés Industriels Sorbonne Universités - 
> > Université de Technologie de Compiègne CS 60319, 60203 Compiègne 
> > cedex Tel : +33(0)344234688 http://www.utc.fr/~mottelet
> >
> > ___
> > users mailing list
> > users@lists.scilab.org
> > http://lists.scilab.org/mailman/listinfo/users
>

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

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

Re: [Scilab-users] Strange behaviour of prod on rationals

[Perrichon]

Here are examples of my process in Open loop (FTBO) or Close loop (FTBF)

Depending of managemat, D can have s14 …

 



 

 

De : Perrichon  
Envoyé : mardi 17 mars 2020 10:49
À : 'Users mailing list for Scilab' 
Objet : RE: [Scilab-users] Strange behaviour of prod on rationals

 

Hello Federico

 

I have met few months or years ago this problem when i was developping my  « 
OPTSIM Solution » software to fix parameters of a PID for turbines (30 mw to 2 
gw) in Nyquist and Bode Plans with hydraulic parameters site

So I’ve seen instability of the denominator, witch damage calculus.

I don ‘t remember what I’ve done to get a cool solution, but it  has been a 
hard and severe problem with syslin, tf2ss and ss2tf instructions 

 

Sincerely

 

Pierre P.

 

 

De : users mailto:users-boun...@lists.scilab.org> > De la part de Federico Miyara
Envoyé : mardi 17 mars 2020 10:31
À : Users mailing list for Scilab mailto:users@lists.scilab.org> >
Objet : [Scilab-users] Strange behaviour of prod on rationals

 


Dear all, 

Look at this code (the coefficients are actually the result of pevious 
calculations):

NUM = [5.858D-09 + 2.011D-08*%s + 4.884D-08*%s^2 ... 
   5.858D-09 + 8.796D-10*%s + 7.028D-10*%s^2] 
DEN = [0.1199597 + 7.2765093*%s + %s^2 ... 
   8.336136 +  7.0282601*%s + %s^2] 
q = NUM./DEN
 
Running it yields

   5.858D-09 +2.011D-08s +4.884D-08s²  5.858D-09 +8.796D-10s +7.028D-10s²  
   --  --  
   0.1199597 +7.2765093s +s²8.336136 +7.0282601s +s²   

This is, correctly, a two-component rational vector with the expected 
numerators and denominators. 

Now let's evaluate 

q = prod(NUM./DEN) 

The prod documantation sys that the argument may be "an array of reals, 
complex, booleans, polynomials or rational fractions". It should provide the 
rational obtained by multiplying the twonumrators and the two denominators. 
However, we get

   3.432D-17 +1.230D-16s +3.079D-16s² +5.709D-17s³ +3.432D-17s⁴  
     
1

The numeratoris right, but the expected denominator has been just replaced by 1

However, rewriting the command as

prod(NUM)/prod(DEN)

we get the expected result:

   3.432D-17 +1.230D-16s +3.079D-16s² +5.709D-17s³ +3.432D-17s⁴  
     
   1.004 +61.501079s +59.597296s² +14.304769s³ +s⁴   

This is quite strange!

Now we repeat with simpler polynomials:

NUM = [1-%s 2-%s]
DEN = [1+%s 2+%s]
q = NUM./DEN 

We get 

   1 -s  2 -s  
       
   1 +s  2 +s 

Now evaluate

prod(NUM./DEN)

The result is the expected one!
  
   2 -3s +s²  
   -  
   2 +3s +s²  

The behavior seems to depend on the type of polynomials. 

Is this a bug or there is something I'm not interpreting correctly?

Regards,

Federico Miyara

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

Re: [Scilab-users] Strange behaviour of prod on rationals

[Perrichon]

Hello Federico

 

I have met few months or years ago this problem when i was developping my  « 
OPTSIM Solution » software to fix parameters of a PID for turbines (30 mw to 2 
gw) in Nyquist and Bode Plans with hydraulic parameters site

So I’ve seen instability of the denominator, witch damage calculus.

I don ‘t remember what I’ve done to get a cool solution, but it  has been a 
hard and severe problem with syslin, tf2ss and ss2tf instructions 

 

Sincerely

 

Pierre P.

 

 

De : users  De la part de Federico Miyara
Envoyé : mardi 17 mars 2020 10:31
À : Users mailing list for Scilab 
Objet : [Scilab-users] Strange behaviour of prod on rationals

 


Dear all, 

Look at this code (the coefficients are actually the result of pevious 
calculations):

NUM = [5.858D-09 + 2.011D-08*%s + 4.884D-08*%s^2 ... 
   5.858D-09 + 8.796D-10*%s + 7.028D-10*%s^2] 
DEN = [0.1199597 + 7.2765093*%s + %s^2 ... 
   8.336136 +  7.0282601*%s + %s^2] 
q = NUM./DEN
 
Running it yields

   5.858D-09 +2.011D-08s +4.884D-08s²  5.858D-09 +8.796D-10s +7.028D-10s²  
   --  --  
   0.1199597 +7.2765093s +s²8.336136 +7.0282601s +s²   

This is, correctly, a two-component rational vector with the expected 
numerators and denominators. 

Now let's evaluate 

q = prod(NUM./DEN) 

The prod documantation sys that the argument may be "an array of reals, 
complex, booleans, polynomials or rational fractions". It should provide the 
rational obtained by multiplying the twonumrators and the two denominators. 
However, we get

   3.432D-17 +1.230D-16s +3.079D-16s² +5.709D-17s³ +3.432D-17s⁴  
     
1

The numeratoris right, but the expected denominator has been just replaced by 1

However, rewriting the command as

prod(NUM)/prod(DEN)

we get the expected result:

   3.432D-17 +1.230D-16s +3.079D-16s² +5.709D-17s³ +3.432D-17s⁴  
     
   1.004 +61.501079s +59.597296s² +14.304769s³ +s⁴   

This is quite strange!

Now we repeat with simpler polynomials:

NUM = [1-%s 2-%s]
DEN = [1+%s 2+%s]
q = NUM./DEN 

We get 

   1 -s  2 -s  
       
   1 +s  2 +s 

Now evaluate

prod(NUM./DEN)

The result is the expected one!
  
   2 -3s +s²  
   -  
   2 +3s +s²  

The behavior seems to depend on the type of polynomials. 

Is this a bug or there is something I'm not interpreting correctly?

Regards,

Federico Miyara

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

[Scilab-users] Datatips display are incoherent with the Y-axes scaning using scilab 6.1.0 - Bugzilla #16376

[Perrichon]

Hello,

 

BUG DESCRIPTION:



datatips display are incoherent with the Y-axes scaning using scilab 6.1.0

It was not the case with Scilab 5.5.2

 

At least datatips display should respect precision of the y-axis

 

ERROR LOG:

--

None

 

HOW TO REPRODUCE THE BUG:

-

Open attached file Test2.scg and zoom in up to the bug

 

OTHER INFORMATION:

--

It was correct Scilab 5.5.2

 

 

See Bugzilla #16376 for attached files

Sample time = 0.1s

 



 

 

Best regard

 

 

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

[Scilab-users] Impossibility to open a scg file with datatips recorded with scilab 5.5.2 - Bugzilla #16374

[Perrichon]

Hello,

 

It's no more possible to open a scg file with datatips recorded coming from
Scilab 5.5.2 to Scilab 6.1.0

 

Should it be possible to get a translater for scg coming from 5.5.2 to 6.1.0
?

 

 

I've more than hundred of scg figures in scilab 5.5.2

 

See attached file Test.scg Bugzilla #16374 to test the bug

 

 

ERROR LOG:

--

--> load('C:\0 - tampon\Test.scg')

à la ligne14 de la fonction createDatatip

à la ligne42 de la fonction createSingleHandle   

à la ligne 9 de la fonction createMatrixHandle   

à la ligne42 de la fonction createPolyline   

à la ligne 8 de la fonction createSingleHandle   

à la ligne 9 de la fonction createMatrixHandle   

à la ligne39 de la fonction createAxes   

à la ligne 6 de la fonction createSingleHandle   

à la ligne69 de la fonction createFigure 

à la ligne 4 de la fonction createSingleHandle   

à la ligne 9 de la fonction createMatrixHandle   

à la ligne 4 de la fonction %__convertVariable__ 

à la ligne   955 de la fonction %_sodload( C:\Program
Files\scilab-6.1.0\modules\io\macros\%_sodload.sci ligne 968 )

dans la fonction nativeload 

 

La propriété 'z_component' est obsolète et sera supprimée, utilisez
'display_components' à la place.

 



 

 

Best regards

 

Pierre P.

 

 

 

 

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

[Scilab-users] Scilab 6.1.0 - Benchmark time test terribly worrisome - ratio 20 with Scilab 6.1.0 and scilab 5.5.2 - bugzilla 16359

[Perrichon]

Hello Clément,

 

As you requested, see bugzilla #16359

 

Best regards

Pierre P.

 

 

De : Clément David  
Envoyé : lundi 2 mars 2020 12:25
À : Perrichon ; 'Users mailing list for Scilab'

Cc : Clément David 
Objet : RE: [Scilab-users] Xcos 6.1.0 - benchmark time test

 

Hello Pierre,

 

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

 

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

 

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

 

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

 

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

 

Regards,

 

--

Clément

 

From: Perrichon mailto:perrichon.pie...@wanadoo.fr> > 
Sent: Monday, March 2, 2020 11:09 AM
To: 'Users mailing list for Scilab' mailto:users@lists.scilab.org> >; Clément David
mailto:clement.da...@esi-group.com> >
Subject: RE: [Scilab-users] Xcos 6.1.0 - benchmark time test

 

Hello Clément,

 

Yes, I have some function blocks and expression blocks.

Must I understand that I have to write CBLOCK for scilab function or scilab
expression or both ?

 

Here are other results for a more complex project name PELT1

 

Time request : 100 s

 

Results :

Xcos Scilab 5.5.2 :

Durée de la simulation : 258.3 s

 

Xcos Sciab 6.1.0 :

Durée de la simulation : 4353.4 s

 

So the ratio is 16.8 for PELT1

 

Other information :

 

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

 

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

 

Ratio=19

 

…and I also have other projects more complex

 

Pelt1 is for 1 needle (2 positonning loop)

Perlt6 for 6 !!! (7 positonning loop)

 

 

BR

 

 

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

 

Hello Pierre,

 

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

 

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

 

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

 

Regards,

 

--

Clément

 

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

 

Hello,

 

Here I test a PELTON basic algorithm under xcos, and record with tic-toc the
simulation real time.

These programs have been set for 120 s (scope)

 

Results :

Xcos Scilab 5.5.2 :

Durée de la simulation : 45.4 s

 

Xcos Sciab 6.1.0 :

Durée de la simulation : 65.2 s

 

So the ratio is 1.44 for a basic sheme

 

Any explaination ?

Can that be improved ?

 

BR

 

 

 

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

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

[Perrichon]

Hello Samuel ;

 

I’ve taken into account Chin Luh Tan’s remark  to open scilab in administrator 
mode with a right click on scilab icon :

 



 

, and run a new time your patch with the replace file « script2var.sci »

 

Then

 

--> cd SCI/modules/scicos/macros/scicos_scicos

ans  =

 

  "C:\Program Files\scilab-6.1.0\modules\scicos\macros\scicos_scicos"

 

--> predef clear

 

--> genlib scicos_scicoslib

ans  =

 

  T

 

--> clear script2var

 

Basic and trial tests program are available in Bugzilla #16357.

Before the modification :

 



 

And now



Samuel, I let you close the bufgzilla with resolved fix ?

 

Are a merge version foreseen and a nightlybuild , ? When ?

 

Thanks a lot

 

Also thank to Chin Luh Tan for his help.

 

Pierre P.

 

De : users  De la part de Samuel Gougeon
Envoyé : mardi 3 mars 2020 22:49
À : 'Users mailing list for Scilab' 
Objet : Re: [Scilab-users] Context error in Xcos Scilab 6.1.0

 

Le 03/03/2020 à 20:06, Perrichon a écrit :

PS

I have full read/write rights on my machine

This is the same issue as with Jan for bitget() last week.
I never install Scilab in the default directory C:\Program Files\
I think this is why i do not get this message.

If you had strictly no admin rights, you could even not copy the file in its 
directory.
But maybe there is an intermediate level of administration...
Sometimes when we put such a copy in a "System" directory, we are prompted for 
confirmation,
while theoretically being full rights admin.

One thing is sure: This is a Windows issue, not a Scilab one.

I will try installing Scilab in its default directory, and see how 
Windows can be tuned to accept compiling Scilab libs.

Samuel

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

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

[Perrichon]

PS

I have full read/write rights on my machine

 

 

De : Perrichon  
Envoyé : mardi 3 mars 2020 16:23
À : 'Users mailing list for Scilab' ; 'Samuel Gougeon' 

Objet : RE: [Scilab-users] Context error in Xcos Scilab 6.1.0

 

Hello Samuel :

 

1.  The correct pathname of script2var.sci is rather 
SCI/modules/scicos/macros/scicos_scicos
2.  If I launch your instructions with the correct directory, I get :

 

 

--> cd SCI/modules/scicos/macros/scicos_scicos

ans  =

 

  "C:\Program Files\scilab-6.1.0\modules\scicos\macros\scicos_scicos"

 

--> predef clear

 

--> genlib scicos_scicoslib

genlib : Impossible d'ouvrir le fichier "C:\Program 
Files\scilab-6.1.0\modules\scicos\macros\scicos_scicos\lib".

ans  =

 

  F

 

--> clear script2var

 

To read you

Best regards

 

 

De : users mailto:users-boun...@lists.scilab.org> > De la part de Samuel Gougeon
Envoyé : mardi 3 mars 2020 13:57
À : users@lists.scilab.org <mailto:users@lists.scilab.org> 
Objet : Re: [Scilab-users] Context error in Xcos Scilab 6.1.0

 

Le 02/03/2020 à 10:17, Clément David a écrit :

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

 

Thanks Clément for the indication and the report 
<http://bugzilla.scilab.org/show_bug.cgi?id=16357> .

Pierre, 
A solution is available => there 
<https://codereview.scilab.org/cat/21429%2C2%2Cscilab/modules/scicos/macros/scicos_scicos/script2var.sci>
 .
How to install it:

*   Download and unzip the file. Rename it script2var.sci
*   Put script2var.sci in its SCI/scicos/macros/scicos_scicos directory
*   Run the following Scilab code in the console, with some full read/write 
rights:
cd SCI/scicos/macros/scicos_scicos
predef clear
genlib scicos_scicoslib
clear script2var

Then things should work for your session and any following ones.
If you get some error when running genlib(), it is most probably because you 
don't have enough rights to overwrite the library with its update.

BR
Samuel

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

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

[Perrichon]

Hello Samuel :

 

1.  The correct pathname of script2var.sci is rather 
SCI/modules/scicos/macros/scicos_scicos
2.  If I launch your instructions with the correct directory, I get :

 

 

--> cd SCI/modules/scicos/macros/scicos_scicos

ans  =

 

  "C:\Program Files\scilab-6.1.0\modules\scicos\macros\scicos_scicos"

 

--> predef clear

 

--> genlib scicos_scicoslib

genlib : Impossible d'ouvrir le fichier "C:\Program 
Files\scilab-6.1.0\modules\scicos\macros\scicos_scicos\lib".

ans  =

 

  F

 

--> clear script2var

 

To read you

Best regards

 

 

De : users  De la part de Samuel Gougeon
Envoyé : mardi 3 mars 2020 13:57
À : users@lists.scilab.org
Objet : Re: [Scilab-users] Context error in Xcos Scilab 6.1.0

 

Le 02/03/2020 à 10:17, Clément David a écrit :

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

 

Thanks Clément for the indication and the report 
 .

Pierre, 
A solution is available => there 

 .
How to install it:

*   Download and unzip the file. Rename it script2var.sci
*   Put script2var.sci in its SCI/scicos/macros/scicos_scicos directory
*   Run the following Scilab code in the console, with some full read/write 
rights:
cd SCI/scicos/macros/scicos_scicos
predef clear
genlib scicos_scicoslib
clear script2var

Then things should work for your session and any following ones.
If you get some error when running genlib(), it is most probably because you 
don't have enough rights to overwrite the library with its update.

BR
Samuel

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

Re: [Scilab-users] strange sounds repeated over and over in scilab 6.1.0

[Perrichon]

Ok but this is a strange way to handle backward compatibility

 

 

De : users  De la part de Samuel Gougeon
Envoyé : lundi 2 mars 2020 16:15
À : users@lists.scilab.org
Objet : Re: [Scilab-users] strange sounds repeated over and over in scilab
6.1.0

 

Le 02/03/2020 à 14:52, Perrichon a écrit :

 

Hello

 

Few years ago, I got routines producing sounds in threads

 

With Scilab 5.5.2, sounds are produced once.

 

With Scilab 6.1.0, sounds are repeated endlessly.

 

No no, "only" 16 times :-)
You can stop it with playsnd([]) or CTRL+C.

I have proposed to remove sound(), that is a duplicate of playsnd() and
brings nothing.
But finally this has not been done for 6.1.0.
playsnd() has been upgraded. In the change, its nbits argument has been
removed.
But we have forgotten to update sound() calling playsnd().
So you hear the sound the default nbits=16 times.

You must directly use playsnd() instead.

Samuel

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

[Scilab-users] strange sounds repeated over and over in scilab 6.1.0

[Perrichon]

 

Hello

 

Few years ago, I got routines producing sounds in threads

 

With Scilab 5.5.2, sounds are produced once.

 

With Scilab 6.1.0, sounds are repeated endlessly.

 

 

Best regards

 

W10 x64

 

function Sound1()

// by Gary Scavone, McGill University, 2004

// Bell-like sound

fs = 22050;

T = 1/fs;

dur = 4;

t = 0:T:dur;

T60 = 0.5;

env = 0.95*exp(-t/T60);

// FM parameters

fc = 200;

fm = 280;

Imax = 10;

I = Imax.*env;

y = env.*sin(2*%pi*fc*t + I.*sin(2*%pi*fm*t));

   sound(y, fs);

 

endfunction

 

 

function Sound3()

x=1e2:1e4; b=0.6; y=window('hm',length(x)).*sin(x.^b.*log(x));
sound(y,9944)

endfunction

 

 

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

[Scilab-users] Zoom and datatips no longer work in Xcos version 6.1.0 during runtime

[Perrichon]

Hello,

 

Zoom and datatips no longer work in Xcos version 6.1.0 during runtime

 

It well run with Scilab 5.5.2

 

See also bugzilla #16353

 



 

 

Best regard

 

Pierre P.

 

 

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

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

[Perrichon]

Hello Clément,

 

Yes, I have some function blocks and expression blocks.

Must I understand that I have to write CBLOCK for scilab function or scilab
expression or both ?

 

Here are other results for a more complex project name PELT1

 

Time request : 100 s

 

Results :

Xcos Scilab 5.5.2 :

Durée de la simulation : 258.3 s

 

Xcos Sciab 6.1.0 :

Durée de la simulation : 4353.4 s

 

So the ratio is 16.8 for PELT1

 

Other information :

 

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

 

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

 

Ratio=19

 

…and I also have other projects more complex

 

Pelt1 is for 1 needle (2 positonning loop)

Perlt6 for 6 !!! (7 positonning loop)

 

 

BR

 

 

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

 

Hello Pierre,

 

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

 

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

 

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

 

Regards,

 

--

Clément

 

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

 

Hello,

 

Here I test a PELTON basic algorithm under xcos, and record with tic-toc the
simulation real time.

These programs have been set for 120 s (scope)

 

Results :

Xcos Scilab 5.5.2 :

Durée de la simulation : 45.4 s

 

Xcos Sciab 6.1.0 :

Durée de la simulation : 65.2 s

 

So the ratio is 1.44 for a basic sheme

 

Any explaination ?

Can that be improved ?

 

BR

 

 

 

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

Re: [Scilab-users] Isoview in GUI - Scilab 6.1.0

[Perrichon]

Hello Samuel

 

It’s OK.

I get exactly the same shape

 

Thanks you so much

 

Pierre P.

 

 

De : users  De la part de Samuel Gougeon
Envoyé : jeudi 27 février 2020 15:35
À : users@lists.scilab.org
Objet : Re: [Scilab-users] Isoview in GUI - Scilab 6.1.0

 

Hello Pierre,


The former isoview() implementation mixed some poor isometrical tuning, with
some unrelated rebounding action.

This is why both types of actions have been split:

*   isoview deals only with the isometrical view, in a richer way than
formerly: Please see history sections and compare synopses 
https://help.scilab.org/docs/6.0.0/en_US/isoview.html  with the former
https://help.scilab.org/docs/5.5.2/en_US/isoview.html
*   replot(), whose dedicated action is to rebound axes,  has also been
extended a lot in Scilab: Please compare
https://help.scilab.org/docs/6.0.0/en_US/replot.html with the former
https://help.scilab.org/docs/5.5.2/en_US/replot.html

Users were warned about this isoview change for 3 years.

So, the replacement for the former isoview([xmin,xmax,ymin,ymax]) is simply
isoview
replot([xmin,ymin,xmax,ymax])
with extended features with bounds values.

Maybe you think that replot() is not a nice name, not describing the actual
action of replot().
I would definitively agree. But reframing axes has aways been its dedicated
action.
And isoview() wasn't the right name to support (poor) rebounding features,
either

I hope you will appreciate and use recent isoview and replot features,
separately.

Best regards
Samuel

Le 27/02/2020 à 12:18, Perrichon a écrit :

Hello,

 

I’ve seen that syntax change for the isoview in scilab 6.1.0 :

isoview(gcf(), "on")// Scilab 6.1.0

In that case I must take a new time bounds in Nyquist and positionning 0 dB,
3 dB and so on

 

In my GUI, I personnaly prefer this fonction in scilab 5.5.2, where I can
fixe limits for the drawing

isoview(-1.0,1.0,-1.0,1.0);// Scilab 5.5.2

So I’ve done a copy of isoview Scilab 5.5.2, call Isoview, and automaticcaly
load at scilab 6.1.0 in the scilab.ini of SCIHOME

 

I hope this solution will be sustainable

 

Isoview in GUI - Scilab 5.5.2

 



 

Best regards

 





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

 

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

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

[Perrichon]

PS Samuel

 

Thanks to do the test as I say with A.sce

 

Executing  exec("A.ctx",-1) is a very strange way you do to test the bug

In your case, and for your understanding, and to go faster, simply enter
A=50 in the console.

 

So we stop exchange to keep the problem as a bug.

Too information bring confusion.

 

BR

Pierre P.

 

 

Scilab 5.5.2 run correctly :



Scilab 6.1.0 is bugged :



It means that A is not seen in xcos scilab 6.1.0

 

Must I write a bugzilla.

 

 

De : Perrichon  
Envoyé : samedi 29 février 2020 20:37
À : 'Users mailing list for Scilab' 
Objet : RE: [Scilab-users] Context error in Xcos Scilab 6.1.0

 

Please Samuel

 

If you only run exec("A.ctx",-1) then the xcos file , then A is a global
variable … !!!

 

Error is a matter of portability of variables

 

So thank to only run  A.sce  for testing. Because here the bug

 



 

For recalling, it well run with xcos scilab 5.5.2 and not with xcox 6.1.0

 

BR

 

Pierre P.

 

De : users mailto:users-boun...@lists.scilab.org> > De la part de Samuel Gougeon
Envoyé : samedi 29 février 2020 20:19
À : 'Users mailing list for Scilab' mailto:users@lists.scilab.org> >
Objet : Re: [Scilab-users] Context error in Xcos Scilab 6.1.0

 

Le 29/02/2020 à 19:35, Perrichon a écrit :

Hello Samuel,

 

Glad to see you confirm this bug

 

Context is executed at line 26 of the A.sce file, and not before :

---> xcos_simulate(scs_m, 4);

I did not use your A.sce file.
>From the xcos GUI, i have just tested if the context set in the diagram is
well executed,
noticeably exec("A.ctx",-1) and a mprintf() to show a message.

Samuel

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

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

[Perrichon]

Please Samuel

 

If you only run exec("A.ctx",-1) then the xcos file , then A is a global
variable … !!!

 

Error is a matter of portability of variables

 

So thank to only run  A.sce  for testing. Because here the bug

 



 

For recalling, it well run with xcos scilab 5.5.2 and not with xcox 6.1.0

 

BR

 

Pierre P.

 

De : users  De la part de Samuel Gougeon
Envoyé : samedi 29 février 2020 20:19
À : 'Users mailing list for Scilab' 
Objet : Re: [Scilab-users] Context error in Xcos Scilab 6.1.0

 

Le 29/02/2020 à 19:35, Perrichon a écrit :

Hello Samuel,

 

Glad to see you confirm this bug

 

Context is executed at line 26 of the A.sce file, and not before :

---> xcos_simulate(scs_m, 4);

I did not use your A.sce file.
>From the xcos GUI, i have just tested if the context set in the diagram is
well executed,
noticeably exec("A.ctx",-1) and a mprintf() to show a message.

Samuel

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

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

[Perrichon]

Hello Samuel,

 

Glad to see you confirm this bug

 

Context is executed at line 26 of the A.sce file, and not before :

---> xcos_simulate(scs_m, 4);

 

So in scilab 6.1.0, the A.ctx is executed.

I also add in A610.zcos the instruction

*   mprintf("Running context in xcos. ...So A=%i\n",A)

 

And then here is the track in my PC when running A.sce in xcos 6.1.0 :

 

 

--> exec('C:\0 - tampon\A.sce', -1)

Chargement du contexte d'exécution A.ctx

 

Running context in xcos. ...So A=50

 

Where we can see that A=50 inside A610.zcos.

 

We also can see that A is lost a the end of the context execution

 



This bad behavior also explains that my projects don’t migrate from xcos
5.5.2 to 6.1.0

 

Be sure that in my projects, the ct xis a set of a lot of scilab
instructions who generate variables.

These variables are use in any bloscks and under blocks of my main shemes

 

 

BR

 

 

De : users  De la part de Samuel Gougeon
Envoyé : samedi 29 février 2020 17:53
À : users@lists.scilab.org
Objet : Re: [Scilab-users] Context error in Xcos Scilab 6.1.0

 

Le 29/02/2020 à 17:41, Samuel Gougeon a écrit :

Hello Pierre,

 

Le 29/02/2020 à 11:32, Perrichon a écrit :

Hello,

 

I try to understand and find a reason why my projects done with xcos scilab
5.5.2 not run i 6.1.0

So I isolate at least one reason in a basic test program (see attached
files)

 

Here, zcos file are lunched into scilab 5.5.2 or 6.10, with the A.sce file
which test the version

 

A.ctx is a context file. Here is a simple variable definition A=50 in that
case.

 

Every zcos file contains in its simulation contexte, the instruction «
exec("A.ctx") » ; accessible with simulation-> context modifying 

 

To run this program, make a directory, a copy of the attached files, and
change eventually line 4 in A.sce :

Root="c:\0 - tampon"
// Répertoire de travail pour le test

 

So run A.sce inside xcos scilab 5.5.2 or 6.1.0

 

Scilab 5.5.2 run correctly :






Scilab 6.1.0 is bugged :

 

 

Apparently, the problem is that the context is not executed when the diagram
is loaded.
Despite what the context message indicates:

 

Indeed, the message mprintf("Chargement du contexte d''exécution
%s\n\n",FichierContexte)
set in the context is not displayed when the diagram is loaded in 6.1.0 ;
only when the context
is updated (or simply edited and revalidated).

With Scilab 5.5, the context is not executed when loading the diagram,but
when running it.

So, to me, there are apparently 2 issues:

1.  The Set Context message should be fixed: "... and every time the
diagram is run" (not loaded)
2.  The fact that the context is executed when the diagram is run should
be restored in Scilab 6.

Sorry, i don't know what occurred with my first trial, but now it works:
In 6.0.2 and 6.1.0, the message is well displayed when the diagram is run.
The error message displayed on the icon is the following:



 

Samuel

 



A610.zcos
Description: Binary data
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

[Scilab-users] Context error in Xcos Scilab 6.1.0

[Perrichon]

Hello,

 

I try to understand and find a reason why my projects done with xcos scilab
5.5.2 not run i 6.1.0

So I isolate at least one reason in a basic test program (see attached
files)

 

Here, zcos file are lunched into scilab 5.5.2 or 6.10, with the A.sce file
which test the version

 

A.ctx is a context file. Here is a simple variable definition A=50 in that
case.

 

Every zcos file contains in its simulation contexte, the instruction «
exec("A.ctx") » ; accessible with simulation-> context modifying 

 

To run this program, make a directory, a copy of the attached files, and
change eventually line 4 in A.sce :

Root="c:\0 - tampon"
// Répertoire de travail pour le test

 

So run A.sce inside xcos scilab 5.5.2 or 6.1.0

 

Scilab 5.5.2 run correctly :



Scilab 6.1.0 is bugged :



It means that A is not seen in xcos scilab 6.1.0

 

Must I write a bugzilla.

 

Sincerely

 

Pierre P.

 

 

 



A.ctx
Description: Binary data


A.sce
Description: Binary data


A552.zcos
Description: Binary data


A610.zcos
Description: Binary data
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

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

[Perrichon]

Sorry , I wanted to write :

 

I’ve  NEVER work with scilab 6.0.x

 

 

De : users  De la part de Perrichon
Envoyé : vendredi 28 février 2020 12:10
À : 'Users mailing list for Scilab' 
Objet : Re: [Scilab-users] Xcos 6.1.0 - benchmark time test

 

Hello Clément

 

In this benchmark test, I only use xcos files in scilab 5.5.2 and 6.1.0,
same file save in 6.1.0 done without any components of my personal palette
SEGPAL. 

So all components are with the xcos standart palettes

 

I’ve work with scilab 6.0.x But all is fine in all my projects with 5.5.2,
so this is a nice blue sky.

 

I now try to go to scilab 6.1.0 which the begining of my nigthmares.

It also means that at this step, I shall not test 6.0.2.

 

Not easy

 

For example, I’ve to understant why instruction « importXcosDiagram » don’t
run. 

But this is another discussion….

This instruction well run in Scilab 5.5.2

à la ligne13 de la fonction importXcosDiagram ( C:\Program
Files\scilab-6.1.0\modules\xcos\macros\importXcosDiagram.sci ligne 32 )

 

BR

 

Pierre P.

 

 

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

 

Hello Pierre,

 

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

 

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

 

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

 

Regards,

 

--

Clément

 

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

 

Hello,

 

Here I test a PELTON basic algorithm under xcos, and record with tic-toc the
simulation real time.

These programs have been set for 120 s (scope)

 

Results :

Xcos Scilab 5.5.2 :

Durée de la simulation : 45.4 s

 

Xcos Sciab 6.1.0 :

Durée de la simulation : 65.2 s

 

So the ratio is 1.44 for a basic sheme

 

Any explaination ?

Can that be improved ?

 

BR

 

 

 

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

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

[Perrichon]

Hello Clément

 

In this benchmark test, I only use xcos files in scilab 5.5.2 and 6.1.0,
same file save in 6.1.0 done without any components of my personal palette
SEGPAL. 

So all components are with the xcos standart palettes

 

I’ve work with scilab 6.0.x But all is fine in all my projects with 5.5.2,
so this is a nice blue sky.

 

I now try to go to scilab 6.1.0 which the begining of my nigthmares.

It also means that at this step, I shall not test 6.0.2.

 

Not easy

 

For example, I’ve to understant why instruction « importXcosDiagram » don’t
run. 

But this is another discussion….

This instruction well run in Scilab 5.5.2

à la ligne13 de la fonction importXcosDiagram ( C:\Program
Files\scilab-6.1.0\modules\xcos\macros\importXcosDiagram.sci ligne 32 )

 

BR

 

Pierre P.

 

 

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

 

Hello Pierre,

 

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

 

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

 

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

 

Regards,

 

--

Clément

 

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

 

Hello,

 

Here I test a PELTON basic algorithm under xcos, and record with tic-toc the
simulation real time.

These programs have been set for 120 s (scope)

 

Results :

Xcos Scilab 5.5.2 :

Durée de la simulation : 45.4 s

 

Xcos Sciab 6.1.0 :

Durée de la simulation : 65.2 s

 

So the ratio is 1.44 for a basic sheme

 

Any explaination ?

Can that be improved ?

 

BR

 

 

 

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

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

[Perrichon]

Hello Clément

This is done
See bugzilla #16343

BR


Before printing, think about ENVIRONMENTAL responsabity


-Message d'origine-
De : users  De la part de Clément David
Envoyé : vendredi 28 février 2020 09:53
À : Users mailing list for Scilab 
Objet : Re: [Scilab-users] Xcos Editor in Scilab 6.1.0 breaks diagrams

Hello Pierre,

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

Thanks,

--
Clément

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

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

[Scilab-users] Xcos 6.1.0 - benchmark time test

[Perrichon]

Hello,

 

Here I test a PELTON basic algorithm under xcos, and record with tic-toc the
simulation real time.

These programs have been set for 120 s (scope)

 

Results :

Xcos Scilab 5.5.2 :

Durée de la simulation : 45.4 s

 

Xcos Sciab 6.1.0 :

Durée de la simulation : 65.2 s

 

So the ratio is 1.44 for a basic sheme

 

Any explaination ?

Can that be improved ?

 

BR

 

 

 

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

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

[Perrichon]

Hello Samuel

I dont’t find this option

BR



 

 

 

De : users  De la part de Samuel Gougeon
Envoyé : jeudi 27 février 2020 20:09
À : users@lists.scilab.org
Objet : Re: [Scilab-users] Xcos Editor in Scilab 6.1.0 breaks diagrams

 

Le 27/02/2020 à 19:56, Perrichon a écrit :

Hello

I correctly rewrite the MUX box dans the zcos.

Then I go out off Scilab, come in a new time and go to my folio.

Now I obtain : 



What to do ?

 

Have you tried to use the Format => Link style => Optimal feature?

 

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

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

[Perrichon]

Hello

I correctly rewrite the MUX box dans the zcos.

Then I go out off Scilab, come in a new time and go to my folio.

Now I obtain : 



What to do ?

 

 

De : users  De la part de Perrichon
Envoyé : jeudi 27 février 2020 19:35
À : 'Users mailing list for Scilab' 
Objet : [Scilab-users] Xcos Editor in Scilab 6.1.0 breaks diagrams

 

Hello,

 

Xcos Editor in Scilab  6.1.0 breaks  diagrams. Number of failure is big.

Must I understand I’ve to rewrite all my projects in Scilab 6.1.0.

 

Here is an example (with  several minus zooms)

The big box in simply a MUX in the standard Palette, normaly drawn at the
bottom of this diagram

 

Must I write a bugzilla ?

 

Best regards

 

 



 

 

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

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

[Perrichon]

Hello,

 

Xcos Editor in Scilab  6.1.0 breaks  diagrams. Number of failure is big.

Must I understand I've to rewrite all my projects in Scilab 6.1.0.

 

Here is an example (with  several minus zooms)

The big box in simply a MUX in the standard Palette, normaly drawn at the
bottom of this diagram

 

Must I write a bugzilla ?

 

Best regards

 

 



 

 

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

[Scilab-users] Isoview in GUI - Scilab 6.1.0

[Perrichon]

Hello,

 

I've seen that syntax change for the isoview in scilab 6.1.0 :

isoview(gcf(), "on")// Scilab 6.1.0

In that case I must take a new time bounds in Nyquist and positionning 0 dB,
3 dB and so on

 

In my GUI, I personnaly prefer this fonction in scilab 5.5.2, where I can
fixe limits for the drawing

isoview(-1.0,1.0,-1.0,1.0);// Scilab 5.5.2

So I've done a copy of isoview Scilab 5.5.2, call Isoview, and automaticcaly
load at scilab 6.1.0 in the scilab.ini of SCIHOME

 

I hope this solution will be sustainable

 

Isoview in GUI - Scilab 5.5.2

 



 

Best regards

 

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

[Scilab-users] Bugzilla 15921 : The multiplication operator is missing

[Perrichon]

Hello,

 

Coment about Bugzilla 15921 in xcos scilab 6.1.0 : The multiplication
operator is missing :

 



 

Best regards

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

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

[Perrichon]

Hello

 

Using my personnal palette, I see that drag and drop a component in an xcos
screen is not drawn with Scilab 6.1.0

 

See bugzilla #16338 for attached file "Photo of the Bug"

 

It was fine with scilab 5.5.2

 

So what to do in the  -case "define"- part of the sci files? See the sci
attached file

 

And why does it happen???

 

 

Best regards

Pierre P.

 

 

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

[Scilab-users] Scilab 6.1.0 - MinGW

[Perrichon]

Hello

Many Thanks to Antoine for reintroducing MinGW tools in atom pack and plug,
after all discussions on email and phone last week-end, for compiling
palette in xcos with no errors and no warnings in c++.

Include files are ok now (.h)

Buider is ok. After other problems to discuss.

BR

Pierre P.

 

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

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

[Perrichon]

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

 

 

De : Perrichon  
Envoyé : mardi 25 février 2020 16:57
À : 'Users mailing list for Scilab' 
Objet : several problems with xcos scilab 6.1.0

 

Hello,

Even if it is minor, apparently somebody has decided to define the time
simulation to 30 s by default. Why ? I don’t know

Before, it was 1.0E05 s and I stop the simulation with the END box in my
main scheme. (to avoid user to go on this menu and choose another solver, at
least). (choose is Newton for me , so the default one)

So I’ve hundred shemes to see

 

And this is not the first surprise.

 

Others tests don’t work anymore

 

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

 

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

 

Pierre P.

 

 

 

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

[Scilab-users] several problems with xcos scilab 6.1.0

[Perrichon]

Hello,

Even if it is minor, apparently somebody has decided to define the time
simulation to 30 s by default. Why ? I don't know

Before, it was 1.0E05 s and I stop the simulation with the END box in my
main scheme. (to avoid user to go on this menu and choose another solver, at
least). (choose is Newton for me , so the default one)

So I've hundred shemes to see

 

And this is not the first surprise.

 

Others tests don't work anymore

 

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

 

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

 

Pierre P.

 

 

 

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

[Scilab-users] Palette Builder failed with scilab 6.1.0 nightly build - Bugzilla #16332

[Perrichon]

Hello,

I created several years ago my palette SEGPAL for additional components in
XCOS, using Scilab 5.5.2 W10 x64

This library very well run

 

Now, I try to recompile it using Scilab 6.1.0 nightly build, but the
buider.sce failed and I don"t know how tu continue

 

PS : For the C files, I use gcc version 4.6.3

 

See bugzilla #16332 for attached file (SEGPAL library)

 

I get errors :

 

--> exec('C:\SEGPAL\SegPal\builder.sce', -1)

Création des macros...

-- Création de [SegPallib] (Macros) --

genlib : Traitement du fichier : CLRseg.sci

genlib : Traitement du fichier : DerFil.sci

genlib : Traitement du fichier : EdgeTrigger.sci

genlib : Traitement du fichier : IntHyd.sci

genlib : Traitement du fichier : IntLim.sci

genlib : Traitement du fichier : IntSuiv.sci

genlib : Traitement du fichier : IntegralInt.sci

genlib : Traitement du fichier : Memo.sci

genlib : Traitement du fichier : PSB.sci

genlib : Traitement du fichier : PSBsuiv.sci

genlib : Traitement du fichier : PlusInt.sci

genlib : Traitement du fichier : Pow.sci

genlib : Traitement du fichier : RampJet.sci

genlib : Traitement du fichier : Rampe.sci

genlib : Traitement du fichier : Satur.sci

genlib : Traitement du fichier : Step2.sci

genlib : Traitement du fichier : TempoTrig.sci

genlib : Traitement du fichier : Time_Delay.sci

Création des blocs...

Création des sources...

à la ligne57 de la fonction detectmsvc64tools ( C:\Program
Files\scilab-branch-master\modules\dynamic_link\macros\detectmsvc64tools.sci
ligne 71 )

à la ligne 4 de la fonction dlwHaveCompiler   ( C:\Program
Files\scilab-branch-master\modules\dynamic_link\macros\windows\dlwHaveCompil
er.sci ligne 17 )

à la ligne 7 de la fonction haveacompiler ( C:\Program
Files\scilab-branch-master\modules\dynamic_link\macros\haveacompiler.sci
ligne 20 )

à la ligne38 de la fonction tbx_builder_src   ( C:\Program
Files\scilab-branch-master\modules\modules_manager\macros\tbx_builder_src.sc
i ligne 55 )

à la ligne35 de la fonction main_builder  (
C:\SEGPAL\SegPal\builder.sce ligne 43 )

à la ligne51 du fichier exécuté C:\SEGPAL\SegPal\builder.sce

 

Variable non définie : dlwIsVc11Express

 

 

Best regards

 

Pierre P.

 

 

 

 

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

[Scilab-users] Request for information - Release of Scilab for version 6.1

[Perrichon]

Hello,

 

I actually work with Scilab 5.5.2

 

For the next version 6.1.0, I have to plan my interventions and warn
customers. 

I plan at least 2 months of work for my part at least.
Can I announce July 2020? Or more?
Could we know more?

 

Here is my basic scheme, with 30 algos per machine (10 machines). Big work I
suppose.

 



 

 

 

Sincerely

Pierre P.

 

 

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

[Scilab-users] Sampling in the CSCOPE component - Last sample - Bugzilla 16322

[Perrichon]

Hello

 

Last sample time is missed in a CSOPE componant

 

W10- x64-scilab 6.1.0 

 



 

 

 

See bugzilla #16322

 

Best regards

 

 

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

Re: [Scilab-users] Scilab Nigthly build - bugzilla 16308

[Perrichon]

I use Mozilla Firefox and Window 10

B.R

 

 

De : Samuel Gougeon  
Envoyé : dimanche 2 février 2020 18:09
À : Perrichon ; 'Users mailing list for Scilab'

Objet : Re: [Scilab-users] Scilab Nigthly build - bugzilla 16308

 

Le 02/02/2020 à 17:13, Perrichon a écrit :

Hello Samuel

I’ve download two times with full success scilab 5.5.2 and 6.0.2 and
reinstall on my computer without any problem.

I maintain that I can’t download the scilab nightly build, after more than
fifteen trys.

So I cannot test your proposal concerning bugzilla #16308

 



 

Yes, sometimes the download is interrupted. I guess that the server
delivering the Continuous build is less powerful than the one for
downloading the official releases. But then it has been always possible (on
Windows 7, with Firefox, Chrome or Opera) to resume the download, to
complete it, without restarting it from scratch.

Regards
Samuel

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

Re: [Scilab-users] Scilab Nigthly build - bugzilla 16308

[Perrichon]

Hello Samuel

 

I’ve download two times with full success scilab 5.5.2 and 6.0.2 and
reinstall on my computer without any problem.

 

I maintain that I can’t download the scilab nightly build, after more than
fifteen trys.

So I cannot test your proposal concerning bugzilla #16308

 



 

Best regards

 

 

De : users  De la part de Samuel Gougeon
Envoyé : vendredi 31 janvier 2020 12:15
À : 'Users mailing list for Scilab' 
Objet : Re: [Scilab-users] Scilab Nigthly build - bugzilla 16308

 

Hello Pierre,

 

Le 31/01/2020 à 08:28, Perrichon a écrit :

Hello Samuel

 

Is there a way to load nigthly build version, as it existed in the past :
apparently not available on the new download site

 

Nighly build are replaced with the Continuous Build, that can change several
times a day according to the activity on the main Scilab forge.
As answered in Bugzilla, currently the Continuous Build version is the
master one. It can be found and downloaded there:

Overview:
https://build.scilab.org/view/Scilab%20binaries/

Windows:
https://build.scilab.org/view/Scilab%20binaries/job/scilab-master-windows-64
/lastSuccessfulBuild/artifact/scilab-branch-master_x64.exe

Linux:
https://build.scilab.org/view/Scilab%20binaries/job/scilab-master-linux-64/l
astSuccessfulBuild/artifact/scilab-branch-master-linux-x86_64.tar.gz

The issue with the anti-virus software on your computer is independent from
the access to Continuous Build binaries.

Regards
Samuel

 

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

[Scilab-users] Scilab Nigthly build - bugzilla 16308

[Perrichon]

Hello Samuel

 

Is there a way to load nigthly build version, as it existed in the past :
apparently not available on the new download site

 

Sincerely

 

Pierre P.

 

 

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

[Scilab-users] Refreshing the browser under Xcos

[Perrichon]

Hello

 

I save a set of figures in a sce file under Xcos, using xsave instruction

But the browser is no refresh with the new files (I have to go to another
directory and go back tu the current directory to finally see the new files.

Is there a scilab instruction to resfreh the directory into the Xcos browser
?

 

Best Regards

Pierre P.

 

 

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

Re: [Scilab-users] BUG legends_mc with xsave and xload

[Perrichon]

PS : xsave and xload correctly work with « legend » instruction under 5.5.2,
but « legends_mc » is the ideal presentation.

 

 

De : Perrichon  
Envoyé : mercredi 15 janvier 2020 10:05
À : 'Users mailing list for Scilab' 
Objet : RE: [Scilab-users] BUG legends_mc with xsave and xload

 

Hello Samuel,

You are rigth, it runs with scilab .0.2

But my project is written ith scilab 5.5.2, and I can’t actually go to
6.0.2. May be in the second part of 2020

 

Is there a way to write a workaround with 5.5.2 ?

 

I’ve done a copy of xload from 6.02 and try to adapt

1 no recursive for gcf().uid~=uid ==> replace by hh=gcf() then hh.uid~=uid

2 && not an operator in 5.5.2 (C langage) replace by &

 

But the problem seems with load(fil) in function xloadFigure(fil)

 

This is urgent for me to find a solution

Any advices ?

 

Best regards

 

Pierre P.

 

De : users mailto:users-boun...@lists.scilab.org> > De la part de Samuel Gougeon
Envoyé : mardi 14 janvier 2020 21:08
À : users@lists.scilab.org <mailto:users@lists.scilab.org> 
Objet : Re: [Scilab-users] BUG legends_mc with xsave and xload

 

Hello Pierre,

 

Le 14/01/2020 à 18:33, Perrichon a écrit :

Hello, Hello Samuel,

 

It seems that it is not possible to correctly record or to restaure a graph
using « legends_scm » with « xsave » and « xload »

Structures of the graph are not respected and illegible.

 

If the bug is not corrected, I’ll will be obliged to go back with the «
legend » instruction

Sincerely

 

How to reproduce the bugg :

 

scf(1)

clf, plot2d(), legends_mc('line #'+string(1:3), Lpc=-1, pos="ul" ) //
classic

xsave("foo.scg", gcf())

scf(2)

xload("foo.scg")

 

I am not able to reproduce any issue when running this code with Scilab
6.0.2 on Windows 7.
The initial legend is recovered with the whole figure.

Samuel

 

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

Re: [Scilab-users] BUG legends_mc with xsave and xload

[Perrichon]

Hello Samuel,

You are rigth, it runs with scilab .0.2

But my project is written ith scilab 5.5.2, and I can’t actually go to
6.0.2. May be in the second part of 2020

 

Is there a way to write a workaround with 5.5.2 ?

 

I’ve done a copy of xload from 6.02 and try to adapt

1 no recursive for gcf().uid~=uid ==> replace by hh=gcf() then hh.uid~=uid

2 && not an operator in 5.5.2 (C langage) replace by &

 

But the problem seems with load(fil) in function xloadFigure(fil)

 

This is urgent for me to find a solution

Any advices ?

 

Best regards

 

Pierre P.

 

De : users  De la part de Samuel Gougeon
Envoyé : mardi 14 janvier 2020 21:08
À : users@lists.scilab.org
Objet : Re: [Scilab-users] BUG legends_mc with xsave and xload

 

Hello Pierre,

 

Le 14/01/2020 à 18:33, Perrichon a écrit :

Hello, Hello Samuel,

 

It seems that it is not possible to correctly record or to restaure a graph
using « legends_scm » with « xsave » and « xload »

Structures of the graph are not respected and illegible.

 

If the bug is not corrected, I’ll will be obliged to go back with the «
legend » instruction

Sincerely

 

How to reproduce the bugg :

 

scf(1)

clf, plot2d(), legends_mc('line #'+string(1:3), Lpc=-1, pos="ul" ) //
classic

xsave("foo.scg", gcf())

scf(2)

xload("foo.scg")

 

I am not able to reproduce any issue when running this code with Scilab
6.0.2 on Windows 7.
The initial legend is recovered with the whole figure.

Samuel

 

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

[Scilab-users] BUG legends_mc with xsave and xload

[Perrichon]

Hello, Hello Samuel,

 

It seems that it is not possible to correctly record or to restaure a graph
using < legends_scm > with < xsave > and < xload >

Structures of the graph are not respected and illegible.

 

If the bug is not corrected, I'll will be obliged to go back with the <
legend > instruction

Sincerely

 

 

How to reproduce the bugg :

 

scf(1)

clf, plot2d(), legends_mc('line #'+string(1:3), Lpc=-1, pos="ul" ) //
classic

xsave("foo.scg", gcf())

scf(2)

xload("foo.scg")

 

 

 

 

 

 

 

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

Re: [Scilab-users] About legend instruction in graphics -

[Perrichon]

Hello,

 

Samuel’s « legends_mc » is a very nice instruction.

It does exactly what  I wanted

 

   xLeg=0.;

   yLeg=1.04;

 

 
Xlegend=["CVitesse";"Vitesse";"Vannage";"Débit";"Chute";"Puissance"]


 
legends_mc(Xlegend, Lpc=-10, framed?=%f, pos=[xLeg yLeg])

 

 



Other case

 
Xlegend=["Cons.Vitesse";'Vitesse filtrée';"Dérivée";"Intégrale";"Lim.
Ouverture";"Cons. Vannage CVA";"Cons. charge CC"]


 
legends_mc(Xlegend, Lpc=2, framed?=%f, pos=[xLeg yLeg])

 

 :

 

 

Best regard

 

Pierre P.

De : users  De la part de Samuel Gougeon
Envoyé : mercredi 8 janvier 2020 20:13
À : users@lists.scilab.org
Objet : Re: [Scilab-users] About legend instruction in graphics

 

Hello,

 

Le 08/01/2020 à 19:30, Perrichon a écrit :

 

Hello,

 

When drawing scope X(t) with multiple chanels, is there a way to get a
horizontal legend to maximalize the graphic area (as matlab does)

All proposal for the legend positionning reduce the graphic area (vertical
display with box or no box)

 

1.  Legend are into the graphic. Some curves are not visible
2.  Legend are out of graphic, but reduces the graphic area.

 

 

 

Best Regards

 

Pierre P.

 

 

legend_mc() aims to do that:
https://fileexchange.scilab.org/toolboxes/274000

 

--> legends_mc
function [] = legends_mc(Texts,Styles,Lpc,font_size,thickness,pos,framed?)
 For many curves & related legends, displays a multicolumn bloc of legends:
  - The shape of the bloc can be specified (Lpc)
  - Positionning with Logarithmic or/and reversed axes is supported
  - Lines styles and Markers styles are supported and can be mixed.
A set of polyline handles or having polyline children can be
alternatively provided
  - Lines thickness(es) can be specified (ignored if handles are 
given: read out from the polylines properties)

 HELP: run legends_mc() without any parameter
 DEMO: run legends_mc(..) without specifying Texts

 Texts  : vector of legends
 Styles : a) vector of related lines or markers styles (integer indices)
  Styles(i)>0 -> line color (only solid style supported)
  -14<= Styles(i) <=0 -> marker (overlay with line unsupported)
 b) (2,n) matrix: 
 Styles(1,:) = as in a)
 Styles(2,:) = line style, or color of marker
 c) vector of graphical handles. Then all Polyline children
are searched (in chronological order of creation).
Texts must have as many entries as there are available
polylines.
If only 1 handle is given and is an axes, the legends is 
set in this axes. When returning, the focus is restored 
to the axes priorly active.
If a set of handles or an handle not being an axes is given,
the legends are set in the currently active axes.
 Default Styles : gca()
 Lpc>0 :  (maximal) number of Lines Per Column (integer)
 Lpc<0 : -(maximal) number of Columns per line (integer)
 framed? : boolean: if %T, draws the global box of legends (default)
 pos : position of the block:
  "ur" | 1 : in the upper right corner (default)
  "ul" | 2 : in the upper left corner
  "ll" | 3 : in the lower left corner
  "lr" | 4 : in the lower right corner
  "?"  | 5 : interactive positionning with the mouse
  [xr,yr]: relative coordinates 0 <= xr,yr <= 1 of the upper left 
 corner of the block, with respect to the upper left corner
 of the data bounds area. [0,0] is equivalent to "ul"
 thickness: scalar or vector of lines thickness. 
If a vector is provided, its length must = Styles one.
If styles are from handles, thickness vector is ignored.
 
 DEMOS: run legends_mc(..) without Texts of legends:
   clf, legends_mc( framed?=%f )
   clf, legends_mc( Lpc=7, pos="?" )
   clf, legends_mc( Lpc=-3, pos="lr" )
   clf, legends_mc( Lpc=-2, pos=[0.15 0.3] )
   clf, legends_mc( font_size=2, pos="ll" )
   clf, legends_mc( pos="?", thickness=2 )
   clf, legends_mc( pos="lr", thickness=1+round(rand(1:19)) )
   clf, plot2d(), legends_mc( Lpc=-3, pos="ll" )
   clf, plot(), f=gcf(); legends_mc(Styles=f.children($), pos="?")

 EXAMPLE: 
   clf, plot2d(), legends_mc("line #"+string(1:3), Lpc=-3, pos="?" )

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

[Scilab-users] About legend instruction in graphics

[Perrichon]

 

Hello,

 

When drawing scope X(t) with multiple chanels, is there a way to get a
horizontal legend to maximalize the graphic area (as matlab does)

All proposal for the legend positionning reduce the graphic area (vertical
display with box or no box)

 

1.  Legend are into the graphic. Some curves are not visible
2.  Legend are out of graphic, but reduces the graphic area.

 



 

Best Regards

 

Pierre P.

 

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

Re: [Scilab-users] C source directory doesn't exist in SCI/modules/scicos_blocks/src/c/

[Perrichon]

Thanks you so much Samuel

Good WE

 

 

De : users  De la part de Samuel Gougeon
Envoyé : samedi 28 décembre 2019 11:03
À : users@lists.scilab.org
Objet : Re: [Scilab-users] C source directory doesn't exist in
SCI/modules/scicos_blocks/src/c/

 

Le 28/12/2019 à 10:55, Perrichon a écrit :

Hello Samuel

 

Tanks for your response, but dowlnoad the source is no more available in the
new scilab distribution site.

In the past, it was possible, but now how to access the Source files ?

 

Right. Sources archives are now in the "Previous versions" item, what is
quite misleading.
https://www.scilab.org/previous-scilab-versions

 

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

Re: [Scilab-users] C source directory doesn't exist in SCI/modules/scicos_blocks/src/c/

[Perrichon]

Hello Samuel

 

Tanks for your response, but dowlnoad the source is no more available in the
new scilab distribution site.

In the past, it was possible, but now how to access the Source files ?

 

Regards

 

 

De : users  De la part de Samuel Gougeon
Envoyé : samedi 28 décembre 2019 10:42
À : users@lists.scilab.org
Objet : Re: [Scilab-users] C source directory doesn't exist in
SCI/modules/scicos_blocks/src/c/

 

Le 28/12/2019 à 10:33, Perrichon a écrit :

Hello,

I was looking for the source file SCI/modules/scicos_blocks/src/c/tows_c.c
(Type 4)

But in fact, the C directory is not delivered in the windows package, Scilab
5.5.2 or 6.0.2 

 

Only .sci source files are delivered with the binary scilab, in the macros
directories.
To get all source files (help pages, C, C++, Java, Fortran codes, etc), the
sources archive must be downloaded and browsed.

 

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

[Scilab-users] C source directory doesn't exist in SCI/modules/scicos_blocks/src/c/

[Perrichon]

Hello,

I was looking for the source file SCI/modules/scicos_blocks/src/c/tows_c.c
(Type 4)

But in fact, the C directory is not delivered in the windows package, Scilab
5.5.2 or 6.0.2 

Must I write a bugzilla ?

 

(type help on tows_c on the component into the Xcos workspace)

 

Best regard

 

 

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

Re: [Scilab-users] Unexpected Figure n°0 in xload instruction under XCOS - Buggzilla 16289

[Perrichon]

Ok

Sorry

 

 

De : users  De la part de Samuel Gougeon
Envoyé : jeudi 26 décembre 2019 19:56
À : users@lists.scilab.org
Objet : Re: [Scilab-users] Unexpected Figure n°0 in xload instruction under
XCOS - Buggzilla 16289

 

Le 26/12/2019 à 12:01, Perrichon a écrit :

Dear,

 

Runing routine in xload help under XCOS, but adding a xload in figure n°100,
also create an unexpected empty Figure n°0

So 2 figures are generated : Empty Figure 0 and Figure 100 in the following
example

 

t=0:0.01:10;

subplot(211),plot2d(t,sin(t))

subplot(212),plot2d(t,sin(3*t))

xsave(TMPDIR + "/foo.scg", gcf())

clf()

xload(TMPDIR + "/foo.scg",100)

 

I don't catch what you mean with Runing routine in xload help under XCOS.

But running this code in the Scilab console yields what is expected. The
default figure #0 where plots are drawn and finally cleared is kept, and its
saved version is loaded in a separate figure #100.

Regards

 

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

[Scilab-users] Unexpected Figure n°0 in xload instruction under XCOS - Buggzilla 16289

[Perrichon]

Dear,

 

Runing routine in xload help under XCOS, but adding a xload in figure n°100,
also create an unexpected empty Figure n°0

So 2 figures are generated : Empty Figure 0 and Figure 100 in the following
example

 

t=0:0.01:10;

subplot(211),plot2d(t,sin(t))

subplot(212),plot2d(t,sin(3*t))

xsave(TMPDIR + "/foo.scg", gcf())

clf()

xload(TMPDIR + "/foo.scg",100)

 

 

Workaround after the set of xload :

 

   // Détruire la fenêtre n°0 (bug?)

   //---

   lista=winsid()

   b=find(lista==0)

   if b<>[] then xdel(lista(b)); end;

 

Best regards.

Pierre P.

 

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

Re: [Scilab-users] extract data in a scope under xcos

[Perrichon]

Hello Samuel,

 

In fact, my client want the equivalent of the data in a scilab numerical
scope, but in a format .txt or .csv, as to introduce these files in his
expert analysis software Flexpro.

Since last time, I’ve worked around the structure of a scop, and written a
routine hereafter. That a better solution than added a “TOWS_c » component
in the xcos diagrams.

I also think that the kind of routines are sorely missing in Xcos in “File
menu” (gateway to Excel for exemple). It could be an improvment

 

Sorry for this disturbance

 

Pierre P.

Best regards

 

   a=gca()

   mat=a.children

   Legend=mat(1).text'
// Channels titles

 

   nbv=size(Legend); nbv=nbv(2)   // Number of
channels

 

   Time=mat(2).data(:,1)

   lg=size(Time); lg=lg(1)
// Size of each channel (nb. lines)

 

   NumReg=1

   txtNumreg=sprintf("%02i_",NumReg)

 

   filename=txtNumreg + "Francis" + ".txt";

 

   fd = mopen(filename, "w")

 

   // Line 1 : Print Legends

   //

   mfprintf(fd,"Time")

   

   for i=1:nbv

 
mfprintf(fd,"\t%s",Legend(i))

   end

   mfprintf(fd,"\n")

 

   // Data line per line

   //-

   for i=1:lg

   // Print Time

 
//

 
mfprintf(fd,"%0.2f",Time(i))

   

   //Print Data line

 
//--

   for k=nbv:-1:1

 
mfprintf(fd,"\t%f",mat(k+1).data(i,2))

   end

   mfprintf(fd,"\n")
// Next line

   end

 

   mclose(fd)

 

 

De : users  De la part de Samuel Gougeon
Envoyé : lundi 23 décembre 2019 11:55
À : users@lists.scilab.org
Objet : Re: [Scilab-users] extract data in a scope under xcos

 

Hello Pierre,

 

Le 21/12/2019 à 01:14, Perrichon a écrit :

Dear,

 

Is there anyway to extract the data in a scope under xcos?

…May be because Datatips give every point X,Y

But how to proceed ?

I have added in my scheme a “TOWS_c » component ; it works, but the
management is more heavy in the project.

A solution to extract directly in the scope is welcome.

Do you mean to extract some coordinates of curves displayed in a scope, and
then display them as well on the scope?

If so, there is apparently no sink or annotation block to do this.
May be the scifunc_block_m could be hijacked to do the job. 

Regards
Samuel

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

[Scilab-users] extract data in a scope under xcos

[Perrichon]

Dear,

 

Is there anyway to extract the data in a scope under xcos?

.May be because Datatips give every point X,Y

But how to proceed ?

I have added in my scheme a "TOWS_c > component ; it works, but the
management is more heavy in the project.

A solution to extract directly in the scope is welcome.

 

Best regards.

Pierre P.

 

 

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

[Scilab-users] 2019.11.24 - Strange Bug open file Windows

[Perrichon]

Dear,

I am writing a big  project  for hydraulic water consideration using
scilab/xcos w10 v 5.5.2

 

In one corner of the project, I propose to load parameters coming from
expertise, with the instruction 

 

   ParFile = uigetfile(["*.par"],directory, "Load OpstSim :
Chargement d''un fichier de paramétrisation", %f);

   if ParFile=="" then return; end;

 

>From time to time, Scilab is killed (one over 100). I also mean that this is
not possible to stop Scilab with the windo manager (top of this system). The
only way to escape is to turn off the pc battery of the pc (power down… !)

.

Any explainations ? I don’t see what i have to do but i take all solutions
to go on. I am sad on this  and desapointed. I don’t see what to do

 



 

 

 

Best regards

 

 

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

[Perrichon]

Dear tan

Many thanks  for your poem. It is so romantic.

No sure you speak to the right person

I have no mac at home

 

sincerely yours

 

 

 

 

De : users  De la part de Chin Luh Tan
Envoyé : lundi 4 novembre 2019 02:09
À : Users mailing list for Scilab 
Cc : 'Users mailing list for Scilab' 
Objet : Re: [Scilab-users] Scilab cannot work on macOS 10.15 Catalina: 
Any        progress in sight?

 

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

 

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 mailto:perrichon.pie...@wanadoo.fr> > wrote 

 

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


Before printing, think about ENVIRONMENTAL responsabity 

-Message d'origine- 
De : users mailto:users-boun...@lists.scilab.org> > De la part de Stéphane Mottelet 
Envoyé : dimanche 3 novembre 2019 21:55 
À : users@lists.scilab.org <mailto: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 > <mailto:wknoe...@gmail.com> > 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 certain files or the html links are broken. So maybe it is 
>> either the file/directory structure of the zip file or the link to 
>> the zip file does not exist anymore. Thus it might actually be neither a 
>> SciLab nor an ATOMS issue (indirectly maybe). 
>> 
>> Then I deleted all leftovers of IPCV in the contrib folder and used 
>> atomsInstall('IPCV'), which put the files in the share/.../contrib 
>> folder, but I realized the folder structure is wrong (not 
>> recognised?). I had to move all files and subdirectories from the 
>> .../IPCV/IPCV folder to .../IPCV/4.1/ Then everything works perfe

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

[Perrichon]

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 certain files or the html links are broken. So maybe it is 
>> either the file/directory structure of the zip file or the link to 
>> the zip file does not exist anymore. Thus it might actually be neither a 
>> SciLab nor an ATOMS issue (indirectly maybe).
>>
>> Then I deleted all leftovers of IPCV in the contrib folder and used 
>> atomsInstall('IPCV'), which put the files in the share/.../contrib 
>> folder, but I realized the folder structure is wrong (not 
>> recognised?). I had to move all files and subdirectories from the 
>> .../IPCV/IPCV folder to .../IPCV/4.1/  Then everything works perfectly.
>>
>> Very tricky.
>>
>> BTW, output from getversion() is  "scilab-6.0.2".
>>
>> W.
>>
>>
>>
>> --
>> Sent from: 
>> https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/anti
>> spam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/mailinglists.sci
>> lab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html
>> ___
>> users mailing list
>> users@lists.scilab.org
>> https://antispam.utc.fr/proxy/2/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/anti
>> spam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org
>> /mailman/listinfo/users
> ___
> users mailing list
> users@lists.scilab.org
> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists
> .scilab.org/mailman/listinfo/users

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

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

Re: [Scilab-users] Nysquist instruction - fmin fmax parameters vectorized controlling

[Pierre PERRICHON]

 

Hello,

 

Many thanks to Samuel,

 

So at the begining of next week; I open a bugzilla as "improvement" of nyquist 
instruction, in respect of its own documentation

about vectorized aspect for fmin and fmax fields.

It will be more confortable to present the aim and exhange

 

Sincerely

Pierre

 

 

 

> Message du 31/10/19 18:53
> De : "Samuel Gougeon" 
> A : users@lists.scilab.org
> Copie à : 
> Objet : Re: [Scilab-users] Nysquist instruction - fmin fmax parameters 
> vectorized controlling
> 
> Le 31/10/2019 à 18:34, Pierre PERRICHON a écrit : > > Dear all, > > As said 
> in the nyquist help instruction, it is possible to get a > nyquist plan using 
> this instruction > > nyquist( sl,[fmin,fmax] [,step] [,comments] [,symmetry]) 
> > > ... and this example in the same doc : > > 
> nyquist([Plant;Plant*PID],0.5,100,["Plant";"Plant and PID corrector"]); > > 
> Here, we see that s1 can be a vectorized siso. Also, the legend is > 
> vectorized in the same size. > > Perfect. > > But 0.5 and 100 are not 
> vectorize, and as to stay in final in a same > quarter, as hope, I need to 
> impose min > and mas for h1, h2, h3 ...hn on the siso matrix. > > But this is 
> not the case for fmin and fmax, even if it is described in > the 
> documentation: > > "The frequencies are given by the bounds fmin,fmax (in Hz) 
> > or by a row-vector (or a matrix for multi-output) frq" > > It doesn't work, 
> I get error, and I'm not able to precise each min and > max in that syntax, > 
> Could you please provide an actual full and minimal example enabling to 
> reproduce the error? Apparently, this frq input argument really aims to 
> process vectorized cases. So, at last, it should work. Thanks 
> ___ 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] CLR design component is not clear in scilab 6.0.2 x64 W10

[Pierre PERRICHON]

 

Dear,

 

A new time, Federico is right.

Monsieur Pierre-Simon de Lapalce is a French man ==> so the variable of Laplace 
is p

American are not France, so they use s

Like Grafcet in FRANCE, which is a french conception and SFC in US and their 
copies several years later.

 

I've done my own componants library in certains case under scilab/xcos, without 
problem in  5.5.2 and I use p and s in sheme

For me not a problem. But I can take 5 minyes ti explain history during the 
rush with students.

 

I hope that the last component with CLR will be accepted and retained, so it is 
so nice, as said by Federico ans Samuel pour the next 6.1

 

Regards

 

 

 

 

> Message du 31/10/19 19:52
> De : "Federico Miyara" 
> A : users@lists.scilab.org
> Copie à : 
> Objet : Re: [Scilab-users] CLR design component is not clear in scilab 6.0.2 
> x64 W10
> 
>
> Samuel,
> 
> Just a detail: in some books the p variable is used as the Laplace variable, 
> especially when working with normalized variables. For instance, a normalizad 
> butterworth filter may pe presented as
> 
> 1/(1 + 2*p + 2*p^2 + p^3)
> 
> I recall Bildstein's book on Active filters. See also: 
> 
> https://books.google.com.ar/books?id=r5yjPuWQde0C&pg=PR20&lpg=PR20&dq=%22normalized+laplace+variable%22&source=bl&ots=L0hFQ4aA2a&sig=ACfU3U3DpwZTwRN1lMwtxf6RztQHFPj_6Q&hl=es-419&sa=X&ved=2ahUKEwi2hceJk8flAhUhD7kGHcLsBRUQ6AEwAXoECAkQAQ#v=onepage&q=%22normalized
>  laplace variable%22&f=false
> 
> But it is true that most references use s.
> 
> Regards, 
> 
> Federico Miyara
>   
> 
>
On 30/10/2019 19:02, Samuel Gougeon wrote:
>

Le 30/10/2019 à 10:26, Perrichon a écrit :
>


Hello

CLR design component brings confusion by forgetting the * sign in operand

of a polynomial representation in Laplace plan

It makes schemes unreadeable



> First, you know that la Laplace variable is always s.
> Second, in such specific cases, you can anyway use this:

> 

> Samuel

> 
>


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



>





 
Libre de virus. www.avast.com







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

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

[Scilab-users] Nysquist instruction - fmin fmax parameters vectorized controlling

[Pierre PERRICHON]

Dear all,

As said in the nyquist help instruction, it is possible to get a nyquist plan 
using this instruction

nyquist( sl,[fmin,fmax] [,step] [,comments] [,symmetry])

... and this example in the same doc :

nyquist([Plant;Plant*PID],0.5,100,["Plant";"Plant and PID corrector"]);

Here, we see that s1 can be a vectorized siso. Also, the legend is vectorized 
in the same size.

Perfect.

But 0.5 and 100 are not vectorize, and as to stay in final in a same quarter, 
as hope, I need to impose min 
and mas for h1, h2, h3 ...hn on the siso matrix.

But this is not the case for fmin and fmax, even if it is described in the 
documentation:

"The frequencies are given by the bounds fmin,fmax (in Hz) 
or by a row-vector (or a matrix for multi-output) frq"

It doesn't work, I get error, and I'm not able to precise each min and max in 
that syntax,
even if it is easy to get these one for each component in a loop with the 
vectorized siso,
using the instruction :

[fmin,fmax]=nyquistfrequencybounds(hi,bounds)
Correct with only one transfer function.

The aim is to plot the legend.
That work here, but representation is bad due to the not vectorized fmin fmax
Imagine an isoview (-1,-1, 1 ,1)

I can control the min max in a quater if I plot each member one after one,in a 
loop but in this case I'm not enable
to set any the relevant legend
Is there a solution ? May be in scilab 6.1.0 ?

I look for a syntax as :
[nyquist([h1;h2], [[fminh1, fminh2);[fmaxh1, fmaxh2]],["h1";"h2"])
or, better :
[nyquist([h1;h2], [fminh1, fminh2],[fmaxh1, fmaxh2],["h1";"h2"])

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

Re: [Scilab-users] k*Ts - tr: Re: CLR design component is not clear in scilab 6.0.2 x64 W10

[Pierre PERRICHON]

 

Dear Samuel and Xcosers-scilabers

 

It's OK

Sorry for the reply, my favorite outlook has broken today, and I have had to go 
on the orange plateform which is more difficult for me.

 

OK only one separator of course. This is perfect

the "*" was for the dialog box, not for the final rendering of the xcos  box 
screen of course.

 

Regards

 

I hope this message is correct fot the thread

 

Pierre

 

PS : in my neighborhood we go to fiber
So intermittent communication right now

 

 

> Message du 31/10/19 17:03
> De : "Samuel Gougeon" 
> A : users@lists.scilab.org
> Copie à : 
> Objet : Re: [Scilab-users] k*Ts - tr: Re: CLR design component is not clear 
> in scilab 6.0.2 x64 W10
> 
> Le 31/10/2019 à 15:29, Pierre PERRICHON a écrit : > >  Dear Samuel, > > if we 
> replace Ts by k*Ts, what does it give? (we hope the same symbol > than for .s 
> > Pierre, As written yesterday, we can't use different symbols/separators for 
> distinct kind of left and right operands. If we chose one, it will be the 
> only and same one for all multiplications. So yes, it will be the same 
> symbol. PS: could you please use "Reply to: users@"  when following-up a 
> discussion? Otherwise, this breaks the thread and makes harder reading it, 
> and duplicates threads. Thanks Samuel 
> ___ users mailing list 
> users@lists.scilab.org http://lists.scilab.org/mailman/listinfo/users___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

[Scilab-users] k*Ts - tr: Re: CLR design component is not clear in scilab 6.0.2 x64 W10

[Pierre PERRICHON]

 

Dear Samuel,

if we replace Ts by k*Ts, what does it give? (we hope the same symbol than for 
.s

Sincerely

 

 

 

> Message du 31/10/19 15:11
> De : "Pierre PERRICHON" 

> A : "UsersmailinglistforScilab" 
> Copie à : 
> Objet : tr: Re: [Scilab-users] CLR design component is not clear in scilab 
> 6.0.2 x64 W10
> 
>
Dear all

>  

I think this representation (Federico) is the best one and the most relevant.
It is even better than the one proposed in Simulink.
I sincerely and strongly hope it will be adopted

> Best regards
Pierre

>  

> Here is the last Samuel proposal, the top of the top

> Very very nice idea !

> That's professional and the better I've never seen !

>  

> 

>  

> Regards

> Message du 31/10/19 10:57
> De : "Pierre PERRICHON" 

> A : "UsersmailinglistforScilab" 
> Copie à : 
> Objet : Re: [Scilab-users] CLR design component is not clear in scilab 6.0.2 
> x64 W10
> 
>
> >  

> > Dear all, dear Samuel,

> >  

> > Many thanks for your gallery

> > For me the better d

> >  

> >  

> > 

> >  

> Message du 31/10/19 00:16
> De : "Samuel Gougeon" 
> A : users@lists.scilab.org
> Copie à : 
> Objet : Re: [Scilab-users] CLR design component is not clear in scilab 6.0.2 
> x64 W10
> 
>
Le 30/10/2019 à 23:25, Federico Miyara a écrit :
>

> Samuel,
> 
> In another e-mail that for some reason was not sent (and was completely 
> deleted...) I mentioned this page 
> https://en.wikipedia.org/wiki/List_of_mathematical_symbols and standard ISO 
> 8-2, which in its clause 9, item 2.9.5 
> > > I have well received it, but in private, and ending with this reference, 
> > > that is not public (to buy)
> (not sure that i can access to it from my University. Will try later).

> > > 
>

says that symbol for multiplication is either · or ×, and that they can be 
omitted if no misunderstanding is possible, and presents two examples of 
omission, one with space, such as a b, and one without space, such as ab (I 
suppose this is when one has been already using a and b or they are immediately 
explained).
> 
> > > 
>

> > > Thanks for this explicitness.
>


> I like the space more, it is more general and the only situation where it 
> would be ambiguous is between numbers, such as 1.234 58 (since the thousand 
> separator is a short space according to the ISO-BIPM GUM), but between 
> numbers × is customary.
> 
> > > It would be very hard (and easily prone to errors, due to many specific 
> > > cases, using parentheses, etc) to parse the input to detect all possible 
> > > cases (1-char symbols, multiple-char symbols, literal numbers with or 
> > > without exponential notations, real or complex, etc) and adapt the 
> > > multiplication symbol accordingly.
> 
> We might even define a "Ts.s=2" structure field in the context, and use it in 
> the input. It works.
> ;-)
> 
> A final possible gallery:
>

> > > 

> > >  

 

> > >

> > > 
>

> > > Regards
>


>


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



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

[Scilab-users] tr: Re: CLR design component is not clear in scilab 6.0.2 x64 W10

[Pierre PERRICHON]

Dear all

 

I think this representation (Federico) is the best one and the most relevant.
It is even better than the one proposed in Simulink.
I sincerely and strongly hope it will be adopted

Best regards
Pierre

 

Here is the last Samuel proposal, the top of the top

Very very nice idea !

That's professional and the better I've never seen !

 



 

Regards

> Message du 31/10/19 10:57
> De : "Pierre PERRICHON" 

> A : "UsersmailinglistforScilab" 
> Copie à : 
> Objet : Re: [Scilab-users] CLR design component is not clear in scilab 6.0.2 
> x64 W10
> 
>
>  

> Dear all, dear Samuel,

>  

> Many thanks for your gallery

> For me the better d

>  

>  

> 

>  

> Message du 31/10/19 00:16
> De : "Samuel Gougeon" 
> A : users@lists.scilab.org
> Copie à : 
> Objet : Re: [Scilab-users] CLR design component is not clear in scilab 6.0.2 
> x64 W10
> 
>
Le 30/10/2019 à 23:25, Federico Miyara a écrit :
>

> Samuel,
> 
> In another e-mail that for some reason was not sent (and was completely 
> deleted...) I mentioned this page 
> https://en.wikipedia.org/wiki/List_of_mathematical_symbols and standard ISO 
> 8-2, which in its clause 9, item 2.9.5 
> > I have well received it, but in private, and ending with this reference, 
> > that is not public (to buy)
> (not sure that i can access to it from my University. Will try later).

> > 
>

says that symbol for multiplication is either · or ×, and that they can be 
omitted if no misunderstanding is possible, and presents two examples of 
omission, one with space, such as a b, and one without space, such as ab (I 
suppose this is when one has been already using a and b or they are immediately 
explained).
> 
> > 
>

> > Thanks for this explicitness.
>


> I like the space more, it is more general and the only situation where it 
> would be ambiguous is between numbers, such as 1.234 58 (since the thousand 
> separator is a short space according to the ISO-BIPM GUM), but between 
> numbers × is customary.
> 
> > It would be very hard (and easily prone to errors, due to many specific 
> > cases, using parentheses, etc) to parse the input to detect all possible 
> > cases (1-char symbols, multiple-char symbols, literal numbers with or 
> > without exponential notations, real or complex, etc) and adapt the 
> > multiplication symbol accordingly.
> 
> We might even define a "Ts.s=2" structure field in the context, and use it in 
> the input. It works.
> ;-)
> 
> A final possible gallery:
>

> > 

> >  

 

> >

> > 
>

> > Regards
>


>


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


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

[Scilab-users] Basic test Bode - Nyquist failed scilab 6.0.2

[Pierre PERRICHON]

Hello

 

BUG DESCRIPTION:

When entering "bode" then immediatly nyquist at the console, we get error at 
nyquist execution.

ERROR LOG:
--

Initialisation :
Chargement de l'environnement de travail

--> bode

--> nyquist
à la ligne 162 de la fonction nyquist ( C:\Program 
Files\scilab-6.0.2\modules\cacsd\macros\nyquist.sci ligne 173 )
à la ligne 13 de la fonction nyquist ( C:\Program 
Files\scilab-6.0.2\modules\cacsd\macros\nyquist.sci ligne 24 )

Erreur : les valeurs doivent être strictement positives lorsque le mode 
logarithmique est activé sur l'axe x.


PS : this test doesn"t run with scilab 5.5.2 ===> error 21

HOW TO REPRODUCE THE BUG:
-


OTHER INFORMATION:
--
This error seems due to the fact that figure n°0 is not killed.

Solution :
1) Killing figure n°0 at the top of bode en nyquist sci file
or
2) generate an aleatory n° for the scf window between 20 and 30 for 
example

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

Re: [Scilab-users] CLR design component is not clear in scilab 6.0.2 x64 W10

[Pierre PERRICHON]

 

Dear all, dear Samuel,

 

Many thanks for your gallery

For me the better d

 

 



 

> Message du 31/10/19 00:16
> De : "Samuel Gougeon" 
> A : users@lists.scilab.org
> Copie à : 
> Objet : Re: [Scilab-users] CLR design component is not clear in scilab 6.0.2 
> x64 W10
> 
>
Le 30/10/2019 à 23:25, Federico Miyara a écrit :
>

> Samuel,
> 
> In another e-mail that for some reason was not sent (and was completely 
> deleted...) I mentioned this page 
> https://en.wikipedia.org/wiki/List_of_mathematical_symbols and standard ISO 
> 8-2, which in its clause 9, item 2.9.5 
> I have well received it, but in private, and ending with this reference, that 
> is not public (to buy)
> (not sure that i can access to it from my University. Will try later).

> 
>

says that symbol for multiplication is either · or ×, and that they can be 
omitted if no misunderstanding is possible, and presents two examples of 
omission, one with space, such as a b, and one without space, such as ab (I 
suppose this is when one has been already using a and b or they are immediately 
explained).
> 
> 
>

> Thanks for this explicitness.
>


> I like the space more, it is more general and the only situation where it 
> would be ambiguous is between numbers, such as 1.234 58 (since the thousand 
> separator is a short space according to the ISO-BIPM GUM), but between 
> numbers × is customary.
> 
> It would be very hard (and easily prone to errors, due to many specific 
> cases, using parentheses, etc) to parse the input to detect all possible 
> cases (1-char symbols, multiple-char symbols, literal numbers with or without 
> exponential notations, real or complex, etc) and adapt the multiplication 
> symbol accordingly.
> 
> We might even define a "Ts.s=2" structure field in the context, and use it in 
> the input. It works.
> ;-)
> 
> A final possible gallery:
>

> 

>  

 

>

> 
>

> Regards
>


>


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

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

Re: [Scilab-users] CLR design component is not clear in scilab 6.0.2 x64 W10

[Perrichon]

Hello Samuel,

 

Thanks you for your positive response. It gives me hope

For literal numbers, sign « . » is also acceptable instead of sign « * »

 

Best regards

Pierre

 

 

De : users  De la part de Samuel Gougeon
Envoyé : mercredi 30 octobre 2019 12:00
À : users@lists.scilab.org
Objet : Re: [Scilab-users] CLR design component is not clear in scilab 6.0.2
x64 W10

 

Hello Pierre,

 

Le 30/10/2019 à 10:26, Perrichon a écrit :

Hello

 

CLR design component brings confusion by forgetting the * sign in operand 

of a polynomial representation in Laplace plan

The "*" sign has been removed on purpose, in order to somewhat compact the
expression displayed in the icon, that can be very wide. It's fine when
coefficients are literal numbers, but you are right: when a coefficient is a
variable, the display then becomes ambiguous. I will see how to detect and
avoid this.

Regards
Samuel

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

[Scilab-users] CLR design component is not clear in scilab 6.0.2 x64 W10

[Perrichon]

Hello

 

CLR design component brings confusion by forgetting the * sign in operand 

of a polynomial representation in Laplace plan

 

It makes schemes unreadeable

 

Could it be corrected in a next version 6.xx

 

Regards

Here is a  first lower pass filter with variable Ts=1 (see also buggzilla
16223)

 



 

 

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

[Scilab-users] lincos instruction : example file pendulum_anim45.zcos is corrupted - Buggzilla 16221

[Perrichon]

Hello,

I seems impossible to correctly open the lincos example, so file
"SCI/modules/xcos/tests/unit_tests/pendulum_anim45.zcos"
I’ve written a buggzilla n° 16221
 

 
 
 
Best regards

 

 

 

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

[Scilab-users] TR: {EXT} Curves color when plotting

[Perrichon]

Hello CL

Thanks you for your response. It’s wise en relevant.

But yesterday, I’ve found 5 minutes ti program the children(x).foreground

Also thanks you for this nice conversation and exchange

 

 



 

Pierre P.

 

 

De : users mailto:users-boun...@lists.scilab.org> > De la part de Chin Luh Tan
Envoyé : mercredi 23 octobre 2019 02:02
À : Users mailing list for Scilab mailto:users@lists.scilab.org> >
Objet : Re: [Scilab-users] {EXT} Curves color when plotting

 

 

Hi,

 

I see. In his case, since Scilab is open source, I think the best way is to 
edit the plot to suit to your need. 

 

for example, you can edit the bode function, add extra line to line 125 and 155

 

// Set datatips info
124 e = gce();
125 e.children.foreground = tcolor(1);  <-- extra line
126 for i=1:size(e.children, "*")
154 ephi = gce();
155 ephi.children.foreground = tcolor(2) <-- extra line
// Set datatips info
for i=1:size(ephi.children, "*")

and the header

 

bode(tcolor, varargin)

so you can call the bode by:

 

bode([2,5],h, 0.01, 100);

 

and get

 

 

 

then you goto the SCI\modules\cacsd\macros\ , run buildmacros.sce to make it 
permanent. 

 

 

CL

 

 

---- On Tue, 22 Oct 2019 15:02:55 +0800 Perrichon mailto:perrichon.pie...@wanadoo.fr> > wrote 

 

Hello,

 

Thanks you for your response

 

I mainly plot curves for bode, nyquist plans, et also time response curves  
with csim.

 

With csim, curves are plotted using plot2d. So the problem is very easy to 
solve :

   simulation=csim(in, t, SYS_FTBF );

   plot2d(t' , [in' 
simulation'],rect=[0,ymin_Temp,tmax,ymax_Temp],style=TColor);

 

where TColor=[2 3 5 4 6 16 5 15];

I suppose that 2, 3 …are index in a Color Table by default.  

 

I have no solution to colorize curves with bode or nyquist, exept to acces to 
children(xx).foreground=TColot(i)

where i is the curve number.

 

That's what I wanted to avoid

 

Best regards

 

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

Re: [Scilab-users] {EXT} Curves color when plotting

[Perrichon]

Hello,

 

Thanks you for your response

 

I mainly plot curves for bode, nyquist plans, et also time response curves  
with csim.

 

With csim, curves are plotted using plot2d. So the problem is very easy to 
solve :

   simulation=csim(in, t, SYS_FTBF );

   plot2d(t' , [in' 
simulation'],rect=[0,ymin_Temp,tmax,ymax_Temp],style=TColor);

 

where TColor=[2 3 5 4 6 16 5 15];

I suppose that 2, 3 …are index in a Color Table by default.   

 

I have no solution to colorize curves with bode or nyquist, exept to acces to 
children(xx).foreground=TColot(i)

where i is the curve number.

 

That's what I wanted to avoid

 

Best regards

Pierre P.

 

De : users  De la part de Chin Luh Tan
Envoyé : mardi 22 octobre 2019 04:48
À : Users mailing list for Scilab 
Cc : Users mailing list for Scilab 
Objet : Re: [Scilab-users] {EXT} Curves color when plotting

 

Hi,

 

from my understanding, easiest way to get the color you wanted is by specifying 
it during the plot function. 

--> plot(x,sin(x),'b')

--> plot(x,cos(x),'b')

will gives u 2 blue lines.

 

 

By default, scilab figure will following the sequence as stated in "help plot"

 

 

"A default color table is used to color plotted curves if you do not specify a 
color. When drawing multiple lines, the plot command automatically cycles 
through this table. Here are the used colors:"

 

R   G   B

0.  0.  1.

0.  0.5  0.

1.  0.  0.

0.  0.75  0.75

0.75  0.  0.75

0.75  0.75   0.

0.25  0.25   0.25

 

no matter what colormap you are changing to before the plot, the plot w/o color 
input will search for the "blue" in the newly define colormap as well. 

 

If the previous methods does not work for you, you could plot the graph, find 
the handle for the line, and change it according to the color index in the 
colormap for the figure.

 

plot(x,sin(x),x,cos(x))

f = gcf();

f.children.children.children.foreground

f.children.children.children.foreground(1) = 2;

 

this will change the second line to blue, as the default colormap f.colormap 
define blue in the second row. (f.color_map)

 

hope this helps.

 

rgds,
CL

 

 On Mon, 21 Oct 2019 18:41:09 +0800 Dang Ngoc Chan, Christophe 
mailto:christophe.d...@sidel.com> > wrote 

 

Hello Pierre, 

> De : Perrichon 
> Envoyé : lundi 21 octobre 2019 12:05 
> 
> Generally, when plotting, curves's color are taken in the range color 
> [1 3 5 7 9 11 13 15 [...] Is there a general way to modify this vector 
> as to get another one with blue as first curve. 

You might consider redefining the colour map: 

https://help.scilab.org/docs/6.0.2/en_US/colormap.html 

Hope this helps, 

regards 

-- 
Christophe Dang Ngoc Chan 
Mechanical calculation engineer 

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

 

 

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

[Scilab-users] Curves color when plotting

[Perrichon]

Dear all,

 

Generally, when plotting, curves's color are taken in the range color [1 3 5
7 9 11 13 15], where 1 is the black color.

So, the first curve is black

 

Is there a general way to modify this vector as to get another one with blue
as first curve.

I don't search something like children(i).foreground=xxx, but a generic
instruction to do when launching a sce or sci files

 

This possible in xcos, with a cscope where colors can be re-organized

Exemple in a cscope : [2 3 5 4 6 16 13 15]

 

Best Regards

 

Pierre P.

 

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

Re: [Scilab-users] Re : How to identify componants in a figure ?

[Perrichon]

Hello,

I thanks all the scilabers for their response:
Antoine, Stephane, Philipp, Samuel

I've try with the "find" function

The result is perfectly what I was waiting for

Also great thanks to everybody 
it takes away a thorn from foot

my nice GUI well works now

Best regards


-Message d'origine-
De : users  De la part de sgoug...@free.fr
Envoyé : vendredi 11 octobre 2019 16:16
À : Users mailing list for Scilab 
Objet : [Scilab-users] Re : How to identify componants in a figure ?

Hello Pierre,

Just do find(a.type=="Axes")

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

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

[Scilab-users] How to identify componants in a figure ?

[Perrichon]

Hello

 

In my application, built with uicontrol in a main figure, I add graphs
(Axes) with bode or Nyquist plot in the the main frame

 

So, at the end, if we do

f=gcf()

I get :

 

children: matrix 39x1

 

I add 

a=f.children

 

Then a is a collection (with bode) :

 

Axes  

uicontrol 

uicontrol 

uicontrol 

uicontrol 

uicontrol 

uicontrol 

uicontrol 

uicontrol 

uicontrol 

uicontrol 

uicontrol 

uicontrol 

uicontrol

...

uicontrol 

uicontrol 

uimenu

uimenu

Axes  

 

So, How can I get, in a loop with length(a), the numbers of the chidren who
are Axes ?

 

In that case I hope something like [1, 39]

 

Is there a way to do that ?

I find nothing with the < get > function ?

 

Thanks

 

Pierre P.

 

 

 

 

 

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

[Scilab-users] Error in messagebox - Part of the image is truncated

[Perrichon]

Dear,

 

When displaying a messagebox, part of the image < warning > or < info > for
example is truncated.

I use W10 with Scilab 5.5.2 x64

 

Must I write a buggzilla message ?

 

How to reproduce :

 

 
message=msprintf("... OptSim window not found !")

 
messagebox(message, "Save Optsim", "warning")

 

Best regards

Pierre P.

 

 

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

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

[Perrichon]

Dear,
Scilab 5.5.2 and MingW  4.6.3 are very ok with w64
4.6.3 is on atoms proposals.
regards



Before printing, think about ENVIRONMENTAL responsabity


-Message d'origine-
De : users  De la part de Stéphane Mottelet
Envoyé : mercredi 25 septembre 2019 21:56
À : Users mailing list for Scilab 
Objet : Re: [Scilab-users] c link (mingw)

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 line25 of function dlwCompile(
> C:\NONINS~1\SCILAB~1.2\contrib\mingw\010~1.5\macros\windows\dlwCompile
> .sci
> line 34 )
> at line70 of function ilib_compile  (
> C:\NONINSTALL\scilab-6.0.2\modules\dynamic_link\macros\ilib_compile.sc
> i line
> 86 )
> at line   104 of function ilib_for_link (
> C:\NONINSTALL\scilab-6.0.2\modules\dynamic_link\macros\ilib_for_link.s
> ci
> line 118 )
> at line18 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/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/maili
> nglists.scilab.org/Scilab-users-Mailing-Lists-Archives-f2602246.html
> ___
> users mailing list
> users@lists.scilab.org
> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists
> .scilab.org/mailman/listinfo/users

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

__

Re: [Scilab-users] gui2bitmap 1.0 is released

[Perrichon]

Samuel Gougeon,
This is a very bad road, also change direction and move 
Your soft doesn't correctly go on


Before printing, think about ENVIRONMENTAL responsabity

-Message d'origine-
De : Perrichon  
Envoyé : mardi 13 août 2019 21:42
À : 'Users mailing list for Scilab' 
Objet : RE: [Scilab-users] gui2bitmap 1.0 is released

1000 messages. I don"t understand that sreen captures need to be in the
whole world, if this is correctly done with a sabnshoop of windows.
Could Scilab team improves palette on Xcos. Here is a real question, and
certainlny not Gougeon pixel routines .

Keep serious please


Before printing, think about ENVIRONMENTAL responsabity

-Message d'origine-
De : users  De la part de VTX1801 Envoyé :
mardi 13 août 2019 21:09 À : users@lists.scilab.org Objet : Re:
[Scilab-users] gui2bitmap 1.0 is released

Samuel,
Observations:
The Windows 10 Snipping Tool has a window mode that accurately captures the
selected window.

Additionally, if you hold down the Alt key when you press the Print Screen
key the window that has focus is captured.
Therefore, there must be a Windows command to capture the window that has
focus.
This command might be available to execute from the gui2bitmap code.


Found this information regarding the window command:

WIN32 API
GetActiveWindow will return the top-level window that is associated with the
input focus. GetFocus will return the handle of the window that has the
input focus.

This article might help:
http://www.microsoft.com/msj/0397/Win32/Win320397.aspx

Hope this helps.
Best regards,
Ted



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

Re: [Scilab-users] gui2bitmap 1.0 is released

[Perrichon]

1000 messages. I don"t understand that sreen captures need to be in the
whole world, if this is correctly done with a sabnshoop of windows.
Could Scilab team improves palette on Xcos. Here is a real question, and
certainlny not Gougeon pixel routines .

Keep serious please


Before printing, think about ENVIRONMENTAL responsabity

-Message d'origine-
De : users  De la part de VTX1801
Envoyé : mardi 13 août 2019 21:09
À : users@lists.scilab.org
Objet : Re: [Scilab-users] gui2bitmap 1.0 is released

Samuel,
Observations:
The Windows 10 Snipping Tool has a window mode that accurately captures the
selected window.

Additionally, if you hold down the Alt key when you press the Print Screen
key the window that has focus is captured.
Therefore, there must be a Windows command to capture the window that has
focus.
This command might be available to execute from the gui2bitmap code.


Found this information regarding the window command:

WIN32 API
GetActiveWindow will return the top-level window that is associated
with the input focus. GetFocus will return the handle of the window
that has the input focus.

This article might help:
http://www.microsoft.com/msj/0397/Win32/Win320397.aspx

Hope this helps.
Best regards,
Ted



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

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

Re: [Scilab-users] Nested function definition

[Perrichon]

Are these functions coming from hydraulic simulator for power plants?

Best regards


Before printing, think about ENVIRONMENTAL responsabity

-Message d'origine-
De : users  De la part de Izabela Wójcik-Grzaba
Envoyé : mercredi 10 avril 2019 17:31
À : Users mailing list for Scilab 
Objet : Re: [Scilab-users] Nested function definition

Ok, sorry. It's my mistake connected with using math terms not properly. 
Now I understand that nested function is more general term in Scilab help. The 
help example is similar to mine and this is the whole misunderstanding.
I appreciate your comprehensive explanation.
Now I am happy because the notation of my (mathematical) functions become 
simpler.

Kind regards,
Iza





W dniu 10.04.2019 17:10, Samuel Gougeon napisał(a):
> Izabela,
> 
> I have not clearly understood why you are speaking about "nested 
> functions" in your example.
> A nested function is a function that is _defined_  in another one.
> 
> About the example in the function help page:
> It is right, but with Scilab 6, it looks a bit outdated to me.
> Indeed, let's consider the following example:
> 
> // Content of the File myTest.sci
> function myTest()
>disp("myTest() is running")
>myNextFun()
> endfunction
> function myNextFun()
> disp("myNextFun() is running")
> endfunction
> // End of myTest.sci file
> 
> When building a library (say "myLib"), this file is compiled, and
> 
>   * With Scilab 5 : both functions myTest() and myNextFun() are 
> registered in the library, and so ARE PUBLIC: Both can be called from 
> anywhere, noticeably from the top-level, the console.
> The only way to make myNextFun() a private function known only by
> myTest() is to define it IN myTest(), as a nested function.
> 
>   * With Scilab 6: only myTest() is registered in myLib library, so is 
> public, and can be called from anywhere. In the opposite, myNextFun()
> 
>   * is NOT registered in the library
>   * so, is unknown from the console,
> 
>   * is shared and can be called only by other functions defined in the 
> same file.
> 
> This is a more powerful implementation for the functions privacy, 
> because then
>   * a private function (say myNextFun()) does no longer need to be 
> recompiled each time that myTest() is called.
> 
>   * IMO, this makes the code clearer
> 
>  This change in Scilab 6 could be documented in the --> help function 
> page, in order to discourage true nested function. By the way, the 
> example in the help misses being indented.
> 
> However, out of libraries, nested functions can still be used in 
> scripts.sce or in files.sci that are just exec()uted, for the same
> purpose: keeping nested functions private.
> 
> HTH
> Regards
> Samuel
> 
> Le 10/04/2019 à 16:04, Izabela Wójcik-Grząba a écrit :
> 
>> Ok, so why nested function in help is so complicated:
>> 
>> //nested functions definition
>> function y=foo(x)
>> a=sin(x)
>> function y=sq(x), y=x^2,endfunction
>> y=sq(a)+1
>> endfunction
>> 
>> foo(%pi/3)
>> 
>> Couldn't it be formulated like below:
>> 
>> function y1=foo1(x)
>> a=sin(x);
>> y1=a^2+1;
>> endfunction
>> 
>> foo1(%pi/3)
>> 
>> That's why I had problems with my functions and couldn't understand 
>> why it has to be so complicated.
>> 
>> Thank you once more.
>> 
>> Iza
> ___
> users mailing list
> users@lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

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

[Scilab-users] EDGE_TRIGGER (Xcos component) doesn't run under XCOS

[perrichon]

Dear

 

I try to run a EDGE_TRIGGER under XCOS 5.5.2 Windows 10 to reset an
integrator with a basic small program.

This program doesn’t run with scilab 5.5.2 and windows 5.5.2.

I get the error « L'élément 3 de la liste n'est pas défini. »

 

See bugzzillla 15914 for the attached file.

 

Best regards

 

Pierre P.

 

 

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

Re: [Scilab-users] Enquiry

[perrichon]

The Teamwork !


-Message d'origine-
De : users  De la part de Rafael Guerra
Envoyé : mercredi 31 octobre 2018 17:39
À : Users mailing list for Scilab 
Objet : Re: [Scilab-users] Enquiry

The French Touch !

-Original Message-
From: users  On Behalf Of Stéphane Mottelet
Sent: Wednesday, October 31, 2018 3:01 PM
To: Users mailing list for Scilab 
Subject: Re: [Scilab-users] Enquiry

The price !

> Le 31 oct. 2018 à 12:31, Kombo Theophilus-Johnson 
>  a écrit :
> 
> What's the advantage of scilab over matlab?
> ___
> users mailing list
> users@lists.scilab.org
> https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/lists.scilab.org/mailman/listinfo/users

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

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

[Scilab-users] tf2ss error in Scilab, comparing Scilab and Matlab

[perrichon]

Dears,

 

We here simulate on xcos and matlab/simulink platform, an oscillator to get
the behavior of a hydraulic water 

harmmer in a penstock, following a transmittance of 2 order : b*s/(1+a*s^2).


Our main reference is based on a canonic method using only two integrators
and we also do some tests with a 

state space representation, with xcos and simulink 

The tfss2 function to go from transmittance state-space representation,  in
xcos, gives results : 

XCOS STATE-SPACE MATRIX 

 A =[ 0.  - 1.3782485 ; 1.0. ] 

  B=[  5.2800843 ; 0.]  

  C=[- 5.28008430. ]  

  D=[ 0.  ] 

  X0[ 0. ; 0.]   

 MATLAB STATE-SPACE MATRIX

A =[ 0.  - 0.7256 ; 1.0.]   

  B =[ 1. ;  0.  ] 

  C=[  - 20.22810.  ] 

  D = [0. ]  

  X0  = [ 0. ;  0.] 

 TRANSFER FUNCTIONS   

  TRANSMITTANCE H

 - 20.228058s  

--

1 + 0.7255586s ^2  

  TRANSMITTANCE MATLAB SYSMATLAB

 - 27.877756s  

--

1 + 1.3781698s ^2   

 

Entering in a numerical scop XY, X=canonic method, Y=State-Space method, we
cleary see a correct behavior 

X=Y with Matlab/Simulink coefficients, and a a very strong dispersion with
Scilab/Xcos computing parameters. 

On another way, and because we need a stable state at t=0 (no oscillation),
apparently, only the canonic 

method runs in all modes (sequence=1 ou 2 in the script). The initial vector
X0 is only able to controll the first 

point, but not the stability in this case, so it works only with a zero
initial condition. 

 

Program Xcos/Scilab, ou Matlab/Simulink, schemes, results are available in
buggzilla n°15771 

Tests have been done with Scilab 5.5.2 under windows W10. 

 

To read you. 

Sincerely 

 

Pierre Perrichon

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

Re: [Scilab-users] [Scicos] - Need advice in creation of Super Blocks via script

[perrichon]

Hello Yves,

Book "Tome 2 - SCILAB - Modéliser et Simuler avec XCOS" gives all
explainations to build SuperBlocks

Sincerely

Pierre


-Message d'origine-
De : users  De la part de Yves Rambi
Envoyé : mardi 19 juin 2018 06:34
À : users@lists.scilab.org
Objet : Re: [Scilab-users] [Scicos] - Need advice in creation of Super
Blocks via script

It's a pity that no one can answer.

Have a good day!



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

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

Re: [Scilab-users] Shift indices

[perrichon]

Dear,

 

this instruction is exactly the one I wanted

 

It allows me on a PELTON 6 jet machine to get a rotating pilot injector

 

Pierre.

 

De : users [mailto:users-boun...@lists.scilab.org] De la part de Samuel
Gougeon
Envoyé : jeudi 9 novembre 2017 00:31
À : Users mailing list for Scilab 
Objet : Re: [Scilab-users] Shift indices

 

Le 08/11/2017 à 15:07, Richard llom a écrit :

Hello,
is there a function available to shift indices?
E.g. I have
aa = [1:10]
and want
bb =  6.   7.   8.   9.   10.   1.   2.   3.   4.   5.


If you need to shift i = 1:n indices by any p -- not necessarily n/2 --, you
may do

si = modulo(i+p-1, n)+1// with n = length(i);

Example:
i = 1:10, p = 2;
si = modulo(i+p-1, length(i))+1
--> i = 1:10, p = 2;
 i  = 
   1.   2.   3.   4.   5.   6.   7.   8.   9.   10.

--> si = modulo(i+p-1, length(i))+1
 si  = 
   3.   4.   5.   6.   7.   8.   9.   10.   1.   2.

Samuel

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

Re: [Scilab-users] Problems getting started with Xcos

[Perrichon]

Hello,
Confirmed




Before printing, think about ENVIRONMENTAL responsabity

-Message d'origine-
De : users [mailto:users-boun...@lists.scilab.org] De la part de Clément David
Envoyé : mardi 30 mai 2017 14:28
À : users@lists.scilab.org
Objet : Re: [Scilab-users] Problems getting started with Xcos

Hello,

Thanks for these information, as you wrote the save / load bug might be related 
to your system. Are you using a specific system locale / languages ?

--
Clément 

Le mardi 30 mai 2017 à 03:52 -0700, arwooldridge a écrit :
> Having similar problems with xcos on scilab 6.0.0 with windows 7 and 10.
> 1/ On saving a model and subsequent reopen, some routes get jumbled 
> like spagetti. ( workaround fix: highlight the route and optimise with SC "O"
> subsequent save and open then works)
> 
> 2/ Some text blocks when saved do not reappear on opening, or 
> sometimes appear top left of window.
> 
> 3/ Some models will not reopen after saving, blank window.
> 
> 4/Some saved models halt with "invalid index" on simulation, no 
> apparent reason or explanation. Models were previously working before saving.
> 
> 5/Superblocks not functioning when created by converting selected group.
> 
> Tried on fresh install on different computer, this time Windows 7, 
> Same bugs exhibited.
> 
> The combination and severity of these bugs make xcos unusable, at 
> least in Windows for me.
> 
> Suspect problem in saving files correctly but cannot pin down further. 
> Could it be spaces in filenames, long filenames or other Windows/Linux 
> discrepancies? As far as I can gather Linux users are not having these 
> problems.
> 
> Models built from scratch without saving appear to work OK, but this 
> is not a workable solution!
> 
> 
> 
> 
> --
> View this message in context: 
> http://mailinglists.scilab.org/Problems-getting-started-with-Xcos-tp
> 4035982p4036490.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

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

Re: [Scilab-users] FORTRAN Block in XCOS

[Perrichon]

Dear,

I'm also interest to translate Fortran to C.
It's a big task looking at MGO and science to translate done by the olders

Good luck



Before printing, think about ENVIRONMENTAL responsabity

-Message d'origine-
De : users [mailto:users-boun...@lists.scilab.org] De la part de
planetcooler
Envoyé : lundi 22 mai 2017 22:25
À : users@lists.scilab.org
Objet : Re: [Scilab-users] FORTRAN Block in XCOS

Is there a Developer's Guide somewhere - for folk who want to develop new
blocks? 





--
View this message in context:
http://mailinglists.scilab.org/FORTRAN-Block-in-XCOS-tp4036422p4036441.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] Low limiter zero of an Integral_m integrator doesn't properly work (Scilab Xcos 5.5.2)

[Perrichon]

 

 

Dear Xcos team,

 

In my process, I use an integrator Intergral_m with limiters bewteen 0 and
1.

It seems that small négative values are not taken into account. So the lower
limiter doesn't properly work

 

It seems mandatory to add a saturation 0-1 to get a correct result, which is
redondancy with the limiters.

 

In my record BUGLimiteurIntegrateur.scg , we can see value -8.30 e-101
behind the integrator with limiter

 

 

See http://bugzilla.scilab.org/show_bug.cgi?id=15077 for attached files

 

 

 

Best regards

 

 

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

[Scilab-users] Transcient error in VARIABLE DELAY during initialization

[Perrichon]

Hello,

 

Looking at the example provide in its documentation, and initializing at 1
the initial input, VARIABLE DELAY box shows a real problem in the transcient
phase of that function

 

This bug explains a ; unexpected transcient error in my project (hydraulic
transcients).

 

 

See for attached file ;

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

 

Sincerely

Pierre

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

Re: [Scilab-users] Question about javasci V2

[Perrichon]

Hello Daniel,

 

Here is a basic program I’ve realized under netbeans 7.01

It works with scilab x64 windows 7 or 10, scilab 5.5.2 ; not with 6.0.0 b2

 

Also here are the libraries to incilude in your java project (eclipse if i well 
understood) :

 

org.scilab.modules.jvm.jar

org.scilab.modules.javasci.jar

org.scilab.modules.core.jar

org.scilab.modules.types.jar

JDK1.8

 

It works with jdk1.8.0_40

 

 

//

// Java program and main program

/*

* To change this template, choose Tools | Templates

* and open the template in the editor.

*/

package testscilabv2;

 

import org.scilab.modules.javasci.Scilab;

import org.scilab.modules.types.ScilabType;

import org.scilab.modules.types.ScilabDouble;

 

 

/**

*

* @author pierre

*/

public class TestScilabV2 {



static boolean bgraph;

 

/**

 * @param args the command line arguments

 */

public static void main(String[] args) {



 



try {

 

Scilab sci = new Scilab(true);

 

if (sci.open()) {

/* Send a Scilab instruction */

sci.exec("foo = [ 2, 4, 6; 4, 0, 10; 6, 10, 12 ];");

 

/* Retrieve the variable foo */

ScilabType foo = sci.get("foo");

 

/* Display the variable */

System.out.println("Representation of  : " + foo);

 

/* Get the data and retrieve the 2,2 value */

double[][] aReal = ((ScilabDouble)foo).getRealPart();

System.out.println("foo[1,1] = " + aReal[1][1]);

 

/* Change the value of 2,2 */

aReal[1][1] = Math.PI;

 

/* Create a new variable */

ScilabDouble bar = new ScilabDouble(aReal);

 

/* Send it to Scilab */

sci.put("bar", bar);

 

/* Display it through Scilab */

sci.exec("disp(bar)");

   

sci.exec("about();");

   

   sci.exec("plot3d();");

   

   System.out.println("\nFermer le grahique pour terminer le 
programme de test...");

   

do {

// Boucle tant que le graphique n'a pas été refermé

//-

bgraph=sci.isGraphicOpened();

sci.exec("aPPeScilabJavasciv2=1;");



  

  

  }while (bgraph);

 

sci.close();

   

   
System.out.println("...Fin du programme de test");

   

} else {

System.out.println("Could not start Scilab ");

}

 

 

/* Can be improved by other exceptions: AlreadyRunningException,

 * InitializationException, UndefinedVariableException,

 * UnknownTypeException, etc

 */

} catch (org.scilab.modules.javasci.JavasciException e) {

System.err.println("An exception occurred: " + 
e.getLocalizedMessage());

}

 





    

  

}

}

 

 

De : Daniel Neutzler [mailto:daniel.neutz...@haw-hamburg.de] 
Envoyé : lundi 13 février 2017 13:07
À : Perrichon ; 'Users mailing list for Scilab' 

Objet : Re: [Scilab-users] Question about javasci V2

 

Hello Pierre,
thank you for your answer. It is nice to hear that my Problem is probably a Bug.
I'm not sure how to use your example. Which Libs do I need for it or may you 
have a simple example to use it?
I'm sorry, my Java knowlegde is restricted (Beginner).

Thank You for your Help,
Daniel Neutzler



Am 04.02.2017 um 19:29 schrieb Perrichon:

Hello Daniel

 

I’ve already met your problem one year ago, and for me it is really a bug.

 

I work with scilab x64 5.5.2, netbeans 7.01, on W7 or W10 platform.

 

I’ve sovled it in my application, so I’m just able to propose parts of code.

 

I’ve delay the 2 instructions Scilab sci = new Scilab(true)  and if 
(sci.open()) {, by creating a ScilabManager class, … and a thread class na

Re: [Scilab-users] Question about javasci V2

[Perrichon]

Hello Daniel

 

I’ve already met your problem one year ago, and for me it is really a bug.

 

I work with scilab x64 5.5.2, netbeans 7.01, on W7 or W10 platform.

 

I’ve sovled it in my application, so I’m just able to propose parts of code.

 

I’ve delay the 2 instructions Scilab sci = new Scilab(true)  and if 
(sci.open()) {, by creating a ScilabManager class, … and a thread class named  
Idle

 

Part of ScilabManager  (also note the  public static void OpenScilab())

 

public class ScilabManager {



public static Scilab sci;   //Driver Scilab

public static boolean bScilabOpen;

public static boolean InitScilab;   

 

public  static Fifo FifoScilab;

private static TListeFifo SciJob;

 

static ScilabError TErrorScilab;

 

public static File ScilabFile;

 

private static int dim = 500;

public static String [] Script;

private static int iScript;



public static Configuration AppConfiguration;  

public static Log LogScilab;  



public static int NumGraph=0;

 

 

ScilabManager() {

try {

sci = new Scilab(true);

InitScilab=true;



   } catch (JavasciException.InitializationException ex) {

Logger.getLogger(ScilabManager.class.getName()).log(Level.SEVERE, 
null, ex);

}





}



@SuppressWarnings("CallToThreadDumpStack")

public static void OpenScilab() {





try {



bScilabOpen=sci.open();



} catch (JavasciException ex) {

ex.printStackTrace();

}



if (bScilabOpen) System.out.println("\nScilab est ouvert\n");

else System.out.println("\nErreur ouverture Scilab\n");   



ScilabError.ClearScilabError();   



try {

// Initialisation et chargements des fonctions Scilab

//---

AppConfiguration = new Configuration();

} catch (FileNotFoundException ex) {

Logger.getLogger(ScilabManager.class.getName()).log(Level.SEVERE, 
null, ex);

} catch (IOException ex) {

Logger.getLogger(ScilabManager.class.getName()).log(Level.SEVERE, 
null, ex);

} catch (JavasciException ex) {

Logger.getLogger(ScilabManager.class.getName()).log(Level.SEVERE, 
null, ex);

}



try {

// Initialisation du fichier de log out (Traces commandes Scilab)

//--

LogScilab = new Log();

OptsimView.SetLogFile();

} catch (FileNotFoundException ex) {

ex.printStackTrace();

} catch (IOException ex) {

ex.printStackTrace();

}   



Script = new String[dim];

 

Now note part of Idle task :

 

public class Idle extends Thread  {



protected volatile boolean IdleRunning = true;

public static boolean bCloseIdle=false;



private static int Count=1;

private static int setGraphe=0;

 

 

private static JTextField TF=null;

private static Timer bTimer;

private static JLabel AnimationLabel;

private static Icon idleicone;

 

private int ThreadNumber;

 

 

Idle (JTextField TFi, Timer busyIconTimer,

  JLabel statusAnimationLabel, Icon icone) {

TF=TFi;

bTimer=busyIconTimer;

AnimationLabel=statusAnimationLabel;

idleicone=icone;

this.ThreadNumber=Count++;

}

 

  @Override

  public synchronized void run() {

  

boolean bTest;



if (ScilabManager.InitScilab) {



ScilabManager.OpenScilab();

}



ScilabManager.sci.exec("aPPeScilabJavasciv2=1;");

 



while (IdleRunning) { …etc

 

So instructions Scilab sci = new Scilab(true)  and if (sci.open are delayed.

 

This is the only solution I’ve found. After that Scilab well run with Java 
netbeans and javasci2.

 

Also well note that my program doesn’t work with Scilab 6.0.0 b2 at compile 
time and see :

 

 

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

 

Hope it helps you

 

Sincerely

Pierre

 

De : users [mailto:users-boun...@lists.scilab.org] De la part de Daniel Neutzler
Envoyé : mardi 31 janvier 2017 13:15
À : users@lists.scilab.org
Objet : [Scilab-users] Question about javasci V2

 

Hi, I am using Scilab 5.5.2 and trying to open a Scilab script from
Java. Therfore I followed the documentation: Compute and run with javasci v2.

I use Eclipse to compile and run. It works, but I want now to open it in 
"advanced mode"  to get grahpics
(Scilab sci = new Scilab(true);). If i do it, I get a compile Error. What's 
wrong ?
Code and Error Plot out see below.

Thank You for your Help,
Daniel Neutzler

Error#

Re: [Scilab-users] Printf on console in a c file

[Perrichon]

Hello

I've finally found what I wanted in my C function, with Coserror instruction

Coserror("Lower limiter greater than the Upper");

Thanks for your response



Before printing, think about ENVIRONMENTAL responsabity

-Message d'origine-
De : users [mailto:users-boun...@lists.scilab.org] De la part de Tim Wescott
Envoyé : mardi 20 décembre 2016 19:48
À : Users mailing list for Scilab 
Objet : Re: [Scilab-users] Printf on console in a c file

On Tue, 2016-12-20 at 15:02 +0100, Perrichon wrote:
> Hello,
>  
> I’d like to print in a C file (inside a palette) on the console, but 
> nothing appends.
> Have anybody an idea on how to proceed ?
>  
> I’ve also try something  like :
> fprintf(stderr,"\n Lower limiter greater then Upper one"); but I get 
> errors at compile time, includind stdio.h

Are you trying to use the C standard library printf, or the Scilab printf?

It's been a while since I've done combined C and Scilab code, but if I remember 
correctly you can call Scilab functions from C -- that's probably what you'll 
need to do.

-- 

Tim Wescott
www.wescottdesign.com
Control & Communications systems, circuit & software design.
Phone: 503.631.7815
Cell:  503.349.8432



___
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] Impossibility to generate C code with a basic sum example

[Perrichon]

Dear Xcos team,

 

I try to generate a C code with a basic super bloc containing only a sum
with 2 inputs.(out = in1 + in2)

The generator doesn't produce any code and signals 3 errors

 

Error 1 :
"Not enough information to find ports sizes. I try to find the problem"
 
Error 2:
"Impossible de générer une erreur dans un superbloc. Veuiller compiler le
diagramme pour signler l'erreur"
 
Error 3:
"Problème avec la taille ou le type de port"

 

Note : I have already generated C code using the C generator wihout any
problem, and functions were more complicated

 

 

See bug #14904 for attached files

 

Sincerely

Pierre

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

[Scilab-users] Printf on console in a c file

[Perrichon]

Hello,

 

I'd like to print in a C file (inside a palette) on the console, but nothing
appends.

Have anybody an idea on how to proceed ?

 

I've also try something  like :

fprintf(stderr,"\n Lower limiter greater then Upper one");

but I get errors at compile time, includind stdio.h

 

Sincerely

 

Pierre

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

Re: [Scilab-users] toolbox_skeleton.iss

[Perrichon]

Dear,

The answer interests me

Sincerely

Pierre

 

De : users [mailto:users-boun...@lists.scilab.org] De la part de Samuel Gougeon
Envoyé : jeudi 15 décembre 2016 22:15
À : International users mailing list for Scilab. 
Objet : [Scilab-users] toolbox_skeleton.iss

 

Hello,

The SCI/contrib/toolbox_skeleton directory used as template to create a toolbox 
embeds a toolbox_skeleton.iss file. The usage of this one is not documented, 
neither in the file, nor in the native Scilab help, nor on the dedicated wiki 
page https://wiki.scilab.org/howto/Create%20a%20toolbox

What is this file for?

Is it useful for a toolbox made only of macros?

Thanks for any hints
Samuel Gougeon

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

[Scilab-users] Automatic C generator SuperBlock - Coding error in sci file - bad rendering of component XCOS

[Perrichon]

Dear XCOS team,

 

After adding a component to my palette Ma Palette, I include the new
component in Ma Palette, using the automatic C generator.

I see bad instruction in the generated PB_c.sci file. The consequence is a
bad rendering of the component in the Xcos editor, as shown in the Photo

of the Bug file

 

See bugzilla #14882 for attached files

 

There is a workaround for this problem, waiting for a correction :

 

   //Instructions with bug

   //-

 
//gr_i="xstringb(orig(1),orig(2),""PB"",sz(1),sz(2),""fill"")"

   //sciblk = standard_define([2 2],model,[],gr_i);

   

   //Instruction without bug in the palette components

   //--   

   x0=0;reinit=0;

   exprs = [sci2exp(x0);sci2exp(reinit)];

   sciblk = standard_define([2 2],model,exprs);

 



 

 



 

Sincerely

Pierre

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