-
Notifications
You must be signed in to change notification settings - Fork 21
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
Use points instead of diameters for MorphIO conversion #47
Conversation
May I ask why it is preferable to copy a 2D dataset instead of a 1D to get its length? |
Which copy? The points or diameters are not copied, we just use them to know the total number of points. |
lol: ERROR: Could not build wheels for morphio, which is required to install pyproject.toml-based projects |
You will need to remove python3.6 as morphio does not create wheels for it after support for python3.6 was dropped. |
Data copied from the c++ to the python side. The only reason I used diameters is that they are 1D so would result in a smaller copy. That said, it doesn't really matter because the datasets are rather small. |
Ah ok, thanks. |
Yeah I think we can use the points for now, and when BlueBrain/MorphIO#357 will be solved we will use it. |
@eleftherioszisis do you have the permissions to discard the py36 required job? |
Hello there, |
@eleftherioszisis should we merge this one and use |
Sorry for responding late. |
6f51e91
to
2f9fb94
Compare
#45 was merged in the wrong branch, this PR just cherry-picks the commit to merge it on the master branch.