Memory Full : stopped at Initialize array

[RavensFan]

---

Nghtcrwlr wrote:

 I attach an exapmle image also...336X362

---

That explains it.   336 as an I16 becomes -18176 when squared.  362 becomes -28.  Add them together you get. -18204.  Take the square root of that you get NaN.  Intialize the array with the size of NaN you get a memory error.

Convert your values to a datatype that can hold larger numbers.  A U32 should work.

[Nghtcrwlr]

yeah.. i used a U8 conversion and it wrkd...

thanksss

[RavensFan]

---

Nghtcrwlr wrote:

yeah.. i used a U8 conversion and it wrkd...

thanksss

---

Are you sure it worked?

A U8 will make sure you don't have negative numbers, but it only goes up to 255.  There is no way you can have it hold the square of 336.  It won't even hold 336 itself.

[Nghtcrwlr]

I am using binary images.. so only values between o and 255 is taken...

[altenbach]

---

Nghtcrwlr wrote:
I am using binary images.. so only values between o and 255 is taken...

---

We are not talking about array values, but array dimensions. Big difference. 😉

[Coq_Rouge]

---

Nghtcrwlr wrote:
I am using binary images.. so only values between o and 255 is taken...

---

This is wrong. Your image is organized as a bunch of U8 data. But this does not mean that the size of the picture is limited to 256 bytes. I quote from one of your previous post  "

 I attach an exapmle image also...336X362" As I write this I am very happy for the fact that my screen size is not limited to 256X256 pixels. I think you should go through your data once more

Ps Ravens Fan idea is not insane 😉

[Coq_Rouge]

I also think this is the correct time time to quote my self

---

t06afre wrote: 
 If you keep it between us. Long time ago then I was new to Labview. Debugging was the last thing I learned to master. I trusted my own skills better, so debugging was not a topic

---