Advanced User Support

Advanced User Support offers help that goes beyond the general (basic) user support to provide specialised and more in-depth competence to a research group or community.

  • Service description

    AUS - Service description

    What is Advanced User Support?

    Advanced user support offers help that goes beyond basic user support to provide specialised and  more in‐depth competence to a research group or community. Advice and dedicated efforts from highly competent IT experts can boost the potential exploitation of HPC resources and data services. Ultimately, the advanced user support should contribute to effective and optimal use of the national computing and data‐storage facilities.

    Three types of Advanced User Support

    Advanced user support are classified in Discipline specific AUS and Project-based AUS. The two categories are different in terms of:

    • Who initiates the support
    • Length of support
    • Amount and type of support
    • Local involvement and commitment
    • Funding
    • Plans, follow-up and documentation

    In addition, we also offer other category - User Liason AUS. 

  • Various AUS Types

    AUS Types

    Project-based Avanced User Support

    Project-based AUS can be the sole initiative of a researcher or a science area. The Resource Allocation Committee may grant 2-3 PMs spent over a maximum of 6 months, but is open to consider larger projects. The expected results should preferably have value and benefits beyond the project itself. The exception is for new science areas that need help to start using e-infrastructure. 

    Project-based AUS can for example be:

    • Large projects requiring lots of CPU hours or large storage space in which AUS may ensure that resources are used most efficiently
    • Help to optimize the code with parallelization to use many cores
    • Support to develop and implement special extensions to a data management plan
    • Establish the criteria and plan for the execution of an archive-wide conversion of all data to new formats as part of the data preservation plan

    The RFK considers the following evalution criteria:

    • Clarity, completeness and quality of the proposal
    • The (expected) impact of the proposed activity on addressing the scientific challenge, on the relevant user community at large, as well as on application software, in terms of performance, functionality and/or usability
    • Feasibility and risk assessment, in particular with respect to timely and successful completion of the project.
    • The in-kind or cash contribution to support the staff that will complete the proposed activity

    Discipline-specific Avanced User Support

    Discipline-specific AUS can be initiated in cooperation between Uninett Sigma2 and the universities, with a science discipline focusing on the need for more long-term support. Such AUS-es can have allocations of more than 12 PMs spent over a maximum of 2 years.

    Examples of Discipline-specific AUS:

    • Survey (and restrict) and broad classification of the existing data
    • Create and/or implement data-plans
    • Define META data and storage formats
    • Assess and deploy suitable tools
    • Define Librarian function and/or perform it for a shorter period (  months)
    • Establish portal(s)
    • Major rewriting/adaption of code for new architectures
    • Investigate the latest development in HPC for an area and write a proposal for implementation to consider for new applications
    • Responsibility for the application portfolio

    User Liaisons conducting Advanced User Support 

    In some cases, the ultimate expert on a specific application or application area is a user and not someone within the Metacenter. Typically, this user is the go-to person for a whole user group or community already. When this particular super expert has time and motivation we may benefit from letting this user support his/hers own community/application and act as a user liaison.

    The user liaison is given suitable access and compensating for time spent supporting other users. In addition, the user liaison should work closely with and augment Application Management. Thus, the result should be a win-win for both the user community and the Metacenter.

  • Who can get access?

    AUS - Who can get access?

    Who can apply for Advanced User Support?

    In general, the AUS-service is available to staff and students at Norwegian universities and university colleges.

    Researchers in independent research institutes may also gain access to this service, provided that their work is funded by public grants and meets requirements for scientific publication.

    More specific information about the target groups of the various categories of advanced user support can be found on the AUS Types-page. 

  • Conditions for access?

    AUS - Conditions

    Metacenter is the main contributor

    The Metacenter is the main contributor of performing advanced user support.

    The people performing the AUS should as a rule be employed by a Metacenter at a university, exceptions to this rule need approval from Sigma2. The focus of the Metacenter is to work closely with the researchers in order to help them to utilize the HPC and storage resources in the best possible way.

    HPC or storage project needed

    In addition, applicants for advanced user support should be responsible for an on-going project on the HPC and/or data storage resources, or have the intention to become responsible for such project.

     

  • Apply for AUS

    AUS - Apply for AUS

    Application form

    Download the application form and fill in the project description 
    All fields in the application must be completed.

    The application must be sent (in Word or PDF format) by email to
    sigma2@uninett.no.

    Work plan

    A work plan be submitted once the applicant has received a positive evaluation. The plan must contain a time schedule and milestones from the start to completion of the project.

    The applicant and the person(s) carrying out the work must agree on the plan before it is submitted.

    Progress report

    A progress report must be submitted at regular intervals by the project responsible.

    • The frequency of reporting depends on the length of the project period. Progress must be reported at least once every four months.
    • Reporting dates must be specified in the project plan. 

    Deviations from the objectives of the project, original project plan, and expected results must be reported as well as any corrective action taken. Each progress report must be approved by the project responsible and the person(s) carrying out the work before it is submitted.

    Final report

    A final report must be submitted at the end of the project.

    All final reports will be made available to the Resource Allocation Committee and the Sigma2 Board. Final reports may be referenced during the evaluation of future applications for advanced support.

AUS - Service description

What is Advanced User Support?

Advanced user support offers help that goes beyond basic user support to provide specialised and  more in‐depth competence to a research group or community. Advice and dedicated efforts from highly competent IT experts can boost the potential exploitation of HPC resources and data services. Ultimately, the advanced user support should contribute to effective and optimal use of the national computing and data‐storage facilities.

Three types of Advanced User Support

Advanced user support are classified in Discipline specific AUS and Project-based AUS. The two categories are different in terms of:

  • Who initiates the support
  • Length of support
  • Amount and type of support
  • Local involvement and commitment
  • Funding
  • Plans, follow-up and documentation

In addition, we also offer other category - User Liason AUS. 

AUS Types

Project-based Avanced User Support

Project-based AUS can be the sole initiative of a researcher or a science area. The Resource Allocation Committee may grant 2-3 PMs spent over a maximum of 6 months, but is open to consider larger projects. The expected results should preferably have value and benefits beyond the project itself. The exception is for new science areas that need help to start using e-infrastructure. 

Project-based AUS can for example be:

  • Large projects requiring lots of CPU hours or large storage space in which AUS may ensure that resources are used most efficiently
  • Help to optimize the code with parallelization to use many cores
  • Support to develop and implement special extensions to a data management plan
  • Establish the criteria and plan for the execution of an archive-wide conversion of all data to new formats as part of the data preservation plan

The RFK considers the following evalution criteria:

  • Clarity, completeness and quality of the proposal
  • The (expected) impact of the proposed activity on addressing the scientific challenge, on the relevant user community at large, as well as on application software, in terms of performance, functionality and/or usability
  • Feasibility and risk assessment, in particular with respect to timely and successful completion of the project.
  • The in-kind or cash contribution to support the staff that will complete the proposed activity

Discipline-specific Avanced User Support

Discipline-specific AUS can be initiated in cooperation between Uninett Sigma2 and the universities, with a science discipline focusing on the need for more long-term support. Such AUS-es can have allocations of more than 12 PMs spent over a maximum of 2 years.

Examples of Discipline-specific AUS:

  • Survey (and restrict) and broad classification of the existing data
  • Create and/or implement data-plans
  • Define META data and storage formats
  • Assess and deploy suitable tools
  • Define Librarian function and/or perform it for a shorter period (  months)
  • Establish portal(s)
  • Major rewriting/adaption of code for new architectures
  • Investigate the latest development in HPC for an area and write a proposal for implementation to consider for new applications
  • Responsibility for the application portfolio

User Liaisons conducting Advanced User Support 

In some cases, the ultimate expert on a specific application or application area is a user and not someone within the Metacenter. Typically, this user is the go-to person for a whole user group or community already. When this particular super expert has time and motivation we may benefit from letting this user support his/hers own community/application and act as a user liaison.

The user liaison is given suitable access and compensating for time spent supporting other users. In addition, the user liaison should work closely with and augment Application Management. Thus, the result should be a win-win for both the user community and the Metacenter.

AUS - Who can get access?

Who can apply for Advanced User Support?

In general, the AUS-service is available to staff and students at Norwegian universities and university colleges.

Researchers in independent research institutes may also gain access to this service, provided that their work is funded by public grants and meets requirements for scientific publication.

More specific information about the target groups of the various categories of advanced user support can be found on the AUS Types-page. 

AUS - Conditions

Metacenter is the main contributor

The Metacenter is the main contributor of performing advanced user support.

The people performing the AUS should as a rule be employed by a Metacenter at a university, exceptions to this rule need approval from Sigma2. The focus of the Metacenter is to work closely with the researchers in order to help them to utilize the HPC and storage resources in the best possible way.

HPC or storage project needed

In addition, applicants for advanced user support should be responsible for an on-going project on the HPC and/or data storage resources, or have the intention to become responsible for such project.

 

AUS - Apply for AUS

Application form

Download the application form and fill in the project description 
All fields in the application must be completed.

The application must be sent (in Word or PDF format) by email to
sigma2@uninett.no.

Work plan

A work plan be submitted once the applicant has received a positive evaluation. The plan must contain a time schedule and milestones from the start to completion of the project.

The applicant and the person(s) carrying out the work must agree on the plan before it is submitted.

Progress report

A progress report must be submitted at regular intervals by the project responsible.

  • The frequency of reporting depends on the length of the project period. Progress must be reported at least once every four months.
  • Reporting dates must be specified in the project plan. 

Deviations from the objectives of the project, original project plan, and expected results must be reported as well as any corrective action taken. Each progress report must be approved by the project responsible and the person(s) carrying out the work before it is submitted.

Final report

A final report must be submitted at the end of the project.

All final reports will be made available to the Resource Allocation Committee and the Sigma2 Board. Final reports may be referenced during the evaluation of future applications for advanced support.

Projects with advanced user support from Sigma2