How to get access

In this page you will find general information about getting access to the Life Science Grid and the National Dutch Grid infrastructure:

Local access to an LSG cluster

Granting local access to a Life Science Grid (LSG) cluster enables you:

If your research applies to one of the life science disciplines and your institute hosts a LSG cluster (see LSG clusters), you are eligible to obtain an account on your local LSG cluster.

To get an account on a local user interface, please send a request to your Designated Site Admin (see Locations and local support contacts) or contact us at

Access to the National Dutch Grid or LSG

Access to the Dutch Grid or the LSG clusters (including non-local access) allows for:

Researchers at SURF-affiliated institutes can apply for compute and storage capacity on the Grid by submitting the SURFsara application form. For scientists not affiliated to SURF, rates are based on tailor made packages. Specific details on obtaining accounts can be found in the Access Grid section of our website.

Please contact us at for any inquiry on our possibilities.

Estimate your resource needs

When you request to use the Grid you do so in the context of a project. A project is set to solve a problem, defined as some goals that you want to achieve, which includes a plan on how you will achieve those goals. For each project a suitable amount of resources will be allocated. You can work together with several people in the same project and using the same resource allocation.

In general, each project resource allocation involves:

  • an amount of compute time, measured in core·hours
  • an amount of storage space, for disk or tape or both
  • a start and end date for your project

In order for us to make a suitable allocation for a project, we need to know what your goals are and how you want to achieve those goals. That is why it is important for you to understand how to estimate the resources for your project.

For a proper estimation of resources requirements it is best to start with a few test runs of the code (if existing) on another system (e.g.: your laptop). The outcome of such tests will in many cases be sufficient to derive a total requirement for your larger-scale production runs. Sometimes a more elaborate process is needed to come to an estime, for example if the code does not exist yet of if changes to the existing code are still pending. Ideally you have been running a few representative samples of your runs before you file a resource request, in order to have some concrete information ready about the resources needed by your jobs, such as:

  • how long it takes to run a representative input scenario
  • how much space you need to store input, output and intermediate data
  • what the software requirements are (required software tools, libraries, compilers, etc)
  • how many scenarios (jobs) you need to run for a complete analysis

In case you don’t know how to prepare such an inventory, we would be happy to assist you with that.