-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supported raw and label formats #61
Milestone
Comments
hanslovsky
added a commit
that referenced
this issue
Jun 14, 2018
Addressed in https://github.com/saalfeldlab/paintera/tree/paintera-datasets |
Option (3) does not work for HDF5 (without further thinking/hacking of the HDF5 bindings, which is an OK restriction) |
hanslovsky
added a commit
that referenced
this issue
Jun 19, 2018
hanslovsky
added a commit
that referenced
this issue
Jun 21, 2018
Attempt to add dataset specification as defined in #61
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need to specify a source structure that is supported in the
Paintera
main class entry point.First Draft
Note that this is relevant only for sources that are added through the open dialog or via command line arguments. Any source that is specified in the project's
attributes.json
can be loaded as long as the appropriate de-serializer is on the classpath.Raw
Accept any of these:
"resolution": [x,y,z]
and"offset": [x,y,z]
."multiScale" : true
attribute and contains three-dimensional multi-scale datasetss0
...sN
. Optional attributes are"resolution": [x,y,z]
and"offset: [x,y,z]"
. In addition to the requirements from (1), alls1
...sN
datasets must contain"downsamplingFactors": [x,y,z]
entry (s0
is exempt, will default to[1.0, 1.0, 1.0]
). All datasets must have same type. Optional attributes from (1) will be ignored."painteraData : {"type" : "raw"}
and a dataset/groupdata
that conforms with (1) or (2).Labels
Accept any of these:
LabelMultisetType
("isLabelMultiset": true
) three-dimensional N5 dataset. Optional attributes are"resolution": [x,y,z]
,"offset": [x,y,z]
,"maxId": <id>
. If"maxId"
is not specified, it is determined at start-up and added."multiScale" : true
attribute and contains three-dimensional multi-scale datasetss0
...sN
. Optional attributes are"resolution": [x,y,z]
,"offset": [x,y,z]
,"maxId": <id>
. If"maxId"
is not specified, it is determined at start-up and added (this can be expensive). In addition to the requirements from (1), alls1
...sN
datasets must contain"downsamplingFactors": [x,y,z]
entry (s0
is exempt, will default to[1.0, 1.0, 1.0]
). All datasets must have same type. Optional attributes from (1) will be ignored."painteraData : {"type" : "label"}
and a dataset/groupdata
that conforms with (1) or (2). Optional sub-groups are:fragment-segment-assignment
-- Dataset to store fragment-segment lookup table. Can be empty or will be initialized empty if it does not exist.unique-label-lists
-- Multiscale varlength dataset with same 'dimensions'/'blockSize' and as dataset(s) indata
. Holds unique block lists from which relevant blocks for specific ids are retrieved.Things to consider for labels:
"maxId"
attribute mandatory becauseIdService
needs it and would require to scan whole dataset (can be huge)unique-label-lists
exists, orLabelMultisetType
dataset (currently,VolatileLabelMultisetArray
holds a set of contained labels).unique-label-lists
if option (3), probably useful for looking at small datasets), orattributes.json
). There should be an option to export fragment-segment-assignment as N5 dataset. That way, users can choose to update their source in order to conform with (3) and not lose their work on fragment-segment assignmentsThe text was updated successfully, but these errors were encountered: