AFNI Message Board

Dear AFNI users-

We are very pleased to announce that the new AFNI Message Board framework is up! Please join us at:

https://discuss.afni.nimh.nih.gov

Existing user accounts have been migrated, so returning users can login by requesting a password reset. New users can create accounts, as well, through a standard account creation process. Please note that these setup emails might initially go to spam folders (esp. for NIH users!), so please check those locations in the beginning.

The current Message Board discussion threads have been migrated to the new framework. The current Message Board will remain visible, but read-only, for a little while.

Sincerely, AFNI HQ

History of AFNI updates  

|
May 20, 2020 11:58AM
Ok, so I realised my stim event files needed to have as many rows as runs with a * to indicate if there were none of that stim class in that run.

With that changed, my DM has slightly (attached). But it still eems as if something is going wrong with interpreting the timings in the runs, for example i get these warnings when running 3dDeconvolve:

++ Auto-catenated input datasets treated as multiple imaging runs
++ Auto-catenated datasets start at:  0 217 434 651
++ Skipping check for initial transients
++ Imaging duration=434.0 s; Automatic polort=3
++ -stim_times using TR=2 s for stimulus timing conversion
++ -stim_times using TR=2 s for any -iresp output datasets
++  [you can alter the -iresp TR via the -TR_times option]
++ ** -stim_times NOTE ** guessing GLOBAL times if 1 time per line; LOCAL otherwise
++ ** GUESSED ** -stim_times 1 using LOCAL times
++ ** GUESSED ** -stim_times 2 using LOCAL times
*+ WARNING: '-stim_times 2' (LOCAL) run#3 has 109 times outside range 0 .. 432 [PSFB syndrome]
 + dataset TR being used is 2 s -- unusable times follow
 434 436 438 440 442 444 446 448 450 452 454 456 458 460 462 464 466 468 470 472 474 476 478 480 482 484 486 488 490 492 494 496 498 500 502 504 506 508 510 512 514 516 518 520 522 524 526 528 530 532 534 536 538 540 542 544 546 548 550 552 554 556 558 560 562 564 566 568 570 572 574 576 578 580 582 584 586 588 590 592 594 596 598 600 602 604 606 608 610 612 614 616 618 620 622 624 626 628 630 632 634 636 638 640 642 644 646 648 650
*+ WARNING: '-stim_times 2' (LOCAL) run#4 has 108 times outside range 0 .. 432 [PSFB syndrome]
 + dataset TR being used is 2 s -- unusable times follow
 652 654 656 658 660 662 664 666 668 670 672 674 676 678 680 682 684 686 688 690 692 694 696 698 700 702 704 706 708 710 712 714 716 718 720 722 724 726 728 730 732 734 736 738 740 742 744 746 748 750 752 754 756 758 760 762 764 766 768 770 772 774 776 778 780 782 784 786 788 790 792 794 796 798 800 802 804 806 808 810 812 814 816 818 820 822 824 826 828 830 832 834 836 838 840 842 844 846 848 850 852 854 856 858 860 862 864 866
*+ WARNING: !! '-stim_times 2' file 'preproc/events_supraliminal.1D' has no good stimulus time values
++ Number of time points: 868 (no censoring)
 + Number of parameters:  29 [25 baseline ; 4 signal]


My TRs are 2 seconds long, and there are 868 in total, which AFNI seems to be reading ok, since it says 'Auto-concatenated datasets start at 0 217 434 651' , but then it says the imaging duration is only 434.0s, which Im assuming is what's causing the issues with the unusable times. Also note the first two runs are entirely one stim type, and the third and fourth are the other.



Edited 2 time(s). Last edit at 05/20/2020 12:03PM by bb2958.
Attachments:
open | download - sub-002_designmatrix.jpg (478.9 KB)
Subject Author Posted

concatenating runs in 3dDeconvolve for PPI analysis Attachments

bb2958 May 20, 2020 11:05AM

Re: concatenating runs in 3dDeconvolve for PPI analysis Attachments

bb2958 May 20, 2020 11:58AM

Re: concatenating runs in 3dDeconvolve for PPI analysis

bb2958 May 20, 2020 12:40PM

Re: concatenating runs in 3dDeconvolve for PPI analysis

rick reynolds May 20, 2020 02:08PM