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

Wrong Contours #39

Open
marcoistasy opened this issue Jun 11, 2020 · 3 comments
Open

Wrong Contours #39

marcoistasy opened this issue Jun 11, 2020 · 3 comments

Comments

@marcoistasy
Copy link

I am running into an issue with this library: the code is running to completion without any up errors and outputting the three files (frame_all.mat, reg.mat, and processed.mat). However, when I take a look at the identified contours, they don't match on to any neurones; it almost seems to be that the programme is selecting the ROIs at random.

I have tried tweaking the available parameters, particularly se to no avail; with any iteration, the code runs to completion but outputs the wrong contours. Are there any other parameters, whether high- or low-level, that I should change to receive better contours?

I understand that this is a localised issue and will most likely require that I share the files I am analysing and I am happy to do that.

@JinghaoLu
Copy link
Owner

@marcoistasy Pretty strange. Yes I would like to take a look of the video.

@marcoistasy
Copy link
Author

@marcoistasy Pretty strange. Yes I would like to take a look of the video.

Thank you for your quick response! How should I share it with you?

@JinghaoLu
Copy link
Owner

@marcoistasy to min1pipe2018@gmail.com, like what you did last time. Thanks!

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

No branches or pull requests

2 participants