From: clemc at ccc.com (Clem Cole)
Subject: [COFF] Fwd: Old and Tradition was [TUHS] V9 shell
Date: Mon, 24 Feb 2020 11:27:38 -0500 [thread overview]
Message-ID: <CAC20D2Pr1K+yz589tNQOWfJQSxfXyhtnKdMpwV8nn_OqpkgrFA@mail.gmail.com> (raw)
In-Reply-To: <20200224151929.GJ30841@mcvoy.com>
On Mon, Feb 24, 2020 at 10:19 AM Larry McVoy <lm at mcvoy.com> wrote:
> On Mon, Feb 24, 2020 at 10:40:10AM +0100, Sijmen J. Mulder wrote:
> > Larry McVoy <lm at mcvoy.com> wrote:
> > > Fortran programmers are formally trained (at least I
> > > was, there was a whole semester devoted to this) in accumulated errors.
> > > You did a deep dive into how to code stuff so that the error was
> reduced
> > > each time instead of increased. It has a lot to do with how floating
> > > point works, it's not exact like integers are.
> >
> > I was unaware that there's formal training to be had around this but
> > it's something I'd like to learn more about. Any recommendations on
> > materials? I don't mind diving into Fortran itself either.
>
> My training was 35 years ago, I have no idea where to go look for this
> stuff now. I googled and didn't find much. I'd go to the local
> University that teaches Fortran and ask around.
>
1. Download the Intel Fortran compiler for your Mac, Linux or Windows
box. This will also give you a number of tuning tools. This compiler can
understand syntax back to FORTRAN-66 through Fortran2018 (and often
without any switches - it can usually figure it out and do the right thing).
2. Get a copy of
https://www.amazon.com/Explained-Numerical-Mathematics-Scientific-Computation/dp/0199601429
3. Go to the physics and chem depts a place start as Larry said
4. Or head to a supercomputer center in the US or EU
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200224/2d1b4b32/attachment.html>
next prev parent reply other threads:[~2020-02-24 16:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 18:41 [COFF] " clemc
[not found] ` <CAP2nic2C4-m_Epcx7rbW2ssbS850ZFiLKiL+hg1Wxbcwoaa1vQ@mail.gmail.com>
2020-02-12 0:57 ` [COFF] Fwd: " athornton
2020-02-12 1:58 ` clemc
2020-02-12 3:01 ` lm
2020-02-12 18:12 ` clemc
2020-02-12 21:55 ` cym224
2020-02-12 22:11 ` imp
2020-02-12 22:45 ` sauer
2020-02-12 23:05 ` lm
2020-02-12 23:54 ` [COFF] floating point (Re: " bakul
2020-02-12 23:56 ` bakul
2020-02-13 1:21 ` toby
2020-02-13 6:57 ` [COFF] Fwd: " peter
2020-02-16 21:47 ` wobblygong
2020-02-16 22:10 ` clemc
2020-02-16 22:45 ` krewat
2020-02-16 23:50 ` bakul
2020-02-18 0:17 ` dave
2020-02-18 12:48 ` jpl.jpl
2020-02-24 9:40 ` ik
2020-02-24 15:19 ` lm
[not found] ` <CAP2nic0fK+=eh=5MuY4BJH6zx4tCRMWcazmm1khYMzNmEdf8ug@mail.gmail.com>
2020-02-24 16:15 ` [COFF] [TUHS] Fwd: Old and Tradition was " clemc
2020-02-24 16:19 ` clemc
2020-02-24 16:27 ` clemc [this message]
2020-02-12 16:28 [COFF] Fwd: Old and Tradition was [TUHS] " jnc
2020-02-12 18:13 ` clemc
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=CAC20D2Pr1K+yz589tNQOWfJQSxfXyhtnKdMpwV8nn_OqpkgrFA@mail.gmail.com \
--to=coff@minnie.tuhs.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 NNTP newsgroup(s).