From: zimoun <zimon.toutoune@gmail.com>
To: simon tournier <simon.tournier@univ-paris-diderot.fr>,
guix-devel@gnu.org, guix-hpc@gnu.org
Subject: Re: Reproducible Research Hackathon: Friday, July 3rd
Date: Fri, 03 Jul 2020 19:10:49 +0200 [thread overview]
Message-ID: <86fta8cyna.fsf@gmail.com> (raw)
In-Reply-To: <web-237942488@univ-paris7.fr>
Dear,
Thank you all for joining!
A PAD is still open at:
https://mensuel.framapad.org/p/guix-hackathon-9hlj?lang=en
Please add whatever you have been up. Or drop an email.
We are interested to hear your feedback. Especially about what pass,
what fail and what you have learnt, if you enjoyed the experience, or on
the contrary if you not, what could be improved for the next round.
Personally, I spent the day with the good ol' Fortran and codes using
the norm 77. And I have enjoyed the flexibility of Guix: navigate
between the versions, running in container, etc.. For example,
guix time-machine -C channels.scm -- build -L . foo
guix time-machine -C channels.scm \
-- environment --container -L . foo --ad-hoc bar@x.y
[env] ./configure --with-bar=xx && make
And Guix helps a lot to expose "hidden" dependencies, i.e., not always
explicitly mentioned in paper's instructions. Well, something that I
learnt is you need some resource at hand, at least download or build the
substitutes in advance.
The "g77" issue [1] is not tackled but some points have been raised, so
maybe soonish. :-)
1: https://github.com/ReScience/submissions/issues/41
On the Guix side, a missing feature is to search back in history, i.e.,
somehow improves [2] (which starts 2019-01-01) and be able to find the
commit (or range of commits) which provided foo@x.y and bar@a.b
2: https://data.guix.gnu.org/repository/1/branch/master/package/boost
Well, thank you all again! And hope to see you again on #guix-hpc. :-)
Cheers,
simon
next prev parent reply other threads:[~2020-07-03 17:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 12:40 Reproducible Research Hackathon: Friday, July 3rd simon tournier
2020-07-01 4:57 ` Pjotr Prins
2020-07-01 9:10 ` zimoun
2020-07-01 9:21 ` Efraim Flashner
2020-07-03 17:10 ` zimoun [this message]
2020-07-03 17:36 ` Ricardo Wurmus
2020-07-03 17:56 ` Paul Garlick
2020-07-03 18:19 ` zimoun
2020-07-07 17:52 ` Paul Garlick
2020-07-03 21:17 ` Ricardo Wurmus
2020-07-07 17:44 ` Paul Garlick
2020-07-04 9:51 ` Konrad Hinsen
2020-07-13 13:41 ` Ludovic Courtès
2020-07-14 8:13 ` Konrad Hinsen
2020-07-14 8:54 ` Bonface M. K.
2020-07-14 19:53 ` Konrad Hinsen
2020-07-14 13:18 ` Ludovic Courtès
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=86fta8cyna.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=guix-hpc@gnu.org \
--cc=simon.tournier@univ-paris-diderot.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).