1. Offline Analysis Framework Status & Plans BI TB 21/02/2016 Blaze – JJ – Stephen BE-BI

2. Offline Analysis Framework STATUSBI
OAF

3. An OAF GUI has been developed as command line alternative

4. GUI: Easy Snapshot easy selection
All BI related Public snapshots now automatically appear here as a possible choice. Just create one in Timber and it will appear in the list, ready to ‘report’.

5. GUI: ‘Old’ reports easy production
This option will trigger generation of the report that would have been produced at this date and time.
For instance, a dynamic report could be configured for data between ‘now’ and one hour before. Then, selecting this snapshot with ‘15/09/ :00:00’ as date selection will produce the report for data from ‘15/09/ :00:00 ’ to ‘15/09/ :00:00 ’.

6. GUI: Ready for (but not yet Open to) dedicated expert extra code, including expert alarms
This window allows specifying the name of a special expert function to execute at the end of the standard process. Corresponding code stays in a separate file (one per instrument, editable by the expert) and cannot impact other OAF functions.
We do not plan to open this door before Stage 1 is fully in use (see Plan chapter)…

7. GUI: Lower Resolution Report Production
This option will trigger the generation of a lower (but still proper) resolution report file for quick viewing and printing

8. GUI: Allows you to tune your report’s name
This window allows you to tune your report’s name (instead of the standard one)

9. OAF: Now supports ‘long term’ history

10. OAF: Now supports interactive plots for DB VECTOR (not in
OAF: Now supports interactive plots for DB VECTOR (not in .pdf reports of course)

11. Daily Machine (PSB, CPS, SPS, LHC) Status Reports are now produced

12. Some Extra Instrument Daily Status Reports have been added too…
For BSRA
For BSRT
For BOFSU
… We’ll have the occasion to see them during next TBs …

13. Offline Analysis Framework PLANSBI
OAF

14. Recall from previous TB: Coming Next
New stuff, so expect bugs, missing features… but let give it a try and chance as is to cover correctly its first purpose (status and aging) before seeking for more (absolute perf assessment). JJ is available to discuss and implement your wishes for status/aging reports for this first stage. Probably a lot of useful things can already be done there.
Possible complains from CO/DM due to our new activity on their DB.
We spoke to them. They are aware ...

15. Recall from previous TB: The Next Steps
Missing and foreseen features:
History features for easy long term monitoring on NUMERICS and VECTORNUMERICS
Handling of images (especially with dynamic dimensions)
Low resolution reports.
When aging/status reports will be properly covered, open the door (via a maintainable/efficient solution) to the configurable introduction of dedicated code by <instr/dataset> developed by expert…

16. Offline Analysis Framework PLANS 1/2
Thanks to Blaze and Stephen, Python 3 installation, including major libs (matplotlib, numpy, scipy, pandas…) is deployed and available for all BI on bdidev2.
OAF is ready to cover its full purpose with its GUI
But:
No one ( apart BOFSU team) contacted any of us 3 to know what we could do for their instrument or even where we were standing with our developments
No one showed concrete interest in the existing report follow-up
People are still developping such tools in the group. They never contacted us on the subject and are probably not even aware of our development and objectives.
So, stage 1 (i.e. basic and common ‘good shape’ check and survey) is not yet properly covered

17. Offline Analysis Framework PLANS 2/2
Despite OAF is now potentially ready to go to Stage 2, we will:
Keep supporting a common Python 3 (and libs) for the group usage on a powerful Linux machine, i.e. bdidev2
Not open the door towards expert/individual adds-on until we feel that Stage 1 has been honestly considered and evaluated as a first option for each individual cases.
In order to help you know, understand and appreciate what stage 1 OAF can or could already do for you (for free):
JJ Gras will remain available to discuss, prepare and configure new reports
JJ Gras will also monitor all these reports and extract and present any interesting observations as a recurrent topic of our future TBs (strange, bad and also hopefully good observations. See next slides).

18. LAST but not LEAST: OAF reports as recurrent TB topic
The Technical Board Mandate covers 2 main subjects:
Avoid duplicated or similar developments. Help and promote the adoption of standards.
Assess instrument performance with respect to requirements.

19. OAF reports as recurrent TB topic
In the context of this second point, a regular topic will be added to each TB where JJ Gras will:
Extract and show from OAF reports done since previous TB any strange, bad or good observations.
Report on any improvement or explanations found on previous TB observations tagged as priority issues by the TB.
Inform on new reports created or OAF features added (if any).

20. OAF reports: What I could show for instance…
Glitch on LHC BWS position reading

21. OAF reports: What I could show for instance…
Heavy use on PS BWS

22. OAF reports: What I could show for instance…
Differences between SYNC and IIR in BOFSU

23. OAF reports: What I could show for instance…
Comparison of BCTs in LHC over a full day (good but rare unfortunately)

24. OAF reports: What I could show for instance…
Evolution ‘history’ of BCTDCA/BCTDCB measurements (nice!)

25. OAF reports: What I could show for instance…
Evolution ‘history’ of BCT06 to BCT10 transmission in LIN2
Is this step due to OP improvement or just new BI calibration values?

26. OAF reports: What I could show for instance…
Differences between BCTFR and BQM bunch relative intensity measures

27. OAF reports: What I could show for instance…
Wrong setting of BCTFRB B1 bunch phasing

28. OAF reports: What I could show for instance…
BSRA abort gap population on B1 during stable beam

29. OAF reports: What I could show for instance…
Evolution of the sum of BLMS monitors during a ramp

30. OAF reports: What I could show for instance…
… See You Next Time