Usage Tracking

Existing Group Owners / Project Leaders

If in the past you requested a group on LinGA systems you are considered a Project Leader. There is no command that can list the projects for which you are a leader.  If you are unsure if you are the Project leader of a specific group please contact the LinGA administrators (linga-adm@bu.edu).  As a project leader you need to submit information about your existing project by filling out the Request Project Account Form on LinGA website. This form is available only to BU faculty/staff and is password protected using their BU Kerberos credentials.

http://www.bumc.bu.edu/linga/access/accounts/request-project-account/

Existing projects were not defined with the current needs for tracking in mind.  Many existing projects may need to be reorganized or split into multiple projects.  If this is the case please fill in the form above for your existing projects as best as possible.  In the “Additional Information” section at the bottom of request-project-account please indicate the new projects that this existing group will be split into.  You will then need to fill in an additional request-project-account for each new group/project that you wish to define.  We recognize this will be complex for some larger existing projectd.  Please do not hesitate to set up a time to meet with the LinGA Administrators to discuss reorganization of your existing projects.

Defining New Projects

Project Leaders defining a new project must request a project account

http://www.bumc.bu.edu/linga/access/accounts/request-project-account/

Ideally each project will be attached to a grant but this is not required.  For example, students whose dissertation research is not directly grant funded should set up a project, with their faculty advisor as the project leader and no grant would be associated.  (Other dissertation research may fall under grant funded research and would be part of a grant associated project).  A grant may be associated with multiple projects if there are distinct scientific aims or distinct groups working under a single grant.  There may also be multiple grants associated with one project if the work is supported by multiple sources.

For an example on how to fill out Request Project Account form visit http://www.bumc.bu.edu/linga/documentation/usage/accounts/

Existing Users

All users must be a member of a project/group in order to run jobs. All  jobs will be associated with the user’s default group. Currently the default group for all LinGA users is their own username. Each user must select a new Default group which is associated with a project. You can request a default group by filling out the Change Default Project form on LinGA website. This form is password protected by a user’s BU Kerberos credentials.  This form lists all projects currently existing on LinGA.  The project leader must include you as a group member before a group can become your default group.  If you do not know what is the appropriate default group for you, you should contact the faculty member who supervises your work on LinGA.

http://www.bumc.bu.edu/linga/access/accounts/default-project/

New Users

  1. Must request an individual account http://www.bumc.bu.edu/linga/access/accounts/individual/
  2. Communicate with a project leader to associate your account with their project/group
  3. Once an account is granted and you become a member of projects/groups submit Change Default Project form http://www.bumc.bu.edu/linga/access/accounts/default-project/

Job Tracking / CPU Time

To see a listing of all groups you belong to run:

projects -lp

To see a listing of all groups associated with a project (i.e. list of defined projects) run:

qconf -sprjl

To see the group/project id of the current session run:

id -ng

To start a new session with a different group/project id run:

newgrp project_name

When submitting a job you must specify which project/group this job should be associated with.

    • If this job should be accounted towards the project associated with the group/project id  of the current session run
      qsub -P project_name job_script.qsub

      OR

      qrsh -P project_name
    • If this job should be accounted towards a project different from the group/project id  of the current session run 
      • Two Step:
        newgrp other_project_name
        qsub -P other_project_name  job_script.qsub
        OR
        qrsh -P other_project_name 

      • One Step
        sg other_project_name “qsub -P other_project_name  job_script.qsub”
        OR

        sg other_project_name “qrsh -P other_project_name”

      NOTE: “-P” option added to the qsub command will only be required during the first few months of the usage tracking implementation. It is required to enforce usage tracking from the queuing system. After all projects have been defined and all users have selected a default group/project this requirement will be lifted. Then, if a user does not specify a new session with a different group/project id or does not use sg command, usage will be accounted towards user’s default group/project.

      For an example on how to submit jobs and tag them by project/group visit http://www.bumc.bu.edu/linga/documentation/usage/jobs/

      Storage Tracking

      The requirement to track usage via projects coincides with expanded storage on LinGA coming online.  Therefore, there will be a reorganization of storage tied to definition of projects.  Once a project has been associated with a group, the group’s shared folder will move:

      From /data/share/group to /protected/projects/group

      Similarly, once a user has selected a default project her/his personal data will move:

      From /data/home/user to /protected/individuals/user

      To maintain backwards compatibility for existing groups during a transition period a symbolic link will point

      /data/share/old_group -> /protected/projects/new_project