Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(58) |
Nov
(95) |
Dec
(55) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(205) |
Feb
(106) |
Mar
(36) |
Apr
(25) |
May
(34) |
Jun
(36) |
Jul
(161) |
Aug
(66) |
Sep
(100) |
Oct
(62) |
Nov
(77) |
Dec
(172) |
2003 |
Jan
(101) |
Feb
(202) |
Mar
(191) |
Apr
(97) |
May
(27) |
Jun
(21) |
Jul
(16) |
Aug
(55) |
Sep
(155) |
Oct
(166) |
Nov
(19) |
Dec
(134) |
2004 |
Jan
(569) |
Feb
(367) |
Mar
(81) |
Apr
(62) |
May
(124) |
Jun
(77) |
Jul
(85) |
Aug
(80) |
Sep
(66) |
Oct
(42) |
Nov
(20) |
Dec
(133) |
2005 |
Jan
(192) |
Feb
(143) |
Mar
(183) |
Apr
(128) |
May
(136) |
Jun
(18) |
Jul
(22) |
Aug
(33) |
Sep
(20) |
Oct
(12) |
Nov
(80) |
Dec
(44) |
2006 |
Jan
(42) |
Feb
(38) |
Mar
(17) |
Apr
(112) |
May
(220) |
Jun
(67) |
Jul
(96) |
Aug
(214) |
Sep
(104) |
Oct
(67) |
Nov
(150) |
Dec
(103) |
2007 |
Jan
(111) |
Feb
(50) |
Mar
(113) |
Apr
(19) |
May
(32) |
Jun
(34) |
Jul
(61) |
Aug
(103) |
Sep
(75) |
Oct
(99) |
Nov
(102) |
Dec
(40) |
2008 |
Jan
(86) |
Feb
(56) |
Mar
(104) |
Apr
(50) |
May
(45) |
Jun
(64) |
Jul
(71) |
Aug
(147) |
Sep
(132) |
Oct
(176) |
Nov
(46) |
Dec
(136) |
2009 |
Jan
(159) |
Feb
(136) |
Mar
(188) |
Apr
(189) |
May
(166) |
Jun
(97) |
Jul
(160) |
Aug
(235) |
Sep
(163) |
Oct
(46) |
Nov
(99) |
Dec
(54) |
2010 |
Jan
(104) |
Feb
(121) |
Mar
(153) |
Apr
(75) |
May
(138) |
Jun
(63) |
Jul
(61) |
Aug
(27) |
Sep
(93) |
Oct
(63) |
Nov
(40) |
Dec
(102) |
2011 |
Jan
(52) |
Feb
(26) |
Mar
(61) |
Apr
(27) |
May
(33) |
Jun
(43) |
Jul
(37) |
Aug
(53) |
Sep
(58) |
Oct
(63) |
Nov
(67) |
Dec
(16) |
2012 |
Jan
(97) |
Feb
(34) |
Mar
(6) |
Apr
(18) |
May
(32) |
Jun
(9) |
Jul
(17) |
Aug
(78) |
Sep
(24) |
Oct
(101) |
Nov
(31) |
Dec
(7) |
2013 |
Jan
(44) |
Feb
(35) |
Mar
(59) |
Apr
(17) |
May
(29) |
Jun
(38) |
Jul
(48) |
Aug
(46) |
Sep
(74) |
Oct
(140) |
Nov
(94) |
Dec
(177) |
2014 |
Jan
(94) |
Feb
(74) |
Mar
(75) |
Apr
(63) |
May
(24) |
Jun
(1) |
Jul
(30) |
Aug
(112) |
Sep
(78) |
Oct
(137) |
Nov
(60) |
Dec
(17) |
2015 |
Jan
(128) |
Feb
(254) |
Mar
(273) |
Apr
(137) |
May
(181) |
Jun
(157) |
Jul
(83) |
Aug
(34) |
Sep
(26) |
Oct
(9) |
Nov
(24) |
Dec
(43) |
2016 |
Jan
(94) |
Feb
(77) |
Mar
(83) |
Apr
(19) |
May
(39) |
Jun
(1) |
Jul
(5) |
Aug
(10) |
Sep
(28) |
Oct
(34) |
Nov
(82) |
Dec
(301) |
2017 |
Jan
(53) |
Feb
(50) |
Mar
(11) |
Apr
(15) |
May
(23) |
Jun
(36) |
Jul
(84) |
Aug
(90) |
Sep
(35) |
Oct
(81) |
Nov
(13) |
Dec
(11) |
2018 |
Jan
(15) |
Feb
(4) |
Mar
(2) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
|
1
|
2
|
3
|
4
(2) |
5
|
6
|
7
(4) |
8
(6) |
9
|
10
(3) |
11
(6) |
12
|
13
(1) |
14
(3) |
15
(7) |
16
(5) |
17
(7) |
18
(21) |
19
(8) |
20
(7) |
21
(30) |
22
(21) |
23
(2) |
24
(26) |
25
(5) |
26
(1) |
27
(3) |
28
(9) |
29
(16) |
30
(9) |
31
(3) |
|
|
From: Alan W. Irwin <irwin@be...> - 2002-01-16 22:10:38
|
I received no response on the java source install question so I made some executive decisions: the class files will be retained for ...lib/java/plplot/core. My understanding is these binary files are analogous to a library in the sense they are required to run any application that uses the java front end to plplot. Thus, like a library I install only the binary *.class files and not the source *.java files. The situation is different for all the other examples where we install the source but no binaries. To follow this idea for the java examples, the *.java files (but not the *.class files) are now installed in .../lib/java/plplot/examples. Furthermore, the new README I created (see plplot/examples/java/README) that explains how to build the java examples either from the tmp location or the install location is also installed in .../lib/java/plplot/examples. Joao, I wrote those instructions at your suggestion. By all means please give the instructions a try, and let me know if they need any additions. Alan email: irwin@... phone: 250-727-2902 FAX: 250-721-7715 snail-mail: Dr. Alan W. Irwin Department of Physics and Astronomy, University of Victoria, P.O. Box 3055, Victoria, British Columbia, Canada, V8W 3P6 __________________________ Linux-powered astrophysics __________________________ |
From: Maurice LeBrun <mjl@ga...> - 2002-01-16 06:00:07
|
Alan W. Irwin writes: > Point well taken, but I have investigated further, and there is more to this > story that I didn't understand before. From the above example $ y - > 3.123456 has access to the full ~17 digit precision of y before subtracting the > constant from it so there are actually still 10 significant digits left in > the result (note the last two "81" digits are incorrect because the internal > precision of y is roughly 17 digits.) > > But look how the corresponding matrix result does not act this way. > > pltcl> set tcl_precision 12 > 12 > pltcl> matrix a f 1 = {3.1234567890123456789} > a > pltcl> puts [expr [a 0] - 3.123456] > 7.89010000002e-07 > > There are 5 fewer significant digits in this result than for the y - const > result. > > My mental model of what is going on here is as follows: unlike $y - const, > [a 0] - const only has access to tcl_precision digits of precision for > matrix values. In other words set tcl_precision effectively sets the > internal precision of matrix calculations rather than simply limiting the > number of digits emitted for results. The story becomes more interesting. I believe the two representations (variable or tclMatrix) would've given the same result in pre-Tcl8.0. The reason being that in the old Tcl, "everything's a string". But no longer -- the variable that you create with "set" is "dual-ported", meaning it has both a binary and string representation. The binary one is used in expression evaluations and so is more accurate. I've been poring over the documentation, and I think it's feasible to change tclMatrix to emit objects instead of strings, which seems to be the right way to really fix this. Also will help a lot with performance. The object is equipped with procedure calls to convert it to strings when necessary. Unfortunately this is a pretty major undertaking, and not one I care to get into right now. So as for a stopgap measure, I'll change it to carry 12 digits of precision, both internally and externally. I tried 17 but didn't like the result. E.g. pltcl> matrix c f 3 = {3.2 4.5 5.7} c pltcl> puts [c *] 3.2000000000000002 4.5 5.7000000000000002 which the tclvars man page warns about. -- Maurice LeBrun mjl@... |
From: Maurice LeBrun <mjl@ga...> - 2002-01-16 02:36:00
|
Alan W. Irwin writes: > Point well taken, but I have investigated further, and there is more to this > story that I didn't understand before. From the above example $ y - > 3.123456 has access to the full ~17 digit precision of y before subtracting the > constant from it so there are actually still 10 significant digits left in > the result (note the last two "81" digits are incorrect because the internal > precision of y is roughly 17 digits.) > > But look how the corresponding matrix result does not act this way. > > pltcl> set tcl_precision 12 > 12 > pltcl> matrix a f 1 = {3.1234567890123456789} > a > pltcl> puts [expr [a 0] - 3.123456] > 7.89010000002e-07 > > There are 5 fewer significant digits in this result than for the y - const > result. > > My mental model of what is going on here is as follows: unlike $y - const, > [a 0] - const only has access to tcl_precision digits of precision for > matrix values. In other words set tcl_precision effectively sets the > internal precision of matrix calculations rather than simply limiting the > number of digits emitted for results. You're right, it's still not really right. Will look into it some more. -- Maurice LeBrun mjl@... |
From: Alan W. Irwin <irwin@be...> - 2002-01-16 00:45:57
|
On Tue, 15 Jan 2002, Maurice LeBrun wrote: > Alan W. Irwin writes: > > Thanks for your fix. At first I thought there was a 12-digit limit to the > > matrix precision, but that is just the default value of tcl_precision. If I > > set it to 17 I get full double-precision results. > > > > BTW, tcl_precision doesn't seem to have universal application. My tests > > indicated the internal precision of ordinary variables in pltcl was 17 > > digits regardless of what tcl_precision value was set. For example with > > the default (12) value of tcl_precision I get the following results: > > > > pltcl> set y 3.12345678901234567890 > > 3.12345678901234567890 > > pltcl> puts [expr $y - 3.123456] > > 7.89012345681e-07 > 1 234567890ab > > ..i.e. 12 digits of precision. Point well taken, but I have investigated further, and there is more to this story that I didn't understand before. From the above example $ y - 3.123456 has access to the full ~17 digit precision of y before subtracting the constant from it so there are actually still 10 significant digits left in the result (note the last two "81" digits are incorrect because the internal precision of y is roughly 17 digits.) But look how the corresponding matrix result does not act this way. pltcl> set tcl_precision 12 12 pltcl> matrix a f 1 = {3.1234567890123456789} a pltcl> puts [expr [a 0] - 3.123456] 7.89010000002e-07 There are 5 fewer significant digits in this result than for the y - const result. My mental model of what is going on here is as follows: unlike $y - const, [a 0] - const only has access to tcl_precision digits of precision for matrix values. In other words set tcl_precision effectively sets the internal precision of matrix calculations rather than simply limiting the number of digits emitted for results. > > I would prefer matrix to act the same way regardless ot tcl_precision. > > Therefore, could you just set the matrix precision to 17 digits when PLFLT > > is double and 7 digits otherwise? The other alternative I am considering is > > to set tcl_precision to 17 in each of the examples, but I prefer not to do > > that if there is an automatic PLFLT-style solution you can use for > > libmatrix. > > I really think tying it to tcl_precision is the right thing to do. > It doesn't have any effect on internal representation, just the number > of digits emitted when converting the PLFLT to a string. That would be okay with me, but as you can see from the above example it is affecting the (effective) internal precision, and not just the digits being emitted. Hope you can get this matrix problem sorted out. Alan |
From: Alan W. Irwin <irwin@be...> - 2002-01-16 00:43:32
|
On Tue, 15 Jan 2002, Geoffrey Furnish wrote: > [...] However, your > proposal doesn't seem right to me either, since it seems kludgy to have > to have two additions to classpath to use the java stuff. Maybe you > could take the position that you only need the first one for normal > client codes, and the second one is just to reach the PLplot Java > demos, yes. Also, I was quite happy to see that your java package structure still worked fine if you assembled the bits and pieces from separate directory trees with the appropriate colon-separated list of directories in CLASSPATH. Of course, just because something is possible doesn't mean you have to do it so see below. > but to me it makes more sense to have one classpath component > which reaches all things plplot/java. OK. I will go along with this decision. > Personally, I'd just leave it alone for now, figuring that it wil > lhave to change later once we learn the ways of upscale Java packagers > well enough to follow suit fashionably. OK, to be revisited later when one of us knows more about jar files, etc. You didn't answer my question about the sources. Currently there are no java sources anywhere in the install directory tree. I believe at least the java example sources should be there (by analogy with the source code that is installed for the other examples). Assuming you agree on the examples, do you also want the core sources installed? Alan |