Using Anunna can strengthen research proposals by providing access to high-performance computing (HPC) and AI infrastructure for computationally demanding research. This page provides guidance and standard text that can be used in '''grant proposals, research papers, theses and other publications'''.

== Grant support ==
When applying for research funding, you can include Anunna as part of the computational infrastructure available to your project.

Depending on the requirements of the funding call, you may want to describe:

* the computational requirements of your project;
* the need for HPC and/or AI resources;
* the availability of Anunna at Wageningen University & Research;
* the expected computational workload and resources required;
* how access to Anunna will support the feasibility and impact of the proposed research.

=== Suggested text for grant proposals ===
The following text can be adapted for use in grant applications:<blockquote>'''High-performance computing infrastructure'''

The computational work within this project will make use of Anunna, the High Performance Computing (HPC) facility of Wageningen University & Research (WUR). Anunna provides access to high-performance CPU, GPU, memory and storage resources and supports computationally intensive research and AI applications.

Access to Anunna will enable the project to efficiently process and analyse large datasets and/or run computationally demanding models and simulations. The required computing resources will be made available through the Anunna facility in accordance with the applicable access and usage arrangements.</blockquote>For a proposal that specifically requires '''GPU or AI resources''', the text can be extended to describe the expected workloads, such as machine learning model training, inference, large-scale data processing or other GPU-accelerated applications.

=== Planning your computing requirements ===
For larger grant applications, we recommend discussing your expected computational requirements with the Anunna team during the proposal preparation phase. This can help you estimate the required CPU, GPU, memory, storage and running time and determine whether Anunna is suitable for the proposed workload.

Please contact the Anunna team if you need support in describing the required infrastructure or estimating your computational needs.

== Acknowledgement of Anunna ==
If you use Anunna resources for research that results in a publication, thesis, report or other research output, please acknowledge the facility.

Acknowledging the use of Anunna helps recognise the infrastructure and expertise that enabled the research and demonstrates the value and impact of the facility.

=== Suggested acknowledgement ===
We recommend using the following acknowledgement text:<blockquote>'''The authors acknowledge the use of the Anunna High Performance Computing facility of Wageningen University & Research for providing computational resources for this research.'''</blockquote>Where appropriate, you can also acknowledge the support provided by the HPC team:<blockquote>'''The authors acknowledge the use of the Anunna High Performance Computing facility of Wageningen University & Research for providing computational resources and technical support for this research.'''</blockquote>Please adapt the acknowledgement where specific individuals, projects or funding sources need to be recognised.

== Citing Anunna ==
Anunna should normally be acknowledged rather than cited as a scientific publication. If a publication makes substantial use of a specific Anunna service, software component or technical contribution, additional citations may be appropriate.

If you are unsure whether a specific publication or technical contribution should be cited, please contact the Anunna team.

== Reporting the use of Anunna ==
When reporting research supported by Anunna, it is useful to include information about the computational resources used. Depending on the publication or funding requirements, this may include:

* CPU or GPU resources used;
* approximate compute time;
* storage resources;
* relevant software or computational frameworks;
* significant technical support provided by the Anunna team.

This information helps demonstrate the contribution of research infrastructure to scientific output and supports the continued development of Anunna.

== Questions or support ==
If you are preparing a grant proposal and expect to make significant use of Anunna, or if you are unsure how to acknowledge Anunna in a publication, please contact the Anunna team.

For questions about computational requirements, grant applications or acknowledgement, please contact the Product Owner:

[mailto:alexander.vanittersum@wur.nl]

== See also ==
* [[Tariffs]]
* [[Cluster Architecture Overview]]
* [[Compute Hardware Overview]]
* [[How to Get Help]]

Grant Support & Acknowledgement

2026-08-28T15:13:42Z

Itter003:

Using Anunna can strengthen research proposals by providing access to high-performance computing (HPC) and AI infrastructure for computationally demanding research. This page provides guidance and standard text that can be used in '''grant proposals, research papers, theses and other publications'''.

== Grant support ==
When applying for research funding, you can include Anunna as part of the computational infrastructure available to your project.

Depending on the requirements of the funding call, you may want to describe:

* the computational requirements of your project;
* the need for HPC and/or AI resources;
* the availability of Anunna at Wageningen University & Research;
* the expected computational workload and resources required;
* how access to Anunna will support the feasibility and impact of the proposed research.

=== Suggested text for grant proposals ===
The following text can be adapted for use in grant applications:<blockquote>'''High-performance computing infrastructure'''

The computational work within this project will make use of Anunna, the High Performance Computing (HPC) facility of Wageningen University & Research (WUR). Anunna provides access to high-performance CPU, GPU, memory and storage resources and supports computationally intensive research and AI applications.

Access to Anunna will enable the project to efficiently process and analyse large datasets and/or run computationally demanding models and simulations. The required computing resources will be made available through the Anunna facility in accordance with the applicable access and usage arrangements.</blockquote>For a proposal that specifically requires '''GPU or AI resources''', the text can be extended to describe the expected workloads, such as machine learning model training, inference, large-scale data processing or other GPU-accelerated applications.

=== Planning your computing requirements ===
For larger grant applications, we recommend discussing your expected computational requirements with the Anunna team during the proposal preparation phase. This can help you estimate the required CPU, GPU, memory, storage and running time and determine whether Anunna is suitable for the proposed workload.

Please contact the Anunna team if you need support in describing the required infrastructure or estimating your computational needs.

== Acknowledgement of Anunna ==
If you use Anunna resources for research that results in a publication, thesis, report or other research output, please acknowledge the facility.

Acknowledging the use of Anunna helps recognise the infrastructure and expertise that enabled the research and demonstrates the value and impact of the facility.

=== Suggested acknowledgement ===
We recommend using the following acknowledgement text:<blockquote>'''The authors acknowledge the use of the Anunna High Performance Computing facility of Wageningen University & Research for providing computational resources for this research.'''</blockquote>Where appropriate, you can also acknowledge the support provided by the HPC team:<blockquote>'''The authors acknowledge the use of the Anunna High Performance Computing facility of Wageningen University & Research for providing computational resources and technical support for this research.'''</blockquote>Please adapt the acknowledgement where specific individuals, projects or funding sources need to be recognised.

== Citing Anunna ==
Anunna should normally be acknowledged rather than cited as a scientific publication. If a publication makes substantial use of a specific Anunna service, software component or technical contribution, additional citations may be appropriate.

If you are unsure whether a specific publication or technical contribution should be cited, please contact the Anunna team.

== Reporting the use of Anunna ==
When reporting research supported by Anunna, it is useful to include information about the computational resources used. Depending on the publication or funding requirements, this may include:

* CPU or GPU resources used;
* approximate compute time;
* storage resources;
* relevant software or computational frameworks;
* significant technical support provided by the Anunna team.

This information helps demonstrate the contribution of research infrastructure to scientific output and supports the continued development of Anunna.

== Questions or support ==
If you are preparing a grant proposal and expect to make significant use of Anunna, or if you are unsure how to acknowledge Anunna in a publication, please contact the Anunna team.

For questions about computational requirements, grant applications or acknowledgement, please contact the Product Owner:

[[Mailto:Alexander.vanittersum@wur.nl|Alexander.vanittersum@wur.nl]]

== See also ==
* [[Tariffs]]
* [[Cluster Architecture Overview]]
* [[Compute Hardware Overview]]
* [[How to Get Help]]

Grant Support & Acknowledgement

2026-08-28T14:56:12Z

Itter003:

Using Anunna can strengthen research proposals by providing access to high-performance computing (HPC) and AI infrastructure for computationally demanding research. This page provides guidance and standard text that can be used in '''grant proposals, research papers, theses and other publications'''.

== Grant support ==
When applying for research funding, you can include Anunna as part of the computational infrastructure available to your project.

Depending on the requirements of the funding call, you may want to describe:

* the computational requirements of your project;
* the need for HPC and/or AI resources;
* the availability of Anunna at Wageningen University & Research;
* the expected computational workload and resources required;
* how access to Anunna will support the feasibility and impact of the proposed research.

=== Suggested text for grant proposals ===
The following text can be adapted for use in grant applications:<blockquote>'''High-performance computing infrastructure'''

The computational work within this project will make use of Anunna, the High Performance Computing (HPC) facility of Wageningen University & Research (WUR). Anunna provides access to high-performance CPU, GPU, memory and storage resources and supports computationally intensive research and AI applications.

Access to Anunna will enable the project to efficiently process and analyse large datasets and/or run computationally demanding models and simulations. The required computing resources will be made available through the Anunna facility in accordance with the applicable access and usage arrangements.</blockquote>For a proposal that specifically requires '''GPU or AI resources''', the text can be extended to describe the expected workloads, such as machine learning model training, inference, large-scale data processing or other GPU-accelerated applications.

=== Planning your computing requirements ===
For larger grant applications, we recommend discussing your expected computational requirements with the Anunna team during the proposal preparation phase. This can help you estimate the required CPU, GPU, memory, storage and running time and determine whether Anunna is suitable for the proposed workload.

Please contact the Anunna team if you need support in describing the required infrastructure or estimating your computational needs.

== Acknowledgement of Anunna ==
If you use Anunna resources for research that results in a publication, thesis, report or other research output, please acknowledge the facility.

Acknowledging the use of Anunna helps recognise the infrastructure and expertise that enabled the research and demonstrates the value and impact of the facility.

=== Suggested acknowledgement ===
We recommend using the following acknowledgement text:<blockquote>'''The authors acknowledge the use of the Anunna High Performance Computing facility of Wageningen University & Research for providing computational resources for this research.'''</blockquote>Where appropriate, you can also acknowledge the support provided by the HPC team:<blockquote>'''The authors acknowledge the use of the Anunna High Performance Computing facility of Wageningen University & Research for providing computational resources and technical support for this research.'''</blockquote>Please adapt the acknowledgement where specific individuals, projects or funding sources need to be recognised.

== Citing Anunna ==
Anunna should normally be acknowledged rather than cited as a scientific publication. If a publication makes substantial use of a specific Anunna service, software component or technical contribution, additional citations may be appropriate.

If you are unsure whether a specific publication or technical contribution should be cited, please contact the Anunna team.

== Reporting the use of Anunna ==
When reporting research supported by Anunna, it is useful to include information about the computational resources used. Depending on the publication or funding requirements, this may include:

* CPU or GPU resources used;
* approximate compute time;
* storage resources;
* relevant software or computational frameworks;
* significant technical support provided by the Anunna team.

This information helps demonstrate the contribution of research infrastructure to scientific output and supports the continued development of Anunna.

== Questions or support ==
If you are preparing a grant proposal and expect to make significant use of Anunna, or if you are unsure how to acknowledge Anunna in a publication, please contact the Anunna team.

For questions about computational requirements, grant applications or acknowledgement, please contact the Product Owner:

'''Alexander van Ittersum'''

Alexander.vanittersum@wur.nl

== See also ==
* [[Tariffs]]
* [[Cluster Architecture Overview]]
* [[Compute Hardware Overview]]
* [[How to Get Help]]

Main Page

2026-08-28T13:48:45Z

Itter003: /* About */

2026-08-28T13:01:18Z

Itter003: /* About */

2026-08-28T11:23:04Z

Itter003:

Roadmap

2026-08-28T11:21:36Z

Itter003:

= Anunna Roadmap: How We Decide What to Work On =
The Anunna HPC team has a lot of ideas, wishes, requests and opportunities to work on. At the same time, our capacity is limited. Besides improving and changing Anunna, we also need to keep the day-to-day HPC service running.

This means we need to make deliberate choices about what we work on, when we work on it, and what we do not work on.

Our roadmap is the way we make these choices together with our users and key users.

== Why do we work with a roadmap? ==
There are several reasons why having a clear roadmap is important:

* There is a lot of work to do. If everything is important, nothing is important. We need to make choices and focus our effort where it creates the most value.
* Our capacity is limited. The HPC team is responsible not only for improvements and changes, but also for the day-to-day operation and support of Anunna.
* We are still learning. The Anunna team is continuously learning what works best for our users and for the team.
* Wishes and demands come in different stages of maturity. Some ideas are well understood and ready to act on, while others are still "green" and need more exploration. The roadmap process helps us distinguish between them.
* Every decision to do something is also a decision not to do something else. By making priorities explicit, we make these trade-offs visible.
* Our users should help decide what matters most. The HPC team has technical expertise, but our clients and users are best positioned to tell us where improvements will have the greatest value for their work.

The roadmap is therefore not simply a list of things the HPC team wants to do. It is a shared prioritisation process between the HPC team and the people who use Anunna.

== How does the roadmap process work? ==
We work with a six-month roadmap cycle. Twice a year, representatives of our users come together with the HPC team to discuss and prioritize the work for the coming half year.

The process starts well before the roadmap session itself.

=== 1. Build the longlist ===
We start with a longlist of User Stories.

A User Story describes a need or desired outcome from a user's perspective:<blockquote>As a [type of user],

I want [something],

so that [benefit or outcome].</blockquote>For example:<blockquote>As a researcher, I want to be able to monitor my jobs more easily, so that I can quickly identify jobs that are not progressing as expected.</blockquote>User Stories can cover both small improvements and larger topics. They can be written from any relevant perspective: researcher, data manager, software developer, HPC support, system administrator, or another stakeholder.

The important thing is that the story clearly describes who needs something, what they need, and why it matters.

=== 2. Prepare and prioritise the User Stories ===
Before a User Story is considered for the roadmap, we try to make sure that we understand it sufficiently well.

When preparing a story, we keep several questions in mind:

* What is the expected value? What business, research or user value would this deliver?
* What risk does it reduce or what opportunity does it enable?
* Why now? Is there a reason this needs to happen soon rather than later?
* Are there dependencies? Does this work depend on another change being completed first, or does other work depend on it?

This does not mean that every User Story needs a detailed business case. The purpose is to make the reasoning behind prioritization visible and understandable.

At this stage, the longlist can still be quite large.

=== 3. Vote: what matters most? ===
During the bi-annual roadmap session, every representative receives the complete longlist of User Stories.

Each representative reads through the stories and selects '''four''' User Stories that are most relevant from their perspective.

The voting is deliberately done from the perspective of the people represented in the session. Different users may value different things, and that is useful information.

The goal is not to find a mathematically perfect ranking. The goal is to identify the topics that have the strongest relevance across our user community.

Based on the voting, we reduce the longlist to a shortlist of approximately 10–12 User Stories.

=== 4. High-level estimation ===
The shortlist is then further refined by the HPC team. This is also done during the bi-annual roadmap session.

For each User Story, the team makes a high-level estimate of the effort and complexity involved. This is not intended to be a detailed project plan or a commitment to a precise number of hours.

The purpose is to understand the relationship between:

value × urgency × risk/opportunity × effort × dependencies

The HPC team does the technical estimation, while the client representatives observe the process and are encouraged to ask questions and provide feedback.

This is an important part of the process: the HPC team brings the technical perspective, while the users bring the perspective of value and impact.

== What comes out of the roadmap session? ==
At the end of the roadmap session, we have a clear and predictable set of User Stories for the coming six months.

These stories form the roadmap that the Anunna team will focus on.

The intention is to work through the selected User Stories one by one, rather than constantly switching between many competing priorities. This allows the team to focus its capacity and increases the likelihood that we actually finish the things we start.

The roadmap is therefore also a way of saying:<blockquote>"These are the things we believe will deliver the most value right now, and these are the things we will focus on."</blockquote>It does not mean that nothing else can happen during the six months. Operational incidents, security issues, urgent technical problems and genuinely time-critical opportunities may require us to change course.

However, such changes should be visible and discussed rather than happening simply because the latest request happened to arrive first.

== How can users influence the roadmap? ==
The most direct way to influence the roadmap is through the key-user group.

Key users help us understand what is important to the people using Anunna and bring different perspectives into the roadmap process. They participate in the bi-annual roadmap sessions and help determine which User Stories deserve attention.

You do not need to be an HPC expert to contribute. In fact, a key part of the role is bringing the user perspective into the conversation.

If you have an idea or a problem that you believe should be addressed, it can become a User Story and enter the longlist. Being on the longlist does not automatically mean that it will be implemented; it means that the idea is visible and can be considered as part of the prioritization process.

== Want to join the key-user group? ==
Would you like to help shape the future of Anunna and have a voice in deciding what the HPC team should focus on?

Please reach out to <nowiki>mailto:alexander.vanittersum@wur.nl</nowiki> and let him know that you would like to be part of the Anunna key-user group.

Your perspective helps us make better choices about where our limited capacity can create the most value for the Anunna community.

== See also ==

* [[Mission and Governance]]
* [[Maintenance and Management]]

Roadmap

2026-08-28T11:21:01Z

Itter003:

= Anunna Roadmap: How We Decide What to Work On =
The Anunna HPC team has a lot of ideas, wishes, requests and opportunities to work on. At the same time, our capacity is limited. Besides improving and changing Anunna, we also need to keep the day-to-day HPC service running.

This means we need to make deliberate choices about what we work on, when we work on it, and what we do not work on.

Our roadmap is the way we make these choices together with our users and key users.

== Why do we work with a roadmap? ==
There are several reasons why having a clear roadmap is important:

* There is a lot of work to do. If everything is important, nothing is important. We need to make choices and focus our effort where it creates the most value.
* Our capacity is limited. The HPC team is responsible not only for improvements and changes, but also for the day-to-day operation and support of Anunna.
* We are still learning. The Anunna team is continuously learning what works best for our users and for the team.
* Wishes and demands come in different stages of maturity. Some ideas are well understood and ready to act on, while others are still "green" and need more exploration. The roadmap process helps us distinguish between them.
* Every decision to do something is also a decision not to do something else. By making priorities explicit, we make these trade-offs visible.
* Our users should help decide what matters most. The HPC team has technical expertise, but our clients and users are best positioned to tell us where improvements will have the greatest value for their work.

The roadmap is therefore not simply a list of things the HPC team wants to do. It is a shared prioritisation process between the HPC team and the people who use Anunna.

== How does the roadmap process work? ==
We work with a six-month roadmap cycle. Twice a year, representatives of our users come together with the HPC team to discuss and prioritize the work for the coming half year.

The process starts well before the roadmap session itself.

=== 1. Build the longlist ===
We start with a longlist of User Stories.

A User Story describes a need or desired outcome from a user's perspective:<blockquote>As a [type of user],

I want [something],

so that [benefit or outcome].</blockquote>For example:<blockquote>As a researcher, I want to be able to monitor my jobs more easily, so that I can quickly identify jobs that are not progressing as expected.</blockquote>User Stories can cover both small improvements and larger topics. They can be written from any relevant perspective: researcher, data manager, software developer, HPC support, system administrator, or another stakeholder.

The important thing is that the story clearly describes who needs something, what they need, and why it matters.

=== 2. Prepare and prioritise the User Stories ===
Before a User Story is considered for the roadmap, we try to make sure that we understand it sufficiently well.

When preparing a story, we keep several questions in mind:

* What is the expected value? What business, research or user value would this deliver?
* What risk does it reduce or what opportunity does it enable?
* Why now? Is there a reason this needs to happen soon rather than later?
* Are there dependencies? Does this work depend on another change being completed first, or does other work depend on it?

This does not mean that every User Story needs a detailed business case. The purpose is to make the reasoning behind prioritization visible and understandable.

At this stage, the longlist can still be quite large.

=== 3. Vote: what matters most? ===
During the bi-annual roadmap session, every representative receives the complete longlist of User Stories.

Each representative reads through the stories and selects '''four''' User Stories that are most relevant from their perspective.

The voting is deliberately done from the perspective of the people represented in the session. Different users may value different things, and that is useful information.

The goal is not to find a mathematically perfect ranking. The goal is to identify the topics that have the strongest relevance across our user community.

Based on the voting, we reduce the longlist to a shortlist of approximately 10–12 User Stories.

=== 4. High-level estimation ===
The shortlist is then further refined by the HPC team. This is also done during the bi-annual roadmap session.

For each User Story, the team makes a high-level estimate of the effort and complexity involved. This is not intended to be a detailed project plan or a commitment to a precise number of hours.

The purpose is to understand the relationship between:

value × urgency × risk/opportunity × effort × dependencies

The HPC team does the technical estimation, while the client representatives observe the process and are encouraged to ask questions and provide feedback.

This is an important part of the process: the HPC team brings the technical perspective, while the users bring the perspective of value and impact.

== What comes out of the roadmap session? ==
At the end of the roadmap session, we have a clear and predictable set of User Stories for the coming six months.

These stories form the roadmap that the Anunna team will focus on.

The intention is to work through the selected User Stories one by one, rather than constantly switching between many competing priorities. This allows the team to focus its capacity and increases the likelihood that we actually finish the things we start.

The roadmap is therefore also a way of saying:<blockquote>"These are the things we believe will deliver the most value right now, and these are the things we will focus on."</blockquote>It does not mean that nothing else can happen during the six months. Operational incidents, security issues, urgent technical problems and genuinely time-critical opportunities may require us to change course.

However, such changes should be visible and discussed rather than happening simply because the latest request happened to arrive first.

== How can users influence the roadmap? ==
The most direct way to influence the roadmap is through the key-user group.

Key users help us understand what is important to the people using Anunna and bring different perspectives into the roadmap process. They participate in the bi-annual roadmap sessions and help determine which User Stories deserve attention.

You do not need to be an HPC expert to contribute. In fact, a key part of the role is bringing the user perspective into the conversation.

If you have an idea or a problem that you believe should be addressed, it can become a User Story and enter the longlist. Being on the longlist does not automatically mean that it will be implemented; it means that the idea is visible and can be considered as part of the prioritization process.

== Want to join the key-user group? ==
Would you like to help shape the future of Anunna and have a voice in deciding what the HPC team should focus on?

Please reach out to [[alexander.vanittersum@wur.nl]] and let him know that you would like to be part of the Anunna key-user group.

Your perspective helps us make better choices about where our limited capacity can create the most value for the Anunna community.

== See also ==

* [[Mission and Governance]]
* [[Maintenance and Management]]

Main Page

2026-08-28T11:20:06Z

Itter003:

2026-02-25T06:58:43Z

Itter003:

=== GUI Applications on Anunna ===
Anunna provides access to desktop environments and GUI-based applications to support interactive research workflows. The environment is built on Open OnDemand, an open-source web portal that connects users to HPC resources through a web browser. The platform enables secure job submission, interactive desktop sessions, file management, and access to applications without requiring command-line interaction.

=== Access ===
The portal is available at:

https://apps.anunna.wur.nl

=== Available Applications ===
All supported applications are accessible via the main menu bar within the portal.

The '''Featured Subset''' section highlights commonly used applications, including:
[[File:Featured subset Anunna GUI-apps.png|left|thumb|356x356px]]

* [[Using the File browser|File Browser]]

* [[Using the Shell|Shell Access to Anunna]]
* [[R Studio]]
* Active courses currently using Anunna resources

Additional applications may be available depending on user permissions and project allocations. They can be found in the Menu under "All Applications"
.[[File:Menu Bar Anunna GUI-apps.png|left|thumb]]

General overview

2026-02-25T06:58:30Z

Itter003: