I guess you know this Doug, but make sure you management knows that we are willing to help people here for free because we think this open discussion and troubleshooting helps make the code better and it creates an educational resource for the community. If your project is not open then we just have to say sorry we can’t really help and they really need to hire consultants to work on closed projects.
OK, that’s a great point that I was not clear on. Thanks for making this really clear. I’ll let them know.
Also, I sincerely apologize for not fully understanding this previously.
FYI: Slicer displays this PET series the same as my module…
What do I need to do to display it here? Is there a fix in your latest slicer nightly build?
Thanks.
The release that you tried is almost a year old! Please try the latest Slicer Preview Release. Default color table selection for PET/CT studies has been improved recently.
Yes, this is version 4.11. But the same is happening in 4.13
Here’s an MRI…
Are we the only organization having these issues? Is this something that you would be interested in investigating, Or are we stuck with SlicerQREADS working only with CT? If you’re interested, I can send you the DICOM files.
Thanks
This is the first I’ve seen this, and I’ve seen a whole lot of dicom files in Slicer.
Yes, if you can share these for testing that would help. Can they be made part of a public testing data set? This could help ensure the problem doesn’t crop up again in the future.
Ok, I’ll ask or anonymize. If folks want this fixed, we need to know the cause. This seems to be happening for all of our non-CT data (MR and PET); a major blow for me. This is our test data, but I’ll make extra sure it’s public sharable. I should have them for you by tomorrow on Drop Box.
Thanks
This is very interesting, I don’t recall ever seeing this issue either (and there have been no user complaints about it). It should be trivial to fix it if we get a sample image that reproduces it.
GREAT!!! Looks like some kind of overflow where the pixel values go high they set the sign bit and go negative. I don’t know, but I’ll get it to you. Thanks.
@pieper @lassoan : Interesting hint: It displays fine in QREADS and another DICOM apps. But Photoshop displays just like Slicer.
I am working on getting you the data now.
Thanks
1 Like
Hello @lassoan @jcfr @pieper @jamesobutler @mau_igna_06
QREADS 3D MPR (SlicerQREADS) has been deployed for about a month, and thanks to you, it is rock solid. I think the timing is right for me to ask the powers that be if I can open source it. I will start asking and hopefully I can get it done. Thank you guys so so much for all of the great help; I am so grateful to you. I will be retiring on December 24th, so I’ll be out of here. I’ll keep you informed of how the politics play out with open-sourcing SlicerQREADS. I’ll try my best.
Thanks
3 Likes
That’s great to hear, congrats @spycolyf on getting this accomplished and on your upcoming retirement - hope you have fun!
Ditto. And thanks for your patience and willingness to consider an alternative approach 
the timing is right for me to ask the powers that be if I can open source it.
Sounds great. When it makes sense, consider reaching out so that we consolidate with the version hosted at https://github.com/KitwareMedical/SlicerQReads
Very happy to hear that SlicerQReads project is going well.
Have a good time in your future retirement.
This is awesome news! …and it may be a perfect time to add a few sentences to the Success stories category.
Congratulations for your retirement and please don’t forget to introduce us to you successor(s).
OK @lassoan , I will add to the Success Stories. Thanks for reminding me. 
1 Like
Hello all,
I’m experiencing sometimes the SlicerQREADS module does not display the images. I think it might be the DCM files folder path length. Also, the log files indicate that it could not find the folder. Could you tell me what the maximum length is? Thanks.
By default, that would be 256 characters. See Maximum Path Length Limitation - Win32 apps | Microsoft Learn
Does this also apply to Slicer’s DICOM database? Does it have it’s own path length restrictions? I know the Slicer installation has issues with path lengths. So I was wondering about other Slicer functions as well.
Thanks