Everything your team needs to prepare: a hands-on guide to computational biology tools, the structure of the final presentation, the toolbox and all the frequently asked questions.
Guide to computational biology tools
From sequence to structure — in 7 steps
A practical walkthrough for teams using computational biology tools for the first time, from protein sequence to structure prediction and evaluation: what to do at each step, which tools to use and how to judge how reliable the results are.
Step 1 of 7
Frame the question
Start from a clear, testable biological question — not from the tool. Decide which protein (or complex) you are interested in, what you will compare it with and what you will look at to answer.
Choose a target and a reference to compare against (e.g. the reference enzyme versus a variant).
Write down in advance what would count as evidence — and what would not.
Keep the scope small: one well-supported question is enough.
A good fit for structure prediction
The 3D structure of a protein or a complex.
Where a residue sits relative to the active site or an interface.
Structural hypotheses where no experimental structure exists.
Needs other methods too
The effect of a point mutation on stability or function.
The binding affinity of a drug or inhibitor.
Protein motions and dynamics.
Step 2 of 7
Get the sequence
Look the protein up in UniProt and download its amino-acid sequence in FASTA format. Check the entry’s annotation — organism, isoforms and features such as a signal peptide. For the variant, change only that one residue in a copy of the sequence.
Decide whether to predict the mature protein (without the signal peptide), and make the same choice for the reference and the variant — it also affects the numbering.
Save the reference and the variant as separate, clearly named FASTA files.
Note the entry’s accession number for your documentation.
Caution: A residue’s position in the literature can differ from its position in the UniProt sequence — β‑lactamases are commonly described with Ambler numbering. Before substituting, make sure the position you picked really holds the expected amino acid.
Step 3 of 7
Check what already exists
Before running any prediction, see whether structures already exist. The AlphaFold Protein Structure Database holds ready-made predictions for many UniProt proteins, while RCSB PDB and PDBe hold experimentally determined structures.
An experimental structure is the best reference against which to judge a prediction.
For each structure, note the method, the resolution and any bound ligands.
AlphaFold DB holds predictions for UniProt sequences; a variant you made yourselves is unlikely to be there — you will predict it in step 4.
Step 4 of 7
Run the prediction
AlphaFold Server gives free access to AlphaFold 3 for non-commercial use, with a daily job limit. You paste the sequence (or the sequences of the complex), name the job and submit it. Run the reference and the variant as two separate jobs so that they stay comparable.
Where it is relevant, add the extra chains, ions or ligands that AlphaFold Server supports.
Keep a record: which sequence, which additional molecules, which date, which job name.
Alternative routes: ColabFold, or a local AlphaFold 3 installation.
Caution: AlphaFold Server accepts only the ligands, ions and modifications it supports — not arbitrary chemical structures. Check its FAQ before you design your workflow; complexes with inhibitors such as avibactam may need a local AlphaFold 3 installation or docking.
Step 5 of 7
Read the confidence scores
Every prediction comes with confidence scores. They are the first thing you look at: they show which parts of the model you can use and which you cannot. A structure with low confidence exactly where your region of interest lies does not support conclusions about that region.
pLDDT: per-residue confidence on a 0–100 scale — local accuracy.
PAE (predicted aligned error): expected positional error in Å for pairs of residues — the relative placement of domains and chains.
pTM and ipTM: overall scores — pTM for the whole structure, ipTM for the relative positions of the subunits of a complex.
507090
Step 6 of 7
Visualise and compare
Open the models in ChimeraX or PyMOL, colour them by pLDDT and superimpose them on the experimental structures. The RMSD after superposition gives a numerical measure of the deviation; Foldseek finds structurally similar proteins, even where sequence similarity is low.
Compare prediction with prediction, but also prediction with experimental structure.
Zoom into the region of interest and note what changes: side chains, hydrogen bonds, salt bridges, loop conformation.
Agreement with experimental structures that may have been in the model’s training data is not independent validation.
Keep captioned images — you will need them for the final presentation.
Useful commands
ChimeraXcolor bfactor #1 palette alphafoldColour by pLDDT (the values are stored in the B-factor field).
ChimeraXmatchmaker #2 to #1Superimpose model #2 on #1; the RMSD is reported.
PyMOLalign variant, referenceSuperimpose two structures and compute the RMSD (object names are illustrative).
Step 7 of 7
Interpret critically and document
AlphaFold gives a static structure prediction. It was not designed to predict the effect of point mutations — a single substitution often barely changes the predicted structure — nor binding affinities. That is not a failure of your team; it is the limit of the method, and it should be stated.
Complement it with other approaches: docking, molecular dynamics, stability predictors, the literature.
Separate explicitly what the data show from what you hypothesise.
Record tools, versions, inputs and parameters — you will need them for the final presentation.
Ask your mentors early, not at the last minute: a scientific mentor for the question and its interpretation, a technical mentor for running the predictions and reading the confidence scores.
Final presentation
10 minutes for the presentation
A suggested structure for your team’s final presentation: four parts that take the audience from the idea to the results.
The team and the idea
Team
Challenge
Proposed solution
≈ about 1 min
The scientific problem
Scientific background
The problem
Why it matters
Hypothesis / research question
Available data
≈ about 3 min
The approach
Methodology
Workflow
Input data
Complementary tools
Validation and limitations
≈ about 3 min
Tools and results
How the relevant tools and databases were used (e.g. AlphaFold, UniProt)
What results emerged
How they were assessed
What they contributed to the solution
What the next steps are
≈ about 3 min
A rule for every team
Document what you used
In the final presentation, every team must report:
the tools, databases and external sources it used
its key inputs and parameters
Using AI and computational biology tools does not replace scientific validation.
(opens in a new tab)
Toolbox
Tools for every stage of the analysis
A curated list of bioinformatics and computational biology tools, databases and resources: from checking your sequence to predicting, comparing and visualising structures.
Essential tools
Start here: the tools that cover the core of the hackathon workflow.
These frequently asked questions explain how the Hackathon is run, the basic requirements and the stages of the competition, so that you know what to expect and can prepare properly for taking part.
31 questions
Suggested searches
Participation & process
23 questions
What is BIOHackathon?
BIOHackathon 2027 is a computational biology hackathon organised jointly by the following institutions: Region of Central Macedonia (Deputy Region of Digital Governance), WALK – Center for Entrepreneurship and Innovation of the Aristotle University of Thessaloniki, International Hellenic University (Department of Nutritional Sciences and Dietetics), International Hellenic University (Department of Biomedical Sciences), Centre for Research and Technology Hellas (Institute of Applied Biosciences, INAB), National Hellenic Research Foundation (Institute of Chemical Biology), University of West Attica (Department of Biomedical Engineering), Anatolia American University U.L.E., ACM Student Chapter UoA and Google Developer Group on Campus Athens.
Its purpose is collaboration, developing ideas and searching for innovative solutions to specific challenges (cases). Working in teams, participants use computational biology tools on four antimicrobial-resistance challenges: health, food, agriculture and livestock.
You will work on real antimicrobial-resistance challenges, using computational biology tools.
You will attend talks by experts that provide the necessary scientific and technical background, and you will be supported by scientific and technical mentors.
You will collaborate in an interdisciplinary team, with participants from different scientific or professional fields.
You will present your solution to the Jury and compete for cash prizes.
You register individually, but you always take part as a member of a team. Every participant fills in the organisers’ participant registration form themselves, with their own details, and accepts the terms of participation individually.
Solutions are developed and presented only by teams of 2 to 5 members; there are no individual solutions. If you don’t have a team, simply register and the Organising Committee will place you in one.
No. You can register without a team: the Organising Committee will place you in one, with the aim of interdisciplinary collaboration. Everyone takes part as a team member, though, because solutions are developed and presented by teams only.
Already have a team? Each member registers separately and gives the same team name, so that we can group you together. Each team has 2 to 5 members, from different scientific or professional fields.
No team yet? Register anyway, without giving a team name; the Organising Committee will place you in a team.
Each participant takes part only in the team in which they have registered or been placed.
The hackathon welcomes students, researchers and professionals interested in biology, artificial intelligence and data analysis.
Who is eligible: Natural persons aged 18 or over: students, researchers, members of the academic community, scientists, professionals and anyone else interested (Terms, Article 1).
Each participant registers individually, accepts the terms of participation and becomes a member of a team of 2 to 5 people from different scientific or professional fields — for example, biology or biochemistry knowledge combined with computational skills.
Do I need previous experience with computational tools?
Teams are interdisciplinary, so their members complement each other. The programme includes talks by experts that provide the necessary scientific and technical background, and technical mentors help with preparing input data, reading the outputs and assessing predictions. The preparation resources also include a guide to computational biology tools and a toolbox.
If you have never worked with structure prediction tools, it is worth trying a first prediction — for example on AlphaFold Server — before the hackathon.
BIOHackathon combines short talks with hands-on teamwork on specific cases and real challenges. Teams use computational tools to explore the cases, develop their own approach and propose well-founded solutions.
Key stages:
13 November 2026 — Website launch – Registration opens
30 November 2026 — Registration deadline
7 December 2026 — Team formation
9 December 2026 — Participants are informed of their team
10 December 2026 — Kick Start meetings of the teams with their mentors begin
15 December 2026 — Kick Start meetings of the teams with their mentors end
31 January 2027 — Proposal submission deadline
14 February 2027 — The Jury completes the evaluation of the proposals
26 February 2027: the presentation of the solution at the main event, following the procedure, timing and technical specifications set by the organisers.
A rule for everyone: state the main tools, data sources, libraries, models and third-party material you used, together with the key inputs and parameters.
Final presentation — suggested guide:
10minutes to present
Suggested slide structure:
The team and the idea: Team · Challenge · Proposed solution
The scientific problem: Scientific background · The problem · Why it matters · Hypothesis / research question · Available data
The approach: Methodology · Workflow · Input data · Complementary tools · Validation and limitations
Tools and results: How the relevant tools and databases were used (e.g. AlphaFold, UniProt) · What results emerged · How they were assessed · What they contributed to the solution · What the next steps are
Can I use third-party code, data or other material?
Yes, provided you have the right to use it for the purpose of your participation. Under the terms of participation:
you comply with the licences, terms of use, restrictions and attribution requirements of every tool, piece of software or dataset;
you cite and properly attribute every external source or third-party material you use substantially, in the presentation and/or the documentation of the solution;
you do not use confidential, proprietary or protected material for which you do not hold the necessary right or licence;
you do not use health data from which individuals can be identified, directly or indirectly; only fully anonymised or synthetic data from official, open scientific databases are allowed.
Yes. Participants follow the principles of scientific ethics, transparency, mutual respect and good-faith collaboration. Harassment, discrimination, intimidation and obstructing other people’s participation are not allowed. Knowledge sharing and collaboration between teams are encouraged, but must not lead to unauthorised copying or appropriation of other people’s work.
Grounds for exclusion include, for example, a material breach of the terms, plagiarism, submitting false or misleading information, deliberately falsifying data or results, unauthorised use of software, data or tools, a serious breach of the rules of ethics or safety, and any attempt to unduly influence the evaluation. Before an exclusion decision, the person concerned may set out their views in writing within 24 hours of being notified of the breach.
The Jury assesses the proposals and solutions against 4 criteria, with the following weights:
A. Relevance to the chosen challenge / Scientific and technical validity / Feasibility and potential impact35%
B. Innovation and originality25%
C. Sound and meaningful use of AI tools / Quality and documentation of the open-source code produced20%
D. Quality of the presentation and documentation of the solution20%
Each criterion is scored from 0 to 10; the final score is the weighted sum. In the event of a tie, the team with the higher score in criterion A ranks first; if the tie remains, criterion D decides.
The aim of the evaluation is to highlight solutions with real impact, an innovative approach, scientific validity, a direct link to the challenge and an effective presentation.
Yes. The following cash prizes are awarded to the winning teams:
1st prize€1,500
2nd prize€1,000
3rd prize€500
Each prize is paid in equal shares to the members of the winning team, into each member’s own bank account. Payment follows the applicable law and is subject to any taxes or statutory deductions; the necessary supporting documents may also be requested.
Those who create it — you and your team. Participants keep any intellectual or industrial property rights they hold in the original works, methodologies, code, analyses, presentations and other results they create within the Hackathon. Taking part does not transfer those rights to the organisers, the mentors or other participants; mentors, in particular, waive any intellectual property rights in the solutions of the teams they guide.
You grant the organisers a non-exclusive, royalty-free, worldwide and perpetual licence to use, present, publish and reproduce the deliverables, presentations and summaries of the solutions, for promotion, information and education. The licence does not include any right to exploit them commercially or to publish your full source code, confidential material or unpublished research data.
Presenting an idea or solution at the Hackathon does not give other participants any right to copy or appropriate it.
Presenting a solution in public may affect whether some results can be protected later (e.g. by a patent). If this concerns you, take the steps you need in good time.
VenueRegional Council Chamber (64 26is Oktovriou St., 546 27 Thessaloniki)
FormatIn person
Registration deadline30 November 2026
Before the main event, teams are formed, meet their mentors in the Kick Start meetings and submit their proposals, which the Jury evaluates — see the key stages.
By filling in the organisers’ participant registration form (opens in a new tab). Registration is individual: every participant registers with their own details and accepts the terms of participation individually.
With a team: give your team’s name; all members give the same name, so that we can group you together (2 to 5 members per team).
Without a team: register anyway; the Organising Committee will place you in a team.
Yes. Mentors register separately, as scientific or technical mentors, using the mentor registration form (opens in a new tab). They guide the teams as each team shapes and develops its approach.
Each team has 2 to 5 members from different scientific or professional fields, to encourage interdisciplinary collaboration. Every member registers individually, giving the team’s name; people who register without a team are placed in one by the Organising Committee. Each team appoints a representative, who is its main point of contact with the organisers.
One. Each team chooses one of the four antimicrobial-resistance axes:
AHealth
BFood
CAgriculture
DLivestock
Each axis comes with a short description and an indicative research question. The questions are not mandatory: each team may frame its own, as long as it is clearly linked to the challenge it has chosen.
Each team is supported by one scientific and one technical mentor. The Organising Committee does the matching, based on the teams’ needs, the relevance of each mentor’s expertise and their availability, taking any preferences into account.
Mentoring takes place online, according to the availability each mentor states. Mentors only advise: responsibility for the methodology, the results and the submission of the solution stays with the team.
Every participant submits only their own details, through the organisers’ registration form; the team name is used only to group members of the same team. How your information is processed is described in the privacy notice, together with your rights under the General Data Protection Regulation (GDPR).
AlphaFold predicts the 3D structure of a protein from its amino-acid sequence and gives every prediction confidence scores for each part of the structure. AlphaFold 3 can also model complexes of proteins with other proteins, nucleic acids, small molecules and ions.
What it does not do:
It gives a static snapshot: it does not capture dynamics or the alternative conformations a protein can adopt.
Intrinsically disordered regions come out with low confidence and should not be read as a defined structure.
It is not designed to predict the effect of point mutations or binding affinities.
Every prediction is a hypothesis that needs to be tested.
The indicative research questions of the challenges often involve mutations (e.g. in a carbapenemase such as KPC, or in the CYP51 protein). Differences between the reference protein and a variant can be subtle, so combine predictions with experimental structures and complementary tools.
A single protein: its amino-acid sequence, e.g. in FASTA format from UniProt.
A complex: every chain or molecule separately — proteins, DNA/RNA, ligands, ions — with the right number of copies.
A variant: the modified sequence (with the substitution or insertion), to compare with the reference enzyme.
AlphaFold Server supports a limited set of ligands and ions; for other small molecules, a local AlphaFold 3 installation accepts definitions as a CCD code or SMILES string.
Watch the numbering: mutation positions in β-lactamases are usually given in Ambler numbering, which may differ from the position in your own sequence.
They are the scores AlphaFold uses to estimate how reliable its own prediction is.
pLDDT0–100 · per residue (per atom in AlphaFold 3)
Local confidence for each part of the structure, usually shown on models with these colours.
507090
< 50Very lowOften a disordered region
50–70LowInterpret with caution
70–90ConfidentBackbone generally correct
> 90Very highAccurate backbone and usually side chains
PAEÅ · per residue pair
Predicted aligned error: the expected error in the position of one residue when the prediction is aligned with the true structure on another residue. Low values mean the relative placement of domains or chains is reliable.
pTM0–1 · whole structure
Overall confidence in the structure or complex. Values above 0.5 suggest that the overall fold may resemble the true one.
ipTM0–1 · interface
Confidence in the relative positions of the chains in a complex. Above 0.8: a confident prediction; below 0.6: likely failed; in between: a grey zone.
AlphaFold Server (opens in a new tab) — web access to AlphaFold 3, free for non-commercial use, with a daily job limit. The easiest way to get started.
AlphaFold DB (opens in a new tab) — ready-made predictions for more than 200 million proteins; check here before running a new prediction.
Some mentors have dual expertise and cover both areas. When an issue spans both, tell your mentor what you are trying to answer and what you have already tried.
Do computational tools replace experimental validation?
No. Using AI and computational biology tools such as AlphaFold does not replace scientific validation. Predictions are working hypotheses, to be checked against experimental data, comparisons and the literature.
In the final presentation, every team documents the tools, databases and sources it used, together with the key inputs and parameters, and presents how it validated its approach and what its limitations are.