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";
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 ùùééêë"
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
&
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 dont
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
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
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
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
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.
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 »
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
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
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
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:
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
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
or 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
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
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.
Best regards
W10 x64
function Sound1()
// by Gary Scavone, McGill University, 2004
// Bell-like sound
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
: 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 algorith
,
separately.
Best regards
Samuel
Le 27/02/2020 à 12:18, Perrichon a écrit :
Hello,
Ive 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
nformation 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 : R
ilab 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 y
f 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, P
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
Sorry , I wanted to write :
Ive 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
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,
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
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
Hello Samuel
I dontt 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
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
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
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,
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
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
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
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
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
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
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
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
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
Ive download
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
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
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
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
ers 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 c
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 >
, 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,
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.
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
: 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
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
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
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))
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/
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
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
'
Objet : Re: [Scilab-users] Scilab cannot work on macOS 10.15 Catalina:
Anyprogress 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
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:
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 P
ble%22=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
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
rs@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
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
!
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
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
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 à
: [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 "*" sig
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
Hello,
I seems impossible to correctly open the lincos example, so file
"SCI/modules/xcos/tests/unit_tests/pendulum_anim45.zcos"
Ive written a buggzilla n° 16221
Best regards
___
users mailing list
users@lists.scilab.org
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 p
ine 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
> Envo
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
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
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
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",
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
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
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
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
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 doesnt 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.
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:
, 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
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] -
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
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
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
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
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
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.org] De la part de Tim Wescott
Envoyé : mardi 20 décembre 2016 19:48
À : Users mailing list for Scilab <users@lists.scilab.org>
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
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
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
Dear Scilab Team,
Trying to build a simple toolbox as described in book "Scilab : De la
théorie à la pratique : MaPalette-PlusInt", produce error at link time with
options automatically generated to the linker ; wrong ,W1 option at the end
of the command line.
This bug blocks my
Hello Samuel,
Its seem rather a good idea.
I also think it could be improved on the left when developping the main
under subjects, like « Optimisation » for example. Aslso a development with
click on the array or the title.
This is not done for most of items.
But the idea ais welcome.
Hello Rafael,
May be try with Pierre Henry, the famous author of : « Messe pour le temps
présent »
This is still pop.
De : users [mailto:users-boun...@lists.scilab.org] De la part de Rafael
Guerra
Envoyé : samedi 5 novembre 2016 13:43
À : Users mailing list for Scilab
Dear scilab team,
Drag and drop a STEP_FUNCTION in the edit window produces errors.
Then, it is not possible to modify the trigger with a time lower than 1
second ; which was correctly working with scilab 5.5.2.
Error after drag and drop :
Xcos error: Wrong value for field
1 - 100 of 133 matches
Mail list logo
