-
Notifications
You must be signed in to change notification settings - Fork 11
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
Error running rna scope mouse function @ line 56 #1
Comments
If this is using the sample mouse data, uncomment the Line#20 in rnascope_mouse and comment Line#20 if using real data as mentioned in the Mouse vignette (https://github.com/LieberInstitute/dotdotdot/blob/master/docs/mouse_vignette.md). Line#20 %out{1,2}.Dyes = {'Cy5','DsRed','EGFP','DAPI'}; %dye names are wiped out when cropped and the channel names have no information |
Hi,
Could I ask for a bit of support with the dotdotdot? To preface, I am extremely new to Matlab-I normally utilize in house scripts- so I apologize if these are very basic errors and questions. I am running into an issue optimizing the code for my own data- a lab-mate who is more familiar with Matlab believes the issue is: 'it is not able to detect any nuclei of my images, I think because of the radius of the cells being off since we are using different files than the example images and sizes are off’
I am using .nd2 files and not sure how to optimize it best to my images. My lab-mate is getting these errors after trying to optimize it of the two attached screen shots.
I am also having an issue using the final_table.
Do you have troubleshoot support or instructions posted anywhere else?
Thank you for your time and help,
Julia Schmidt
… On Jun 11, 2020, at 3:38 PM, Madhavi Tippani ***@***.***> wrote:
If this is using the sample mouse data, uncomment the Line#20 in rnascope_mouse and comment Line#20 if using real data as mentioned in the Mouse vignette (https://github.com/LieberInstitute/dotdotdot/blob/master/docs/mouse_vignette.md <https://github.com/LieberInstitute/dotdotdot/blob/master/docs/mouse_vignette.md>).
Line#20 %out{1,2}.Dyes = {'Cy5','DsRed','EGFP','DAPI'}; %dye names are wiped out when cropped and the channel names have no information
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AP5TFDOKEAPFXZYEAECNWG3RWFFGDANCNFSM4N3SQFMA>.
|
Hi Julia, I am also new to Matlab and have been trying to run the dotdotdot (mouse version) but without success. I was wondering whether you were able to run it afterwards and if you were able to get any help or troubleshoot support. Yoser |
Hi Yoser,
It’s not great news, but unfortunately we never got dotdotdot to work for us and never got a response to our emails about trouble shooting either. We have pretty much decided to stop spending time trying to get it to work and instead I am writing my own in-lab code on python trying to analyze our vole data in a similar fashion.
Thanks,
Julia
… On Jul 22, 2020, at 10:47 PM, yoser-alrawi ***@***.***> wrote:
Hi Julia,
I am also new to Matlab and have been trying to run the dotdotdot (mouse version) but without success. I was wondering whether you were able to run it afterwards and if you were able to get any help or troubleshoot support.
Yoser
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AP5TFDLJKFOGWHSWHUYEKPDR466GNANCNFSM4N3SQFMA>.
|
Sorry, our main developer has been on parental leave right as these issues were posted. We will have someone else look into these two issues. Note that the June 19th issue had no screenshots attached. |
Hi,
Here is a screen shot of the June 19th issue email with the screenshots as they were attached.
… On Jul 23, 2020, at 9:13 AM, Andrew Jaffe ***@***.***> wrote:
Sorry, our main developer has been on parental leave right as these issues were posted. We will have someone else look into these two issues. Note that the June 19th issue had no screenshots attached.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AP5TFDOPFNIY2S5W75ZGPBTR5BHSLANCNFSM4N3SQFMA>.
|
The reason (in my case) that the pipeline produces the error at line 56 is because the bioformats library doesn't read in dye names properly. I've tried using .nd2 and .oib formats. For both of these image types, the OME metadata is read in with dye names as empty char vectors. The pipeline should throw an error if dye names come up empty, but instead it breaks at line 56. |
Hi Julia, |
Hi Yoser,
Thanks so much for that input! I’ll give that a try tomorrow. Just out of curiosity where / what lab are you working from? I’m working for the Donaldson Lab at University of Colorado Boulder :)
Thanks,
Julia
… On Aug 7, 2020, at 9:42 AM, yoser-alrawi ***@***.***> wrote:
Hi Julia,
I was getting the same error and when I uncommented line 20 (removed the % signs at the beginning and kept everything else as it it) it worked.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AP5TFDM5VSOKWUT2JKNUW63R7QOE5ANCNFSM4N3SQFMA>.
|
Hi Julia, You are welcome! :) I am in the Gamble lab at the University of Alabama at Birmingham. Our research focus is on the circadian rhythm. Unfortunately, the images I am trying to analyze are in a different format from the sample images provided here. So, when I tried my images using the toolbox it was having an error reading them. The images are in .tiff (I can also get .jpeg images) and the raw ones are in .gci, obtained from the Keyence microscope. I tried the human_tiff command line but got an error initially. After I thought I fixed the error, I got an empty excel sheet! So, I am still struggling with the toolbox and I am hoping someone could help us with our issues. Best regards, |
Hi Yoser, I am not the developer or author, but I have been using their fantastic toolbox extensively. .tiff should work fine; I would never use .jpeg due to image quality loss during compression. You will have to use .tiff as your format because the "bio-formats" within the toolbox does not support .gci. Can you please post screenshots and syntax/code of the errors you are getting? Perhaps even a sample .tif of yours that we can try to get working? I prefer working via syntax/code as my version of Matlab is working off of a server, so I have always have used Matlab without a GUI. Best, |
I tried sending the image folder as zip but it couldn't send as it was over 80MB so I compressed one set of images and here it is: |
Hi Yoser, I think I found your problem. Which I think is also related to @ohmstead [issue (https://github.com//issues/6#issue-669063483) I can go into more detail if you need (at least as far as I understand it) and @andrewejaffe; please correct me if I am wrong! I was able to get your "example" image to work under the following conditions:
If it' s still is not working maybe try: I hope this helps!! Warm regards, |
Hi Josh, Thank you for the comprehensive reply! It was very helpful. I tried following the steps and even tried the last two but I kept getting an error in line 42 with and without altering the last 2 steps. Also, from what you have explained I understood that the way you provided will allow me to analyze the image as a 2D. Is that correct? I wan't aware that the format of the tif images was different as the images were taken as z-stacks from the Keyence microscope. There are 24 z-stack, the one I sent were the images of the first z-stack. Is there a way to extract metadata from those images so we can analyze them as 3D. Thanks again for your help! I really appreciate it. Kind regards, |
Hi Yoser, I remember having this issuer early on, but it had been so long I forgot! I think because of this issue early on, I don't run my .m scripts as a "function!" I cannot tell you why this works, and I don't have time to figure it out, but the changes below worked for me using a new unedited copy of "rnascope_mouse.m" ... REPLACE LINES 1-4, 20:
WITH
If you use a new unedited copy, remember to add in the other changes to detect nuclei. Then to run, for me without a GUI, I just type into the prompt (>>): rnascope_mouse This means you have to edit the script per image file! Best, |
Thank you Josh! I really appreciate your help. I will try everything you mentioned once more from start over the weekend and add those steps and see what I get. Best regards, |
I am getting an error running the rnascope_mouse function at line 56. Another labmate of mine downloaded this 3 weeks ago and is not having this error. I noticed the latest commit was 6 days ago- has something changed with the code or do you have suggestions on why I am receiving this error when running it? The error says the statement is incomplete.
The text was updated successfully, but these errors were encountered: