from:"Dirk Reusch"

Re: [Scilab-users] Scilab 6 // Redefinement of permanent variable does not raise an error!?

2017-05-08 Thread Dirk Reusch

Hi Samuel,

Yes, you are right ... I was looking for a message like "error: ",
so may be the formatting of the message could be improved?

Anyway, there is another glitch:



Startup execution:
  loading initial environment

--> a=123;predef("all");a=456

Redefining permanent variable.

--> [msg,err]=lasterror()
 err  = 

   999.

 msg  = 

 Redefining permanent variable.



It seems, that the error number is now 999 and it has
been or should be 13 (cf. help error_table)?.

Regards,

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

[Scilab-users] Scilab 6 // Redefinement of permanent variable does not raise an error!?

2017-05-07 Thread Dirk Reusch

Hi,

---

Startup execution:
  loading initial environment

->a = 123
 a  =
 
123.  
 
-->predef("all")
 
-->a=456

Redefining permanent variable.
 
-->a
 a  =
 
123.  

---

IMHO, an error should be raised as in Scilab 5.5.x!

Regards,

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

Re: [Scilab-users] Modelling dynamic systems with real world data

2017-04-13 Thread Dirk Reusch

Hello,

This Modelica library might be inspiring:
 
https://github.com/modelica/ElectricalEnergyStorage

Regards,

Dirk

On Thu, 13 Apr 2017 16:15:01 +
Michael J McCann  wrote:

> Hmm... batteries: Charge storage devices which have a largely
> constant voltage in the working range but which show big changes in
> apparent voltage when they reach full charge and when the charge
> drops very low. You don't get all the electrons back. I suspect a
> really good model would relate these effects to the electrochemical
> processes at work. Also because they are "batteries" and not
> individual cells,  the aggregate behaviour will depend on the whole
> (in series) set. With a sort of diodes and resistors model for the
> charge and discharge routes (somewhat different characteristics), it
> is possible to make a fair model for a battery's functional
> operations but I'd be a bit concerned if it was to try to make
> predictions of behaviour under stress  (e.g.very high discharge
> rates) or temperature changes (which in lead acid batteries reduce
> apparent capacity and ability to deliver current). There's an
> industry emerging for batteries with all the associated support
> equipment for creating backups for solar power etc. So it becomes a
> question of how deep you want to go into the physics.
> 
> Mike.
> 
> =
> On 12/04/2017 16:02, t...@wescottdesign.com wrote:
> >
> > I strongly suspect that anything that would be useful would be 
> > specific to batteries, and would perhaps be best done in batch mode
> > to generate a model that is then hand-tweaked and selected for use
> > in xcos -- but I say that in part because over the years I've come
> > to dislike graphical solvers.
> >
> > I think it's possible to build a subsystem out of blocks that can
> > be "masked" so that you can enter parameters in the usual way -- if
> > you could boil your battery model down so that it had a few
> > parameters, you could translate your measured data into parameters
> > once, then use parameterized blocks for the battery behavior.
> >
> > On 2017-04-12 07:49, phillip mobley wrote:
> >
> >> Sure thing Tim,
> >> Thank you for pointing out those details. I will share as much as
> >> I can. I am simulating the behavior of a battery as it is
> >> discharging into a circuit. I recorded data from the battery (for
> >> example, the voltage and current and internal resistance) during
> >> testing. I currently have the data at different time steps inside
> >> of an excel file. I would like to test this battery under
> >> different circuit configurations. However, changing the circuit
> >> can be time consuming and expensive. I was thinking that I could
> >> use xcos ability to do circuit simulation to construct a basic
> >> model of the battery that I am using that utilizes the data that I
> >> gathered. This way I can simulation the battery under different
> >> circuit configurations very easily.
> >> So I was wondering if there was a way that I could import my data 
> >> into xcos to construct a model for simulation.
> >> I actually created the system to simulate the battery.
> >>
> >> On Tue, Apr 11, 2017 at 3:48 PM, Tim Wescott
> >> mailto:t...@wescottdesign.com>> wrote:
> >>
> >> "Simulate the data"?
> >>
> >> Surely you mean you wish to simulate the system which was used
> >> in the measurement!
> >>
> >> You don't give much detail, but I suspect that what you want
> >> to do is to develop a model of the system that fits the
> >> experiment, and then use
> >> that model in your simulations.
> >>
> >> The general term for generating the model is called "system
> >> identification", but that covers a pretty broad swath.
> >>
> >> Can you share the test you did, the sort of data you
> >> collected, the sort of system you're trying to model, and how well
> >> you know the system
> >> itself?
> >>
> >> On Tue, 2017-04-11 at 15:10 -0400, phillip mobley wrote:
> >> > Hello all,
> >> >
> >> > I have some data from a test that I preformed. I was looking
> >> > to simulate this data under different conditions and I was
> >> wondering if
> >> > there is a palette in xcos that would allow me to input data
> >> > (maybe from an excel spreadsheet or copy paste) in order to
> >> > use in the simulation?
> >> >
> >> > Is this possible with xcos?
> >> > ___
> >> > users mailing list
> >> > users@lists.scilab.org 
> >> > http://lists.scilab.org/mailman/listinfo/users
> >> 
> >> --
> >>
> >> Tim Wescott
> >> www.wescottdesign.com 
> >> Control & Communications systems, circuit & software design.
> >> Phone: 503.631.7815 
> >> Cell: 503.349.8432 
> >>
> >>
> >>
> >> ___
> >> users mailing list
> >> users

Re: [Scilab-users] [Scilab-Dev] Scilab release frequency ?

2017-04-10 Thread Dirk Reusch

Hello,

regarding future release cycles, I would really appreciate to see
offical releases as needed and based primarily upon stability criteria.

IMHO, for production use, especially after the big step from 5.x to 6.x,
it is inevitable to have official 6.0.x bug fix releases asap, otherwise
developers and users will stick to 5.5.x and get frustrated ...

Nightly builds are fine, as a testing and development platform, but not
really suited for end users ...

Regarding the incorporation of new features, it is IMHO not that
important to know, how many releases will be made per year.
It is important to know, when will a new feature be available and
useable.

In summary, I would like to see official releases as needed, rather than
following a rigid schedule.

Best regards,

Dirk

PS: Why are Coverity Fixes not directly applied to the 6.0 branch?
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

[Scilab-users] Cell insertion operation using {...} is buggy?!

2017-04-10 Thread Dirk Reusch

Hello,

Using precompiled Scilab 6.0.0 Linux 64bit, I experienced the
following:



Startup execution:
  loading initial environment
  

--> b{1}=2 // Ok
 b  = 

  [1x1 constant]


--> a=2 // Ok
 a  = 

   2.


--> a{1}=2 // Not OK, should throw an error? 
 a  = 

   1.16D-316

--

It seems, that the cell insertion operation via "{...}" when applied
on an existing variable does strange things.

Thanks for any advice and further insight,

Dirk

PS: Tested also with nightly build  branch-6.0-1488991653 ... with the
very same result!
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

[Scilab-users] Building Scilab 6.0 with Visual Studio 2015?

2017-03-24 Thread Dirk Reusch

Hello,

Has anybody successfully build Scilab 6.0 from source for Windows 64Bit
using Visual Studio 2015?

If yes, does it work out-of-the-box following the instructions given
here https://wiki.scilab.org/Compilation%20of%20Scilab ?

Thanks,

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

Re: [Scilab-users] "findmsvccompiler" is buggy!?

2017-03-23 Thread Dirk Reusch

Hello Antoine,

Please have a look at "dlwFindMsVcCompiler" (cf. below), the list
entries of

funcs = list( ... )
 
and the entries of

compilers = [ ... ]

do *not* match!

Best regards,

Dirk

---

function MSCompiler = dlwFindMsVcCompiler()
MSCompiler = "unknown"; // unknown

// We use always last version of MS compiler

val = getenv("SCILAB_PREFERED_MSVC", "");
if val <> "" then
funcs =

list(dlwIsVc14Express,dlwIsVc12Pro,dlwIsVc14Express,dlwIsVc12Pro,dlwIsVc11Express,dlwIsVc11Pro,dlwIsVc10Express,dlwIsVc10Pro);
compilers = [ ... "msvc140express";
"msvc140pro";
"msvc120express";
"msvc120pro";
"msvc110express";
"msvc110pro";
"msvc100express";
"msvc100pro";];
idx = find(val == compilers);
if idx <> [] then
func = funcs(idx);
if func() then
MSCompiler = val;
return;
end
end
end
...

On Thu, 23 Mar 2017 22:26:18 +0100
antoine.el...@scilab-enterprises.com wrote:

>  
> 
> Hello,
> 
> Can you try with :
> 
> setenv("SCILAB_PREFERED_MSVC","msVC140pro")
> 
> I have 4 versions of VS on my computer and I can switch without
> trouble.
> 
> Regards,
> Antoine
> 
> Le 2017-03-23 21:55, Dirk Reusch a écrit :
> > Hello,
> > 
> > Having installed VS 2013 ("msvc120express") and VS 2015
> > ("msvc140pro") and trying to force the use of VS 2015 via
> > 
> > setenv("SCILAB_PREFERED_MSVC","mscv140pro")
> > 
> > I have noticed that "findmsvccompiler()" still reports
> > "msvc120express".
> > 
> > IMHO there is a bug in "dlwFindMsVcCompiler()", because
> > "dlwIsVc14Pro()" returns correctly %t.
> > 
> > Best regards,
> > 
> > Dirk
> > ___
> > users mailing list
> > users@lists.scilab.org
> > http://lists.scilab.org/mailman/listinfo/users
>  


-- 
Kybernetik Dr. Reusch  |  Phone+49 (0)7127 9579 296
Juchtlenstrasse 11 |  Fax  +49 (0)7127 9579 297
72124 Pliezhausen  |  E-Mail   reu...@kybdr.de
Germany|  Internet www.kybdr.de

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

[Scilab-users] "findmsvccompiler" is buggy!?

2017-03-23 Thread Dirk Reusch

Hello,

Having installed VS 2013 ("msvc120express") and VS 2015 ("msvc140pro")
and trying to force the use of VS 2015 via

setenv("SCILAB_PREFERED_MSVC","mscv140pro")

I have noticed that "findmsvccompiler()" still reports "msvc120express".

IMHO there is a bug in "dlwFindMsVcCompiler()", because "dlwIsVc14Pro()"
returns correctly %t.

Best regards,

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

[Scilab-users] Mysteries in the Realm of Overloading Catenation Operators (",", "; ") in Scilab 6.0

2017-03-13 Thread Dirk Reusch

Hello,

Using precompiled Scilab 6.0.0 Linux 64bit, exploring the announced
"ability to define user types in C++ modules" (cf. Scilab 6.0 - Release
Notes February 15th 2017) ... reveals the following:

Startup execution:
  loading initial environment

-->
exec('/home/dirk/Downloads/scilab-branch-6.0-1488991653/modules/ast/tests/unit_tests/newtype.tst',-1)

This is my type.

 %nt_p: This is my type.

--> [a;a]

Undefined operation for the given operands.
check or define function %nt_f_nt for overloading.

--> [a,a]

Undefined operation for the given operands.
check or define function %nt_c_nt for overloading.

--> // So far, it's Ok!, but trying to ..

--> [a,1]

inconsistent row/column dimensions

--> [a;1]

inconsistent row/column dimensions

--> // .. is IMHO not OK!

--> // Why does Scilab here *not* try to call "%nt_c_s", or "%nt_f_s" ?

So it seems IMHO, that the "ability to define user types in C++ modules"
is currently in a rather broken/incomplete state ... but, I am looking
forward to see things improving.

Thanks for any advice and further insight,

Dirk

PS: Tested also with nightly build  branch-6.0-1488991653 ... with the
very same mysteries!
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Logical Operations (&&, ||) with tlist, mlist, or UserType arguments badly crashes Scilab 6.0.0

2017-03-12 Thread Dirk Reusch

Hello Samuel,

Taking also into account my last post (cf. Mar 10, 2017; 3:34pm), one
may summarize as follows:

Scilab 6.0 crashes when using

1) "&&" or "||" with tlist, mlist, or UserTyper arguments

2) "~=" with UserType arguments

Do you think these issues/bugs issues will be fixed in the near future?

Thanks and best regards,

Dirk

On Sun, 12 Mar 2017 16:47:43 +0100
Samuel Gougeon  wrote:

> Hello Dirk,
> 
> Le 12/03/2017 à 15:24, Dirk Reusch a écrit :
> > Using precompiled Scilab 6.0.0 Linux 64bit, the following procedure
> > crashes Scilab silently ...
> >
> > Startup execution:
> >loading initial environment
> >
> > --> a=tlist("T")
> >   a  =
> > a(1)
> >   T
> >
> > --> a & a
> >
> > Undefined operation for the given operands.
> > check or define function %T_h_T for overloading.
> >
> > --> a && a
> >
> > ... SCILAB CRASHES !!!
> 
> Confirmed. It is clearly a bug, very similar to this one: 
> http://bugzilla.scilab.org/15008
> 
> By the way, we may be wondering about the overloading codes for &&
> and ||, that are not documented.
> If there are no specific codes and codes of & and | should be used,
> how would it be possible from the overloading function to distinguish 
> between a call to & from a call to &&?
> But this is another question, beyond the crash.
> 
> 
> ___
> 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] Logical Operations (&&, ||) with tlist, mlist, or UserType arguments badly crashes Scilab 6.0.0

2017-03-12 Thread Dirk Reusch

Using precompiled Scilab 6.0.0 Linux 64bit, the following procedure
crashes Scilab silently ...

Startup execution:
  loading initial environment

--> a=tlist("T")
 a  = 


   a(1)

 T



--> a & a

Undefined operation for the given operands.
check or define function %T_h_T for overloading.

--> a && a

... SCILAB CRASHES !!!


Please note, the very same  crash results occur, when using the "||"
operator, or mlist, or UserType arguments.

Thanks for any advice and further insight,

Dirk

PS: Tested also with nightly build  branch-6.0-1488991653 ... with the
very same crash results!
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

[Scilab-users] Not-Equal-Operation (<>, ~=) with UserType arguments badly crashes Scilab 6.0.0

2017-03-10 Thread Dirk Reusch

Hello,

Using precompiled Scilab 6.0.0 Linux 64bit, the following procedure
crashes Scilab silently ...

Startup execution:
  loading initial environment

-->
exec('/home/dirk/Downloads/scilab-6.0.0/modules/ast/tests/unit_tests/newtype.tst',-1)

This is my type.

 %nt_p: This is my type.

--> a==a

Undefined operation for the given operands.
check or define function %nt_o_nt for overloading.

--> a<>a

... SCILAB CRASHES !!!


Thanks for any advice and further insight,

Dirk

PS: Tested also with current nightly build ... with the very same crash
result!
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

[Scilab-users] Nightly builds of Scilab Branch 6.0 - 64 bits for GNU/Linux

2017-03-07 Thread Dirk Reusch

Hello,

Why are the nightly builds of Scilab Branch 6.0 - 64 bits for GNU/Linux
on scilab.org not up-to-date like for the other platforms?

Thanks,

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

[Scilab-users] Scilab 6.0 C++ API // Crashes due to function calls via overloading mechanism

2017-02-23 Thread Dirk Reusch

Hello,

Using the precompiled "scilab-branch-6.0-1487071837" under Linux 64bit,
I am experiencing crashes "Segmentation fault (core dumped)".

I am trying to use the new C++ API to implement operations like
addition for an user-defined type, lets say "T". 

To reproduce the crashes, I have stripped everything down to the
following minimal example:

1. Implementation of addition operation for Type "T" using C++ API:
---

types::Function::ReturnValue sci_T_a_T(types::typed_list &in, int
_iRetCount, types::typed_list &out) { try
{
return types::Function::OK_NoResult;
}
catch(std::exception& e)
{
return types::Function::Error;
}
return types::Function::OK_NoResult;
}

2. Compile "sci_T_a_T" and map it to "%T_a_T" Scilab function
-

3. Use "%T_a_T" directly => OK
--

A=tlist("T");
B=tlist("T");
%T_a_T(A,B) // OK

4. Use "%T_a_T" via overloading mechanism of "+" operator => Crash
--

A=tlist("T");
B=tlist("T");
A+B // => Crashes Scilab (Segmentation fault (core dumped))

--

So, it seems that using "try-catch" is a problem, when the function is
called via Scilab's overloading mechanism!?

What am I doing wrong, or is it a bug of Scilab?

Please note, that avoiding "try-catch" is not really an option for me,
because I have to use C++ functions from a library with error reporting
via exceptions.

Thanks for any advice and further insight,

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

Re: [Scilab-users] LINEAR SYSTEMS AND BODE PLOT IN SCILAB REPORT

2013-12-13 Thread Dirk Reusch

Hi Vijay,

the frequency unit in scilab's bode plot is [Hz] and not [rad/s]!

Regards,

Dirk

On Thu, 12 Dec 2013 20:04:25 -0600
Vijay Gopal  wrote:

> Hi,
> 
> I am a scilab user and I find it amazing about its capabilities.
> Recently I have encountered a problem for BODE PLOT for Linear
> Systems in continuous domain in scilab. I have made a report on it
> and attached herewith in pdf format. I hope this email will be
> beneficial for mutual progress. Also there are two files attached
> herewith Regards
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] Scilab 6 // Redefinement of permanent variable does not raise an error!?

[Scilab-users] Scilab 6 // Redefinement of permanent variable does not raise an error!?

Re: [Scilab-users] Modelling dynamic systems with real world data

Re: [Scilab-users] [Scilab-Dev] Scilab release frequency ?

[Scilab-users] Cell insertion operation using {...} is buggy?!

[Scilab-users] Building Scilab 6.0 with Visual Studio 2015?

Re: [Scilab-users] "findmsvccompiler" is buggy!?

[Scilab-users] "findmsvccompiler" is buggy!?

[Scilab-users] Mysteries in the Realm of Overloading Catenation Operators (",", "; ") in Scilab 6.0

Re: [Scilab-users] Logical Operations (&&, ||) with tlist, mlist, or UserType arguments badly crashes Scilab 6.0.0

[Scilab-users] Logical Operations (&&, ||) with tlist, mlist, or UserType arguments badly crashes Scilab 6.0.0

[Scilab-users] Not-Equal-Operation (<>, ~=) with UserType arguments badly crashes Scilab 6.0.0

[Scilab-users] Nightly builds of Scilab Branch 6.0 - 64 bits for GNU/Linux

[Scilab-users] Scilab 6.0 C++ API // Crashes due to function calls via overloading mechanism

Re: [Scilab-users] LINEAR SYSTEMS AND BODE PLOT IN SCILAB REPORT

15 matches

Site Navigation

Mail list logo

Footer information