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.

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

'char' support error in h5create called by vectorize_V200/validate_the_OptionalInput #1

Open
liorgolgher opened this issue May 6, 2021 · 1 comment

Comments

@liorgolgher
Copy link

Greetings,

Thank you for publishing this important toolkit!

I have tried to apply it on one of my 2p cerebral microvascular datasets, downscaled to save processing time:

https://drive.google.com/file/d/1RMaNy67zhx8GZn8vqrmr8FTP7NUbtyr8/view?usp=sharing

Unfortunately I got the following error:

Error using h5create>create_dataset (line 228)
'char' is not a supported datatype.

Error in h5create (line 100)
create_dataset(options);

Error in vectorize_V200/validate_the_OptionalInput (line 606)
                        h5create( path_to_original_data, '/d', size_of_image, 'Datatype', original_data_type );

Error in vectorize_V200 (line 764)
    [ ~, ROI_names ] = validate_the_OptionalInput( optional_input );

I suspect that it may have to do with the tif2mat function I used, which I stole from CaImAn:
https://github.com/flatironinstitute/CaImAn-MATLAB/blob/master/endoscope/tif2mat.m
https://github.com/flatironinstitute/NoRMCorre/blob/master/bigread2.m

Are you using a different tif2mat function? How should I work around these issue?

Many thanks,
Lior

@mihelics
Copy link
Collaborator

Hi Lior,

I'm so sorry about the delay. I just noticed that issues have been raised on this page for years. My sincerest apologies.

I hope you found out your issue. I am using this function for the tif2mat call, please excuse any ambiguity in function naming. You should already have this function in the folder with the other source code for this software. Make this your working directory and take other directories off the path to avoid the naming ambiguities.

Regards,
Sam

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants