-
Notifications
You must be signed in to change notification settings - Fork 3
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
Converting Stonyhurst coordinates to pixel values. #4
Comments
@kingbob8, maybe you're able to help here? |
If you're able to directly obtain a HMI image from JSOC, do you see the same thing for the same image? |
This top one is from SDOML, the white cross is the (0,0) point in Stonyhurst coordinates And this one I've obtained directly from JSOC using the For completeness, this is what the |
I believe it's most likely due to inclination that hasn't been corrected for. It should perhaps line up twice a year at (0,0)? I would suggest plotting the position as a function of time, and it should be ~ sinusoidal |
I'll try to do that. Seems likely to be what happens, but I've never heard of such a thing with SDO and images in JHelioviewer seem to be centred, which leads me to believe it may be something to do with SunPy. I'll try to open an issue in their project because their chat isn't working and I'll comment back in case this is useful for people in the future. Indeed, it does have a sinusoidal pattern over time in the y-direction |
I'm trying to convert Stonyhurst coordinates into pixel values by using Sunpy. A simple example, assuming root is the SDOML
s3://gov-nasa-hdrl-data1/contrib/fdl-sdoml/fdl-sdoml-v2/sdomlv2_hmi.zarr/
folder, is as follows (this is just plotting the stonyhurst coordinates which can later on be converted to pixel values withworld_to_pixel
)However, the centre in stonyhurst coordinates is not at the centre of the image. Is this expected? As I understand it, SDO images should have the stonyhurst centre in the centre of the image. Could this be a problem when reading the header information? Or is it a result of the processing that is applied to SDOML data.
The text was updated successfully, but these errors were encountered: