From: Varad Deshmukh <vrd@cs.ucsb.edu>
To: gsl-discuss@sourceware.org
Subject: Contributing to GSL
Date: Wed, 28 Mar 2012 04:11:00 -0000 [thread overview]
Message-ID: <4F728F55.2010404@cs.ucsb.edu> (raw)
Hi,
I am Varad Deshmukh, a Master's student at UCSB majoring in Computer
Science. My research interests are in Scientific Computing and HPC, and
I am interested in contributing to GSL. I recently took up a course in
numerical simulation and I figured a good way to start would be looking
into ODE solvers.
The TODO list mentions work to be done for adding other stepper
methods - especially the BDF methods for DAE's implemented in DASSL and
DASPK. Could you please elaborate more on which new methods you want to
focus on? I have been reading the code for the Runge-Kutta methods - the
driver, evolve and control formats - and have a rough idea about the design.
It would be great if I could get some help regarding GSL development in
general and ode-initval2 in particular. If you feel that I should work
with smaller bugs and fix them before going into a new implementation, I
would like to hear suggestions.
Thank you,
Varad.
next reply other threads:[~2012-03-28 4:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 4:11 Varad Deshmukh [this message]
2012-03-31 7:42 ` Tuomo Keskitalo
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=4F728F55.2010404@cs.ucsb.edu \
--to=vrd@cs.ucsb.edu \
--cc=gsl-discuss@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).