A stopwatch and a thermometer will get you through a lesson. They will not get you a top-band internal assessment. This page is about the kit that collects better data than you can by hand, and about knowing when to reach for it.
📚 What you need to know
Computational chemistry uses computer models and maths to study chemicals and predict how they behave.
Large data sets come from four places: experiments, sensors, databases and simulations.
A data logger collects readings automatically, stores them, and shows them in real time.
A sensor is an input device: it detects a change and turns it into an electrical signal.
The four sensors to know: pH, temperature, pressure, conductivity.
A database is a structured collection of data that can be searched, sorted and filtered.
A model is a simplified version of reality, so it always involves some loss of accuracy.
Simulations let you explore what would be unsafe or impossible in a real lab.
Where computational chemistry fits in
Computational chemistry means using computers and maths to study chemicals rather than only mixing them in a flask. It is good at two things in particular: spotting patterns in large amounts of data, and making predictions from those patterns.
Predicting how reactive an element will be, or estimating a boiling point for a compound nobody has made yet, both fall into this. But any prediction is only as good as the data it was built from, which is why collecting that data properly matters so much.
Data loggers
A data logger is a small box that sits between your sensors and your computer. Sensors feed it readings, it stores them with a time stamp, and it passes them on.
The sensors detect, the logger records, the computer analyses. Keeping those three jobs separate in your head makes the whole system easy to describe.
What a logger actually buys you:
Speed. It can take readings many times a second. You cannot.
No reaction-time error. There is no moment where you glance at a stopwatch and then at a burette.
Real time display. You see the graph building as the reaction runs, so you notice problems while you can still fix them.
Better gradients. More points on a curve means a far more reliable rate of change.
It never gets bored. A logger will happily record overnight.
The grey line is what the reaction really did. Notice how the dashed hand-drawn version cuts the corner in the first ten seconds, which is where the rate is largest.
If your internal assessment involves a rate, this diagram is your argument for using a logger. You are not saying “it is easier”. You are saying the extra points let you find the initial gradient properly.
Sensors
A sensor is an input device. It detects a change in its surroundings and converts that change into an electrical signal, which the data logger then stores.
Sensor
What it measures
Typical use in chemistry
pH meter
Acidity or alkalinity
Finding the end point of a titration; testing buffers
Temperature probe
Temperature of a system
Calorimetry; following exothermic and endothermic changes
Pressure sensor
Pressure of a gas or liquid
Gas law experiments; reactions that produce a gas
Conductivity sensor
Electrical conductivity
Finding ion concentration; following a rate of reaction
How a pH meter works
A pH meter is not one sensor but two electrodes working as a pair.
The reference electrode gives a fixed, steady reading no matter what solution it sits in.
The other electrode ends in a thin glass membrane that responds to the concentration of H+ ions around it.
The meter measures the difference between the two signals and converts it into a pH value. Because the reference never moves, any change in the reading must be coming from the H+ ions.
The glass bulb is fragile and must stay wet between uses. A dried-out membrane is the usual reason a school pH meter gives nonsense.
Always calibrate. Before a titration, put the probe in known buffer solutions (usually pH 4, 7 and 10) so the meter knows what those values look like. An uncalibrated reading is not data, it is a number.
Getting data out of databases
A database is just a collection of data that has been organised so it can be searched, sorted, filtered and analysed quickly. Chemists use them constantly, because there is no point measuring something that has already been measured a thousand times.
Data you might pull from a database includes:
Formulae and charges of polyatomic ions
Physical properties such as melting and boiling points
Thermodynamic data: enthalpy changes, entropies, Gibbs energy values
Kinetic data such as rate constants, and equilibrium constants
Spectroscopic data, including NMR and IR spectra
Chemical structures, bond lengths and bond angles
Organic synthesis routes with their conditions and procedures
Names worth knowing, all free to search by name: PubChem for structures and properties of a huge range of compounds, ChemSpider for properties and spectra, the NIST WebBook for formulae, properties and reaction searching, SDBS (the Spectral Database for Organic Compounds) for NMR and IR spectra, and MolCalc for calculated molecular properties.
In an internal assessment, database values are perfectly acceptable as literature comparison data — but say where each number came from. A percentage error against an unsourced value is worth very little.
Models and simulations
A model is a simplified version of reality. A ball-and-stick model is the obvious example: it shows you the shape and the bond angles but says nothing about how the electrons are really arranged.
That simplification is deliberate, and it is also the catch. Every model involves approximation, so every model loses some accuracy. Even the enormous climate models running on supercomputers are simplifications.
A simulation takes a model and lets it run, so you can change a variable and watch what happens. Two things make simulations genuinely useful:
You can investigate what would be dangerous or impossible in a school lab — caesium and water, for instance.
You can change one variable at a time perfectly, with no measurement error at all.
The catch is the same one as before: the results are only as good as the model behind them. PhET is the simulation site most IB students meet, with tools for molecular shapes, the pH scale and states of matter.
🧩 Choosing the right sensor for your investigation
Write down what actually changes during the reaction — heat given out, gas produced, ions formed, acid used up.
Match that change to a measurable quantity. Ions formed means conductivity; gas produced means pressure.
Check the sensor can reach the range you need and is precise enough to see the change.
Decide your sampling rate. Fast reactions need many readings per second; slow ones do not.
Calibrate anything that needs it, and record that you did.
Run a quick trial before the real thing. It is much cheaper to find out now that the signal barely moves.
Worked examples
WORKED EXAMPLE
A student is following the reaction between magnesium and dilute hydrochloric acid. Suggest two different sensors that could measure the rate, and say what each one would record.
What changes during the reaction?
Hydrogen gas is produced and H+ ions are used up. Heat is also released.
Option 1
A pressure sensor in a sealed flask. Pressure rises as hydrogen is made, so the gradient gives the rate.
Option 2
A pH meter in the acid. As H+ is consumed the pH rises, and the rate of that rise follows the reaction.
Pressure sensor or pH meter, both logged against timea conductivity sensor also works, since Mg2+ replaces H+ and the conductivity changes
WORKED EXAMPLE
Explain two advantages of using a temperature probe and data logger rather than a thermometer and a stopwatch in a calorimetry experiment.
Advantage 1 — more readings
The logger records many times a second, so the cooling curve is properly defined and can be extrapolated back to the moment of mixing.
Advantage 2 — no human timing error
Every reading is time-stamped by the logger, so there is no reaction-time uncertainty from starting and stopping a stopwatch.
A third one if the marks allow
The maximum temperature is far less likely to be missed between readings.
More frequent readings and no human timing errorsay what the extra data lets you do, not just that there is more of it
💡 Exam tip
Learn the difference: a sensor detects, a data logger records and stores. Do not use the words interchangeably.
When asked for an advantage of data logging, give the consequence too: more points means a more reliable gradient.
For pH meters, name both electrodes. “It has a glass bit” is not an answer.
Say calibrate with buffer solutions whenever a pH meter appears in a method.
If a question asks about a model or simulation, mention approximation and the resulting loss of accuracy.
In your internal assessment, name any database you used. Unsourced literature values lose credit.
⚠️ Common mix-up
Saying a data logger is “more accurate”. It is more precise and takes more readings. Accuracy depends on calibration.
Thinking sensors remove all uncertainty. Every sensor has a stated uncertainty, and it belongs in your write-up.
Treating a simulation as evidence. It shows what the model predicts, not what nature does.
Confusing a database with a search engine. A database is structured and can be sorted and filtered.
Forgetting that models are simplifications. A perfect model would be reality itself.
Using a pH meter straight from the cupboard. Without calibration the reading drifts.
Up next: Using Technology to Process Data — what to do with all those readings once the logger has finished collecting them.
Want this explained one-to-one?
Book a free session with an experienced IB Chemistry tutor and get your trickiest topics made simple.
