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

[McIDAS #QNX-338397]: Can't display images using Mcidas command IMGDISP

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [McIDAS #QNX-338397]: Can't display images using Mcidas command IMGDISP
  • Date: Mon, 17 Sep 2007 09:33:39 -0600
Hi Trung,

re:
> The following message is from executing one of my applications.
> 
> COPY ALL THREE BANDS FIRST
> Beginning Image Data transfer, bytes= 512768
> Transferring AREA data outbound, bytes= 617808
> IMGCOPY: GER/GECONS04I2.13 copied to LOC/POS.952
> imgcopy.k: done
> Beginning Image Data transfer, bytes= 512768
> Transferring AREA data outbound, bytes= 617808
> IMGCOPY: GER/GECONS04I4.65 copied to LOC/POS.954
> imgcopy.k: done
> Beginning Image Data transfer, bytes= 512928
> Transferring AREA data outbound, bytes= 617968
> IMGCOPY: GER/GECONS04I6.57 copied to LOC/POS.956
> imgcopy.k: done

This looks OK.

> But I couldn't display the imagery using Mcidas window with the
> following command.
> 
> IMGDISP LOC/POS.952
> IMGDISP: No images satisfy the selection criteria
> IMGDISP: done

Hmm...  Are the IMGCOPY and IMGDISP outputs from the same McIDAS session?

> Similarly for .954 and 956...
> However, I could display the source image (i.e. GER/GECONS04I2.13,
> GER/GECONS04I4.65 , ...)

This is a bit weird.

> By the way, I had all the Mcidas setup in place like:
> dsserver.k
> LOC/POS                  IMAGE AREA 1-9999

OK, with this ADDE server mapping table setup, the images
created from your IMGCOPY should be stored in the files:

LOC/POS.952  -> AREA0952
LOC/POS.954  -> AREA0954
LOC/POS.956  -> AREA0956

The first thing to check is if the images actually got created:

DMAP AREA09

> [~/mcidas/data] $ redirect.k LIST ALL
> AREA1* /data/voldata
> AREA5* /data/voldata
> AREA6* /data/voldata
> AREA7* /data/voldata
> AREA8* /data/voldata

Yes, but what about AREA0*?  If there is no file REDIRECTion for AREA0*
then the output images should be created in your McIDAS working directory.
This would be ~/mcidas/data for the non-'mcidas' user and ~/workdata for
'mcidas' _if_ you setup your account(s) according to the instructions
in the Unidata McIDAS-X Users Guide.

> I had no problem displaying the images before. The problem just arose
> after I moved my codes under a new user account.

This comment makes me suspicious about if the output images were actually
created.

> Could you tell me what caused this problem?

Please send the output of the DMAP command I included above.

> Thanks.

No worries.

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: QNX-338397
Department: Support McIDAS
Priority: Normal
Status: Closed