Could you file a gitlab issue on this?
Offhand, I think it'd be best to modify petscdiff to check the suffix
and then pass it off to exodiff. This would be more easily extended to
other file types (e.g., h5diff).
Scott
On 2021-02-19 04:59, Blaise A Bourdin did write:
> Hi,
>
> I would
Patrick Sanan writes:
> Aside: it's been on the list of good things to do, docs-wise, to be able to
> label parts of the API as more or less stable, so I'm hoping we'll get to
> that (though I think it makes sense to wait until we've finished some of the
> current migrations tasks).
Yes, I
We ended up doing it just as you say - copy the data to the host, use it to
build the IS, and build the scatter. Would be fun to optimize further, maybe,
but as you say that might be premature since there's ongoing work. Happy to get
to play with it a bit, though!
Aside: it's been on the list
ISCUDA isn't even right (perhaps ISGENERALCUDA, ISBLOCKCUDA). I agree that this
isn't a priority, but I could see it being needed in the next few years to
avoid bottlenecks in adaptive mesh refinement or other adaptive algorithms.
It's not a small amount of work, but I think all the index
Even ISCUDA is simple to add, the PetscSFSetUp algorithm and many functions
involved are done on host (and are not simple to be parallelized on GPU)
The indices passed to VecScatter are analyzed and re-grouped. Even they are
copied to device eventually, they are likely not in their original form.
True that it's not a huge efficiency concern, as this only affects the setup
stage. This is more wondering if there's a simpler way to do the setup (sounds
like there isn't at the moment).
> Am 19.02.2021 um 11:41 schrieb Stefano Zampini :
>
> I dont understand the issue. I assume your
I dont understand the issue. I assume your vecscatter is not a throw away
object but you will reuse it many times. Once the setup is done, the
indices used internally by the implementation should be on gpu , or not?
Il Ven 19 Feb 2021, 13:33 Patrick Sanan ha
scritto:
> Thanks! That helps a
Thanks! That helps a lot.
I assume "no," but is ISCUDA simple to add?
More on what I'm trying to do, in case I'm missing an obvious approach:
I'm working on a demo code that uses an external library, based on Kokkos, as a
solver - I create a Vec of type KOKKOS and populate it with the
