Re: Is there a command which could tell a CDF file is good or not? [message #66127] |
Mon, 20 April 2009 02:21 |
R.Bauer
Messages: 1424 Registered: November 1998
|
Senior Member |
|
|
litongmu@gmail.com schrieb:
> Hi all,
>
> I am trying to run a code to deal with 1200 CDF files. However, some
> of them are not good files. When I use certain CDF commands to open or
> read them. IDL will return a error message and stop running. Now the
> problem is I have so many files. And I do not know which are good,
> which are bad. They all look the same size. But I can only tell when
> the code stop running. Therefore, I have to rerun the code again after
> deleting the bad file it picked out. So is there any command in IDL
> which could tell whether a CDF file is good or not. The important
> feature is that it can return results based on the judge. And it will
> not stop a program from running.
> Thanks in advance.
>
> Sincerely
can you share one of the "broken" files.
We have had some trouble in the past by a broken hard disk. Only small
sections of the netCDF file were corrupted.
cheers
Reimar
|
|
|
Re: Is there a command which could tell a CDF file is good or not? [message #66130 is a reply to message #66127] |
Sun, 19 April 2009 14:49  |
David Fanning
Messages: 11724 Registered: August 2001
|
Senior Member |
|
|
litongmu@gmail.com writes:
> I am trying to run a code to deal with 1200 CDF files. However, some
> of them are not good files. When I use certain CDF commands to open or
> read them. IDL will return a error message and stop running. Now the
> problem is I have so many files. And I do not know which are good,
> which are bad. They all look the same size. But I can only tell when
> the code stop running. Therefore, I have to rerun the code again after
> deleting the bad file it picked out. So is there any command in IDL
> which could tell whether a CDF file is good or not. The important
> feature is that it can return results based on the judge. And it will
> not stop a program from running.
This is a general, and annoying, problem with all the IDL
scientific data formats. See, for example, this article:
http://www.dfanning.com/fileio_tips/nohdf.html
It appears to have to do with the underlying C libraries
that have been incorporated into IDL. But you are not the
only one who has run into exactly this problem.
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
|
|
|