Recenter tool only looks at reference layer

[Jdaviz-Triage-Bot]

Reporter: Camilla Pacifici

1. I have 2 images loaded with different resolutions (e.g., same object in at pixel 300,500 in image 1 and at pixel 30,50 in image 2).
2. I select a subset. Subset tool says the subset is at 300,500.
3. If I select image 1 and I use the recenter tool, it works fine.
4. If I select image 2 and I use the recenter tool, it tries to recenter on pixel 300,500 instead of at 30,50 and starts wondering around. The user has no ides what is happening.

Need to figure out a way to deal with this.

As a user, in an ideal world, I would expect the subset to automatically shift to the correct position in image 2, but this might get cumbersome if the user keeps switching from one to the other.
Working in sky coordinates might solve the problem, but the pixel position would still need to be obvious to the user.

Any mitigation plans in the meantime are welcome.

🐱

---

DISCLAIMER: This issue was autocreated by the Jdaviz Issue Creation Bot on behalf of the reporter. If any information is incorrect, please contact Duy Nguyen

[camipacifici]

In the example, images are linked by WCS.

[pllim]

The user has no ides what is happening.

I think what is happening is the same problem as #2139 . The center is accounted for correctly but not the different pixel scales. So, the circle becomes too big when you apply it to the second smaller image. As a result, you probably get too much junk data in that aperture, breaking centering feature.

A natural way to fix this is to use sky region behind the scenes (as discussed also for other workflow problems).

However, this also naturally becomes a non-issue if we proceed with #2238