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
I know you've stated there are hardcoded dependencies for certain versions, so this issue is already known. I've tried running the software with check_version=False, in which case the read() operation succeeds and returns a <nanoscope.nanoscope.NanoscopeFile> object. When trying to do any processing however, it returns a NoneType object. I've checked the methods and there are no images in the list_images. Is this package only designed for image files then? I'm unsure if the problem is because of the version or because I'm processing curves not images.
Please let me know if you have any advice on correctly pulling the F-D data from the binary portion of the file!
The text was updated successfully, but these errors were encountered:
The software was initially designed with only images in mind - so the issue is likely that there is no support for curves in the parsing code rather than the file version. As far as fulling the F-D data from the raw binary I'd have to check the documentation on how it's stored.
I know you've stated there are hardcoded dependencies for certain versions, so this issue is already known. I've tried running the software with check_version=False, in which case the read() operation succeeds and returns a <nanoscope.nanoscope.NanoscopeFile> object. When trying to do any processing however, it returns a NoneType object. I've checked the methods and there are no images in the list_images. Is this package only designed for image files then? I'm unsure if the problem is because of the version or because I'm processing curves not images.
Please let me know if you have any advice on correctly pulling the F-D data from the binary portion of the file!
The text was updated successfully, but these errors were encountered: