Differences between revisions 7 and 8
Revision 7 as of 11:11:22 30-04-2015
Size: 2472
Comment:
Revision 8 as of 09:13:54 29-10-2015
Size: 3248
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
== When I run FIX, I obtain the following output: “No valid labelling file specified” What does it mean? ==
 FIX doesn’t find the classification file with the list of components to be removed, so the error could be either in the features extraction or in the classification.
To see which is the problem have a look at the following log files:
 * <subject.ica>/fix/logMatlab.txt
(this should show errors in Matlab part, i.e. features extraction)
== When I run FIX, I obtain the following output: “No valid labelling file specified”. What does it mean? ==
 . FIX doesn’t find the classification file with the list of components to be removed, so the error could be either in the features extraction or in the classification. To see which is the problem have a look at the following log files:
 * <subject.ica>/fix/logMatlab.txt (this should show errors in Matlab part, i.e. features extraction)
Line 9: Line 7:
 * <subject.ica>/.fix_2b_predict.log
(those are log file in general for the whole routine)
You’ll probably find errors related to Matlab or R, so you might need to check your settings.sh file following the setup instructions described in the FIX README file
 * <subject.ica>/.fix_2b_predict.log (those are log file in general for the whole routine) You’ll probably find errors related to Matlab or R, so you might need to check your settings.sh file following the setup instructions described in the FIX README file
Line 14: Line 10:
 FIX is more likely to work better with the training dataset that is most similar to your data, both in terms of acquisition parameters (TR and resolution) and preprocessing steps applied.
Regarding the threshold to use, you can start with the “default” 20 and increase or decrease it according to FIX performance (i.e. visual check of the components' classification contained in the file fix4melview_TRAIN_thr.txt).
For example, if it is very important to you that almost no good components are removed, and hence you would prefer to leave in the data a larger number of bad components, then use a low threshold. If you want to remove more noise, use a higher threshold.
 . FIX is more likely to work better with the training dataset that is most similar to your data, both in terms of acquisition parameters (TR and resolution) and preprocessing steps applied. Regarding the threshold to use, you can start with the “default” 20 and increase or decrease it according to FIX performance (i.e. visual check of the components' classification contained in the file fix4melview_TRAIN_thr.txt). For example, if it is very important to you that almost no good components are removed, and hence you would prefer to leave in the data a larger number of bad components, then use a low threshold. If you want to remove more noise, use a higher threshold.
Line 19: Line 13:
 FIX output is basically the (automated) equivalent of the output of fsl_regfilt, so you don’t need to run both:  . FIX output is basically the (automated) equivalent of the output of fsl_regfilt, so you don’t need to run both:
Line 21: Line 15:
 * FIX automatically classifies the artefactual components and regress their contribution out of the data —> cleaned data
(the equivalent to fsl_regfilt would be using FIX with the –A option – see user guide)
To check that FIX is removing the artifactual components correctly (i.e. it is doing what you would do before running fsl_regfilt) you can check the classification done by FIX in the fix4melview….txt file and adjust the training dataset and threshold you are using as appropriate.
 * FIX automatically classifies the artefactual components and regress their contribution out of the data —> cleaned data (the equivalent to fsl_regfilt would be using FIX with the –A option – see user guide) To check that FIX is removing the artifactual components correctly (i.e. it is doing what you would do before running fsl_regfilt) you can check the classification done by FIX in the fix4melview….txt file and adjust the training dataset and threshold you are using as appropriate.
Line 26: Line 18:
 Yes, although you will probably need to create a study-specific training dataset  . Yes, although you will probably need to create a study-specific training dataset

== When I run FIX to create a new training file (-t), the output folder is created, but no .RData is produced at the end, with no explicit error message. What does it mean? ==
 . Check the content of the folllowing hidden files within the output directory created:
 .
 * .fixlist --> should contain the list of subjects included in the training dataset (to check if they've been all loaded/recognised properly)
 * .Rlog1 --> contains errors from R about the generation of the .RData file
 . Also, make sure that the .txt files (hand_labels_noise.txt) are in the correct format: the last line should contain the list of the components only, within square brackets and comma separated, and there should be an empty line at the end (i.e. hit return after writing the list).
 .

When I run FIX, I obtain the following output: “No valid labelling file specified”. What does it mean?

How do I choose the best training dataset (among the existing ones) and/or threshold for my data?

What is the difference between fsl_regfilt and FIX?

Can I use FIX to clean task fMRI data?

When I run FIX to create a new training file (-t), the output folder is created, but no .RData is produced at the end, with no explicit error message. What does it mean?

 

FIX/FAQ (last edited 05:49:35 29-06-2018 by LudovicaGriffanti)