| 9 Sep 2022 |
|  rhousand joined the room. | 18:41:59 |
| 12 Sep 2022 |
|  Xe (xe/they) changed their profile picture. | 21:40:20 |
| 14 Sep 2022 |
|  search_sense joined the room. | 19:40:45 |
| 15 Sep 2022 |
|  @m_algery:leohoo.xyz joined the room. | 11:45:46 |
| @m_algery:leohoo.xyz left the room. | 11:45:52 |
| 18 Sep 2022 |
|  FRidh set a profile picture. | 17:20:56 |
| 19 Sep 2022 |
|  @benoitj:matrix.org joined the room. | 01:00:25 |
| 22 Sep 2022 |
| rhousand changed their display name from Ryan Housand to rhousand. | 00:15:58 |
|  edi33416 joined the room. | 18:14:35 |
| 24 Sep 2022 |
 raboof | https://r13y.com hasn't been updated in a while - looks like something that needs maintenance on the builtkite machine, but proposing https://github.com/grahamc/r13y.com/pull/36 that possibly would allow the report to be generated even if some paths can't be checked | 10:43:13 |
| raboof | ran the iso-minimal report myself, result at https://arnout.engelen.eu/nixos-iso-minimal-r13y/ . Also added issues to the GitHub issue tracker for those | 10:44:03 |
| raboof | would be neat to have an issue template for r-b issues, proposed https://github.com/NixOS/nixpkgs/pull/192724 | 10:44:35 |
| raboof | and proposed an asciidoc fix ;) - https://github.com/NixOS/nixpkgs/pull/192743 | 10:45:03 |
 @trofi:matrix.org | Is sed \#-e intended in your asciidoc fix? | 10:54:11 |
| raboof | In reply to @trofi:matrix.org
Is sed \#-e intended in your asciidoc fix? oops, definitely not, amended | 11:11:37 |
| 25 Sep 2022 |
| raboof | https://github.com/NixOS/nixpkgs/pull/192860 🤞 | 08:11:16 |
| raboof | https://github.com/NixOS/nixpkgs/pull/192882 | 12:04:28 |
| 26 Sep 2022 |
|  @seapat:matrix.org joined the room. | 22:11:51 |
| 27 Sep 2022 |
|  @profpatsch:augsburg.one changed their display name from profpatsch to Profpatsch. | 13:32:37 |
| 29 Sep 2022 |
|  mathandball joined the room. | 08:13:15 |
|  fzakaria joined the room. | 18:22:07 |
| fzakaria | Workshop on reproducibility
https://ucsc.zoom.us/j/92228537801?pwd=SGNmTHRaNjE3UURsRjNHQzZGektRZz09
Title: Reproducibility in HPCThere is a reproducibility crisis across the scientific research world — studies have shown that the results of many scientific papers cannot be reproduced. In HPC the problem is exacerbated, as each machine is essentially unique. Performance results depend on the CPU, GPU, and system software and hardware configuration. It is seldom the case that we run the exact same configuration of some program twice.Are there solutions that can enable better reproducibility for HPC, or are we looking at the problem the wrong way? Do we care about reproducing a particular build, or a particular conclusion? This panel will explore issues of software and hardware reproducibility in HPC.Our 4 panelists will present some different angles on reproducibility, and we’ll follow this up with some questions and discussion:
| 18:22:25 |
 tpw_rules | is there some sort of talk announcement for this? i joined but just want some context | 19:25:35 |
| fzakaria | last minute -- sorry | 19:26:42 |
| fzakaria | it was : https://ospo.ucsc.edu/post/20220823/ | 19:26:47 |
| fzakaria | or
https://docs.google.com/document/u/1/d/e/2PACX-1vQin8rKcMZhWwi31e2Djbbvgo8uAWexyRixqQHUgEpmeXGn5As465yKhZl8IEpvuBmDfzly9ybxo5w8/pub | 19:27:15 |
| fzakaria | we are on the tail end now | 19:27:33 |
| tpw_rules | ah, you are presenting? | 19:27:51 |
| tpw_rules | i have used nix on hpc before but more just as a curiosity | 19:28:53 |
| tpw_rules | but demonstrating that it's practical to use without administrator collaboration | 19:31:56 |
