[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[McIDAS #JGN-249914]: IMGMAKE



Hi Mike,

re: failed to revert the 2017 version of 'mcupdate' to a previous, simple state
 
> No worries, glad we came across it fairly quick and that it was an easy fix .

re: what could be causing your white backgrounds and MCSTRETCH failures!!

> I'm working on sniffing this out.  So far I've tried to install the
> latest version on my dev server on top of the pre-release version that
> was on there.  So this was more or less the same procedure that I just
> did on my other server.  Same results, it would plot but dim, and
> IMGCOPY wouldn't work.  The next thing I tried was to rename
> ~mcidas/mcidas2017 and ~mcidas/bin and then install, so I didn't blow
> anything away but it should have been a "cleaner" install.  And then
> installed it just the same.  Here's what happened next...
> 
> IMGDISP NPGOESRL/CONUSC13 MAG=-3 LAT=37 95
> IMGDISP: AGETSERV failed on exec of abisaget
> IMGDISP: done
> IMGDISP failed, RC=2

Ah Ha!  The 'failed on exec of abisaget' indicates that your ADDE dataset
definition(s) are still using ABIS as the type of the NPGOESR images,
not SCMI.  If you recall, a very early version of my SCMI servers were
actually named using ABIS: abisadir and abisaget.  Your invocations before
renaming ~mcidas/mcidas2017 or actually ~mcidas/bin were causing the old servers
to be run, not the new ones.  And all bets are off with the old servers!

re:
> And just to make sure, from your server:
> 
> IMGDISP NPGOESR/CONUSC13 MAG=-3 LAT=37 95
> Beginning Image Data transfer, bytes= 481220
> IMGDISP: loaded frame  1
> IMGDISP: done
> 
> So everything is still fine there.  But what's up with abisaget?
> 
> find . -name "abisaget*"
> ./bin_old/abisaget
> ./mcidas2017_old/src/abisaget.cp
> 
> Nothing from ./bin or ./mcidas2017/src, so with a clean new install I
> don't have an abisaget binary.  I should, right?

Right.  See above.

re:
> If I should have one, then this is a concern:
> tar -ztvf mcidasx2017.tar.gz | grep "abisaget"
> -nothing-

There shouldn't be.  I believe that we talked about this in one of our
email exchanges (but I could be dreaming).  Once you change your
ADDE dataset definitions for the NPGOESR group to SCMI, everything
should work correctly.

re:
> That comes up empty, no files found.  It's in the pre-release though...
> tar -ztvf mcidasx2017_pr.tar.gz | grep "abisaget"
> -rw-r--r-- mcidas/Unidata    36725 2017-07-10 22:54 mcidas2017/src/abisaget.cp
> 
> This is also true for abisadir, I don't seem to have that either.

See above.

re: apologies

> No apologies necessary!  I totally understand that this is just how it
> goes sometimes, all part of the process.

re: many thanks for being my front line tester

> I am more than happy to contribute, and glad it's helping so much.
> I'll always be a willing test subject.  :)

So, as soon as you change ABIS to SCMI in your RESOLV.SRV, things should
work correctly.  Please let me know the results!

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.



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.