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

look vectors problem #128

Open
CUMT530849827 opened this issue Nov 16, 2024 · 6 comments
Open

look vectors problem #128

CUMT530849827 opened this issue Nov 16, 2024 · 6 comments

Comments

@CUMT530849827
Copy link

I processed gmtsar data with kite and found that the look vectors for lifting the rail were incorrect. I processed two earthquakes in a row and found that it was the same in both cases. Could you tell me how this happened? How should I solve this problem
#73 (comment)
Here are the look vectors for the two earthquakes I worked with
image
image
The following is the direction of the lift vector given in the case list
image

@hvasbath
Copy link
Member

hvasbath commented Nov 17, 2024

Yes, so please make sure that the los vector is correct. You need to rotate your heading angle by 180 degree.

@CUMT530849827
Copy link
Author

@hvasbath @miili
I calculated the enu of the ascending and descending orbits and found that there was no error here. I searched for many reasons and did not find it, but I found hvasbath/beat#93 that the ascending vector in this problem was the same, and I wondered if there was a problem with the drawing script
image
image
image
hvasbath/beat#93 The picture in question is below
image

@hvasbath
Copy link
Member

First of all there is no point in showing plots of BEAT. Please open the kite scenes with spool and check the look vectors there. BEAT does nothing but reading from Kite, if there is sth wrong then happens in the import from GMTSAR. I dont understand what the first column of your screenshot is supposed to be?

@CUMT530849827
Copy link
Author

I used spool to open the track lifting data, but I don't know how to check their look vectors
image

@hvasbath
Copy link
Member

You can select phi here, but already from the formula in scene_io we can see there is sth wrong.
image

image

For ascending track this arrow you marked must look into the exact other direction- so rotated by 180 deg.

So the error is in the equation you marked just here:
image

Until that is fixed I suggest you load your scene through a python script and add pi.

from kite.sceene import Scene
from numpy import pi

scn = Scene.load("your_scene_name")
scn.phi += pi
scn.save('kite_scene_outname')

Then please check again in spool. And once that is correct- please reimport to BEAT.

@CUMT530849827
Copy link
Author

Thank you very much for helping me find the mistake so kindly and carefully

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