radsstat produces "Error loading variable" for e1 and e2

[GoogleCodeExporter]

radsstat produces "Error loading variable" for e1 and e2

[GoogleCodeExporter]

This is actually quite normal, but could be fixed. Feedback requested.

This issue is as follows:
Both ERS-1 and ERS-2 use alt_reaper as the default orbit. However, the orbit is 
not available on a number of days. As a result, RADS4 reports that "alt" is not 
available.

This can be circumvented by defaulting back to the age-old DGM-E04 orbits. And 
for ERS-2 to the GFZ orbits after the DGM-E04 processing was stopped.
This may not be what we want to do, since that would mix orbit types. Though 
"some orbit" is better than none.

Original comment by [email protected] on 15 Jun 2012 at 4:14

• Changed state: Accepted

[GoogleCodeExporter]

I'd suggest either adding a -q/--quiet flag to suppress the errors or only send 
them to stderr when -v has been called.

Original comment by [email protected] on 15 Jun 2012 at 3:43

[GoogleCodeExporter]

I don't think it's good to use -q too liberally, though worthwhile to add (and 
I will).
But instead, I think it is better to have a
<default>nan</default>
on those orbit descriptions. That will quietly set them to NaN. 

Original comment by [email protected] on 15 Jun 2012 at 3:55

[GoogleCodeExporter]

Using <default>nan</default> works for me.

Original comment by [email protected] on 15 Jun 2012 at 3:56

[GoogleCodeExporter]

I meant to say, <backup>nan</backup>, of course. Added in r148.
Options -q|--quiet added in r149. Suppresses warnings, not fatal errors.

Original comment by [email protected] on 15 Jun 2012 at 4:23

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by [email protected] on 15 Jun 2012 at 4:33

• Changed state: Verified