(Sent previously just to Samuel by mistake)
drawlater();
gfig = gcf ();
drawnow();
Sent from my Verizon 4G LTE smartphone
Original message
From: Samuel Gougeon
Date: 10/6/16 2:13 PM (GMT-08:00)
To: t...@wescottdesign.com, Users mailing list for Scilab
Subject:
Le 06/10/2016 21:57, Tim Wescott a écrit :
So, I have some code that works all right, it works all right but not
exactly quite*:
errbar(time(ixg) / sampleRate, ..
demodulator.eqData.idealPulse(ix), pv, pv);
gfig.children(1).children(1).clip_state = 'on';
gfig.chi
So, I have some code that works all right, it works all right but not
exactly quite*:
errbar(time(ixg) / sampleRate, ..
demodulator.eqData.idealPulse(ix), pv, pv);
gfig.children(1).children(1).clip_state = 'on';
gfig.children(1).children(1).segs_color = 4;
This has wo
*Edit in #3*
Am 06.10.2016 18:20, schrieb Jens Simon Strom:
Hallo Frieder,
You ask many questions in one post.
1: You just divide the (numerical) time interval into an adequate
number of points (which can be neatly accommodated) with linspace or
':' and plot the corresponding time text colum
For that matter, you can pass a vector of infemums and supremums for
each element of the vector you're optimizing. (and +inf and -inf work,
for things that don't matter). As long as you can optimize within a
rectilinear space then you can easily dodge the "bad" values. It's in
the help for optim
Le 06/10/2016 12:31, paul.carr...@free.fr a écrit :
thanks for the advice
well I tried but it does not work as expected ; errcatch seems to be
obsolete so I'm testing it with execstr: the warning is not displayed
... why
Try / catch / end was very buggy in Scilab 5.
Scilab 6 efficiently
Hallo Frieder,
You ask many questions in one post.
1: You just divide the (numerical) time interval into an adequate
number of points (which can be neatly accommodated) with linspace or ':'
and plot the corresponding time text colums via a for-loop. There is no
need that 'text times' coincid
Hello Clément,
yes. I do translate:
danke schön. Die Testmatrix ist Unsinn. Somit weiß ich nun, dass der
Fehler im Programm nicht an ´dieser Passage liegt, sondern bereits
davor
Auftritt.
Thank you. I had a mistake in the random Matrix. It's now clear, that
my mistake isn't in this code, b
Hallo Frieder,
Most of this ML readers / writers are not german speaker, could you please use
english next time ?
Thanks,
--
Clément
Le jeudi 06 octobre 2016 à 15:18 +0200, Frieder Nikolaisen a écrit :
> Hallo Jens,
>
> danke schön. Die Testmatrix ist Unsinn. Somit weiß ich nun, dass der
> F
Hallo Jens,
danke schön. Die Testmatrix ist Unsinn. Somit weiß ich nun, dass der
Fehler im Programm nicht an ´dieser Passage liegt, sondern bereits davor
Auftritt.
Viele Grüße
Frieder
Am 06.10.2016 11:45, schrieb Jens Simon Strom:
Hallo Frieder,
insert the line
disp(''
Hello,
to Jens: ich habe Fortschritte gemacht, bin dennoch nicht zum Ergebnis
gekommen.
I will write about the problem, in English:
1. Attached are two plots. The 16 line plot shows the Dates. But even
with just 16 lines, it's not easy to read, as there are to many Dates
ploted. How can I r
thanks everybody for the supports
Paul
- Mail original -
De: "Mike Page"
À: "Users mailing list for Scilab"
Envoyé: Jeudi 6 Octobre 2016 12:34:59
Objet: Re: [Scilab-users] Scilab control after an impossible calculation
Hi Paul,
Would Scilab's try-catch block do what you
If you use optim you can set the ind retured arg to -1 in the cost
function to say that the function cannot be evaluated at this point.
Serge
Le 06/10/2016 à 10:51, paul.carr...@free.fr a écrit :
Hi All
I’m using Scilab as the interface between my optimizer and my finite
element solver(s)
Hi Paul,
Here are a couple of things you can do:
- as already mentioned, try/catch structures can be used to handle problems
instead of crashing.
- can't you bullet-proof your code? I mean check x!=0 if you have 1/x somewhere
in your code.
- just change your parametrization to use y=1/x as a p
Hi Paul,
Would Scilab's try-catch block do what you want? For example:
for i=1:10;
try;
disp(1/(i-5));
catch;
disp("err");
end;
end
won't crash when it gets to the divide by zero.
This is the more structured way, but you can use execstr with errcatch to
do the same thing.
thanks for the information and the link
Paul
- Mail original -
De: "Dang Ngoc Chan, Christophe"
À: "Users mailing list for Scilab"
Envoyé: Jeudi 6 Octobre 2016 10:26:50
Objet: [Scilab-users] Peaks and valleys [was: Forum dedicated to Scilab
developments -> practical concern]
H
thanks for the advice
well I tried but it does not work as expected ; errcatch seems to be obsolete
so I'm testing it with execstr: the warning is not displayed ... why
###
mode(0)
try
x = 0;
y = (1/x)
if execstr(('y','errcatch') <> 0) t
Hi Paul,
Thanks for sharing the interesting code & link.
Please note that for noisy data you may still be able to use your
peaks-and-valleys code by filtering the input data beforehand.
Depending on the type of noise, Scilab offers different solutions:
- Low-Pass filters: if the noise is mainly
Hello,
> De : paul.carr...@free.fr
> Envoyé : mercredi 5 octobre 2016 21:56
>
> In attachment is typically a project I'm working on :
> determination of peaks and valley on a noisy signal;
> Trying to avoid reinventing the wheel,
> I had a look on information's and algorithms on internet
> n
Try errcatch().
Am 06.10.2016 10:51, schrieb paul.carr...@free.fr:
Hi All
I'm using Scilab as the interface between my optimizer and my finite
element solver(s) and sometimes Scilab stops because of unexpected and
Hallo Frieder,
insert the line
disp(''), c=c,sizeA=size(A)
before the problem line
if A(c-1,3)==0 then
and you will see what happens there.
Regards
Jens
---
Am 06.10.2016 08:29, schrieb Frieder Nikolaisen:
With the real Code, it's more
Hi All
I’m using Scilab as the interface between my optimizer and my finite element
solver(s) and sometimes Scilab stops because of unexpected and impossible
calculus (1/x with x = 0 as an example ); obviously Scilab stops (and so the
optimization).
I’m wondering if it’s possible:
- To ask
22 matches
Mail list logo
