|
|
| Re: Use IDLanROI or not [message #84413 is a reply to message #84412] |
Mon, 03 June 2013 07:27  |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Fabien writes:
> Anyways, I would also suggest to use it but be careful. The output
> depends on what you define as grid and grid points. I use mostly
> atmospheric model data where grid coordinates are located in the center
> of the pixels, while in imagery it is often at the corner. Every time I
> start to think about this again I have to redo the tests by myself to
> remember which point of view IDLanROI uses ;-)
And then, of course, whether the origin is in the lower-left or upper-
left and... Oh, my head is hurting again!
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thue. ("Perhaps thou speakest truth.")
|
|
|
|
| Re: Use IDLanROI or not [message #84415 is a reply to message #84413] |
Mon, 03 June 2013 07:22 |
Fabzi
Messages: 305
Registered: July 2010
|
Senior Member |
|
|
On 06/03/2013 04:03 PM, David Fanning wrote:
> I wasn't aware of a bug in it (yikes!).
The bug was in IDLanROIgroup, I had to send a bugfix to ExcelisVIS:
http://comp.lang.idl-pvwave.narkive.com/qftQBzrg/crashing-ro i-s
I like IDLanROI's but I wish the ->ContainsPoints method to be faster.
It is so slow in comparison to ->ComputeMask !!!
Anyways, I would also suggest to use it but be careful. The output
depends on what you define as grid and grid points. I use mostly
atmospheric model data where grid coordinates are located in the center
of the pixels, while in imagery it is often at the corner. Every time I
start to think about this again I have to redo the tests by myself to
remember which point of view IDLanROI uses ;-)
Cheers,
Fab
|
|
|
|
| Re: Use IDLanROI or not [message #84416 is a reply to message #84415] |
Mon, 03 June 2013 07:19 |
Helder Marchetto
Messages: 520
Registered: November 2011
|
Senior Member |
|
|
On Monday, June 3, 2013 4:03:31 PM UTC+2, David Fanning wrote:
> Helder writes:
>
>
>
>> I'm confronted with a philosophical question that has probably been answered in this group already, but I wanted to check on it again.
>
>> I have my own piece of software that shows images, manages the scaling, the cross-sections and integration over stacks.
>
>> To analyze my images I have been defining my own ROIs as squares/rectangles, circles, hexagons and free hand via xROI. Now in xROI I store the objects IDLanROI, whereas for the other types I use my own structures.
>
>
>
> I typically use IDLanROI objects for all kinds of ROIs. I wasn't aware
>
> of a bug in it (yikes!). I'm for anything that makes code easier to read
>
> and use. :-)
>
>
>
> Cheers,
>
>
>
> David
>
>
>
>
>
>
>
> --
>
> David Fanning, Ph.D.
>
> Fanning Software Consulting, Inc.
>
> Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
>
> Sepore ma de ni thue. ("Perhaps thou speakest truth.")
Hi David,
thanks. I was referring to this post: https://groups.google.com/d/msg/comp.lang.idl-pvwave/QoaALkX GMPQ/PQdEO_aSn5MJ
It seems to be solved. What I'm worried about are memory leaks or the similar. But if you use them, they must be good, otherwise there would be an object called cgIDLanROI :-)
Cheers,
Helder
|
|
|
|
| Re: Use IDLanROI or not [message #84417 is a reply to message #84416] |
Mon, 03 June 2013 07:03 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Helder writes:
> I'm confronted with a philosophical question that has probably been answered in this group already, but I wanted to check on it again.
> I have my own piece of software that shows images, manages the scaling, the cross-sections and integration over stacks.
> To analyze my images I have been defining my own ROIs as squares/rectangles, circles, hexagons and free hand via xROI. Now in xROI I store the objects IDLanROI, whereas for the other types I use my own structures.
I typically use IDLanROI objects for all kinds of ROIs. I wasn't aware
of a bug in it (yikes!). I'm for anything that makes code easier to read
and use. :-)
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.idlcoyote.com/
Sepore ma de ni thue. ("Perhaps thou speakest truth.")
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
