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

Issues with Matching the 72 reference Tract Folder number to the corresponding HCP Dataset IDs/Subject number #265

Open
AhmedEndrisH opened this issue Feb 16, 2024 · 1 comment

Comments

@AhmedEndrisH
Copy link

Hello Dear Author,
I hope you're doing well. I have encountered an issue of matching HCP datasets and the corresponding reference tract. after I downloaded both I noticed that the subject IDs/folder names of the HCP datasets do not match with the subject IDs/folder names of the tract data.
For example, the tract data folder names include IDs such as '992774', '991267', '987983', '984472', etc., whereas the HCP datasets have IDs like '100206', '100307', '100408', '100610', '101006', and so on.
I am looking to match each of the 105 HCP datasets with the corresponding folder name/ID of each of the 105 72 tract datasets. I would greatly appreciate your guidance on how to match these datasets or if there is any help available that provides this mapping.

Here are the details of my download:
Number of HCP datasets downloaded: 105
Number of reference tract data folders: 105
Source of tract data: https://zenodo.org/records/1477956#.ZBQ5wHZByN

Thank you so much for your time and assistance.

@Gqingkun
Copy link

我也遇到这问题了 不嫌弃的话可以交流交流qq1634501642

@AhmedEndrisH AhmedEndrisH changed the title Need an assistance with Matching the 72 reference Tract Folder number to the corresponding HCP Dataset IDs/Subject number Issues with Matching the 72 reference Tract Folder number to the corresponding HCP Dataset IDs/Subject number Mar 6, 2024
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