This PR is meant to better handle the ionosphere correction in MintPy. Before this PR, the ionosphere data was loaded into MintPy as ionospheric interferograms. We then do an SBAS inversion to get an ionospheric time series to do the correction (history).
As MintPy users, for simplicity, now, we want to load the ionosphere time series products from ISCE2/topStack processor directly. Once this #600 PR on ISCE is merged into topsStack code, the ionosphere final products contain the following files storing under the directory of topsStack processor, $STACK_DIR:
$STACK_DIR/ion_dates/*.ion: the smooth ionospheric time series for each epoch
$STACK_DIR/ion_burst_ramp_merged_dates/*.float: the burst ramp time series for each epoch
Once the mintpy .cfg template file is filled with the above two paths, we can load those ionospheric time series directly into two separate time-series files ion.h5 and ionBurstRamp.h5, respectively during the load_data.py stage.
## EXAMPLE
load_data.py -t smallbaselineApp.cfg # this will load ifgrams, geometry, and ionosphere time series
load_data.py -t smallbaselineApp.cfg -l ifg geom ion # equivalent to above
load_data.py -t smallbaselineApp.cfg -l ion # this will just load the ionosphere time series
load_data.py -t smallbaselineApp.cfg -l geom # this will just load the geometry
The loaded ionosphere files ion.h5 and ionBurstRamp.h5 will be under inputs/. Later, we can apply the correction by the following:
Thank you @yuankailiu for the big PR. I want to let you know that it may take some time for me to find time and review it. In the meanwhile, I will cut for a new release (version 1.5.2) before merging this PR.
Outline
This PR is meant to better handle the ionosphere correction in MintPy. Before this PR, the ionosphere data was loaded into MintPy as ionospheric interferograms. We then do an SBAS inversion to get an ionospheric time series to do the correction (history).
As MintPy users, for simplicity, now, we want to load the ionosphere time series products from ISCE2/topStack processor directly. Once this #600 PR on ISCE is merged into topsStack code, the ionosphere final products contain the following files storing under the directory of topsStack processor,
$STACK_DIR
:$STACK_DIR/ion_dates/*.ion
: the smooth ionospheric time series for each epoch$STACK_DIR/ion_burst_ramp_merged_dates/*.float
: the burst ramp time series for each epochOnce the mintpy .cfg template file is filled with the above two paths, we can load those ionospheric time series directly into two separate time-series files
ion.h5
andionBurstRamp.h5
, respectively during theload_data.py
stage.The loaded ionosphere files
ion.h5
andionBurstRamp.h5
will be underinputs/
. Later, we can apply the correction by the following:Commits
new template keywords for the ion time series:
Based on above, I also update the
defaults/auto_path.py
,defaults/smallbaselineApp.cfg
,objects/stack.py
.load_data: more flexible loading datasets (changes in
load_data.py
,cli/load_data.py
)load_data.py -l
option. choice from {ifg
,geom
,ion
}prep_isce.py
andstackDict.py
: read ion time-series files from topsStack fileschanges in
readfile.py
to read these isce .float and .ion filesDescription of proposed changes
Reminders