Computer Old Farts Forum
 help / color / mirror / Atom feed
Subject: [COFF] How much Fortran?
Date: Mon, 3 Feb 2020 18:36:25 +0000	[thread overview]
Message-ID: <kj34spc9gjqbmgfntk39v9qt@localhost> (raw)
In-Reply-To: <CAEoi9W79Cx9tupSgGBLtdSoNTuDj22+0Dw-Khu6vu48Y7kLn-A@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1373 bytes --]

On 3 Feb 2020 12:06 -0500, from crossd at gmail.com (Dan Cross):
> Regardless, one DOES wonder in what capacity FORTRAN was used in the
> mission. Was it used on the onboard computers, or was it used on the
> downlink stations for e.g. data analysis?

I would be _extremely_ surprised if the Voyager probes themselves run
FORTRAN code.

Maybe, possibly, just barely _might_, they run code that was compiled
from FORTRAN code, but that seems unlikely.

Somewhat less unrealistically, they might run software which was
initially prototyped in FORTRAN, before being translated into
something else. But even that seems a stretch.

Adding up the numbers in [1], the memory capacity of each of the
Voyager probes comes out to a total of 557,248 bits (not bytes), split
between custom-built computers with 16 and 18 bit word lengths.
Wikipedia summarizes it as "Total number of words among the six
computers is about 32K." which seems about right; 557,248/17 ~ 32,779,
and two out of the three computer pairs are said to use 18-bit words.

For ground data processing systems to run code written in FORTRAN does
however seem plausible to me.

 [1] https://en.wikipedia.org/wiki/Voyager_program#Computers_and_data_processing

-- 
Michael Kjörling • https://michael.kjorling.se • michael at kjorling.se
 “Remember when, on the Internet, nobody cared that you were a dog?”



  reply	other threads:[~2020-02-03 18:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03  1:38 krewat
2020-02-03  3:47 ` lm
2020-02-03 15:53   ` clemc
2020-02-03 16:06     ` lm
2020-02-03 16:20       ` clemc
2020-02-03 19:50     ` dave
2020-02-03 17:01   ` thomas.paulsen
2020-02-03  4:50 ` drb
2020-02-03 17:06 ` crossd
2020-02-03 18:36   `  [this message]
2020-02-03 19:26     ` cym224
2020-02-04  1:25     ` wobblygong
2020-02-06  4:59 rudi.j.blom
2020-02-06 20:04 ` dave
2020-02-07 21:09 dave

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=kj34spc9gjqbmgfntk39v9qt@localhost \
    --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).