Helicon Soft Forum

Dear Helicon Community,

This question applies to both H-Remote & H-Focus.

We do a lot of imaging for museum professionals and forensic specialists.

Both of these audiences consistently request a processing "log file" of what actually took place within the 'capture' or 'focus' events.

(here's the jist, we need to provide scientific provenance or 'proof' of what how the files were generated and the changes that occurred to them - they want to be able to prove that the chance of image manipulation or fraud is Zero)

Is there a way that I can save / export an 'Event Process Log File'? preferrabley into a .XML file? Human or machine readable?

Thanks for any info,

Marlin.

Yes, this is possible to implement. Please send us a sample log to [email protected]

hi Stas,

sorry about the delay, I wanted to check with my peers previous to sending this data.

This sort of data is really important to a certain audience. I really appreciate you taking a look at this. In a way this is a slippery slope, bc its straight forward to write events to a log file, there's just so much of it.

In a conversation with my professional peers, we wanted keep it simple:

-basic requirements like a time and date stamp
-what version of the tool was used
-a recording of all the steps (such as how many images taken, focal changes (if there is numerical data for that)
-camera data, etc

For the processing I am not sure the best way to record what Helicon does.
-perhaps state how many images were stacked
-what the names of those original images were
-name for the algorithm they use (or any parameters or user settings to record that)

We have a really simple 'log' text file for our "array capture software" - an example this is below. The 'log file' is just text.

(you can see our 'light array' product and learn more at this url:)
http://culturalheritageimaging.org/What ... jects/wam/

I hope that you get the idea.

If Helicon could export a similar 'log file' from Focus and from Remote. Adoption by the museum and forensic committees, etc, would really benefit from the argument of being to claim that Helicon really is one step closer to 'scientific imaging'.

I'd be interested to learn about your thoughts and next steps, and if you're going to adopt the ability to export an event 'log file'.

thanks.
marlin.

********************

Capture Client Version : 1.7.0.CHI
Capture started at Fri Jul 19 11:44:38 2013

No patch panel file loaded for lights. Using default mapping.
Camera Parameters
Av : 8
Tv : 15
ISO : 200
Image Quality :

LightPort = COM3
SequenceSize = 45
SavePath = \\vmware-host\Shared Folders\My Desktop\Yale-rig-testing
RootPrefix = sphere-2-in
LightsDelay = 1000
TurntableEnabled = 0
TurntablePort =
Viewpoints = 33554434
ViewSeperation = 1.9478e-043
RotationDelay = 1919

sphere-2-in_01
sphere-2-in_02
sphere-2-in_03
sphere-2-in_04
sphere-2-in_05
sphere-2-in_06
sphere-2-in_07
sphere-2-in_08
sphere-2-in_09
sphere-2-in_10
sphere-2-in_11
sphere-2-in_12
sphere-2-in_13
sphere-2-in_14
sphere-2-in_15
sphere-2-in_16
sphere-2-in_17
sphere-2-in_18
sphere-2-in_19
sphere-2-in_20
sphere-2-in_21
sphere-2-in_22
sphere-2-in_23
sphere-2-in_24
sphere-2-in_25
sphere-2-in_26
sphere-2-in_27
sphere-2-in_28
sphere-2-in_29
sphere-2-in_30
sphere-2-in_31
sphere-2-in_32
sphere-2-in_33
sphere-2-in_34
sphere-2-in_35
sphere-2-in_36
sphere-2-in_37
sphere-2-in_38
sphere-2-in_39
sphere-2-in_40
sphere-2-in_41
sphere-2-in_42
sphere-2-in_43
sphere-2-in_44
sphere-2-in_45
45 photos taken.