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
When you've typed in the wrong channel name or it has a typo, it would eb preferable if a list of found channel names could be returned.
Describe the solution you would like.
Something akin to the following which is returned for the wrong channel in ..spm
[minicircle] : dosfbipqeb not in .spm channel list: ['Height Sensor', 'Peak Force Error', 'DMTModulus', 'LogDMTModulus', 'Adhesion', 'Deformation', 'Dissipation', 'Height']
Describe the alternatives you have considered.
Written in the TopoStats issues before AFMReader:
Trying to process a ASD file it was found that it did not have the existing set of channels that we are aware of.
They were instead listed as...
0
20564
21061
Whilst we can add these as possible validated channels for the .asd file format it points to/suggests a wider problem in so much as there may be file specifications in use in the wild that we are not aware of.
To which end attempting to obtain a comprehensive sample of target file formats currently in use and that have been produced in the past would be beneficial so that we can enhance the channels that are supported.
This has scope for being compounded further as hardware manufacturers may change or modify their file specifications.
Would a potential solution be to say if no height channel is found it just
tries to process the first channel in the data?
Sample Image
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
When you've typed in the wrong channel name or it has a typo, it would eb preferable if a list of found channel names could be returned.
Describe the solution you would like.
Something akin to the following which is returned for the wrong channel in
..spm
Describe the alternatives you have considered.
Written in the TopoStats issues before AFMReader:
Trying to process a ASD file it was found that it did not have the existing set of channels that we are aware of.
They were instead listed as...
Whilst we can add these as possible validated channels for the .asd file format it points to/suggests a wider problem in so much as there may be file specifications in use in the wild that we are not aware of.
To which end attempting to obtain a comprehensive sample of target file formats currently in use and that have been produced in the past would be beneficial so that we can enhance the channels that are supported.
This has scope for being compounded further as hardware manufacturers may change or modify their file specifications.
Would a potential solution be to say if no height channel is found it just
tries to process the first channel in the data?
Sample Image
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: