Analysis Mtg 181015
From Moller Wiki
Back to Main Page >> Analysis Software overview >> Analysis Meetings
previous meeting << >> following meeting
Meeting information
Meeting time: 4:00pm
BlueJeans calling instructions: Toll-Free Number (U.S.& Canada): 888-240-2560 International toll number: 408-740-7256 Other BlueJeans access phone numbers are listed at www.bluejeans.com/numbers Bluejeans CODE: 512 142 216 Bluejeans link: https://bluejeans.com/512142216
Agenda
- Brainstorming discussion: Parity mode brainstorming
- General issues
Attendance
Chat Log
Message from Wouter: Wouter is here too now Wouter is here too now Message from Wouter: sorry for being late sorry for being late Message from Wouter: Re: correlations: we need to determine correlations of everything against everything. That would have caught Qweak PMT DD from the start. Re: correlations: we need to determine correlations of everything against everything. That would have caught Qweak PMT DD from the start. Message from Wouter: (sorry, just typing some notes here, don' twant to interrupt te flow of the conversation) (sorry, just typing some notes here, don' twant to interrupt te flow of the conversation) Message from Wouter: Color-coded 2D correlations maps are very useful for many channels Color-coded 2D correlations maps are very useful for many channels Message from Wouter: We will need web-based run-level data quality plots that are easily accessible and browseable. We will need web-based run-level data quality plots that are easily accessible and browseable. Message from Wouter: We should track null asymmetries and widths better than we did for Qweak. We should track null asymmetries and widths better than we did for Qweak. Message from Wouter: YES! YES! Message from Wouter: Treating pattern as basic unit.- Pro: no sync issues, easier parallellization and data stream transfers, asymmetry widths can be calculated online (assuming A < Delta A).- Con: hardware errors can cause patterns to become out of sync, which would be unrecoverable. Treating pattern as basic unit.- Pro: no sync issues, easier parallellization and data stream transfers, asymmetry widths can be calculated online (assuming A < Delta A).- Con: hardware errors can cause patterns to become out of sync, which would be unrecoverable. Message from Wouter: Q: do we want a better way to deal with pedestals than what we did in Qweak? I remember that being a PITA and very manual process. Q: do we want a better way to deal with pedestals than what we did in Qweak? I remember that being a PITA and very manual process. Ciprian Gal Message from Ciprian Gal: you should speak up .. not sure anyone is looking at this :P .. also PITA could mean something else to people working in the injector ;) you should speak up .. not sure anyone is looking at this :P .. also PITA could mean something else to people working in the injector ;) Message from Wouter: I'm in a coffee shop, too much background noise, also, I'm just in brainstorming mode and this isn't supposed to be part of the flow of discussion. More riffing on tangents... I'm in a coffee shop, too much background noise, also, I'm just in brainstorming mode and this isn't supposed to be part of the flow of discussion. More riffing on tangents... Message from Wouter: By the time MOLLER runs we should consider how prevalent python is. By the time MOLLER runs we should consider how prevalent python is. Message from Wouter: Already in Qweak we had JF write quick offline QA scripts in python that would have been difficult in c++. Already in Qweak we had JF write quick offline QA scripts in python that would have been difficult in c++. Ciprian Gal Message from Ciprian Gal: I agree! i think all the browseable stuff could be done through python and a series of DBs I agree! i think all the browseable stuff could be done through python and a series of DBs Message from Wouter: We should consider how we do software release management on the analyzer: "release when feature ready" was not the best in Qweak. I think "periodic announced release" may be better. e.g. Japan release 2018.04, etc. We should consider how we do software release management on the analyzer: "release when feature ready" was not the best in Qweak. I think "periodic announced release" may be better. e.g. Japan release 2018.04, etc. Message from Wouter: Has someone tried merging Japan with Jana? Has someone tried merging Japan with Jana? Ciprian Gal Message from Ciprian Gal: Not sure what Jana had, but for online monitoring Kent prefers to go with the old happex thing which offers a lot of flexibility Not sure what Jana had, but for online monitoring Kent prefers to go with the old happex thing which offers a lot of flexibility
