 Weekly Chat meeting #9 - Friday 15th January 1999
 

Participants: Peter Kretschmar, Juhani Huovelin, Sami Maisala, Niels-Joergen
	Westergaard, Stefan Larsson, Carol Anne Oxborrow

Subjects discussed:
	Oested Launch
	Monthly Reports
	Simulator output/calibration data
	Gantt chart: bottlenecks and holdups
	CTS 2.2: draft holdup due to NAG
	February meeting
	Background problem: formulating the problem
	`Nice' Coding Standards
	Level 1 and 2 Data Structures
	Developer's Forum

Action Items

AI990115_1 	CAO	FOREVER		Remind SDAST members to report any
holdups and bottlenecks that could affect the GANTT chart with each monthly
report reminder.
OPEN.

AI990115_2	NJW	1/2/99		Circulate note on background handling
problem to include a list of questions and points raised by SDAST (see 
AI990108_2). This note is to be produced in collaboration with Juhani Huovelin.
OPEN

AI990115_3	ALL	ASAP		Read PK's email about nice programming
practices.
OPEN


*** IRC session log started at Fri Jan 15 09:30:21 1999.
<Peter:#jemxadr> Good morning Juhani! And Sami if he's with you!
H huovelin     #jemxadr 0 *real name unknown*   ~huovelin@us.astro.helsinki.fi
H Peter@       #jemxadr 0 KRETSCHMAR Peter         ~pkretsch@isdcul10.unige.ch
H oxborrow     #jemxadr 0 Carol Anne Oxborrow          ~oxborrow@tenma.dsri.dk
315 apollo.dsri.dk * End of /WHO list.      
<Peter:#jemxadr> Good morning Carol Anne!
<huovelin:#jemxadr> Good morning. Sami is here with me END
#jemxadr> Hello everyone! Special hello to Sami, since I've never met him. Will he
+ be coming to the meeting in February? END
<huovelin:#jemxadr> Yes. We come together END
#jemxadr> Great! It'll be good to see you both. Niels Joergen will be with us soon
+ END
*** larsson <~larsson@tenma.dsri.dk> joined channel #jemxadr
#jemxadr> Good morning Stefan. END
<larsson:#jemxadr> Morning!
<larsson:#jemxadr> END
*** njw <~njw@heao1.dsri.dk> joined channel #jemxadr
#jemxadr> Allan can't make it today. There's lots of excitement here because Oerst
+ed, the first all-danish satellite is being launched from Vandenburg airforce bas
+e in California
<Peter:#jemxadr> Great. When is the precise launch date?
#jemxadr> at 11.39 our time, about 2.30 am californian time.
#jemxadr> I can give you a URL where you can see it live. END
<huovelin:#jemxadr> Please do it END
#jemxadr> If you want to see the Oersted launch go to  http://www.boeing.com/news/
+feature/argos0199/ at about 11.30 Danish time. END
<Peter:#jemxadr> Thanks! END
#jemxadr> There's a big affair at the Planetarium in town, so the institute's goin
+g to be almost empty today. END
#jemxadr> Is nJW with us? Shall we start? END
<Peter:#jemxadr> Yes, let's start.
<Peter:#jemxadr> END]
<njw:#jemxadr> Hello and good morning END
#jemxadr> First, the open Actions. First still open is on Allan, so we'll skip tha
+t. Next is on
#jemxadr> all of us to do the application by application monthly reports. Not much
+ has been reported thus far, but now that Xmas and the New Year is behind us I ex
+pect significant progress on at least one application from each of you ! END
#jemxadr> Any comments? END
<larsson:#jemxadr> Not much to say but an appology.......
<larsson:#jemxadr> I will try to be a good boy from now...END
<Peter:#jemxadr> Well, I plan to work on some JEM-X code after the OMC meeting nex
+t week, so hopefully I'll be lucky ... END
#jemxadr> Okay, next one is on all of us to provide material for SCREWs with each 
+delivery of soft ware and update of the ADD. Are we all clear about this? END
<Peter:#jemxadr> For me in principle yes, but remind us when we get close to deliv
+ery. END
<huovelin:#jemxadr> We will be making progress in programming as soon as Sami gets
+ his DAL.RIL and PIL working under his account END
#jemxadr> Next is on NJW to provide calibration data/files to me. It's due today, 
+so I'll be round to hassle you about that later on. How's it coming along? END
<njw:#jemxadr> I have made some progress, but mainly as a preparation for the simu
+lator.
<njw:#jemxadr> About the calibration data files I've just made one for you, CAO EN
+D
#jemxadr> I'll be needing this stuff by the middle of next week I think. END
<huovelin:#jemxadr> By the way, NJW, should we get the latest version of your data
+ simulator from somewhere ? END
#jemxadr> That's a good question. Where do we generally access the stuff your simu
+lator produces? END
<njw:#jemxadr> No, Juhani, I'm making a new version (in C) which fits the Observat
+ion Simulator
<njw:#jemxadr> with two JEMX's etc. so be patient a couple of months. In the meant
+ime what you've got is the best available. END
<njw:#jemxadr> I can make the present version available through the development WW
+W pages for SDAST END
#jemxadr> Okay, we'll be patient. We'll discuss the website a little later. END
<huovelin:#jemxadr> OK (to NJW). Fine, we will copy and install that, to be sure t
+hat we dont have a too old version END
<huovelin:#jemxadr> The main thing is to have the correct data structure there for
+ tests of IO END
#jemxadr> The next AI is about holdups and the Gantt chart. I think this is either
+ closed, or ongoing, since at any time till the final delivery we should inform A
+H as soon as the Gannt chart is no longer in agreement with reality. Also as Sw m
+anager
#jemxadr> he needs to know about all potential holdups and bottlenecks. So closed 
+or ongoing? END
<Peter:#jemxadr> In this formulation it's closed, IMHO. 
<Peter:#jemxadr> Maybe we should add one to inform Allan promptly about any bottle
+necks etc. coming up while we're working. END
#jemxadr> Okay, I'll close this AI, but perhaps I should send a reminder about rep
+orting holdups and bottlenecks with each monthly report reminder. END
<njw:#jemxadr> Probably a good idea END
<larsson:#jemxadr> Fine with me. END
<huovelin:#jemxadr> OK END
#jemxadr> The next 3 AI's have due dates in the future. So let's move to AIAI98121
+8_3
*** Signoff: huovelin (EOF From client)
*** huovelin <~huovelin@taurus.astro.helsinki.fi> joined channel #JEMXADR
#jemxadr> which is checking through the CTS2.2d. At the moment it's still a draft
#jemxadr> version. The last I heard there was a holdup making this an official
#jemxadr> release because ISDC is negotiating to use the NAG libraries. Has everyo
+ne skimmed through the CTS? I didn't see anything too startling in it. END
<larsson:#jemxadr> Were can it be found? END
<Peter:#jemxadr> The information regarding NAG is true. No news yet, as far as I k
+now. END
#jemxadr> It's worth a look because of extended sections about delivery modules an
+d executables, scripting languages etc. END
#jemxadr> If there are no comments, I'll close this AI. END
<Peter:#jemxadr> To Stefan: Go to ISDC's homepage, follow the link to documents EN
+D
<njw:#jemxadr> Is CTS2.2 very different from CTS2.1 ? END
<larsson:#jemxadr> Peter: I only found 2.1 END
#jemxadr> It's more extensive in certain areas, which is useful for us. END
<Peter:#jemxadr> Ooops, you're right. Let me check ... END
#jemxadr> Draft 2.2 is on Don's personal directory somewhere. He sent us the URL m
+onths ago, I can find it and sent it to you if you want. END
<huovelin:#JEMXADR> Please do that (to CAO ) END
<larsson:#jemxadr> IThen I can probably find it if not I will ask you. END
<Peter:#jemxadr> CAO is right. The holdup is probably the cause, why it isn't on t
+he Web yet. END
#jemxadr> My guess would be that major problems with the CTS are only going to sho
+w up after alot of coding and a little integration. END
<Peter:#jemxadr> I'll subscribe to that!
<Peter:#jemxadr> ENd
#jemxadr> For example, I've got one V1 delivery module to do, and I'm not doing an
+y DD on the V2 stuff until integration of the V1 module is complete - it's my tes
+t module to see how things really get done at ISDC, so I'm working only on that o
+ne. 
#jemxadr> Until I've experienced integration myself, I don't really think I know e
+xactly what it is they want. Also CTS 2.2 will be on the official web page once i
+t's officially released. END
#jemxadr> If there are no more comments, I'll close the CTS AI. Next AI is on Alla
+n to arrange a meeting. I think that AI's almost closed. 
<huovelin:#JEMXADR> We have already reserved a hotel. hopefully the dates are not 
+going to change END
#jemxadr> We should all be thinking about the next AI: pondering background proble
+ms and writing questions that arise to NJW and Juhani. Any comments? END
#jemxadr> I think those dates are quite fixed. But I haven't had any definite conf
+irmation from Allan. END
<njw:#jemxadr> I'm about to write a little note on this question which I hope to d
+istribute before the meeting END
<huovelin:#JEMXADR> Those would be very useful, since wealready have our idea of h
+ow to do those things, but ... END
<huovelin:#JEMXADR> My previous comment referred to the BKG END
#jemxadr> NJW: I'll make you an AI for that backgroung problem note distribution. 
+Will this be a note soliciting ideas or a note summarizing the quesitons that hav
+e been received? END
<njw:#jemxadr> It'll be a note putting forward some ideas and concepts to stimulat
+e questions and discussion END
<huovelin:#JEMXADR> I think that questions and the possible solutions should be se
+parated somehow END
#jemxadr> So it will include all our questions and points raised? END
<njw:#jemxadr> yes END
#jemxadr> Okay, so the due date on that AI will be Feb 1 1999. END
<njw:#jemxadr> OK END
<huovelin:#JEMXADR> Do you mean that we dont process the questions and comments be
+fore the meeting ? END
#jemxadr> As I see it, NJW's note should be the result of processing the recieved 
+questions and points raised. END
<njw:#jemxadr> No, we should try to complete a number of loops before the meeting,
+ CAO's date I consider as the latest possible END
<huovelin:#JEMXADR> Fine. And we will send our comments before Jan 27 (or earlier)
+ ? END
#jemxadr> Shall we move the date on submitting questions forward, say a week to Ja
+n 20th so that NJW and Juhani get a chance to discuss the material they've receiv
+ed and formulate the discussion note? END
<njw:#jemxadr> Finishing comment: about the web page, I've handed some stuff to CA
+O. Good bye, I'm heading for the planetarium. END
<larsson:#jemxadr> Yes Jan 20 for the first "loop" END
#jemxadr> So dat on AI990108_2 is changed to Friday 22 Jan, which gives NJW and Ju
+hani a chance to collate the material. END
<njw:#jemxadr> OK to Jan 20. END
#jemxadr> Jan 20th, next wednesday it is END
#jemxadr> Bye NJW, have a good time. END
#jemxadr> Last open AI, has just been closed by PK's latest email, I think. Any co
+mments PK? END
<Peter:#jemxadr> Nothing specific, I tried to put all into the mail
<Peter:#jemxadr> But I'll probably also start a WWW page for ISSW development next
+ week. I will let you know when something is there. END
#jemxadr> So that's an AI on everyone to read Peter's email and digest it. END
<huovelin:#JEMXADR> Slurp ! END
<Peter:#jemxadr> There isn't that much new information there. I hope to provide mo
+re on an ongoing basis when I delve deeper into the development. END
#jemxadr> Next on the agenda is the level 1 and 2 data structures. Last week I fin
+ally got to NL and he wants to keep the APIDs the way they are for pretty persuas
+ive reasons, so that makes things a little tougher for Preprocessing, but not as 
+tough 
#jemxadr> as it would be to change things now that the engineering model is so clo
+se to delivery. Also I have one or two other small things I should raise with Ste
+phane Paltani. Any other comments from SDAST? END
<larsson:#jemxadr> No from here. END
<huovelin:#JEMXADR> No comments END
<Peter:#jemxadr> Nothing specific - it might have side effects which we can't see 
+at the moment. END
#jemxadr> In that case, we'll probably be making final approval on these data stru
+ctures next week. I'm sorry we've been so long - it's harder than getting an audi
+ence with Elvis to get hold of the IT people at the moment - they're up to their 
+necks 
#jemxadr> in work thanks to that delivery. END
#jemxadr> Final point on the agenda: the developers forum. You all have good contr
+ibutions I know, so just send me the URL for your own personal directory full of 
+developement goodies. END
<huovelin:#JEMXADR> Its nice that someone thinks positive ! END
#jemxadr> I'll include PK's latest email as a technical note. The background note 
+from NJW and JH can be included as a discussion document. Any thing else? END
<larsson:#jemxadr> No. END
<huovelin:#JEMXADR> No thing END
<Peter:#jemxadr> Nothing END
<huovelin:#JEMXADR> Are we ready for the weekend ? END
<Peter:#jemxadr> Well, I don't kknow about you - I have to prepare the OMC meeting
+ next week :-) END
<larsson:#jemxadr> We have a seminar in 2 min. END
<huovelin:#JEMXADR> Sounds acceptable . Bye bye folks ! END
#jemxadr> So next meeting Friday 9.30 Danish Time. END
<Peter:#jemxadr> OK, so let's finish if there is nothing left. END
#jemxadr> Take care, and have a good weekend. END
*** Signoff: huovelin ()
<larsson:#jemxadr> Bye. Have a nice weekend. END
<Peter:#jemxadr> Fine, 'see' you next week. END
<Peter:#jemxadr> Goodby enjoy the weekend! END
*** Signoff: Peter (Leaving)
#jemxadr> Bye. END
*** Error: Closing Link: oxborrow[~oxborrow@tenma.dsri.dk] () 
*** IRC session log ended at Fri Jan 15 10:29:44 1999.
