Skip to content
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.

Sign up for GitHub

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

Jump to bottom

refactor the HDF5 service to produce both DATATYPE and DBTYPE #38

Closed
alexbaden opened this issue May 17, 2015 · 5 comments
Closed

refactor the HDF5 service to produce both DATATYPE and DBTYPE #38

alexbaden opened this issue May 17, 2015 · 5 comments
Assignees
@alexbaden

Comments

@alexbaden
Copy link
Contributor

Right now it produces DATATYPE, which contains one of {image, annotation, probmap, etc}. I'd like to rename that DBTYPE and add DATATYPE, which contains {uint8, uint16, uint32, etc}. We could probably engineer a solution to pull the DATATYPE from the CUTOUT, but this is a more general way to do it.
@alexbaden alexbaden self-assigned this May 17, 2015
@alexbaden
Copy link
Contributor Author

I changed this so I can make progress on CAJAL right now. Easy enough to refactor if we decide something else.

@alexbaden alexbaden mentioned this issue May 17, 2015
Closed
alexbaden pushed a commit that referenced this issue May 17, 2015
refactored hdf5 to output a file with DATATYPE and DBTYPE -- see issue …
c8279da 
…#38
@randalburns
Copy link
Collaborator

OK, we decided on naming these "channel type" and and "data type" This is consistent with the ocpcaprojects implementation with has channel_type and channel_datatype

@alexbaden
Copy link
Contributor Author

Need to rename this to CHANNELTYPE in my branch ( ab-cajal-d7 )

@alexbaden alexbaden reopened this May 19, 2015
@kunallillaney
Copy link
Collaborator

@alexbaden @randalburns Have we reached a consensus on this? Let me know the final format for both POST and GET(ideally the same) and I will ensure that it is the same.

@kunallillaney
Copy link
Collaborator

Done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alexbaden alexbaden

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@randalburns @kunallillaney @alexbaden