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

[TIGGE #CED-782031]: does ldm server extract files locally

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: [TIGGE #CED-782031]: does ldm server extract files locally
  • Date: Thu, 28 Feb 2008 16:26:00 -0700
Dear MA Qiang,

> Why I can see the following message on ldm at CMA:
> 
> ldm01@tgn06 [ 
> /usr/local/ldm01/data/tigge_data/babj/glob/2008022700/prod/0240/pl ]
> $ ldmadmin watch
> (Type ^D when finished)
> Feb 28 12:03:35 pqutil INFO:   411062 20080228120334.539     EXP 000  
> z_tigge_c_babj_20080228000000_glob_prod_cf_pl_0006_000_0300_v.grib:32778
> 
> Does it mean that we receive babj data from other LDM Server

The output from the "ldmadmin watch" means that the data-product with
the product-identifier of 
"z_tigge_c_babj_20080228000000_glob_prod_cf_pl_0006_000_0300_v.grib:32778"
was created and injected into the LDM network at 2008-02-28 12:03:34.539 UTC.
The same data-product was received by the CMA LDM at 2008-02-28 12:03:35 UTC.
The data-product was received within one second after it was created.
Presumably (I don't know the data) the timestamp in the product-identifier
indicates that the data-product is for the time 2008-02-28 00:00:00 (UTC?) --
more than twelve hours before the product was created.  Either the time
in the product-identifier isn't UTC, or the product was created after its
canonical time.

> and the babj data is not extracted locally?

I'm not sure what you're asking.

The data-product should be processed by a "pqact" process if such a
process is started by an EXEC entry in the LDM configuration-file
(etc/ldmd.conf) and the "pqact" process is told to select such a
product (via the "-f" and "-p" options) and the product matches
an entry in the "pqact" configuration-file used by the "pqact"
process.

> I also found that the babj data files which were stored in ~/data
> were not accessed in a short time. The interval of access time was
> over 2 hours.

> ldm01@tgn06 [ 
> /usr/local/ldm01/data/tigge_data/babj/glob/2008022700/prod/0240/pl ]
> $ ls -ltr|head
> total 241200
> -rw-r--r--  1 ldm01 ldm 411062 Feb 27 09:44 
> z_tigge_c_babj_20080227000000_glob_prod_pf_pl_0240_002_1000_v.grib
> -rw-r--r--  1 ldm01 ldm 411062 Feb 27 09:44 
> z_tigge_c_babj_20080227000000_glob_prod_pf_pl_0240_012_1000_u.grib
> -rw-r--r--  1 ldm01 ldm 411062 Feb 27 09:45 
> z_tigge_c_babj_20080227000000_glob_prod_pf_pl_0240_006_0500_q.grib
> -rw-r--r--  1 ldm01 ldm 411062 Feb 27 09:45 
> z_tigge_c_babj_20080227000000_glob_prod_pf_pl_0240_006_0200_t.grib
> -rw-r--r--  1 ldm01 ldm 411062 Feb 27 09:45 
> z_tigge_c_babj_20080227000000_glob_prod_pf_pl_0240_001_0250_t.grib
> -rw-r--r--  1 ldm01 ldm 411062 Feb 27 09:46 
> z_tigge_c_babj_20080227000000_glob_prod_pf_pl_0240_008_0850_q.grib
> -rw-r--r--  1 ldm01 ldm 411062 Feb 27 09:46 
> z_tigge_c_babj_20080227000000_glob_prod_pf_pl_0240_006_1000_q.grib
> -rw-r--r--  1 ldm01 ldm 411062 Feb 27 09:46 
> z_tigge_c_babj_20080227000000_glob_prod_cf_pl_0240_000_0200_q.grib
> -rw-r--r--  1 ldm01 ldm 411062 Feb 27 09:47 
> z_tigge_c_babj_20080227000000_glob_prod_pf_pl_0240_010_0300_t.grib
> 
> ldm01@tgn06 [ 
> /usr/local/ldm01/data/tigge_data/babj/glob/2008022700/prod/0240/pl ]
> $ ls -ltr|tail
> -rw-r--r--  1 ldm01 ldm 411062 Feb 27 12:10 
> z_tigge_c_babj_20080227000000_glob_prod_pf_pl_0240_008_1000_t.grib
> -rw-r--r--  1 ldm01 ldm 411062 Feb 27 12:10 
> z_tigge_c_babj_20080227000000_glob_prod_pf_pl_0240_011_0500_gh.grib
> -rw-r--r--  1 ldm01 ldm 411062 Feb 27 12:10 
> z_tigge_c_babj_20080227000000_glob_prod_pf_pl_0240_013_0850_gh.grib
> -rw-r--r--  1 ldm01 ldm 411062 Feb 27 12:11 
> z_tigge_c_babj_20080227000000_glob_prod_pf_pl_0240_011_1000_gh.grib
> -rw-r--r--  1 ldm01 ldm 411062 Feb 27 12:11 
> z_tigge_c_babj_20080227000000_glob_prod_pf_pl_0240_002_0500_v.grib
> -rw-r--r--  1 ldm01 ldm 411062 Feb 27 12:11 
> z_tigge_c_babj_20080227000000_glob_prod_pf_pl_0240_002_0700_t.grib
> -rw-r--r--  1 ldm01 ldm 411062 Feb 27 12:11 
> z_tigge_c_babj_20080227000000_glob_prod_pf_pl_0240_012_0500_u.grib
> -rw-r--r--  1 ldm01 ldm 411062 Feb 27 12:11 
> z_tigge_c_babj_20080227000000_glob_prod_pf_pl_0240_004_0850_v.grib
> -rw-r--r--  1 ldm01 ldm 411062 Feb 27 12:11 
> z_tigge_c_babj_20080227000000_glob_prod_pf_pl_0240_014_0850_u.grib
> -rw-r--r--  1 ldm01 ldm 411062 Feb 27 12:12 
> z_tigge_c_babj_20080227000000_glob_prod_pf_pl_0240_007_0925_v.grib
> 
> Could you please tell me how to explain it?

I'm not sure what you mean.

If many data-products arrive in a short period of time (as the
TIGGE data does) then when a data-product is processed locally
will depend on how long it takes the processing program to process
each data-product.  If the relevant "pqact" process is either
started in verbose mode (via the "-v" option) or sent a USR2
signal, then it will log the processing of every data-product
into the LDM log file.  Could this help?

> Thank you!
> 
> Best regards,
> MA Qiang
> 
> National Meteorological Information Center
> 2008-02-28

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: CED-782031
Department: Support IDD TIGGE
Priority: Normal
Status: Closed