Re: problem with output of the program on different OS

On May 9, 3:11=A0pm, pereges <Brol...@[EMAIL PROTECTED]
> wrote:
> On May 9, 6:46 pm, Bart <b...@[EMAIL PROTECTED]
> wrote:
>
> > On May 9, 2:33 pm, pereges <Brol...@[EMAIL PROTECTED]
> wrote:
> > Didn't like this. I used reader(&obj); (reader takes **object).
>
> I'm sorry, you are correct.
>
> > OK, but what should the output be?
>
> > With inputs of 40000000, 0.0001 and 1100, I got:
>
> > Es: 2.979907e-012 Ei: inf RCS: 0.000000e+000
>
> > But then, I'm running on Windows and you say the problem is with
> > Linux..
>
> I will have to check up some scientific literature to determine what
> the *exact* =A0and expected output should be. But I can definetely tell
> something is wrong because I'm getting the following output on windows
> for the same input that you have taken:
>
> Es: 4.431255e-10 Ei: 1.226668e-04 RCS: 4.539517e+01
>
> There is definetely something wrong and its quite likely that these
> are all garbage values

Something went amiss with my last post -- it'll turn up half-finished
soon.

Anyway in find_closest_intersection(), index is  not set and makes
res.tindex have funny values in raytrace(), causing array bounds
overflow. But setting this to 0 just gave more errors a bit later on.
Whether this is relevant to your main problem, I don't know, but it
should be fixed.

Hope this helps.

--
Bartc