Skip to content
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

Allow other VR Types for Date Jitter #182

Merged
merged 9 commits into from
Jul 7, 2021
Merged

Conversation

wetzelj
Copy link
Contributor

@wetzelj wetzelj commented Jul 7, 2021

Description

Related issues: #175, #180, #181

Pull requests #180 and #181 were originally based on master before #178 had been merged into master. This pull request merges the latest changes in master with the changes necessary for #175, #180, #181.

The changes that had previously been implemented for #178 were revised with the implementation of changes for #175.

This pull request will supersede #180 and #181. Both of the prior PRs can simply be closed.

Checklist

  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings
  • My code follows the style guidelines of this project

Open questions

Questions that require more discussion or to be addressed in future development:

vsoch and others added 9 commits June 29, 2021 19:53
Signed-off-by: vsoch <[email protected]>
Adjusted ctbrain1.dcm file to contain non-DA/DT date field, added test method.
When implementing unit test for jittering on values lists, identified a bug which prevented private fields from being jittered. Modified jitter_timestamp to simply return the new value of the field and use replace_field() to actually perform the dicom update.
Fixing formatting for PR.
Correcting formatting for PR.
@vsoch
Copy link
Member

vsoch commented Jul 7, 2021

Thank you @wetzelj ! Let's merge and get this release underway. Sorry for the git-fu!

@vsoch vsoch merged commit f177634 into pydicom:master Jul 7, 2021
@wetzelj wetzelj deleted the other-vr-jitter branch November 21, 2022 16:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants