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

Add PiecewiseSRM to the package #49

Open
2 tasks
thomasbazeille opened this issue Sep 24, 2021 · 10 comments
Open
2 tasks

Add PiecewiseSRM to the package #49

thomasbazeille opened this issue Sep 24, 2021 · 10 comments

Comments

@thomasbazeille
Copy link
Collaborator

Goal : Piecewise SRM

Main questions :

  • How to handle IdentifiableSRM dependency ? import a copy of [Hugo's package] code (https://github.com/hugorichard/FastSRM) (that should maybe become the upstream then) or depend on the package
  • Should we change the API ? As of now it seems hard to match it to other fmralign objects more than it already is

Other than that, main depencies are compatible and fmralign helpers are already used. A few functions are duplicated to handle the list input (instead of pairwise input usually) such as generate_X_is, fit_one_piece, fit_one_parcellation. We could either refactor their counterpart in fmralign, or keep the duplication in order to keep a clearer codebase.

@bthirion
Copy link
Contributor

I'd rather import it, but you seem to be reluctant to that, and I'm not sure why ?
API change: to be discussed with @hugo
Deduplication would be great. Maybe aligning the FastSRM to the cogalign one seems a right option, as you ahve worked more on the API I guess.

@thomasbazeille
Copy link
Collaborator Author

I'd rather import it, but you seem to be reluctant to that, and I'm not sure why ?

I guess it is mostly a question of future maintenance and involvement. Having a strong dependency on a personal package seems like something that's likely to make things break if it is not maintained and bringing everything in the same place also means centralizing future maintenance but I don't have a strong opinion.

@emdupre
Copy link
Collaborator

emdupre commented Sep 24, 2021

Personal +1 that a central location might decentralize maintenance, but @hugorichard 's opinion is probably the most pressing, here !

@thomasbazeille
Copy link
Collaborator Author

thomasbazeille commented Sep 25, 2021

Maybe my bad wording in the first place introduced a misunderstanding. If by

I'd rather import it, but you seem to be reluctant to that, and I'm not sure why ?

you mean we should have a copy of one SRM inside fmralign, then I think we all agree.

@hugorichard
Copy link

I would rather import it. FastSRM is already used in Multiview ICA. Maybe I could remove this dependency though. I need to think about it.

@bthirion
Copy link
Contributor

+1 for import (sorry if I was unclear)

@thomasbazeille
Copy link
Collaborator Author

@hugorichard did you have any time to think about this ?

@hugorichard
Copy link

Should I include our implementation here as a PR ?

@bthirion
Copy link
Contributor

bthirion commented Nov 7, 2021

Yes, please add a PR that imports FastSRM properly. Thx !

@hugorichard
Copy link

@thomasbazeille @bthirion I have added a PR #50 . CircleCI seem to be broken (the tests do not even run).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants