Re: software situation

From	Jeff Liebermann <jeffl@cruzio.com>
Newsgroups	sci.electronics.design
Subject	Re: software situation
Date	2026-03-27 16:04 -0700
Message-ID	<ql2esktl2p5b5al5ftghuvrl3526ifvmun@4ax.com> (permalink)
References	<hssask1jni4460b638qcdm4bumb47jvbc4@4ax.com> <18a098629788bab0$85$2674190$4286dcd3@news.newsgroupdirect.com> <jt4dsk560hvavrmtev516762u5elod5ion@4ax.com>

Show all headers | View raw

On Fri, 27 Mar 2026 07:41:26 -0700, Jeff Liebermann <jeffl@cruzio.com>
wrote:

>ECMMWF forecasts have been available online for about 4 years.
><https://www.ecmwf.int/en/forecasts>

Oops.  The ECMWF was founded in 1975.  I believe that forecasts were
widely distributed starting in about 1992.  

Key Historical Milestones

1971-1975: Conceptualization and signing of the ECMWF Convention to
pool European scientific resources.

Nov 1, 1975: The Convention formally comes into force, establishing
the Centre.

1979: First real-time operational medium-range forecasts produced.

1992: Launch of operational ensemble forecasting (EPS) to predict
weather uncertainty.

2005-2010: Convention amended to allow new Member States to join.

2020s: Post-Brexit, operations shifted to include Bonn, Germany, and
the headquarters initiated plans to move to the University of
Reading's Whiteknights Park campus.

2025: Celebrated 50 years of operation and advancements in AI-based
forecasting.

-- 
Jeff Liebermann                 jeffl@cruzio.com
PO Box 272      http://www.LearnByDestroying.com
Ben Lomond CA 95005-0272   AE6KS    831-336-2558

Back to sci.electronics.design | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

software situation john larkin <jl@glen--canyon.com> - 2026-03-26 10:58 -0700
  Re: software situation Sergey Kubushyn <ksi@koi8.net> - 2026-03-26 20:29 +0000
    Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-26 17:51 -0700
      Re: software situation Sergey Kubushyn <ksi@koi8.net> - 2026-03-27 02:03 +0000
        Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-26 21:41 -0700
          Re: software situation Sergey Kubushyn <ksi@koi8.net> - 2026-03-27 06:09 +0000
            Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-27 04:15 -0700
          Re: software situation Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-03-27 10:07 +0000
            Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-27 05:37 -0700
              Re: software situation Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-03-27 18:24 +0000
                Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-27 12:04 -0700
                Re: software situation Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-03-27 22:35 +0000
                Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-27 15:58 -0700
                Re: software situation Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-03-29 09:24 +0000
        Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-27 10:00 -0700
          Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-27 10:17 -0700
            Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-27 10:32 -0700
              Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-27 11:22 -0700
              Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-27 11:34 -0700
                Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-28 06:41 -0700
                Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-28 13:56 -0700
                Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-29 05:53 -0700
                Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-29 12:39 -0700
                Re: software situation john larkin <jl@glen--canyon.com> - 2026-03-29 13:13 -0700
                Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-29 14:29 -0700
                Re: software situation john larkin <jl@glen--canyon.com> - 2026-03-29 15:24 -0700
                Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-29 20:54 -0700
                Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-29 21:07 -0700
                Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-29 21:16 -0700
                Re: software situation john larkin <jl@glen--canyon.com> - 2026-03-30 07:44 -0700
                Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-30 09:02 -0700
                Re: software situation john larkin <jl@glen--canyon.com> - 2026-03-30 16:00 -0700
                Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-29 17:09 -0700
                Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-29 20:48 -0700
              Re: software situation Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-03-27 21:38 +0000
      Re: software situation someone <cffbf4deb9142bce48974efc0e64dede@example.com> - 2026-03-27 04:30 +0000
      Re: software situation Joerg <news@analogconsultants.com> - 2026-03-27 10:35 -0700
        Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-27 11:27 -0700
          Re: software situation Joerg <news@analogconsultants.com> - 2026-03-27 11:46 -0700
            Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-27 14:54 -0700
  Re: software situation someone <cffbf4deb9142bce48974efc0e64dede@example.com> - 2026-03-27 04:30 +0000
    Re: software situation Jeff Liebermann <jeffl@cruzio.com> - 2026-03-27 07:41 -0700
      Re: software situation Jeff Liebermann <jeffl@cruzio.com> - 2026-03-27 16:04 -0700
      Re: software situation someone <cffbf4deb9142bce48974efc0e64dede@example.com> - 2026-03-30 23:30 +0000
        Re: software situation john larkin <jl@glen--canyon.com> - 2026-03-31 11:01 -0700
          Re: software situation Jeff Liebermann <jeffl@cruzio.com> - 2026-03-31 13:54 -0700
            Re: software situation john larkin <jl@glen--canyon.com> - 2026-03-31 15:06 -0700
              Re: software situation Jeff Liebermann <jeffl@cruzio.com> - 2026-03-31 16:14 -0700
                Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-03-31 16:43 -0700
                Re: software situation Jan Panteltje <alien@comet.invalid> - 2026-04-01 06:41 +0000
                Re: software situation john larkin <jl@glen--canyon.com> - 2026-04-01 00:49 -0700
                Re: software situation Jeff Liebermann <jeffl@cruzio.com> - 2026-04-01 17:39 -0700
        Re: software situation Jeff Liebermann <jeffl@cruzio.com> - 2026-03-31 14:15 -0700
          Re: software situation Jan Panteltje <alien@comet.invalid> - 2026-04-01 06:45 +0000
            Re: software situation Jeff Liebermann <jeffl@cruzio.com> - 2026-04-01 09:11 -0700
              Re: software situation Ross Finlayson <ross.a.finlayson@gmail.com> - 2026-04-01 09:43 -0700
              Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-04-01 10:35 -0700
    Re: software situation john larkin <jl@glen--canyon.com> - 2026-03-27 08:16 -0700
      Re: software situation Jeff Liebermann <jeffl@cruzio.com> - 2026-03-27 09:01 -0700
        Re: software situation Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-03-27 17:57 +0000
          Re: software situation Jeff Liebermann <jeffl@cruzio.com> - 2026-03-27 15:06 -0700
            Re: software situation Don Y <blockedofcourse@foo.invalid> - 2026-03-27 15:48 -0700
            Re: software situation Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-03-28 00:44 +0000
      Re: software situation someone <cffbf4deb9142bce48974efc0e64dede@example.com> - 2026-03-30 23:30 +0000
  Re: software situation Jan Panteltje <alien@comet.invalid> - 2026-03-27 08:03 +0000
  Re: software situation someone <cffbf4deb9142bce48974efc0e64dede@example.com> - 2026-03-30 23:30 +0000

csiph-web