GeorgeM

significantly improved by @ana-096 at https://github.com/mikepound/cubes/pull/11

implemented parallelism and threw more cores at the problem, each parallel thread is much slower, but more cores are more cores n=10 benchmark for the parallelism run: PS C:\Users\georg\orig_cubes> python.exe...

> that's fair, depending on how things go (I suspect this should calm down eventually once the obvious ideas have been had and implemented) it might be worth spinning up...

> > > > > > > > > that's fair, depending on how things go (I suspect this should calm down eventually once the obvious ideas have been had...

also yes once you have invited someone as a collaborator you should be able to set their permissions, though i'm used to private repos on github business and am not...

I can confirm I can push, the real question will come when a pull request or issue comes up, I will see what my options are there. Thanks.

> returning the array + dimensions in byte format (as opposed to shifting bits) makes this about 15% or so faster > > ` return polycube.tobytes() + polycube.shape[0].to_bytes(1) + polycube.shape[1].to_bytes(1)...

looks good and is well commented, however your choice of ordering of the axis (first = third) , otherwise I'm happy to merge this asap!

that's real good, is their a repo that people can contribute to ? id be happy to implement p-cube loading in JavaScript. as for improvements, very minor but a "random...

Hi @presseyt sorry for taking so long to get back to you on this, this is interesting and I'm happy to merge if you agree to license this code under...