

	Weekly chat meeting #30: Tuesday February 29th 2000

Participating: Peter Kretschmar, Niels Joergen Westergaard, Carol Anne Oxborrow,
	Sami Maisala, Eero Esko, Stefan Larsson
	
Subjects discussed: Contributions to ADD5.0
		Contributions to jemx.h
		Installation and longevity of ISDC RP1.4
		Agenda SDAST meeting March 9th 2000
		Separate analysis branches for spectra and lightcurves
		V2 component status
		
Action Items

AI_000229_1	ALL	Send CAO ALL contributions to ADD by end of week
AI_000229_2	ALL	Send CAO ALL contributions to jemx.h by end of week
AI_000229_3	ALL	Send CAO component-by-component V2 status


**** Logging Started : Tue Feb 29 08:59:49 MET 2000
*** njw (~njw@130.226.216.177) has joined channel #jemxadr
<njw> Good morning END
<eesko> FI end
<eesko> oops.
*** Signoff: eesko ( )
*** eesko (~eesko@aquarius.astro.helsinki.fi) has joined channel #jemxadr
> Hi, NJW! What's happened to eero? END
<eesko> I can't see what I'm typing END
*** larsson (~larsson@tenma.dsri.dk) has joined channel #jemxadr
> To the best of my knowledge Stefan and Sami should also be joining us, so let's
<eesko> I closed netscape but I still don't have enougc colors it seems END
> wait for them. END
<larsson> I am here CA. END
*** eesko has left channel #jemxadr : (eesko)
*** eesko (~eesko@aquarius.astro.helsinki.fi) has joined channel #jemxadr
> Hi Eero! Again! Is Sami there with you? END
<eesko> He said he would be here in a few minutes END
> Okay let's start by hearing what the status is on each of your
> ADD contributions. Stefan? END
<eesko> Sami has some problems with his computer it will take a few minutes END
> Peter? What about your contributions? END
<larsson> I will need another day or two CA. END
<peter> I'm just working on them and expect to be able to send you 
<peter> an update of the whole j_binning description this evening.
> NJW are you close to delivering something? END
<njw> Most of the work is the changing of names but in a couple of days END
> Alright guys, the deadline was today, but let's say I expect 
> EVERYTHING by the end of the week: I really want the draft ready
> for the meeting next week. By everything I mean: one file per component
*** smaisala (^smaisala@mizar.astro.helsinki.fi) has joined channel #jemxadr
> complete with name changes and diagrams to show how it fits in with
> the rest of the issw. Any introductory information: background 
> handling especially and other contributions to the `overview' chapter;
> and last but not least data structures: all the data structures that
<peter> For the overview drawings I contributed, I may need another day END
> you use that are not in RP1.4 MUST have an entry in the form of a
> rough template file. That's all! END
>  Hi Sami: when will your ADD contributions be forthcoming? END
<smaisala> I can send it to you today! END 
> All of it??? That's great! END
> Okay, next on the agenda: the jemx header: any thing you want added
<smaisala> I only have to chnge few names (templates) that's all END
> so that I can make an `official' version 2.0 release. END
<peter> Stefan: have you thought about the spectral data structures? Do you want to see them, or can I clear them with Stephane? END
<peter> Regarding jemx.h, I'm content with what is there. END
<larsson> I just sent a mail to you .
<larsson> Yes, they look fine to me. END
<peter> OK. Thanks. Carol Anne: You want those templates then after I've crosschecked with Stephane? END
<larsson> (but please send templates if they are availble. END)
> Yes, I want as many new templates as possible so that the documentation
> of the data structures is as complete as possible at the time of
> the mini-review in April. END
<peter> OK, I'll send them after Stephane has had a look to weed out possible stupid mistakes. END
> ALL data structure names should also be included in jemx.h ASAP, so
> you probably all need to send me a list of data structure names and
> the constant names (capitals and underscores) that you want used
> for them. END
<smaisala> When do you want that list ? END
> ASAP (yesterday!) END
> If no one else has comments on ADD and jemx.h, then on to RP1.4: just
> a general comment: I think we need to document consistently in our
> deliveries which ISDC RP version the delivered software was
> developed and tested under (also which version of jemx.h) END
> I can also recommend the `strawberryisation' of F90 - this is the
> approved method at ISDC too! (see yesterday's email on the subject) END
> Any comments? END
<peter> Sidenote: everything you deliver from now on _must_ be tested under RP1.4 END
<peter> I did not get the `strawberryisation' ... END
> Ask Stephane, Peter - I didn't send it to you because you don't
> have to install the ISDC system yourself - it's just a tip for
> those of us who do END
<peter> OK, I will. END
> Peter: how long can we expect RP1.4 to be the standard RP at ISDC? END
<peter> Good question. 
<peter> Probably long enough for all 'on-time' V2 deliveries ;-) END
> Let's hope we're on time then! END
<peter> It will definitely evolve further, e.g. to integrate background access in DAL3JEMX and
<peter> including new templates. I'll ask Stephane about his prediction. END
> Any more comments on RP1.4? END
<peter> Stephane says: probably up to mid-April. END
<larsson> No, except I had no problems installing either under solariss or Linux. END
> Good, Stefan! Okay next background data structure names, where are
> we up to on these Sami and Peter? END
<peter> IMHO we have them settled now, as long as we do not invent anything in addition. END
> I'd like templates for all of them in ADD5.0 END
<smaisala> Ok END
<peter> That's up to Sami but shouldn't be a problem. END
<smaisala> It is not a problem. END
> Okay, next AOB. I have some AOB: please will each of you tell me
> NOW what you'd like to discuss at the meeting next week so that
> I can make an agenda. Also, what time are you all arriving/leaving? END
<peter> Well, I'll be there from the day before :-). 
> Helsinki and Stockholm, what are your ETA's at DSRI? END
<larsson> I will arrive by overnight train (about 8 or so).
<peter> I want to talk about analysis architecture, data groups (beyond the SWG) and formats of analysis outputs. END
<njw> I'd like to see a presentation of the bkg treatment as it has been defined in Helsinki
<smaisala> I have same schelude I did last time. END
<njw> with a great effort in the last weeks END
> Remind me what that is Sami. END
<smaisala> I will be there at 9.00 am and I have to leave 18.30 END
> So the meeting will be 9.30 to about 18.00. Is that okay with everyone?END
<larsson> OK with me. END
<peter> Fine with me. END
<smaisala> OK END
> Good: so agenda is: background (architecture and data structures); data groups;
> analysis architecture; analysis outputs; add5.0; jemx.h; v2 status;
> I'll circulate a first draft agenda before the end of the week. END
> Finally, I need a V2 component-by-component status from each of you
> NOW for the monthly report - please email me after this chat END
> Any more AOB? END
<peter> OK. I'll try my best. END
<smaisala> same here END
> NJW? Stefan? END
<larsson> Yes. END
<peter> AOB: Has anybody thought about my question if we should split our analysis? END
> Yes: I don't like the idea. What if the big instruments change their
<peter> Sorry, split in separatae branches for spectra and lightcurves? END
> architecture? Do we have to change again? END
<larsson> I think we should stick to our present approach. END
<njw> OK to input to MR END
<peter> I don't think they would change again. And as I wrote, I prefer keeping our approach
> I don't see that we have to follow their architecture just because
<peter> but we should have an option for the user to get only one part. END
> the other instruments were the last to define their architecture ! END
> That can be handled by some parameter file switch, surely. And all
> data products have to be produced whether a given user wants them
> or not. END
<peter> All have to be produced in Standard Analysis but not necessarily in Offline. END
> Of course Offline will be run with all sorts of user-defined switches,
<peter> And I did not bring it up because the others did so, but also because it's sort of a 'natural' split. END
> so I don't see there's a problem. END
<peter> I don't see a real problem either but we should, IMHO, mention this already in the ADD. END
> We could put something in the overview section, but I don't see it
> as something nearly as important as describing background handling
> or calibration. END
> Perhaps when the offline possiblities are defined better, we can
<peter> You may be right there, but it is an architectural question. I'm happy with the general feeling but needed to bring it up. END
> include a  whole introduction in ADD6.0 on options available to
> users. END
> Okay, any more AOB ? END
<larsson> No. END
<peter> Nothing I can think of right now. END
> Okay, thanks for a brief chat: now remember I want three things
> from you all ASAP: contributions to ADD, contributions to jemx.h and
> component status for v2. I'm waiting! END
<peter> Yes ma'am! END
> That's the spirit! Bye for now END
<smaisala> Ok Bye END
*** njw has left channel #jemxadr : (bye)
*** smaisala has left channel #jemxadr : (smaisala)
<peter> Good bye, see you soon. I assume we won't have a chat next week. END
