public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: "M. Edward (Ed) Borasky" <znmeb@cesmail.net>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] Re: New category proposal - sci-vis
Date: Sun, 27 Nov 2005 17:01:19 -0800	[thread overview]
Message-ID: <438A56DF.3030904@cesmail.net> (raw)
In-Reply-To: <438A49AE.6020203@gentoo.org>

Donnie Berkholz wrote:

> Macromolecular graphics tools I really consider biochemistry, so they
> can go either way. But I more often hear biochemistry elongated as
> biological chemistry than chemical biology. So if forced to categorize
> one or the other, I lean toward chemistry.

It all depends on the size of the molecules and the amount of 
specialization of the researchers, I think. We could go to the extreme 
of a category for each package if we were perverse enough. :)

I'm just starting to explore the Bioconductor Project 
(http://www.bioconductor.org). When all is said and done, Bioconductor, 
though it's primarly a collection of R code for cancer and genetics 
research, is really applied math and computer science. For example, I'm 
using some of the routines in Bioconductor for computer performance 
engineering.

Of course, my father was a biochemist and the correspondences between 
computer science, computational biochemistry and genetics were not lost 
on me. In short, my vote is for biology or biocomputing or 
bioinformatics rather than biochemistry or chemistry.

Just on the off chance some of you are interested in the heavy stuff, 
the good folks in Seattle at the Fred Hutchinson Cancer Research Center 
are having an advanced R programming class in January. I've already 
spoken to the organizers and they've assured me that the course is more 
about R than bioinformatics and that computer scientists like myself are 
welcome. If I go I will be bringing a Gentoo laptop, of course. :) For 
more details, visit  https://cobra.fhcrc.org/rforbioc/

-- 
M. Edward (Ed) Borasky

http://linuxcapacityplanning.com

-- 
gentoo-science@gentoo.org mailing list



  reply	other threads:[~2005-11-28  1:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-27 20:53 [gentoo-science] New category proposal - sci-vis Marcus D. Hanwell
2005-11-27 21:40 ` Olivier Fisette
2005-11-27 21:51 ` Holger Peters
2005-11-27 22:05   ` Marcus D. Hanwell
2005-11-27 22:11 ` [gentoo-science] " George Shapovalov
2005-11-27 23:05   ` Marcus D. Hanwell
2005-11-28  0:12     ` Donnie Berkholz
2005-11-27 22:47 ` Markus Dittrich
2005-11-27 23:00   ` Marcus D. Hanwell
2005-11-28  0:05   ` Donnie Berkholz
2005-11-28  1:01     ` M. Edward (Ed) Borasky [this message]
2005-11-28  5:36     ` Markus Dittrich
2005-11-28  5:40       ` Donnie Berkholz
2005-11-28  0:43 ` [gentoo-science] " M. Edward (Ed) Borasky
2006-01-29 21:16   ` Marcus D. Hanwell
2006-01-29 22:15     ` Donnie Berkholz
2006-01-29 22:23       ` Marcus D. Hanwell
2006-01-29 22:41         ` M. Edward (Ed) Borasky
2006-01-30  2:29       ` Markus Dittrich
2006-01-30  6:35         ` M. Edward (Ed) Borasky
2006-01-30  8:38           ` Marcus D. Hanwell
2006-01-30 14:51             ` M. Edward (Ed) Borasky
2006-01-30 21:21         ` Olivier Fisette
2006-01-30 22:26           ` Markus Dittrich
2006-01-29 22:53     ` jak
2006-01-30  8:59       ` Marcus D. Hanwell

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=438A56DF.3030904@cesmail.net \
    --to=znmeb@cesmail.net \
    --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