[Dsg-engineering] today's agenda

[Aaron Brown]

Okay.
So, just be clear and explicit, the meetings are as follows:

Monday - Phoebus (where we discuss all things Phoebus)

Tuesday - Engineering (where we discuss all projects)

Wednesday - General (where we discuss the previous week's work and other administrative topics)

Thursday - SICOM (where we discuss simulations and software - plans, testing, and issues)


This is the scope for all meetings going forward?

I'm sorry if this is too much, but I just want to be sure of what the expectations for these meetings are.


Thanks,

Aaron

________________________________
From: Amrit Yegneswaran <yeg at jlab.org>
Sent: Tuesday, November 19, 2024 11:59 AM
To: Aaron Brown <ambrown at jlab.org>; dsg-engineering at jlab.org <dsg-engineering at jlab.org>
Subject: Re: today's agenda

there are two groups in DSG
i'm not sure whether i should use the term engineers; let's say the so-called and so-hoped core expert group (aaron, pablo, brian, tyler, and peter)  where each one is apprised of what the technical issues are and can pitch in if needed. as per the motto knowledge is power (not ignorance is bliss)

like in soccer (5 forwards, 3 halfbacks, 2 fullbacks and one goalee. we never replaced the second fullback) (see my first talk for dsg) where the ball can be passed seamlessly from one forward to another.

[cid:156f6b5c-c0e6-4114-8cfb-7fa22a1ba9b8]

Like without my asking you or pablo requesting you, when you are aware that pablo has to make a gradient plot in python, you send him your version of the program. if someone were to request a change in the ECAL program in december without being told to do so pablo could do it, etc.

then there are the assistant experts mary ann, mindy marc and george, who should be aware of which way the wind blows. shouldn't be, any way the wind blows doesn't really matter to me.

phoebus expert + assistant expert quorum: aaron, pablo, brian, tyler, peter, and mary ann
sicom expert + assistant expert quorum: aron, pablo, brian, tyler, peter, marc, and george
dirc expert + assistant expert quorum: aron, pablo, brian, tyler, peter, marc, george
rich expert + assistant expert quorum: aron, pablo, brian, tyler, peter, george, marc
ecal expert + assistant expert quorum: aron, pablo, brian, tyler, peter, george, marc
anyone who wishes to join a meeting is welcome like, patrizia, mindy, thia, .....

engineering meeting and summary meeting is for the whole group  to update the idiot who is missing from berkley.


________________________________
From: Aaron Brown <ambrown at jlab.org>
Sent: Tuesday, November 19, 2024 10:26 AM
To: Amrit Yegneswaran <yeg at jlab.org>; dsg-engineering at jlab.org <dsg-engineering at jlab.org>
Subject: Re: today's agenda

Hi Amrit,

I think I need some clarification on the scope of each meeting:

Monday - Phoebus (where we discuss all things Phoebus)
Tuesday - Engineering (where we discuss hardware - plans, testing, and issues)
Wednesday - General (we discuss all projects and other administrative topics)
Thursday - SICOM (where we discuss simulations and software - plans, testing, and issues)

Each meeting, with the exception of the Wednesday meeting, was supposed to be a "working meeting" wherein we work through problems or workout upcoming plans to move projects forward. More informal...

Is this not the case anymore?
Do we need to make a slide for each project for every meeting, or just the Engineering meeting?

Thanks,
Aaron
________________________________
From: Amrit Yegneswaran <yeg at jlab.org>
Sent: Tuesday, November 19, 2024 9:44 AM
To: Aaron Brown <ambrown at jlab.org>; dsg-engineering at jlab.org <dsg-engineering at jlab.org>
Subject: Re: today's agenda

One should mentally prepare for a meeting and spend a few minutes collecting one's thoughts about what one is going to say in the meeting. Appears to me, we don't do it. Because all meetings look like a question and answer session. At the end of the meeting, the key people should keep a personal record so that at the start of the next meeting they can refresh everyone's memory, including their own.  In essence, we don't know what we are going to say and what we have said previously. Bless our hearts.

This is the reason for the agenda. Listing the topics in the agenda helps give the persons who are going to talk about the topic advance notice to collect their thoughts (most important to least important). Much like a shopping list which one generates by the route which one plans to take in the store.

Starting today for the meeting, we start making a slide on each topic which lists what we are going to talk about. Should help with the minutes as well. Since we have only 4 projects the slides should be on ALERT, ECAL, Moller,  and Phoebus.

Let us pitch additional topics, for one it bugs me and for another, it sounds as if we are in a knitting club. If there are additional items to talk about, I'm sure the individuals who want to mention them will remember if not it wasn't important.





________________________________
From: Dsg-engineering <dsg-engineering-bounces at jlab.org> on behalf of Aaron Brown <ambrown at jlab.org>
Sent: Tuesday, November 19, 2024 9:01 AM
To: dsg-engineering at jlab.org <dsg-engineering at jlab.org>
Subject: [Dsg-engineering] today's agenda

Hi All,

Here is the agenda for this afternoon's meeting.
As usual, feel free to add or remove items as needed.

Thanks,
Aaron
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/dsg-engineering/attachments/20241119/e61a7b50/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 27222 bytes
Desc: image.png
URL: <https://mailman.jlab.org/pipermail/dsg-engineering/attachments/20241119/e61a7b50/attachment-0001.png>