NOTE: The decoders
mailing list is no longer active. The list archives are made available for historical reasons.
============================================================================== Robb Kambic Unidata Program Center Software Engineer III Univ. Corp for Atmospheric Research rkambic@xxxxxxxxxxxxxxxx WWW: http://www.unidata.ucar.edu/ ============================================================================== ---------- Forwarded message ---------- Date: Sat, 26 Jun 2004 09:02:20 -0400 From: Philip Bogden <bogden@xxxxxxxxxxxx> To: Robb Kambic <rkambic@xxxxxxxxxxxxxxxx>, Russ Rew <russ@xxxxxxxxxxxxxxxx>, Philip Bogden <bogden@xxxxxxxxxxxx>, Jason Thaxter <thaxter@xxxxxxxxxx>, Jo Hansen <jhansen@xxxxxxxx> Eric Bridger <eric@xxxxxxxxxx> Subject: RE: NetCDF library problems (fwd) Gee, thanks for responding so quickly to this...you seem to be well aware of the problem. We'll be happy to work with you to help where we can. Thanks again! Philip -------------- Dr. Philip Bogden, CEO GoMOOS, PO Box 4919, Portland, ME 04112-4919 Office Location: 1 Canal Plaza, 7th Floor Office: 207-773-0423 bogden@xxxxxxxxxx Mobile: 207-632-3308 Fax: 207-773-8672 -------------- www.gomoos.org -------------- -----Original Message----- From: Robb Kambic [mailto:rkambic@xxxxxxxxxxxxxxxx] Sent: Friday, June 25, 2004 11:48 AM To: Russ Rew; Philip Bogden; Jason Thaxter; Jo Hansen Subject: Re: NetCDF library problems (fwd) On Fri, 25 Jun 2004, Russ Rew wrote:
Robb, Do you know anything about the problem described in this email with the Perl netCDF interface not working with Perl 5.8? Have you come up with some sort of workaround for this problem to use with your perl decoders?
Russ, et al. Yes, there is a bug in perl 5.8.0 that doesn't have any work around. The decoders appear to be working ok then usual behavior happens and no recovery is possible. Currently, the decoders are being tested on perl 5.8.4 on a Linux box. The decoders have run w/o problems for a couple of days but sometimes it takes as much as 4 days before the problems appear. The solution is to upgrade to perl 5.8.4 More comments below.
--Russ ------- Forwarded Message Date: Fri, 25 Jun 2004 07:18:21 -0600 From: Jo Hansen <jhansen@xxxxxxxxxxxxxxxx> To: Russ Rew <russ@xxxxxxxxxxxxxxxx> Subject: FW: NetCDF libary problems (fwd) see below Date: Fri, 25 Jun 2004 06:04:17 -0400 From: Philip Bogden <bogden@xxxxxxxxxxxx> To: Jo Hansen <jhansen@xxxxxxxx> Subject: FW: NetCDF libary problems Hi Jo, Can you advise me on the right person at Unidata to contact about the problem my guys are having with a NetCDF interface, please? They seem not to be getting adequate response through the mail lists. Thanks, Philip -------------- Dr. Philip Bogden, CEO GoMOOS, PO Box 4919, Portland, ME 04112-4919 Office Location: 1 Canal Plaza, 7th Floor Office: 207-773-0423 bogden@xxxxxxxxxx Mobile: 207-632-3308 Fax: 207-773-8672 -------------- www.gomoos.org -------------- -----Original Message----- From: Jason Thaxter [mailto:thaxter@xxxxxxxxxx] Sent: Wednesday, June 16, 2004 2:51 PM To: Philip Bogden Subject: NetCDF libary problems Here's a quick summary of the NetCDF problems with the Perl interface: 1) The current version has a bug that we really need fixed: for NetCDF variables which are arrays of bytes, it only gets the first element of the array. Our doppler quality fields are stored this way. I can verify this problem.
There is either a bug in netcdf-perl or in the your routine calling netcdf-perl. It would help if I could look at your code with some sample data to test.
2) The updated NetCDF perl does NOT compile on our system. Or many others.
What systems: boxes/os's
3) The guy who would fix this says he's overcommitted and that this is a
low
priority (as in "this is not going to be fixed anytime soon"):
http://my.unidata.ucar.edu/content/support/help/MailArchives/netcdf-perl/msg 00120.html
4) The PDL (Perl Data Language) NetCDF interface does correctly handle
byte
variables. I've tested all of this on a couple test NetCDFs Linda made for me.
Are you saying, byte vars are handled correctly but array of bytes are not? Robb...
The maintainer, Steve Emmerson, has basically said "If you want to fix it, you volunteer to be the maintainer for this package". I don't know what's the best way to approach this, but obviously there are more options than I realized.... Let me know what you/I/we can/should do. I'll take any solution, as long as it's soon. Jason -- ---------------------------------------------- Jason Thaxter GoMOOS, P.O. Box 4919, Portland, ME 04112-4919 Office Location: 1 Canal Plaza, 7th Floor Office: 207.773.0423 Fax: 207.773.8672 Email: thaxter@xxxxxxxxxx ------------www.gomoos.org-------------------- ------- End of Forwarded Message
=========================================================================== == Robb Kambic Unidata Program Center Software Engineer III Univ. Corp for Atmospheric Research rkambic@xxxxxxxxxxxxxxxx WWW: http://www.unidata.ucar.edu/ =========================================================================== ==
decoders
archives: