Hello!
(Version AFNI_23.3.02 'Septimius Severus')
I'm fairly new to AFNI and working to create timing files with the timing tool where duration is not married to onset time. I've read through the timing tool help page but I'm not sure I saw anything that would achieve this. I've tried setting the duration with -stim_dur, thinking that a constant duration would be ignored and not used for modulation, but the output was still Onset:Duration.
Any advice?
Tejiri
Went ahead and ran it both ways
With the -write_timing command preceding 1dMarry -divorce nodm_class.1D there was too many commands.
Then ran as timing_tool.py -fsl_timing_files nodm_class_run*.txt 1dMarry -divorce nodm_class.1D
timing_tool.py -fsl_timing_files nodm_iti_run*.txt 1dMarry -divorce nodm_iti.1D
Only mini concern was that I got this message for each epoch/participant:
++ No filename given to get divorce results ==> using 'nodm_class.1D'
Tells me that afni is smarter than I am lol, but I don't know where in the input I was supposed to add the filename so it wouldn't have to search for it. Thanks for all the help!
I was typing this up as you sent the clarification, is it ok that I used the -write_as_married bit? I don't think we necessarily needed to change the duration time
The -write_as_married option forces output to be married. In your case, it should not be needed. It is too bad that I did not make that a yes/no option to force married or not.
The warning about "divorce results" is just because there isn't a second parameter given as an output file pattern, and so it uses the input one. Please feel free to add a divorce output name, such as nodm_divorce.
rick
1 Like
The
National Institute of Mental Health (NIMH) is part of the National Institutes of
Health (NIH), a component of the U.S. Department of Health and Human
Services.