CAVEclient
CAVEclient copied to clipboard
This is te python client for accessing REST APIs within the Connectome Annotation Versioning Engine.
```python datastack = 'minnie65_public' client = CAVEclient(datastack) client.materialize.query_table( 'nucleus_detection_v0', random_sample=10 ) ``` Returns an empty dataframe with the correct columns. Either `limit` or omitting `random_sample` entirely work fine.
I have a 500 server error when I access the table list using the `materialize.get_tables()` function. ```python url = "https://global.brain-wire-test.org/" datastack = "h01_c3_flat" client = CAVEclient(datastack_name=datastack, server_address=url) client.materialize.get_tables() ``` ```...
Add datastack check to not record datastack-to-server mapping if datastack is None.
Related to https://github.com/CAVEconnectome/MaterializationEngine/issues/134 This just raises an error client-side and instructs the user how to temporarily fix. In the future this will be fixed server-side, but still worth having this...
When trying to query a view that (I assume) did not yet exist at a given materialization we get a rather cryptic error: ```python >>> public = cv.CAVEclient('flywire_fafb_public') >>> client.materialize.query_view('valid_synapses_nt_np_v5',...
Live query results are coming back with `deleted` and `superceded_id` columns, which explicitly are always NaT/NaN because otherwise they wouldn't be in the data returned. `query_table` does not return these...
Here's a simple example after authenticating that doesn't seem to work: ```python from caveclient import CAVEclient client = CAVEclient(datastack_name="minnie65_public_v117") client.materialize.get_tables() ``` This results in the following error (re-formatted by me...
I'd like to get segment root_ids for objects that are directly contacting a target object. Using [get_contact_sites](https://caveconnectome.github.io/CAVEclient/extended_api/chunkedgraph/#caveclient.chunkedgraph.ChunkedGraphClientV1.get_contact_sites) should provide what I'm looking for, but I get an error. Using: ```...
we discussed two interfaces for specifying the units for dimensions for inputs and outputs: 1. methods could implement a `units`/`resolution`/etc. flag which denotes what units a user is inputting (e.g....