- mpi-forum - mailman3.cels.anl.gov

Second vote request for a couple of sessions related issues and associated pull requests
by Pritchard Jr., Howard 17 Nov '22

17 Nov '22

Hello All, I’d like to put in a request to have second votes on the following pull requests for the December ’22 MPI Forum: Language bindings chapter needs updating for Sessions model https://github.com/mpi-forum/mpi-issues/issues/535<https://urldefense.com/v3/__https:/github.com/mpi-forum/mpi-issues/issues/5…> https://github.com/mpi-forum/mpi-standard/pull/658<https://urldefense.com/v3/__https:/github.com/mpi-forum/mpi-standard/pull/6…> Clarify/fix description and usage of MPI_GROUP_NULL https://github.com/mpi-forum/mpi-issues/issues/534<https://urldefense.com/v3/__https:/github.com/mpi-forum/mpi-issues/issues/5…> https://github.com/mpi-forum/mpi-standard/pull/651<https://urldefense.com/v3/__https:/github.com/mpi-forum/mpi-standard/pull/6…> Thanks, Howard — [signature_61897647] Howard Pritchard Research Scientist HPC-ENV Los Alamos National Laboratory howardp(a)lanl.gov [signature_4030117403]<https://www.instagram.com/losalamosnatlab/>[signature_2594880257]<https://twitter.com/LosAlamosNatLab>[signature_1423503820]<https://www.linkedin.com/company/los-alamos-national-laboratory/>[signature_1185700962]<https://www.facebook.com/LosAlamosNationalLab/>

1 0

Reading and voting announcement - additionally #641 and co.
by Rolf Rabenseifner 17 Nov '22

17 Nov '22

Hello all together, As Language Bindings Summary Chapter, I'd like to read the following issues at the next meeting (Dec. 2022). The Annex A.2 was developed by Terms WG as proof of new Semantic Terms section 2.4 for MPI-4.0 and also as a very helpful summary for the reader of the MPI standard. Puri Bangalore converted it into Latex, Joseph Schuchart helped to add the RMA chapter, and other smaller issues, and the forum commented on it at the virtual meeting Nov. 9, 2022. The forum asked for moving it into a side-doc as long as it is incomplete. The following issues and pull requests are completing the side-document Annex A.2 and moving it back to the MPI-standard. Completing the side-doc: - Issue A.2-#17: https://github.com/mpi-forum/function-table/issues/17 PR: https://github.com/mpi-forum/function-table/pull/9 Adding all operation related routines for one-sided communication - Issue A.2-#5: https://github.com/mpi-forum/function-table/issues/5 PR: https://github.com/mpi-forum/function-table/pull/14 Adding MPI_Comm_set_info - Issue A.2-#7: https://github.com/mpi-forum/function-table/issues/7 PR: https://github.com/mpi-forum/function-table/pull/15 Correction for MPI_COMM_CREATE, ... (a missing f in the table entry) - Issue A.2-#8: https://github.com/mpi-forum/function-table/issues/8 PR: https://github.com/mpi-forum/function-table/pull/12 Removing wrong remark 4) on the NEIGHBOR-routines - Issue A.2-#10: https://github.com/mpi-forum/function-table/issues/10 PR: https://github.com/mpi-forum/function-table/pull/16 Adding MPI_Cancel and MPI_Test_cancelled - Issue A.2-#11: https://github.com/mpi-forum/function-table/issues/11 PR: https://github.com/mpi-forum/function-table/pull/13 Adding an intro sentence that often procedures are presented under constrains And then moving the side-doc into MPI-4.1: - Issue #641: https://github.com/mpi-forum/mpi-issues/issues/641 PR: https://github.com/mpi-forum/mpi-standard/pull/752 Integrating the content of the side-doc https://www.mpi-forum.org/docs/mpi-4.0/addendum-Semantics.pdf plus all the issues above into MPI-4.1 The whole Annex A.2 including all these PRs can be viewed as commented pdf: - PDF, see pages 11, 839-846 and 1007: https://github.com/mpi-forum/mpi-standard/files/10031494/mpi41-report_Issue… It includes PR752 and all the Annex A.2 side-doc pull requests A.2-PR9, A.2-PR12, A.2-PR13, A.2-PR14, A.2-PR15, and A.2-PR16. All the other issues (493, 499, 468, 565, 471, 605, 556) and probably chapter committee changes (412, 420, 492, 560) see below in my email from yesterday. Best regards Rolf ----- Original Message ----- > To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> > Cc: "Rolf Rabenseifner" <rabenseifner(a)hlrs.de> > Sent: Wednesday, November 16, 2022 11:44:48 PM > Subject: [Mpi-forum] Reading and voting announcement > Hello all, > > As the Chapter Committee or WG chair or member, or ticket owner, > I'd like to read the following items at the next meeting (Dec. 2022): > > Readings about the Progress rules: > > - Issue #493: https://github.com/mpi-forum/mpi-issues/issues/493 > PR: https://github.com/mpi-forum/mpi-standard/pull/753 > PDF: > https://github.com/mpi-forum/mpi-standard/files/10016623/mpi41-report_Issue… > > Issue: New Section "2.9 Progress" in the Terms-Chapter > + additional rule and example 12.13 in Section "12.7.3 Progress" > > The proposal was developed by Dan Holmes, Claudia Blaas-Schenner, Joseph > Schuchart, > Tobias Haas, and myself with additional support from Bill Gropp and many forum > members > during the discussions for MPI-4.0 and at the virtual MPI-4.1 meeting on Nov. 2, > 2022. > > > - Issue #499: https://github.com/mpi-forum/mpi-issues/issues/499 > PR: https://github.com/mpi-forum/mpi-standard/pull/729 > PDF: > https://github.com/mpi-forum/mpi-standard/files/10024194/mpi41-report_Issue… > see page pages 569 and 999 > > Issue: Explicit progress rule for MPI_WIN_TEST > > - Related Issue #468 (MPI_REQUEST_GET_STATUS) and #492 (some wording) see below. > > > Reading about Annex A.2 (semantic of operation-related MPI procedures) > > - will be announced tomorrow (Issue #641 and PR752) > > > Other readings: > > - Issue #565: https://github.com/mpi-forum/mpi-issues/issues/565 > PR: https://github.com/mpi-forum/mpi-standard/pull/727 > > Issue: Fortran 2018 instead or additional to TS 29113 > (by Jeff Hammond) > In Terms and Language Binding chapters > > > Reading + Issue-0 voting > ------------------------ > > - Issue #471: https://github.com/mpi-forum/mpi-issues/issues/471 > PR: https://github.com/mpi-forum/mpi-standard/pull/751 > Content: tasks --> MPI processes in Terms chapter > reading + ticket-0-voting > > > - Issue #605: https://github.com/mpi-forum/mpi-issues/issues/605 > PR: https://github.com/mpi-forum/mpi-standard/pull/746 > PDF: > https://github.com/mpi-forum/mpi-standard/files/10024811/mpi41-report_Issue… > > Issue: Title-lines/sentences for all examples in the "Topologies" chapter > > > Errata reading and voting > ------------------------- > > - Issue #556: https://github.com/mpi-forum/mpi-issues/issues/556 > PR: https://github.com/mpi-forum/mpi-standard/pull/690 > > Issue: Reverting unintended change of the definition of > the coords argument in MPI_CART_COORDS > (Issue is by Kyle Gerard Felker, PR by Christoph Niethammer) > > > 1st vote is scheduled for > ------------------------- > > - Issue #468: https://github.com/mpi-forum/mpi-issues/issues/468 > PR: https://github.com/mpi-forum/mpi-standard/pull/667 > > Issue: Explicit progress rule for MPI_REQUEST_GET_STATUS > > > In addition, I'd like to read the following items at the Dec. 2022 forum meeting > if they are not yet passed as chapter committee change. > > If they pass as chapter committee change, then please take this > only as a notice about those changes: > > - Issue #412: https://github.com/mpi-forum/mpi-issues/issues/412 > PR: https://github.com/mpi-forum/mpi-standard/pull/743 > PDF: > https://github.com/mpi-forum/mpi-standard/files/10023828/mpi41-report_Issue… > > - Issue #420: https://github.com/mpi-forum/mpi-issues/issues/420 > PR: https://github.com/mpi-forum/mpi-standard/pull/745 > PDF: > https://github.com/mpi-forum/mpi-standard/files/10023634/mpi41-report_Issue… > > - Issue #492: https://github.com/mpi-forum/mpi-issues/issues/492 > PR: https://github.com/mpi-forum/mpi-standard/pull/672 > no PDF, because trivial > > - Issue #560: https://github.com/mpi-forum/mpi-issues/issues/560 > PR: https://github.com/mpi-forum/mpi-standard/pull/713 > PDF: > https://github.com/mpi-forum/mpi-standard/files/10023611/mpi41-report_Issue… > > > Best regards > Rolf -- Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseifner(a)hlrs.de . High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . Nobelstr. 19, 70569 Stuttgart, Germany

1 0

Reading and voting announcement
by Rolf Rabenseifner 16 Nov '22

16 Nov '22

Hello all, As the Chapter Committee or WG chair or member, or ticket owner, I'd like to read the following items at the next meeting (Dec. 2022): Readings about the Progress rules: - Issue #493: https://github.com/mpi-forum/mpi-issues/issues/493 PR: https://github.com/mpi-forum/mpi-standard/pull/753 PDF: https://github.com/mpi-forum/mpi-standard/files/10016623/mpi41-report_Issue… Issue: New Section "2.9 Progress" in the Terms-Chapter + additional rule and example 12.13 in Section "12.7.3 Progress" The proposal was developed by Dan Holmes, Claudia Blaas-Schenner, Joseph Schuchart, Tobias Haas, and myself with additional support from Bill Gropp and many forum members during the discussions for MPI-4.0 and at the virtual MPI-4.1 meeting on Nov. 2, 2022. - Issue #499: https://github.com/mpi-forum/mpi-issues/issues/499 PR: https://github.com/mpi-forum/mpi-standard/pull/729 PDF: https://github.com/mpi-forum/mpi-standard/files/10024194/mpi41-report_Issue… see page pages 569 and 999 Issue: Explicit progress rule for MPI_WIN_TEST - Related Issue #468 (MPI_REQUEST_GET_STATUS) and #492 (some wording) see below. Reading about Annex A.2 (semantic of operation-related MPI procedures) - will be announced tomorrow (Issue #641 and PR752) Other readings: - Issue #565: https://github.com/mpi-forum/mpi-issues/issues/565 PR: https://github.com/mpi-forum/mpi-standard/pull/727 Issue: Fortran 2018 instead or additional to TS 29113 (by Jeff Hammond) In Terms and Language Binding chapters Reading + Issue-0 voting ------------------------ - Issue #471: https://github.com/mpi-forum/mpi-issues/issues/471 PR: https://github.com/mpi-forum/mpi-standard/pull/751 Content: tasks --> MPI processes in Terms chapter reading + ticket-0-voting - Issue #605: https://github.com/mpi-forum/mpi-issues/issues/605 PR: https://github.com/mpi-forum/mpi-standard/pull/746 PDF: https://github.com/mpi-forum/mpi-standard/files/10024811/mpi41-report_Issue… Issue: Title-lines/sentences for all examples in the "Topologies" chapter Errata reading and voting ------------------------- - Issue #556: https://github.com/mpi-forum/mpi-issues/issues/556 PR: https://github.com/mpi-forum/mpi-standard/pull/690 Issue: Reverting unintended change of the definition of the coords argument in MPI_CART_COORDS (Issue is by Kyle Gerard Felker, PR by Christoph Niethammer) 1st vote is scheduled for ------------------------- - Issue #468: https://github.com/mpi-forum/mpi-issues/issues/468 PR: https://github.com/mpi-forum/mpi-standard/pull/667 Issue: Explicit progress rule for MPI_REQUEST_GET_STATUS In addition, I'd like to read the following items at the Dec. 2022 forum meeting if they are not yet passed as chapter committee change. If they pass as chapter committee change, then please take this only as a notice about those changes: - Issue #412: https://github.com/mpi-forum/mpi-issues/issues/412 PR: https://github.com/mpi-forum/mpi-standard/pull/743 PDF: https://github.com/mpi-forum/mpi-standard/files/10023828/mpi41-report_Issue… - Issue #420: https://github.com/mpi-forum/mpi-issues/issues/420 PR: https://github.com/mpi-forum/mpi-standard/pull/745 PDF: https://github.com/mpi-forum/mpi-standard/files/10023634/mpi41-report_Issue… - Issue #492: https://github.com/mpi-forum/mpi-issues/issues/492 PR: https://github.com/mpi-forum/mpi-standard/pull/672 no PDF, because trivial - Issue #560: https://github.com/mpi-forum/mpi-issues/issues/560 PR: https://github.com/mpi-forum/mpi-standard/pull/713 PDF: https://github.com/mpi-forum/mpi-standard/files/10023611/mpi41-report_Issue… Best regards Rolf -- Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseifner(a)hlrs.de . High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . Nobelstr. 19, 70569 Stuttgart, Germany

1 0

Re: [Mpi-forum] propose ABI working group
by Jeff Hammond 16 Nov '22

16 Nov '22

> On 16Nov 2022, at 5:11 PM, Wes Bland <wesley(a)wesbland.com> wrote: > > The rules say you need to get four IMOVE (voting) orgs to support creating a WG at a meeting: > > > Working groups can be established at MPI Forum meetings once at least four IMOVE organizations indicate support for that proposed Working Group. > > So feel free to propose it at the December meeting and have some folks lined up to give it a thumbs up. Of course, in the meantime, folks are free to start getting together and discussing the topic. The old mailing list from 2008 is still around <https://lists.mpi-forum.org/mailman/listinfo/mpi3-abi>, but I’d recommend you not use it since it uses our old naming scheme. Once the group is official, I’ll make the new list and GitHub org. Thanks, I’ll rally the votes. Interested parties should ping me on Slack to be added to #wg-abi. Somebody was optimistic enough to create https://github.com/mpiwg-abi/ this morning but it’s a mystery who 😉 Jeff > Thanks, > Wes > >> On Nov 16, 2022, at 1:54 AM, Jeff Hammond via mpi-forum <mpi-forum(a)lists.mpi-forum.org> wrote: >> >> I don't know what we do to create new working groups with the post-COVID rules, but I would like to create and chair a WG focused on ABI standardization. >> >> There is strong support for this effort in many user communities, including developers and maintainers of Spack, mpi4py, Julia MPI (MPI.jl), Rust MPI (rsmpi), PETSc and NVHPC SDK, to name a few. There are even a few implementers who have expressed support, but I won't name them for their own protection. >> >> The problem is so exasperating for our users that there are at least two different projects devoted to mitigating ABI problems (not including shims built in to the aforementioned MPI wrappers): >> >> https://github.com/cea-hpc/wi4mpi <https://github.com/cea-hpc/wi4mpi> >> https://github.com/eschnett/MPItrampoline <https://github.com/eschnett/MPItrampoline> >> >> I've written about this a bit already, for those who are interested. More material will be forthcoming once I have time for more experiments. >> >> https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI.md <https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI.md> >> https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_2.md <https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_2.md> >> https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_3.md <https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_3.md> >> https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_4.md <https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_4.md> >> >> I understand this is a controversial topic, particularly for implementers. I hope that we can proceed objectively. >> >> Thanks, >> >> Jeff >> >> -- >> Jeff Hammond >> jeff.science(a)gmail.com <mailto:[email protected]> >> http://jeffhammond.github.io/ <http://jeffhammond.github.io/>_______________________________________________ >> mpi-forum mailing list >> mpi-forum(a)lists.mpi-forum.org >> https://lists.mpi-forum.org/mailman/listinfo/mpi-forum >

1 0

propose ABI working group
by Jeff Hammond 16 Nov '22

16 Nov '22

I don't know what we do to create new working groups with the post-COVID rules, but I would like to create and chair a WG focused on ABI standardization. There is strong support for this effort in many user communities, including developers and maintainers of Spack, mpi4py, Julia MPI (MPI.jl), Rust MPI (rsmpi), PETSc and NVHPC SDK, to name a few. There are even a few implementers who have expressed support, but I won't name them for their own protection. The problem is so exasperating for our users that there are at least two different projects devoted to mitigating ABI problems (not including shims built in to the aforementioned MPI wrappers): https://github.com/cea-hpc/wi4mpi https://github.com/eschnett/MPItrampoline I've written about this a bit already, for those who are interested. More material will be forthcoming once I have time for more experiments. https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI.md https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_2.md https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_3.md https://github.com/jeffhammond/blog/blob/main/MPI_Needs_ABI_Part_4.md I understand this is a controversial topic, particularly for implementers. I hope that we can proceed objectively. Thanks, Jeff -- Jeff Hammond jeff.science(a)gmail.com http://jeffhammond.github.io/

1 0

MPI 4.1 Progress Update
by Wes Bland 10 Nov '22

10 Nov '22

Hi all, Sorry I haven’t been able to attend the last couple of virtual meetings to give an update on progress for MPI 4.1. I wanted to do so quickly before we get into the two week window for the upcoming meeting. Remember that the next voting meeting is on December 5, which makes November 21 (the week of Thanksgiving in the US and the week after SC everywhere) the deadline. All readings need to be announced by then and we only have two meetings left for readings. Also, keep in mind that almost all tickets need a re-reading so please try to have your tickets ready for the December meeting to keep us on track for getting MPI 4.1 ready for SC 23. With that out of the way, folks have been making progress on their issues since the last meeting. Our current status is that we have (excluding chapter committee and editor changes that can be made any time): * 60 items marked as “To Do” (have no pull request) * 40 items marked as “In Progress” (have a pull request, but have not been read) * 6 items marked as “Had Reading” * 3 items marked as having passed their first vote As usual, to see which issues have been assigned to you, you can click on this link: https://github.com/orgs/mpi-forum/projects/1/views/3 You also should have received an automated email from me a few weeks ago listing all of your issues. I did unbundle some of the issues that had been assigned to each chapter committee after that email, so your list may have grown a bit since then. If you have any questions about any issue assigned to you, feel free to reach out to Martin or myself. Let’s try to improve MPI 4.1 as much as possible by moving these todo’s forward. If there is something on your list that you think should be moved out to MPI 5.0 or dropped entirely, feel free to post a comment on the issue itself and we can make a decision from there. Thanks, Wes

1 0

Virtual MPI Meeting today (9. Nov.), 10am CT
by Martin Schulz 09 Nov '22

09 Nov '22

Hi all, We will have our next virtual MPI forum meeting today (9th of November) at 10am CT – the dial in is, as usual, on the forum webpage and the topic is the integration of the annex document listing the semantics of MPI procedures into the actual standard. Thanks, Martin PS: Note, both Europe and the US have switched to normal or winter time – hence the usual time difference applies. -- Prof. Dr. Martin Schulz, Chair of Computer Architecture and Parallel Systems Department of Informatics, TU-Munich, Boltzmannstraße 3, D-85748 Garching Member of the Board of Directors at the Leibniz Supercomputing Centre (LRZ) Email: schulzm(a)in.tum.de

1 0

Virtual MPI Forum Meeting tomorrow (Wed. Nov. 2, 2022) on "MPI Progress" (updated)
by Rolf Rabenseifner 01 Nov '22

01 Nov '22

Dear all, (pdf updated, see link below) We want to invite you to our Virtual MPI Forum meeting tomorrow, Wednesday, Nov. 2, 2022, - at 10am US CDT (still US summer time) - which is in Europe - as far as I understand - 1 hour earlier as usual, i.e. 4pm CET (Central European winter time) The zoom link is, as usual, available via the meeting page. Topics: - the proposal about **MPI Progress** (in general) see https://github.com/mpi-forum/mpi-issues/issues/493 and the **updated** pdf file https://github.com/mpi-forum/mpi-issues/files/9914195/progress_proposal_rab… - the related proposal on MPI_REQUEST_GET_STATUS (a re-reading) see https://github.com/mpi-forum/mpi-issues/issues/468 plus https://github.com/mpi-forum/mpi-standard/pull/667 - the related proposal on MPI_WIN_TEST see https://github.com/mpi-forum/mpi-issues/issues/499 plus https://github.com/mpi-forum/mpi-standard/pull/729 The agenda for this 2 hour meeting is - a complete reading (including only short Q&A) of all three issues that everybody in the meeting can get familiar with all aspects, - a discussion on the proposals. Only if there is remaining time, we can go also to very chapter-specific questions. The proposal is prepared by Claudia Blaas-Schenner, Dan Holmes, Joseph Schuchart, Puri Bangalore, Tobias Haas, and me, with all the input from the MPI-4.0 discussions and additional input from the RMA and the Semantic Terms WGs during the common meeting last week. Kind regards - on behave of the terms WG - Rolf -- Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseifner(a)hlrs.de . High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . Nobelstr. 19, 70569 Stuttgart, Germany

1 0

Virtual MPI Forum Meeting tomorrow (Wed. Nov. 2, 2022) on "MPI Progress"
by Rolf Rabenseifner 01 Nov '22

01 Nov '22

Dear all, We want to invite you to our Virtual MPI Forum meeting tomorrow, Wednesday, Nov. 2, 2022, - at 10am US CDT (still US summer time) - which is in Europe - as far as I understand - 1 hour earlier as usual, i.e. 4pm CET (Central European winter time) The zoom link is, as usual, available via the meeting page. Topics: - the proposal about **MPI Progress** (in general) see https://github.com/mpi-forum/mpi-issues/issues/493 and the pdf file https://github.com/mpi-forum/mpi-issues/files/9908852/progress_proposal_rab… - the related proposal on MPI_REQUEST_GET_STATUS (a re-reading) see https://github.com/mpi-forum/mpi-issues/issues/468 plus https://github.com/mpi-forum/mpi-standard/pull/667 - the related proposal on MPI_WIN_TEST see https://github.com/mpi-forum/mpi-issues/issues/499 plus https://github.com/mpi-forum/mpi-standard/pull/729 The agenda for this 2 hour meeting is - a complete reading (including only short Q&A) of all three issues that everybody in the meeting can get familiar with all aspects, - a discussion on the proposals. Only if there is remaining time, we can go also to very chapter-specific questions. The proposal is prepared by Claudia Blaas-Schenner, Dan Holmes, Joseph Schuchart, Puri Bangalore, Tobias Haas, and me, with all the input from the MPI-4.0 discussions and additional input from the RMA and the Semantic Terms WGs during the common meeting last week. Kind regards - on behave of the terms WG - Rolf -- Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseifner(a)hlrs.de . High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 . University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner . Nobelstr. 19, 70569 Stuttgart, Germany

1 0

Reminder: MPI Virtual Meeting today 10am US CT
by Martin Schulz 26 Oct '22

26 Oct '22

Hi all, We have a virtual MPI Forum meeting today covering the discussion on PBuf_prepare for partitioned communication (or possibly beyond that). The access link is, as usual, available from the meetings page. Thanks, Martin -- Prof. Dr. Martin Schulz, Chair of Computer Architecture and Parallel Systems Department of Informatics, TU-Munich, Boltzmannstraße 3, D-85748 Garching Member of the Board of Directors at the Leibniz Supercomputing Centre (LRZ) Email: schulzm(a)in.tum.de

1 0