Skip to content

Conversation

@jakobtroidl
Copy link
Contributor

  • added hint that bucket must be public
  • mentioned not to use dashes in bigtable name

$ kubectl exec -ti deploy/master -- bash
// now you're in the container
> ingest graph <unique_test_bigtable_name> datasets/test.yml --test
> ingest graph <unique_test_bigtable_name> datasets/test.yml --test // avoid dashes in <unique_test_bigtable_name>, neuroglancer can't handle them
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it might be cave code that has issues with dashes. It is better to just say use underscores instead.


> NOTE: Depending on your dataset, you will need to figure out the optimal limits for cpu and memory in your worker deployments. To do that adjust the `count` and `machine` variables in terraform.tfvars. It can vary with chunk size, size of supervoxels (atomic semgents in layer 1), number of edges per chunk and so on.

> NOTE: The bucket storing the edges, components etc must be public. The bucket is also linked in `example_values.yaml` [here](https://github.com/seung-lab/CAVEpipelines/blob/4d0ee8d98fb8891074d6e1115ed9394e6a021cd5/helm/pychunkedgraph/example_values.yaml#L29).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The bucket with segmentation data needs to be public, not the one with edges and components. They do not need to be in the same bucket. It needs to be public for neuroglancer to read.

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.

2 participants