Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Initial Dask trimesh support #696

Merged
merged 3 commits into from
Feb 7, 2019
Merged

Initial Dask trimesh support #696

merged 3 commits into from
Feb 7, 2019

Commits on Feb 1, 2019

  1. When calling datashader.utils.mesh with dask dataframes, return a das… 

    …k dataframe.

Computing the mesh still requires bringing the entire vertices/simplices dataframes into memory, but the resulting mesh is now a Dask dataframe with partitions that are chosen intentionally to not cause triangles to straddle partitions.
    @jonmmease
    jonmmease committed Feb 1, 2019
    Configuration menu
    Copy the full SHA
    b33c860 View commit details
    Browse the repository at this point in the history

  2. Add documentation note about parallelizing trimesh aggregation with Dask

    @jonmmease
    jonmmease committed Feb 1, 2019
    Configuration menu
    Copy the full SHA
    ca5b977 View commit details
    Browse the repository at this point in the history

Commits on Feb 6, 2019

  1. revert conda 4.6 change, let pyctdev handle it

    @jonmmease
    jonmmease committed Feb 6, 2019
    Configuration menu
    Copy the full SHA
    42ba2c1 View commit details
    Browse the repository at this point in the history