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

RHESSI images and flare feature events sometimes not the same. #631

Open
wafels opened this issue Oct 8, 2024 · 0 comments
Open

RHESSI images and flare feature events sometimes not the same. #631

wafels opened this issue Oct 8, 2024 · 0 comments

Comments

@wafels
Copy link
Contributor

wafels commented Oct 8, 2024

This link shows the issue

https://helioviewer.org/?loadState=f20bd38277b40673a46f576857b96a434c04e6f020bff8254d97153eee846d19

but it needs some more explanation.

In this case, the user has selected to show RHESSI images and the RHESSI flare feature/event. One might expect that for a given time, the RHESSI image and feature/event should be at the same place on the Sun. This is because RHESSI provides images only when there are solar flares, and solar flares occur over small portions of the Sun.

I think what is going here is that the image selector and RHESSI flare feature/event selector are both working as intended, but they are giving a non-intuitive result. The RHESSI flare feature/event selector is showing the feature/event that overlap with the observation time. The image selector for RHESSI is finding the image closest in time that matches the energy band and reconstruction method criteria. These need not be the same flare - it is possible that an image that satisfies all the defined criteria occurred at a different time and place than the RHESSI feature/event pin.

This is illustrated in this link:

https://helioviewer.org/load/f6179d722593f93be5c8ffedc621d54e6f41152421ef524d8db3e95636487cf8

The only difference in helioviewer.org between the first and second link is the change in energy band for the RHESSI image. The RHESSI image and the feature/event pin are now co-spatial, which makes intuitive sense.

The question is, what to do about this?

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

1 participant