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
Some users are interested in getting the anatomical information from the ROIs and not just passing the DLMUSE output to downstream ML tasks. To enable quick use of the DLMUSE tools, it would be helpful for them to be able to access this information directly from the CLI without needing to find this file and Ctrl-F until they get what they want.
We already have the shared dictionary at https://github.com/CBICA/NiChart_DLMUSE/blob/main/NiChart_DLMUSE/shared/dicts/MUSE_ROI_complete_list.json which contains the ROI information. I suggest that we simply add a command line flag, something like "--roi-lookup 701" that finds the corresponding ROI information and renders it. This could just be the anatomical name, but it could also show the anatomical names of any ROIs it consists of too. If this flag is passed, all other input should probably be ignored.
The text was updated successfully, but these errors were encountered:
Some users are interested in getting the anatomical information from the ROIs and not just passing the DLMUSE output to downstream ML tasks. To enable quick use of the DLMUSE tools, it would be helpful for them to be able to access this information directly from the CLI without needing to find this file and Ctrl-F until they get what they want.
We already have the shared dictionary at https://github.com/CBICA/NiChart_DLMUSE/blob/main/NiChart_DLMUSE/shared/dicts/MUSE_ROI_complete_list.json which contains the ROI information. I suggest that we simply add a command line flag, something like "--roi-lookup 701" that finds the corresponding ROI information and renders it. This could just be the anatomical name, but it could also show the anatomical names of any ROIs it consists of too. If this flag is passed, all other input should probably be ignored.
The text was updated successfully, but these errors were encountered: