Calculation issue with octave (data unexpectedly go to zero at some point)

[rchretien]

Hi everybody,

I contact you because of my poor knowledge of octave. For my master thesis,
I have to use Octave installed on a remote cluster whilst I am running
matlab at home. For the same code, matlab and octave do not produce the same
results. Or rather, should I precise, they produce the same results during a
certain amount of time, until octave produces an unexpected collapse of the
data to zero.

Here is an example of what happens :

http://hpics.li/3e16497

Under matlab (I repeat that I have used the same version of the code), the
output is basically the same, except for abscissae greater than ~975 (i.e.
the abscissa from where octave collapses) where no crash is observed
(contrarily to what can be seen here above). Roughly speaking, the code
behaves as expected when run under matlab and not when run under octave. 

My question is, since this is manifestedly not a coding problem (in which
case, the output from matlab would also collapse), is this problem linked to
an option, or some kind of precision, or to a version problem, in octave ?
Has this problem already been observed ? If so, how can I fix it ?

I’m looking forward to reading your opinions and suggestions,

Renaud



--
View this message in context: 
http://octave.1599824.n4.nabble.com/Calculation-issue-with-octave-data-unexpectedly-go-to-zero-at-some-point-tp4662177.html
Sent from the Octave - General mailing list archive at Nabble.com.