SDAST Chat meeting #103: Wednesday 2005/05/04 Present: Peter Kretschmar, Silvia Martinez-Nunez, Jerome Chenevez, Carol Anne Oxborrow, Niels Jørgen Westergaard, Stefan Larsson Subjects discussed OSA 5.0 status: A low priority SPR still open on j_cor_gain Roland blocked the SCREW on the detector map, so that's not done Low-priority SPR on j_calib_gain_fitting will be done without reference to OSA 5.0 Schedule Silvia waiting on delivery of new IC files to deliver working scripts Back projection and IMOD files have been delivered IROS still has one open SPR so another delivery is due Still an open SPR on j_ima_shadowgram Spectral calibration still to be done Stefan bogged down in teaching: one more delivery needed for keyword update - validation will need latest IC data from NJW, first due next week (responses etc.) JC has completed his planned deliveries for mosaicking Peter's components will not be updated, but he needs to correct a bug he added to j_correction GRB seen just 1.5 hours ago - second one in less then 54 hours ISDC rotation: latest line up emailed to CAO to put on the forum, though rotation hasn't been followed very well up to now (2 months out of 4!) Subject of people power and how to deploy it must be discussed thoroughly at SDAST meeting in June AI on smart selection closed: CAO to put NJW's email on the Forum Chat meeting rate should be at least every other week Jerome will be at ISDC next week: in addition to the usual he should discuss mosaicking, validation, strange user results - should also try to circulate an email summary of his activities there. **** Logging Started : Wed May 04 10:58:15 MEST 2005 *** silvia (~silvia@130.226.216.2) has joined channel #jemxadr *** jerome (~jerome@130.226.216.2) has joined channel #jemxadr *** larsson (~larsson@130.226.216.181) has joined channel #jemxadr Hi Hello there! *** peter (~pkretsch@isdcsf5.unige.ch) has joined channel #jemxadr ¡Hola chicos! Hola, Peter, you want to impress us with your spanish! END Good morning everyone ! END > Hello everyone!! It's good to see you all turned up! END *** njw (~njw@130.226.216.2) has joined channel #jemxadr Not really - there's not yet too much to boast with :-) Hello all, sorry I'm late END > Well, I'm impressed. I hope `chicos' is something nice. END chicos means guys ! END > Since we're all here let's get going: Point one OSA 5.0 status. I'll start > the ball rolling: The SPR on j_cor_gain where is fails for various Then you and me Carol Anne are exclued :-) END > (a couple of) non-standard revolutions will not be done in time for OSA 5.0 W.r.t Spanish: our teacher explained to us that in mixed company the male form is used always, as Spanish is a 'macho' language :-) > I don't think, because the gain aging factors take precedence. As explained > in my email to Isabelle, there is a work-around for tough revolutions that's > well documented. I would like to get the detector map thing implemented > for the 5.1 release, but this seems to require a lot of negotiation with > Roland, who clearly would rather that we leave things well alone. > The `anti-glitch' SPR on j_calib-gain_fitting, is similarly low priority > and is not technically part of OSA, so will be delivered ASAP independently > of the OSA schedule. That's all folks. Next up.....Silvia. How's it going > with you Silvia? END Regarding the detector map, I think Roland's point was that it would only make sense if we have coordinated deliveries such that downstream The scripts are running fine using the latest executables at ISDC since two weeks ago but I was waiting for the ingestion of the latest IC files to deliver them analysis S/W actually uses it, which was not the case for OSA 5.0 anymore > But it needs to be implemented in j_cor_gain, then in imaging, then in > source extraction, and the last two can't be done until the first step is > taken. END Today, thanks to Peter, I have already find these calibration files at the ISDC system. And I hope to deliver them this morning. > Good news, Silvia - so we're practically complete for OSA 5.0? END Yes, we are. END What it worry me, is the validation of the current software, mainly the j_ima_iros results. END Well, I found a problem in the j_correction script (SPR 4122) which I need o fix soon. END Otherwise, I agree with Silvia! END On j_ima_iros I can tell that we have one more SPR so at least one more delivery has > Great! Of course validation is a worry, for all components, but at least to be made, but th eproblem has been fixed. > we've got the foundations laid. END The bacprojection lists and the IMOD updates have been delivered for the IC tree. > How soon can you do this NJW? Silvia, is there any problem getting the > last delivery of j_ima_iros integrated? END There is an SPR on j_ima_shadowgram that I'll try to deal with (the REST/FULL energy ranges). A new spectral calibration series has also to be done EMD EMD=END END I think it should be easier than the integration for the first version of j_ima_iros ! END > NJW anything more to add on your OSA status? END No, except that I will probably be able to deliver j_ima_iros-1.3.0 today END Then, should I include this new version of j_ima_iros before delivering the scripts ? END What kind of deadline are we up against ? If we have a couple of days more then I think you should * njw wait END > Yes, I think so - there's not point wasting time and energy making two > deliveries. END We already one month late :-) but I htink ISDC can wait a couple of days more END > Can we move on to Stefan's OSA Status? END I have had little time for anything else than teaching NJW: I will appreciate to receive an e-mail with the changes done in this new version, mainly parameters and IC changes. END the last few weeks. When I have been through all the exams on my course (later today) I will make an effort to reread my thoughts from a few weeks back to get back on the software track... I would like to make a minor update (no interface changes) if there is time for that. Within days. > Have you delivered everything you intend to deliver for OSA 5.0? END (1 or 2 maybe) END What exactly would that update be? What is the timetable for the very imprtant validation? END Keyword update. Validation for me will be to go through the results of the set of Crab analysis. I can spend maybe two days on this. When depends on the shedule. I think this should be done with the new responses. When will they be available Niels J Some time next week END "Internal" testing of my components I have done. What is needed is the global test at different time epoch etc. END > Any more comments on Stefan's status? Stefan, could you send me the delivery tar.gz files of your components or show me where to grab them ? END To NJ: I will mail you info of that. END Thanks END > Okay, we'll move on to Jerome's OSA 5.0 Status. END May I first just call your attention to the GRB observed 1h1/2 ago? This is the 2nd one in JEM-X FoV in less than 54h! Well, regarding j_ima_mosaic, the version 5.0.1 has been succesfully delivered already some time ago. I just wonder if there have been any soul testing it, because I have not got any kind of feedback yet. But i do not complain :-) END > Like they say: no news is good news! Perhaps there's no need for feedback! I've tried but ran into the j_correction problem first ... END > END > Peter did you give a status? END No, not yet. > Fire away, Peter, END My executables have not and won't be updated. But I'll have to fix the erronous code I put into j_correction. END > Is that everyone? If there are no more comments, let's move on to the > issue of ISDC rotation. Jerome could you let us know when everyone should No other news. I held myself available to support Silvia somewhat but she did the integration so competently, I actually had time for some other problems. END > be at ISDC? Also, shouldn't we have a more streamlined idea of what whe > should do when we get there? And what's the policy on months where people > simply don't go? END Ok, the rotation list has been distributed several time at this forum but, since it is not really followed by the intereted people I wonder why we still have to have this list...? Anyway, as you know I take my turn next week. Regarding what we should do when we are at ISDC, I think this issue has already been discussed several times. I guess we have to show up and discuss with people there. Agreed. Also maintain the instrument station if there is need. Run ISWT analysis with OSA and diffuse the results. What else? END > I can't think of anything else. Can't we do the GPS data thing from here? What do you mean -here-? > Could you send me the very latest version of the list so I can be sure Regarding my involment in the ISDC rotation, my institute financial situation is not good right now. Niels told me that the DNSC can support my trips to ISDC, but may be it is better to postpone my turn until my institue receives the money for hte new project (October- November). END > that we're all updated on the forum, so no one has any excuses for not > turning up when they should. END > `Here' means, `at home' i.e. without having to go to ISDC. END As far as I can see you already have the updated list... No changes have been made. Not so many visits neither! END regarding the analysis thing, yes og course you can so it from your office but do you do it? So I mean that may be the occasion to make the analysis when we are at ISDC > No, that's true I don't do it here. But then again it's always rather hard directly connected to ISDC machines. END > getting it done there. Anyway, are there any further comments? END N > Next the SDAST meeting in June: any absolutely essential subjects to > address? END You mean besides the general status and where we want to go to? END I think we should discuss how Stefan's components will survive and continue evolution > Yes, beside the generic subjects. If no one can think of anything essential > we can move on. END As I understand it Stefan will have less and less time to do this, ritght Stefan ? END Yes.... END I've just had a call from Stephane Paltani. He wants very much to have the j_ima_iros new delivery as soon as possible. They are going to do some serious testing at ISDC with the OSA5 component. Stephane also thinks that you, Silvia, can deliver the script irrespective of the j_ima_iros delivery since there are no parameter nor IC changes, but Stephane will * njw contact you. END > If there are no pressing matters concerning next month's meeting, let's > move on to something very pressing: people power and how to deploy it. > As just mentioned, Stefan has less and less time for this work, so who's > going to take it over? Also, who's responsible for background handling and > model determination now? END To NJW: Stephane Paltani has already called me. After the chat, I will like to talk with you by phone. END OK END I'm afraid that the background model updates etc. is left in the dark. Is anybody ready to I _might_ take over a large part of Stefan's work, but still have to see in the coming weeks how things develop. END take up this work ? END Maybe I could take up Bkg modelling, but this will not be before the other side of summer. END > I think a full discussion of this topic should be made at the next meeting > (real meeting that is). I can't take on any more work for JEM-X because > I already owe a couple of months of work to planck. END That will be fine, Jèrôme, we are not using the background info very much, actually one of the components, j_ima_basic_recon has just dropped out END I have to discuss with Victor and Niels my future involment. Next SDAST meeting is a good time to talk about it. END > So let's put this on the agenda - it needs a thorough discussion. END > AI list - anyone accidently done some AIs? END Well, not really, but I can describe how the 'semi-smart' radius selection is done in Why don't you circulate that as email? END I'll promise to read it! END j_ima_iros. Four radii are given as parameters, each associated with an energy (are you asking me or CAO?) Perhaps I should continue in an email END No closed AI's from my side - sorry END No AIs closed here... END > If you write and email about the Smart Selection and how it's done in iros, > then that becomes the default standard I think - so then it's up to > everyone else to implement it in the same way, I think. Please circulate > the email and I'll close the AI. > Any more soon-to-closed AIs? Has everyone read the current list? END Y N Y Well, maybe not read but at least looked... END Y, I do not have AI ... good ... END Y > Okay, on to AOB. I'd like to suggest that we hold chat meetings just once > a month.......they have been described by someone who shall remain nameless > as `a waste of time'. So how about we keep it to once a month, say the > first wednesday of every month. That way we get to hear the mournful sound > of the testing of the emergency response sirens at the same time! END > Thanks for the email NJW: the AI is now closed. END I don't hear that siren and frankly my feeling was that we rather had too little communication than too much the last months. END So if we have to hear the sirenes while we chat, that makes them only once a year... END It is true that our communication rate should increase since we have several tasks in the > So others would like to keep it at every other week, or what? END I agree with Peter. We had have little communication regarding changes in the executables that have implications on the rest of the pipeline. END near future and one of them is the Science Validation Report. In my opinin, we should chat at least every two weeks. END It is due in less than a month and we need to produce some OSA5 results END I think this kind of communication can be made by email and should not wait for an eventaul chat meeting. RND END Some yes, but then you must remember sending the mail. The chats often trigger activity on 'small' questions which otherwise go under. Email is always a possibility but chats are good for arising the interest for the AI list and tieing up loose ends END Evidently they are less useful for you guys at DSRI but for Stefan, Silvia and myself, quite a bit only gets discussed in the chats. END OK, then that means that you need the chat meetings. END > Personally every week or every other week is fine with me, but what do you > guys outside DNSC need? END > Shall we stick with every other week? This seems to be our natural rate. END I think so. END Y Well, information ... a summary of what is going on, what the plans are for the next weeks etc. Yes, I like the "other" week... English is nice :-) END y Some of this oculd come by email but the chat allows asking questions more immediately. END > We'll stick to every other week. Any more AOB?? END No. END N N Sorry Yes! Have anybody any inputs to me for my visit at ISDC next week? END No at the moment. END n N Well, I assume you discuss mosaic questions and validation results in detail. > Let us know whether actual users are getting strange results - odd spectral Yes, at least I know quite well the mosaic part of the S/W. END > bumps etc. END It would be nice if you could write up and circulate a summary of your findings & discussions. END Ok, I will try that but I do not promise anything. I am not as good as Carol Anne to write everything done! END done : down Anyone is as good as Carol Anne :-) END > Let's call it a day folks! We've got a meeting to get to I'm afraid. END > Thanks Silvia - it's nice to know I have a little fan club out there! END We will forgive some small shortcomings compared to the one and only Carol Anne :-) END Yes a meeting with a plate aknife and a fork at least. END You are welcome ! Bye everyone ! I have also a meeting with my boss. END > Chat with you all in 2 weeks! I promise! Bye! END OK, "see" you guys in 2 weeks then, don't let that keep you from busy email exchanges. END Bye > No a meeting of the Dansk magisterforening! END TO NJW : do you have now sometime to talk with me ? END