How should NDCube.resample handle extra_coords?

Open
#431 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
data

Research direction

Start at the NDCube.resample entry point and inspect how extra_coords are currently treated. Investigate the challenges of resampling extra_coords and compare the possible policies described in the issue. Done means agreeing on a policy and recording the resulting behavior for this functionality.

Written by the indexing model from the issue text.

Description

Discussion Resample
Description

Initial implementation of NDCube.resample will ignore and drop NDCube.extra_coords. However, this must be resolved before we release this functionality. One option is to decide to always ignore extra_coords. However a preferable situation for users would be that extra_coords would be handled in some way.

What are the challenges for resample regarding extra_coords and what should be our policy?

Dominant language
Python
Stars
49
Forks
56
Avg merge
5h 54m
Merged PRs (30d)
9

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sunpy/ndcube

All issues in sunpy/ndcube

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.