[McIDAS #JGN-249914]: IMGMAKE

Hi Mike,

re: ADDE servers are in C and ldm-alchemy has already done a LOT of the work

> Fair points.  Doing everything we've been doing in python has been
> daunting.

SSEC has been talking about trying to roll an ADDE server in Python.
That would be interesting!

re:
> Even though we haven't turned the fire hose on full with
> McIDAS yet, by comparison it seems like a walk in the park while
> twirling a cane!

:-) Quite the visual image ;-)

re:
> Ldm-alchemy does have some load associated with it,
> but it's very reasonable and about what I would expect.

The job of stitching together the tiles is best done once
given its heavy weight.  I have been considering the pros
and cons of doing the stitching together here (or in the
cloud) and then relaying the reconstituted images (with
netCDF compression turned on) in the IDD.  This approach
has a log of attractive points, but the bandwidth hit might
be daunting for schools with less than stellar networks.

re: McIDAS-X v2016 (both SSEC and Unidata versions) don't support
the netCDF4 images in NOAAPort; I'm the one writing the ADDE
server for the data, and will work with SSEC to (perhaps) incorporate
it into the McIDAS core.

> Well that explains that.

Yup. :-)

re:
> For the sake of testing & development, all of our work now is being
> done on the side of our main operations.

The smart way of doing things!

re:
> So if upgrading versions
> requires any changes that's totally fine right now.  I'll consult with
> Paul about what that will mean for our operational environment, but we
> wouldn't do that for some time I believe.

OK.

> 
re: scheme to "brighten" the NOAAPort-distributed GOES-16 images

> Neat, looking forward to it.

My plan is to do regressions on each band for images distributed in
the GRB (GOES ReBroadcast for GOES-16) to see if they are consistent.
FYI the images in GRB are _not_ dim like the ones in NOAAPort.  It
is entirely (likely?) possible that the group that is creating the
images for NOAAPort are already working on correcting the problems that
we all know exist with the NOAAPort images.  It has been a little 
painful/exasperating waiting for the next iteration of the images to
hit the air as I'd really like to get the Unidata McIDAS-X v2017
released!

re: get a v2017 prelease now or wait?

> If it's not a big deal for you, I'm raring to go.  The sooner we can
> sort out some logistics on our end the better as I'll need to bounce
> between a few other projects in coming weeks.  That's my preference,
> but if you'd rather hold off until those tweaks are in place I
> completely understand.

OK.  I'll cut a new v2017 prerelease cut when I get into the office (been
working from home this morning) and make it available to you (I believe
that I still have the login credentials to SSH to (weather|climate).cod.edu,
and, if I do, I'll SCP the distribution and unpacking script to one of those
machines and let you know where I put it.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: JGN-249914
Department: Support McIDAS
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.