Skip to content
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

Experimental data versus Arrhenius models in literature data. #262

Open
FuerstT opened this issue Aug 16, 2023 · 1 comment
Open

Experimental data versus Arrhenius models in literature data. #262

FuerstT opened this issue Aug 16, 2023 · 1 comment

Comments

@FuerstT
Copy link
Contributor

FuerstT commented Aug 16, 2023

Starting this thread to have a discussion on the best practice for reporting experimental data versus Arrhenius fits for literature values.

My preference would be to report the Arrhenius fit model from the paper if only plot data points in plots are given. The use of a web plot digitizer just adds additional uncertainty and potential human error. It is also difficult to check. However, if data is reported in a table or available in supporting information, those can be added to the database rather than the fit. Or if only data is presented with no Arrhenius fit in the paper.

@RemDelaporteMathurin
Copy link
Owner

I agree that the best case is when authors provide the raw data in a table, or even better in a downloadable supplementary file.
However it's far from being the common practice.

Data from WPD is less easy to check for sure. Though it's possible by simply loading the .tar file in WPD.

There are cases where the arrhenius fit doesn't match the data presented in graphs , like Fukada 2014. In this case, the fit was wrong but the data was correct (since the authors use it in a follow up publication). Using WPD was the only solution here.

About the uncertainty and human error, copying data from a table can also lead to human error since a lot of copy pastes are required. I think there's never a perfect and 100% automated solution.
The data uncertainty (not having the original data values) is small since the axes are calibrated and usually span over orders of magnitude.

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

No branches or pull requests

2 participants