-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compute residuals to the timeseries inversion, save to raster outputs #523
Merged
scottstanie
merged 16 commits into
isce-framework:main
from
scottstanie:add-ts-residuals-raster
Jan 9, 2025
Merged
Compute residuals to the timeseries inversion, save to raster outputs #523
scottstanie
merged 16 commits into
isce-framework:main
from
scottstanie:add-ts-residuals-raster
Jan 9, 2025
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When doing `GDAL_NUM_THREADS=2` and LZW, this came up File "/Users/staniewi/repos/dolphin/src/dolphin/_overviews.py", line 95, in create_image_overviews ds.BuildOverviews(resampling.value, levels) File "/Users/staniewi/miniforge3/envs/mapping-312/lib/python3.12/site-packages/osgeo/gdal.py", line 4378, in BuildOverviews return _gdal.Dataset_BuildOverviews(self, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ RuntimeError: /vsimem/decompress_0x312935528.tif:Using code not yet in table After turning the python multithreading off, and the GDAL_NUM_THREADS=1, it was still giving this: RuntimeError: 20210606_20210618.tif, band 1: IReadBlock failed at X offset 0, Y offset 2: TIFFReadEncodedTile() failed. May be caused by: TIFFReadEncodedTile() failed. May be caused by: /Users/staniewi/repos/dolphin/docs/notebooks/work-walkthrough/timeseries/20210606_20210618.tif:Using code not yet in table This was on a Mac with Gdal 3.9.0 $ gdalinfo --version GDAL 3.9.3, released 2024/10/07
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To see whether the time series inversion ran smoothly (which encompasses detecting unwrapping errors, as well as several other upstream errors which may have snuck in), we'd like to see the residuals of
where$A$ is the incidence matrix used during the inversion, $\mathbf{b}$ is the vector of unwrapped phases at a single pixel, and $\mathbf{x}$ is the vector of solved phases, one per secondary date.
Since there could be one single date (or a couple sparse dates) which had problems, we the same number of residual rasters as timeseries rasters by doing
where$|A|^{T}$ is the elementwise absolute value of A.
Small test over tests on the walkthrough data:
A histogram of all the residuals for this area (with vertical lines marking multiple of pi)