https://github.com/arm61/linearization-issues
ESI for "Is there still a place for linearization in the chemistry curriculum?"
Science Score: 36.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
○.zenodo.json file
-
✓DOI references
Found 6 DOI reference(s) in README -
✓Academic publication links
Links to: zenodo.org -
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (14.0%) to scientific vocabulary
Repository
ESI for "Is there still a place for linearization in the chemistry curriculum?"
Basic Info
Statistics
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
- Releases: 2
Metadata Files
README.md
Is there still a place for linearization in the chemistry curriculum?
The use of mathematical transformations to reduce non-linear functions to linear problems, which can be tackled with analytical linear regression, is commonplace in the chemistry curriculum. The linearization procedure, however, assumes an incorrect statistical model for real experimental data; leading to biased estimates of regression parameters and should therefore not be used in formal data analysis. This fact is overlooked in many chemistry degrees, students do not yet have the mathematical knowledge to appreciate why linearization leads to bias when it is introduced. I hope that this commentary will start a discussion around the place of linearization in the chemistry curriculum, and more broadly around how mathematical and statistical training is currently provided to chemistry students.
Andrew R. McCluskey*
*andrew.mccluskey@bristol.ac.uk
This is the electronic supplementary information (ESI) associated with the publication "Is there still a place for linearization in the chemistry curriculum?".
This ESI uses showyourwork to provide a completely reproducible and automated analysis, plotting, and paper generation workflow.
To run the workflow and generate the paper locally using the cached data run the following:
git clone git@github.com:arm61/linearization-issues.git
cd linearization-issues
pip install showyourwork
showyourwork build
Full details of the workflow can be determined from the Snakefile and the showyourwork.yml.
Contents
Shown below is a documented directory structure for this repository.
For those interested in the Jupyter Notebook that shows the general approach to non-linear optimisation, this can be found at src/scripts/weighted-non-linear.ipynb.
├── .github/workflows # Workflows for builidng the manuscript on Github
├── src
│ ├── scripts
│ │ ├── .gitignore
│ │ ├── LICENCE
│ │ ├── _fig_params.py # Custom figure formatting
│ │ ├── distributions.py # Script to produce Figure 3
│ │ ├── matplotlibrc
│ │ ├── ols.py # Script to produce Figure 1
│ │ ├── paths.py # Helper file to control paths
│ │ └── weighted-non-linear.ipynb # Jupyter Notebook showing weighted non-linear optimization
│ │ ├── wls.py # Script to produce Figure 2
│ └── tex
│ │ ├── figures # Figure pdfs are placed here when compiled
│ │ ├── outputs # TeX snippets are placed here when compiled
│ │ ├── .gitignore
│ │ ├── LICENCE
│ │ ├── bib.bib # Bibliography
│ │ ├── ms.tex # TeX of the manuscript
│ │ └── showyourwork.sty # LaTeX styles for showyourwork
├── .gitignore
├── LICENCE
├── README.md # You are here
├── Snakefile # Additional snakemake rules
├── environment.yml # conda/mamba environment file
└── showyourwork.yml # Defines showyourwork structure and options
Owner
- Name: Andrew McCluskey
- Login: arm61
- Kind: user
- Location: Copenhagen
- Company: European Spallation Source
- Website: https://mccluskey.scot
- Repositories: 8
- Profile: https://github.com/arm61
instrument data scientist @essneutron (he/him)
GitHub Events
Total
- Push event: 2
Last Year
- Push event: 2
Issues and Pull Requests
Last synced: over 1 year ago
All Time
- Total issues: 0
- Total pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Total issue authors: 0
- Total pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 0
- Pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Issue authors: 0
- Pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0