JPK file format is outdated

ocesou / hooke

Automatically exported from code.google.com/p/hooke

GNU Lesser General Public License v3.0

0 stars 0 forks source link

JPK file format is outdated #22

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
JPK upgraded its file format earlier this year. Files of the new format are
not recognized. 

What is the expected output? What do you see instead?
"Not a recognizeable curve format."

What version of the product are you using? On what operating system?
version 0.8.3_devel
Windows XP
Python 2.5.2

Please provide any additional information below.
JPK has a very tolerant ugrade strategy. Even users of the NanoWizard I get
the latest updates for the image processing software. Therefore most users
might "produce" files in the new format. (Which is actually a zip-package.
File is attached.)

Original issue reported on code.google.com by albedomanu@googlemail.com on 16 Oct 2009 at 5:41

Attachments:

GoogleCodeExporter commented 8 years ago

Hi, thank you for the information! The JPK support was based on a few example 
files
supplied by a JPK guy after a demo, so it has never been properly tested. I'll 
try to
have a look to the new file format.

Original comment by devicera...@gmail.com on 20 Oct 2009 at 10:59

GoogleCodeExporter commented 8 years ago

albedomanu,

Your force curves reference the piezo calibration file:
  /etc/opt/jpkspm-config-3.3.1/instruments/JPK00343/calibrations/default.cal
Could you attach that as well?

It's been a while since this issue opened, so perhaps albedomanu is no longer 
following it.  If anyone has one of the JPK calibration files, that would be 
useful.

Thanks!

Original comment by tvrkng@gmail.com on 14 Jun 2010 at 11:30

GoogleCodeExporter commented 8 years ago

Hi,

nice, that you are working on the jpk file format. The recently introduced 
ForceRobot 300 uses the same file format. Therefore your work could be double 
useful. (I even tried to write an import filter on my own, but without success.)

Please have some patience until next Monday. Then I will sent you the requested 
file.

Original comment by albedomanu@googlemail.com on 14 Jun 2010 at 2:10

GoogleCodeExporter commented 8 years ago

And here is the requested file.

Original comment by albedomanu@googlemail.com on 16 Jun 2010 at 1:35

Attachments:

default.cal

GoogleCodeExporter commented 8 years ago

Calibration file support as of
  http://www.physics.drexel.edu/~wking/code/hg/hgwebdir.cgi/hooke/rev/72acdb93d5be
but I'm not sure about my format interpretation.  I've emailed JPK to ask.

Original comment by tvrkng@gmail.com on 17 Jun 2010 at 5:20

GoogleCodeExporter commented 8 years ago

JPK's Michael Haggerty just confirmed my format interpretation, and also 
pointed out that the information in the external calibration file is reproduced 
in the curve file itself.  Moreover, the version in the curve file records the 
calibration at the time that the experiment was performed, while the external 
file may have changed since then due to subsequent recalibrations with piezo 
degradation, etc.

The new JPKDriver now correctly handles the 'file'-type calibrations by 
treating them like internal 'simple'-type calibrations:
  http://www.physics.drexel.edu/~wking/code/hg/hgwebdir.cgi/hooke/rev/3d99af36fcca

We can close this bug once my branch gets merged into the trunk.

Original comment by tvrkng@gmail.com on 17 Aug 2010 at 2:25