bperp_$bdate.1.in and look_angle.1.in

247 views
Skip to first unread message

Mark Falkenberg

unread,
Nov 27, 2012, 2:23:24 PM11/27/12
to mai...@googlegroups.com
Dear MAINSAR group

I am currently processing a area in the north of denmark.
I have several focused slcs in CEOS format, all fairly coherent.

I have managed to google and read my way through most of the steps in the manual, but this one has me stumped.

Everything goes fine until I reach the first step in stamps. Using the recommended values in mt_prep (0.4 2 3 50 200) i get the following error when using the '>>stamps' command:

########################################
############ StaMPS Step 1 #############
########################################

PS_LOAD_INITIAL: Starting
Loading data into matlab...
SETPARM: heading = 197.801
SETPARM: lambda = 0.056565
SETPARM: slc_osf = 1
Rotating by -17.801 degrees

Error using reshape
To RESHAPE the number of elements must not change.

Error in ps_load_initial (line 226)
    la0=reshape(la0,50,50)';
 Error in stamps (line 118)
            ps_load_initial;

--------------------------------------------------------------------------------------------------------------------

I have found out the problem is the files 'look_angle.1.in' and 'bperp_$bdate.1'.in'.

When running mt_prep, the script mt_extract_info is run within. This is the script that generates 'look_angle.1.in' and 'bperp_$bdate.1'.in', in the following lines;


foreach ifg(`\ls $INSARDIR/*/cint.minrefdem.raw`)
    set ifgdir = `echo $ifg | gawk 'BEGIN {FS = "/cint.minrefdem.raw"}{print $1}'`
    set bdate = `echo $ifgdir | gawk 'BEGIN {FS = "/"}{print $(NF)}'`
    set blog = $ifgdir/step_coarse.log
    grep 'Bpar, Bperp' $blog | gawk '{print $6}' > bperp_$bdate.1.in
    set bperphead = `head -n1 bperp_$bdate.1.in`
    if ($bperphead == "") then
        echo "trying make_orbits.log instead..."
        set blog = $ifgdir/make_orbits.log
        grep 'Bpar, Bperp' $blog | gawk '{print $6}' > bperp_$bdate.1.in
        set bperphead = `head -n1 bperp_$bdate.1.in`
        if ($bperphead == "") then
            echo ""
            echo "ERROR: cannot find bperp info for $bdate"
            echo "$PRG terminated prematurely"
            exit 12
        else
            echo "success!"
            grep 'Look angle' $blog | gawk '{print $6}' > look_angle.1.in
        endif
    else
        grep 'Look angle' $blog | gawk '{print $6}' > look_angle.1.in
    endif
   
end


I dont know where the problem is, but during the make_orbits step there was created a file named 'step_orbit.log' not 'make_orbits.log' as in the  line;

        set blog = $ifgdir/make_orbits.log
        grep 'Bpar, Bperp' $blog | gawk '{print $6}' > bperp_$bdate.1.in

The thing is neither 'make_orbits.log' or 'step_orbit.log' nor 'step_coarse.log' has any information no 'Look angle', 'Bpar' or 'Bperp' .

the '.out' files do contain information on 'Look angle', 'Bpar' or 'Bperp' , but only the one value per variable. As these are not enough to make a 2x50x50 grid file I am at a loss as where to find these mystrious numbers.

In short I need to know how I get the data from the doris outfiles into 'look_angle.1.in' and 'bperp_$bdate.1'.in' ?

   -regards

            Mark Falkenberg




Qing Wan

unread,
Nov 13, 2013, 9:15:12 PM11/13/13
to mai...@googlegroups.com
I also got this problem when processing my data, looking for help ~

wq

Emily Montgomery-Brown

unread,
Jan 10, 2017, 2:56:21 PM1/10/17
to MAINSAR
Hi All,

I am getting a similar error (empty bperp.1.in) and I wonder if someone could tell me which step generates bperp.1.in?  I re-ran some DORIS steps on my CSK data, but I wonder if I may just need to delete my INSAR_date directory and start fresh.

Thanks,

Emily


########################################
############ StaMPS Step 1 #############
########################################
PS_LOAD_INITIAL: Starting
Loading data into matlab...
Error using load
Unknown text on line number 1 of ASCII file ../bperp.1.in
"//".

Error in ps_load_initial (line 75)
bperp=load(bperpname);

Error in stamps (line 141)
                ps_load_initial;


% "//" ... the two slashes are the only line in the bperp.1.in file

Adreas Saer

unread,
Mar 20, 2017, 9:51:39 AM3/20/17
to MAINSAR
Dear All,


I am facing the same issue. Bperp.txt contains to slashes //. Any suggestion on this?

Kind Regards,
Andreas
Reply all
Reply to author
Forward
0 new messages