unofficial mirror of guix-science@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Giovanni Biscuolo <giovanni@biscuolo.net>
Cc: guix-science@gnu.org
Subject: Re: A guide to reproducible research papers
Date: Thu, 29 Jun 2023 12:54:15 +0200	[thread overview]
Message-ID: <87o7kyr12g.fsf@inria.fr> (raw)
In-Reply-To: <87h6qqo8ot.fsf@xelera.eu> (Giovanni Biscuolo's message of "Thu,  29 Jun 2023 12:37:54 +0200")

Ciao Giovanni,

Giovanni Biscuolo <giovanni@biscuolo.net> skribis:

> You mentioned this citation from Jon Claerbout:
>
>  Published documents are merely the advertisement of scholarship whereas
>  the computer programs, input data, parameter values, etc. embody the
>  scholarship itself.
>
> and I was very curious about the source: I found that's a citation from
> the abstract of «Making scientc computations reproducible» (Matthias
> Schwab , Martin Karrenbach, Jon Claerbout, Published 2000) [1]

Right, I found this one but couldn’t find precisely the original source
(I spent quite a while looking for it and eventually gave up).

> Nevertheless, the first occurrence of a similar statement by Jon
> Claerbout is in a talk named «Seventeen years of super computing and
> other problems in seismology» dated Oct 2 1994, precisely in the section
> about "Technology transfer and research reproducibility" [2]
>
>
> In engineering, a published paper is an advertisement of scholarship but
> the electronic document can be the scholarship itself. Forty years ago
> data were "pencil marks on paper" and theory was some Greek
> symbols. Then paper documents were adequate. No more. Now we need
> electronic documents.
>
> Just to add a little bit of history of computational reproducibility of
> research.

[...]

> [2] https://sepwww.stanford.edu/sep/jon/nrc.html#Technology%20transfer%20and%20research%20reproducibility

Excellent, thank you for sharing!

The takeaway here is that there’s nothing new: we’re probably going
further in implementing these ideas and adapting them to current
practices, but the core issue was already well documented 25+ years ago.

Ludo’.


      reply	other threads:[~2023-06-29 10:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23  9:49 A guide to reproducible research papers Ludovic Courtès
2023-06-29 10:37 ` Giovanni Biscuolo
2023-06-29 10:54   ` Ludovic Courtès [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o7kyr12g.fsf@inria.fr \
    --to=ludovic.courtes@inria.fr \
    --cc=giovanni@biscuolo.net \
    --cc=guix-science@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).