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

[McIDAS #HQH-586893]: mcidas-x download forbidden

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 #HQH-586893]: mcidas-x download forbidden
  • Date: Sun, 17 Feb 2019 08:47:59 -0700
Hi Jim,

re:
> Thanks, Tom.  You've been a great help.

No worries.

Questions:

- Did you make progress yesterday?

- Is how to setup ADDE datasets making sense?

  The best way to think about the DIRFILE= keyword that one uses
  in the DSSERVE command is it is exactly like a regular expression
  that you would use in an 'ls' command to list out a set of files.
  In fact, I used how 'ls' works as the basis for what eventually
  became DIRFILE= when I first added this concept to McIDAS a number
  of years ago (the DIRFILE= keyword was SSEC's idea; I was using
  DIR= and FILE=).

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: HQH-586893
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.