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.
2003 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(3) |
Dec
(8) |
2005 |
Jan
(9) |
Feb
(4) |
Mar
(3) |
Apr
(1) |
May
|
Jun
(2) |
Jul
(16) |
Aug
(11) |
Sep
(10) |
Oct
|
Nov
|
Dec
|
2006 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(7) |
Aug
(2) |
Sep
|
Oct
|
Nov
(7) |
Dec
(4) |
2007 |
Jan
|
Feb
|
Mar
(1) |
Apr
(4) |
May
(4) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
2009 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
|
|
|
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
(1) |
13
|
14
|
15
|
16
|
17
|
18
|
19
|
20
|
21
(3) |
22
(4) |
23
|
24
|
25
(1) |
26
|
27
(1) |
28
(5) |
29
(1) |
30
|
31
|
|
|
|
|
|
|
From: <thamelry@bi...> - 2005-07-28 21:23:33
|
> All but one of the PyObject_Print statements are gone (I just > deleted the one I missed which is a debug print only when raising > an exception if you illegally slice a communicator). Great - thanks. > I haven't verified the leak status though I did plug some holes > in the 2.4b1 release. Is there a mocapy run that illustrates the > problem? I could use it in the release test suite then. I've got a small test script that illustrates the problem - I'll send it tomorrow. Best regards, -Thomas |
From: Pat Miller <patmiller@ll...> - 2005-07-28 21:01:59
|
> pyMPI_comm.c, pyMPI_comm_collective.c and pyMPI_comm_misc.c > contain PyObject_Print statements that print out a lot of what All but one of the PyObject_Print statements are gone (I just deleted the one I missed which is a debug print only when raising an exception if you illegally slice a communicator). I haven't verified the leak status though I did plug some holes in the 2.4b1 release. Is there a mocapy run that illustrates the problem? I could use it in the release test suite then. Pat -- Pat Miller | (925) 423-0309 | http://www.llnl.gov/CASC/people/pmiller Be the change you want to see in the world. -- Mahatma Gandhi (1869-1948) |
From: <thamelry@bi...> - 2005-07-28 16:15:29
|
> Thomas > > Can you explain what the problem of the extra stdout output is? Pat > probably > knows, but I'm not sure what this means. Hi Julian, pyMPI_comm.c, pyMPI_comm_collective.c and pyMPI_comm_misc.c contain PyObject_Print statements that print out a lot of what seems to be debugging info. This generates a huge amount of irrelevant output that clogs log files. I'm very near Mocapy 1.0 - a toolkit that does parallelized learning and inference in Dynamic Bayesian Networks (https://sourceforge.net/projects/mocapy/). It depends on pyMPI so I'd like to see these things fixed before I claim Mocapy is ready-to-use. The memory leak problem is particularly problematic, of course, since Mocapy typically runs for several days. Cheers, -Thomas |
From: Julian Cook <rjcookusa@cs...> - 2005-07-28 15:56:05
|
Thomas Can you explain what the problem of the extra stdout output is? Pat probably knows, but I'm not sure what this means. Tks Julian Cook FNX Ltd -----Original Message----- From: pympi-users-admin@... [mailto:pympi-users-admin@...]On Behalf Of Thomas Hamelryck Sent: Thursday, July 28, 2005 3:05 AM To: Pat Miller; pympi-users@... Subject: Re: [Pympi-users] pyMPI 2.4 beta 2 available.... Hi Pat, On Wednesday 27 July 2005 23:57, Pat Miller wrote: > Thanks to Julian, I uncovered a bad bug in pack/unpack in which > short strings were sometimes truncated with an EOF error. You > should strongly consider downloading 2.4b2 to replace any 2.4b1 > version you have. I was wondering if the memory leak problem associated with buffer2 (I submitted a patch for this) and the problem of the extra stdout output are fixed as well? Best regards & thanks for a great tool, -- Thomas Hamelryck, Postdoctoral researcher Bioinformatics center Institute of Molecular Biology and Physiology University of Copenhagen Universitetsparken 15 Bygning 10 2100 Copenhagen, Denmark --- http://www.binf.ku.dk/users/thamelry/ ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Pympi-users mailing list Pympi-users@... https://lists.sourceforge.net/lists/listinfo/pympi-users |
From: Thomas Hamelryck <thamelry@bi...> - 2005-07-28 07:20:48
|
Hi Pat, On Wednesday 27 July 2005 23:57, Pat Miller wrote: > Thanks to Julian, I uncovered a bad bug in pack/unpack in which > short strings were sometimes truncated with an EOF error. You > should strongly consider downloading 2.4b2 to replace any 2.4b1 > version you have. I was wondering if the memory leak problem associated with buffer2 (I submitted a patch for this) and the problem of the extra stdout output are fixed as well? Best regards & thanks for a great tool, -- Thomas Hamelryck, Postdoctoral researcher Bioinformatics center Institute of Molecular Biology and Physiology University of Copenhagen Universitetsparken 15 Bygning 10 2100 Copenhagen, Denmark --- http://www.binf.ku.dk/users/thamelry/ |