-
Notifications
You must be signed in to change notification settings - Fork 28
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
Fix error when reading pts file with frame_list, frame_start_index (was PR #67) #68
Conversation
Add tests for frame_start_index and frame_shift
Codecov ReportBase: 83.52% // Head: 84.11% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #68 +/- ##
==========================================
+ Coverage 83.52% 84.11% +0.58%
==========================================
Files 49 56 +7
Lines 8390 8411 +21
Branches 1893 1890 -3
==========================================
+ Hits 7008 7075 +67
+ Misses 909 877 -32
+ Partials 473 459 -14
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Continuation of #67 |
512628c
to
a0d5b00
Compare
a0d5b00
to
c3bbad5
Compare
2806142
to
8d316d4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks good.
Do you want to add a release note mentioning the following?
- Bugfix : error when reading JEOL .pts file with un-ordered frame list
- Bugfix : error when length of frame_start_index is smaller than sweep count
Thank you. By the way, if it is needed, should I write issue before adding upcoming_changes? |
Based on my experience, release notes are useful even for the most minor changes/bug fix, as it is only useful for users but also for ourselves in the future and developers of other libraries. To add a release note, you just need to add a file in the |
Ok, I put 68.bugfix.rst into upcoming_change directory |
ad1d50a
to
d222c57
Compare
Description of the change
Progress of the PR
upcoming_changes
folder (seeupcoming_changes/README.rst
),readthedocs
doc build of this PR (link in github checks)Minimal example of the bug fix or the new feature