jgostick

Also, `None` would be an option. So `[100, None, 100]` would be shrunk to `[100, 100]`.

The best way to do this would be to create a helper method in the `utils` module called `_parse_shape` which contains all the logic. Each generator function would then call...

Additional thoughts: - `porosimetry` should be moved to the `simulations` module, since that's what it is. - So the logic that is currently in `porosimetry` should be moved into the...

That function is in need of some fixes. I think there are already some bug reports on the issue tracker so I'll affect this to the list.

We've been using it to do operations in chunks, like this: ``` python import numpy as np from dask import delayed, compute # This decorator tells dask to delay computation...

Maybe this could be done as a post process? I'm thinking you could either find the steps in walker's path where it hit a wall, then apply a probability of...

Indeed, 1000 time steps won't even give you valid results...should be 100,000 or more right?

seems like an 'int' overflow issue. That number is exactly (2^32)/2.

Sorry, I wrote my initial point quickly just to start the thread...let me explain: If we could get each walking moving in a random direction, and keep it moving in...

It might be a bug. The sphere touches the edge of the image image, which is correct, so perhaps I need to check the logic for the clearance. Thanks for...