You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The package has an error and is not able to run since 2020 (as documented in their github issues). Another user proposed a solution, but this was not adapted in the release version.
This package is an implementation based on a tool originally written in R. We, the original authors of the tool, have now translated the tool to Python ourselves. Therefore, we would like to replace the package.
We send emails to two different email addresses we found of the maintainer (sangyushen at gmail.com, notes4hatchin at gmail.com) on September 14 and a second time on September 25. I also reached out on LinkedIn and opened an issue on their github repository. However, we did not get a reaction on any of these channels.
Code of Conduct
I agree to follow the PSF Code of Conduct
The text was updated successfully, but these errors were encountered:
Project to be claimed
FlowSOM
: https://pypi.org/project/FlowSOMYour PyPI username
SofieVG
: https://pypi.org/user/SofieVGReasons for the request
The package has an error and is not able to run since 2020 (as documented in their github issues). Another user proposed a solution, but this was not adapted in the release version.
This package is an implementation based on a tool originally written in R. We, the original authors of the tool, have now translated the tool to Python ourselves. Therefore, we would like to replace the package.
Maintenance or replacement?
Replacement
Source code repositories URLs
Current project: https://github.com/Hatchin/FlowSOM
Replacement project: https://github.com/saeyslab/FlowSOM_Python
Contact and additional research
We send emails to two different email addresses we found of the maintainer (sangyushen at gmail.com, notes4hatchin at gmail.com) on September 14 and a second time on September 25. I also reached out on LinkedIn and opened an issue on their github repository. However, we did not get a reaction on any of these channels.
Code of Conduct
The text was updated successfully, but these errors were encountered: