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

Functionality to read and analyse data from RHESSI mission archive #154

Open
hayesla opened this issue Dec 17, 2024 · 2 comments
Open

Functionality to read and analyse data from RHESSI mission archive #154

hayesla opened this issue Dec 17, 2024 · 2 comments
Labels
Feature Request New feature wanted.

Comments

@hayesla
Copy link
Member

hayesla commented Dec 17, 2024

Describe the feature

There is now lots of nice data products available on the rhessi mission archive
https://hesperia.gsfc.nasa.gov/rhessi3/mission-archive/index.html

It would be good to scope out and add functionality to sunkit-instruments on ways to read this data and analyse it. For example, a way to read the rhessi spec and srm files which could then be imported into sunkit-spex to do spectral fitting etc.

The image cubes could be read in as ndcubes etc.

More to think about here and scoped out as a project

things to think about:

  • the visibility files could be used together with xrayvision to construct images (maps) in python
  • the event lists/flare list reader
  • the spectrum files and srm files for both the standard energy resolution files and the flare high resolution files
  • reading the image cubes as mapcubes (ndcubes) or something
@hayesla hayesla added the Feature Request New feature wanted. label Dec 17, 2024
@hayesla
Copy link
Member Author

hayesla commented Dec 17, 2024

@ianan if you have any other thoughts here on what would be nice to have RHESSI wise

@ianan
Copy link

ianan commented Dec 18, 2024

For these files to be useful often requires additional info from other files, which is easily available within sswidl, for instance flare list info or times for flares/night/saa/decimation, times for "good" detectors etc

From looking at the current functionality already have the ability to read the summary and dbase files (lightcurves and flags) which gives some of this info, but need to double check that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request New feature wanted.
Projects
None yet
Development

No branches or pull requests

2 participants