Changeset 123 for pypar/README
- Timestamp:
- Jul 11, 2005, 3:20:03 PM (20 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
pypar/README
r85 r123 179 179 180 180 HISTORY 181 version 1.9.1 (15 Dec 2003) 182 Consistent naming (all lower case, no abbreviations) 183 version 1.9 (3 Dec 2003) 184 Obsoleted raw forms of communication as they were confusing. 185 The semantics of send, receive, scatter, gather etc is now that 186 one can optionally specify a buffer to use if desired. 187 Bypass forms added. 188 181 189 version 1.8.2 (16 November 2003) 182 190 Fixed scatter, gather and reduce calls to automatically … … 235 243 236 244 TODO 237 Modify scatter, gather and reduce to automatically determine length238 in order to comply with the other functions: send, receive and bcast239 which do.240 241 Get rid of 'raw' forms as they are confusing.242 Incorporate a keyword argument, buffer = x, instead.243 This gives the flexibility to specify an existing receive244 buffer. The corresponding send command will need a flag, buffer=1,245 or something like that.246 247 245 max_tag is set to 32767. This works for Linux/LAM 248 246 I couldn't use MPI_TAG_UB as it returned 0. … … 250 248 251 249 250 Scatter needs to send buffer specified on all processes 251 even though it is ignored by all non-root processes. 252 How could we overcome that? 253 Similar problem for gather 254 255 Gather an scatter: One should be able to specify along which axis 256 arrays should be concatenated. 257 258 252 259 KNOWN BUGS 253 In raw_receive one must assign explicitly to buffer variable 254 if it uses (or reverts to) vanilla mode: 255 B = raw_receive(B, ....) 256 257 The collective communication have not yet been tested for multidimensional arrays 258 and the complex datatype 259 260 Scatter for the moment works only properly when the amount of data is a 261 multiple of the number of processors (as does the underlying MPI_Scatter). 262 I am working on a more general scatter (and gather) which will 263 distribute data as evenly as possible for all amounts of data. 264 260 265 261 266 LICENSE … … 323 328 324 329 330 331 332
Note: See TracChangeset
for help on using the changeset viewer.