Problem -- 0 datapoints (t,x,y,z) read from: "master.res"

[JY]

Hi Andy,

I'm now processing ERS2 raw data with StaMPS.

In the step "step_master_orbit", I encountered an error stating - 0
datapoints (t,x,y,z) read from: "master.res". This seems to imply a
problem in precise orbit. And indeed, there's no datapoint in
master.res.

I couldn't figure out where the problem is, but I'll put down some
observations here, and hope you can help me troubleshoot this:

1. during "step_slc_ers", StaMPS did not complained about precise
orbit; however it had several echo-ed sentences caught my eyes:
+roi_prep.pl setting roi default
+roi_prep.pl Reading resource file: 19991113.raw.rsc
Keyword RANGE_OFFSET doesn't exist in 19991113.raw.rsc,
returning 0
Keyword SL_AZIMUT_RESOL doesn't exist in
19991113.raw.rsc, returning 0
Is this normal?

2. At the end of "step_slc_ers" and "make_slcs_ers", there's an error
message:

+roi.pl /usr/radar/ROI_PAC_3_0/ROI_PAC/INT_SCR/
length.pl 19991113.slc
date: illegal option -- -
usage: date [-jnu] [-d dst] [-r seconds] [-t west] [-
v[+|-]val[ymwdHMS]] ...
[-f fmt date | [[[mm]dd]HH]MM[[cc]yy][.ss]]
[+format]
Would this affect anything?

Any thought?

Thanks a lot

JY

[Andy Hooper]

Hi Jiun-Yee

On Thu, Jun 5, 2008 at 3:51 PM, JY <jyyens...@gmail.com> wrote:
>
> Hi Andy,
>
> I'm now processing ERS2 raw data with StaMPS.
>
> In the step "step_master_orbit", I encountered an error stating - 0
> datapoints (t,x,y,z) read from: "master.res". This seems to imply a
> problem in precise orbit. And indeed, there's no datapoint in
> master.res.
>
> I couldn't figure out where the problem is, but I'll put down some
> observations here, and hope you can help me troubleshoot this:
>
> 1. during "step_slc_ers", StaMPS did not complained about precise
> orbit; however it had several echo-ed sentences caught my eyes:
> +roi_prep.pl setting roi default
> +roi_prep.pl Reading resource file: 19991113.raw.rsc
> Keyword RANGE_OFFSET doesn't exist in 19991113.raw.rsc,
> returning 0
> Keyword SL_AZIMUT_RESOL doesn't exist in
> 19991113.raw.rsc, returning 0
> Is this normal?

Yes, this is normal.

>
> 2. At the end of "step_slc_ers" and "make_slcs_ers", there's an error
> message:
>
> +roi.pl /usr/radar/ROI_PAC_3_0/ROI_PAC/INT_SCR/
> length.pl 19991113.slc
> date: illegal option -- -
> usage: date [-jnu] [-d dst] [-r seconds] [-t west] [-
> v[+|-]val[ymwdHMS]] ...
> [-f fmt date | [[[mm]dd]HH]MM[[cc]yy][.ss]]
> [+format]
> Would this affect anything?

Yes, this will cause a problem. The script roipac2doris uses the
utility program 'date' to do a date conversion. Your version of 'date'
doesn't recognize the option '--' followed by the date to convert. Can
you find a version that does?

Cheers.
Andy

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Andy Hooper
Nordic Volcanological Center
Institute of Earth Sciences
University of Iceland
Sturlugata 7, 101 Reykjavik
(+354) 525-4490
(+354) 562-9767 (fax)
http://www.hi.is/~ahooper
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[JY]

Hi Andy,

I checked out 'fink', it doesn't have this. I was poking around in
sourceforge but couldn't find anything useful. Keyword 'date' is just
too common a word! I'll keep looking around for that.

I guess in the long run, I'll have to move it to Linux!

cheers,

Jiun-Yee

[Piyush Agram]

Try and obtain coreutils 5.2.1 with the right date utility. This can
handle dates of format "yyyymmdd 0:0:sssss".
The new linux versions seem to have date 5.9x by defaults and the
above format is no longer supported.

Piyush

[Piyush Agram]

Delete the following lines of roipac2doris:
"set UTC1=...."
"set AZIT1_DS=....."


Insert the following after the line "set AZIT1_WS = ...." in
roipac2doris

set AZIHH = `expr $AZIT1_WS / 3600`
set AZIMM = `expr $AZIT1_WS % 3600`
set AZIMM = `expr $AZIMM / 60`
set AZISS = `expr $AZIMM % 60`
set AZIT1_DS = `echo "$AZIT1 +$AZISS -$AZIT1_WS" | bc -l`
set UTCtemp = `date --date="$YEAR$MONTH$DAY" +"%d-%b-%Y"`
set UTC1 = $UTCtemp" "$AZIHH":"$AZIMM":"$AZIT1_DS

by the set of commands shown above. That should take care of the
problem with the new "date" command versions.

Piyush

[Piyush Agram]

set AZIHH = `expr $AZIT1_WS / 3600`
set AZIMM = `expr $AZIT1_WS % 3600`

set AZISS = `expr $AZIMM % 60`
set AZIMM = `expr $AZIMM / 60`
set AZIT1_DS = `echo "$AZIT1 +$AZISS -$AZIT1_WS" | bc -l`
set UTCtemp = `date --date="$YEAR$MONTH$DAY" +"%d-%b-%Y"`
set UTC1 = $UTCtemp" "$AZIHH":"$AZIMM":"$AZIT1_DS

Oops.. this would be the correct sequence. Error in copy pasting.

Piyush

[JY]

Hi Piyush,

Thanks for posting this! I'll be trying this out as soon as I get
some time later this week.

I checked the original script, it seems the original script contain
the variable 'UTC1' already. Should I comment out that line (line 208
in the original script), or should I just paste your fix into the
original script? Also, should I concern about where in the script I
should paste this into?

cheers,

Jiun-Yee

[JY]

Hi Piyush,

It doesn't seem to work. 'date' utility in Mac seems to be very
different than the one in Linux! Can it use '-d' instead of '--
date=......'?

JY

[Piyush Agram]

Hi JY,
date -d should work. Just run a "man date" in your command prompt
to ensure. In my fix, we only work with the date using the command.
So, no hours,mins or secs information needs to be provided.

Also, comment out the original UTC1 line.

Piyush

[JY]

Hi Piyush,

I was just going to reply to you and this thread that I finally had
this problem solved. (I haven't really process the entire PS yet,
but forming SLC seems to be fine!)

Main thing I had to do was get the gnu version of "date" utility. I
posted a question about this and <http://www.macresearch.org/date-
command-leopard-alternative>, and somebody reply and said that I
should install "coreutils" in Mac OS X using Macports or Fink; this
solve the problem about "date" utility.

2nd is to modify the script to your version as you previously
mentioned (and I forgot to comment out UTC1 line the 1st time).

After that, it seems to work fine.

Thanks!

JY