Ilya Belevich

All I'd like to do is select features inside the image, without the centre of the brush tool being within the image. ok, now I finally got the point. I need to check how easy it can be done, but I agree, it it nice thing to have. Will the new boundary dimensions apply when I reload a model? or do I need to re-load the image, add a frame with dX/dY, then load the model? The only requirement is that physical sizes (width/height/depth) of the image dataset and models should match. When you add frame,...

thank you for clarification. I am specifically referring to case 1. by default it is not possible. The reason is that the model takes the same physical size (in pixels) as the underlying data image, having models of different from the image size is technically possible, but it requires additional logic. Also, normally we can't model the structures that we can't see. There is, however, a solution to that problem. What you need to do is to extend the width/height of your dataset to the desired value....

Hi Ben, the clipping of the brush tool occurs in two situations: 1. when the brush is at the physical edge of the dataset (Pixel Info: has negative values, as in case1.jpg) 2. when the brush is at the edge of the viewing window(for example when zoomed-in, case2.jpg) to make sure that I understand the problem correctly, which of these cases you are referring?

great! I bumped myself few times into the similar issues, so those "obvious" ones are just obvious for me :]

Hello Julien, there may be multiple reasons for that, here the two most obvious ones: 1. the transparency slider for the selection later is set to complete transparency. Please try to move it (it is in the View settings panel at the bottom) 2. Another reason could be due to the Disable Selection combo box is set to "yes" in the preferences window: http://mib.helsinki.fi/help/main2/ug_gui_menu_file_preferences.html Let me know if it does not help. Also, I encourage you to use https://forum.image.sc/...

Hello Ben, thank you for the datasets! I was able to load the images (tif stack) and the classifier. In my case the prediction worked quite well. I have not noticed any issues (please note that I was using the Matlab version of MIB). However, I noticed a possible problem with your *.fm files. The FM-files contain variable features used by the classifier for the prediction; these files should roughly be the same size. In my case, all fm-files were about 448Mb. The files that you've send me were 452...

Hello Ben, I just quickly tested on a small stack and there were no problems. Would you be able to send me (http://www.biocenter.helsinki.fi/~ibelev/) the first part of that dataset and the model used for training, I can test it then? Best regards, Ilya On Sat, Jan 19, 2019 at 10:47 AM Ben Padman bpadman@users.sourceforge.net wrote: [tickets:#17] https://sourceforge.net/p/im-browser/tickets/17/ Erronious activity on "Membrane Detection" classifier tool* Status: New Labels: membrane detection stall...

Loading 16bit images as Amira files into MIB error