Skip to content
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

autoRIFT binding #6

Open
leiyangleon opened this issue Sep 28, 2021 · 1 comment
Open

autoRIFT binding #6

leiyangleon opened this issue Sep 28, 2021 · 1 comment

Comments

@leiyangleon
Copy link

leiyangleon commented Sep 28, 2021

Hello, I was wondering if autoRIFT is directly included in the isce3 installation as done in isce2.

Is there any update in isce3 that would potentially improve the workflow of topsApp(up to mergebursts)+autoRIFT?

@hfattahi
Copy link
Contributor

Hi Yang,
No autoRift is not currently included in isce3. ISCE3 developments is driven by NISAR and therefore the software does not formally support Sentinel-1 yet. As we will add Sentinel-1 support to isce3 we can build other algorithms within isce3. It can be discussed if we should have many workflows (such as autoRift, topsApp, stripmapApp, etc) within isce3 or have isce3 to stay as core module library and other workflows in different repositories could use isce3 as needed. For example I can imagine that autoRift could have its own repository and its own dependencies which would be for example isce3 and openCV, etc. This way, isce3 dependencies won't go out of hand and will remain limited and manageable. What I'm trying to clarify here is not specific to autoRIFT but the same discussion applies to any other workflow. I'm interested to hear others opinions on this topic.

LiangJYu pushed a commit to LiangJYu/isce3 that referenced this issue Apr 16, 2022
merged the most recent develop branch into split_main_band
gmgunter pushed a commit that referenced this issue Oct 2, 2023
* add GUNW

* refactor and reformat

* change the h5dataset

* formate with black and refactor

* add GOFF

* fix typos

* condense the code

* add RUNW

* add ROFF RIFG RUNW

* reformat with black

* reformat

* rename the io to insar

* test the codes and add a test.py

* address VB comments

* add the georeference to the GUNW and GOFF products

* fix some parameters of pixelOffsets

* change the geolocation_grid

* fix the iono disable error

* fix the mixed mode

* revise the pixelOffsets dimension

* address VB 2rd review

* make insar new spec package

* fix the insar package issue

* test the insar workflow

* change the RUNW az and rg looks and fix VB comments

* change H5Dataset

* add the RIFG test

* refactor

* refactor the h5_prep

* fix product bug

* correlation surface peak

* fix h5_prep.run for insar

* run isort

* fix the geocode_insar bugs

* fix the unit tests

* fix the crossmul unit test

* attempt to fix the unit tests but failed

* change the productspec version from 1.0.0 to 0.9

* change the product.h5

* remove the odd looks checking

* remove prep_ds_insar

* some formats

* reformat the unwrap

* fix errors in unit test (#6)

* fix errors in unit test

* delete old files

Co-authored-by: Jungkyo Jung <jungkyoj@nisar-adt-dev-7.jpl.nasa.gov>

* address the crossmul unit test failure

* fix the crossmul and rubbersheet unit tests

* fix the hydrostatic

* fix minors

* product specification version

* minor change

* change 0.9 to 0.9.0

* change the prep_insar to prepare_insar_hdf5

* fix LY comments

* address LY comments

* reduce file size (#7)

Co-authored-by: Jungkyo Jung <jungkyoj@nisar-adt-dev-7.jpl.nasa.gov>

* fix geocode_insar bugs

* add the scenecenter parameters

* fix typos

* uploaded compressed files (#8)

Co-authored-by: Jungkyo Jung <jungkyoj@nisar-adt-dev-7.jpl.nasa.gov>

Co-authored-by: Xiaodong Huang <xhuang@nisar-adt-dev-3.jpl.nasa.gov>
Co-authored-by: Jungkyo Jung <jungkyo.jung@jpl.nasa.gov>
Co-authored-by: Jungkyo Jung <jungkyoj@nisar-adt-dev-7.jpl.nasa.gov>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants