search

yumorishita / LiCSBAS2

GNU General Public License v3.0
26 stars 4 forks source link

LiCSBAS2-1.9.0 stuck in reading unw and cc data and terminal closing automatically showing no errors #43

Closed sagarmaniraut closed 8 months ago

sagarmaniraut commented 8 months ago

I am a student and doing my dissertation on this topic however I am not been able to proceed forward from this step as the terminal stops here and close automatically without showing any error. The same things happens retrying. Help me please ! IMG_4979

yumorishita commented 8 months ago

I have no idea. Maybe your disk is full?

sagarmaniraut commented 8 months ago

Thank you for your comment sir. The problem is solved while running the data in mac OS. Previously I was trying in windows OS through virtual Box.

amelindanuronf commented 7 months ago

Dear Mr. Morishita, I was running batch_LiCSBAS.sh. The processing stopped at the "Create unw and cc" stage with the following error:

580/1375th IFG... 380/1375th IFG... 610/1375th IFG... ERROR 1: TIFFFillStrip:Read error at scanline 1794; got 3293 bytes, expected 3488 ERROR 1: TIFFReadEncodedStrip() failed. ERROR 1: /mnt/c/Project_TA/Ascending2/GEOC/20190409_20190415/20190409_20190415.geo.cc.tif, band 1: IReadBlock failed at X offset 0, Y offset 898: TIFFReadEncodedStrip() failed. 20190409_20190415.geo.cc.tif cannot open. Skip 640/1375th IFG... 670/1375th IFG... 440/1375th IFG... 700/1375th IFG... ERROR 1: TIFFFillStrip:Read error at scanline 1098; got 6347 bytes, expected 6717 ERROR 1: TIFFReadEncodedStrip() failed. ERROR 1: /mnt/c/Project_TA/Ascending2/GEOC/20181029_20181116/20181029_20181116.geo.unw.tif, band 1: IReadBlock failed at X offset 0, Y offset 1099: TIFFReadEncodedStrip() failed. 20181029_20181116.geo.unw.tif cannot open. Skip 470/1375th IFG... 500/1375th IFG...

202402292236batch_LiCSBAS_01_16.log

202402291913batch_LiCSBAS_01_16.log

I have tried re-downloading the file, but the error persists. Can you please help me resolve this issue?

Thank you

yumorishita commented 7 months ago

I tried processing the same dataset but could not reproduce the issue. I have no idea because it seems to be because of your environment.