There are a few things that can help with executing multiple hysplit runs at the same time.
1. you can name your CONTROL and SETUP.CFG files with a suffix - CONTROL.suffix1 SETUP.suffix1, CONTROL.suffix2 SETUP.suffix2.
Then you call the hysplit executable with (example shell scrip)Then you execute all of your runs in the same directory. However, occasionally this will fail because both runs are trying to access the ASCDATA.CFG file at the same time. It helps to stagger the start time of each run to avoid this problem.
2. You can execute each of your runs in its own directory. In this case you would have a directory structure such as run1/ run2/ run3/ and each directory would have CONTROL, SETUP.CFG, ASCDATA.CFG files for the run. For this configuration your script has to execute a directory change for each call to hyts_std. For instance in a shell script:Note - there should not be any reason that you need multiple hyts_std executables.
1. you can name your CONTROL and SETUP.CFG files with a suffix - CONTROL.suffix1 SETUP.suffix1, CONTROL.suffix2 SETUP.suffix2.
Then you call the hysplit executable with (example shell scrip)
CODE:
/hysplit/exec/hyts_std suffix1 & /hysplit/exec/hyts_std suffix2 &2. You can execute each of your runs in its own directory. In this case you would have a directory structure such as run1/ run2/ run3/ and each directory would have CONTROL, SETUP.CFG, ASCDATA.CFG files for the run. For this configuration your script has to execute a directory change for each call to hyts_std. For instance in a shell script:
CODE:
cd ./run1/hysplit/exec/hyts_std &cd ../run2/hysplit/exec/hyts_std &cd ../run3/hysplit/exec/hyts_std &Statistics: Posted by alicec — March 21st, 2024, 12:04 pm
