You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just tested this App and it finished successfully!
One issue that I ran into was that I didn't know how to set the tract IDs. The App's tractID_list looked like I shoud specify this via range like "32-33" as shown here
which resulted in an error. I had to update to something like 32, 33, 38, 39 instead. I think the description should be updated.
Also, would it be possible/better to classify all known tracts if the user doesn't specify any tract IDs?
The text was updated successfully, but these errors were encountered:
I have updated the app description, now it should be clearer.
Up to now, it won't be possible to segment all known tracts since the algorithm is not meant to perform whole brain segmentation. Up to now, the original algorithm can segment 28 different kind of bundles, and the version implemented in branch 1.0 allows the user to select 10 of them. The next release I am working on will allow the user to select all the kind of bundles we performed the training with.
I think the simplest thing to do is to just set the default value for tractID_list field to have all supported ID, and let user trim the IDs that they don't want?
I think a lot of users just want to demo the App before they invest their time, so the easier it is to get something running, more likely that they will learn how to use it.
I just tested this App and it finished successfully!
One issue that I ran into was that I didn't know how to set the tract IDs. The App's tractID_list looked like I shoud specify this via range like "32-33" as shown here
which resulted in an error. I had to update to something like
32, 33, 38, 39
instead. I think the description should be updated.Also, would it be possible/better to classify all known tracts if the user doesn't specify any tract IDs?
The text was updated successfully, but these errors were encountered: