The fate of a cell is ultimately the product of the regulation of its genes. Gene regulation is a coordinated process acting at multiple levels of which transcription and translation are the most prominent. The Valen group is dedicated to the fundamental question of how transcription and translation is integrated to obtain the desired protein abundance. The recent development of high-throughput next generation sequencing techniques to monitor both active translation and transcription has made it possible to study this connection at the genome scale.

This project aims to elucidate the links between regulation of translation and transcription. The applicant will analyze next generation sequencing data and model gene regulation on a genome-wide level to identify the features that affect the translational output of transcripts. The work will be done in close collaboration with experimental scientists who will test the predictions of the computational models.

Additional information on the position can be obtained by contacting Eivind Valen (eivind.valen@ii.uib.no).

The research fellow must take part in the University’s approved PhD program leading to the degree within a time limit of 3 years. Application for admission to the PhD program, including a project plan outline for the training module, will be worked out in collaboration with the research group in question.

In total, the fellowship period is 4 years, 25 % of this will be allocated to teaching and/or administrative duties. The fellowship period may be reduced if the successful applicant has held previous employment as a research fellow or similar.

http://www.jobbnorge.no/en/available-jobs/job/102235/research-fellow-phd-candidate-in-computational-biology-2-positions

The pipeline is built using Nextflow, a workflow tool to run tasks across multiple compute infrastructures in a very portable manner. It uses Docker/Singularity containers making installation trivial and results highly reproducible. The Nextflow DSL2 implementation of this pipeline uses one container per process which makes it much easier to maintain and update software dependencies.

Address of the bookmark: https://github.com/AusARG/pipesnake

1. Make friends with local bioinformatics groups
2. Talk to your computing group
3. Obtain clear expectations
4. Rewrite your job description
5. Papers
6. Attend bioinformatics meetings
7. Try first, ask later

Address of the bookmark: http://biomickwatson.wordpress.com/2013/04/23/a-guide-for-the-lonely-bioinformatician/

Why Bioinformatics Matters More Than Ever

Every day, our world generates massive amounts of biological data—from genome sequences to microbiome profiles to real-time pathogen surveillance. Hidden within these datasets are the answers to some of the greatest challenges humanity faces: emerging diseases, antimicrobial resistance, environmental stress, genetic disorders, sustainable agriculture, and more.

Bioinformatics isn’t just a skill.
It’s the language of the future of biology.

By mastering it, you give yourself the power to:

Decode genomes and understand life at its most fundamental level

Identify patterns no microscope could ever reveal

Predict disease outbreaks before they occur

Accelerate drug discovery with computational precision

Contribute to open-source tools that empower scientists worldwide

You don’t just follow science—you drive it.

Every Expert Was Once a Beginner

Many newcomers feel intimidated. Command-line interfaces. R scripts. Python packages. Next-generation sequencing data. Complex machine learning models.

But here’s the truth: every bioinformatician started exactly where you are now—curious, unsure, but excited.

No one writes perfect code on day one.

No one understands genomics pipelines immediately.

What makes you a bioinformatician is not perfection, but perseverance.

When your script throws a cryptic error…
When your data refuses to format…
When your pipeline runs for 6 hours only to crash…

Remember: this is part of the journey.
Every error teaches you. Every retry strengthens you. Every breakthrough energizes you.

Bioinformatics Is Not Just a Career—It’s a Mindset

It’s the mindset of:

Problem-solving.

Continuous learning.

Turning chaos into clarity.

Seeing what others can’t.

Bioinformaticians are detectives of biological complexity. You sit at the intersection of innovation, using tools that can shape public health, medicine, agriculture, and ecology. Few fields give you such direct impact on the world.

Your Contribution Matters

As you work on your script, pipeline, genome, or model, remember:

Somewhere, your analysis might contribute to:

A new therapy

A faster diagnostic test

A better understanding of a pathogen

A more resilient crop

An open-source dataset that helps thousands

A discovery that rewrites textbooks

Your code may be small, but its ripple effect is powerful.

The Future Is Bioinformatics—And You Are Part of It

The world is shifting. Wet labs are integrating AI. Hospitals rely on genomic insights. Farmers use gene-level predictions. Governments monitor disease in real time. Students launch pipelines that become global tools.

This is a golden era—and you are not late.
You are exactly where you need to be.

Keep Pushing. Keep Learning. Keep Discovering.

Bioinformatics is a journey filled with challenges, but also with unmatched rewards.

So the next time you feel stuck, frustrated, or overwhelmed, remember:
You’re building the science of tomorrow.

Be proud. Stay curious. Keep going.
Your work matters more than you think.

Research Area

We are interested in the development of the statistics and computational methods for the analysis of this data in breast cancer.
We have worked on probabilistic models for subcellular localization, protein-protein interactions, and problems related to chemical genomics.
We are interested in the development of bioinformatics/biostatistical methodology in the analysis of epigenetic/epigenomic data.
We are interested in integrative bioinformatics approaches to learn the gene, gene products, interactions, and regulatory mechanisms involved in mental retardation.

Link @ http://www.mcgill.ca/mcb/

The next step after reading genetic code is writing a script to analyse and explore the hidden information. This tutorial is aimed to introduce you new biological programming languages with their packages/libraries, and assist in your scripting work.

Navigate the sub-section of this page [ see right hand side of the page for it ]

17 Nov 2013 -22 Nov 2013

More at http://events.embo.org/13-large-scale-data/

Online Registration: https://www.conference-service.com/pc13-47/welcome.cgi

Find more detail news at http://www.forbes.com/sites/erincarlyle/2013/10/30/carlos-slim-gives-another-74-million-to-make-genomic-research-less-ethnically-biased/?utm_campaign=forbesfbsf&utm_source=facebook&utm_medium=social

Tasks:  239 total,   1 running,  238 sleeping,   0 stopped,   0 zombie

This line tells you how many processes are running. If you are using laptops machines it’s not so interesting because you really are the only one using this machine.

Cpu(s):  0.0%us,  0.0%sy,  0.0%ni,100.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st

This line contains the CPU load. The first two numbers are how busy the system is doing computation (“us” stands for “user”) and how busy the system is doing system-y things like accessing disks or network (“sy” stands for “system”). We’ll talk more about this later.

Mem:   49457320k total,    3492174k used,  14535596k free,    1435148k buffers

This should be easy to understand – how much memory you’re using!

Swap:   539356k total,   28332k used,   836562k free,    29862014k cached

Swap is just on-disk memory that can be used to “swap” out programs from main memory. Again, we’ll talk about this later.:

PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
  1 root      39   19  0  0  0 S  0.0  0.0   246:57.22 kipmi0
  2 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/0

And... finally! What’s actually running! The two most important numbers are the %CPU and %MEM towards the right, as well as the COMMAND. This tells you how compute- and memory-intensive your program is. Right now, nothing’s running so the numbers aren’t very interesting, but just wait until we run something...