This page will serve as documentation for several yearly tasks. Not all of these are spin-pwg related tasks, but should be documented somewhere public, and then can be linked elsewhere if necessary. It's a work in progress currently, but hopefully soon all bullets below will be filled out with information.

1.) CDEV Monitoring:
If the current run is a polarized (proton) run, then CDEV should be running - and is generally associated with the spin PWG. This code grabs spin information output by C-AD, and stores it into a MySQL database for use later after the run. This code is documented year-to-year on the online machines. Currently, if one logs into onl02, then the information for the most recent cdev run (2013) can be found in

/ldaphome/onlmon/cdev2013/README

This will get one started with the code, and teach them how to start it running, barring any new issues. It should be updated yearly with any kind of issues that pop up, and could come up again in the future.

After the run the CDEV information will be used to retreive the spin information from the MySQL database, and then upload that to the database where it's used in MuDst, etc. This comes in two steps:

- Produce runlist and QA spin patterns
- Upload results to star database

2.) L2 Monitoring:
Necessary Files: L2 Monitoring and Pedestal Documentation

The URL above sends you to a blog post which has the most recent (as of 2/12/2015) version of the L2 monitoring and pedestal documentation. The relevant sections for the overall monitoring scripts are the introduction to Section 1, and then Section 1.1 will give the instructions on how to start the L2 monitoring code.

3.) L2 Pedestal Monitoring and Updates:
Necessary Files: L2 Monitoring and Pedestal Documentation

The URL above sends you to a blog post which has the most recent (as of 2/12/2015) version of the L2 monitoring and pedestal documentation. The relevant sections for the pedestal monitoring and updating are the introduction to Section 1, and then Section 1.2 will give the instructions on how to monitor and update the pedestals for L2.

4.) BEMC Trigger Database Monitoring:
Necessary Files: Documentation for setting up BEMC online trigger database monitoring code

The above documentation isn't extremely expansive, but does get the new user started with the code, and points them to the appropriate place to get an enumerated list of steps that gets the code going. In principle, this code is very simple to set up and keep running, so long as no issues arise.

This task shouldn't be ignored. It'll either be run by the EMC software coordinator or a dedicated monitor, and should be checked daily for validity and to ensure proper execution of the code (i.e. reviewing the log files.)

5.) BSMD Pedestal Monitoring:
Necessary Files: Documentation for setting up and running BSMD monitoring code

This monitoring tasks produces the BSMD Pedestal PDFs, as well as monitoring plots run-by-run, and can be found here. The code is simple to set up and run, barring any issues. There are, though, a few issues that persist and are noted in the above documentation. The code will compile and run with these issues, but should be investigated in the future when time allows.

One should update these instructions on another blog accordingly for the appropriate year.

6.) BEMC Status/Pedestal Tables
Necessary Files: Documentation on creation and QA of offline BEMC status/pedestal tables

This task is particularly important to get done before production because the vertex finder uses tower statuses. Thus, they should be up to date before production begins. This code can be executed during the running period, but as it uses files from each fill it's best to wait till the end of the run to make the status and pedestal tables (but before production!). This task will be headed up by the BEMC software coordinator, but will involve an "assistant" which will be from the spin-pwg community (in general) if the most recent run was dedicated to spin (i.e. pp running). Thus the instructions for the usage of the code is included here for those helpers as well as future software coordinators.