April 2008 - Mpi-21 - mailman3.cels.anl.gov

All REVIEWERS - Final 1.3 and 2.1 review
by unknown＠example.com 19 Apr '08

19 Apr '08

Dear reviewer, this is the *final* review. http://www.hlrs.de/mpi/mpi21/doc/ is updated with - final version = official reading of MPI-1.3 (hopefully) - official reading version of MPI-2.1 One exception: - The authors and reviewers of Chap. Point-to-Point and Chap. Datatypes may work strongly together to have at the end of the week a version that will have a review at the meeting withou showing further needs. Please, mark errors in your reviews clearly with ERR. Please mark all other stuff with 22 because it will go into MPI-2.2. The resources for MPI-2.1 are now nearly fully consumed. The shortest summary of open issues can be found at http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review-openissues.… Review format - please use: ---------------------------------------------------------------------------------- 1234567890123456789012345678901234567890123456789012345678901234567890123456789012 All references are based on MPI-2.1 Draft Apr. 19, 2008 ww.a __ pnnn.ll text (with nnn=page number and ll=line number text continued ... ww.b __ pnnn.ll text ... and so on (total line length <= 82 characters.) ---------------------------------------------------------------------------------- PLEASE: - Please check very carefully all red or magenta changes. Modifications are done by the chapter's author (red) or by me (magenta). You may be the first reviewer who read and check this text. - Please check carefully the cyan text. Those modifications are proposed by a reviewer and have been implemented by my You may be the second reviewer for those modifications. - All green stuff should be fine, because it is based on Forum's decisions (Ballot 1-4). - Original text is black (MPI-1.3) or blue (MPI-2.0). Thanks and best regards Rolf Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30)

1 0

Re: [Mpi-21] AUTHORS+REVIEWERS - Draft Apr. 12, 2008
by unknown＠example.com 19 Apr '08

19 Apr '08

Hi Adam, Rolf, > I've marked most of your edits with DON2, which means I've made the > change as you recommended. However, there are a number for which I'm > not clear on what you meant. These are marked with "vv", which points > to the question following. Would you please clarify these items? As a > reference, let's use the following document for page and line numbers: > > http://www.hlrs.de/organization/par/services/models/mpi/mpi21/doc/mpi-repor… > -Adam Thanks Adam! I commented on your comments below. Ah, btw. the page numbers are *not* correct in xpdf (pdf page numbers vs. printed page numbers). Rolf, please add the things we decided to run by the Forum to some ballot for the meeting next week - they should be easy to solve. Thanks! > >general: the line numbers are completely out of sync ... it's hard to > >classify a line that is between two line numbers. This is still ambiguous, but it seems to be a general problem. Why is the font used to number the lines smaller than the text in the lines? > >5.a DON2 EDIT p129.19-41 "all group members" vs. "all members of a group" > > should use the same phrasing (parallel structure) > > > > > >5.b DON2 NICE p129.41 Reference to 5.11 not 5.11.1 > >5.c DON2 EDIT p129.45 remove "," (comma) > >5.d DON2 EDIT p129.43 replace "the same" with "a" > >5.e DON2 EDIT p129.45 "the same group" in line 43 conflicts with "group or > > groups" > > > > > There is not really a clear way to state this. As Rejeev also > suggested, the definition of "matching" is not well understood here. > Perhaps the best option is to remove this statement altogether, since it > is defined in more detail in the "Specifics" sections for intra- and > inter-communicators. I'll remove the statement, but the idea of > "matching" parameters in collective calls should be discussed in the > Forum. Thus, the following lines: > "A collective operation is executed by having all processes in the > same group call the > communication routine, with matching arguments. One of the key > arguments is a communicator ..." > are now written more simply as: > "One of the key arguments in a call to a collective routine is a > communicator ..." ok > >5.f vv CLAR p131.1 add "with exceptions stated in the following" to first > > sentence > > > > > Do you mean exceptions to the matching of datatypes in sender and > receiver? Are there exceptions to this? The expection is for arguments that are only significant at certain processes. I.e., not all arguments must match (because they are ignored). But I guess it's ok and clear as it is - we don't need a change here. > >5.g DON2 EDIT p131.4 no linebreak (Chapter~\ref{...}) > >5.h *NO* ERR p131.31 replace "will" with "might" > > > > > I'd leave this in, since it was the original wording for this version of > the standard. I think there is still an escape here already in the "(or > a similar mechanism)" phrase. I would like to run this by the Forum. Yes, it is the original wording, but some parts of the original wording are not accurate, so we should discuss this. Non-blocking collectives without tags are possible and useful, so why should we say wrong things in the revised version of the standard? And we also do not need "similar mechanisms". I'd say this sentence is misleading. > >5.i vv ERR p132. "special communicator must be created" this is wrong, > > later (in the bcast section) it is stated differently > > ... I would just remove this part of the advice or say > > "might be created" (see Bcast advice) > > > > > Could you specify the particular advice via page and line numbers? It's > not clear to me what you are referring to here. ups, I forgot the line numbers here - sorry! It's line 1-2. It says that implementors need to implement a "special communicator". Nobody does this, most implementations just use special tags. So this advice is also misleading (actually wrong). > >5.j vv CLAR p131.37 add "depending on the operation performed after last > > sentence (right now it sounds like ths user is free to > > choose which argument to replace) > > > > > Do you mean p132.27 instead? The recommendation doesn't seem to line up > with the document I have. yes, this is line 27, got confused with the line numbers here. > >5.k *NO* EDIT p133.32 "a" -> "an"? > > > > > I think "a" is actually appropriate here. hmm, I learned that "an" has to come before words starting with a,e,o,u ... but "a" sounds (flows) much more natural. Don't change it (that's why I added the "?" to my original comment :). > >5.l DON2 EDIT p136.22 start sentence with "If the communicator is an > > intracommunicator" as for all the other operations, > > remove "for intracommunicators" in line 23 > >5.m DON2 EDIT p136.24 replace "," by "and" > >5.n ?? EDIT p136.26-31 this paragraph is redundant (it's all already stated > > earlier, do we want this redundancy in the standard?) > > > > > I agree that it is redundant, but this emphasis in a particular case may > be useful to get the point across. I'd leave it up to the Forum to vote > on this. ok, good idea. > >5.o *NO* EDIT p136.32 move sentence to end of the previous paragraph (line > > 25) > > > > > Although, this text may read more smoothly with this edit, it breaks > symmetry on where the "in place" statements are placed in other > descriptions. ok, I agree. > >5.p *NO* EDIT p136.37 "data is braodcasted" (not braodcast) > > > > > Left as "broadcast" per discussion between Bronis and Torsten which > concluded that "broadcast" is recommended. yes! > >5.q DON2 CLAR p136.38-39 the text talks about send and receive buffer argument, > > but bcast only has a single buffer argument ... > > > > > >5.r ?? CLAR p136.38 "must be consistent with the ..." what does the word > > consistent mean in this context? This seems undefined. > > I think it means that the signature (size, count) is > > the same. We should say this explicitely. The same > > term "consistent" is used in all following operations > > (I'm not going to add it again) > > > > > I agree that "consistent" is not defined, however, I'm not sure what it > means either. I think this change should be left to the Forum. Yes, I'd just say that this needs to be defined. I can only guess what it means. > >5.s DON2 EDIT p138.3 write "all processes" instead of "process i" (i is > > never defined) > > > > > I changed this to: > "The type signature of sendcount, sendtype on each process must be > equal ..." perfect! > >5.t *NO* ERR p139.47 data is not necessarily placed in rank order. The > > order is freely definably by the user in the displs[] > > array. Or does the standard enforce the displs[] array > > to preserve order? We might want to run this through > > the forum (or just ignore it?)? > > > > > I think the "that is, ..." portion of this statement clarifies the meaning. I don't think so. I also discussed this with Jesper who also thinks that this is a controversary statement. Actually, I'd say that the standard forces the displs[] array to be in rank-order. Everything else can be interpreted as an erroneous MPI program. I think we don't want this. But we should run this by the Forum. > >5.u DON2 CLAR p136.42 add "The examples in this section are using > > intracommunicators." as in p140.27 > >5.v ?? EDIT p147.48 the last paragraph is redundant (has been stated > > before for all collectives) > > > > > Again, I'll leave this redundancy question to the Forum. ok > >5.w DON2 EDIT p157.35 why a separate subsection for Alltoallw but not for > > Alltoallv? I'd remove this subsection > >5.x DON2 EDIT p157.36 the first two sentences should go to rationale (we > > don't need to rationalize the operation in the > > description) > > > > > I missed this piece in the original rewrite, and so this section still > required significant editting. I've made it look and feel more like the > AlltoallV definition. great! > >5.y DON2 EDIT p161.13 replace "Reduce" by "Reduction" or "Operations for > > MPI_Reduce" > >5.z vv EDIT p162.13 state that the example is in Fortran (it's said for > > all the C examples before) > > > > > I don't see examples in this chapter that say they are in C either, or > at least, there are many that don't. ok, there are some that do and some that don't. Ah, I don't care ... people who are not able to recognize the language are not our target audience anyway (I hope). > >5.aa DON2 EDIT p163.10-12 I think we don't need to backref to MPI-1 here if we > > consider MPI-2.1 a complete standard. > > > > > Ok, I've been convinced to remove this. :) > >5.ab DON2 CLAR p163.20 replace "bit" by "numeric" or "integer" > >5.ac *NO* EDIT p167.41 doubled sentence "The order of ..." > > > > > The sentence is not technically duplicated. I'll leave this text as is > now, although, I agree that this paragraph could be rewritten to state > its point more clearly. "The order of evaluation can be changed, talking advantage of the associativity of the operation. If commute = true then the order of evaluation can be changed" ... ok, I see. It sounds like double. I'd still re-phrase this into a single sentence, such as: "If commute = true, then the order of evaluation can be changed, talking advantage of the associativity of the operation." > >5.ad DON2 CLAR p169.2 add: (without supporting the "in place" option) > >5.ae DON2 ERR p169.16-20 the example will deadlock if root == groupsize-1. Has > > been there for a while :). Use Irecv/Wait instead. > >5.af vv EDIT p171.48 state that example is in Fortran > > > > > Again, not sure if this needs to be done? agree - please ignore this > >5.ag DON2 ERR p174.12-20 this rationale should be erased completely because it > > explains (for MPI-1), why only the inclusive is supported ;-) > >5.ah DON2 ERR p175.20 erase the last sentence in rationale, we don't need > > this anymore (is MPI-1) > >5.ai ?? EDIT p177.48 move orphaned Example header to next page (might > > change after edits though -> check chapter for orphans) > >5.aj ?? EDIT p179.24 the font suddenly changes? (sans-serif) > > > > > Haven't checked these two in the recent document. I suppose some of the > checks will need to wait until the final copy is available for reading. yes, I just wanted to remind us to do it at the end. > >5.ak ?? CLAR p179.27 maybe we should add: "and to ensure appropriate > > matching (for deterministic behavior) > > > > > I'll leave this one to the Forum. ok Thanks & Best, Torsten -- bash$ :(){ :|:&};: --------------------- http://www.unixer.de/ ----- Indiana University | http://www.indiana.edu Open Systems Lab | http://osl.iu.edu/ 150 S. Woodlawn Ave. | Bloomington, IN, 474045-7104 | USA Lindley Hall Room 135 | +01 (812) 855-3608

1 0

AUTHORS - write token is back at me (except pt2pt + datatypes)
by unknown＠example.com 19 Apr '08

19 Apr '08

All authors (except Rich [pt2pt and datatypes]), the write toke is now back at me. Please do *not* further modify the source. I'll finish the MPI-1.3 and MPI 2.1 and I'll put the final version for review on the web in the next hours. Exception: Rich and Co. will work on pt2pt.tex and datatypes.tex the next week together with the reviewers to finish these two chapters also until the meeting. Best regards (next mail with pdf-on-web will come in a few hours) Rolf Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30)

1 0

Re: [Mpi-21] AUTHORS+REVIEWERS - Draft Apr. 12, 2008
by unknown＠example.com 18 Apr '08

18 Apr '08

Hi Torsten, I've marked most of your edits with DON2, which means I've made the change as you recommended. However, there are a number for which I'm not clear on what you meant. These are marked with "vv", which points to the question following. Would you please clarify these items? As a reference, let's use the following document for page and line numbers: http://www.hlrs.de/organization/par/services/models/mpi/mpi21/doc/mpi-repor… -Adam Torsten Hoefler wrote: >Hi Rolf, Adam, >I understand from your mail Rolf, that Adam lost his write token and >that only you can apply the changes/comments to the chapter (in my case >the collectives chapter). Thus, I'll send my review results to the list >instead the chapter author directly. My general comment: very well done >Adam :). > >I have some smaller editing remarks and also found some small errors and >clarification possibilities (see below). > > > >>---------------------------------------------------------------------------------- >>1234567890123456789012345678901234567890123456789012345678901234567890123456789012 >> All references are based on MPI-2.1 Draft Apr. 12, 2008 >>ww.a __ pnnn.ll text (with nnn=page number and ll=line number >> text continued >> ... >>ww.b __ pnnn.ll text ... and so on (total line length <= 82 characters.) >>---------------------------------------------------------------------------------- >> >> >Ok, here my remarks, many of them (especially EDIT or CLAR) can probably >be ignored, but I thought I'd bring it up: > >general: the line numbers are completely out of sync ... it's hard to >classify a line that is between two line numbers. > >5.a DON2 EDIT p129.19-41 "all group members" vs. "all members of a group" > should use the same phrasing (parallel structure) > > >5.b DON2 NICE p129.41 Reference to 5.11 not 5.11.1 >5.c DON2 EDIT p129.45 remove "," (comma) >5.d DON2 EDIT p129.43 replace "the same" with "a" >5.e DON2 EDIT p129.45 "the same group" in line 43 conflicts with "group or > groups" > > There is not really a clear way to state this. As Rejeev also suggested, the definition of "matching" is not well understood here. Perhaps the best option is to remove this statement altogether, since it is defined in more detail in the "Specifics" sections for intra- and inter-communicators. I'll remove the statement, but the idea of "matching" parameters in collective calls should be discussed in the Forum. Thus, the following lines: "A collective operation is executed by having all processes in the same group call the communication routine, with matching arguments. One of the key arguments is a communicator ..." are now written more simply as: "One of the key arguments in a call to a collective routine is a communicator ..." >5.f vv CLAR p131.1 add "with exceptions stated in the following" to first > sentence > > Do you mean exceptions to the matching of datatypes in sender and receiver? Are there exceptions to this? >5.g DON2 EDIT p131.4 no linebreak (Chapter~\ref{...}) >5.h *NO* ERR p131.31 replace "will" with "might" > > I'd leave this in, since it was the original wording for this version of the standard. I think there is still an escape here already in the "(or a similar mechanism)" phrase. >5.i vv ERR p132. "special communicator must be created" this is wrong, > later (in the bcast section) it is stated differently > ... I would just remove this part of the advice or say > "might be created" (see Bcast advice) > > Could you specify the particular advice via page and line numbers? It's not clear to me what you are referring to here. >5.j vv CLAR p131.37 add "depending on the operation performed after last > sentence (right now it sounds like ths user is free to > choose which argument to replace) > > Do you mean p132.27 instead? The recommendation doesn't seem to line up with the document I have. >5.k *NO* EDIT p133.32 "a" -> "an"? > > I think "a" is actually appropriate here. >5.l DON2 EDIT p136.22 start sentence with "If the communicator is an > intracommunicator" as for all the other operations, > remove "for intracommunicators" in line 23 >5.m DON2 EDIT p136.24 replace "," by "and" >5.n ?? EDIT p136.26-31 this paragraph is redundant (it's all already stated > earlier, do we want this redundancy in the standard?) > > I agree that it is redundant, but this emphasis in a particular case may be useful to get the point across. I'd leave it up to the Forum to vote on this. >5.o *NO* EDIT p136.32 move sentence to end of the previous paragraph (line > 25) > > Although, this text may read more smoothly with this edit, it breaks symmetry on where the "in place" statements are placed in other descriptions. >5.p *NO* EDIT p136.37 "data is braodcasted" (not braodcast) > > Left as "broadcast" per discussion between Bronis and Torsten which concluded that "broadcast" is recommended. >5.q DON2 CLAR p136.38-39 the text talks about send and receive buffer argument, > but bcast only has a single buffer argument ... > > >5.r ?? CLAR p136.38 "must be consistent with the ..." what does the word > consistent mean in this context? This seems undefined. > I think it means that the signature (size, count) is > the same. We should say this explicitely. The same > term "consistent" is used in all following operations > (I'm not going to add it again) > > I agree that "consistent" is not defined, however, I'm not sure what it means either. I think this change should be left to the Forum. >5.s DON2 EDIT p138.3 write "all processes" instead of "process i" (i is > never defined) > > I changed this to: "The type signature of sendcount, sendtype on each process must be equal ..." >5.t *NO* ERR p139.47 data is not necessarily placed in rank order. The > order is freely definably by the user in the displs[] > array. Or does the standard enforce the displs[] array > to preserve order? We might want to run this through > the forum (or just ignore it?)? > > I think the "that is, ..." portion of this statement clarifies the meaning. >5.u DON2 CLAR p136.42 add "The examples in this section are using > intracommunicators." as in p140.27 >5.v ?? EDIT p147.48 the last paragraph is redundant (has been stated > before for all collectives) > > Again, I'll leave this redundancy question to the Forum. >5.w DON2 EDIT p157.35 why a separate subsection for Alltoallw but not for > Alltoallv? I'd remove this subsection >5.x DON2 EDIT p157.36 the first two sentences should go to rationale (we > don't need to rationalize the operation in the > description) > > I missed this piece in the original rewrite, and so this section still required significant editting. I've made it look and feel more like the AlltoallV definition. >5.y DON2 EDIT p161.13 replace "Reduce" by "Reduction" or "Operations for > MPI_Reduce" >5.z vv EDIT p162.13 state that the example is in Fortran (it's said for > all the C examples before) > > I don't see examples in this chapter that say they are in C either, or at least, there are many that don't. >5.aa DON2 EDIT p163.10-12 I think we don't need to backref to MPI-1 here if we > consider MPI-2.1 a complete standard. > > Ok, I've been convinced to remove this. >5.ab DON2 CLAR p163.20 replace "bit" by "numeric" or "integer" >5.ac *NO* EDIT p167.41 doubled sentence "The order of ..." > > The sentence is not technically duplicated. I'll leave this text as is now, although, I agree that this paragraph could be rewritten to state its point more clearly. >5.ad DON2 CLAR p169.2 add: (without supporting the "in place" option) >5.ae DON2 ERR p169.16-20 the example will deadlock if root == groupsize-1. Has > been there for a while :). Use Irecv/Wait instead. >5.af vv EDIT p171.48 state that example is in Fortran > > Again, not sure if this needs to be done? >5.ag DON2 ERR p174.12-20 this rationale should be erased completely because it > explains (for MPI-1), why only the inclusive is supported ;-) >5.ah DON2 ERR p175.20 erase the last sentence in rationale, we don't need > this anymore (is MPI-1) >5.ai ?? EDIT p177.48 move orphaned Example header to next page (might > change after edits though -> check chapter for orphans) >5.aj ?? EDIT p179.24 the font suddenly changes? (sans-serif) > > Haven't checked these two in the recent document. I suppose some of the checks will need to wait until the final copy is available for reading. >5.ak ?? CLAR p179.27 maybe we should add: "and to ensure appropriate > matching (for deterministic behavior) > > I'll leave this one to the Forum. >Best, > Torsten > > > *

1 0

2nd reply - Re: AUTHORS+REVIEWERS - reminder - Draft Apr. 12, 2008
by unknown＠example.com 18 Apr '08

18 Apr '08

Please send me a revised mail from Torstens mail where you mark all done items with DON2 and all other with the defined mark-ups as shown on http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt Thanks Rolf On Thu, 17 Apr 2008 18:01:18 -0700 Adam Moody <moody20_at_[hidden]> wrote: > Hi Rolf, > I'll need Friday the 18th to incorporate Torsten's comments into the > Collectives chapter. I missed them when he first sent them. > -Adam > > Rolf Rabenseifner wrote: > > >All authors (except Rich [pt2pt and datatypes]), > > > >- The authors get back the write-token until Thursday, Apr. 17. > > (If you need also Friday Apr. 18, then please inform me!!) > >- All stuff that is not done until that point, will be defered to MPI-2.2! > > > >This is the last reminder and chance for latest updates **today**. > > > >(Details on the WORKPLAN, see mail below) > > > >Best regards > >Rolf > > > > > >On Sun, 13 Apr 2008 00:05:37 +0200 > > "Rolf Rabenseifner" <rabenseifner_at_[hidden]> wrote: > > > > > >>Dear chapter author, dear reviewer, > >> > >>This e-mail is the first preparation of the official reading. > >>Please read carefully. > >> > >>Again,we have a stable and consistent draft. > >>It is SVN revision 108 and pdf and ps are on > >> http://www.hlrs.de/mpi/mpi21/doc/ > >>(username and password are mpi21) > >> > >>Nearly all chapters have received an update by the chapters' authors. > >>Not finished is - as far as I can see > >> - Point-to-point (may-be without MPI-1/2 problems] (Rich Graham) > >> - Datatypes [it was split from Point-to-point] (Rich Graham) > >>and full MPI-2 based chapters (maybe without need for updates) > >> - Terms (Tony Skjellum) > >> - External Interfaces (Bronis de Supinski) > >> - Profiling (Bronis de Supinski) > >>Therefore, review can start in all chapters, except the datatype chapter. > >> > >>IMPORTANT for authors: > >>If you make further modifications, please be sure that you use > >>the macros and that your modification (or at least an delete-anchor) > >>is printed **red**. (Details on using the macros, see below.) > >>Please check red color in the resulting mpi-report.pdf before you > >>svn commit your changes. > >>As far as I can see, all changes up to now may have no problem > >>for acceptance by the Forum. > >>At this late stage, I would recommend to do only changes that do > >>not need intensive debates at the Forum meeting. Such things > >>would be MPI-2.2 modifications. > >> > >>IMPORTANT for reviewers: > >>- Please check very carefully all red or magenta changes. > >> Modifications are done by the chapter's author (red) or > >> by me (magenta). > >> You may be the first reviewer who read and check this text. > >>- Please check carefully the cyan text. > >> Those modifications are proposed by a reviewer and have been > >> implemented by my > >> You may be the second reviewer for those modifications. > >>- All green stuff should be fine, because it is based on > >> Forum's decisions (Ballot 1-4). > >>- Original text is black (MPI-1.3) or blue (MPI-2.0). > >>- Please make all comments in the format > >> > >>---------------------------------------------------------------------------------- > >>1234567890123456789012345678901234567890123456789012345678901234567890123456789012 > >> All references are based on MPI-2.1 Draft Apr. 12, 2008 > >>ww.a __ pnnn.ll text (with nnn=page number and ll=line number > >> text continued > >> ... > >>ww.b __ pnnn.ll text ... and so on (total line length <= 82 characters.) > >>---------------------------------------------------------------------------------- > >> > >>- Please send only review items that are in the category > >> -- ERROR, must be fixed. > >>- If you want to send an item in the categories > >> -- Nice to have, > >> -- Editorial proposal (like move xxx to yyy), > >> -- Clarification which needs Forum decisions, > >> -- ... > >> then please substitute the __ by 22, because then it should be > >> handled in MPI-2.2. > >> > >>This format is used in > >>http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt > >>where all reviews are filed in. > >>(I'll substitute your xx by the next number. If you have more than > >>26 items, then please continue with xx.a -- xx.z, yy.a - ...) > >> > >>Please use this format. I'll have only a few minutes between two flights > >>to put all reviews together. > >> > >>WORKPLAN: > >>- The authors get back the write-token until Thursday, Apr. 17. > >> (If you need also Friday Apr. 18, then please inform me!!) > >>- All stuff that is not done until that point, will be defered to MPI-2.2! > >>- I'm on travel and may not be able to respond on e-mails this week. > >>- On Friday, Apr. 18 (or Saturday, Apr. 19), I will make the > >> final version for all final reviews and for the official reading. > >>- Version Apr. 17 together with all your review mails will be the > >> basis for the official reading. > >>- Reviews until Friday, Apr. 25. according the format above. > >>- Saturday, Apr. 26: > >> I will put all reviews together to have unique numbers. > >> > >>Best regards > >>Rolf > >> > >> > >>Annex: The rules for authors: > >> > >>The goals of your work as chapter author: > >>----------------------------------------- > >> > >>- Remove references to MPI-1 and MPI-2. > >>- Substitute by MPI. > >>- Necessary modifications to achieve this goal. > >> > >>With this, we should have a single MPI-2.1 standard that does > >>not "know" the MPI-1 or MPI-2 history of individual functions. > >> > >>** This should be mainly a task in the area of chapter-introductions. > >>** Please, never change the wording of function definitions. > >> > >>Exceptions: > >>- There are routines that are deprecated and that are > >> already referenced in a consistent way. > >> My recommendation: > >> Current wording: > >> There are *new* function, and existing are now deprecated. > >> Proposal: > >> There are functions, and there exist also deprecated functions > >> with (nearly) same functionality but deprecated due to some lack > >> in the bindings (or functionality) > >>- There is history information in the frontmatter. > >>- there is a change-log annex with limited memory (only previous version) > >> > >>Technical editing rule: > >>----------------------- > >> > >>You must identify all of your changes: > >> > >>a) new/modified wording - you are highlighting your new/modified wording with: > >> > >>\mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification > >>.... your modified / new wording .... > >>\mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification > >> > >>b) Moved paragraphs, sentences, ... - you are highlighting the first word > >> of the moved text with: > >> > >>\mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move > >>First-word > >>\mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move > >>... rest of the moved text.... > >>% MPI-2.1 round-two - end of text-move > >> > >>c) If you want to delete text (i.e. not only a move to another location), > >> the please us > >> > >>\mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - deleted-text-anchor > >>Last word of the previous text > >>\mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of anchor > >> > >>% MPI-2.1 round-two - begin of deteted text - Draft Apr.1, 2008 page/line-page/line > >>% the text you delete must be preceded with "% " > >>% deprecated text > >>% ... > >>% deprecated text > >>% MPI-2.1 round-two - end of deteted text > >> > >> Additionally, you must add this outcommented text to the end of > >> removed_source.tex > >> > >>Caution: These macros work only in black parts of the text. > >> > >>In blue parts you must substitute > >> \mpiiidotiMergeNEWforSINGLEendI% > >>by > >> \mpiiidotiMergeNEWforSINGLEendII% > >> > >> > >>The highlighting is done with red color. > >>(There are only a few other sentences from me magenta. > >> Therefore red should be the best to highlight the round-two modifications.) > >> > >>----------------------------------------------------- > >>Using svn: > >>Before you start to make changes: > >> > >> cd ....your_directory..../trunk/MPI-2.1/ > >> svn update > >> > >>to get the newest sources. > >> > >>After you made changes, please call make and check mpi-report.pdf > >>to guarantee that all your changes are really highlighted with *red* color. > >> > >>When you make the first svn commit after you received a new username with > >>write-permission, you must use the aditional option > >> > >> --username your_new_user_name > >> > >>Please commit with > >> > >>svn commit chap-xxxx/xxxx.tex -m 'MPI-2.1 - your name - what you have done' > >> > >>Please commit as soon as you finished the changes and after you have > >>checked the red color. > >> > >>-------------------------------------------------- > >> > >>Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] > >>High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 > >>University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 > >>Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner > >>Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) > >> > >> > > > > > > > >Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] > >High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 > >University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 > >Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner > >Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) > >_______________________________________________ > >mpi-21 mailing list > >mpi-21_at_[hidden] > >http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 > > > > > > > _______________________________________________ > mpi-21 mailing list > mpi-21_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30)

1 0

Re: [Mpi-21] AUTHORS+REVIEWERS - reminder - Draft Apr. 12, 2008
by unknown＠example.com 18 Apr '08

18 Apr '08

Hi Adam, okay. Please send me a short reply when you have finished coll.tex. Thanks and best regards Rolf On Thu, 17 Apr 2008 18:01:18 -0700 Adam Moody <moody20_at_[hidden]> wrote: > Hi Rolf, > I'll need Friday the 18th to incorporate Torsten's comments into the > Collectives chapter. I missed them when he first sent them. > -Adam > > Rolf Rabenseifner wrote: > > >All authors (except Rich [pt2pt and datatypes]), > > > >- The authors get back the write-token until Thursday, Apr. 17. > > (If you need also Friday Apr. 18, then please inform me!!) > >- All stuff that is not done until that point, will be defered to MPI-2.2! > > > >This is the last reminder and chance for latest updates **today**. > > > >(Details on the WORKPLAN, see mail below) > > > >Best regards > >Rolf > > > > > >On Sun, 13 Apr 2008 00:05:37 +0200 > > "Rolf Rabenseifner" <rabenseifner_at_[hidden]> wrote: > > > > > >>Dear chapter author, dear reviewer, > >> > >>This e-mail is the first preparation of the official reading. > >>Please read carefully. > >> > >>Again,we have a stable and consistent draft. > >>It is SVN revision 108 and pdf and ps are on > >> http://www.hlrs.de/mpi/mpi21/doc/ > >>(username and password are mpi21) > >> > >>Nearly all chapters have received an update by the chapters' authors. > >>Not finished is - as far as I can see > >> - Point-to-point (may-be without MPI-1/2 problems] (Rich Graham) > >> - Datatypes [it was split from Point-to-point] (Rich Graham) > >>and full MPI-2 based chapters (maybe without need for updates) > >> - Terms (Tony Skjellum) > >> - External Interfaces (Bronis de Supinski) > >> - Profiling (Bronis de Supinski) > >>Therefore, review can start in all chapters, except the datatype chapter. > >> > >>IMPORTANT for authors: > >>If you make further modifications, please be sure that you use > >>the macros and that your modification (or at least an delete-anchor) > >>is printed **red**. (Details on using the macros, see below.) > >>Please check red color in the resulting mpi-report.pdf before you > >>svn commit your changes. > >>As far as I can see, all changes up to now may have no problem > >>for acceptance by the Forum. > >>At this late stage, I would recommend to do only changes that do > >>not need intensive debates at the Forum meeting. Such things > >>would be MPI-2.2 modifications. > >> > >>IMPORTANT for reviewers: > >>- Please check very carefully all red or magenta changes. > >> Modifications are done by the chapter's author (red) or > >> by me (magenta). > >> You may be the first reviewer who read and check this text. > >>- Please check carefully the cyan text. > >> Those modifications are proposed by a reviewer and have been > >> implemented by my > >> You may be the second reviewer for those modifications. > >>- All green stuff should be fine, because it is based on > >> Forum's decisions (Ballot 1-4). > >>- Original text is black (MPI-1.3) or blue (MPI-2.0). > >>- Please make all comments in the format > >> > >>---------------------------------------------------------------------------------- > >>1234567890123456789012345678901234567890123456789012345678901234567890123456789012 > >> All references are based on MPI-2.1 Draft Apr. 12, 2008 > >>ww.a __ pnnn.ll text (with nnn=page number and ll=line number > >> text continued > >> ... > >>ww.b __ pnnn.ll text ... and so on (total line length <= 82 characters.) > >>---------------------------------------------------------------------------------- > >> > >>- Please send only review items that are in the category > >> -- ERROR, must be fixed. > >>- If you want to send an item in the categories > >> -- Nice to have, > >> -- Editorial proposal (like move xxx to yyy), > >> -- Clarification which needs Forum decisions, > >> -- ... > >> then please substitute the __ by 22, because then it should be > >> handled in MPI-2.2. > >> > >>This format is used in > >>http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt > >>where all reviews are filed in. > >>(I'll substitute your xx by the next number. If you have more than > >>26 items, then please continue with xx.a -- xx.z, yy.a - ...) > >> > >>Please use this format. I'll have only a few minutes between two flights > >>to put all reviews together. > >> > >>WORKPLAN: > >>- The authors get back the write-token until Thursday, Apr. 17. > >> (If you need also Friday Apr. 18, then please inform me!!) > >>- All stuff that is not done until that point, will be defered to MPI-2.2! > >>- I'm on travel and may not be able to respond on e-mails this week. > >>- On Friday, Apr. 18 (or Saturday, Apr. 19), I will make the > >> final version for all final reviews and for the official reading. > >>- Version Apr. 17 together with all your review mails will be the > >> basis for the official reading. > >>- Reviews until Friday, Apr. 25. according the format above. > >>- Saturday, Apr. 26: > >> I will put all reviews together to have unique numbers. > >> > >>Best regards > >>Rolf > >> > >> > >>Annex: The rules for authors: > >> > >>The goals of your work as chapter author: > >>----------------------------------------- > >> > >>- Remove references to MPI-1 and MPI-2. > >>- Substitute by MPI. > >>- Necessary modifications to achieve this goal. > >> > >>With this, we should have a single MPI-2.1 standard that does > >>not "know" the MPI-1 or MPI-2 history of individual functions. > >> > >>** This should be mainly a task in the area of chapter-introductions. > >>** Please, never change the wording of function definitions. > >> > >>Exceptions: > >>- There are routines that are deprecated and that are > >> already referenced in a consistent way. > >> My recommendation: > >> Current wording: > >> There are *new* function, and existing are now deprecated. > >> Proposal: > >> There are functions, and there exist also deprecated functions > >> with (nearly) same functionality but deprecated due to some lack > >> in the bindings (or functionality) > >>- There is history information in the frontmatter. > >>- there is a change-log annex with limited memory (only previous version) > >> > >>Technical editing rule: > >>----------------------- > >> > >>You must identify all of your changes: > >> > >>a) new/modified wording - you are highlighting your new/modified wording with: > >> > >>\mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification > >>.... your modified / new wording .... > >>\mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification > >> > >>b) Moved paragraphs, sentences, ... - you are highlighting the first word > >> of the moved text with: > >> > >>\mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move > >>First-word > >>\mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move > >>... rest of the moved text.... > >>% MPI-2.1 round-two - end of text-move > >> > >>c) If you want to delete text (i.e. not only a move to another location), > >> the please us > >> > >>\mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - deleted-text-anchor > >>Last word of the previous text > >>\mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of anchor > >> > >>% MPI-2.1 round-two - begin of deteted text - Draft Apr.1, 2008 page/line-page/line > >>% the text you delete must be preceded with "% " > >>% deprecated text > >>% ... > >>% deprecated text > >>% MPI-2.1 round-two - end of deteted text > >> > >> Additionally, you must add this outcommented text to the end of > >> removed_source.tex > >> > >>Caution: These macros work only in black parts of the text. > >> > >>In blue parts you must substitute > >> \mpiiidotiMergeNEWforSINGLEendI% > >>by > >> \mpiiidotiMergeNEWforSINGLEendII% > >> > >> > >>The highlighting is done with red color. > >>(There are only a few other sentences from me magenta. > >> Therefore red should be the best to highlight the round-two modifications.) > >> > >>----------------------------------------------------- > >>Using svn: > >>Before you start to make changes: > >> > >> cd ....your_directory..../trunk/MPI-2.1/ > >> svn update > >> > >>to get the newest sources. > >> > >>After you made changes, please call make and check mpi-report.pdf > >>to guarantee that all your changes are really highlighted with *red* color. > >> > >>When you make the first svn commit after you received a new username with > >>write-permission, you must use the aditional option > >> > >> --username your_new_user_name > >> > >>Please commit with > >> > >>svn commit chap-xxxx/xxxx.tex -m 'MPI-2.1 - your name - what you have done' > >> > >>Please commit as soon as you finished the changes and after you have > >>checked the red color. > >> > >>-------------------------------------------------- > >> > >>Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] > >>High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 > >>University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 > >>Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner > >>Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) > >> > >> > > > > > > > >Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] > >High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 > >University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 > >Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner > >Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) > >_______________________________________________ > >mpi-21 mailing list > >mpi-21_at_[hidden] > >http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 > > > > > > > _______________________________________________ > mpi-21 mailing list > mpi-21_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30)

1 0

Re: [Mpi-21] AUTHORS+REVIEWERS - reminder - Draft Apr. 12, 2008
by unknown＠example.com 17 Apr '08

17 Apr '08

Hi Rolf, I'll need Friday the 18th to incorporate Torsten's comments into the Collectives chapter. I missed them when he first sent them. -Adam Rolf Rabenseifner wrote: >All authors (except Rich [pt2pt and datatypes]), > >- The authors get back the write-token until Thursday, Apr. 17. > (If you need also Friday Apr. 18, then please inform me!!) >- All stuff that is not done until that point, will be defered to MPI-2.2! > >This is the last reminder and chance for latest updates **today**. > >(Details on the WORKPLAN, see mail below) > >Best regards >Rolf > > >On Sun, 13 Apr 2008 00:05:37 +0200 > "Rolf Rabenseifner" <rabenseifner_at_[hidden]> wrote: > > >>Dear chapter author, dear reviewer, >> >>This e-mail is the first preparation of the official reading. >>Please read carefully. >> >>Again,we have a stable and consistent draft. >>It is SVN revision 108 and pdf and ps are on >> http://www.hlrs.de/mpi/mpi21/doc/ >>(username and password are mpi21) >> >>Nearly all chapters have received an update by the chapters' authors. >>Not finished is - as far as I can see >> - Point-to-point (may-be without MPI-1/2 problems] (Rich Graham) >> - Datatypes [it was split from Point-to-point] (Rich Graham) >>and full MPI-2 based chapters (maybe without need for updates) >> - Terms (Tony Skjellum) >> - External Interfaces (Bronis de Supinski) >> - Profiling (Bronis de Supinski) >>Therefore, review can start in all chapters, except the datatype chapter. >> >>IMPORTANT for authors: >>If you make further modifications, please be sure that you use >>the macros and that your modification (or at least an delete-anchor) >>is printed **red**. (Details on using the macros, see below.) >>Please check red color in the resulting mpi-report.pdf before you >>svn commit your changes. >>As far as I can see, all changes up to now may have no problem >>for acceptance by the Forum. >>At this late stage, I would recommend to do only changes that do >>not need intensive debates at the Forum meeting. Such things >>would be MPI-2.2 modifications. >> >>IMPORTANT for reviewers: >>- Please check very carefully all red or magenta changes. >> Modifications are done by the chapter's author (red) or >> by me (magenta). >> You may be the first reviewer who read and check this text. >>- Please check carefully the cyan text. >> Those modifications are proposed by a reviewer and have been >> implemented by my >> You may be the second reviewer for those modifications. >>- All green stuff should be fine, because it is based on >> Forum's decisions (Ballot 1-4). >>- Original text is black (MPI-1.3) or blue (MPI-2.0). >>- Please make all comments in the format >> >>---------------------------------------------------------------------------------- >>1234567890123456789012345678901234567890123456789012345678901234567890123456789012 >> All references are based on MPI-2.1 Draft Apr. 12, 2008 >>ww.a __ pnnn.ll text (with nnn=page number and ll=line number >> text continued >> ... >>ww.b __ pnnn.ll text ... and so on (total line length <= 82 characters.) >>---------------------------------------------------------------------------------- >> >>- Please send only review items that are in the category >> -- ERROR, must be fixed. >>- If you want to send an item in the categories >> -- Nice to have, >> -- Editorial proposal (like move xxx to yyy), >> -- Clarification which needs Forum decisions, >> -- ... >> then please substitute the __ by 22, because then it should be >> handled in MPI-2.2. >> >>This format is used in >>http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt >>where all reviews are filed in. >>(I'll substitute your xx by the next number. If you have more than >>26 items, then please continue with xx.a -- xx.z, yy.a - ...) >> >>Please use this format. I'll have only a few minutes between two flights >>to put all reviews together. >> >>WORKPLAN: >>- The authors get back the write-token until Thursday, Apr. 17. >> (If you need also Friday Apr. 18, then please inform me!!) >>- All stuff that is not done until that point, will be defered to MPI-2.2! >>- I'm on travel and may not be able to respond on e-mails this week. >>- On Friday, Apr. 18 (or Saturday, Apr. 19), I will make the >> final version for all final reviews and for the official reading. >>- Version Apr. 17 together with all your review mails will be the >> basis for the official reading. >>- Reviews until Friday, Apr. 25. according the format above. >>- Saturday, Apr. 26: >> I will put all reviews together to have unique numbers. >> >>Best regards >>Rolf >> >> >>Annex: The rules for authors: >> >>The goals of your work as chapter author: >>----------------------------------------- >> >>- Remove references to MPI-1 and MPI-2. >>- Substitute by MPI. >>- Necessary modifications to achieve this goal. >> >>With this, we should have a single MPI-2.1 standard that does >>not "know" the MPI-1 or MPI-2 history of individual functions. >> >>** This should be mainly a task in the area of chapter-introductions. >>** Please, never change the wording of function definitions. >> >>Exceptions: >>- There are routines that are deprecated and that are >> already referenced in a consistent way. >> My recommendation: >> Current wording: >> There are *new* function, and existing are now deprecated. >> Proposal: >> There are functions, and there exist also deprecated functions >> with (nearly) same functionality but deprecated due to some lack >> in the bindings (or functionality) >>- There is history information in the frontmatter. >>- there is a change-log annex with limited memory (only previous version) >> >>Technical editing rule: >>----------------------- >> >>You must identify all of your changes: >> >>a) new/modified wording - you are highlighting your new/modified wording with: >> >>\mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification >>.... your modified / new wording .... >>\mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification >> >>b) Moved paragraphs, sentences, ... - you are highlighting the first word >> of the moved text with: >> >>\mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move >>First-word >>\mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move >>... rest of the moved text.... >>% MPI-2.1 round-two - end of text-move >> >>c) If you want to delete text (i.e. not only a move to another location), >> the please us >> >>\mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - deleted-text-anchor >>Last word of the previous text >>\mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of anchor >> >>% MPI-2.1 round-two - begin of deteted text - Draft Apr.1, 2008 page/line-page/line >>% the text you delete must be preceded with "% " >>% deprecated text >>% ... >>% deprecated text >>% MPI-2.1 round-two - end of deteted text >> >> Additionally, you must add this outcommented text to the end of >> removed_source.tex >> >>Caution: These macros work only in black parts of the text. >> >>In blue parts you must substitute >> \mpiiidotiMergeNEWforSINGLEendI% >>by >> \mpiiidotiMergeNEWforSINGLEendII% >> >> >>The highlighting is done with red color. >>(There are only a few other sentences from me magenta. >> Therefore red should be the best to highlight the round-two modifications.) >> >>----------------------------------------------------- >>Using svn: >>Before you start to make changes: >> >> cd ....your_directory..../trunk/MPI-2.1/ >> svn update >> >>to get the newest sources. >> >>After you made changes, please call make and check mpi-report.pdf >>to guarantee that all your changes are really highlighted with *red* color. >> >>When you make the first svn commit after you received a new username with >>write-permission, you must use the aditional option >> >> --username your_new_user_name >> >>Please commit with >> >>svn commit chap-xxxx/xxxx.tex -m 'MPI-2.1 - your name - what you have done' >> >>Please commit as soon as you finished the changes and after you have >>checked the red color. >> >>-------------------------------------------------- >> >>Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] >>High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 >>University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 >>Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner >>Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) >> >> > > > >Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] >High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 >University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 >Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner >Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) >_______________________________________________ >mpi-21 mailing list >mpi-21_at_[hidden] >http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 > > >

1 0

Re: [Mpi-21] AUTHORS+REVIEWERS - reminder - Draft Apr. 12, 2008
by unknown＠example.com 17 Apr '08

17 Apr '08

I do not plan to revise Chapter 5 this pass. You have the write token Rolf. Anything not covered in the version I checked in a week or so back should go to MPI 2.2 Dick Dick Treumann - MPI Team/TCEM IBM Systems & Technology Group Dept 0lva / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601 Tele (845) 433-7846 Fax (845) 433-8363 *

1 0

Re: [Mpi-21] AUTHORS+REVIEWERS - reminder - Draft Apr. 12, 2008
by unknown＠example.com 17 Apr '08

17 Apr '08

I believe that the language bindings chapter is up-to-date for MPI 2.1. On Apr 17, 2008, at 8:32 AM, Rolf Rabenseifner wrote: > All authors (except Rich [pt2pt and datatypes]), > > - The authors get back the write-token until Thursday, Apr. 17. > (If you need also Friday Apr. 18, then please inform me!!) > - All stuff that is not done until that point, will be defered to > MPI-2.2! > > This is the last reminder and chance for latest updates **today**. > > (Details on the WORKPLAN, see mail below) > > Best regards > Rolf > > > On Sun, 13 Apr 2008 00:05:37 +0200 > "Rolf Rabenseifner" <rabenseifner_at_[hidden]> wrote: >> Dear chapter author, dear reviewer, >> >> This e-mail is the first preparation of the official reading. >> Please read carefully. >> >> Again,we have a stable and consistent draft. >> It is SVN revision 108 and pdf and ps are on >> http://www.hlrs.de/mpi/mpi21/doc/ >> (username and password are mpi21) >> >> Nearly all chapters have received an update by the chapters' authors. >> Not finished is - as far as I can see >> - Point-to-point (may-be without MPI-1/2 problems] (Rich Graham) >> - Datatypes [it was split from Point-to-point] (Rich Graham) >> and full MPI-2 based chapters (maybe without need for updates) >> - Terms (Tony Skjellum) >> - External Interfaces (Bronis de Supinski) >> - Profiling (Bronis de Supinski) >> Therefore, review can start in all chapters, except the datatype >> chapter. >> >> IMPORTANT for authors: >> If you make further modifications, please be sure that you use >> the macros and that your modification (or at least an delete-anchor) >> is printed **red**. (Details on using the macros, see below.) >> Please check red color in the resulting mpi-report.pdf before you >> svn commit your changes. >> As far as I can see, all changes up to now may have no problem >> for acceptance by the Forum. >> At this late stage, I would recommend to do only changes that do >> not need intensive debates at the Forum meeting. Such things >> would be MPI-2.2 modifications. >> >> IMPORTANT for reviewers: >> - Please check very carefully all red or magenta changes. >> Modifications are done by the chapter's author (red) or >> by me (magenta). >> You may be the first reviewer who read and check this text. >> - Please check carefully the cyan text. >> Those modifications are proposed by a reviewer and have been >> implemented by my >> You may be the second reviewer for those modifications. >> - All green stuff should be fine, because it is based on >> Forum's decisions (Ballot 1-4). >> - Original text is black (MPI-1.3) or blue (MPI-2.0). >> - Please make all comments in the format >> >> ---------------------------------------------------------------------------------- >> 1234567890123456789012345678901234567890123456789012345678901234567890123456789012 >> All references are based on MPI-2.1 Draft Apr. 12, 2008 >> ww.a __ pnnn.ll text (with nnn=page number and ll=line number >> text continued >> ... >> ww.b __ pnnn.ll text ... and so on (total line length <= 82 >> characters.) >> ---------------------------------------------------------------------------------- >> >> - Please send only review items that are in the category >> -- ERROR, must be fixed. >> - If you want to send an item in the categories >> -- Nice to have, >> -- Editorial proposal (like move xxx to yyy), >> -- Clarification which needs Forum decisions, >> -- ... >> then please substitute the __ by 22, because then it should be >> handled in MPI-2.2. >> >> This format is used in >> http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt >> where all reviews are filed in. >> (I'll substitute your xx by the next number. If you have more than >> 26 items, then please continue with xx.a -- xx.z, yy.a - ...) >> >> Please use this format. I'll have only a few minutes between two >> flights >> to put all reviews together. >> >> WORKPLAN: >> - The authors get back the write-token until Thursday, Apr. 17. >> (If you need also Friday Apr. 18, then please inform me!!) >> - All stuff that is not done until that point, will be defered to >> MPI-2.2! >> - I'm on travel and may not be able to respond on e-mails this week. >> - On Friday, Apr. 18 (or Saturday, Apr. 19), I will make the >> final version for all final reviews and for the official reading. >> - Version Apr. 17 together with all your review mails will be the >> basis for the official reading. >> - Reviews until Friday, Apr. 25. according the format above. >> - Saturday, Apr. 26: >> I will put all reviews together to have unique numbers. >> >> Best regards >> Rolf >> >> >> Annex: The rules for authors: >> >> The goals of your work as chapter author: >> ----------------------------------------- >> >> - Remove references to MPI-1 and MPI-2. >> - Substitute by MPI. >> - Necessary modifications to achieve this goal. >> >> With this, we should have a single MPI-2.1 standard that does >> not "know" the MPI-1 or MPI-2 history of individual functions. >> >> ** This should be mainly a task in the area of chapter-introductions. >> ** Please, never change the wording of function definitions. >> >> Exceptions: >> - There are routines that are deprecated and that are >> already referenced in a consistent way. >> My recommendation: >> Current wording: >> There are *new* function, and existing are now deprecated. >> Proposal: >> There are functions, and there exist also deprecated functions >> with (nearly) same functionality but deprecated due to some lack >> in the bindings (or functionality) >> - There is history information in the frontmatter. >> - there is a change-log annex with limited memory (only previous >> version) >> >> Technical editing rule: >> ----------------------- >> >> You must identify all of your changes: >> >> a) new/modified wording - you are highlighting your new/modified >> wording with: >> >> \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of >> modification >> .... your modified / new wording .... >> \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of >> modification >> >> b) Moved paragraphs, sentences, ... - you are highlighting the >> first word >> of the moved text with: >> >> \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text- >> move >> First-word >> \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text- >> move >> ... rest of the moved text.... >> % MPI-2.1 round-two - end of text-move >> >> c) If you want to delete text (i.e. not only a move to another >> location), >> the please us >> >> \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - deleted-text- >> anchor >> Last word of the previous text >> \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of anchor >> >> % MPI-2.1 round-two - begin of deteted text - Draft Apr.1, 2008 >> page/line-page/line >> % the text you delete must be preceded with "% " >> % deprecated text >> % ... >> % deprecated text >> % MPI-2.1 round-two - end of deteted text >> >> Additionally, you must add this outcommented text to the end of >> removed_source.tex >> >> Caution: These macros work only in black parts of the text. >> >> In blue parts you must substitute >> \mpiiidotiMergeNEWforSINGLEendI% >> by >> \mpiiidotiMergeNEWforSINGLEendII% >> >> >> The highlighting is done with red color. >> (There are only a few other sentences from me magenta. >> Therefore red should be the best to highlight the round-two >> modifications.) >> >> ----------------------------------------------------- >> Using svn: >> Before you start to make changes: >> >> cd ....your_directory..../trunk/MPI-2.1/ >> svn update >> >> to get the newest sources. >> >> After you made changes, please call make and check mpi-report.pdf >> to guarantee that all your changes are really highlighted with >> *red* color. >> >> When you make the first svn commit after you received a new >> username with >> write-permission, you must use the aditional option >> >> --username your_new_user_name >> >> Please commit with >> >> svn commit chap-xxxx/xxxx.tex -m 'MPI-2.1 - your name - what you >> have done' >> >> Please commit as soon as you finished the changes and after you have >> checked the red color. >> >> -------------------------------------------------- >> >> Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] >> High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 >> University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 >> Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner >> Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) > > > > Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] > High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 > University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 > Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner > Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) > _______________________________________________ > mpi-21 mailing list > mpi-21_at_[hidden] > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21 -- Jeff Squyres Cisco Systems

1 0

AUTHORS+REVIEWERS - reminder - Draft Apr. 12, 2008
by unknown＠example.com 17 Apr '08

17 Apr '08

All authors (except Rich [pt2pt and datatypes]), - The authors get back the write-token until Thursday, Apr. 17. (If you need also Friday Apr. 18, then please inform me!!) - All stuff that is not done until that point, will be defered to MPI-2.2! This is the last reminder and chance for latest updates **today**. (Details on the WORKPLAN, see mail below) Best regards Rolf On Sun, 13 Apr 2008 00:05:37 +0200 "Rolf Rabenseifner" <rabenseifner_at_[hidden]> wrote: > Dear chapter author, dear reviewer, > > This e-mail is the first preparation of the official reading. > Please read carefully. > > Again,we have a stable and consistent draft. > It is SVN revision 108 and pdf and ps are on > http://www.hlrs.de/mpi/mpi21/doc/ > (username and password are mpi21) > > Nearly all chapters have received an update by the chapters' authors. > Not finished is - as far as I can see > - Point-to-point (may-be without MPI-1/2 problems] (Rich Graham) > - Datatypes [it was split from Point-to-point] (Rich Graham) > and full MPI-2 based chapters (maybe without need for updates) > - Terms (Tony Skjellum) > - External Interfaces (Bronis de Supinski) > - Profiling (Bronis de Supinski) > Therefore, review can start in all chapters, except the datatype chapter. > > IMPORTANT for authors: > If you make further modifications, please be sure that you use > the macros and that your modification (or at least an delete-anchor) > is printed **red**. (Details on using the macros, see below.) > Please check red color in the resulting mpi-report.pdf before you > svn commit your changes. > As far as I can see, all changes up to now may have no problem > for acceptance by the Forum. > At this late stage, I would recommend to do only changes that do > not need intensive debates at the Forum meeting. Such things > would be MPI-2.2 modifications. > > IMPORTANT for reviewers: > - Please check very carefully all red or magenta changes. > Modifications are done by the chapter's author (red) or > by me (magenta). > You may be the first reviewer who read and check this text. > - Please check carefully the cyan text. > Those modifications are proposed by a reviewer and have been > implemented by my > You may be the second reviewer for those modifications. > - All green stuff should be fine, because it is based on > Forum's decisions (Ballot 1-4). > - Original text is black (MPI-1.3) or blue (MPI-2.0). > - Please make all comments in the format > > ---------------------------------------------------------------------------------- > 1234567890123456789012345678901234567890123456789012345678901234567890123456789012 > All references are based on MPI-2.1 Draft Apr. 12, 2008 > ww.a __ pnnn.ll text (with nnn=page number and ll=line number > text continued > ... > ww.b __ pnnn.ll text ... and so on (total line length <= 82 characters.) > ---------------------------------------------------------------------------------- > > - Please send only review items that are in the category > -- ERROR, must be fixed. > - If you want to send an item in the categories > -- Nice to have, > -- Editorial proposal (like move xxx to yyy), > -- Clarification which needs Forum decisions, > -- ... > then please substitute the __ by 22, because then it should be > handled in MPI-2.2. > > This format is used in > http://www.hlrs.de/mpi/mpi21/doc/MPI-2.1draft-2008-02-23-review.txt > where all reviews are filed in. > (I'll substitute your xx by the next number. If you have more than > 26 items, then please continue with xx.a -- xx.z, yy.a - ...) > > Please use this format. I'll have only a few minutes between two flights > to put all reviews together. > > WORKPLAN: > - The authors get back the write-token until Thursday, Apr. 17. > (If you need also Friday Apr. 18, then please inform me!!) > - All stuff that is not done until that point, will be defered to MPI-2.2! > - I'm on travel and may not be able to respond on e-mails this week. > - On Friday, Apr. 18 (or Saturday, Apr. 19), I will make the > final version for all final reviews and for the official reading. > - Version Apr. 17 together with all your review mails will be the > basis for the official reading. > - Reviews until Friday, Apr. 25. according the format above. > - Saturday, Apr. 26: > I will put all reviews together to have unique numbers. > > Best regards > Rolf > > > Annex: The rules for authors: > > The goals of your work as chapter author: > ----------------------------------------- > > - Remove references to MPI-1 and MPI-2. > - Substitute by MPI. > - Necessary modifications to achieve this goal. > > With this, we should have a single MPI-2.1 standard that does > not "know" the MPI-1 or MPI-2 history of individual functions. > > ** This should be mainly a task in the area of chapter-introductions. > ** Please, never change the wording of function definitions. > > Exceptions: > - There are routines that are deprecated and that are > already referenced in a consistent way. > My recommendation: > Current wording: > There are *new* function, and existing are now deprecated. > Proposal: > There are functions, and there exist also deprecated functions > with (nearly) same functionality but deprecated due to some lack > in the bindings (or functionality) > - There is history information in the frontmatter. > - there is a change-log annex with limited memory (only previous version) > > Technical editing rule: > ----------------------- > > You must identify all of your changes: > > a) new/modified wording - you are highlighting your new/modified wording with: > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of modification > .... your modified / new wording .... > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of modification > > b) Moved paragraphs, sentences, ... - you are highlighting the first word > of the moved text with: > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - begin of text-move > First-word > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - ongoing text-move > ... rest of the moved text.... > % MPI-2.1 round-two - end of text-move > > c) If you want to delete text (i.e. not only a move to another location), > the please us > > \mpiiidotiMergeNEWforSINGLEbegin% MPI-2.1 round-two - deleted-text-anchor > Last word of the previous text > \mpiiidotiMergeNEWforSINGLEendI% MPI-2.1 round-two - end of anchor > > % MPI-2.1 round-two - begin of deteted text - Draft Apr.1, 2008 page/line-page/line > % the text you delete must be preceded with "% " > % deprecated text > % ... > % deprecated text > % MPI-2.1 round-two - end of deteted text > > Additionally, you must add this outcommented text to the end of > removed_source.tex > > Caution: These macros work only in black parts of the text. > > In blue parts you must substitute > \mpiiidotiMergeNEWforSINGLEendI% > by > \mpiiidotiMergeNEWforSINGLEendII% > > > The highlighting is done with red color. > (There are only a few other sentences from me magenta. > Therefore red should be the best to highlight the round-two modifications.) > > ----------------------------------------------------- > Using svn: > Before you start to make changes: > > cd ....your_directory..../trunk/MPI-2.1/ > svn update > > to get the newest sources. > > After you made changes, please call make and check mpi-report.pdf > to guarantee that all your changes are really highlighted with *red* color. > > When you make the first svn commit after you received a new username with > write-permission, you must use the aditional option > > --username your_new_user_name > > Please commit with > > svn commit chap-xxxx/xxxx.tex -m 'MPI-2.1 - your name - what you have done' > > Please commit as soon as you finished the changes and after you have > checked the red color. > > -------------------------------------------------- > > Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] > High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 > University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 > Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner > Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden] High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30)

1 0