Particularly after nullification, would probably be helpful if we could include a way of stating for each pixel what the mean baseline of all the IFGs that have data for it is

Hi,
great work, but I met a problem when I used the COMET version to process frame 136D_04941_172131 and 056A_04947_282019.
I'm not sure if there's a problem with my installation. I used Anaconda and installed the required modules using LiCSBAS_requirements.txt

The full log was attached.
202309202016batch_LiCSBAS_11_16.log
202309202030batch_LiCSBAS_02_16.log

Best regards,
Fengnian Chang

• LiCSBAS12: allow nullification threshold to have custom value (e.g. if < pi, we could nullify strong phase bias)
• LiCSBAS12: sum the abs. value of loop closure residuals (identify pixels affected by phase bias) -> maskable

Create a cum.h5 file from epoch models such as GACOS or tides

Add LOOPY (Jacks attempts at at unw error correction)

densify network from a selected good ifg list to achieve a target number of new ifgs to be added

Add in new option for aggressive and conservative nullification

Ensure that if a job times out during the sb inversion, you can pick up from where you left off by reading in the already processed patches

Mask IFGs based on their own coherences, rather than the average
Include plot coherence option for LiCSBAS02

Drop in the code to allow co and post seismic velocities

Hi COMET, I am currently using the interferogram product from LiCS as input for LiCSBAS. To bridge the dry season interferograms, may I request the interferograms product to be reprocessed with spatio-temporal baselines parameters of 120 m and 14 months for a particular frame covering my study area please? Thank you in advance. -Daisy

130 is my way of running sb_inv using 120ref.txt and a user-defined interferogram list from rounds of unwrapping mistake corrections.
133 recalculates the masking stats using ifgs after the correction and masking and adds them to the cum.h5 file.