Jeremy Maitin-Shepard

Results 521 comments of Jeremy Maitin-Shepard

Can you say a bit more about the input data, and how you want to load it? I don't have example code, but one example application might be that you...

Glad to hear that the performance is good! Unfortunately there is not a way to list the scales at the moment. I have planned a "MultiscaleTensorStore" type that will provide...

For macOS, I believe the issue is that you need to set MACOSX_DEPLOYMENT_TARGET >= 10.14 due to tensorstore's use of sized/aligned operator new/delete: https://github.com/google/tensorstore/blob/a3f3ee23a8d27a5ba8c1faee944d3a23b00fedf4/setup.py#L117 I am not sure what the...

I think the issue with Ubuntu 20.04 is that, despite our documentation claiming support for GCC 9, we stopped testing with GCC 9 some time ago. Currently we only test...

Regarding that error: TensorStore defines that link feature here: https://github.com/google/tensorstore/blob/b92f40210186e7246c6873bdb3947c30c17cd74a/tools/cmake/bazel_to_cmake.cmake#L70 That file is included from tensorstore's CMakeLists.txt: https://github.com/google/tensorstore/blob/b92f40210186e7246c6873bdb3947c30c17cd74a/CMakeLists.txt#L75 Therefore I'm not sure what the issue is. However, that error suggests...

This particular warning would be fixed by updating our version of aom. In general with the large number of dependencies and compilers to support it may be difficult to avoid...

Currently tensorstore expects those data types to be "|i1" and "|u1" since for a 1-byte type endianness does not matter. It looks like zarr-python also seems to use "|i1" and...

We are working on adding C++ API documentation and examples, but unfortunately haven't had the time to finish that yet. In the meantime you can look here for some usage...

Assuming you are using bazel to build, drivers are registered by including the appropriate driver target as a dependency in your build. For `zarr` and `file` drivers you need: `//tensorstore/driver/zarr`...

`tensorstore::Open` returns a `Future`, calling `result()` gives you a `Result` (which holds either a `TensorStore` value (indicating success) or an error `absl::Status`). If you instead call `value()` you will get...