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

PyCuAmpcor: offer an option to fix the starting pixel locations #722

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

lijun99
Copy link
Contributor

@lijun99 lijun99 commented May 25, 2023

Some changes were made to allow users to fix the coordinate of the first window (center). This will be useful in cases such as 1) to compare the results with different window sizes (center needs to be fixed); 2) to find out the offsets for a particular pixel or a group of pixels.

When the center is fixed, it is possible that some pixels in the window are out of range when the window is close to borders. Zeros are padded for these out-of-range pixels.

The code tidying from #622 is also merged. Thanks, @rtburns-jpl !

Lijun Zhu added 2 commits May 28, 2022 16:17
in this update,
* either the starting pixel(corner) or the center of window location may be specified (see README)
* by specifying the starting/ending pixel locations, the reference/search window may go beyond the range of the original images. Zeros are filled in instead. In this case, the offset fields at the edge may be incorrect.
* The range check is no longer needed. It only runs in DEBUG mode and issues warning messages when pixels are outside the image range.
@lijun99
Copy link
Contributor Author

lijun99 commented Dec 15, 2023

A recent update 51af91d fixes the issue of gpu memory leak when repeating the cuAmpcor processes within the same python script.

@hfattahi
Copy link
Collaborator

hfattahi commented Apr 8, 2024

@lijun99 sorry for getting to this PR very late. We have had enough with the ISCE3, NISAR etc. Is this PR still the latest or do you want to change anything?
@vbrancat and @rtburns-jpl please take a look at this PR. Also, do we need to port any part to isce3?

@hfattahi hfattahi requested review from rtburns-jpl and vbrancat April 8, 2024 16:05
@lijun99
Copy link
Contributor Author

lijun99 commented Nov 5, 2024

Sorry for my late reply, I was into other things as well.

Please consider approving this PR, which includes two major updates

  1. an option to choose the location of the starting pixel, which is good for debugging, also, comparing the offsets with different window sizes;
  2. a memory leak issue if the script is called repeatedly.

Thanks! @hfattahi @rtburns-jpl @vbrancat

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

Successfully merging this pull request may close these issues.

2 participants