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
This creates an OMERO.table with an additional Image ID column:
Image Name
Dataset Name
Bounding_Box
Channel_Index
Channel_Name
Image
img-01.png
dataset01
0.0469
1
DAPI
36638
img-02.png
dataset01
0.142
2
GFP
36639
If I name the first column to Image I get a failure with
ValueError: invalid literal for long() with base 10: 'img-01.png'
I'm just documenting this to clarify the results of my investigations and document the current behaviour. It seems inconsistent for Plate that we use Well and Plate columns that are really Well Name and Plate Name. The Project behaviour is more expected.
The text was updated successfully, but these errors were encountered:
Looking at examples added to the README in #28
it seems that the CSV format has different rules for Screen compared with Project:
Screen example has columns of
Well,Plate
and the column types arewell,plate
.Omitting the
# header
has no effect on column types ofwell and plate
.This creates an OMERO.table with additional
Well Name
andPlate Name
columns and the previousWell
andPlate
columns now have IDs instead of Names.If I use column named
Plate Name
instead ofPlate
in the csv, the script fails:and it also fails if I use
Well Name
instead ofWell
.When the target is a Project, we need columns named
Dataset Name
andImage Name
in the CSV and these columns are of typeString
.This creates an OMERO.table with an additional
Image
ID column:If I name the first column to
Image
I get a failure withI'm just documenting this to clarify the results of my investigations and document the current behaviour. It seems inconsistent for Plate that we use
Well
andPlate
columns that are reallyWell Name
andPlate Name
. The Project behaviour is more expected.The text was updated successfully, but these errors were encountered: