I was processing some big rasters from Lidar data last week. There were five basic steps I wanted to complete: 1. Terrain to raster 2. Fill. 3. Flow Direction, 4. Flow Accumulation, 5. A Con to select the higher values of the Flow Accumulation to get to stream lines. While step 2 was running, I started thinking "Hey, this is going to take a while. I could put steps 3,4, and 5 in a script or model, and get them ready to run unattended once this Fill completes." But the Fill was still running when I went home. This got me wishing that I could launch the script running the remaining steps, but make the script wait until the Fill completed. Like I used to do in Unix environments.
I installed the wmi module for python, http://stackoverflow.com/questions/1632234/list-running-processes-on-64-bit-windows
but when I ran it, my process list was empty. They say it runs the same for Windows 7 64 like I am running, but I didn't figure this out.
. I could get a list of my processes at cmd, so it will work in python, but I didn't figure out a way recognize my Fill process or a way to test for the absence of my Fill process. I suppose the way to do it is to have the script run in circles until the process is not found, then let the script continue, like I did once with Unix shell scripts. Does anyone have an example of how to do this in Windows.