[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ldmMcidas #PUC-404507]: MD storage limits
- To: zehel@xxxxxxx
- Subject: [ldmMcidas #PUC-404507]: MD storage limits
- From: "Unidata ldm-mcidas Support" <support-ldm-mcidas@xxxxxxxxxxxxxxxx>
- Date: Fri, 07 Mar 2008 20:52:20 -0700
- Delivered-to: support-ldm-mcidas@unidata.ucar.edu by laraine.unidata.ucar.edu (Postfix) with ESMTP id E5A7ACB196; Fri, 7 Mar 2008 20:52:20 -0700 (MST) id B848ED5116; Fri, 7 Mar 2008 20:52:20 -0700 (MST)
Hi Samuel,
re:
> I have done this for all MD file formats, do I need to do this for other file formats (like AREA)?
You shouldn't have to do this since your general pqact.conf actions for image
processing are already writing files with descriptive names.
Example from ~ldm/etc/pqact.conf_mcidasB:
# Vis (0.65 um)
UNIWISC ^pnga2area Q. (U[^ACXY13]) (.*) (.*)_IMG (0.65)um (.*) (........) (....)
PIPE -close util/ldmfile.sh
/data/ldm/mcidas/images/sat/\3/\5/VIS/VIS_\6_\7
The image files in AREA format that are being written to ~ldm/data/mcidas
using the AREA file naming convention are replicated by other actions in
pqact.conf_mcidasB. The AREAnnnn files are written so that GOES-East/West
compositing can be done by a process run upon receipt of the various
East and West products.
Cheers,
Tom
****************************************************************************
Unidata User Support UCAR Unidata Program
(303) 497-8642 P.O. Box 3000
support@xxxxxxxxxxxxxxxx Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage http://www.unidata.ucar.edu
****************************************************************************
Ticket Details
===================
Ticket ID: PUC-404507
Department: Support ldm-mcidas
Priority: Normal
Status: Closed