For lab members

Resources

Templates, tools, and shared files for the group. Everything here is meant to be downloaded and used in your own work.

Experimental design

How we plan experiments — start from what you want to know, then let the question set the design.

Start from the question, not the technique

The habit the group is built on: decide what you want to know, phrase it so it could come out either way, and choose the experiment that most directly separates the possible answers. Use the AI prompt pack to think a design through — or to check a write-up. Worked case studies will be added here over time.

Design the experiment from the question, not from the instrument. Decide what you want to know first; the right experiment is whatever separates the possible answers most directly. A technique you happen to have is not a reason to run it.

  1. State the question so it can come out either way. "Does the additive suppress dendrites?" is answerable; "characterise the additive" is not. If no result would surprise you, there is no question yet.
  2. Write down the prediction and its alternative. What do you expect to see, and what would the competing explanation predict instead? Two named outcomes on paper before any cell is built.
  3. Name the result that would change your mind. A claim that no measurement could contradict is not worth measuring. Decide, in advance, what would falsify your prediction — that observation is the experiment.
  4. Choose the minimal design that tells those outcomes apart. Vary one thing, hold the rest fixed, and make sure the two predictions land in visibly different places. Extra conditions that cannot change the conclusion are decoration.
  5. List the controls that rule out the boring explanation. Baseline, reference, and "nothing changed" conditions exist to kill the trivial reasons your effect might appear. If a reviewer can explain your result without your hypothesis, add the control that closes that door.
  6. Fix what you will measure and report before you start. Choose the metrics, the conditions to disclose, and the number of cells up front — not after seeing the data. This is also where the reporting checklist (below) comes in.
Also in this section
  • Battery reporting checklist — what a battery result must disclose to be trusted and compared (below).
  • Case studies (coming) — worked examples from the group: the question, the design chosen, and why.

Battery reporting checklist — what to report, what to do

Before you plot a battery result, make sure it can be trusted and compared. This is a simple summary of what every battery figure and Methods section must disclose, distilled from the reporting guidelines of Joule, ACS Energy Letters, Advanced Energy Materials, and the Nature journals — the same items most journals expect.

A reader should be able to rebuild your cell and reproduce your plot from the Methods and SI alone, and compare your numbers to anyone else's on equal terms. If they can't, something below is missing. Full version and printable copy: download the file at the bottom.

Report — cell & electrodes
  • Cell type & configuration; half-cell vs full-cell; 2- or 3-electrode
  • Counter/reference (e.g. Li) — half-cell CE ≠ full-cell CE
  • Active-material mass and loading (mg cm⁻²)
  • Electrode area and areal capacity (mAh cm⁻²)
  • Formulation (active:conductive:binder), thickness, density
  • N/P ratio for full cells; Li excess for Li-metal
Report — electrolyte
  • Composition and amount — E/C ratio (µL mAh⁻¹). A flooded cell hides poor efficiency
  • Separator type/thickness
Report — protocol
  • Voltage window (cut-offs)
  • C-rate and current density; define what 1C means
  • Basis of specific values: per active / electrode / cell
  • Temperature (controlled?); formation, CC–CV, rests; cycle count
Report — metrics
  • Specific capacity with basis stated
  • Initial & steady-state CE to enough sig-figs (99.92 %, not ~100 %)
  • Retention: % over N cycles and absolute capacities
  • Energy/power density — state the level; rate capability
Do — to make the numbers trustworthy
  • Test at a practical mass loading (mAh cm⁻² range) — thin electrodes inflate rate & cycling
  • Run a fair control under identical conditions in the same study
  • More than one cell: report n, show error bars/spread, give the average — not the best cell
  • Show raw voltage profiles, not only capacity-vs-cycle
  • Make a full cell (or say you didn't) before claiming device-level performance
Red flags reviewers catch

Big areal capacity from a tiny loading · half-cell shown as a full cell · CE quoted as "~100 %" · no electrolyte amount · "high rate" from an unrealistically thin electrode · only % retention with no absolute numbers · only the single best cell.

Distilled from the reporting guidelines of Joule (Battery Checklist required at submission), ACS Energy Letters, Advanced Energy Materials, and the Nature journals — which most journals, including Materials Today Energy, expect too. Full sources are in the download.

Figures & design

Colour, style, and templates for figures, posters, and slide decks.

Lab figure palette — Teal & Amber

The colour system for every figure we publish: papers, theses, posters, and slides. Drawing every figure from the same colours — in the same order and with the same meanings — is what makes our output recognisable, and it keeps figures readable for colour-blind readers and in greyscale, which most journals require. Start with the style guide, pin up the reference sheet, and apply it with the Python module or the AI prompt.

Categorical — for discrete groups, used strictly in this order
teal#0F6E6Bcontrol / baseline
amber#E29A2Dthe effect of interest
rust#BE654C3rd condition
skyblue#5A91BE4th condition
sage#83A4625th condition
plum#995A906th condition
graphite#333F4Aaxes, ticks, text
sand#DFC98Ffills / CI bands
Neutrals — text, axes and gridlines (never pure black)
ink#1C242B
graphite#333F4A
slate#66727C
mist#B9C1C6
paper#F3F0EB
Ramps — for continuous data, not discrete groups
Sequential teal — unsigned magnitude (intensity, density)
Sequential amber — second magnitude channel
Diverging — signed values, centred on zero (log2FC, z-score)
Python

Drop labpalette.py beside your script, then one line applies the whole house style:

import labpalette as lp
lp.apply()                     # colours, fonts, 600 dpi
ax.plot(x, y, label="control") # cycles teal, amber, rust, ...
ax.imshow(Z, cmap=lp.cmap("teal"))
AI tools

Open the AI prompt pack below, copy the block, and paste it into ChatGPT / Claude / Gemini before asking for a plot, diagram, or figure. It makes the AI use these exact colours and rules.

Core rules
  • teal = control/baseline, amber = the effect the figure is about.
  • Use categorical colours in order; add marker shape or line style beyond 4 groups.
  • Axes and text in graphite (#333F4A) — never pure black; gridlines in mist.
  • Categorical for groups, ramps for continuous. Centre the diverging ramp on zero.

Full rationale, accessibility validation, and setup for R, Illustrator, LaTeX and CSS are in the style guide below.