mdonovan wrote: [quote=lukeiamyourfather]The whole sequence of simulating on a node could be initiated in RealFlow with a GUI though, a batch script. However you do it try to keep projects self contained and not split up assets from the scene file. Cheers!
Sorry if this is obvious ... but how do I do the whole thing from a batch within realflow ... I mean how to I execute the remote command line from within my local realflow ?
man I fell like a noob.[/quote]
Python itself can directly interact with the command prompt or shell. The os module (os.system() which is kind of old school) or subprocess module (subprocess.Popen() replaced os.system() with more features like piping) can launch things, or submit tasks to a queue manager, whatever can be done directly in the command prompt or shell. Also some queue managers have Python API so you can submit tasks directly form Python without using the shell or command prompt.
Ideally simulation tasks should be sent through a queue manager just like renders would be, but if you have to send it to a single remote system explicitly then do it with ssh or something like that. Not sure if Windows has a remote shell equivalent but it probably does. Not to dog Windows too much but this is where using Linux in a production environment is just meant to be. Cheers!