Re: Reproducibility terminology/definitions

2023-11-11 Thread Bernhard M. Wiedemann via rb-general
On 08/11/2023 16.38, Pol Dellaiera wrote: you define functions doing I/O as Impure functions. But without I/O, no build output can be written, so all builds must use impure functions. In practice we see non-determinism from approx 10 sources, such as documented in

Re: Reproducibility terminology/definitions

2023-11-09 Thread Richard Purdie
On Thu, 2023-11-09 at 22:12 +0100, kpcyrd wrote: > > - $E$, the set of all possible software environment > > I'm not aware of any project having this in scope. It's crucial for > projects to document their build environment (see buildinfo files) and > matching it when reproducing the build. If

Re: Reproducibility terminology/definitions

2023-11-09 Thread kpcyrd
On 11/9/23 11:13, Pol Dellaiera wrote: The document includes a dedicated section that attempts to formalize the concepts of 'computation' and 'reproducibility'. I've taken the liberty of synthesizing our formalism discussions into an online document, which is now available at:

Re: Reproducibility terminology/definitions

2023-11-09 Thread Pol Dellaiera
Thanks John, I will read all of this carefully. In the meantime, and based on all the input I gathered, I have begun drafting a document which is now available at: https://typst.app/project/rhUl4XwrXToXvxjoaWB6DI The idea is to have a more formal approach of the definitions. Let me know

Re: Reproducibility terminology/definitions

2023-11-09 Thread Pol Dellaiera
Thanks Ed, Based on all the input I gathered, I have begun drafting a document which is now available at: https://typst.app/project/rhUl4XwrXToXvxjoaWB6DI Let me know what you think, feel free to made all your comments. On 11/9/23 02:02, Ed Warnicke wrote: Pol, Formal definitions can be

Re: Reproducibility terminology/definitions

2023-11-09 Thread Janneke Nieuwenhuizen
Pol Dellaiera writes: > Upon reflection, I realize that my initial email may not have fully > conveyed my objective. My intent is to lay the groundwork for a > rigorous, formal definition of reproducibility in C.S. One thing that the official definition

Re: Reproducibility terminology/definitions

2023-11-09 Thread Pol Dellaiera
Dear Holger, Upon reflection, I realize that my initial email may not have fully conveyed my objective. My intent is to lay the groundwork for a rigorous, formal definition of reproducibility in C.S. To this end, I have begun drafting a document that delves into the nuances of

Re: Reproducibility terminology/definitions

2023-11-08 Thread Ed Warnicke
Pol, Formal definitions can be quite helpful. I suspect your ambitions greatly exceed my thoughts on the subject, but I thought I might share how I think about it in the hopes it might prove of some assistance. A build is reproducible if an equivalent set of inputs into the build results in an

Re: Reproducibility terminology/definitions

2023-11-08 Thread John Gilmore
Pol Dellaiera wrote: > To that end, I'm currently drafting a formal definition of > reproducibility that I hope to contribute. However, before I proceed > further, I would like to know whether any of you have already worked > on formulating such a definition. Here are a few emails (from prior

Re: Reproducibility terminology/definitions

2023-11-08 Thread Holger Levsen
Hi Pol, On Wed, Nov 08, 2023 at 04:38:19PM +0100, Pol Dellaiera wrote: > I'm writing to express my enthusiasm for the discussions and initiatives that > took place during the meeting in Hamburg. Although I was regrettably unable > to attend, I have been closely following the outcomes and I'm

Reproducibility terminology/definitions

2023-11-08 Thread Pol Dellaiera
Dear friends, colleagues, I'm writing to express my enthusiasm for the discussions and initiatives that took place during the meeting in Hamburg. Although I was regrettably unable to attend, I have been closely following the outcomes and I'm particularly interested in the effort to enhance