Realflow Meshing Fails

atomicx · August 31, 2014, 9:18pm

I have been unable to get deadline to run a realflow meshing job without failing. In doing some internet searching it seems that the error causing this is “import site” failed. Apparently this is not an issue that should kill the process. The licenses are getting picked up fine. Here is a reference on the un-official realflow forum: realflowforum.com/viewtopic. … %27+failed

Any help would be appreciated. I really need to use the farm to batch the meshing.

Below is an error log from one of the renderboxes:

=======================================================
Error

Error: Renderer returned non-zero error code, 1. Check the log for more information.
at Deadline.Plugins.ScriptPlugin.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel)

=======================================================
Type

RenderPluginException

=======================================================
Stack Trace

at Deadline.Plugins.Plugin.RenderTask(String taskId, Int32 startFrame, Int32 endFrame)
at Deadline.Slaves.SlaveRenderThread.a(TaskLogWriter A_0)

=======================================================
Full Log

2014-08-31 15:10:24: BEGIN - STRYKER\Christian
2014-08-31 15:10:24: 0: Start Job timeout is disabled.
2014-08-31 15:10:24: 0: Task timeout is disabled.
2014-08-31 15:10:24: 0: Loaded job: 16_Stones_v6.4_Base.flw (54037f678df1fa13845fedd9)
2014-08-31 15:10:24: 0: Skipping drive mapping because they have already been mapped for this job
2014-08-31 15:10:24: 0: INFO: Executing plugin script C:\Users\Christian\AppData\Local\Thinkbox\Deadline7\slave\Stryker\plugins\54037f678df1fa13845fedd9\RealFlow.py
2014-08-31 15:10:24: 0: INFO: About: RealFlow Plugin for Deadline
2014-08-31 15:10:24: 0: INFO: The current environment will be used for rendering
2014-08-31 15:10:24: 0: Plugin rendering frame(s): 8
2014-08-31 15:10:24: 0: INFO: Stdout Handling Enabled: True
2014-08-31 15:10:24: 0: INFO: Popup Handling Enabled: False
2014-08-31 15:10:24: 0: INFO: Using Process Tree: True
2014-08-31 15:10:24: 0: INFO: Hiding DOS Window: True
2014-08-31 15:10:24: 0: INFO: Creating New Console: False
2014-08-31 15:10:24: 0: INFO: Running as user: Christian
2014-08-31 15:10:24: 0: INFO: Enforcing 64 bit build of RealFlow
2014-08-31 15:10:24: 0: INFO: Executable: “C:/Program Files/Next Limit/RealFlow 2014/RealFlowNode.exe”
2014-08-31 15:10:24: 0: INFO: Argument: -range 8 8 -mesh -useCache “X:/16_Stones/3D/16_Stones_RF_v06/16_Stones_v6.4_Base.flw”
2014-08-31 15:10:24: 0: INFO: Startup Directory: “C:\Program Files\Next Limit\RealFlow 2014”
2014-08-31 15:10:24: 0: INFO: Process Priority: BelowNormal
2014-08-31 15:10:24: 0: INFO: Process Affinity: default
2014-08-31 15:10:24: 0: INFO: Process is now running
2014-08-31 15:10:32: 0: STDOUT: -----------------------------------------------------------------
2014-08-31 15:10:32: 0: STDOUT: 1998-2014 © Next Limit - RealFlow(x86_64) v2014(8.1.1.0179)
2014-08-31 15:10:32: 0: STDOUT: -----------------------------------------------------------------
2014-08-31 15:10:32: 0: STDOUT: Initializing license manager…
2014-08-31 15:10:32: 0: STDOUT: Checking license…
2014-08-31 15:10:32: 0: STDOUT: Initializing Services…
2014-08-31 15:10:32: 0: STDOUT: Initializing Parameter Blocks …
2014-08-31 15:10:32: 0: STDOUT: Retrieving CPU information…
2014-08-31 15:10:32: 0: STDOUT: Detecting OpenCL devices…
2014-08-31 15:10:32: 0: STDOUT: ----------- Processing Devices Info -----------
2014-08-31 15:10:32: 0: STDOUT: Devices type CPU detected: 8
2014-08-31 15:10:32: 0: STDOUT: Devices type OpenCL-GPU detected: 0
2014-08-31 15:10:32: 0: STDOUT: Devices type OpenCL-CPU detected: 0
2014-08-31 15:10:32: 0: STDOUT: Devices type OpenCL-ACCELERATOR detected: 0
2014-08-31 15:10:32: 0: STDOUT: ----------- OpenCL Platforms Info -----------
2014-08-31 15:10:32: 0: STDOUT: ----------- OpenCL Devices Info -----------
2014-08-31 15:10:32: 0: STDOUT: Initializing expressions engine …
2014-08-31 15:10:32: 0: STDOUT: Initializing Simulation Pipeline dispatcher …
2014-08-31 15:10:32: 0: STDOUT: Loading plugins …
2014-08-31 15:10:32: 0: STDOUT: Initializing Scene Layers …
2014-08-31 15:10:32: 0: STDOUT: Loading workspace X:/16_Stones/3D/16_Stones_RF_v06/16_Stones_v6.4_Base.flw …
2014-08-31 15:10:32: 0: STDOUT: >15:10:24: Workspace version: 8026.25.0.34 (STANDARD EDITION)
2014-08-31 15:10:32: 0: STDOUT: >>> Setting up scene
2014-08-31 15:10:32: 0: STDOUT: >>> 7%
2014-08-31 15:10:32: 0: STDOUT: >>> 14%
2014-08-31 15:10:32: 0: STDOUT: >>> 21%
2014-08-31 15:10:32: 0: STDOUT: >>> 28%
2014-08-31 15:10:32: 0: STDOUT: >>> 35%
2014-08-31 15:10:32: 0: STDOUT: >>> 42%
2014-08-31 15:10:32: 0: STDOUT: >>> 50%
2014-08-31 15:10:32: 0: STDOUT: >>> 57%
2014-08-31 15:10:32: 0: STDOUT: >>> 64%
2014-08-31 15:10:32: 0: STDOUT: >>> 71%
2014-08-31 15:10:32: 0: STDOUT: >>> 78%
2014-08-31 15:10:32: 0: STDOUT: >>> 85%
2014-08-31 15:10:32: 0: STDOUT: >>> 92%
2014-08-31 15:10:32: 0: STDOUT: >>> 100%
2014-08-31 15:10:32: 0: STDOUT: Using 8 threads for this simulation …
2014-08-31 15:10:32: 0: STDOUT: >15:10:28: ================ Frame 8 started ================
2014-08-31 15:10:32: 0: STDOUT: >15:10:32: Mesh done.
2014-08-31 15:10:32: 0: STDOUT: Summary information
2014-08-31 15:10:32: 0: STDOUT: -------------------
2014-08-31 15:10:32: 0: STDOUT: container: [8 vertices - 12 faces] [] [vx:0]
2014-08-31 15:10:32: 0: STDOUT: collision_boundary: [8 vertices - 12 faces] [] [vx:0]
2014-08-31 15:10:32: 0: STDOUT: birthing_boundary: [8 vertices - 12 faces] [] [vx:0]
2014-08-31 15:10:32: 0: STDOUT: killing_boundary: [8 vertices - 12 faces] [] [vx:0]
2014-08-31 15:10:32: 0: STDOUT: HY_D_01: [0x0x0 0 cells] [7,773,832 particles] [0.300000 cell size]
2014-08-31 15:10:32: 0: STDOUT: SceneCamera01
2014-08-31 15:10:32: 0: STDOUT: Gravity02
2014-08-31 15:10:32: 0: STDOUT: Ocean_Force01
2014-08-31 15:10:32: 0: STDOUT: Ocean_Force02
2014-08-31 15:10:32: 0: STDOUT: Sheeter01
2014-08-31 15:10:32: 0: STDOUT: Drag_Force01
2014-08-31 15:10:32: 0: STDOUT: k_Isolated01
2014-08-31 15:10:32: 0: STDOUT: Ocean_Force03
2014-08-31 15:10:32: 0: STDOUT: Timing information
2014-08-31 15:10:32: 0: STDOUT: -------------------
2014-08-31 15:10:32: 0: STDOUT: Elapsed time: 00:00:04
2014-08-31 15:10:32: 0: STDOUT: Remaining time (estimated): -2147483648:-2147483648:-2147483648
2014-08-31 15:10:32: 0: STDOUT: Average time (frame): -2147483648:-2147483648:-2147483648
2014-08-31 15:10:32: 0: STDOUT: >15:10:32: ================ Frame finished ================
2014-08-31 15:10:32: 0: STDOUT: ‘import site’ failed; use -v for traceback
2014-08-31 15:10:33: 0: INFO: Process exit code: 1

=======================================================
Details

Date: 08/31/2014 15:10:46
Frames: 8
Elapsed Time: 00:00:00:12
Job Submit Date: 08/31/2014 14:03:09
Job User: christian
Average RAM Usage: 2618662656 (11%)
Peak RAM Usage: 4891734016 (19%)
Average CPU Usage: 16%
Peak CPU Usage: 62%

=======================================================
Slave Information

Slave Name: Stryker
Version: v7.0.0.26 R (c53f90c95)
Operating System: Windows 7 Ultimate (SP1)
Machine User: Christian
IP Address: 10.10.1.104
MAC Address: 54:04:A6:49:2F:CD
CPU Architecture: x64
CPUs: 8
CPU Usage: 6%
Memory Usage: 2.1 GB / 24.0 GB (8%)
Free Disk Space: 187.164 GB
Video Card: NVIDIA GeForce 210

atomicx · September 1, 2014, 1:48am

One other note. This scene meshes fine from cmd line and I am currently using RealFlow Job manager which is a PITA!

rrussell · September 2, 2014, 4:46pm

The reason why Deadline is failing the render is because RealFlowNode.exe is returning an non-zero exit code of “1”, which normally indicates that there was an error. However, based on the log, the frame is being saved successfully, so maybe that import error results in an exit code of 1, rather than 0. That could explain why it works fine when testing from the command line.

Can you test with the command line again, and then copy & paste the output text from the command line window? We can compare it to the log from the Deadline job you posted earlier to see if anything stands out.

Also, have you tried rebooting the render nodes to see if it helps? Maybe Deadline was still running when RF 2014 was installed, and it’s not recognizing some new environment variables. Restarting the machine would ensure a “clean” environment.

Cheers,
Ryan

atomicx · September 2, 2014, 11:37pm

I have restarted the render nodes several times as well as the server in trying to troubleshoot. No luck… Below is the output from the cmd line. Notice that the ‘import site’ failed; appears at the beginning. From what I understand this is a python issue and should not cause a problem as the sim still completes but flags an error. I’m not sure if this is what is causing an exit code of “1” or something else. Also notice that the frame completes but the time is 1:23, when running from Deadline it completes in a few seconds. Something is failing somewhere.

C:\Program Files\Next Limit\RealFlow 2014>RealFlowNode.exe -range 0 10 X:\16_Stones\3D\16_Stones_RF_v06\16_Stones_v6.4_B
ase.flw
‘import site’ failed; use -v for traceback

1998-2014 © Next Limit - RealFlow(x86_64) v2014(8.1.1.0179)

Initializing license manager…
Checking license…
Initializing Services…
Initializing Parameter Blocks …
Retrieving CPU information…
Detecting OpenCL devices…
----------- Processing Devices Info -----------
Devices type CPU detected: 8
Devices type OpenCL-GPU detected: 0
Devices type OpenCL-CPU detected: 0
Devices type OpenCL-ACCELERATOR detected: 0

----------- OpenCL Platforms Info -----------

----------- OpenCL Devices Info -----------

Initializing expressions engine …
Initializing Simulation Pipeline dispatcher …

Loading plugins …
Initializing Scene Layers …
Loading workspace X:\16_Stones\3D\16_Stones_RF_v06\16_Stones_v6.4_Base.flw …

17:25:33: Workspace version: 8026.25.0.34 (STANDARD EDITION)

Setting up scene
6%
12%
18%
25%
31%
37%
43%
50%
56%
62%
68%
75%
81%
87%
93%
100%

Using 8 threads for this simulation …

17:25:51: File X:\16_Stones\3D\16_Stones_RF_v06/meshes/6_4_BaseHY_Mesh01_00000.abc not found.
17:25:51: Using the displacement in cache mode for node HY_D_01 but resource not checked in the export central.
17:25:51: Using 8 thread(s) for this simulation.
17:25:51: ================ Frame 0 started ================

Summary information

HY_Mesh01: [4,465,379 vertices - 8,967,862 faces]
container: [8 vertices - 12 faces] [] [vx:0]
collision_boundary: [8 vertices - 12 faces] [] [vx:0]
birthing_boundary: [8 vertices - 12 faces] [] [vx:0]
killing_boundary: [8 vertices - 12 faces] [] [vx:0]
Mesh_Clip: [8 vertices - 12 faces] [] [vx:0]
HY_D_01: [359x33x359 4,253,073 cells] [7,694,754 particles] [0.300000 cell size]
SceneCamera01
Gravity02
Ocean_Force01
Ocean_Force02
Sheeter01
Drag_Force01
k_Isolated01
Ocean_Force03

Timing information

Elapsed time: 00:01:23
Remaining time (estimated): 00:12:35
Average time (frame): 00:01:23

17:27:15: ================ Frame finished ================

atomicx · September 2, 2014, 11:50pm

Also, when running from Deadline there is no output mesh saved even though is says frame complete. Running cmd line or RealFlow Job Manager outputs the mesh correctly.

rrussell · September 3, 2014, 1:04pm

Thanks for posting the log! I noticed that the command line you ran is a bit different than the one that Deadline is running:

Deadline:

RealFlowNode.exe -range 8 8 -mesh -useCache "X:/16_Stones/3D/16_Stones_RF_v06/16_Stones_v6.4_Base.flw"

Your command line:

RealFlowNode.exe -range 0 10 X:\16_Stones\3D\16_Stones_RF_v06\16_Stones_v6.4_B

In Deadline’s command line, the -mesh and -useCache options are being passed (which means you have the Generate Mesh and Use Particle Cache options enabled when submitting the job. Can you try disabling those options when submitting to Deadline to see if it works properly, or on the other hand, can you include the -mesh and -useCache options in your command line to see if you have the same problem?

Cheers,
Ryan

atomicx · September 3, 2014, 11:20pm

I retried in Deadline setting the “generate mesh” and “use particle cache” options to off. Guess what? No error I also tried with the “use particle cache” option on, this also worked with no error. From my understanding, you would only set the “use particle cache” if you are continuing a simulation of particles from where the cache left off. In this case I am only meshing so it’s not really relevant. In the RealFlow scene the Hybrido particle domain is set to cached mode so when it loads the scene it just processes what’s active. In my scene that’s only the Hybrido mesh.

I then tried running straight from the cmd line again, this time using the -mesh option. The frame completed correctly. I pasted the log below. I’m not sure what Deadline is doing different when using the “generate mesh” option but that seems to be the problem. One thought is that I’m using a Hybrido mesh. I know they made some updates to that in 2014 so there may be a bug in RealFlow or maybe there is something different that needs to be passed from Deadline.

Another bug I noticed while testing this. I initially set up Deadline with only one rendernode active (the same rendernode in the previous logs). It was running along and generating meshes but there was no update in the Deadline Monitor. It showed it still running on frame 0 for about 30 min. I opened up the slave log and I could see that it was indeed processing through the frames. I then added in the other rendernodes and restarted. Everything ran smoothly updating and distributing frames.

C:\Program Files\Next Limit\RealFlow 2014>RealFlowNode.exe -range 8 10 -mesh X:\16_Stones\3D\16_Stones_RF_v06\16_Stones_v6.4_Base.flw
‘import site’ failed; use -v for traceback

1998-2014 © Next Limit - RealFlow(x86_64) v2014(8.1.1.0179)

Initializing license manager…
Checking license…
Initializing Services…
Initializing Parameter Blocks …
Retrieving CPU information…
Detecting OpenCL devices…
----------- Processing Devices Info -----------
Devices type CPU detected: 8
Devices type OpenCL-GPU detected: 0
Devices type OpenCL-CPU detected: 0
Devices type OpenCL-ACCELERATOR detected: 0

----------- OpenCL Platforms Info -----------

----------- OpenCL Devices Info -----------

Initializing expressions engine …
Initializing Simulation Pipeline dispatcher …

Loading plugins …
Initializing Scene Layers …
Loading workspace X:\16_Stones\3D\16_Stones_RF_v06\16_Stones_v6.4_Base.flw …

16:50:58: Workspace version: 8026.25.0.34 (STANDARD EDITION)

Setting up scene
6%
12%
18%
25%
31%
37%
43%
50%
56%
62%
68%
75%
81%
87%
93%
100%

Using 8 threads for this simulation …

16:51:16: ================ Frame 8 started ================

16:52:36: Mesh done.
Summary information

HY_Mesh01: [4,049,057 vertices - 8,111,865 faces]
container: [8 vertices - 12 faces] [] [vx:0]
collision_boundary: [8 vertices - 12 faces] [] [vx:0]
birthing_boundary: [8 vertices - 12 faces] [] [vx:0]
killing_boundary: [8 vertices - 12 faces] [] [vx:0]
Mesh_Clip: [8 vertices - 12 faces] [] [vx:0]
HY_D_01: [360x33x360 4,276,800 cells] [7,773,832 particles] [0.300000 cell size]
SceneCamera01
Gravity02
Ocean_Force01
Ocean_Force02
Sheeter01
Drag_Force01
k_Isolated01
Ocean_Force03

Timing information

Elapsed time: 00:01:19
Remaining time (estimated): -2147483648:-2147483648:-2147483648
Average time (frame): -2147483648:-2147483648:-2147483648

16:52:36: ================ Frame finished ================

atomicx · September 3, 2014, 11:29pm

I did try checking using the Deadline Monitor from two different machines and the frames were not progressing. It showed it running on frame zero even though the render time was being updated. Sorry this thread diverted to two different bugs…

rrussell · September 4, 2014, 1:54pm

Let’s continue focusing on the meshing problem for now, then we can move on to the progress issue.

I don’t know if this matters, but in your command line, you are giving RF a range of 8 to 10, whereas the Deadline job is just doing frame 8. From your command line, can you try running the following and see what happens?

RealFlowNode.exe -range 8 8 -mesh X:\16_Stones\3D\16_Stones_RF_v06\16_Stones_v6.4_Base.flw

If you can post the log for this, that would be great. Then, can you submit the job to Deadline with just the “Generate Mesh” option enabled, and post the job’s log for frame 8? That way, we can do a direct comparison and try to figure out what’s going on.

Finally, do you have Deadline installed as a service on your machines? It’s not by default, and if you can see the Slave user interface, that means it’s not running as a service.

Thanks!
Ryan

atomicx · September 4, 2014, 6:44pm

Below is the output from the cmd line using just frame 8 as you specified. It completed the mesh correctly.

C:\Program Files\Next Limit\RealFlow 2014>RealFlowNode.exe -range 8 8 -mesh X:\16_Stones\3D\16_Stones_RF_v06\16_Stones_v6.4_Base.flw
‘import site’ failed; use -v for traceback

1998-2014 © Next Limit - RealFlow(x86_64) v2014(8.1.1.0179)

Initializing license manager…
Checking license…
Initializing Services…
Initializing Parameter Blocks …
Retrieving CPU information…
Detecting OpenCL devices…
----------- Processing Devices Info -----------
Devices type CPU detected: 8
Devices type OpenCL-GPU detected: 0
Devices type OpenCL-CPU detected: 0
Devices type OpenCL-ACCELERATOR detected: 0

----------- OpenCL Platforms Info -----------

----------- OpenCL Devices Info -----------

Initializing expressions engine …
Initializing Simulation Pipeline dispatcher …

Loading plugins …
Initializing Scene Layers …
Loading workspace X:\16_Stones\3D\16_Stones_RF_v06\16_Stones_v6.4_Base.flw …

12:31:47: Workspace version: 8026.25.0.34 (STANDARD EDITION)

Setting up scene
6%
12%
18%
25%
31%
37%
43%
50%
56%
62%
68%
75%
81%
87%
93%
100%

Using 8 threads for this simulation …

12:32:05: ================ Frame 8 started ================

12:33:26: Mesh done.
Summary information

HY_Mesh01: [4,049,057 vertices - 8,111,865 faces]
container: [8 vertices - 12 faces] [] [vx:0]
collision_boundary: [8 vertices - 12 faces] [] [vx:0]
birthing_boundary: [8 vertices - 12 faces] [] [vx:0]
killing_boundary: [8 vertices - 12 faces] [] [vx:0]
Mesh_Clip: [8 vertices - 12 faces] [] [vx:0]
HY_D_01: [360x33x360 4,276,800 cells] [7,773,832 particles] [0.300000 cell size]
SceneCamera01
Gravity02
Ocean_Force01
Ocean_Force02
Sheeter01
Drag_Force01
k_Isolated01
Ocean_Force03

Timing information

Elapsed time: 00:01:21
Remaining time (estimated): -2147483648:-2147483648:-2147483648
Average time (frame): -2147483648:-2147483648:-2147483648

12:33:26: ================ Frame finished ================

C:\Program Files\Next Limit\RealFlow 2014>

atomicx · September 4, 2014, 6:50pm

Below is the output from Deadline. I submitted just frame 8 with only the one rendernode online. The only option enabled was the “Generate Mesh”. After it errored, it attempted again to run the frame giving the same error. I am not running the slave in service mode. I log into the rendernodes using RDP.

=======================================================
Error

Error: Renderer returned non-zero error code, 1. Check the log for more information.
at Deadline.Plugins.ScriptPlugin.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel)

=======================================================
Type

RenderPluginException

=======================================================
Stack Trace

at Deadline.Plugins.Plugin.RenderTask(String taskId, Int32 startFrame, Int32 endFrame)
at Deadline.Slaves.SlaveRenderThread.a(TaskLogWriter A_0)

=======================================================
Full Log

2014-09-04 12:38:51: BEGIN - STRYKER\Christian
2014-09-04 12:38:51: 0: Start Job timeout is disabled.
2014-09-04 12:38:51: 0: Task timeout is disabled.
2014-09-04 12:38:51: 0: Loaded job: Bug Test (5408b1948df1fa17b81fdcc9)
2014-09-04 12:38:51: 0: Skipping X: because it is already mapped
2014-09-04 12:38:52: 0: INFO: Executing plugin script C:\Users\Christian\AppData\Local\Thinkbox\Deadline7\slave\Stryker\plugins\5408b1948df1fa17b81fdcc9\RealFlow.py
2014-09-04 12:38:52: 0: INFO: About: RealFlow Plugin for Deadline
2014-09-04 12:38:52: 0: INFO: The current environment will be used for rendering
2014-09-04 12:38:52: 0: Plugin rendering frame(s): 8
2014-09-04 12:38:52: 0: INFO: Stdout Handling Enabled: True
2014-09-04 12:38:52: 0: INFO: Popup Handling Enabled: False
2014-09-04 12:38:52: 0: INFO: Using Process Tree: True
2014-09-04 12:38:52: 0: INFO: Hiding DOS Window: True
2014-09-04 12:38:52: 0: INFO: Creating New Console: False
2014-09-04 12:38:52: 0: INFO: Running as user: Christian
2014-09-04 12:38:52: 0: INFO: Enforcing 64 bit build of RealFlow
2014-09-04 12:38:52: 0: INFO: Executable: “C:/Program Files/Next Limit/RealFlow 2014/RealFlowNode.exe”
2014-09-04 12:38:52: 0: INFO: Argument: -range 8 8 -mesh “X:/16_Stones/3D/16_Stones_RF_v06/16_Stones_v6.4_Base.flw”
2014-09-04 12:38:52: 0: INFO: Startup Directory: “C:\Program Files\Next Limit\RealFlow 2014”
2014-09-04 12:38:52: 0: INFO: Process Priority: BelowNormal
2014-09-04 12:38:52: 0: INFO: Process Affinity: default
2014-09-04 12:38:52: 0: INFO: Process is now running
2014-09-04 12:40:30: 0: STDOUT: -----------------------------------------------------------------
2014-09-04 12:40:30: 0: STDOUT: 1998-2014 © Next Limit - RealFlow(x86_64) v2014(8.1.1.0179)
2014-09-04 12:40:30: 0: STDOUT: -----------------------------------------------------------------
2014-09-04 12:40:30: 0: STDOUT: Initializing license manager…
2014-09-04 12:40:30: 0: STDOUT: Checking license…
2014-09-04 12:40:30: 0: STDOUT: Initializing Services…
2014-09-04 12:40:30: 0: STDOUT: Initializing Parameter Blocks …
2014-09-04 12:40:30: 0: STDOUT: Retrieving CPU information…
2014-09-04 12:40:30: 0: STDOUT: Detecting OpenCL devices…
2014-09-04 12:40:30: 0: STDOUT: ----------- Processing Devices Info -----------
2014-09-04 12:40:30: 0: STDOUT: Devices type CPU detected: 8
2014-09-04 12:40:30: 0: STDOUT: Devices type OpenCL-GPU detected: 0
2014-09-04 12:40:30: 0: STDOUT: Devices type OpenCL-CPU detected: 0
2014-09-04 12:40:30: 0: STDOUT: Devices type OpenCL-ACCELERATOR detected: 0
2014-09-04 12:40:30: 0: STDOUT: ----------- OpenCL Platforms Info -----------
2014-09-04 12:40:30: 0: STDOUT: ----------- OpenCL Devices Info -----------
2014-09-04 12:40:30: 0: STDOUT: Initializing expressions engine …
2014-09-04 12:40:30: 0: STDOUT: Initializing Simulation Pipeline dispatcher …
2014-09-04 12:40:30: 0: STDOUT: Loading plugins …
2014-09-04 12:40:30: 0: STDOUT: Initializing Scene Layers …
2014-09-04 12:40:30: 0: STDOUT: Loading workspace X:/16_Stones/3D/16_Stones_RF_v06/16_Stones_v6.4_Base.flw …
2014-09-04 12:40:30: 0: STDOUT: >12:38:53: Workspace version: 8026.25.0.34 (STANDARD EDITION)
2014-09-04 12:40:30: 0: STDOUT: >>> Setting up scene
2014-09-04 12:40:30: 0: STDOUT: >>> 6%
2014-09-04 12:40:30: 0: STDOUT: >>> 12%
2014-09-04 12:40:30: 0: STDOUT: >>> 18%
2014-09-04 12:40:30: 0: STDOUT: >>> 25%
2014-09-04 12:40:30: 0: STDOUT: >>> 31%
2014-09-04 12:40:30: 0: STDOUT: >>> 37%
2014-09-04 12:40:30: 0: STDOUT: >>> 43%
2014-09-04 12:40:30: 0: STDOUT: >>> 50%
2014-09-04 12:40:30: 0: STDOUT: >>> 56%
2014-09-04 12:40:30: 0: STDOUT: >>> 62%
2014-09-04 12:40:30: 0: STDOUT: >>> 68%
2014-09-04 12:40:30: 0: STDOUT: >>> 75%
2014-09-04 12:40:30: 0: STDOUT: >>> 81%
2014-09-04 12:40:30: 0: STDOUT: >>> 87%
2014-09-04 12:40:30: 0: STDOUT: >>> 93%
2014-09-04 12:40:30: 0: STDOUT: >>> 100%
2014-09-04 12:40:30: 0: STDOUT: Using 8 threads for this simulation …
2014-09-04 12:40:30: 0: STDOUT: >12:39:10: ================ Frame 8 started ================
2014-09-04 12:40:30: 0: STDOUT: >12:40:30: Mesh done.
2014-09-04 12:40:30: 0: STDOUT: Summary information
2014-09-04 12:40:30: 0: STDOUT: -------------------
2014-09-04 12:40:30: 0: STDOUT: HY_Mesh01: [4,049,057 vertices - 8,111,865 faces]
2014-09-04 12:40:30: 0: STDOUT: container: [8 vertices - 12 faces] [] [vx:0]
2014-09-04 12:40:30: 0: STDOUT: collision_boundary: [8 vertices - 12 faces] [] [vx:0]
2014-09-04 12:40:30: 0: STDOUT: birthing_boundary: [8 vertices - 12 faces] [] [vx:0]
2014-09-04 12:40:30: 0: STDOUT: killing_boundary: [8 vertices - 12 faces] [] [vx:0]
2014-09-04 12:40:30: 0: STDOUT: Mesh_Clip: [8 vertices - 12 faces] [] [vx:0]
2014-09-04 12:40:30: 0: STDOUT: HY_D_01: [360x33x360 4,276,800 cells] [7,773,832 particles] [0.300000 cell size]
2014-09-04 12:40:30: 0: STDOUT: SceneCamera01
2014-09-04 12:40:30: 0: STDOUT: Gravity02
2014-09-04 12:40:30: 0: STDOUT: Ocean_Force01
2014-09-04 12:40:30: 0: STDOUT: Ocean_Force02
2014-09-04 12:40:30: 0: STDOUT: Sheeter01
2014-09-04 12:40:30: 0: STDOUT: Drag_Force01
2014-09-04 12:40:30: 0: STDOUT: k_Isolated01
2014-09-04 12:40:30: 0: STDOUT: Ocean_Force03
2014-09-04 12:40:30: 0: STDOUT: Timing information
2014-09-04 12:40:30: 0: STDOUT: -------------------
2014-09-04 12:40:30: 0: STDOUT: Elapsed time: 00:01:19
2014-09-04 12:40:30: 0: STDOUT: Remaining time (estimated): -2147483648:-2147483648:-2147483648
2014-09-04 12:40:30: 0: STDOUT: Average time (frame): -2147483648:-2147483648:-2147483648
2014-09-04 12:40:30: 0: STDOUT: >12:40:30: ================ Frame finished ================
2014-09-04 12:40:30: 0: STDOUT: ‘import site’ failed; use -v for traceback
2014-09-04 12:40:31: 0: INFO: Process exit code: 1

=======================================================
Details

Date: 09/04/2014 12:40:43
Frames: 8
Elapsed Time: 00:00:01:42
Job Submit Date: 09/04/2014 12:38:44
Job User: christian
Average RAM Usage: 6032928256 (24%)
Peak RAM Usage: 8736276480 (34%)
Average CPU Usage: 26%
Peak CPU Usage: 100%

=======================================================
Slave Information

Slave Name: Stryker
Version: v7.0.0.26 R (c53f90c95)
Operating System: Windows 7 Ultimate (SP1)
Machine User: Christian
IP Address: 10.10.1.106
MAC Address: 54:04:A6:49:2F:CD
CPU Architecture: x64
CPUs: 8
CPU Usage: 1%
Memory Usage: 7.4 GB / 24.0 GB (31%)
Free Disk Space: 187.097 GB
Video Card: NVIDIA GeForce 210

atomicx · September 4, 2014, 6:54pm

I should note that I have been progressing on this scene with new versions, I’m at v8.2 on this project. I have been successfully using Deadline to mesh as long as I don’t use the “Generate Mesh” option.

rrussell · September 4, 2014, 7:51pm

Thanks for the logs! One last question - when you tested the Deadline job this last time, did it output frames (even though it keeps retrying the job)? If so, my guess at this point is that in this case, Realflow is simply returning an exit code of 1 when the -mesh option is provided, even though frames are being saved out properly.

By default, Deadline treats all non-zero exit codes as errors, and that’s the only thing that’s tripping up Deadline at this point. It could be possible to modify the Realflow plugin for Deadline to treat exit codes of 1 as success, but that could result in actual errors getting missed.

To me, this almost sounds like in Realflow, unless of course this is by design. Maybe you could email Next Limit’s support team about this and find out if that’s the case? At least going forward, you can get it to work with Deadline by simply not enabling the Generate Mesh option.

Finally, regarding the mesh progress reporting, I checked our current change log and progress reporting should work with Hybrido meshing in the beta 3 release (which should be ready in a week or two).

Cheers,
Ryan

atomicx · September 5, 2014, 4:14pm

Yes it did output frames. It just errors and keeps trying to que the frame again.

I’ll see if I can get any info from NextLimit support and I’ll pass it along. At least I have a workflow that is working.

Thanks for your help!

Realflow Meshing Fails

======================================================= Error

======================================================= Type

======================================================= Stack Trace

======================================================= Full Log

======================================================= Details

======================================================= Slave Information

C:\Program Files\Next Limit\RealFlow 2014>RealFlowNode.exe -range 0 10 X:\16_Stones\3D\16_Stones_RF_v06\16_Stones_v6.4_B ase.flw ‘import site’ failed; use -v for traceback

1998-2014 © Next Limit - RealFlow(x86_64) v2014(8.1.1.0179)

Summary information

Timing information

C:\Program Files\Next Limit\RealFlow 2014>RealFlowNode.exe -range 8 10 -mesh X:\16_Stones\3D\16_Stones_RF_v06\16_Stones_v6.4_Base.flw ‘import site’ failed; use -v for traceback

1998-2014 © Next Limit - RealFlow(x86_64) v2014(8.1.1.0179)

Timing information

C:\Program Files\Next Limit\RealFlow 2014>RealFlowNode.exe -range 8 8 -mesh X:\16_Stones\3D\16_Stones_RF_v06\16_Stones_v6.4_Base.flw ‘import site’ failed; use -v for traceback

1998-2014 © Next Limit - RealFlow(x86_64) v2014(8.1.1.0179)

Timing information

======================================================= Error

======================================================= Type

======================================================= Stack Trace

======================================================= Full Log

======================================================= Details

======================================================= Slave Information

=======================================================
Error

=======================================================
Type

=======================================================
Stack Trace

=======================================================
Full Log

=======================================================
Details

=======================================================
Slave Information

C:\Program Files\Next Limit\RealFlow 2014>RealFlowNode.exe -range 0 10 X:\16_Stones\3D\16_Stones_RF_v06\16_Stones_v6.4_B
ase.flw
‘import site’ failed; use -v for traceback

C:\Program Files\Next Limit\RealFlow 2014>RealFlowNode.exe -range 8 10 -mesh X:\16_Stones\3D\16_Stones_RF_v06\16_Stones_v6.4_Base.flw
‘import site’ failed; use -v for traceback

C:\Program Files\Next Limit\RealFlow 2014>RealFlowNode.exe -range 8 8 -mesh X:\16_Stones\3D\16_Stones_RF_v06\16_Stones_v6.4_Base.flw
‘import site’ failed; use -v for traceback

=======================================================
Error

=======================================================
Type

=======================================================
Stack Trace

=======================================================
Full Log

=======================================================
Details

=======================================================
Slave Information