yt-project/yt

Implement Periodicity YTEP

Open

#1,366 opened on May 4, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (315 forks)auto 404
help wantedwishlist

Repository metrics

Stars
 (556 stars)
PR merge metrics
 (PR metrics pending)

Description

We have a long-standing plan to better handle different kinds of boundary conditions. Doing so would make yt nicer to use for people who work with non-periodic data. In addition we would resolve a number of issues, e.g. #1209 and #1185.

Optimally we shouldn't need to tell our users to set ds.periodicity = (True, True, True). Instead, yt should do something sensible when you ask for data at a non-periodic boundary.

Contributor guide

Research direction
Read the YTEP 0006 document and examine related issues #1209 and #1185 to understand the desired behavior. Then plan implementation changes in the codebase to handle non periodic boundaries.
Tech stack
python
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50