# SlicerQR Development

**URL:** <https://discourse.slicer.org/t/slicerqr-development/15954>\
**Category:** Development\
**Tags:** registration, build, segmentation, dicom, python\
**Created:** [February 11, 2021, 3:59pm UTC](https://discourse.slicer.org/t/slicerqr-development/15954 "2021-02-11T15:59:22Z")\
**Posts on this page:** 1\
**Showing post:** 86

<div class="post-metadata">

**Author:** ![spycolyf](https://avatars.discourse-cdn.com/v4/letter/s/f17d59/32.png) [@spycolyf](https://discourse.slicer.org/u/spycolyf)\
**Post date:** [March 8, 2021, 4:40pm UTC](https://discourse.slicer.org/t/slicerqr-development/15954/86 "2021-03-08T16:40:08Z")

</div>

@lassoan @jcfr @pieper,

Do you think this is something that can be corrected this week? The Med school needs to use this in new student orientation on March 30th, and there is a lot of implementation and testing work that I need to do with SlicerQREADS deployment. I plan on implementing a quick and dirty on-demand SlicerQREADS extension deployment for the students in the March 30th orientation. But it is critical that the orientation is not worse than the Sankhesh’s FourPaneViewer used for the past 2 years.

---

_[View the full topic](https://discourse.slicer.org/t/slicerqr-development/15954)._
