comp.lang.idl-pvwave archive: archive » Re: TRIANGULATE/TRIGRID problem in IDL 5.3 (SGI)

Home » Public Forums » archive » Re: TRIANGULATE/TRIGRID problem in IDL 5.3 (SGI)

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: TRIANGULATE/TRIGRID problem in IDL 5.3 (SGI) [message #24783 is a reply to message #24782]

Fri, 20 April 2001 15:26

James Kuyper
Messages: 425
Registered: March 2000

Senior Member

"Liam E. Gumley" wrote:
...
> swath where I don't want triangles! However it also demonstrates that
> the triangles are created in a very consistent manner for the swath
> itself. The swath dimensions of 1354 x 10 are never going to change
> (yes, it is MODIS data), and I don't believe the connectivity list will
> ever change. So I can probably compute a triangle list manually just
> once (without using TRIANGULATE), and then use it for all cases in
> conjunction with TRIGRID. I'll send an update when I've implemented and
> tested this idea.

That will handle the normal case. However, if you need to be able to
handle data even when things go a little bit wrong, then for each scan
you should:

0) Check the "Geo scan quality" SDS; if the first column for a given
scan has a 1 in it, we got no useful information about how fast the
mirror was moving, making geolocation of that scan impossible.

1) Check the 'EV frames' value for that scan; it doesn't have to be 1354
- occasionally it's 0 due to a long data gap (> 0.5 seconds). Less
frequently, it's a number between 0 and 1354; this happens if a long
data gap starts or finishes during the Earth View segment of a scan.

2) Check the gflags SDS. There are things that can go wrong with
geolocation on a per-pixel basis; in the pixels where gflags is >=64,
either the line of sight could not be calculated, or it didn't intersect
the Earth; either way, the stored values are unusable fill values.

If you follow that advice, it's going to mess up your pre-computed
triangulation. On the other hand, less-than-perfect scans are rare
enough that most users can afford to simply discard them.

Report message to a moderator

[Message index]

		Re: TRIANGULATE/TRIGRID problem in IDL 5.3 (SGI) By: Ben Tupper on Sat, 21 April 2001 17:28
		Re: TRIANGULATE/TRIGRID problem in IDL 5.3 (SGI) By: Ben Tupper on Fri, 20 April 2001 15:44
		Re: TRIANGULATE/TRIGRID problem in IDL 5.3 (SGI) By: James Kuyper on Fri, 20 April 2001 15:26
		Re: TRIANGULATE/TRIGRID problem in IDL 5.3 (SGI) By: Liam E. Gumley on Fri, 20 April 2001 12:46
		Re: TRIANGULATE/TRIGRID problem in IDL 5.3 (SGI) By: James Kuyper on Fri, 20 April 2001 08:04
		Re: TRIANGULATE/TRIGRID problem in IDL 5.3 (SGI) By: Ben Tupper on Thu, 19 April 2001 19:08
		Re: TRIANGULATE/TRIGRID problem in IDL 5.3 (SGI) By: Kenneth P. Bowman on Thu, 19 April 2001 17:16
		Re: TRIANGULATE/TRIGRID problem in IDL 5.3 (SGI) By: Craig Markwardt on Thu, 19 April 2001 13:12

Previous Topic:	fastest operations/fctns.
Next Topic:	MPFIT update (and bug notice)

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 15:55:22 PDT 2025

Total time taken to generate the page: 0.00224 seconds