From: Markus Dittrich <markusle@gentoo.org>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] elektronic lab book
Date: Sun, 17 Sep 2006 14:25:38 +0000 (UTC) [thread overview]
Message-ID: <Pine.LNX.4.64.0609171421010.12560@woodpecker.gentoo.org> (raw)
In-Reply-To: <200609170009.57880.ribosome@gentoo.org>
On Sun, 17 Sep 2006, Olivier Fisette wrote:
> On Saturday, 16 September 2006 10:38, Norman Warthmann wrote:
>> I am having my eyes open for an electronic way of keeping a lab book
>> for my experiments for quite some time now, however to my surprise,
>> it seems there is none open source. I am wondering how people in the
>> science herd are organizing their day by day experiments.
>
> Hi Norman,
>
> There are open source ELN and LIMS such as OpenSourceELN
> (www.opensourceeln.org) and HalX (Prilusky et al. 2005,
> halx.genomics.eu.org), but I personally prefer to use text files,
> directories, vim and a few shell scripts to keep track of my day-to-day work.
> I never felt the need for anything more complex. ;)
>
> Cheers,
>
Same here! I mostly use README files combined with a suitable
directory structure in addition to a good old paper lab
notebook. I also use cvs/subversion to keep track of changes
to scripts, analysis routines, data files, and for paper writing.
The only decent and usable electronic notebook I've seen
is notetaker, which, unfortunately, is only available on OS X.
http://www.aquaminds.com/
best,
Markus
--
Markus Dittrich (markusle)
Gentoo Linux Developer
Scientific applications
--
gentoo-science@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-17 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-16 14:38 [gentoo-science] elektronic lab book Norman Warthmann
2006-09-17 4:09 ` Olivier Fisette
2006-09-17 14:25 ` Markus Dittrich [this message]
2006-09-17 17:39 ` Markus Luisser
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0609171421010.12560@woodpecker.gentoo.org \
--to=markusle@gentoo.org \
--cc=gentoo-science@lists.gentoo.org \
/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