Zhang Yunjun

You should run `prepSlcALOS2.py`, and do not run `prepRawSensor.py`, if I understand your workflow correctly.

For frames in 3-digit, e.g. 750, if we set the frame number in the XML file as `0750`, then the code runs through without issue, so I revert the changes,...

mintpy users reported the same issue before while using pyaps (https://github.com/insarlab/MintPy/issues/447): it was because the study area was across the 0 longitudes. The error is fixed on the pyaps side...

@cirrusasf github flagged conflicts for this PR, could you resolve them?

@cirrusasf Thanks for the update. Is this PR ready for review?

Hmm, I would expect the overlapping region having the same SET as well. Your 2nd plot shows this residual is a ramp long the range direction and almost centered around...

I guess this could be due to the `step_size` used in the SET calculation for speedup. Could you test the `set_e` again by setting `step_size = 1` [here](https://github.com/insarlab/MintPy/blob/7704c34797a5db62d2521e84010561ac8cbf94f2/src/mintpy/solid_earth_tides.py#L156)? If confirmed...

> If subtracting 1 from the dimensions [like this](https://github.com/insarlab/PySolid/blob/302ac2c89590b15b7ba81c368b8e8c284cdbaf10/src/pysolid/grid.py#L87-L88) intentional? Yes, this was intentional, to ensure the generated SET from the fortran program to have the size of `length x...

> To clarify though, is this necessary or should the outputs be agnostic to a reference point? I see the output SET.h5 cubes themselves had different recorded reference points, but...

[Thoughts In Progress] until we figure out the offset without spatial referencing. With these tests you have done here, which is super helpful, I think we should adjust the step...