Matthew Jennings
Matthew Jennings
See attached DICOM RT Plan file and associated error. Error complains oabout tag (300A,0090), the "Beam Dose" attribute. [RT Plan error.zip](https://github.com/bastula/dicompyler/files/2722744/RT.Plan.error.zip)
> Can we have this elsewhere within the documentation, and simply link to it within the readme? _Originally posted by @SimonBiggs in https://github.com/pymedphys/pymedphys/pull/1701#discussion_r937388583_
Hi @nlambriICH and @SimonBiggs, I've just happened to notice that the example used to demonstrate the speed-up potential of using `random-subset` is not very compelling. I.e., for a 10% sample...
Current status: ~~PRE-REVIEW~~ **REVIEW** See [#4470](https://github.com/openjournals/joss-reviews/issues/4470)
Hi all, I think the docs could really benefit from some simplification. A while ago, a decision was made to embrace a framework that included _background_, _tutorials_, _how-to-guides_ and _reference_....
Is this a worthwhile endeavour? Any idea on how much the current anonymiser is used and/or how much interest there is in a python-based anonymiser that is nicely integrable into...
A huge gap at the moment is documentation on how to be a contributor, and also how to be a maintainer, how to review, how to do a release, as...
With reference to [this discussion](https://github.com/pymedphys/pymedphys/pull/1360#discussion_r566496543): - When a PR only involves "site-specific" or "prototyping" code: no review needed, and best not to even flag someone. - When a PR involves...
From https://github.com/openjournals/joss-reviews/issues/4555#issuecomment-1247632276: > @Matthew-Jennings, after fixing the above issue, could you: > > * [ ] Make a tagged release of your software, and list the version tag of the...