Hi Jose,
With pull request #719 we have finished a set of fixes to VECCUDA stuff. With
these changes it is now possible to run many tests in SLEPc's testsuite on GPU
(AIJCUSPARSE+VECCUDA). These tests will be included in the nightly tests from
now on.
great!
However, PETSc nightly tests r
Hi.
With pull request #719 we have finished a set of fixes to VECCUDA stuff. With
these changes it is now possible to run many tests in SLEPc's testsuite on GPU
(AIJCUSPARSE+VECCUDA). These tests will be included in the nightly tests from
now on.
However, PETSc nightly tests related to VECCUDA
We want to support both in a clean way.
> On Jul 26, 2017, at 10:17 AM, Zhang, Hong wrote:
>
>
> > On Jul 26, 2017, at 9:31 AM, Lisandro Dalcin wrote:
> >
> > On 26 July 2017 at 16:34, Stefano Zampini wrote:
> >>
> >> We should come to an agreement on it, as it is used to monitoring a TS
> On Jul 26, 2017, at 9:31 AM, Lisandro Dalcin wrote:
>
> On 26 July 2017 at 16:34, Stefano Zampini wrote:
>>
>> We should come to an agreement on it, as it is used to monitoring a TSSolve
>> call, and to save the trajectory, as per commit
>>
>
> WTF??? Who changed the calls to TSMonitor() t
On Mon, 24 Jul 2017, Karl Rupp wrote:
> Hi folks,
>
> alright, let me summarize and organize things. If you're on the list, please
> provide or update information on 'what left' and 'expected completion':
>
> * SF support for MPIUNI
> - Who: Jed
> - What left: Implementation
> - Expected c
On Jul 26, 2017, at 8:34 AM, Stefano Zampini
mailto:stefano.zamp...@gmail.com>> wrote:
this is regarding ts->total_steps. What is the actual purpose of it?
You claim it is a unique identifier, but actually TSAdjointStep decrements it.
We should come to an agreement on it, as it is used to monit
On 26 July 2017 at 16:34, Stefano Zampini wrote:
>
> We should come to an agreement on it, as it is used to monitoring a TSSolve
> call, and to save the trajectory, as per commit
>
WTF??? Who changed the calls to TSMonitor() to use ts->total_steps ?
What's the rationale? So now I get this output
this is regarding ts->total_steps. What is the actual purpose of it?
You claim it is a unique identifier, but actually TSAdjointStep decrements
it.
We should come to an agreement on it, as it is used to monitoring a TSSolve
call, and to save the trajectory, as per commit
https://bitbucket.org/pet
2017-07-25 22:45 GMT+03:00 Zhang, Hong :
>
>
> >
> > Actually, it is not usable: take for example TSTrajectoryGet() with a
> given step number: then, if I want to use BASIC it will always return the
> last step recorded from the previous TSSolve (this behavior is common to
> all the TSTrajectory i
