Help & FAQ for beginners

Getting started & cost

Is BioNexus Hub really free?

Yes, completely. There is no paywall, no subscription, and no payment of any kind. You do not even need an account to read the lessons. It was built to make bioinformatics accessible to everyone.

I have never written code and barely remember biology. Can I still start?

Yes, this is built for exactly you. Begin with the Introduction lessons: what bioinformatics is, then the biology a coder needs, then your first 10 lines of Python. Each one assumes you know nothing and explains every term.

Do I need to be good at math?

No. You do not need advanced math to start. When a lesson needs a concept (like what a p-value means), it explains it from scratch in plain language.

Running the code (no install needed)

Do I need to install anything on my computer?

No. Every hands-on lesson runs free in your web browser. Some lessons even run Python right on the page (just press Run). Most use Google Colab, a free service that runs code in your browser with nothing to install. Installing software on your own machine is optional and only for later, when you want to work locally.

What is Google Colab, and is signing into Google safe?

Google Colab is a free Google service that runs coding notebooks in your browser, so you never install Python yourself. When you open a Colab notebook it may ask you to sign in with a normal, free Google account (the same kind you would use for Gmail). This is normal and free, you will not be charged. Signing in simply lets Google run the notebook and save your work.

Can I use VS Code (or Jupyter, PyCharm) instead of Google Colab?

Yes. The code is the same wherever you run it, so you can use any editor you like. We default to Google Colab because it needs zero setup, which is perfect when you are starting out. If you would rather work on your own computer in VS Code, Jupyter, or PyCharm, you can, but first you install Python (or R) and the needed packages yourself. See the Foundations setup lessons and the VS Code guide. In short: Colab is the easy, no-install path; your own editor is the "when you are ready" path. You can also download any Colab notebook and open it in VS Code or Jupyter later.

Will running code break or harm my computer?

No. Colab runs on Google's servers, not on your machine, so nothing you do there can harm your computer. Experiment freely, the worst that happens is an error message, which you just fix and re-run.

When something goes wrong

A code cell turned red and showed an error. What do I do?

First: do not panic. Errors are completely normal, every programmer, including experts, hits them constantly. They are information, not failure. Try these steps in order:

1. Read the last line of the red text. It usually names the actual problem (for example "NameError: name 'x' is not defined").
2. Check for small typos: a missing quote or bracket, a wrong capital letter, or wrong indentation (spaces at the start of a line).
3. Did you skip a cell? If it says something is "not defined," you may have run a later cell before an earlier one. Re-run the lesson from the top.
4. Restart and run again: in Colab, choose Runtime → Restart session and run all.
5. Search the error: copy the last line of the red text into Google. Someone has almost always hit the same thing.

Colab says "runtime disconnected," or an install is taking a long time.

Both are normal. Free Colab disconnects after a period of inactivity, just reconnect and re-run the first (setup) cell. The first time you install packages in a session, especially R/Bioconductor tools, it can take a few minutes; that is expected and only happens once per session.

Colab says "too many sessions."

You have other Colab notebooks still running. Open Runtime → Manage sessions, close the ones you are not using, and try again.

Getting help

Where can I ask a question or report a problem?

Use the feedback button at the bottom-right of every page, it reaches us directly. You can also visit the BioNexus Hub Facebook page. For broader community questions, experienced bioinformaticians answer on Biostars and Stack Overflow, but do not feel you have to start there; a beginner question is always welcome with us first.

I still feel overwhelmed. Any advice?

Go slowly and celebrate small wins. You do not need to understand everything at once. Do one short lesson, run one piece of code, and let it sink in. Consistency (a little, often) beats intensity. Everyone who codes today was once exactly where you are.