<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body>
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p>Matt's method seems to work well, though instead of editing the actual function I put the relevant parts directly into my code. I made the small example attached here.<br>
</p>
<p><br>
</p>
<p>I might look into Star Forests at some point, though it's not really touched upon in the manual (I will probably take a look at your paper,
<a href="https://arxiv.org/abs/2102.13018" class="OWAAutoLink" id="LPlnk80864">https://arxiv.org/abs/2102.13018</a>).<br>
</p>
<p><br>
</p>
<p>Med venlig hilsen / Best regards</p>
<p>Peder<br>
</p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>Fra:</b> Junchao Zhang <junchao.zhang@gmail.com><br>
<b>Sendt:</b> 1. juli 2021 16:38:29<br>
<b>Til:</b> Jed Brown<br>
<b>Cc:</b> Peder Jørgensgaard Olesen; petsc-users@mcs.anl.gov<br>
<b>Emne:</b> Re: Sv: [petsc-users] Scatter parallel Vec to sequential Vec on non-zeroth process</font>
<div> </div>
</div>
<div>
<div dir="ltr">Peder,
<div> PETSCSF_PATTERN_ALLTOALL only supports MPI_Alltoall (not Alltoallv), and is only used by petsc internally at few places. </div>
<div> I suggest you can go with Matt's approach. After it solves your problem, you can distill an example to demo the communication pattern. Then we can see how to efficiently support that in petsc. </div>
<div><br>
</div>
<div> Thanks.</div>
<div>
<div>
<div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">--Junchao Zhang</div>
</div>
</div>
<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Jul 1, 2021 at 7:42 AM Jed Brown <<a href="mailto:jed@jedbrown.org">jed@jedbrown.org</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Peder Jørgensgaard Olesen <<a href="mailto:pjool@mek.dtu.dk" target="_blank">pjool@mek.dtu.dk</a>> writes:<br>
<br>
> Each process is assigned an indexed subset of the tasks (the tasks are of constant size), and, for each task index, the relevant data is scattered as a SEQVEC to the process (this is done for all processes in each step, using an adaption of the code in Matt's
link). This way each process only receives just the data it needs to complete the task. While I'm currently working with very moderate size data sets I'll eventually need to handle something rather more massive, so I want to economize memory where possible
and give each process only the data it needs.<br>
<br>
>From the sounds of it, this pattern ultimately boils down to MPI_Gather being called P times where P is the size of the communicator. This will work okay when P is small, but it's much less efficient than calling MPI_Alltoall (or MPI_Alltoallv), which you can
do by creating one PetscSF that ships the needed data to each task and PETSCSF_PATTERN_ALLTOALL. You can see an example.<br>
<br>
<a href="https://gitlab.com/petsc/petsc/-/blob/main/src/vec/is/sf/tests/ex3.c#L93-151" rel="noreferrer" target="_blank">https://gitlab.com/petsc/petsc/-/blob/main/src/vec/is/sf/tests/ex3.c#L93-151</a><br>
</blockquote>
</div>
</div>
</body>
</html>