Skip to content
New issue

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

Determine theoretical bases for different options for --sourceTEs #203

Closed
tsalo opened this issue Jan 26, 2019 · 6 comments
Closed

Determine theoretical bases for different options for --sourceTEs #203

tsalo opened this issue Jan 26, 2019 · 6 comments
Labels
discussion issues that still need to be discussed

Comments

@tsalo
Copy link
Member

tsalo commented Jan 26, 2019

We provide users with the option to perform tedpca and tedica on the optimally combined data (the default), the full z-concatenated data, or a subset of echoes from the full data. Unfortunately, while results may vary significantly based on which option is used, we don't currently have any solid theoretical or even empirical basis for choosing one option over another documented anywhere. This is something I would like to figure out before we do the validation/comparison analysis, in which we will compare results across many different parameters, including different values for --sourceTEs.

Here is what I know so far about sourceTEs:
The first time it's used is in tedpca, so all echoes are used for T2* estimation and optimal combination, as well as to fit dependence models in component selection. When --sourceTEs is set to an index of echoes, tedpca is performed on the concatenated data for just the selected echoes, and returns a dimensionally reduced version of that concatenated data. Then, tedica seems to be performed on the dimensionally reduced concatenated data, rather than on a dimensionally reduced version of the optimally combined data (default) or of the full concatenated data (when --sourceTEs is set to -1). I believe that this means that both PCA and ICA will be performed treating the additional echo data as additional samples, rather than additional time points.

@tsalo tsalo added the discussion issues that still need to be discussed label Jan 26, 2019
@dowdlelt
Copy link
Collaborator

Agreeing with you latter point based on limited testing - it appears to be performing PCA/ICA on the full stack, with the same number of timepoints. I am not sure which is preferable and haven't had a chance to perform extensive testing. Performing the PCA/ICA with 'more data' rather than a reduced (optimally combined) version is intuitively more appealing to me, but then again, each echo can be fairly noisy, which is reduced substantially by combination. Looking forward to empirical testing.

@jbteves
Copy link
Collaborator

jbteves commented May 23, 2019

Is this something explicitly mapped out in the reliability analysis @tsalo ?

@tsalo
Copy link
Member Author

tsalo commented May 25, 2019

@jbteves I'm not planning to test out different sourceTEs options in the reliability analysis. I am planning to do that in the validation analysis, but even then I'm not sure if we'll know what the theoretical basis for each option is based on those results (just what seems to give the best results).

@jbteves
Copy link
Collaborator

jbteves commented May 26, 2019

That's true; sorry for conflating the two. I think it would be great to get @handwerkerd's input on this, and I'm going to ask my PI when he gets back from vacation in a week-ish; I think he'd commented on it when we were talking about it with Peter Bandettini but my memory is very flawed.

@tsalo
Copy link
Member Author

tsalo commented Jul 15, 2019

Would running PCA/ICA on the z-concatenated data bias toward identifying TE-independent signals over TE-dependent ones? Otherwise, it does seem like @dowdlelt's point about the tradeoff between quantity and quality of the data is the only impact sourceTEs would have.

@stale
Copy link

stale bot commented Nov 9, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions to tedana:tada: !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion issues that still need to be discussed
Projects
None yet
Development

No branches or pull requests

3 participants