- jlzhang's home page
- Posts
- 2024
- March (1)
- 2022
- 2021
- December (1)
- 2019
- April (1)
- 2018
- 2017
- 2016
- 2015
- December (1)
- November (1)
- September (3)
- August (1)
- May (1)
- April (1)
- March (4)
- February (5)
- January (3)
- 2014
- December (4)
- November (4)
- October (2)
- September (3)
- August (4)
- July (3)
- June (4)
- May (2)
- April (1)
- March (2)
- February (2)
- January (1)
- 2013
- My blog
- Post new blog entry
- All blogs
BEMC Software Coordinator Tasks
Updated on Thu, 2018-02-15 12:19. Originally created by jlzhang on 2018-02-15 12:10.
1. Preparation for the run
1.1 initialize database timeline
2. Online monitoring
2.1 Keep monitoring the online script running;
Note: Stop the monitoring jobs once the run concluded
3. Calibration
3.1 In-run calibration
4. Software maintenance
- Work together with BEMC software experts to maintain the BEMC related codes.
Helpful links:
1. Preparation for the run
1.1 initialize database timeline
- Copy previous year tables to a new timestamp which is provide by Software leader.
- for both "ofl" and "sim"
- scripts : Change timeOld to newer year, change timeNew for "ofl" and "sim" and run twice. Check from database browser.
- L2 Monitoring
- Trigger Database Monitoring (Ask starsuport@bnl.gov for Tech./permission help)
- BSMD Status Monitoring
- Note: Refer to the version used in the last year.
- Volunteers will be very helpful for the monitoring tasks
2. Online monitoring
2.1 Keep monitoring the online script running;
- monitoring scripts could crash some time, if happens, fix it immediately
- update timely based on everyday's monitoring
Note: Stop the monitoring jobs once the run concluded
3. Calibration
3.1 In-run calibration
- Once good data are taken, upload a new Status/pedestal tables.
- for the fast offline production
- QA'ed Status/pedestal tables should be made and uploaded to the database before data production. This task is more time consuming than the others. Helps from another collaborator/volunteer are usually needed.
- Upload BEMC trigger DB file once the run is ended.
4. Software maintenance
- Work together with BEMC software experts to maintain the BEMC related codes.
Helpful links:
- BEMC subsystem and it's sub-pages
- Slides or drupal blogs by previous SC: e.g. Kevin's , or search on drupal
- Kevin's slides on yearly tasks.
»
- jlzhang's blog
- Login or register to post comments