[ferret_users] quicker detection of dimensions improperly specified

To: ferret_users@xxxxxxxx
Subject: [ferret_users] quicker detection of dimensions improperly specified
From: Ryo Furue <furue@xxxxxxxxxx>
Date: Tue, 16 Oct 2012 10:55:31 -1000 (HST)
List-archive: <http://groups.google.com/a/noaa.gov/group/ferret_users/?hl=en_US>
List-help: <http://support.google.com/a/noaa.gov/bin/topic.py?hl=en_US&topic=25838>, <mailto:ferret_users+help@noaa.gov>
List-id: <ferret_users.noaa.gov>
List-post: <http://groups.google.com/a/noaa.gov/group/ferret_users/post?hl=en_US>, <mailto:ferret_users@noaa.gov>
List-unsubscribe: <http://groups.google.com/a/noaa.gov/group/ferret_users/subscribe?hl=en_US>, <mailto:googlegroups-manage+809428289204+unsubscribe@googlegroups.com>
Mailing-list: list ferret_users@xxxxxxxx; contact ferret_users+owners@xxxxxxxx
Sender: owner-ferret_users@xxxxxxxx

Ferret users and developers,

I'm wondering if it's possible to detect an improper dimension
specification, such as

  yes? fill  some_3D_variable

UP FRONT . . .  It sometimes takes quite a bit of time before we
see the error message

  **ERROR: dimensions improperly specified: must be a 2D region

especially when the dataset is accessed across the network.

I make this mistake very often and then hit Ctrl-C frantically,
which it still takes Ferret quite a bit of time to respond to.

Regards,
Ryo

Follow-Ups:
- Re: [ferret_users] quicker detection of dimensions improperly specified
  - From: Ansley Manke
- Re: [ferret_users] quicker detection of dimensions improperly specified
  - From: Hein Zelle

Previous by thread: [ferret_users] Calculate Transport between points not lying on a latitude or longitude
Next by thread: Re: [ferret_users] quicker detection of dimensions improperly specified

[Thread Prev][Thread Next][Index] Contact Us

Dept of Commerce / NOAA / OAR / PMEL / Ferret