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

Take into account accurate times in FOV plotting #41

Open
ebuchlin opened this issue Feb 1, 2024 · 2 comments
Open

Take into account accurate times in FOV plotting #41

ebuchlin opened this issue Feb 1, 2024 · 2 comments

Comments

@ebuchlin
Copy link
Collaborator

ebuchlin commented Feb 1, 2024

The observer for each FOV plot is taken at the mid-time of the observation (see FileMetadata.get_observer(), but the delay between this reference time and the actual time of each exposure can be quite large.

This delay should be taken into account, for the left and right edges of the FOV (last and first slit positions), and in principle also for each point on the top and bottom boundaries. However, one needs to be careful to interpret the WCS headers correctly, especially what they mean in case target locking (following solar rotation) is activated.

@ebuchlin
Copy link
Collaborator Author

This concerns 1 observation; there would be the same issue when plotting the FOVs for several observations over a long duration.

@ebuchlin
Copy link
Collaborator Author

Maybe use SunPy's propagate_with_solar_surface context manager.

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