You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+83-10Lines changed: 83 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -271,23 +271,22 @@ These should match the relevant column type. Mapped variables are substituted in
271
271
A `variables` map usually isn't needed for simple queries. The basic condition string should automatically get converted to a meaningful type, but when this fails
272
272
replacing tricky elements with a variable may help.
273
273
274
-
### Remote registration[Experimental]
274
+
### Remote registration
275
275
276
276
For **OMERO Plus** installations which support TileDB as the OMERO.tables backend
277
277
it is possible to register tables in-place in a similar manner to in-place image
278
278
imports (otherwise table data is stored in the ManagedRepository).
279
279
280
+
This is a two-step process:
281
+
1) Convert the dataframe into a TileDB file
282
+
2) Register the remote converted table with OMERO
283
+
280
284
If you don't know what table backend your OMERO Plus server is using, you
281
285
probably don't have this feature available. If you have access to the server
282
286
machine you can check by running `omero config get omero.tables.module`,
283
287
if the response is `omero_plus.run_tables_pytables_or_tiledb` then tiledb is
284
288
available.
285
289
286
-
This feature is currently in active development. The current version of
287
-
omero2pandas can export tables locally in TileDB format to be registered with
288
-
OMERO using external tooling.
289
-
290
-
291
290
For this mode to be available extra dependencies must also be installed as follows
292
291
293
292
```bash
@@ -305,8 +304,82 @@ db_path = omero2pandas.upload_table("/path/to/my_data.csv", "Name for table",
305
304
```
306
305
307
306
Similar to regular table uploads, the input can be a dataframe in memory or a
308
-
csv file on disk.
307
+
csv file on disk. The input will be copied into a new TileDB database and
308
+
registered to OMERO in-place.
309
+
310
+
To perform this kind of registration you need to provide the `local_path` argument
311
+
to the standard `omero2pandas.upload_table` function (alongside required params for
312
+
a "normal" upload e.g. server connection details). The local path is the file path
313
+
where the tiledb file will be written to and registered to OMERO from.
314
+
If you provide a directory instead the tiledb file will be named based on the `table_name` argument.
315
+
316
+
Naturally, the OMERO server will need to be able to access the resulting tiledb file
317
+
in order to be registered. If the `local_path` is also visible from the server machine
318
+
(e.g. you're running the upload on the server itself) then that's sufficient. Otherwise
319
+
a `remote_path` argument is also available to tell the server where it should
320
+
find the table. This is typically needed if the tiledb file ends up mounted at a
321
+
different location between the local machine and the OMERO server.
322
+
323
+
For example, if registering from a Windows machine with a network drive to an OMERO server on Linux:
0 commit comments