paida-users Mailing List for PAIDA (Page 3)
Brought to you by:
korry
You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
(2) |
Sep
(16) |
Oct
(7) |
Nov
(7) |
Dec
(3) |
2005 |
Jan
(1) |
Feb
|
Mar
(6) |
Apr
|
May
|
Jun
|
Jul
(6) |
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
(3) |
2006 |
Jan
|
Feb
|
Mar
(4) |
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2007 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
(4) |
Aug
(2) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
|
From: Koji K. <ko...@us...> - 2004-10-15 15:14:43
|
Hi Alex, I'm glad to receive your e-mail. It always makes PAIDA much better! > (1) storage of 2D histos: > is it possible that now there is some inconsitency between storage and > reading > back? when I read back a file written by PAIDA it complains about > weightedRmsX > or so not found. > (2) storage of ntuples: types > if the "type" of a column is a string, then PAIDA writes "String" and > JAIDA > "string" into the xml file. this causes problems when reading one with > the > other. I have no idea which one is correct. > (4) storage of strings in ntuples: > PAIDA writes strings with too many quotation marks in the xml file, > i.e. > instead of "my text" it writes "'my text'" I've comfirmed the miscodings then they will be fixed in the next bug fix release. > (3) storage of ntuples: names > JAIDA stores names with a la "ev=" "momentum=", i.e. with the equal > sign > even if there is no default value. PAIDA doesnt write "=" if there is > no > default value. > Again, I don't know what the behaviour should be. This is intended behaviour but it's not good not to be able to read from JAIDA's XML file. - JAIDA (or JAS3) can read both "momentum=" and "momentum" expressions. - PAIDA can read only "momentum" expression. This will be fixed in the next bug fix release. > (5) plotting: > well this one is a matter of taste but the box which is drawn around > each > region is either useless (in one-region plots) or too much and > confusing > (in multi-region plots).. at least for my taste. but thats not really > an > issue.. OK, you have a point there. I think it's better that the user can select the line and filling color of the box and the default is: - line : transparent - filling : white If there is another idea, please let me know. The changes will be included into the next minor version up release. (in the not-so-distant future) > (6) tree windows: > when closing a tree, its window should disappear?! (but doesnt?!) > moreover, sometimes it seems to get confused and opens an additional > window > for each ntuple inside a tree. maybe it would be better to put all > trees > in a single window anyway..? They are my mistakes. - The window should disappear when closed. - Unnecessary tree window was opened when the XML file has ITuple data. They will be fixed in the next bug fix release. Cheers Koji |
From: <dm...@bl...> - 2004-10-12 18:23:13
|
Hi Koji, thanks for the new release. Now it works better and better (especially the DOCTYPE fix helps a lot) and the problems become smaller and smaller, but I still found a few: (1) storage of 2D histos: is it possible that now there is some inconsitency between storage and reading back? when I read back a file written by PAIDA it complains about weightedRmsX or so not found. (2) storage of ntuples: types if the "type" of a column is a string, then PAIDA writes "String" and JAIDA "string" into the xml file. this causes problems when reading one with the other. I have no idea which one is correct. (3) storage of ntuples: names JAIDA stores names with a la "ev=" "momentum=", i.e. with the equal sign even if there is no default value. PAIDA doesnt write "=" if there is no default value. Again, I don't know what the behaviour should be. (4) storage of strings in ntuples: PAIDA writes strings with too many quotation marks in the xml file, i.e. instead of "my text" it writes "'my text'" (5) plotting: well this one is a matter of taste but the box which is drawn around each region is either useless (in one-region plots) or too much and confusing (in multi-region plots).. at least for my taste. but thats not really an issue.. (6) tree windows: when closing a tree, its window should disappear?! (but doesnt?!) moreover, sometimes it seems to get confused and opens an additional window for each ntuple inside a tree. maybe it would be better to put all trees in a single window anyway..? Cheers Alex |
From: Koji K. <ko...@us...> - 2004-10-02 07:00:56
|
paida-3.2.1_2.3 was released on 2004/09/01. [3.2.1_2.3] (AIDA3.2.1_PAIDA2.3) ### New features ### - Now works correctly on Windows platform. - Simple texts box for info.addText() is supported. - More faster on plotter.writeToFile() on MacOSX platform. - Experimental support for time scaled axis. - New faster fitting engine "simplePAIDA" which calculates only parabolic error. (not both parabolic and asymmetric errors.) ### Bug fixes ### - Old legends were always replaced by new legend. - Overlay plotting didn't work properly. (Histogram2D, Cloud2D, Profile2D, DataPointSet2D, Cloud3D and DataPointSet3D) - Plotting histogram1D or cloud1D with histogram format option was incorrect when the minimum X axis value is larger than 0.0. - "weightedRms" of each bin of histograms is omitted in the exported XML file. - Plotting objects which has zero entries raised an exception. - Improved support for GUI threading. - Reading <!DOCTYPE> line in a XML file raised an exception if you have no internet connection. |
From: Koji K. <ko...@us...> - 2004-10-02 06:49:44
|
Hi Alex, I've fixed all of the issues you pointed out. I'll release paida3.2.1_2.3 soon. Thank you for your helping! Regards, Koji |
From: Koji K. <ko...@us...> - 2004-09-28 13:26:00
|
Hi Peter, I have finally fixed the bug on Windows platform! I tested with Enthought Python 2.3.3. I'll release as paida-3.2.1-2.3 a couple of weeks later. If you need it immediately, please let me know. I'll send it in a separate email. Thanks Koji |
From: Koji K. <ko...@us...> - 2004-09-26 08:50:13
|
Hi Alex, I'm sorry for my late reply. I've been absent for a week. (i) Text in infobox I reached a determination. Now I think it will be better for PAIDA to be able to display three boxes: statistics, legends and texts. The texts box will display user-defined texts like fitted parameter values. (ii) DOCTYPE The Python documentation you suggested seems to be very helpful to this issue. I'll try to overwrite the handler. (iii) Fitting speed OK, in the next release, PAIDA will accept a option argument to limit the asymmetric error calculation. The fitting time will be reduced by about 50% at least. (iv) Plots with zero entries That's right. I had also found this bug and modified local copies to, as you mentioned, check the lower and upper values. Cheers, Koji |
From: <dm...@bl...> - 2004-09-20 17:46:57
|
Hi Koji, Text in infobox: The plotting implemtation in ANAPHE is only rudimentary, so I never really tried that. But in the code I see that the text is just appended to the legend items. It seems that there only seems to be one 'Infobox' which can contain text (user-defined or statistics/fitting params (i.e. annotations) of a histogram) or 'legends' (i.e. text with some graphics thing). This is also the impression I get from the AIDA definitions (which, I agree, are not very clear..) DOCTYPE: I looked a little bit around to find ways to suppress this problem: it seems that in the parser class (http://www.python.org/doc/current/lib/xmlparser-objects.html) there is a function StartDoctypeDeclHandler which may need to be overwritten in order to stop it from looking up the dtd file on the web? I don't know but maybe this hint can help you.. Fitting speed: I think it would useful to have the possibility to do simple error calculation only (if it speeds things up). Especially when you are in an interactive session you don't want to wait more than a few seconds for a (simple) fit result; at the same time you don't need the most sophisticated errors. 'New' plotting bug: Plotting (1D) histograms with zero entries results in some math exception because it tries to have a Y axis between 0 and 0. I don't know what the optimal behaviour should be, but checking upperY and lowerY and setting them to 1 and 0, respectively can be a solution (other plotting tools write a big 'no entries' in the middle of the plot which I personally don't like too much..) I didn't check the behaviour of 2D and 3D. Cheers, Alex |
From: Koji K. <ki...@po...> - 2004-09-16 01:51:45
|
Hi Alex, (1) Legend box Because I always used addLegend() with a new plotterStyle created by plotterFactory.createPlotterStyle(), the problem didn't come to my attention. This must be fixed. As you mentioned, Python stores only a reference and the easiest way to avoid it is creating its copy. I've prepared a internal method _createCopy() for a plotterStyle and used it in styled plot(). So, I can resolve this issue soon. (2) addText in info I'm sorry for the lack of documentation about this. The addText() is not implemented because I don't know how its behavior should be. At the time, his was not implemented also in JAIDA (at least 0.7.5 for MacOSX) and I could find no detailed documentation in AIDA. I have trouble with the text rendering position: (i) in the statistics box (ii) in the legends box (iii) in the "text box" (iv) any position in the region Would you tell me how ANAPHE does or the behavior should be? (I'm sorry but I can not use ANAPHE now form the computer environment reason.) (3) Fitting The main reason of slow fitting speed is, as you guessed, the pure Python coding. The others are because PAIDA calculates not only parabolic errors but also asymmetric errors at once and uses analytical derivatives of fitting function. Especially asymmetric error calculation needs much machine power in general. The possible optimizations in the future release: (i) provide a switch option for only calculating parabolic errors. (ii) provide a option to use scientific package in C or Fortran etc. like Numarray which relatively can be installed easily. (iii) more optimized pure Python coding. There are one for two canditate modules. (4) weightedRms The key of this issue is the accuracy. PAIDA uses the weightedRms values for reproduce the binRms data and this is used when histogram arithmetics (add, multiply etc.) in the histogramFactory. Of course, these arithmetics can be done only from histogram.mean() and histogram.rms() but I think it will be more accurate to calculate from each histogram.binMean() and histogram.binRms(). But when I reconsider this issue, it would be better not to use weightedRms for the XML data file commonality. I'll make a change. I am recently working for the critical bug of PAIDA on Windows platform, so I apologize to you about my slow fixing of bugs you pointed out. Regards, Koji |
From: <dm...@bl...> - 2004-09-14 18:30:51
|
Hi Koji, Some little details about the legend box etc: When plotting several histograms into the same region (lets say 1D and with line color black,red,blue) and then plotting the legend box, all linestyles will be the last linestyle which was plotted, i.e. blue. This is due to the addLegend function in IInfo. Actually, python will only store a reference to the style and not the style itself. So it will always point to the same (last) linestyle. I do not know any elegant way to cure that. Anyway, creating a new empty linestyle and then copying the color and addint this new linestyle to the list solves the problem (but it's ugly and error prone). I guess you know how to do that properly. The same will probably apply to the other types of styles (marker/fill) which can be added to the legend. In IInfo, plotting of the 'text' is not implemented (right?!). That's a pity because it is only a few lines: one loop to find the maximum length and another one to actually print it into the legend box. At least that worked for me. I used the addText to print fit parameters. Or is there a way to put those into the statisticsbox? (btw: fitting is really slow.. is this only because it is scripted, or is there still some optimization possible? the fit quality is very nice though..) Then I get a few divisionbyzero exceptions when reading in some of my 2D histos. But here I will check first whether that is not the fault of my histos. Btw: none of my histos produced with ANAPHE has the 'weightedRms' parameter set. I don't know whether this is according to AIDA specs. Anyway, setting it to 0 instead of throwing an exception works for me (but of course this could be related to the problem I mention above..) I'll check that. Cheers, Alex |
From: Koji K. <ko...@us...> - 2004-09-13 09:27:11
|
Hi Alex, > I found this is due to the quitting of the plotting method with > if not (lowerX <= binMeanX <= upperX): > around line 970-980 of IPlotterRegion if the bin shall not be drawn. > Of course, > the value 'previousHeight' is then not correct for the next bin. That's right. OK, for the meantime, this poroblem will be avoided by replacing from binMeanX = item.binMean(binNumber) if not (lowerX <= binMeanX <= upperX): continue height = convertY(lowerY, upperY, item.binHeight(binNumber)) binLower = convertX(lowerX, upperX, axisX.binLowerEdge(binNumber)) binUpper = convertX(lowerX, upperX, axisX.binUpperEdge(binNumber)) to binLowerEdge = axisX.binLowerEdge(binNumber) binUpperEdge = axisX.binUpperEdge(binNumber) if (binUpperEdge <= lowerX) or (upperX < binLowerEdge): continue height = convertY(lowerY, upperY, item.binHeight(binNumber)) binLower = convertX(lowerX, upperX, binLowerEdge) binUpper = convertX(lowerX, upperX, binUpperEdge) Of course, this is not the best way and some other problems still remain. I'll resolve all these problems in the next release. (Only histogram1D and cloud1D with the "histogram" format option are affected by this issue. So histogram2D and 3D are OK.) Thanks a lot for your helping! Koji |
From: <dm...@bl...> - 2004-09-12 10:10:11
|
Hi Koji thanks for your fast answers. I am making a lot of tests before writing hundreds of lines of scripts for paida for some project, thats why I still find some problems. One more is in the plotting of 1D histos: when drawing a bin, which has no neighbouring bin to its left and/or right (for example a bin which is not filled) the "borders" (i.e. connection lines to the neighbouring bins) are not correct. I found this is due to the quitting of the plotting method with if not (lowerX <= binMeanX <= upperX): around line 970-980 of IPlotterRegion if the bin shall not be drawn. Of course, the value 'previousHeight' is then not correct for the next bin. Setting a suitable value would help for the left border. For the right border there is no such easy solution. If the bin on the right is not drawn, the right border is not drawn. So for me it works not to quit the drawing at all. This will of course 'repaint' the x-axis in case of bins which are not filled.. but ok.. Otherwise for each bin which shall not be drawn it should be checked whether at least the left border must be drawn because there was a valid bin on the left. Maybe there are analogous problems for 2D and 3D histos?! Any idea? Cheers, Alex |
From: Koji K. <ko...@us...> - 2004-09-11 04:23:21
|
Hi Alex, Thank you for your continuing to use. (1) The issue of <!DOCTYPE> bothered me too. This behavior comes from Python's xml module. Because I didn't know how to avoid this, currently PAIDA doesn't generate the line <!DOCTYPE>. But, as you pointed out, if the importing xml file has the line, the xml module processes it and may raise an exception. Now, I'm going to try fixing it again! (2) I'm sorry but this seems to be a simple bug. I promise to fix in the next release. Koji |
From: <dm...@bl...> - 2004-09-10 11:50:33
|
Hi Sorry for my late response. I tried the fixes in 3.2.1_2.2.1 and now it reads in and plots my 2D datapointsets properly. Thanks a lot for the quick fix. However I found two new issues: (1) if I open an xml file with the dtd definition in the header, i.e. something like <!DOCTYPE aida SYSTEM "http://aida.freehep.org/schemas/3.0/aida.dtd" > it crashes if you don't have a web connection. If you are online, everything is fine. If you remove the line, everything is fine, too. I don't know whether this behaviour is a feature or whether it's the fault of some xml module. But it would be reasonable to ignore this line if no connection can be made. See for the output further down. (2) plotting an overlay of two different DataPointSets in the same region doesn't work (options: scatter and with error bars). Plotting them separately in different regions works fine. The error happens when calling region.plot() for the second time. Here again, I have no idea what is going on so I also append the output. Thanks for help Alex output to (1) Traceback (most recent call last): File "sampleDPS1.py", line 7, in ? tree = treeFactory.create("/home/alex/y2.xml","xml",True,False) File "/usr/lib/python2.3/site-packages/paida/paida_core/ITreeFactory.py", line 92, in create return ITree(storeName, storeType, readOnly) File "/usr/lib/python2.3/site-packages/paida/paida_gui/tkinter/ITree.py", line 1901, in __init__ parser.parse(fileObj) File "/usr/lib/python2.3/site-packages/_xmlplus/sax/expatreader.py", line 109, in parse xmlreader.IncrementalParser.parse(self, source) File "/usr/lib/python2.3/site-packages/_xmlplus/sax/xmlreader.py", line 123, in parse self.feed(buffer) File "/usr/lib/python2.3/site-packages/_xmlplus/sax/expatreader.py", line 216, in feed self._parser.Parse(data, isFinal) File "/usr/lib/python2.3/site-packages/_xmlplus/sax/expatreader.py", line 395, in external_entity_ref self._source.getSystemId() or File "/usr/lib/python2.3/site-packages/_xmlplus/sax/saxutils.py", line 515, in prepare_input_source f = urllib2.urlopen(source.getSystemId()) File "/usr/lib/python2.3/urllib2.py", line 129, in urlopen return _opener.open(url, data) File "/usr/lib/python2.3/urllib2.py", line 326, in open '_open', req) File "/usr/lib/python2.3/urllib2.py", line 306, in _call_chain result = func(*args) File "/usr/lib/python2.3/urllib2.py", line 901, in http_open return self.do_open(httplib.HTTP, req) File "/usr/lib/python2.3/urllib2.py", line 886, in do_open raise URLError(err) urllib2.URLError: <urlopen error (-3, 'Temporary failure in name resolution')> output to (2) Traceback (most recent call last): File "sampleDPS1.py", line 42, in ? region.plot(dps2) File "/usr/lib/python2.3/site-packages/paida/paida_gui/tkinter/IPlotterRegion.py", line 862, in plot self._plot(data1, plotterStyle, options) File "/usr/lib/python2.3/site-packages/paida/paida_gui/tkinter/IPlotterRegion.py", line 896, in _plot self._plotDataPointSet2D(data, plotterStyle, options) File "/usr/lib/python2.3/site-packages/paida/paida_gui/tkinter/IPlotterRegion.py", line 2029, in _plotDataPointSet2D canvasX = convertX(lowerX, upperX, valueX) UnboundLocalError: local variable 'convertX' referenced before assignment Killed |
From: Koji K. <ko...@us...> - 2004-09-09 11:23:04
|
Thank you for your reply. OK, now there must be a bug in PAIDA (on Windows). Please give me some time to fix it. Concerning sampleBasic.py, I'm sorry but it's just my fault. I'll fix it too. Koji On 2004/09/09, at 18:46, Peter Olsen wrote: > Koji, > > Oops! > > I also tried to use paida under Cygwin Python 2.3.4. It > failed there as well. > > Your suggestion about the example being out of phase with > the version I was using sounds plausible. > > BTW, I wasn't ever able to download source code for the > first example, sampleBasic.py. I kept getting unprintable > characters. I was able to download another example, > sampleHistogram2D.py, but that froze too. > > Peter > > > Peter Olsen, PE, Ae.E. > National Security Analysis Group > The MITRE Corporation > 877-631-6178 (pager) |
From: Peter O. <po...@mi...> - 2004-09-09 09:46:58
|
Koji, Oops! I also tried to use paida under Cygwin Python 2.3.4. It failed there as well. Your suggestion about the example being out of phase with the version I was using sounds plausible. BTW, I wasn't ever able to download source code for the first example, sampleBasic.py. I kept getting unprintable characters. I was able to download another example, sampleHistogram2D.py, but that froze too. Peter Peter Olsen, PE, Ae.E. National Security Analysis Group The MITRE Corporation 877-631-6178 (pager) -----Original Message----- From: pai...@li... [mailto:pai...@li...] On Behalf Of Koji KISHIMOTO Sent: Wednesday, September 08, 2004 11:29 PM To: pai...@li... Cc: Peter Olsen Subject: Re: [paida-users] paida freezes under both Enthought Python 2.3.3 and Cygwin python 2.3.3 First of all, let me ask the version number of your PAIDA because It seems that the examples you are using are for the old version 3.0a1. (currently 3.2.1_2.2.1) If you are using the latest version, the problem may be caused by the threading module. I'm trying to test with Cygwin python 2.3.3 and will report the results. Koji ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ paida-users mailing list pai...@li... https://lists.sourceforge.net/lists/listinfo/paida-users |
From: Peter O. <po...@mi...> - 2004-09-09 09:39:27
|
I'm using the newest version of paida and the examples off of the web page, http://paida.sourceforge.net/paida-3.2.1_2.2/documentation/i ndex.html. This is once sub.sub.version behind, but it's the documentation page pointed to by the latest version. (Perhaps that's the problem right there. I didn't think of that.) I'll be away from my office computer today, but you can still reach me from-time-to-time at pc...@co.... The actual python I was using was Enthought's modification of Python 2.3.4 for windows. Enthought has packaged Numeric, SciPy, and several other things in the basic distribution so they are available straight out-of-the-box. Peter Olsen, PE, Ae.E. National Security Analysis Group The MITRE Corporation 877-631-6178 (pager) -----Original Message----- From: pai...@li... [mailto:pai...@li...] On Behalf Of Koji KISHIMOTO Sent: Wednesday, September 08, 2004 11:29 PM To: pai...@li... Cc: Peter Olsen Subject: Re: [paida-users] paida freezes under both Enthought Python 2.3.3 and Cygwin python 2.3.3 First of all, let me ask the version number of your PAIDA because It seems that the examples you are using are for the old version 3.0a1. (currently 3.2.1_2.2.1) If you are using the latest version, the problem may be caused by the threading module. I'm trying to test with Cygwin python 2.3.3 and will report the results. Koji ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ paida-users mailing list pai...@li... https://lists.sourceforge.net/lists/listinfo/paida-users |
From: Koji K. <ko...@us...> - 2004-09-09 03:29:08
|
First of all, let me ask the version number of your PAIDA because It seems that the examples you are using are for the old version 3.0a1. (currently 3.2.1_2.2.1) If you are using the latest version, the problem may be caused by the threading module. I'm trying to test with Cygwin python 2.3.3 and will report the results. Koji |
From: Peter O. <po...@mi...> - 2004-09-08 18:12:51
|
I've been trying to install and run paida, but I can't get any of the examples to run. Every time I try, python freezes solid. I have to kill the process to escape. I've tried several programs from the documentation, but they all fail. (I had some trouble downloading the first, I believe I've traced the problem (or at least the first problem) to a specific line. I've included below the simplest script I've found. I've shown where I think things are falling apart. I'm down to a short deadline for a data analysis problem, so I'd really appreciate some help. Otherwise I'll be using gnuplot. That's nice, but I think paida will be nicer. ------------------------------------------------------------ ---------------------------------- from paida.paida_core import IAnalysisFactory # Analysis factory. af = IAnalysisFactory.create() # Tree factory. tf = af.createTreeFactory() # Tree with zipped XML storing. tree = tf.create("test.aida", 'xml', False, True, "compress=yes") <<<<<<<<<< I think things hang here. # Histogram factory. hf = af.createHistogramFactory(tree) # 1d histogram. h1d = hf.createHistogram1D('test name', 'test title', 10, 0.0, 10.0) ## You can use Int in lower edge value etc. ## I think this is more Python-like. ## h1d = hf.createHistogram1D('test name', 'test title', 10, 0, 10) # Filling. h1d.fill(2.0) h1d.fill(4.0) ## Off course you can write ## h1d.fill(2) ## h1d.fill(4) # Check. print 'Mean is 3.0? :', h1d.mean() # Save all data. tree.commit() tree.close() Peter Olsen, PE, Ae.E. National Security Analysis Group The MITRE Corporation 877-631-6178 (pager) |
From: Koji K. <ko...@us...> - 2004-09-01 06:49:23
|
paida-3.2.1_2.2.1 was released on 2004/09/01. [3.2.1_2.2.1] (AIDA3.2.1_PAIDA2.2.1) This is the bug fix release. ### Bug fixes ### - A tree did not export dataPointSet objects correctly to a XML file. - A tree did not import dataPointSet objects correctly from a XML file. |
From: Koji K. <ko...@us...> - 2004-09-01 06:43:24
|
Hi Alex, Thank you for your detailed pointing out and it was very helpful to the debugging. As you say, they were simple bugs and I've fixed them. - checking </dataPointSet> correctly - adding a closing tag </dataPoint> for every dataPoint - filling imported dataPointSet data to all dimensions correctly I will release a bug fix version 3.2.1_2.2.1 soon. Please try it out. Cheers, Koji |
From: <dm...@bl...> - 2004-08-31 13:13:03
|
Hi all, I am running 3.2.1_2.2 on a SUSE 9.1 box and have a number of problems with DataPointSets reflected in the 'history' of things I did: -I tried to open an xml file created with ANAPHE (from CERN) with a 2D DataPointSet and it fails with an unknown tag exception in paida_gui/tkinter/ITree.py (line 1360 or so..) -First I thought this is due to incompatible xml files so I changed the DataPointSet example to store the tree in a file and tried to read it in. Again exception about unkown tag "dataPointSet". -I tried to find out why and it seems that once inside a DataPointSet tag it does not check for a </dataPointSet> end tag but instead for a "profile2d" end tag. -After this fix it does not fail to read in the datapointset from the example but it only reads in the first of the eight datapoints (confirmed by the 'size'). Looking into the xml file it seems that the end tag for all datapoints is missing. A cross-check with my file from ANAPHE confirms that there should be one. -Reading in the datapointset from the ANAPHE file works. Even size and dimension give the correct values. But when trying to plot it, it throws another exception and I gave up (not even remembering where exactly it fails...) Any help/ideas/comments? I assume the problems are due to quite simple bugs which could only survive because DataPointSets may not be as heavily tested as histograms and ntuples?? Thanks Alex |
From: K.KISHIMOTO <ko...@us...> - 2004-08-19 09:29:48
|
paida3.2.1_2.2 was released on 2004/08/19. [3.2.1_2.2] (AIDA3.2.1_PAIDA2.2) ### New features ### - Now PAIDA can plot all types of AIDA objects including 3D histogram, cloud and dataPointSet. - More precise and the same position control on various platforms. - Simple tree window. - Transparent color is supported. Setting color to "" will select this behavior. ### Bug fixes ### - The output postscript file is more precise now. - PAIDA attempts the default font to be set to "Courier". - Profile2D was not created correctly. - .binEntriesX() etc. in histogram2D, histogram3D and profile2D raised an exception. - .fill() in histogram3D raised an exception. - .createCopy() in histogramFactory raised an exception. - .symlink() in tree raised an exception. Enjoy! |
From: K.KISHIMOTO <ko...@us...> - 2004-06-15 12:16:22
|
paida3.2.1_2.1.1 was released on 2004/06/15. This is the bug fix release. - The tick line length was zero in a small plotter region. Enjoy! |