Some experiment specific monitoring links can be found in:

Offsite monitoring:

Are you submitting jobs ob the OSG? Or, your jobs running on the OSG have problems?
Have a look here.

Number of running/queued jobs at FZU is available through official OSG monitoring page[]=10189&gridtype=on&gridtype_1=on&active_value=1&disable_value=1

where all NOvA jobs runs in a queue named "nova". They also have local monitoring that shows number of available batch slots and number of jobs in each queue

but in a near future they will replace the current batch system (torque+maui) with htcondor and local monitoring will be different.

(Information provided by Petr on 11/10/15)


To clone the OPOS git repository

git clone ssh:///cvs/projects/offline_production_operations_service-opos

To commit some changes

git add --all
git status
git commit -m "Message describing the changes"
git push origin master


mac-120557:Sam pbuitrag$ git add --all
mac-120557:Sam pbuitrag$ git status
On branch master
Your branch is up-to-date with 'origin/master'.

Changes to be committed:
(use "git reset HEAD <file>..." to unstage)

renamed: .gitignore -> docs/.gitignore
new file: monitoring/.gitignore
new file: scripts/.gitignore
new file: test/.gitignore

mac-120557:Sam pbuitrag$ git commit -m "Fixing - second OPOS folder"
[master 34fbf2e] Fixing - second OPOS folder
4 files changed, 12 insertions(+)
rename Common/Sam/{ => docs}/.gitignore (100%)
create mode 100644 Common/Sam/monitoring/.gitignore
create mode 100644 Common/Sam/scripts/.gitignore
create mode 100644 Common/Sam/test/.gitignore
mac-120557:Sam pbuitrag$ git push origin master
Counting objects: 5, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 294 bytes | 0 bytes/s, done.
Total 3 (delta 0), reused 0 (delta 0)
To ssh:///cvs/projects/offline_production_operations_service-opos
9aaf302..34fbf2e master -> master
mac-120557:Sam pbuitrag$

To pull the last updated version of the remote repository

git pull

Useful links

The simple guide How to undo almost everything

Task Dashboard


How to use it:

  • A new task is created after agreeing with all the group.
    - It was created during a meeting.
    - It's not created during a meeting. The person creating it sends an email around to OPOS.
  • Tentatively: There will be a daily 15 minutes meeting to review board. We will decide the time of the meeting dinamically every day based on the availability of members of the group.

Looking forward:

Once the use of the dashboard gets traction in the team, we could start using the folllowing conventions if convenient:

  • Tickets colors represent the priority of the task in the following way:
    - Yellow - Critical
    - Green - High
    - Blue - Medium
    - White - Low
  • Dot colors represent the experiment/project this task is associated with, in the following way:
    - No dot - General task
    - Red - NOvA
    - Green - MINERvA
    - Blue - MINOS+
    - Purple - DUNE