Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a new
EISCube.extract_points()
method:SkyCoord
object (see SunPy coordinate tutorial) containing the coordinates of any points inside the EIS field-of-view. Pixel indices are also accepted by inputting an array and setting "units = 'pixel'" (Astropy units work fine too). Input world coords must be in the helioprojective coordinate frame and an obstime at or near the time of the EIS observation..extract_points()
method outputs a newEISCube
with the data at the selected points (output shape of [1, N, n_wave]). Coordinate information about the selected points are stored in a newEISCube.meta['extracted']
dict. The method also updates.meta['date_obs']
and.meta['duration']
with the information at each point (rather than each raster position).EISCube
can be fit and the results saved to disk, just like any otherEISCube
Other minor changes:
EISCube
will now update.meta['notes']
with a copy of the slice indices. This allows for better recordkeeping of data cutouts. This even works when slicing using real world coords and the.crop
method, although only the array indices for the slice are noted.