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 :
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
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 Scil
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 Sci
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", "w
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
uicontro
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'or
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 childre
) = 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
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
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
http://lists.
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 buggzil
: [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
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-us
cilab'
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
ma
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''u
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 wel
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,
L
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))
xs
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
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@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 i
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,
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. Som
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 :
Hell
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 > inst
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 correct
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
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 th
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/l
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 ther
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
Iv
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
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
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
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
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
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
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
att
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,
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
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 diagra
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-u
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,
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
or 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 Perri
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
He
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 benchma
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
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/
d 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,
Gla
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'
tures,
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
: 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 alg
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.
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
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 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\s
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
ist 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 Fil
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
He
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
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 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 ca
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,
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
-Me
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 » instructi
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.
__
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, Erro
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
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
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 r
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 understand
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 matric
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(N
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
1000 messages !
Before printing, think about ENVIRONMENTAL responsabity
-Message d'origine-
De : users [mailto:users-boun...@lists.scilab.org] De la part de Rafael
Guerra
Envoyé : lundi 4 avril 2016 22:24
À : 'Users mailing list for Scilab'
Objet : Re: [Scilab-users] "Smoothing" very l
Dear all,
I've written a java program which use javasci, and which perfectly works
using scilab 5.5.2 or 5.5.3, with 0x32 or 0x64 configuration.
This program fails with scilab 6.xx. So I've tried the basic example v2
provided inside the package, same conclusions : ok with 5.5.2, nok with
6.x
Hello
I retrieve an old xcos program about hydraulic simulation.
Worry :
A superblock containing a vairable < tf < doesn't match the value
programmed in the initialization part.
If < tf > a reserved word and where can I find a reserved list
Or is it a bugg ?
Are other variables c
in Scilab, functions can see the superior-scope variables (here, 'tf').
So just write "tmf=3; tf=2;" in your context and everything should run fine.
Regards,
Paul
On 06/10/2016 06:47 PM, Perrichon wrote:
Hello
I retrieve an old xcos program about hydraulic simulation.
the modifications will be lost (their scope is limited to the
context).
Regards,
Paul
De : Perrichon [mailto:perrichon.pie...@wanadoo.fr]
Envoyé : lundi 13 juin 2016 18:44
À : 'Users mailing list for Scilab'
Objet : RE: [Scilab-users] Xcos - Problem with tf variable name in a
Dear,
With Scilab-Xcos 6.0.0 beta (1 or 2), signs are no more taken into account
and drawn in BIGSOM and PRODUCT components
All was correctly working with Scilab 5.5.2.
More, if we use a schema done with Scialab 5.5.2 and edit it with Scilab
6.0.0. beta2, signs or operations are pr
Dear,
Apparetly, CSCOPE component with Xcos doesn't work under W10 Scilab x64
6.0.0.0 beta 2.
We get the error
< cscope is compiled without GUI, cannot use Scope >
See also Bug #14599
Sincerely
Pierre
Bug_Scope.zcos
Description: Binary data
Dear,
When plotting a figure, menus « Editions/Propriétés de la figure » or «
Edition/Propriétés des axes » are bugged with Scilab 5.5.2 W10 x64, and open
an empty window "Figure Editor" which is not possible to re-close
Important note : that doesn't happen with Scilab 5.5.2 W10 x32
PS : Same problem with Scilab 6.0.0 x32 W10
Sincerely
De : Perrichon [mailto:perrichon.pie...@wanadoo.fr]
Envoyé : mercredi 22 juin 2016 11:51
À : 'users@lists.scilab.org'
Objet : 2016.06.22 - Xcos - CSCOPE doesn't work under W10 Scilab x64 6.0.0.0
beta 2
Dear,
Hello,
It is impossible to record a signal using WriteC_f component with scilab
5.5.2 x64 on W10.
That correctly works using scilab 5.5.2 x32 on W10.
ERROR LOG:
--
On Scilab console, we obtain :
Warning !!!
Scilab has found a critical error (EXCEPTION_ACCESS_VIOLATION)
with
Good evening,
I wrote a program in Scilab 5.5.2 x64 W10 witch multiplie 4 by 3 and sends
result on a display device.
I try now with Scilab 6.0.0 x64 beta 2 W10, and mutiplie 5 by 3. Normally
result is 15.
Here:
Remark 1:
Display of PRODUCT_f is bugged (not conform, see attached f
b.org/18287 .
Note that the bug is just a rendering bug and does not impact simulation values.
Regards,
--
Clément
Le lundi 20 juin 2016 à 19:25 +0200, Perrichon a écrit :
> Dear,
>
> With Scilab-Xcos 6.0.0 beta (1 or 2), signs are no more taken into
> account and drawn in B
Hello,
I am so disapointed to learn the futre disaspperance of WFILE_f component
for a lot of reasons (Scilab 6.0.0 branch)
1 - Actually, WRITEC_f doen't replace WFILE_f. It seems impossible to obtain
an ASCII file with the proposed format in that box or I don't know how to do
with in
Hello,
When using plot3d instruction with scilab 5.5.2 W10:
-with x32, background color is correct and white
-with x64, background color is cyan and the figure unreadable. It breaks my
program demonstration (done with javasci which doesn't work with scilab
6.0.0 beta2)
See also
18:11, Perrichon a écrit :
Dear,
When plotting a figure, menus « Editions/Propriétés de la figure » or «
Edition/Propriétés des axes » are bugged with Scilab 5.5.2 W10 x64, and open
an empty window "Figure Editor" which is not possible to re-close
Important note : that doesn
Hello,
Ive tried to download Scilab Master Nightly built 6.0.0 x32 beta 2 this
morning, but its impossible when clicking.
It goes directly to the « Merci davoir téléchargé Scilab » page.
Site : http://www.scilab.org/fr/development/nightly_builds/master
Sincerely
Dear,
BUG DESCRIPTION:
A basic program compare a sinusoidal signal with 2 thresholds S1 and S2.
This function used an EXPRESSION block, the ouput is 1 if the signal is
between the two signals, 0 else.
The program correctly runs with scilab 5.5.2 x64, but fails with Sci
Hello,
Annotations are not properly laid or lost in Xcos templates from Scilab
5.5.2 to Scilab 6.0.0 x64 w10
In the original shema written with scilab 5.5.2 x64 w10, we draw 4
components. For each component, we edit an annotation : "Generator",
"Link1", Real
Time Clock", "Numeric scop
Dear,
Diagrams shifting error using Xcos 5.2.2 x64 w10. Annotation of a connector
between 2 boxes don't follow the movment and stay in place.
In the original shema written with scilab 5.5.2 x64 w10, we draw 4
components. For each component, we edit an annotation : "Generator",
"Link1",
Hello,
Loss of Annotation on connector in a SuperBlock using Xcos 5.5.2 x64 w10.
Annotation of a connector between 2 boxes is lost.
In the original shema written with scilab 5.5.2 x64 w10, we draw 4
components. For each component, we edit an annotation : "Generator",
"Link1",
Real Time
ment
>
> Le mardi 28 juin 2016 à 12:31 +0200, Perrichon a écrit :
> >
> > Hello,
> >
> > I’ve tried to download Scilab Master Nightly built 6.0.0 x32 beta 2
> > this morning, but it’s impossible when clicking.
> > It goes directly to the « Merci d’
Hello,
Today, the Nightly Buid server delivers the same version
scilab-master-1467282800_x64.exe, and display 6.0.0 when executing ver()
instruction.
So it creates a full confusion to distinguish bugs from 5.5.2 or 6.0.0, or
appreciates improvments.
Sincerely
Pierre
___
Dear,
When I click a zcos file or sce file, the Scilab GUI opens, but not Xcos for
zcos ou Scinotes for sce files.
It was working 1 month ago, but now I can't do anything, even if I
re-install Scilab 5.5.2 x64 W10
Note : others Scilab version are installed on my machine : Scilab 5.5.2
m with Wscilex, or a bad
management done by W10
To read you
Sincerely,
Pierre
Correct icons :
Bad icons :
De : Perrichon [mailto:perrichon.pie...@wanadoo.fr]
Envoyé : samedi 2 juillet 2016 18:51
À : 'Users mailing list for Scilab'
Objet : 2016.07.02 - Double click
1 - 100 of 144 matches
Mail list logo
