
	SDAST WEEKLY CHAT MEETING #28: Tuesday 8th February 2000
	
Participating: Allan Hornstrup, Peter Kretschmar, Niels Joergen Westergaard,
	Juhani Huovelin, Sami Maisala, Petter Nikula, Stefan Larsson, Carol
	Anne Oxborrow.
	
Subjects discussed: DAL3JEMX API proposals: grey filter and background access
	New component names: using underscores and less than 20 characters
	Naming Detector coordintate: RAWX/RAWY, DETX/DETY

Action Items
	None.

**** Logging Started : Tue Feb 08 09:33:05 MET 2000
*** huovelin (~huovelin@taurus.astro.helsinki.fi) has joined channel #jemxadr
> Hi Juhani - it's good to have you with us END
<Peter> I'll be back in a minute ... END
*** Signoff: Peter (ircII/tkirc)
*** Peter (~pkretsch@isdcul10.unige.ch) has joined channel #jemxadr
*** smaisala (^smaisala@mizar.astro.helsinki.fi) has joined channel #jemxadr
> Hi Sami - now we just need Stefan and we'll be ready to start END
<smaisala> Hello everybody ! END
> Is Petter joining us? I gave him instructions on how to do chatting yesterday END
> We'll give Stefan two more minutes and then we'll have to start. END
> I think we'll start without Stefan,I've just rang his office and the
> secretary says he's working at home today. END
> First, Peter's proposals for DAL3JEMX. Let's have some positivie responses
> here! END
> Did everyone read Peter's email? END
<smaisala> Yes END
<njw> Y
<allan> y
<Peter> So what are your opinions finally?
> Personally, I don't feel a need for these functions: certainly not enough
> to force anyone to go off and code them. But you background chaps must have
> some clear ideas about what you want for background access. END
<njw> As Peter points out in the mail the background functions are not
<njw> very complicated and on the other hand they'll be good to have to
<njw> avoid thinking about the organization of the background spectra etc.
<njw> I'll vote for them END
> And what about our background Tzar? END
*** ponikula (^ponikula@mizar.astro.helsinki.fi) has joined channel #jemxadr
> Hi Petter - good that you could join us - so the instructions worked? END
<ponikula> Hi! Not quite I am afraid. END
<njw> Similarly the grey filter ones is a first step to the goal:
> We're discussing DAL3JEMX functions, specifically background access END
<njw> Producing corrected light curves and assigning errors to spectra END
<allan> It seems to me that the functions are needed to some extent and
<allan> at least good to have. So let's go for them END
<Peter> Since Stefan was also opting for them, if I remember correctly,
<Peter> let's settle for the straightforward functions. I will discuss implementation
<Peter> with Stephane this week or next. END
*** larsson (~larsson@tenma.dsri.dk) has joined channel #jemxadr
> So that's finished? We'll go with Peter's suggestions in the email? END
<njw> Y
<larsson> Sorry folks, problems with the trains this morning. END
> Hi Stefan, we've just finished discussing Peters second proposal for
> DAL3JEMX functions that he sent in an email last week. END
> Do you have any particular feelings about these functions, Stefan? END
<allan> We should also inform you, that we have agreed to implement them :-) END
<larsson> Hmm. I think they looked fine in Peters mail (I think I sent him a mail on that). END
<allan> You did END
> Okay, next on the agenda: name changes. Shall we go ahead and implement
> them? END
* allan No objections END
> Better sooner than later. END
<njw> If the 20  character limit for the name is strict we have to change anyway -
<huovelin> Implementing OK END
<larsson> True CA. I have no strong feelings either way though... END
<ponikula> Fine by me, also. END
> Good: so we'll go ahead with the name changes. However, this means ALOT of
<njw> I think that Peter's proposal is OK END
> work getting the ADD finished on time: Every component has to have new
> input tex file. All cross referencing has to be changed. All of the introductory
> chapter has to be updated, including the all-important diagram. Everyone of
> you must send a diagram to show what your new components are called and
> where they fit into the scheme of things - this applies especially to 
> Helsinki, who's processing changes with every delivery of ADD input.
> All this has to be done before the end of February, so be warned END
<allan> If the names are unique now,
<allan> and will be afterwards, isn't it then "easy" to
<allan> do a global swap?  Except for the 
<allan> drawings, of course END
> It's easy work, but it has to be done, and done by those who are coding the
> components, not by me END
<Peter> I agree with Carol Anne. For the others its a bit of either manual editing
<Peter> or daring to use sed :-) END
<larsson> No objections there. END
> Good stuff chaps: I'll expect your new input, and explantory diagrams in a couple of
<smaisala> I AGREE END
> weeks END
> Next, and final topic: what do we call our detector co-ordinates. After spending
> a week reading all the JEMX/ISDC manuals etc. it's clear that everyone
> whats to use X/Y for the detector coordinates AND X for the pointing 
> direction. X clearly exerts a strong psychological attraction for everyone. END
<huovelin> I am sorry, but the discussion seems to progress so slowly, that ...
<njw> Carl usually makes his plots with the cathode position as X-axis,
<huovelin> my possible contribution has to wait for some mails after this chat ...
> Also, the two detectors might be mounted at 90 degrees to each other. END
<njw> and the backplane position as Y-axis.
<njw> Would it be too complicated to use XCAT & YBACK ?? END
<huovelin> so, please, excuse me, I have to quit. Bye END
> Yes, that's Carl's convention, but it's not used consistently within the EID-B
> END
<Peter> Wait a second, there are also some OGIP standards that we would like to implement at ISDC. END
*** Signoff: huovelin ()
<Peter> To summarize:
<njw> OGIP uses DETX and DETY ?? END
<Peter> - ESA uses X as optical axis for some (strange) reasons. 
<Peter> - OGIP prefers DETX and DETY 
> So should we switch over to Y/Z? END
<larsson> I am among those who prefer to use X/Y in the detector plane, e.g. DETX,DETY
<Peter> - Since the orientation of the JEM-X instruments can _not_ be guaranteed to match
> I can live with DETX and DETY END
<njw> To CAO: No , I don't think so - there will be a confusion with S/C coordinates END
<Peter> the spacecraft Y & Z axes, finally I'd prefer to stay with DETX and DETY
<larsson> As long as we dont use simply X, Y we should have no real problem I think. END
<Peter> That is RAWX and RAWY for the uncorrected positions/
<Peter> and DETX, DETY for the corrected/actual ones END
<njw> Nevertheless I think that DETX should correspond to the cathode direction
<njw> and DETY to the backplane direction (the position - not the direction of the electrodes) END
> I agree with NJW: that way we get a consistenty between detectors. END
<smaisala> I think Peter's logic is clear END 
> Okay, so we have RAWX and RAWY for the positions gleaned direct from
<njw> And we should force Carl and co. to write a technical note on the
> telemetry and DETX and DETY for the corrected positions: the ones that
> come out of JCorrection? END
<ponikula> No comments ;) END
<njw> coordinate directions viz-a-viz signals END
> Did you write `FORCE Carl and co.'???? You can certainly try NJW, but I
> don't see `and co.' being very happy about it! END
<njw> Doesn't have to be more than a page END
> You could suggest that it be included in the next update of the EID-B. END
<Peter> Fine, I've looked up the OGIP proposal again and this use is exactly in line with the document. END
<njw> Good idea, CAO END
> Okay, I'm glad to get that cleared up. AOB anyone? END
<larsson> Coffee? END
<Peter> Not from me. But since I did not say it before, I support NJW's proposal for the
<Peter> definition of DETX, DETY. END
<allan> me too END
> Me too END
<larsson> Agree on DETX,DETY. END
<njw> Y
<Peter> OK, so it seems we have made several important decisions at breathtaking speed ...
<Peter> what di we do differently this time? END
> So to summarize meeting: yes to Peter's proposals, yes to name changes and
> yes to DETX/DETY, RAWX/RAWY. Good show chaps! Same time next week? END
<njw> Y
<ponikula> Sure! END
<allan> See you END
<smaisala> Y END
> We had a clear agenda, and stuck to it. END
*** allan has left channel #jemxadr : (Bye bye)
<smaisala> bye
*** njw has left channel #jemxadr : (Bye Bye)
<larsson> Yes. Bye. END
*** smaisala has left channel #jemxadr : (smaisala)
*** Signoff: larsson ()
<ponikula> /quit Bye!
