First crack log position

[RupertPupkin]

Hi,
why is the first crack position in the log so strange?
Example:

338.283 210.000 209.700 210.914 210.674
339.283 210.000 209.700 211.057 210.791
340.283 211.250 211.050 211.068 210.912
341.283 212.500 212.100 211.157 211.031
342.283 212.500 212.900 211.243 211.147
343.283 212.000 212.550 211.336 211.265
344.283 210.500 210.550 211.268 211.381
345.283 210.750 210.450 211.304 211.496
346.283 211.500 211.600 211.529 211.609
347.283 211.750 211.750 211.693 211.721
!first_crack:338.498
348.283 210.750 210.750 211.532 211.836

Why is it written at this line? Should be several lines up.
And in KL Studio the first crack temperature is shown as 211.2°C. That correlates more to the values on the 340.283 line. How did you end up with 211.2?

[kaffelogic]

The first column in the log is time since the user pressed start - 'timer time'. The second column is unsmoothed temperature. Kaffelogic Studio displays everything in 'profile time', which is offset from 'timer time' by several seconds, and uses smoothed temperature data. The smoothing is done by moving means which introduces it's own time offset. Studio makes a number of time adjustments in the background. To complicate things further, the first crack log entry uses profile time.

TLDR: the raw data is time shifted and aligned by Studio. The numbers do not necessarily make sense until the adjustments are made.

[RupertPupkin]

Ok, thanks!
I was thinking about writing a parser to fetch log information and present it in table format, for easy comparation.

[kaffelogic]

If you export the log in Artisan format you get the data presented in columns with all of the offsets applied. You could consider writing your parser to use these exported files. In any case it lets you confirm that you have applied the offsets correctly.