		JEMX SDAST CHAT MEETING 20th August 1999

Participants:

Peter Kretschmar, Juhani Huovelin, Allan Hornstrup, Carol Anne Oxborrow,
Niels Joergen Westergaard, Eero Esko, Stefan Larsson

Subjects covered:
	New SDASTer Eero Esko
	ISDC Reference Platform
	Limit bug fixes to latest library releases
	New Makefiles
	DAL1.3 release:
		Sorting Children in a Group
	INDEX system
	JEMX status and grey filter history
	Meeting in Helsinki 22-23rd September 1999
	ISSW components status
	Deadline for ADD updates contributions
	Deadline for DDD version 1.0 contributions
	
New Action Items

AI990820_1	ALL	Today!!	Send AH email with DETAILED  status of each
and every component for which one is listed on the MOU and ADD.
OPEN

AI990820_2	AH, CAO	Circulate summary of ISSW status to all SDAST
OPEN

AI990820_3	ALL	17/09/99 Send CAO updates for ADD
OPEN

AI990820_4	ALL	15/10/99 Send CAO contributions to DDD version 1.0
OPEN



*** IRC session log started at Fri Aug 20 09:29:55 1999.
H huovelin     #jemxadr 0 *real name unknown*   ~huovelin@us.astro.helsinki.fi
H oxborrow@    #jemxadr 0 Carol Anne Oxborrow          ~oxborrow@tenma.dsri.dk
315 apollo.dsri.dk * End of /WHO list.      
#jemxadr> .Hi Juhani _ I've just had a bit of a panic, the system's been sick 
#jemxadr> while Allan and Guilio were on holiday, and now IRC wouldn't work, It's
*** eesko <~eesko@taurus.astro.helsinki.fi> joined channel #jemxadr
*** Peter <~pkretsch@isdcul10.unige.ch> joined channel #jemxadr
#jemxadr> all put right now. How are you? END
#jemxadr> Hi Peter, it's good to have you with us!
<Peter:#jemxadr> Fine, thank you.
#jemxadr> Hi `eesko', who are you? I'm Carol Anne. END
<Peter:#jemxadr> I assume Alan and Niels Joergen will join any minute now. NED
#jemxadr> Allan will be with us soon - I haven't seen NJW yet this morninging END
<huovelin:#jemxadr> Hello everybody, I have a new member to our group, Eero Esko, joining
+ the Helsinki team here END
<eesko:#jemxadr> Hello, im Eero Esko
*** larsson <~larsson@tenma.dsri.dk> joined channel #jemxadr
<Peter:#jemxadr> Great! Welcome to the team Eero! END
#jemxadr> Hi Stefan and Eero, I'm glad you could both make it. END
<larsson:#jemxadr> Morning everybody END.
#jemxadr> Will Sami be joining us today, Juhani? END
H larsson      #jemxadr 0 Stefan Larsson                ~larsson@tenma.dsri.dk
H Peter        #jemxadr 0 KRETSCHMAR Peter         ~pkretsch@isdcul10.unige.ch
H huovelin     #jemxadr 0 *real name unknown*   ~huovelin@us.astro.helsinki.fi
H eesko        #jemxadr 0 *real name unknown*   ~eesko@aurus.astro.helsinki.fi
H oxborrow@    #jemxadr 0 Carol Anne Oxborrow          ~oxborrow@tenma.dsri.dk
315 apollo.dsri.dk * End of /WHO list.      
<huovelin:#jemxadr> Sami is still on vacation, and coming back only next Monday END
#jemxadr> I'll go and rustle up NJW. END
<huovelin:#jemxadr> So, we are a bit lost on what's happened during ther past two months 
+END
<Peter:#jemxadr> Not too much anyway, one of the reasons why this chat became more and mo
+re urgent. END
<Peter:#jemxadr> A stupid question from my side: is Eero a male or a female name? END
<eesko:#jemxadr> a male
<eesko:#jemxadr> END
<Peter:#jemxadr> Thanks! It sounded like, but I've been misled before :-) END
*** Change: eesko is now known as Eero
<Peter:#jemxadr> Eero, maybe you could introduce yourself a little. I hope Juhani has tol
+d you a little bit about the rest of us. END
#jemxadr> Still no sign of NJW, so we had better start now with an introduction to Eero. 
+Just what will you be doing in this project Eero, and what's you background? END
<Eero:#jemxadr> It seems that I will be coding. 
#jemxadr> Do you know which bits you're responsible for yet? END
<huovelin:#jemxadr> Eero is a student at the University of Technology (computer technolog
+y) END
*** allan <~allan@apollo.dsri.dk> joined channel #jemxadr
<Eero:#jemxadr> Im studying computer science at the Helsinki university of technology, bu
+t im here because instead of going to the army (obligatory in Finland) i chose to do a s
+ort of community service.
#jemxadr> Hi Allan, we're getting acquainted with Eero who will be working in Helsinki EN
+D
<Peter:#jemxadr> Welcome to the strange world of coding for ISDC. I hope we all and Sami 
+in particular will be able to give you a good start. END
<allan:#jemxadr> Welcome, Eero!
<allan:#jemxadr> END
<Eero:#jemxadr> No, not yet END
<Peter:#jemxadr> That's a useful community service! I did not get an option like that in 
+Germany ... END
#jemxadr> INTEGRAL is considered `community service'??? That's interesting. END
<Peter:#jemxadr> To CAO: Absolutely it's for the good of the (scientific) community - or 
+at least the X- and Gamma-ray people
<huovelin:#jemxadr> To be honest, we get inexpensive labour that way END
<Peter:#jemxadr> If those form only about 10-7 to 10-6 of the world's population, we can;
+t help it :-) END
#jemxadr> Now we're all here, at last, I think we'd better get down to the Agenda: point 
+1, Reference platform. What about it Peter? END
<Eero:#jemxadr> Well, I had to fint the work myself, and started looking for something in
+ the university. END
<Peter:#jemxadr> OK, back to work: 1) the Reference Platform
<Peter:#jemxadr> There were some discussions going in within the ISDC because our librari
+es are constantly updated
<Peter:#jemxadr> to resolve problems found by various people but the official Refernce Pl
+atform did not follow.
<Peter:#jemxadr> Yesterday in the software meeting the following procedure was agreed upo
+n:
<huovelin:#jemxadr> We have had problems with fitting our referemce computer, and that's 
+why we use the ISDC system for compiling the final versions END
<Peter:#jemxadr> 1. The Reference Platfom may be updated quite frequently, possibly every
+ few weeks.
<Peter:#jemxadr> 2. These 'rapid' changes shall only be on ISDC's support libraries. Such
+ changes chall be marked by the decimal in the version number
<Peter:#jemxadr> I.e. an update of DAL would lead to a version change 1.4->1.5 (example)
<Peter:#jemxadr> Major changes (hardware, systems software) will be much less frequent an
+d marked by a change in the most significant number (e.g. 1.5->2.0)
<Peter:#jemxadr> 3. There will be a .tar file wth all released and (somewhat) tested libr
+aries corresponding to the most current reference platform, so people outside ISDC can m
+ake a quick update to the newest version.
<Peter:#jemxadr> 4. Bugfixes in our libraries may still require that you use a newer vers
+ion of the library than the reference. 
<Peter:#jemxadr> Because we have to check interdepencies between the various parts, it mi
+ght take a few weeks between the change in, e.g., DAL and a new Reference Platform relea
+se.
<Peter:#jemxadr> 5. While it would be nice if your software was compiled, linked and test
+ed with the latest Reference Platform when you deliver, this is not absolutely mandatory
<huovelin:#jemxadr> Connected to this, could you arrange Eero an account in the ISDC syst
+em, since he will be doing a lot of coding work, Peter ? END
<Peter:#jemxadr> The reason is that even if you did, if we make changes a few weeks later
+, your software would be 'outdated' again. END
<Peter:#jemxadr> To Juhani & Eero: yes, absolutely. We'll need some details to be sent to
+ us. Does the DSRI crew remember the necessary steps? END
<allan:#jemxadr> Your procedure sounds reasonable END
<Peter:#jemxadr> Now to the 'ugly' point:
<allan:#jemxadr> I bet I can find the email describing the step to get an account
<allan:#jemxadr> let me check after the chat. END
<huovelin:#jemxadr> OK, Allan END
<Peter:#jemxadr> Don would like to limit isdc-help bug searching to people who have insta
+lled the latest platform (like a commercial helpdesk :-) )
<Peter:#jemxadr> But a majority around the table disagreed.
#jemxadr> What's wrong with that? _it seems like a reasonable limitation given the limite
+d resources END
<Peter:#jemxadr> It may mean thougj, that if you run into problems that can be traced to 
+our libraries, the first thing we'd tell you would be: get the latest release, recompile
+ and try again. END
#jemxadr> That's reasonable enough. It's what we do. END
<Peter:#jemxadr> Good. As I had hoped :-) END
#jemxadr> Nobody can expect Don and Co. to hunt down bugs that may already be fixed END
<Peter:#jemxadr> Well, some people seem to want both only rare library updates and full, 
+bugfixed finctionality ... END
#jemxadr> That's unrealistic. This is a very fluid developmental situation. END
<Peter:#jemxadr> If nobody cires out, let's movve to item 2 on the agenda. END
<Peter:#jemxadr> "cries out" END
#jemxadr> Makefiles:Peter? END
<Peter:#jemxadr> Just a short note: We have a new set of even better Makefiles which you 
+can downlowd from our Software WWW page and which should be used for future deliveries.
#jemxadr> Do you have an URL for that? END
<Peter:#jemxadr> Actually I think all improvements help for F90 programmers but one never
+ knows what else has been changed (our software organization is still somewhat fluid). E
+ND
<Peter:#jemxadr> Follow the link Software from http://isdc.unige.ch. It's all by CGI scri
+pts ... END
#jemxadr> Thanks peter. END
#jemxadr> Next, DAL updates: Peter? END
<Peter:#jemxadr> Currently the URL http://isdc/bin/sw2html.cgi? works. END
<Peter:#jemxadr> DAL 1.3 is on the verge of being released (today, according to yesterday
+'s statements). 
<Peter:#jemxadr> There are several improvements, especially regarding the sorting of chil
+dren in a group. 
<Peter:#jemxadr> As soem of you might have encountered, DAL 1.2.x did sometimes reverse t
+he order of elements within a group for technical reasons.
<Peter:#jemxadr> In many cases this is completely irrelevant, but as at least 3 people ar
+ound here (me included) found out - it can hurt badly if you depend on the order in two 
+sets of data being aigned.
<Peter:#jemxadr> aligned
#jemxadr> Are there any other major fixes? END
<Peter:#jemxadr> Among other improvements, DAL 1.3 now includes functions to sort childre
+n by various criteria, the default being the original order in the group table. END
<Peter:#jemxadr> Actually these sorting functions could lead to some neat data access met
+hods. There is some overlap with the functionality that was supposed to come out of the 
+INDEX system. END
<Peter:#jemxadr> To CAO: None I can remember right now, but there were many larger and sm
+aller improvements. END
#jemxadr> What's the status of the INDEX system now. I've never used it or even had need 
+for it. END
<Peter:#jemxadr> Btw, the fact that DAL did not guarantee the order of elements was even 
+documented, but nobody really took notice. END
<Peter:#jemxadr> INDEX will be taken up by Don, because Laurent seems overloaded. 
<Peter:#jemxadr> We think that it will be actually very useful to store calibration and i
+nstrument model data. 
<Peter:#jemxadr> The main problem was and is taht with a weakly defined system, it's hard
+ to discuss functionality :-(
<Peter:#jemxadr> IMHO we could and should discuss this in our next face-to-face meeting. 
+END
#jemxadr> So INDEX is still and in-the-future system? We shouldn't be incorporating it ye
+t in our ISSW? END
#jemxadr> Hello, has my system gone down? END
<Peter:#jemxadr> If you know what you do, you should include it. The main problem may be 
+to understand hwo to use it and what we have. END
#jemxadr> Yes, there isn't much documentation? Is that forseen soon? END
<Peter:#jemxadr> If we don't meet soon, I'll try to give an overview by email and we can 
+play Q+A in the next chat. OK? END
#jemxadr> That seems fine, Peter. Next: JEMX status and grey filter history: Peter? END
<Peter:#jemxadr> Phew, I get to 'talk' a lot today ...
<Peter:#jemxadr> OK: We have a slight(?) problem:
<Peter:#jemxadr> Some time ago I convinced everybody that we could and should just rely o
+n the general Data Preparation S/W of Reiner Rohlfs which generates a general "Mode Hist
+ory" of all instruments.
#jemxadr> Yes, it's horribly cumbersome. END
<Peter:#jemxadr> This one includes grey filter status and can be easily(?) accessed by DA
+L3 functions. END
<Peter:#jemxadr> Now, after looking at the problem again, I've come to the conclusion tha
+t it is _NOT_ sensible to have a detailed mode change and grey filter history within Rei
+ner's table.
<Peter:#jemxadr> The problem is that the detailed history requires a complex cross-check 
+of several sources of information:
<Peter:#jemxadr> - Housekeeping
<Peter:#jemxadr> - Science packet headers
<Peter:#jemxadr> - 'Dummy' events (stored as -SRW raw data)
<Peter:#jemxadr> So at the moment, RR's software will only monitor the data accesible in 
+the cyclical HK packets. Sufficient for OSM purposes but not necessarily for our analysi
+s software.
<Peter:#jemxadr> This means that we need two JEM-X specific tables with the detailed hist
+ory - and, worse, an executable to generate them!
<Peter:#jemxadr> The questions are now:
<Peter:#jemxadr> 1. Do you agree to the statements above
<Peter:#jemxadr> 2. If yes, who writes this executable?
<Peter:#jemxadr> END
#jemxadr> Yes, I agree to the statements above. Answer 2: hhmmmmm.........END
<allan:#jemxadr> Hmm, about 2: Didnt we have a volonteer? END
<Peter:#jemxadr> Not me - I'm running late on multiple tasks already. END
#jemxadr> How soon do we need a delivery of this function? END
#jemxadr> Didn't I hear somewhere recently that Juhani just got some cheap new manpower? 
+Just joking. END
<Peter:#jemxadr> In theory with V1. In practice, I'd say in parallel with V2, but it shou
+ld be one of the earlier deliveries. END
<Peter:#jemxadr> Well, if Eero came here for a week so Stephane and me could explain to h
+im the intricacies of JEM-X raw data, how ISDC stores it and how to write an ISSW execut
+able, it might be possible. 
<Peter:#jemxadr> From remote this would be very difficult. END
<Peter:#jemxadr> For someone new to all this, I mean END
*** njw <~njw@heao1.dsri.dk> joined channel #jemxadr
<huovelin:#jemxadr> I have to discuss this with Eero and Sami, but we can consider it END
<Peter:#jemxadr> Great! END
<njw:#jemxadr> Hello, unexpected delay - END
#jemxadr> I could certainly do this function, but my own V1 and V2 deliveries must have f
+irst priority. END
<allan:#jemxadr> Maybe Eero could come here on the way back from Geneva
<allan:#jemxadr> and CAO and Eero could work it out together - here? END
<larsson:#jemxadr> (No cheap manpower in Stockholm I am afraid). END
#jemxadr> Allan's suggestion sounds good. END
<Peter:#jemxadr> To Allan: sounds good to me, but Juhani & Eero must first agree to the i
+nvestment in time & travel money :-) END
#jemxadr> What about in conjunction with an SDAST meeting here? END
<allan:#jemxadr> I thought the next meeting should be in Finland? END
<huovelin:#jemxadr> OK, we can work out the details after the chat END
#jemxadr> I could still talk to Eero in Finland, I think. END
<huovelin:#jemxadr> Are we already in 5) ?END
<Peter:#jemxadr> Why don't we move to item 5: Meeting
#jemxadr> We're sliding that way. ENd
<huovelin:#jemxadr> I suggest aht we have the next meeting in finland END
#jemxadr> Great! END
<Peter:#jemxadr> I'd be happy. The question is when END
<larsson:#jemxadr> Yes. END
<huovelin:#jemxadr> aht =that , finland = Finland END
<larsson:#jemxadr> I prefer beginning of week rather than end. END
<Peter:#jemxadr> Anyone want to propose a date? END
<njw:#jemxadr> There is an ISDC meeting 27/28 sept - before or after ? END
<huovelin:#jemxadr> There is a bunch of Meetings at DSRI in the end of September and begi
+nning of October, so that time is not suitable JEM-X HW meetings ) END
<huovelin:#jemxadr> ... (JEM-X HW meetings) END
<Peter:#jemxadr> For me September is completely blocked between Sep 6 and Sep 20 (I retur
+n from the U.S. on Sep 20).
<huovelin:#jemxadr> I suggest before 27/28 Sep END
<allan:#jemxadr> Seems that 22-24 Sep is the only option? END
<Peter:#jemxadr> I'd prefer not to meet in the week Sep 20-24, because I will probably ha
+ve to prepare for the Consortium Meeting. But if that's the only possibility ... END
#jemxadr> I'm pretty busy until Sept 17th, and there's half-term holiday in October 18-24
+th. So either early October or November END
<allan:#jemxadr> I am not at home from Oct 1-17
<allan:#jemxadr> END
#jemxadr> The week Sept 20 to 24th looks good for me END
<huovelin:#jemxadr> Do we need one or two days ? END
#jemxadr> My guess would be 2 days, since it's such a long time since the last meeting. E
+ND
<huovelin:#jemxadr> Fine: So, how about 20-21 Sep ? END
<Peter:#jemxadr> Two days would allow us to discuss a lot of detailed questions (data str
+uctures, etc.). So, while my schedule is cramped enough, I vote for two days. END
#jemxadr> I guess the agenda would look something like today's agenda with a very extende
+d item 6 (component-by-component status) and DAL discussion. END
<Peter:#jemxadr> Not Sep 20-21. I arrive at 9:45 A.M. from Boston on Sep 20. Jetlagged to
+o. END
<Peter:#jemxadr> Sep 23/24 would be a possibility, even though it's a crowded week then. 
+END
<huovelin:#jemxadr> So, new suggestion : 23-24, agreed ? END
#jemxadr> That leaves 22, 23, 24 Sept. Ideally not spilling over to 25th - that's my daug
+hter's birthday. ENd
<njw:#jemxadr> That's OK for me END
#jemxadr> 23-24 is fine with me. END
<Peter:#jemxadr> Allan? END
<larsson:#jemxadr> I might have problems the 24th but I am not sure. (Trying to find out)
+. END
#jemxadr> I'd prefer 22, 23rd if possible, but 23, 24's okay. END
<Peter:#jemxadr> Since I probably won;t stay the weekend this time, it could be Sep 22/23
+ if that helps. END
<allan:#jemxadr> I am checking the calendar, and just discovered problems, but I will 
<allan:#jemxadr> try to fix that. I agree to 22-23, if possible...END
<huovelin:#jemxadr> 22-23 suits equally END
<larsson:#jemxadr> FINE. END
#jemxadr> Could everyone who's in favour of 22-23rd September please respond now? END
<njw:#jemxadr> Still OK END
<Peter:#jemxadr> OK. So let's settle on 22/23. END
#jemxadr> Okay with me. END
<allan:#jemxadr> OK END
<huovelin:#jemxadr> OK END
<larsson:#jemxadr> 22-23. Yes. END
<Eero:#jemxadr> OK END
#jemxadr> Motion carried: 22 and 23rd september. END
<Peter:#jemxadr> In Helsinki? END
<huovelin:#jemxadr> Welcome to Helsinki. hopefully we'll have a nice weather END
<larsson:#jemxadr> I hope so. Last week I experienced +2 degrees ( at 4 in the morning
<larsson:#jemxadr> near Helsinki!!). END
<Peter:#jemxadr> To Juhani: we all expect a serious effort to create sunshine and mid-Eur
+opean temperatures! END
<huovelin:#jemxadr> It's only night time, during the daytime we still have nearly 20 END
#jemxadr> I won't be awake to experience anything at 4am, in Helsinki or otherwise. END
<larsson:#jemxadr> So lets have the meeting in daytime. END
<huovelin:#jemxadr> That's the time youll go to sleep ? END
<huovelin:#jemxadr> (that was to CAO) END
<larsson:#jemxadr> (Thats the time I am driving to the ferry in 
<larsson:#jemxadr> Aabo. END
<huovelin:#jemxadr> Aabo = Turku END
#jemxadr> We'll all discuss hotels etc. off line. I look forward to seeing Helsinki - I'l
+l bring my thermal undies! ENd
<larsson:#jemxadr> Turku = Aabo. End
#jemxadr> Next point. Sorry to be REALLY tedious, but what's the status of each of your e
+xecutables? First Peter. END
<Peter:#jemxadr> How about miving to item 6)? And somebody else could begin ... END
<Peter:#jemxadr> OK, OK, I'll begin.
<Peter:#jemxadr> My executable for V1 (jcreatespecmode) is delivered but will need updati
+ng according to the TM changes.
<Peter:#jemxadr> Currently I'm waiting for the TM definition to settle down ...
<allan:#jemxadr> Sorry to be blocking anything, but it would be nice to have these 
<allan:#jemxadr> status reports more cohrently collected. Would it be possible for
<allan:#jemxadr> all of you right after this session to send an email where
<Peter:#jemxadr> No work yet on the V2 software, i.e. JSpectrumBinning, etc.
<allan:#jemxadr> you explecitly explain the status? END
#jemxadr> That sounds like a very good idea Allan. END
<larsson:#jemxadr> Agree with Allans suggestion. END
<allan:#jemxadr> maybe we can skip the point here, then EN
<allan:#jemxadr> D
<Peter:#jemxadr> Fine with me. Will you send a summary of the overall status around? END
<allan:#jemxadr> Certainly END
#jemxadr> AI on all of us to send Allan an email with detailed component-by-component
#jemxadr> status of our ISSW.
<allan:#jemxadr> due today :-) END
#jemxadr> AI on allan or me to send summary of statuses to everyone else. END
<Peter:#jemxadr> I'll just use this forum to remind everybody that serious work on V2 ISS
+W better begin now, if it hasn't already begun. END-OF-SOAPBOX
<larsson:#jemxadr> Is that all for today folks? END
<Peter:#jemxadr> What about outstanding actions? END
<allan:#jemxadr> ADD/DDD? END
#jemxadr> I think V2 coding can procede MUCH faster once we've all learned the tricks of 
+the trade with the V1 deliveries. END
<larsson:#jemxadr> Sorry. END
#jemxadr> Outstanding AIs: Everyone to provide DDD contributions based on ddd.sty for eac
+h FUNCTION (not just component). Still open.
#jemxadr> I'll recirculate the ddd.sty fill-in template so that you can all get down to i
+t. Except Peter - he's already delivered his contributions. ENd
#jemxadr> The other open AI is to do with binning files and is dependant on the instrumen
+t team, so frankly it's going to be open for quite a while yet. END
#jemxadr> I'd like to create another AI to go with the one for ddd contributions and that
+'s for ADD contributions: I need updates for all you components, especially where data s
+tructure names are concerned.
#jemxadr> Could we all please agree on a deadline we all think we can achieve for contrib
+utions
#jemxadr> to each of these two documents?
<huovelin:#jemxadr> Could you add eesko@carina.astro.helsinki.fi in your mailing list, CA
+O and Peter ? END
#jemxadr> Once I receive your contributions it takes quite a while getting everything to 
+fit to gether, and an absolute age to make sure that
#jemxadr>  everything is self-consistent, especially where the aforementioned data struct
+ures are concerned. END
<Peter:#jemxadr> To Juhani: done END
#jemxadr> Done here too. END
#jemxadr> So when do you think you can deliver ADD updates and new DDD files? END
<Peter:#jemxadr> Do you need anything from me? I don't remember if I made an ADD update. 
+END
#jemxadr> I think I need ADD updates from you PEter. but the DDD stuff you sent me is jus
+t fine. END
<njw:#jemxadr> For data strucutrues
<njw:#jemxadr> For data structures and names wouldn't a week before our meeting be a nice
+ goal ? END
<larsson:#jemxadr> I can agree on that NJ. END
<huovelin:#jemxadr> Agree with NJW, if not necessary earlier END
#jemxadr> I suggest Friday 17th September as deadline for ADD update contributions - that
+ way I can harrass you personally the following week if you don't deliver! END
<Peter:#jemxadr> Fine with me. END
<njw:#jemxadr> I guess the DDD stuff would be dripping in as coding proceeds END
#jemxadr> At the moment I'm just looking for `filling' material or `place markers' for ev
+erything that hasn't been delivered yet (i.e V2)
#jemxadr> while V1 will of course be in it's nearly final form. END
#jemxadr> How about Friday 15th October for DDD contributions: these can be quite basic f
+or undelivered components END
#jemxadr> I realise these deadlines are quite far away, but I really expect you to stick 
+to them, AND provide input that I don't have to add to at all - that's why you're gettin
+g so much time. END
<Peter:#jemxadr> Fine with me again. END
#jemxadr> If there are no complaints I'll carve those deadlines in stone. END
<huovelin:#jemxadr> OK END
#jemxadr> Final point AOB. Well People? END
<Peter:#jemxadr> Nothing, I can think of right now. END
<huovelin:#jemxadr> Nothing more. We'll be in touch soon about our AI's  END
<larsson:#jemxadr> No. END
#jemxadr> We will have another meeting next friday, as usual, so anthing else can be save
+d for next week. Please keep in touch and
#jemxadr> participate next week: I promise to keep it short END
<huovelin:#jemxadr> Bye folks ! END
#jemxadr> Have a good weekend you all!END
<larsson:#jemxadr> Bye. END
*** Signoff: huovelin ()
<Peter:#jemxadr> Have a nice weekend everyone. END
<njw:#jemxadr> bye END
#jemxadr> Nice to `meet' you Eero END
*** Signoff: larsson ()
<Eero:#jemxadr> Bye END
*** Signoff: njw ()
#jemxadr> bye.
*** Signoff: Eero ()
*** Error: Closing Link: oxborrow[~oxborrow@tenma.dsri.dk] () 
*** IRC session log ended at Fri Aug 20 11:17:59 1999.
