Multiprocessor run using particle input file (PARINIT)

Post any questions or comments regarding the LINUX version of HYSPLIT. This includes the model execution, GUIs, results, or graphics. Be sure to mention the version of LINUX you are using.
Posts: 629
Joined: November 7th, 2012, 3:14 pm
Registered HYSPLIT User: Yes

Re: Multiprocessor run using particle input file (PARINIT)

Post by ariel.stein » February 25th, 2014, 4:05 pm

It looks like you are writing the PARDUMP correctly. However, there seems to be a problem with the way you are restarting the run. Can you please show me the script that you are using to re-initialize the second cycle? I think you are not properly overlapping the end time from the first cycle with the one in the second.

Posts: 300
Joined: November 9th, 2012, 4:23 pm
Registered HYSPLIT User: Yes

Re: Multiprocessor run using particle input file (PARINIT)

Post by barbara.stunder » February 28th, 2014, 12:13 pm

WARNING parinp: initialization in time wait mode
means that the time of the particles in the PARINIT file don't match that of the current time in the run. You can run one of the particle plotting programs (e.g. parxplot) to see what times are in the particle file.

If you get that message for a multi-processor run, you should also get it for a single-processor run, given the same run start times, etc. Check for other any other "parinp" messages in the MESSAGE file.

If your 1st run starts at 06z, runs for 6 hours, and you are outputting particles hourly, then you start the 2nd run at 12z with the PARINIT.001 etc files in the working directory, it should read the PARINIT.001 etc for the valid time 12z.

Post Reply