Joseph H Kennedy

@yunjunz yep! I'll expand soon; I'm just waiting for the conda-forge PR to go through so I can point to specific things in the feedstock.

So overall, I'm coming from the perspective of "I want my build/installation tool to do as much of the work as possible." This lets the tool handle all the different...

Oh, and I should say, the full refactor (arg-less main and a work function) isn't needed -- it's a nice to have to support the same workflows both programmatically and...

@yunjunz Yep! I think the heavier refactoring is just a "think about it for future development" -- I've actually got a PR started that does all the entrypoints and all...

@yunjunz and @Arctic-Ambrun , a few thoughts the HyP3 side: * using `hyp3lib` is not recommended, and likely to change drastically, as is stated in the `hyp3lib` [README](https://github.com/ASFHyP3/hyp3-lib): > #...

> I'm not actually sure where we should separate hyp3 maintained stuff and MintPy stuff.... To follow up on this a little, the majority of usage we (HyP3) sees is...

@gyp-1991-gq I'm just seeing this, do you still need help? In your error message it looks like `l1.tif` doesn't exist

Since we're processing Level-1 now, the example pair would be: LE07_L1TP_062018_20210717_20210812_02_T1 LE07_L1TP_062018_20210701_20210728_02_T1

In order to better test Landsat-7, we can compare directly to version 1 ITS_LIVE products: * http://its-live-data.jpl.nasa.gov.s3.amazonaws.com/velocity_image_pair/landsat/v00.0/32607/LE07_L1TP_061018_20040321_20160927_01_T1_X_LE07_L1TP_062018_20040225_20160927_01_T1_G0240V01_P076.nc * http://its-live-data.jpl.nasa.gov.s3.amazonaws.com/velocity_image_pair/landsat/v00.0/32607/LE07_L1TP_063018_20040911_20160926_01_T1_X_LE07_L1TP_063018_20040810_20160926_01_T1_G0240V01_P075.nc * http://its-live-data.jpl.nasa.gov.s3.amazonaws.com/velocity_image_pair/landsat/v00.0/32607/LE07_L1TP_061018_20050324_20160925_01_T1_X_LE07_L1TP_061018_20040321_20160927_01_T1_G0240V01_P072.nc * http://its-live-data.jpl.nasa.gov.s3.amazonaws.com/velocity_image_pair/landsat/v00.0/32607/LE07_L1TP_062018_20040803_20160926_01_T1_X_LE07_L1TP_061018_20040625_20160926_01_T1_G0240V01_P068.nc * http://its-live-data.jpl.nasa.gov.s3.amazonaws.com/velocity_image_pair/landsat/v00.0/32607/LE07_L1TP_063018_20040319_20160926_01_T1_X_LE07_L1TP_062018_20040225_20160927_01_T1_G0240V01_P067.nc * http://its-live-data.jpl.nasa.gov.s3.amazonaws.com/velocity_image_pair/landsat/v00.0/32607/LE07_L1TP_061018_20040625_20160926_01_T1_X_LE07_L1TP_061018_20030810_20160927_01_T1_G0240V01_P066.nc * http://its-live-data.jpl.nasa.gov.s3.amazonaws.com/velocity_image_pair/landsat/v00.0/32607/LE07_L1TP_061018_20040711_20160926_01_T1_X_LE07_L1TP_061018_20040625_20160926_01_T1_G0240V01_P066.nc *...

Here's the Landsat-7 naming convention, which holds across collections: https://www.usgs.gov/faqs/what-naming-convention-landsat-collections-level-1-scenes So it looks like just the collection number and possibly the processing date needs to change. You can use this...