-
Notifications
You must be signed in to change notification settings - Fork 6
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
Bug: Compability with jpk-force-map #25
Comments
It could be that the file format changed. Do you have an example file we can use for testing? |
Of course! Thank you for your time! |
Apparently it doesn't like all of the jpk-Files, I also tested jpk-force and it does not work By any chance you haven't had time to take a look? The software from jpk itself is...well... improvable. |
Hi, unfortunately I did not have time yet to look into it, sorry. |
@Kutzti It looks like there are three segments per curve in the file. What are those? For force-indentation measurements, nanite expects two segments per curve (approach and retract). |
These segments are pauses. Interesting, I was not aware of the fact that only 2 segments were expected. |
OK, what is the reasons for these pauses? And how are you implementing them (constant height or constant force). AFAIK, there should not be any pauses, because then you would be mixing force-indentation with creep-compliance or stress-relaxation. |
There is currently some compability problem with .jpk-force-map. Neither .load_data() nor load_group() nor QMap() can handle force maps.
Each of the upper methods lead to an empty group.
The text was updated successfully, but these errors were encountered: