Thread: [paida-users] new release
Brought to you by:
korry
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-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 |