Hi Bruce, At this rate, you are going to get a lot of tuppence. :-) Given 1) that the issue occurs when the number of projects reaches some unclear number, and 2) that the effect can be non-obviously changed data, I think that there should be an arbitrary, but safe number that can be bypassed as Shelly suggests. If the effect caused bells and whistles and the program to crash, then it would not be as much of an issue, but changed data without some obvious symptom of the change is dangerous. Mark -----Original Message----- From: ifeffit-bounces@millenia.cars.aps.anl.gov [mailto:ifeffit-bounces@millenia.cars.aps.anl.gov] On Behalf Of Kelly, Shelly D. Sent: Wednesday, May 09, 2007 12:11 PM To: Ravel, Bruce D.; XAFS Analysis using Ifeffit Subject: Re: [Ifeffit] care and feeding of Athena
So what do you all think? Is it better to impose the somewhat arbitrary limit that Scott suggests in hopes that it will work as intended most of the time? Or is it better to leave things as they are, allowing you to import more data but running the risk of corrupting Ifeffit's memory management?
Hi Bruce, I think that there should be a limit that is by default turned on and set to a value of something like 50 groups. This feature should be configurable so that the user, under a warning, can turn it off or change the group limit. Easy and configurable = plus 2cents. It occurs to me that a better way would be for Ifeffit (or Athena) to keep track of how much memory swapping is going on. Once it reaches some large but safe value, a warning is sent to the user. In this scenario the deleting and reading in a bunch of new groups would also trigger the warning. This seems like it would be hard to implement = negative 2cents. I'm even. Shelly _______________________________________________ Ifeffit mailing list Ifeffit@millenia.cars.aps.anl.gov http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit