From: Thibault Lestang <t.lestang@imperial.ac.uk>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: guix-science@gnu.org
Subject: Re: Conda environments and reproducibility
Date: Tue, 04 Apr 2023 13:19:20 +0100 [thread overview]
Message-ID: <87y1n7kf6d.fsf@imperial.ac.uk> (raw)
In-Reply-To: <87fs9hf0st.fsf@gmail.com>
Simon Tournier <zimon.toutoune@gmail.com> writes:
> On jeu., 16 mars 2023 at 13:40, Thibault Lestang <t.lestang@imperial.ac.uk> wrote:
>
>> @Simon: Whether I actually do it or not, feel free to add/tweak the
>> pipelines when you're back. You should be able to open a merge request?
>
> I am back. :-)
>
> Nice, you already did it. Well, I will see if instead the simple Numpy
> example, we can also add something using PyTorch – some more complicated
> stack.
That would be helpful, thanks. I'm not very familiar with PyTorch or
Tensorflow and lacking inspiration on what to add to the environment.
Hope you had a good break :)
-- Thibault
next prev parent reply other threads:[~2023-04-04 12:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 17:28 Conda environments and reproducibility Thibault Lestang
2022-11-28 19:45 ` Konrad Hinsen
2022-11-29 10:32 ` Thibault Lestang
2022-11-29 13:12 ` Hugo Buddelmeijer
2022-11-29 13:39 ` Konrad Hinsen
2022-12-01 14:01 ` Hugo Buddelmeijer
2022-12-02 13:01 ` Konrad Hinsen
2022-11-29 20:10 ` Simon Tournier
2022-12-16 10:16 ` Thibault Lestang
2023-03-11 11:05 ` Ludovic Courtès
2023-03-11 11:43 ` Simon Tournier
2023-03-13 10:26 ` Lestang, Thibault
2023-03-13 11:00 ` Ricardo Wurmus
2023-03-13 12:38 ` Simon Tournier
2023-03-16 10:26 ` Ludovic Courtès
2023-03-16 13:40 ` Thibault Lestang
2023-04-03 15:22 ` Simon Tournier
2023-04-04 12:19 ` Thibault Lestang [this message]
2022-12-02 10:52 ` Ludovic Courtès
2022-12-02 11:05 ` Ludovic Courtès
2022-12-02 13:59 ` Simon Tournier
2022-12-02 14:06 ` Hugo Buddelmeijer
2022-11-28 20:46 ` Simon Tournier
2022-11-29 10:41 ` Thibault Lestang
2022-11-29 14:25 ` Simon Tournier
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=87y1n7kf6d.fsf@imperial.ac.uk \
--to=t.lestang@imperial.ac.uk \
--cc=guix-science@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).