Skip to content

Conversation

@Felix-Nicolas
Copy link
Contributor

Hi,

there was an issue with the baseline correction. Now, the MCC data should be fine.

Best,
Felix

@leventon
Copy link
Contributor

Hi Felix, thanks for updating this.
Things look good but I may misunderstand something here - it looks like the timestamps in your data are now earlier, but the associated temperatures are higher than before. Can you clarify?

@Felix-Nicolas
Copy link
Contributor Author

Hi Isaac,

Yes, I can explain that. For the revised dataset, the baseline correction was performed using the FTT Curve Fit software. The limits were set to approximately 200 °C and 600 °C. I then restricted the data uploaded here exactly to the range between 200 and 600 °C.

In the Curve Fit software, applying the baseline correction automatically limits the dataset to the selected range, and the point at the lower bound (around 200 °C) is defined as time = 0 s.

In the original dataset, the baseline correction was applied to the entire dataset and no data were truncated.

This is why the absolute time values differ between the previous version and the version in this PR. Unfortunately, I cannot change the way the FTT software handles the time data. If this is a major issue, I can alternatively perform a linear baseline correction myself using a Python script. You can decide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants