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

Support for Level 3 EVE data products #4216

Open
wtbarnes opened this issue May 29, 2020 · 6 comments
Open

Support for Level 3 EVE data products #4216

wtbarnes opened this issue May 29, 2020 · 6 comments
Labels
Effort Medium Requires a moderate time investment net Affects the net submodule Package Novice Requires little knowledge of the internal structure of SunPy Priority Low Slow action required timeseries Affects the timeseries submodule Upstream Fix Required A fix needs to go upstream to another package

Comments

@wtbarnes
Copy link
Member

We currently support downloading and parsing Level 0 and Level 1 EVE data via Fido and TimeSeries. Support for Level 2 data is still an outstanding issue (#2407). Additionally, there are Level 3 data products. These are daily averages from each spectral band from each instrument. Additional details in the links below. We should consider adding support for downloading and parsing these files.

@wtbarnes wtbarnes added net Affects the net submodule timeseries Affects the timeseries submodule labels May 29, 2020
@hayesla
Copy link
Member

hayesla commented May 29, 2020

I guess we only support EVE/ESP level 0 and 1, ESP is only timeseries and doesn't deal with spectra - EVE/MEGS which is a bit more complicated but would be great to do!

@dstansby
Copy link
Member

Should this go in the new instrument package instead of core?

@wtbarnes
Copy link
Member Author

wtbarnes commented Jun 2, 2020

Maybe? This goes back to the question of what the responsibility of core is though.

We definitely don't want to provide specific analysis tools for this data. But I think we should be providing at least a way to download and read in the data into some core, albeit maybe generic, data structure.

To @hayesla's point though, I guess this would necessitate better support for spectra which we certainly don't have at the moment.

@Cadair
Copy link
Member

Cadair commented Jun 3, 2020

I believe that @jmason86 and others at LASP are working on stuff related to this, so we should coordinate with them.

@jmason86
Copy link
Sponsor Contributor

jmason86 commented Jun 3, 2020

"working on" is generous. We have plans to do so and are proposing a NASA HDEE to get all of the LASP hosted solar spectral irradiance data accessible from sunpy through Fido. It'll likely be analogous to the VSO or JSOC classes that are there now (LASP's is called LISIRD and the API is called LaTiS). We're planning to leverage @wafels ongoing HDEE work to establish a spectral container / data structure / what-have-you. HDEE proposals this year are due July 1 so this month we should have a clearer picture of how we may accomplish this, but the work won't actually start for several months.

@wtbarnes
Copy link
Member Author

wtbarnes commented Jun 5, 2020

That's great to hear. I'll go ahead and keep this open and perhaps we can break it into more specific issues as things progress.

@nabobalis nabobalis added Effort Medium Requires a moderate time investment Package Novice Requires little knowledge of the internal structure of SunPy Priority Low Slow action required Upstream Fix Required A fix needs to go upstream to another package labels Jul 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Effort Medium Requires a moderate time investment net Affects the net submodule Package Novice Requires little knowledge of the internal structure of SunPy Priority Low Slow action required timeseries Affects the timeseries submodule Upstream Fix Required A fix needs to go upstream to another package
Projects
None yet
Development

No branches or pull requests

6 participants