"Path Translation Rules" (PTR) are actually always required, even in networks where all computers share the same operating system. There, you need them if you trigger jobs with a local path to a scene. In so-called heterogenous networks it is a little more difficult, because different operating systems also use different path notations. Without these path translations rules it is impossible for RealFlow to identify the directories where the simulation data are stored. The result is that the node cannot contribute to a simulation. One of the
Info |
---|
The most important things with path translation rules is to look at everything from the view of the computer with the “Job Manager” running. |
Let's assume you have a small network with three computers: 2 with Windows operating systems and 1 with OS X. The correct PTR depend on the computer where your RealFlow GUI application is running, because the location of RealFlow plays an important role. If you have more than one license on different computers you can choose from which machine you want to trigger a network simulation, but this also means that you have to specify path translation rules for each RealFlow application as well. With just a single RealFlow GUI license you only have to do this once.
...
Computer 1 | Windows | IP 192.168.1.15 | RealFlow GUI | Job Manager | Job Node |
---|---|---|---|---|---|
Computer 2 | Windows | IP 192.168.1.16 | Job Node | ||
Computer 3 | OS X | IP 192.168.1.17 | Job Node |
...
Prefix | C:/Documents and Settings/rfnode/RealFlow Projects/ |
---|---|
Windows | /Documents and Settings/rfnode/RealFlow Projects/ |
...
Computer 1 | Windows | IP 192.168.1.15 | Job Node | ||
---|---|---|---|---|---|
Computer 2 | Windows | IP 192.168.1.16 | Job Node | ||
Computer 3 | OS X | IP 192.168.1.17 | RealFlow GUI | Job Manager | Job Node |
...