-
Notifications
You must be signed in to change notification settings - Fork 28
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
code for generating simulated data #66
Comments
Working on this, will update here. |
Thanks a lot! Looking forward. By the way, we noticed that the roi type must be polygon. |
The simulation code is now available in our SimCalc repository. @zcq0730 Sorry for the delay, hopefully it is still useful! Any bugs and oddities you might run into are best asked in the SimCalc repository itself. |
Thanks a lot! Definitely, it will be very useful! |
Sorry for the delayed reply. Thank you very much for opening an issue on this! Add the selected ROI which is created with this tool into ROI manager, from ROI manager click “More –> LIST” a pop-up window “Overlay Elements” will appear. One could from there find out the detailed properties of created ROI. As you would see, the created ROI type with brush selection tool is Composite type. Currently, FISSA could load these Composite type of ROIs and treat them as Polygon type. However, one could find out for some reason selected ROIs are recognized incorrectly. The selected ROIs are expanded to squared shape ROIs and passed to FISSA for further calculations (which would definitely compromise FISSA´s accuracy). We have wrote an ImageJ Marco to rapidly convert all such selected Composite ROIs into Polygon ROIs (I don´t know if it could be easily done in python, I put the imageJ java code here for your convenience if you would like to implement this in python): nROIs = roiManager("count"); Above code was inspired by the following Ref: Thanks a lot both for your help and interest in this issue! |
Would you please include the code for generating simulated data into the fissa toolbox?
Thanks a lot!
The text was updated successfully, but these errors were encountered: