This shows you the differences between two versions of the page.
jvs:fscan:manual:chapter1:opening_behavioral_files_with_functional_images [2011/08/02 13:54] voyvodic |
jvs:fscan:manual:chapter1:opening_behavioral_files_with_functional_images [2023/02/23 18:43] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | == Opening Behavioral Files with Functional Images == | ||
- | |||
- | To see the activation maps on fScan, open the appropriate functional file (or if one has been created, the aligned.wdf file). Once this file has been opened on fScan, make sure that the file accurately corresponds to the run-time log. Look at the first few slices of the functional file. If these are considerably brighter than the later slices, the disdaqs were not properly removed from the file and the appropriate delay will have to be calculated to account for this. If the first few slices do not differ from the later slices, then the disdaqs were properly accounted for and there is no need to make an additional delay when running the behavioural file. | ||
- | |||
- | //Run-time reference command// | ||
- | |||
- | See also [[CmdLine]] | ||
- | |||
- | To run an image of the functional file based on the behavioral files, open a command line window and enter: | ||
- | *-r run1list.txt delay 4.5 -ttest 1 2 | ||
- | |||
- | This command has several components. The **-r** is the [[jvs: | ||
- | |||
- | Finally, [[jvs: | ||