home.social

#maneage — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #maneage, aggregated by home.social.

  1. The #Maneage #reproducibility system for scientific research papers that starts from a minimal POSIX-like host OS does not yet build [1] the #GNUCLibrary = #GLibC . We have a draft implementation building glibc *after* #GCC [2]; and an alternative proposal arguing that building glibc *first* and gcc second would be more long-term sustainable [[1] comment18].

    Should GLibC be built first? Why (or why not)?

    [1] savannah.nongnu.org/task/?1539
    [2] gitlab.com/maneage/project-dev

  2. The #Maneage #reproducibility system for scientific research papers that starts from a minimal POSIX-like host OS does not yet build [1] the #GNUCLibrary = #GLibC . We have a draft implementation building glibc *after* #GCC [2]; and an alternative proposal arguing that building glibc *first* and gcc second would be more long-term sustainable [[1] comment18].

    Should GLibC be built first? Why (or why not)?

    [1] savannah.nongnu.org/task/?1539
    [2] gitlab.com/maneage/project-dev

  3. The #Maneage #reproducibility system for scientific research papers that starts from a minimal POSIX-like host OS does not yet build [1] the #GNUCLibrary = #GLibC . We have a draft implementation building glibc *after* #GCC [2]; and an alternative proposal arguing that building glibc *first* and gcc second would be more long-term sustainable [[1] comment18].

    Should GLibC be built first? Why (or why not)?

    [1] savannah.nongnu.org/task/?1539
    [2] gitlab.com/maneage/project-dev

  4. The #Maneage #reproducibility system for scientific research papers that starts from a minimal POSIX-like host OS does not yet build [1] the #GNUCLibrary = #GLibC . We have a draft implementation building glibc *after* #GCC [2]; and an alternative proposal arguing that building glibc *first* and gcc second would be more long-term sustainable [[1] comment18].

    Should GLibC be built first? Why (or why not)?

    [1] savannah.nongnu.org/task/?1539
    [2] gitlab.com/maneage/project-dev

  5. The #Maneage #reproducibility system for scientific research papers that starts from a minimal POSIX-like host OS does not yet build [1] the #GNUCLibrary = #GLibC . We have a draft implementation building glibc *after* #GCC [2]; and an alternative proposal arguing that building glibc *first* and gcc second would be more long-term sustainable [[1] comment18].

    Should GLibC be built first? Why (or why not)?

    [1] savannah.nongnu.org/task/?1539
    [2] gitlab.com/maneage/project-dev

  6. Is a peer-reviewed #Maneage paper [1] (software + full results) reproducible from scratch?

    Same author+machine; OS Debian stable updated 2021...2025.

    Reproduction to final pdf by merge to current maneage 'software/' +minor hacks +disable a few verifications [2].

    Result: final pdf has small but scientifically negligible diffs [3]; (due to python/numpy int or float changes?).

    #Reproducibility

    [1] peerj.com/articles/11856
    [2] codeberg.org/boud/subpoisson/s commit f554c7e9
    [3] codeberg.org/boud/subpoisson/c

  7. Is a peer-reviewed #Maneage paper [1] (software + full results) reproducible from scratch?

    Same author+machine; OS Debian stable updated 2021...2025.

    Reproduction to final pdf by merge to current maneage 'software/' +minor hacks +disable a few verifications [2].

    Result: final pdf has small but scientifically negligible diffs [3]; (due to python/numpy int or float changes?).

    #Reproducibility

    [1] peerj.com/articles/11856
    [2] codeberg.org/boud/subpoisson/s commit f554c7e9
    [3] codeberg.org/boud/subpoisson/c

  8. Is a peer-reviewed #Maneage paper [1] (software + full results) reproducible from scratch?

    Same author+machine; OS Debian stable updated 2021...2025.

    Reproduction to final pdf by merge to current maneage 'software/' +minor hacks +disable a few verifications [2].

    Result: final pdf has small but scientifically negligible diffs [3]; (due to python/numpy int or float changes?).

    #Reproducibility

    [1] peerj.com/articles/11856
    [2] codeberg.org/boud/subpoisson/s commit f554c7e9
    [3] codeberg.org/boud/subpoisson/c

  9. Is a peer-reviewed #Maneage paper [1] (software + full results) reproducible from scratch?

    Same author+machine; OS Debian stable updated 2021...2025.

    Reproduction to final pdf by merge to current maneage 'software/' +minor hacks +disable a few verifications [2].

    Result: final pdf has small but scientifically negligible diffs [3]; (due to python/numpy int or float changes?).

    #Reproducibility

    [1] peerj.com/articles/11856
    [2] codeberg.org/boud/subpoisson/s commit f554c7e9
    [3] codeberg.org/boud/subpoisson/c

  10. Is a peer-reviewed #Maneage paper [1] (software + full results) reproducible from scratch?

    Same author+machine; OS Debian stable updated 2021...2025.

    Reproduction to final pdf by merge to current maneage 'software/' +minor hacks +disable a few verifications [2].

    Result: final pdf has small but scientifically negligible diffs [3]; (due to python/numpy int or float changes?).

    #Reproducibility

    [1] peerj.com/articles/11856
    [2] codeberg.org/boud/subpoisson/s commit f554c7e9
    [3] codeberg.org/boud/subpoisson/c

  11. @leibnizopenscience

    The paper seems to have missed a powerful workflow language: #Make [1], with #GNUMake [2] being the canonical example. It's stable and nearly half a century old. Learn and use it now and your scientific grandchildren will be able to reproduce your workflow in 2075 [3]. #Maneage [3][4] uses Make for *both* reproducible software + reproducible workflows.

    [1] en.wikipedia.org/wiki/Make_%28

    [2] gnu.org/software/make

    [3] maneage.org

    [4] doi.org/10.1109/MCSE.2021.3072

  12. @leibnizopenscience

    The paper seems to have missed a powerful workflow language: #Make [1], with #GNUMake [2] being the canonical example. It's stable and nearly half a century old. Learn and use it now and your scientific grandchildren will be able to reproduce your workflow in 2075 [3]. #Maneage [3][4] uses Make for *both* reproducible software + reproducible workflows.

    [1] en.wikipedia.org/wiki/Make_%28

    [2] gnu.org/software/make

    [3] maneage.org

    [4] doi.org/10.1109/MCSE.2021.3072

  13. @leibnizopenscience

    The paper seems to have missed a powerful workflow language: #Make [1], with #GNUMake [2] being the canonical example. It's stable and nearly half a century old. Learn and use it now and your scientific grandchildren will be able to reproduce your workflow in 2075 [3]. #Maneage [3][4] uses Make for *both* reproducible software + reproducible workflows.

    [1] en.wikipedia.org/wiki/Make_%28

    [2] gnu.org/software/make

    [3] maneage.org

    [4] doi.org/10.1109/MCSE.2021.3072

  14. @leibnizopenscience

    The paper seems to have missed a powerful workflow language: #Make [1], with #GNUMake [2] being the canonical example. It's stable and nearly half a century old. Learn and use it now and your scientific grandchildren will be able to reproduce your workflow in 2075 [3]. #Maneage [3][4] uses Make for *both* reproducible software + reproducible workflows.

    [1] en.wikipedia.org/wiki/Make_%28

    [2] gnu.org/software/make

    [3] maneage.org

    [4] doi.org/10.1109/MCSE.2021.3072

  15. @leibnizopenscience

    The paper seems to have missed a powerful workflow language: #Make [1], with #GNUMake [2] being the canonical example. It's stable and nearly half a century old. Learn and use it now and your scientific grandchildren will be able to reproduce your workflow in 2075 [3]. #Maneage [3][4] uses Make for *both* reproducible software + reproducible workflows.

    [1] en.wikipedia.org/wiki/Make_%28

    [2] gnu.org/software/make

    [3] maneage.org

    [4] doi.org/10.1109/MCSE.2021.3072

  16. An official PhD course in #ReproducibleResearchPapers will start next week [1]. Unofficial participation is welcome in the #ManeageCommunity room [2] (curated homeservers [3]), where much of the practical sessions will take place (days/times TBD). The focus is on #ReproducibleAstronomy, but #Maneage is (in principle) usable in any field of science.

    @academicchatter #OpenScience #Reproducibility #Astronomy

    [1] usosweb.umk.pl/kontroler.php?_

    [2] matrix.to/#/#maneage_community

    [3] servers.joinmatrix.org

  17. @Pol

    FOSS is criterion 8 of the eight #Maneage criteria for long-term archivable reproducibility [1][2].

    Proprietary software is not reproducible because it "typically cannot be distributed, inspected, or modified by others. [It is], thus, reliant on a single supplier (even without payments) and prone to proprietary obsolescence. [f]"

    @zimoun

    [1] maneage.org

    [2] doi.org/10.1109/MCSE.2021.3072 = arxiv.org/abs/2006.03018 = zenodo.org/records/6533902

    [f] gnu.org/proprietary/proprietar

  18. @Pol

    FOSS is criterion 8 of the eight #Maneage criteria for long-term archivable reproducibility [1][2].

    Proprietary software is not reproducible because it "typically cannot be distributed, inspected, or modified by others. [It is], thus, reliant on a single supplier (even without payments) and prone to proprietary obsolescence. [f]"

    @zimoun

    [1] maneage.org

    [2] doi.org/10.1109/MCSE.2021.3072 = arxiv.org/abs/2006.03018 = zenodo.org/records/6533902

    [f] gnu.org/proprietary/proprietar

  19. @Pol

    FOSS is criterion 8 of the eight #Maneage criteria for long-term archivable reproducibility [1][2].

    Proprietary software is not reproducible because it "typically cannot be distributed, inspected, or modified by others. [It is], thus, reliant on a single supplier (even without payments) and prone to proprietary obsolescence. [f]"

    @zimoun

    [1] maneage.org

    [2] doi.org/10.1109/MCSE.2021.3072 = arxiv.org/abs/2006.03018 = zenodo.org/records/6533902

    [f] gnu.org/proprietary/proprietar

  20. @Pol

    FOSS is criterion 8 of the eight #Maneage criteria for long-term archivable reproducibility [1][2].

    Proprietary software is not reproducible because it "typically cannot be distributed, inspected, or modified by others. [It is], thus, reliant on a single supplier (even without payments) and prone to proprietary obsolescence. [f]"

    @zimoun

    [1] maneage.org

    [2] doi.org/10.1109/MCSE.2021.3072 = arxiv.org/abs/2006.03018 = zenodo.org/records/6533902

    [f] gnu.org/proprietary/proprietar

  21. @Pol

    FOSS is criterion 8 of the eight #Maneage criteria for long-term archivable reproducibility [1][2].

    Proprietary software is not reproducible because it "typically cannot be distributed, inspected, or modified by others. [It is], thus, reliant on a single supplier (even without payments) and prone to proprietary obsolescence. [f]"

    @zimoun

    [1] maneage.org

    [2] doi.org/10.1109/MCSE.2021.3072 = arxiv.org/abs/2006.03018 = zenodo.org/records/6533902

    [f] gnu.org/proprietary/proprietar

  22. Can #cosmology research papers satisfy all 8 #Maneage reproducibility criteria?

    At least 3 cosmology papers have been published using the #Maneage shell/make template.

    All welcome in my online+f2f seminar (BBB) [1] tomorrow (CET) at 10:15 UTC = 11:15 CET Monday 11 March 2024.

    * pdf [2]
    * Matrix [3]

    #OpenScience #Reproducibility
    @cosmology

    [1] astro.umk.pl/en/institute/gene - vc.umk.pl/b/mar-byg-8yu-z15

    [2] cosmo.torun.pl/~boud/Roukema20

    [3] matrix.to/#/#maneage_community

  23. Can #cosmology research papers satisfy all 8 #Maneage reproducibility criteria?

    At least 3 cosmology papers have been published using the #Maneage shell/make template.

    All welcome in my online+f2f seminar (BBB) [1] tomorrow (CET) at 10:15 UTC = 11:15 CET Monday 11 March 2024.

    * pdf [2]
    * Matrix [3]

    #OpenScience #Reproducibility
    @cosmology

    [1] astro.umk.pl/en/institute/gene - vc.umk.pl/b/mar-byg-8yu-z15

    [2] cosmo.torun.pl/~boud/Roukema20

    [3] matrix.to/#/#maneage_community

  24. Can #cosmology research papers satisfy all 8 #Maneage reproducibility criteria?

    At least 3 cosmology papers have been published using the #Maneage shell/make template.

    All welcome in my online+f2f seminar (BBB) [1] tomorrow (CET) at 10:15 UTC = 11:15 CET Monday 11 March 2024.

    * pdf [2]
    * Matrix [3]

    #OpenScience #Reproducibility
    @cosmology

    [1] astro.umk.pl/en/institute/gene - vc.umk.pl/b/mar-byg-8yu-z15

    [2] cosmo.torun.pl/~boud/Roukema20

    [3] matrix.to/#/#maneage_community

  25. Can #cosmology research papers satisfy all 8 #Maneage reproducibility criteria?

    At least 3 cosmology papers have been published using the #Maneage shell/make template.

    All welcome in my online+f2f seminar (BBB) [1] tomorrow (CET) at 10:15 UTC = 11:15 CET Monday 11 March 2024.

    * pdf [2]
    * Matrix [3]

    #OpenScience #Reproducibility
    @cosmology

    [1] astro.umk.pl/en/institute/gene - vc.umk.pl/b/mar-byg-8yu-z15

    [2] cosmo.torun.pl/~boud/Roukema20

    [3] matrix.to/#/#maneage_community

  26. Can #cosmology research papers satisfy all 8 #Maneage reproducibility criteria?

    At least 3 cosmology papers have been published using the #Maneage shell/make template.

    All welcome in my online+f2f seminar (BBB) [1] tomorrow (CET) at 10:15 UTC = 11:15 CET Monday 11 March 2024.

    * pdf [2]
    * Matrix [3]

    #OpenScience #Reproducibility
    @cosmology

    [1] astro.umk.pl/en/institute/gene - vc.umk.pl/b/mar-byg-8yu-z15

    [2] cosmo.torun.pl/~boud/Roukema20

    [3] matrix.to/#/#maneage_community

  27. @ethanwhite @tpoisot

    In #Maneage [1], level 4+ is different:

    * in analysis/ we use 'make' for the higher-level workflow, encouraging bash scripts for details;

    * in software/ we use 'make' to build all the software with sha512sum checks on the downloads, starting from a minimal unix-like system;

    * the makefiles initialize.mk and paper.mk are the workflow for the paper

    Fully reproduce:
    ./project configure
    ./project make

    Example: [2]

    [1] maneage.org
    [2] zenodo.org/record/7792910

  28. @ethanwhite @tpoisot

    In #Maneage [1], level 4+ is different:

    * in analysis/ we use 'make' for the higher-level workflow, encouraging bash scripts for details;

    * in software/ we use 'make' to build all the software with sha512sum checks on the downloads, starting from a minimal unix-like system;

    * the makefiles initialize.mk and paper.mk are the workflow for the paper

    Fully reproduce:
    ./project configure
    ./project make

    Example: [2]

    [1] maneage.org
    [2] zenodo.org/record/7792910

  29. @ethanwhite @tpoisot

    In #Maneage [1], level 4+ is different:

    * in analysis/ we use 'make' for the higher-level workflow, encouraging bash scripts for details;

    * in software/ we use 'make' to build all the software with sha512sum checks on the downloads, starting from a minimal unix-like system;

    * the makefiles initialize.mk and paper.mk are the workflow for the paper

    Fully reproduce:
    ./project configure
    ./project make

    Example: [2]

    [1] maneage.org
    [2] zenodo.org/record/7792910

  30. @ethanwhite @tpoisot

    In #Maneage [1], level 4+ is different:

    * in analysis/ we use 'make' for the higher-level workflow, encouraging bash scripts for details;

    * in software/ we use 'make' to build all the software with sha512sum checks on the downloads, starting from a minimal unix-like system;

    * the makefiles initialize.mk and paper.mk are the workflow for the paper

    Fully reproduce:
    ./project configure
    ./project make

    Example: [2]

    [1] maneage.org
    [2] zenodo.org/record/7792910

  31. @ethanwhite @tpoisot

    In #Maneage [1], level 4+ is different:

    * in analysis/ we use 'make' for the higher-level workflow, encouraging bash scripts for details;

    * in software/ we use 'make' to build all the software with sha512sum checks on the downloads, starting from a minimal unix-like system;

    * the makefiles initialize.mk and paper.mk are the workflow for the paper

    Fully reproduce:
    ./project configure
    ./project make

    Example: [2]

    [1] maneage.org
    [2] zenodo.org/record/7792910

  32. @civodul @khinsen

    We use #CosmicVoids in [1][2], which in N-body sims are traced by low num-densities of particles => high noise. Full #Maneage controls + fixed seed rng's. We still have intramachine + (higher) intermachine randomness. Statistical upper limits to results OK. But still untraced sources of randomness.

    Any clues for remaining randomness [2]?

    #Reproducibility #ArXiv_2304_00591 #OpenScience

    [1] Frozen record: zenodo.org/record/7792910

    [2] Live git: codeberg.org/mpeper/lensing

  33. @civodul @khinsen

    We use #CosmicVoids in [1][2], which in N-body sims are traced by low num-densities of particles => high noise. Full #Maneage controls + fixed seed rng's. We still have intramachine + (higher) intermachine randomness. Statistical upper limits to results OK. But still untraced sources of randomness.

    Any clues for remaining randomness [2]?

    #Reproducibility #ArXiv_2304_00591 #OpenScience

    [1] Frozen record: zenodo.org/record/7792910

    [2] Live git: codeberg.org/mpeper/lensing

  34. @civodul @khinsen

    We use #CosmicVoids in [1][2], which in N-body sims are traced by low num-densities of particles => high noise. Full #Maneage controls + fixed seed rng's. We still have intramachine + (higher) intermachine randomness. Statistical upper limits to results OK. But still untraced sources of randomness.

    Any clues for remaining randomness [2]?

    #Reproducibility #ArXiv_2304_00591 #OpenScience

    [1] Frozen record: zenodo.org/record/7792910

    [2] Live git: codeberg.org/mpeper/lensing

  35. @civodul @khinsen

    We use #CosmicVoids in [1][2], which in N-body sims are traced by low num-densities of particles => high noise. Full #Maneage controls + fixed seed rng's. We still have intramachine + (higher) intermachine randomness. Statistical upper limits to results OK. But still untraced sources of randomness.

    Any clues for remaining randomness [2]?

    #Reproducibility #ArXiv_2304_00591 #OpenScience

    [1] Frozen record: zenodo.org/record/7792910

    [2] Live git: codeberg.org/mpeper/lensing

  36. @civodul @khinsen

    We use #CosmicVoids in [1][2], which in N-body sims are traced by low num-densities of particles => high noise. Full #Maneage controls + fixed seed rng's. We still have intramachine + (higher) intermachine randomness. Statistical upper limits to results OK. But still untraced sources of randomness.

    Any clues for remaining randomness [2]?

    #Reproducibility #ArXiv_2304_00591 #OpenScience

    [1] Frozen record: zenodo.org/record/7792910

    [2] Live git: codeberg.org/mpeper/lensing