We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The Readmes and example seem to make it clear that running the gMSHBM steps are optional and only necessary for gMSHBM.
I am running cMSHBM and getting an error in the estimate group priors step that the "gradient_list" files are not found:
Error using readtable (line 198) Unable to open file '<project_dir>/estimate_group_priors/gradient_list/training_set/gradient_list_lh.txt'. Error in CBIG_ArealMSHBM_cMSHBM_estimate_group_priors_parent>fetch_data (line 749) lh_gradient_name = table2cell(readtable(lh_data_gradient, 'Delimiter', ' ', 'ReadVariableNames', false)); Error in CBIG_ArealMSHBM_cMSHBM_estimate_group_priors_parent (line 192) fetch_data(project_dir, setting_params.num_session, setting_params.num_sub, setting_params.mesh, tmp_dir);
i think this could be easily reproduced by following the steps using new study data (rather than the example data including pre-computed files)
THanks!
The text was updated successfully, but these errors were encountered:
@annchenknodt Yes we have this bug in our previous releases. We have resolved the issue in recent releases.
Sorry, something went wrong.
No branches or pull requests
Expected situation
The Readmes and example seem to make it clear that running the gMSHBM steps are optional and only necessary for gMSHBM.
Actual situation
I am running cMSHBM and getting an error in the estimate group priors step that the "gradient_list" files are not found:
Steps to reproduce the issue (optional)
i think this could be easily reproduced by following the steps using new study data (rather than the example data including pre-computed files)
THanks!
The text was updated successfully, but these errors were encountered: