HYSPLIT Forum: hysplitbbs.arl.noaa.gov

Hi, i'm working on a fire model which can predict the occurrence and timing of wildfires and estimate the corresponding pm2.5 emissions within a certain geographic region between 2030 and 2100. I was wondering, if it is possible to project the dispersion of pm2.5 emitted from future wildfires (2030-...

The issue has been resolved. It turned out the output was generated in the upper directory.

I'm running the Linux version of Hysplit and i was able to initiate a model run properly using a sh script i wrote to call hycs_std. All the files that are supposed to be generated along with the model run are all there, except for the final output. Can someone please help me find out why? Attached ...

I wanted to report that the issue had been resolved. Turned out there was a typo in the sh script and it got passed to hysplit which led to the error.

Thanks for being so patient with me. I got rid of the extra zeros but still got the same error.

Thanks for your response! I changed those values but still got the same errors. I thought by setting the span values to 0, the models would be run using the default values [180.0] [360.0]. I didn't run into any issues using 0 as the input span values when i ran Hysplit on my PC.

Thanks for spotting that error. However, after i've fixed it, the same error persists. I'm still getting the error message At line 224 of file depset.f (unit = 74, file = 'CONTROL') Fortran runtime error: End of file from the command line and WARNING metini: FLUXES not found in data (kg,kt) 1 1 Sett...

I realized i should have copied and pasted the text in the CONTROL file directly. So here it is: 05 05 20 04 1 57.6 -157.5 5000 1704 0 10000.0 6 /gpfs/data1/working/ NARR200505 /gpfs/data1/working/ NARR200506 /gpfs/data1/working/ NARR200507 /gpfs/data1/working/ NARR200508 /gpfs/data1/working/ NARR20...

I tried and got the same error message
"At line 224 of file depset.f (unit = 74, file = 'CONTROL')
Fortran runtime error: End of file
"
However, since i was using hycs_std, only one such message was shown (instead of 30 in the previous run which was using hycm_std on 30 nodes).

I should have done this myself! Thanks for being so thoughtful!