[Carpet] changing the warning level for errors with HDF5 files

[Thomas Radke]

Thomas Radke wrote:
> Erik Schnetter wrote:
> 
>> On Mar 20, 2007, at 09:32:01, Bruno Giacomazzo wrote:
>>
>>> Hi,
>>>      in one of my last run with Carpet (3rd stable version) and the
>>> development version of Cactus, my job had problems writing the  
>>> checkpoint
>>> files and was returning the errors you can find at the end of this  
>>> email.
>>>
>>>      The problem is that it gave only a warning level 1 error and then
>>> went on. This happened several times and so at the end the job did not
>>> save any checkpoint files (the checkpoints were saved on the  scratch 
>>> area
>>> of the nodes and it seems that some of them had some problem).
>>>
>>>      Is it possible to have a parameter that can change to Warning
>>> level 0 the messages related with this kind of problems? Should  this be
>>> the default value?
>>
>>
>>
>> A level 0 warning would have aborted the job, still leaving no  
>> checkpoint files.  Sometimes the error is intermittent and goes away  
>> later, so that continuing would actually have produced checkpoint  
>> files.  At the moment you spent your own time and computing time  
>> unnecessarily.
>>
>> I think we can introduce a parameter.  Thomas, what do you think?
> 
> 
> Sure, if users want this, no problem. It's easy enough to implement. I 
> suggest a boolean parameter IO::abort_on_io_errors (any suggestions for 
> a better name?) in thorn CactusBase/IOUtil which then can be used by any 
> other I/O thorn.

I have just added the above parameter to thorn CactusBase/IOUtil and 
implemented its checking in the darcs development version of thorn 
Carpet/CarpetIOHDF5.

-- 
Cheers, Thomas.