-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
31 changed files
with
925 additions
and
454 deletions.
There are no files selected for viewing
18 changes: 16 additions & 2 deletions
18
.github/ISSUE_TEMPLATE.md → .github/ISSUE_TEMPLATE/bugs.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,15 +1,29 @@ | ||
--- | ||
name: Bug report | ||
about: Create a report to help us improve | ||
title: '' | ||
labels: bug | ||
assignees: '' | ||
|
||
--- | ||
|
||
* traccuracy version: | ||
* Python version: | ||
* Operating System: | ||
|
||
### Description | ||
# Description | ||
|
||
Describe what you were trying to get done. | ||
Tell us what happened, what went wrong, and what you expected to happen. | ||
|
||
### What I Did | ||
# Minimal example to reproduce the bug | ||
|
||
``` | ||
Paste the command(s) you ran and the output. | ||
If there was a crash, please include the traceback here. | ||
``` | ||
|
||
# Severity | ||
- [ ] Unusable | ||
- [ ] Annoying, but still functional | ||
- [ ] Very minor |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
--- | ||
name: Feature | ||
about: Suggest an idea for this project | ||
title: '' | ||
labels: enhancement | ||
assignees: '' | ||
|
||
--- | ||
|
||
# Description | ||
|
||
Please describe the feature that you would like to see implemented in `traccuracy`. | ||
|
||
# Topics | ||
|
||
What types of changes are you suggesting? Put an x in the boxes that apply. | ||
- [ ] New feature or enhancement | ||
- [ ] Documentation update | ||
- [ ] Tests and benchmarks | ||
- [ ] Maintenance (e.g. dependencies, CI, releases, etc.) | ||
|
||
Which topics does your change affect? Put an x in the boxes that apply. | ||
- [ ] Loaders | ||
- [ ] Matchers | ||
- [ ] Track Errors | ||
- [ ] Metrics | ||
- [ ] Core functionality (e.g. `TrackingGraph`, `run_metrics`, `cli`, etc.) | ||
|
||
# Priority | ||
- [ ] This is an essential feature | ||
- [ ] Nice to have | ||
- [ ] Future idea | ||
|
||
# Are you interested in contributing? | ||
- [ ] Yes! :tada: | ||
- [ ] No :slightly_frowning_face: |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
If you are implementing a new matcher or metric, please append this `&template=new_matcher_metric.md` to your url to load the correct template. | ||
|
||
# Proposed Change | ||
Briefly describe the contribution. If it resolves an issue or feature request, be sure to link to that issue. | ||
|
||
# Types of Changes | ||
What types of changes does your code introduce? Put an x in the boxes that apply. | ||
- [ ] Bugfix (non-breaking change which fixes an issue) | ||
- [ ] New feature or enhancement | ||
- [ ] Documentation update | ||
- [ ] Tests and benchmarks | ||
- [ ] Maintenance (e.g. dependencies, CI, releases, etc.) | ||
|
||
Which topics does your change affect? Put an x in the boxes that apply. | ||
- [ ] Loaders | ||
- [ ] Matchers | ||
- [ ] Track Errors | ||
- [ ] Metrics | ||
- [ ] Core functionality (e.g. `TrackingGraph`, `run_metrics`, `cli`, etc.) | ||
|
||
# Checklist | ||
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. | ||
|
||
- [ ] I have read the developer/contributing docs. | ||
- [ ] I have added tests that prove that my feature works in various situations or tests the bugfix (if appropriate). | ||
- [ ] I have checked that I maintained or improved code coverage. | ||
- [ ] I have checked the benchmarking action to verify that my changes did not adversely affect performance. | ||
- [ ] I have written docstrings and checked that they render correctly in the Read The Docs build (created after the PR is opened). | ||
- [ ] I have updated the general documentation including Metric descriptions and example notebooks if necessary. | ||
|
||
# Further Comments | ||
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
# Proposed Matcher or Metric Addition | ||
- [ ] Matcher | ||
- [ ] Metric | ||
|
||
Briefly describe your new Matcher or Metric class, including links to publication or other source code if relevant. A full description should be included in the documentation. If it resolves a feature request, be sure to link to that issue. | ||
|
||
# Checklist | ||
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code. | ||
|
||
- [ ] I have read the developer/contributing docs. | ||
- [ ] I have added tests that prove that my feature works in various situations. | ||
- [ ] I have checked that I maintained or improved code coverage. | ||
- [ ] I have added benchmarking functions for my change `tests/bench.py`. | ||
- [ ] I have added a page to the documentation with a complete description of my matcher/metric including any references. | ||
- [ ] I have written docstrings and checked that they render correctly in the Read The Docs build (created after the PR is opened). | ||
|
||
# Further Comments | ||
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.