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

[GEMPAK #HXZ-866042]: use of gdcsv

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: [GEMPAK #HXZ-866042]: use of gdcsv
  • Date: Tue, 15 Apr 2014 14:20:09 -0600
Hi Pete,

I am not aware of any issue with multiple instances of gdcsv running, my only 
thought is if more than one instance is writing to the same file, that could 
obviously result in not seeing the file written correctly.

Is there anything which points to the source of the problem?  A particular 
model, date/time, parameter to isolate?   

Perhaps if I could hear more details about how gdcsv is being used, how many 
instances, how frequently they run, etc.  

-Michael James
Unidata


> We are using gdcsv in a multitasking environment -  launching many
> scripts in the background running gdcsv.  At times we are finding that
> gdcsv is not creating a csv file, but we are not seeing any errors or
> status messages.
>
> Is there an issue with running multi instances of gdcsv? Does anything
> need to be done with gplt, such as when to call gpend?


Ticket Details
===================
Ticket ID: HXZ-866042
Department: Support GEMPAK
Priority: Normal
Status: Open