[petsc-users] reproducibility

[Mark Adams]

Same SHA1 (?):

13:18 adams/cusparse-cpu-solve=
/gpfs/alpine/csc314/scratch/adams/petsc/src/ts/utils/dmplexlandau/tutorials/tput$
git log -1
commit 4bf14ff56aaf20873dd75467a8e4c029914a4549
Author: Mark Adams <mfadams at lbl.gov>
Date:   Sat May 15 12:22:00 2021 -0700

    turn cpu solve back on



commit 4bf14ff56aaf20873dd75467a8e4c029914a4549 (HEAD ->
adams/cusparse-cpu-solve, origin/adams/cusparse-cpu-solve)
Author: Mark Adams <mfadams at lbl.gov>
Date:   Sat May 15 12:22:00 2021 -0700

    turn cpu solve back on
lines 1-5/5 (END)

On Mon, Jun 14, 2021 at 12:55 PM Matthew Knepley <knepley at gmail.com> wrote:

> On Mon, Jun 14, 2021 at 12:38 PM Mark Adams <mfadams at lbl.gov> wrote:
>
>> I am working on reproducibility for SC and I have two machines that are
>> using the same branch that is up-to-date as far as I can tell but they seem
>> to have different SHA1:
>>
>> out10_1_1_Cuda_CPU.txt:Using Petsc Development GIT revision:
>> v3.15.0-792-gacb395f  GIT Date: 2021-06-13 22:56:54 +0000
>>
>>
>> out11_1_1_Cuda_CPU.txt:Using Petsc Development GIT revision:
>> v3.15.0-794-g4bf14ff56a  GIT Date: 2021-06-14 07:47:59 -0400
>>
>> Does this look right?
>>
>
> They definitely look like they are on different change sets. Can you do
>
>   git log -1
>
>   Thanks,
>
>     Matt
>
>
>> Thanks,
>> Mark
>>
>>
>
> --
> What most experimenters take for granted before they begin their
> experiments is infinitely more interesting than any results to which their
> experiments lead.
> -- Norbert Wiener
>
> https://www.cse.buffalo.edu/~knepley/
> <http://www.cse.buffalo.edu/~knepley/>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20210614/e069e258/attachment.html>