Create IFGs - step 0 (readfiles:)
Selena_Ge
I have processed my raw data in ROIPAC. Now I have slc data.
I tried to run master_orbit_ERS1.dorisin (followed by instruction,
step Create IFGs (using DORIS))
but I received next -
ERROR : [ioroutines.cc[1329]]: Requested step: 3 (precise_orbits:)
seems impossible, because step 0 (readfiles:) is not in resultfile.
Have I create *.res files manualy or how can I decied this problem ?
Best regards,
Elena
Karsten
First off, I do not recognize the command master_orbit_ERS1.dorisin.
As far as I can look back (v3.1), the first step in the create IFG's
section is step_master_orbit_ODR. Are you using the newest version
(v3.2)?
In any case, the error you are getting is a Doris error, it is
basically telling you it is missing some data in the master result
file from step 0, which is the readfiles step. This step is skipped by
StaMPS, and the result file necessary for Doris is created by
roipac2doris, which happens to be the command missing above.
roipac2doris is located in $STAMPS/bin, and this should be in your
$PATH. Have you changed the StaMPS_CONFIG.bash file to represent your
directory structure? If you made an error there, it should be in the
first line:
export STAMPS="[your stamps directory]"
The above should hold for v3.1 and above surely, but most likely will
also hold for the versions below. Still, I would strongly recommend
using the newest version, if you are not doing so already.
Let me know if you still cannot find the problem.
Karsten
On 9 feb, 13:44, Selena_Ge <helennikola...@mail.ru> wrote:
> Additional info.
>
> elena@sec21-dynip-181:~/data/DORIS/slc> source /usr/local/
> StaMPS_v3.2b3/StaMPS_CONFIG.bash
> elena@sec21-dynip-181:~/data/DORIS/slc> roipac2doris
> bash: roipac2doris: command not found
>
> I feld that I do something wrong ... but what?
Selena_Ge
Thanks a lot for your answer.
I have decided my those problem. I use last version.
But now I confuse on the step
make_coarse
After this step I checked my Coarse_orbits_translation_lines: and
Coarse_orbits_translation_pixels:
4 slaves have good values, 5 slaves have wrong values, 8 slaves have
some values Coarse_orbits_translation_lines/pisels but haven't
information
Number of correlation windows: 0 of 21
# center(l,p) coherence offsetL offsetP
What is it mean? How is possible to solve this?
In instruction I didn't understand next :
Add the translation (?) to the master crop range (where are
_Start_crop: ??)
Thanks a lot
Selena
Selena_Ge
--- WARNING SUMMARY ---
There were 6 messages:
1: found_sarp==false
2: ABW deviates more than 100 Hz from ERS2 nominal?
3: found_sarp==false
4: ABW deviates more than 100 Hz from ERS2 nominal?
5: getoffset: mean coherence of estimates used < 0.2
6: (please check bottom of LOGFILE to see if offset is OK)
Selena
Karsten
find a proper offset, which in practice means that it can't find a
matching area in the master and slave within the search window. This
can have several causes. Could you send me the step_coarse.log of one
(or multiple) of the failed slaves? It might give me some clues about
what is going wrong.
Karsten
Karsten
And during timing I have
ERROR : [products.cc[2800]]: master outside DEM: most South
latitude: 47 [deg]; master requires: 41.9967 [deg]
Caught error of EXCEPTION class!
But it is strange for me because I check in another program that my
DEM covers master....
Selena [/quote]
Doris checks if a DEM covers the master using the metadata that you
provide in timing.dorisin. It does not use the data inside the DEM
itself. The error would suggest there is an error in your metadata.
Check timing.doris to see if SAM_IN_SIZE, SAM_IN_DELTA and SAM_IN_UL
are correct.
Ziyadin
Hi,
It seems very likely that your lat lon and/or nx ny are placed in
reverse sense. Try swapping the order ; should be lat lon and thus
number of lines (in south-north) number of collumns (in east - west).
then the upper left corner should be given.
Ziyadin
Selena_Ge
Thanks!
So my real range of Lat (N) 41.52-43.2
of Long (E) 43.15 - 44.41 (master image)
SAM_IN_SIZE 3601 2402 // rows cols
SAM_IN_DELTA 0.000833333333333 // in degrees
SAM_IN_UL 44.00 43.00 // lat and lon of upper left
ERROR : [products.cc[2817]]: master outside DEM: most West
longitude: 43 [deg]; master window requires: 37.2313 [deg]
Ziyadin
Assuming the coordinates and the pixel size (0. 0008333333) you give
correct ny and nx should be calculated
41.52 - 43.2=1.68/0.0008333333=2017 and
43.15 - 44.41= 0.9716/0.0008333333= 1166
So it should be
SAM_IN_SIZE 2017 1166
SAM_IN_DELTA 0.00083333333333
SAM_IN_UL 43.2 43.15
Make sure that
dem file size is exactly equal to nx * ny * pixel size * 4 (if
intiger then * 2 not *4)
ziyadin
> --
> You received this message because you are subscribed to the Google
> Groups "MAINSAR" group.
> To post to this group, send email to mai...@googlegroups.com.
> To unsubscribe from this group, send email to mainsar+u...@googlegroups.com
> .
> For more options, visit this group at http://groups.google.com/group/mainsar?hl=en
> .
>
Karsten
master image, not her DEM. That would make the above calculate rows
and columns incorrect. From what I have seen so far, the DEM and the
metadata seems correct, but Doris is somehow getting the coordinates
of the master window wrong.
"master window requires: 37.2313 [deg]"
37.23 degrees E is way outside her area of interest, and as far as I
could see not the area covered by the SAR images. I am not at all sure
what is causing this though.
Karsten
On 10 feb, 22:38, Ziyadin <ziya...@gmail.com> wrote:
> Hi,
>
> Assuming the coordinates and the pixel size (0. 0008333333) you give
> correct ny and nx should be calculated
> 41.52 - 43.2=1.68/0.0008333333=2017 and
> 43.15 - 44.41= 0.9716/0.0008333333= 1166
> So it should be
>
> SAM_IN_SIZE 2017 1166
> SAM_IN_DELTA 0.00083333333333
> SAM_IN_UL 43.2 43.15
>
> Make sure that
> dem file size is exactly equal to nx * ny * pixel size * 4 (if
> intiger then * 2 not *4)
>
> ziyadin
>
Selena_Ge
I checked all my data and found next:
10 images I have normal res file
Scene_centre_latitude: 42.6526164573
Scene_centre_longitude: 44.6046064673
8 images in my res file I have next:
Scene_centre_latitude: -0.0000000016
Scene_centre_longitude: 7.8441110999
Have you somebody idea how can I decide this problem?
See my preview message:
>8 slaves have
>some values Coarse_orbits_translation_lines/pisels but haven't
>information
>Number of correlation windows: 0 of 21
># center(l,p) coherence offsetL offsetP
Because this images without long and lat....
Best,
Elena
Karsten
holds a set of output paramaters from ROI_PAC, among others the
latitude and longitude of the satelite, called LATITUDE and LONGITUDE.
Could you compare those for the correct and incorrect scenes?
Selena_Ge
In rsc:
HEIGHT_DT
13.5619100613252
VELOCITY
7550.17913207102
LATITUDE
41.8660236
LONGITUDE
40.4860701
in res:
Scene_centre_latitude: 42.6526164573
Scene_centre_longitude: 44.6046064673
'Unnormal' case :
In rsc:
HEIGHT
0
HEIGHT_DT
nan
VELOCITY
nan
LATITUDE
NaN
LONGITUDE
0.0000000
HEADING
NaN
in res:
Scene_centre_latitude: 7.8441110999
Scene_centre_longitude: 0.0000000000
So problems in ROI_PAC... is it possible to calculate manualy? Or what
advise?
Elena
Karsten
in question. Is orbit information available? Anyway, you could try and
copy/paste the scene latitudes and longitudes from the correct .res
files in the incorrect ones manually, I have no idea if it will work,
but surely worth a shot I would say.
Selena_Ge
about copy/paste
for example in one data long=44.60939
another cases long=44.61097 or long= 44.624158
Karsten
If you want to try it, just pick one of them, the differences are
(relatively) small. If the orbit information is truly available, Doris
will redo the orbit information in the make_orbits step when creating
the IFG's. Check after that step (especially for the 8 scenes) if
Doris was able to find datapoints from the orbit files. If this is not
the case, something is wrong with your orbit files. Again though, I am
not sure if the copy/paste will work.
Selena_Ge
I followed your advise (copied lat/long to 8 scenes from
20040218-20060607 from another scene) and recieved next:
Again 8 images have next:
Coarse_correlation_translation_lines: 1537
Coarse_correlation_translation_pixels: -269
Number of correlation windows: 0 of 21
# center(l,p) coherence offsetL offsetP
Best,
Elena
Karsten
I am sorry, but I have no idea what else to try. I can only suggest
subscribing to the Doris user list and present them with the question.
See:
http://enterprise.lr.tudelft.nl/doris/Doris_registration.html
Karsten
On Feb 12, 5:53 pm, Selena_Ge <helennikola...@mail.ru> wrote:
> So,
> I followed your advise (copied lat/long to 8 scenes from
> 20040218-20060607 from another scene) and recieved next:
>
> Again 8 images have next:
>
> Coarse_correlation_translation_lines: 1537
> Coarse_correlation_translation_pixels: -269
> Number of correlation windows: 0 of 21
>
> # center(l,p) coherence offsetL offsetP
>
> Best,
> Elena
Andy Hooper
it looks like you are processing post-2000 ERS-2 data, is this correct?
If so, ROI_PAC can only process them in deskew mode if the Doppler
centroid is less than half a PRF in magnitude, so this may be your
problem. Also, there are no precise orbits after August 2003.
Cheers,
Andy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Andy Hooper
Assistant Professor
Delft Institute of Earth Observation and Space Systems
Delft University of Technology
Kluyverweg 1, 2629 HS, Delft, The Netherlands
a.j.h...@tudelft.nl
tel: +31 15 278 2574
fax +31 15 278 3711
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Selena_Ge
Thanks for answer! I have problem with data after August 2003.
And you wrote:
'there are no precise orbits after August 2003. '
is it possible to do something usefull with this data?
Best,
Elena
Selena_Ge
do?
I have same situation with ENVISAT data(2004-2007), i.e. I couldn't
read Orbit Information (using ODR). I have in res files next:
HEIGHT 0
HEIGHT_DT 0
VELOCITY 0
LATITUDE 0
LONGITUDE 0
HEADING 0
In case when I use HDR :Illegal division by zero at /usr/../
make_raw_envi.pl line 286, <RSC1> line 120 (because could't read same
values)
As I can suggest I have problem with getorb. Getorb_2.3.2 have been
installed. Somebody has idea how to fix this?
Best,
Elena
Andy Hooper
it is possible to process with the header orbits by changing ODR to
HDR in step_slc_ers. You will also need to get the orbit information
into the master and slave.res files - you can do this in the same way
as is done at the end of step_slc_envi_vor.
Cheers,
Andy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Andy Hooper
Assistant Professor
Delft Institute of Earth Observation and Space Systems
Delft University of Technology
Kluyverweg 1, 2629 HS, Delft, The Netherlands
a.j.h...@tudelft.nl
tel: +31 15 278 2574
fax +31 15 278 3711
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Selena_Ge
It works with ERS-2 data!!!
But ENVISAT...
slc/20070905> step_slc_envi_vor
ASA_IM__0CNPAM20070905_184711_000000162061_00228_28839_2754.N1
+make_raw_envi.pl Checking I/O
+make_raw_envi.pl General definitions
Facility: PDAS-M
Acqsn date: 070905
+make_raw_envi.pl Retrieving Instrument file from /usr/local/
ROI_PAC_3_0_1/ROI_PAC/INS_DIR
+make_raw_envi.pl Using Instrument file: /usr/local/ROI_PAC_3_0_1/
ROI_PAC/INS_DIR/
ASA_INS_AXVIEC20061220_105425_20030211_000000_20071231_000000
Decoding 1
frame(s)
+make_raw_envi.pl asa_im_decode
ASA_IM__0CNPAM20070905_184711_000000162061_00228_28839_2754.N1 /usr/
local/ROI_PAC_3_0_1/ROI_PAC/INS_DIR/
ASA_INS_AXVIEC20061220_105425_20030211_000000_20071231_000000
tmp_IMAGERY.raw 1
0
width=5681,
length=26175
subtracting range
bias
+make_raw_envi.pl Finding reference counter, pri and
prf
+make_raw_envi.pl Reading the imagery
file
+make_raw_envi.pl Writing the imagery resource
file
+make_raw_envi.pl Reading state vectors, Building
hdr_data_points_20070905
file
+make_raw_envi.pl Retrieving Orbit file from /usr/local/ROI_PAC_3_0_1/
ROI_PAC/
VOR_DIR
+make_raw_envi.pl Final orbits not found, using PRELIMINARY orbit file
+make_raw_envi.pl Orbit file was not found in /usr/local/ROI_PAC_3_0_1/
ROI_PAC/VOR_DIR or
+roi_prep.pl Read the inputfile
+roi_prep.pl Checking I/O
20070905.raw does not exist or is not readable
Can't read 20070905_roi.in
Best,
Elena
Selena_Ge
I have to ask because I feel something goes wrong.. I think, I
misunderstand something (((. My steps:
>step_slc_ers
>bash: dismph: command not found
>step_master_setup
Output: Parameter pool for Doris: /home/elena/data/DORIS/SLC/19950808/
master.res
cpxfiddle -qnormal -w5700 -l5999 -L20999 -p1999 -P4999 -fcr4 -ofloat
19950808.slc > 19950808_crop.slc
@(#)Doris software, $Revision: 4.01 $, $Author: TUDelft $
# fsize: 682176000
#cpxfiddle: WARNING: -L: lastline>numlines; continuing with numlines
of file.
(master_crop.slc, master.slc.rsc have been created in INSAR_master
folder- my comment)
>make_slcs_ers
Keyword RANGE_OFFSET doesn't exist in 19920726.raw.rsc, returning 0
cpxfiddle: INFO: Number of output pixels: 1425
(slave_crop.slc haven#t be created!!! - my comment)
>step_master_orbit_ODR
WARNING : Strange value for f_DC_a1: 0; setting f_DC_a1=0 (expected
~1e7)
WARNING : other definition of ATLANTIS?
WARNING : strange value for f_DC_a2: 0; setting f_DC_a2=0 (expected
~1e12)
WARNING : other definition of ATLANTIS?
WARNING : found_sarp==false
WARNING : ABW deviates more than 100 Hz from ERS2 nominal?
...
WARNING : File: '/home/elena/.../INSAR_19950808/19950808_crop.slc' has
wrong fileformat or dimensions: bytesperpix=8, #l=15001, #p=3001;
size_computed=360144008B v. size_ondisk=215159696B
>step_master_timing
WARNING : Strange value for f_DC_a1: 0; setting f_DC_a1=0 (expected
~1e7)
WARNING : other definition of
ATLANTIS?
WARNING : strange value for f_DC_a2: 0; setting f_DC_a2=0 (expected
~1e12)
WARNING : other definition of
ATLANTIS?
WARNING :
found_sarp==false
WARNING : ABW deviates more than 100 Hz from ERS2 nominal?
cpxfiddle: WARNING: using real input, width in non-complex pixels
WARNING : Check estimated offset coarse corr: it seems unreliable.
WARNING : There are 2 offset pairs which has equal mode values are
equal.
WARNING : Check offset results and logs, and increase the number and/
or the size of the correlation windows.
WARNING : getmodeoffset: mean coherence of estimates used < 0.2
WARNING : (please check bottom of LOGFILE to see if offset is OK)
FILEs
ropfiles_ers.dorisin
S_DBOW 6000 21000 2000 5000
master_crop.dorisin
M_DBOW 6000 21000 2000 5000
first_l 6000
last_l 21000
first_p 2000
last_p 5000
roi.proc
use1dopp=1
mean_pixel_rng = 1500
ymin = 6000
ymax = 21000
Andy Hooper
please follow the manual carefully. Line numbers in master_crop.in are
relative to the SLC that has been created, not the SLC for the whole
data file.
Andy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Andy Hooper
Assistant Professor
Delft Institute of Earth Observation and Space Systems
Delft University of Technology
Kluyverweg 1, 2629 HS, Delft, The Netherlands
a.j.h...@tudelft.nl
tel: +31 15 278 2574
fax +31 15 278 3711
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karsten
program to visualize complex data, which you will have to install if
you want to use it. With current StaMPS version, you however don't
need it. You can open the .ras files created with most graphics
programs (like xv, eog, GIMP, etc). If you open those, you can preview
the crops and such.
Karsten
StaMPS, but is no longer part of StaMPS due to it not compiling
properly on current Linux versions. In any case, use the .ras files to
preview your crops. I'll also remove that command from the manual.
Selena_Ge
It's works.
Now I have a next problem - my data are so bad. All time I get: mean
coherence of estimates used <0.2
I changed the number of windows in timing.dorisin to higher number
(90). I tried to calculate manual DEM offset.
I didn't use orbits info.
Now I have prc orbits. Is it possible to use them? How?
Best,
Elena
Selena_Ge
I change HDR on PRC in step_slc_ers.
Add export SAR_PRC_DIR="/usr/local/.../PRC_DIR"
PRC_DIR with folders ers1 and ers2. in each folders are files
PPP_yymmdd_no_revi.Z.
When I run step_slc_ers I get :
/usr/local/.../PRC_DIR/ERS2/arclist not readable
+state_vector.pl select_PRC_date.pl failed in state_vector.pl
How is possible to create this arclist if I haven't
Best,
Elena
Selena_Ge
Retrieve the orbit file with the date and orbit number that most
closely precedes the date and orbit of the given SAR scene. After
downloading the necessary files, update the list of orbit files by
running arclist_PRC.pl in the same directory.
It seems to be working )))!
Elena
Selena_Ge
So, I an using PRC orbits. But step : step_master_orbit_ODR confused
me.
I decided skip as wrote in manual (only run if using precise ODR
orbits). I run step_master_timing and get next:
PROGRESS: Start SIMULATE AMPLITUDE.
Caught SIGSEGV: Segmentation fault.
and then in the step make-orbits:
WARNING : string: "NUMBER_OF_DATAPOINTS:" not found (i.e., orbit) in
file: master.res.
....
(getorb: reading arclist /usr/local/ROI_PAC_3_0_1/ROI_PAC/ERS2/
arclist)
(getorb: orbit file /usr/local/ROI_PAC_3_0_1/ROI_PAC/ERS2/ODR.B65)
So, By default again I use ODR orbits
Help me please, I misunderstand this.
Best,
Elena