From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 2002:a24:7996:: with SMTP id
 z144-v6mr11839427itc.10.1538851800266;
        Sat, 06 Oct 2018 11:50:00 -0700 (PDT)
X-Received: by 2002:aca:ab8b:: with SMTP id
 u133-v6mr265082oie.6.1538851800176;
 Sat, 06 Oct 2018 11:50:00 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!2.eu.feeder.erje.net!4.us.feeder.erje.net!feeder.erje.net!nntp.club.cc.cmu.edu!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!x98-v6no233175ita.0!news-out.google.com!n199-v6ni313itn.0!nntp.google.com!z5-v6no232160ite.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Sat, 6 Oct 2018 11:49:59 -0700 (PDT)
In-Reply-To: <ppamf9$ebu$1@dont-email.me>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=76.18.64.97;
 posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC
NNTP-Posting-Host: 76.18.64.97
References: <3f2828df-d54a-4427-bc3c-dc5ef0dc8069@googlegroups.com>
 <g1oe5gFjk04U1@mid.individual.net>
 <c457fabd-54ab-4294-a268-f3af228b241e@googlegroups.com>
 <g1plu7Frjb1U1@mid.individual.net>
 <13fa128f-5ec7-453e-9231-2260dd4adcbc@googlegroups.com>
 <ppamf9$ebu$1@dont-email.me>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <3226be36-848e-4793-b52c-3295f8e9a67b@googlegroups.com>
Subject: Re: A little trouble with very large arrays.
From: Shark8 <onewingedshark@gmail.com>
Injection-Date: Sat, 06 Oct 2018 18:50:00 +0000
Content-Type: text/plain; charset="UTF-8"
Xref: reader02.eternal-september.org comp.lang.ada:54509
Date: 2018-10-06T11:49:59-07:00
List-Id: <comp.lang.ada>

On Saturday, October 6, 2018 at 10:04:59 AM UTC-6, Jeffrey R. Carter wrote:
> On 10/05/2018 09:49 PM, Shark8 wrote:
> > 
> > Most of the anticipated usage for where I am right now would be producing FITS files, likely in something that would boil down to a coupling like this:
> 
> For that you can probably get by with something that translates your image into 
> a sequence of FITS "blocks" and writes them to a file:
> 
> FITS.Write (Image => Image, File_Name => "George");
> 
> There doesn't seem to be any reason to store a FITS object.

For our specific usage *RIGHT NOW*, sure.
All that's *REALLY* required, for the Telescope's production-side is writing out those blocks, this is true... but doing it this way would be kneecapping myself in the sense of maintenance & usability. (Like global-variables/states.)

[WRT software:] The Astronomy field is pretty fragmented and ripe for solid, reliable, libraries. Getting a good FITS library is only one of several things I'd like to produce:
(1) A good ISO 8601 library, to include periods and intervals;
--(a) This would include a secondary scheduling library.
(2) A stellar-coordinate library;
(3) A good abstraction for telescope-control.