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.

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

Feature/flywire meshes #25

Merged
merged 6 commits into from
Aug 28, 2020
Merged

Feature/flywire meshes #25

merged 6 commits into from
Aug 28, 2020

Conversation

jefferis
Copy link
Collaborator

read flywire meshes directly

* we might use cloudvolume for other mesh types
* but still depends on DracoPy
* alternatives to get rid of this include
  - using the javascript dracodec library (which is probably fast enough) in combination
    with the V8 R package.
  - wrapping the dracodec portion of draco in an R C++ package
  (probably not a big deal if one could figure out what was needed from the cmake file)
* need to think about whether this should actually be in suggests or not (but if not we will get a warning from R CMD check).
@jefferis
Copy link
Collaborator Author

jefferis commented Aug 4, 2020

  • note that dracor is now on CRAN however because meshes are encoded in multiple mesh fragments, the functionality on this branch is still inferior to cloudvolume since a) it does not simplify redundant vertices contained in more than one fragment b) fetching meshes is slower because (I believe) cloudvolume fetches meshes in parallel whereas this fetches them one by one.

@jefferis jefferis merged commit d657cbb into master Aug 28, 2020
@jefferis jefferis deleted the feature/flywire-meshes branch October 23, 2020 22:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant