tedana
tedana copied to clipboard
Dependency Changing Causes Different Processing Results
Summary
#517 was introduced because of a new release of one of our dependencies. Despite searching the changelog and playing with the code, we have not isolated the cause of #517. We should track down what it is eventually.
Additional Detail
Next Steps
From the January developer's call: We wanted to loop in @smoia who observed something related to automatic dependency checking that may be relevant for this issue. If you have anything useful to add here, do so
While contributing to all-contributors for a little, I saw that they have a bot that keep track of their dependencies. They use npm, so it's not for us, however I saw this other bot: https://requires.io/ that does the same for python packages. I requested integration in ME-ICA just not to forget at a later moment.