	
	Weekly Chat Meeting # 42: Wednesday 3rd January 2001
	
Participants: Allan Hornstrup, Niels Joergen Westergaard, Peter Kretschmar,
	Sami Maisala, Stefan Larsson, Carol Anne Oxborrow
	
Subjects discussed: AI list 
		Problems logging on to CVS repository
		Background modelling requirements
		GRANT contact
		V2 consolidation: what, how?
		Agenda for SDAST meeting Copenhagen 9-10/01/01
		
Action Items: none

**** Logging Started : Wed Jan 03 09:42:34 MET 2001
<njw> There is one on myself due 5/1 2001 for the calibration document. I have begun the work, so it's coming END
> Hello everyone, good to see so many of you here - please forgive my lateness END
<njw> Welcome, Carol Anne, we've just started taking a look at the AI list END
<njw> The next (REVII_1) is for Peter: the ISDCLVL usage ? where are you ? END
> That's good - could I remind you all that ALL the ADD AI's were due
> yesterday and that includes ISDCLVL. END
<peter> Yes, I know I'm late. I was caught by some malady of the bowels with fever after Christmas and am still not 100% back on track ...
<larsson> Yesterday is a little late in Sweden this year CA..... END
<peter> Let's say that I'll try to get as far as possible before our meeting. END
<peter> P.S. If someone could tell me:
<peter> 1. If I have a DSRI account
<peter> 2. What the username is
<peter> 3. The password ....
> I'll be putting together the ADD starting today - your user name is
<peter> it would probaly help ;-) END
> pkretsch I think. END
<allan> pkretsch it is
> pkretsch to be exact END
<allan> we can assign a new passwd :-)
<allan> END
> While you can all continue to tinker with your ADD input right up
<smaisala> One question: I have user account to DSRI but I cannot take ssh connection. What is the problem? END
> to the time make the release version, no major changes should be made
<allan> you have to be more specific - and use tenma.dsri.dk
<allan> END
> after today without telling me. END
<smaisala> to allan: Secure connection to tenma.dsri.dk refused. END
<peter> To allan: thanks, please set a new password, I tried some options but none was correct. END
<larsson> Regarding ssh I get the same as Sami. I am using telnet. END
<peter> Same from here
<smaisala> OK. But I have to say. No good!! END
<allan> we will look into these problems, make sure ssh is running, assigning PK a new pwd etc... END
> Looks like we have some kind problem - can you help Allan? END
> Okay, let's move on to non-ADD AI's until the ssh thing is fixed -
<allan> BBB
<allan>  
> AI16.5	PK/SM	30/11/00 Go through j_performance specifications and see how
OPEN			well they fit into OSM

> PK/SM? END
*** Signoff: allan ()
*** allan (~allan@apollo.dsri.dk) has joined channel #jemxadr
<peter> For me the ball is with Sami. I sent him some input a while ago. END
> cancelled? more realistic due date? END
> Hello? END
> Okay, next one -
> AI16.13	AH	10/00	Contact Juhani to find out what is needed for the
OPEN			background.

> AH? Cancelled? new due date? you decide. END
<allan> The AI is kind of strange, since I just have to ask Juhani to
<allan> specify the input to the background 
<allan> calculation program in Southh...
<allan> Actually, if this is still needed, I
> So What should we do with this one? Have the requirements he needs
<allan> think Sami and Juhani should ask us to provide the information.
<allan> END
<njw> What about AI16.7, 16.9 (ADD related), 16.11 ?
> changed since the AI was created since their using GEANT at Helsinki? END
<njw> I just had a little talk with Tony Dean in Ecogia last year. He said, that
> I think we can skip further discussion of ADD AI's since no one's even
<njw> a new simulation is coming very soon. Actuallyy I'm compiling data on the JEMX
> admitted that they can't log on to DSRI until today (i.e. a day after
<njw> detector as a new input to the TIMM END
> the due date) - so I think we all know how they're (not) going. END
<allan> SOme people do logon - using e.g. telnet END
> Has ANYONE outside DSRI actually checked anything out of the ADD
> CVS repository? END
> If not, let's get on to the other AI's. END
<smaisala> NOPE. cannot log in. 
<larsson> CVS no END
<peter> CVS: No
> Okay, we'll have to get that problem fixed before worrying about the
> ADD AI's. What about this input to/from background modelling in
> Helsinki? END
> Should it be on next week's agenda? END
<njw> I definitely think so. I would very much like a presentation  by Sami on
<njw> the current status of the background modelling and how to use it END
> That sounds like a very good idea. END
<smaisala> OK. END
> Now, we have several IBH AI's and I suggest they all get cancelled
> and replaced by agenda items next week - I suggest that both
> SL and SM present their ideas at the meeting, we have a round table
> discussion, and aim to produce a detailed design description in list
> form by the end of themeeting. What say you? END
<njw> Agreed END
<peter> I fully agree. END
<smaisala> I agree. END
> So be it END
> NEXt: 001031_2	SM	12/00 Circulate GRANAT background information within
OPEN			SDAST when he gets it.

> So how's the contact coming along SM? END
<smaisala> I have to say I haven't got any response from GRANAT people. I have sent emails but no response. 
<smaisala> How about those GRANAT people who were at ISDC?? Peter? END
<peter> Sorry, we came to very little talking finally. I will try to incite some more response from them this week. END
> I'll change that due date to `whenever' Sami - you can after all only
> solicit information - not wring it out of them! I chatted a little to
> one of the Russians during the consortium meeting, but he didn't have
> much to say short of `contact the guys in Russia' - sorry. END
<smaisala> OK. END
> Next a christmas goody for njw:
> CAL1.1	NJW	15/12	To look into where conversion values for HK parameters
OPEN			come from (JMXi-CONV-MOD)	

<njw> Ib (and Steen - when he has time) is working on a document describing this
<njw> it is intended to be ready by the end of this week. END
<njw> I hope to have some input for our meeting END
> Thanks, nJW. Now PK's turn:
> AI38.1	PK	15/01/01 Borrow ISDC software problem tracking tool for SDAST
OPEN			integration problems and to-dos.

> I'll put `ONGOING' next to this one??? END
<peter> Oops that one ... No progress yet due to ISDC being still working on its own ... ONGOING is a good idea. END
> Then we have the three consolidation-related AI's - I put them here
> to ensure they get a regular airing and remain foremost in our thoughts
> during V2 consolidation: PLEASE read these suggestions of Peter's
<njw> Couldn't we (=CAO) set up a list with tick marks when overhauled ?
> for how to go about consolidation, I think they are all good suggestions.
<njw> And who is to judge that? Perhaps we could do it circularly: A checks on B, B checks on C,
> Can't we more or less see this from the s/w delivery forms at ISDC?
<njw> and C checks on A ? What do you think ? END
> I doubt anyone has time to do this - simply giving you all lists of
> data structures to check over proved to be almost worthless, when it
> got done at all. END
<njw> Other opinions ?
> Could we maybe include component change histories for each component
> in the ADD, as part of it's upgrading to DDD status? That way one
> could at least read what had been done. Could we also insist that
> every time a component gets delivered to ISDC that a corresponding new
> entry for the whole component is put into the ADD within a couple of
> days? END
<peter> Sounds reasonable to me. 
> Any other ideas? END
<peter> While systematically checking the points I raised  seems too much effort
<larsson> Is it not enough to have the component change history in the
<peter> I sincerely hope that with the availability of OSim
<larsson> delivered files? It will be some extra work to do the same at two places. END
<peter> and the analysis tools to downlowad (my scripts will be available soon).
<njw> I have no problems with CAO's suggestions, I simply think that it is a
> How about I simply add a `revision' table to the ADD with dates and
<njw> good idea to have somebody else read and understand your programs END
<peter> That we will all start to play with the tools, look into the code, to try and understand it, exchange comments and thus improve the overall quality. END
> version numbers for every executable? This does  mean that you should
> let me know as soon as you've delivered a module and also send the
> module to me for inclusion on the Forum page. END
> I agree that reading each other's code is a good idea, but do we have
>  END
> time for it right now? END
<larsson> Lets discuss these things next week. END
<njw> Does it have to be right now? When does the consolidation period stop ? END
> Okay, let's make that an agenda point: Consolidation, how to do it. END
<njw> Alright END
<peter> Good, I'll try to present the "big picture" at our meeting. END
> That'll be good Peter. END
> The last AI isn't due till after the meeting so let's forget it.
> Next on today's agenda: Next week's agenda. Thus far I have:
> IBH: presentations, discussion, draft DDD
> In-flight calibration: how, what, where
> Consolidation: how, what, when
> V2 consolidation: current status
> ADD: updates and beyond
> Background modelling: ???
> j_performance: how it fits with OSM
> I seem to have run dry: any ideas anyone? END
<peter> No, seems complete to me. END
<njw> Perhaps Stefan could tell us something on the results of his executables ? END
<allan> We still have a two day meeting (Tue-Wed?) END
<larsson> Nothing else comes to my mind.... END
> Yes, it's two days with the two big subjects one on each day:
<larsson> Well, yes I can give an update. END
> background, calibration. END
<allan> I would like to see you all for dinner Tuesday evening then END
> That sounds wonderful Allan, thanks. END
<peter> Thanks Allan! END
<larsson> Looking forward to that Allan. END
<smaisala> Thanks Allan.
> So before we can make the actual agenda a few questions:
> What's the earliest everyone can be in Copenhagen on Tuesday?
> What's the earliest anyone has to leave on Wednesday?
<larsson> I will arrive monday evening. END
> What time for supper Allan? 
<smaisala> I will be there about 9.00-9.30.END
<peter> I'm easy: I'll be there already an my flight on Wednesday is late (~20:00)
> Coffee or hot chocolate breaks? END
<smaisala> A lot of them :-)
> How much beer on Tuesday evening, Allan (could affect starttime on Wednesday!)END
<allan> Around 1800 - to prevent starving children :-) END
<allan> Beer - or redwine - well, it's perhaps ver ypersonal, but
<allan> supplies are sufficient for all. END
<larsson> My plan is to leave by a train at 18.00 on wednesday. END
> So we'll start 9.30 on Tues. and finish by 16.30 on Wednesday. Okay?
> END
<larsson> Fine. END
<peter> OK
<njw> Y
<smaisala> OK
<njw> AOB ? END
<smaisala> N
> I'll circulate the draft agenda this morning - all additions are
> welcome. Otherwise no AOB from me. See you all next week! END
<larsson> OK, nothing else from here. END
<smaisala> BYE 
*** Signoff: smaisala (EOF From client)
<njw> Bye, everybody 
*** njw has left channel #jemxadr : (njw)
<allan> bye
*** Signoff: peter (Connection reset by peer)
*** Signoff: allan ()
> Goodbye everyone. END
