June 2013: S&C week at CERN:
- presented status and plans for DEFT
- staged approach to commissioning in late 2013
- Web UI can be developed in parallel, facilitates team effort
Meetings at CERN:
- Nurcan and Johannes: requirements for the Analysis application of DEFT
- No fundamental difference between production and analysis
- More details in previous entries in this blog
- Baranov, Sargsyan, Potekhin, Klimentov, Stradling: machine provisioning, software installation and general setup of the Web service for the DEFT UI
Development:
- Bug fixes and additional functionality in deft-core (both in CLI and Oracle interface), meta-task storage
- DB Insertion performance testing
- Initial test drive of Django 1.4 and some of the new semantics since 0.96 which was used in previous apps
- Import of DEFT schemas into Django ORM and validation of database access from the data model (with Oracle RDBMS); created HTML templates for initial dev effort
- Integration of task numbering in JEDI: tested with ATLAS_PANDA.DEFT_TASK_SEQ under ATLAS_PANDA, and also PRODSYS2_TASK_ID_SEQ (the DEFT/JEDI seq.)
- Changed schema to better handle time stamps
- Added attributes to improve the schema
- DEFT Web UI: added JSON serialization to the app
- Tested additional Python modules installed on voatlas270 in order to enable running deft-core on that machine
Documentation:
- Created and maintained a TWiki page for the DEFT Web UI.
- Documented the DEFT meetings
- Coordination with A.Petrosyan: since JEDI monitoring is not in the
coding stage yet, it makes sense to integrate the effort, and benefit
from easier cross-reference of the data.
No comments:
Post a Comment