Malformed Header Error

Questions and postings pertaining to the development of HYSPLIT, feature enhancements, and HYSPLIT internals. HYSPLIT source code and algorithms are discussed here.
Post Reply
thomasb
Posts: 5
Joined: July 16th, 2015, 1:05 pm
Registered HYSPLIT User: No

Malformed Header Error

Post by thomasb » August 18th, 2015, 2:16 pm

I am writing a python program that executes Hysplit and when it begins hycs_std I receive this error:

"malformed header from script. Bad Header= HYSPLIT4 - Initialization 201: hysupdate.py"

Have any of you encountered this error before? What exactly does it mean?

glenn.rolph
Posts: 288
Joined: November 7th, 2012, 1:39 pm
Registered HYSPLIT User: Yes
Contact:

Re: Malformed Header Error

Post by glenn.rolph » August 18th, 2015, 2:35 pm

This message is written to standard output when HYSPLIT is started giving the version number of HYSPLIT, so your program needs to account for messages coming out of standard out.

thomasb
Posts: 5
Joined: July 16th, 2015, 1:05 pm
Registered HYSPLIT User: No

Re: Malformed Header Error

Post by thomasb » August 18th, 2015, 3:33 pm

In the script I include a process ID number that is associated with the CONTROL file. Isn't that supposed to bypass the interaction?
The line in the script is:

Code: Select all

os.system('usr/local/hysplit/trunk/exec/hycs_std '+pid)
With pid being the process ID. I have a correlating CONTROL.pid in the working directory.

glenn.rolph
Posts: 288
Joined: November 7th, 2012, 1:39 pm
Registered HYSPLIT User: Yes
Contact:

Re: Malformed Header Error

Post by glenn.rolph » August 19th, 2015, 6:45 am

Unfortunately some comments are not written to the MESSAGE file that has the extension. It is best to pipe the output that is not written to the MESSAGE file similar to (in perl)

exec "$CGI/disp4.scr $proc 1>>$proc_progress.txt 2>>$proc_progress.txt"

where disp4.scr contains the call to hycs_std

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest