evanrudefx Posted August 16, 2017 Share Posted August 16, 2017 Hey, I am using the the output of my flip sim to save the simulation to disk. I told it to do 600 frames. It does around 120 then randomly stops. It gives no error. Houdini has not crashed. What would cause this? Thanks Quote Link to comment Share on other sites More sharing options...
Atom Posted August 16, 2017 Share Posted August 16, 2017 You are out of disk space? Quote Link to comment Share on other sites More sharing options...
evanrudefx Posted August 16, 2017 Author Share Posted August 16, 2017 (edited) I don't think so, it says 40 terabytes free I checked ram usage, it still had around 35% free when it stopped. Edited August 16, 2017 by ejr32123 Quote Link to comment Share on other sites More sharing options...
Atom Posted August 16, 2017 Share Posted August 16, 2017 (edited) When I am working with FLIP I never save .sim files. The best work flow suggest to me was to save out the compressed cache first as .bgeo.sc. Then save out the surface cache second. So it is a two step process. The fluidimport node is where you will find these two surfacing support nodes. The FileCache are put in place by the shelf tools so if you used those for your initial setup then they should already be in place. The reason you want to save out the compressed cache first is so you can have a bit more interactivity when dialing in the surface characteristic on fluid surface node. If you don't have a compressed cache you will find that every time you move to a new frame, you will have to sim again. Also whitewater references the compressed cache node for it's surface so once you have that cache written to disk bothe fluid surface and white water will respond much quicker. Also it allows you to sim at a little higher resolution because you don't have to hold both caches in memory at once. Edited August 16, 2017 by Atom Quote Link to comment Share on other sites More sharing options...
evanrudefx Posted August 16, 2017 Author Share Posted August 16, 2017 (edited) The reason I save my .sim files is because it seems to use more memory when caching the compressed fluid. It would crash (run out of memory) then I would have to start over. My workflow is I save my .sim then save compressed cache then save my surface cache. If it does crash when saving my compressed cache its ok because my sim is saved and I can start at any frame. Edited August 16, 2017 by ejr32123 Quote Link to comment Share on other sites More sharing options...
Atom Posted August 16, 2017 Share Posted August 16, 2017 (edited) I recently started adding a single float channel to my FLIPObject. Then I place this expression in the field. It takes into account the size of the fluid box and the particle separation to produce a number that is the approximate voxel count for the fluid area you have defined. ch("../flipsolver1/limit_sizex")/ch("particlesep")*ch("../flipsolver1/limit_sizey")/ch("particlesep")*ch("../flipsolver1/limit_sizez")/ch("particlesep") This will generate a number in scientific notation. Basically +6 at the end mean a million voxels, +7 means 10 million voxels and +8 means 100 million voxels. If you are in the +8 range or higher your computer may not have enough memory for your simulation, so try a higher value for particle separation to lower voxel count. Can you place your system specs in your signature? Also, you must leave OpenCL checkbox off to do any hi-resolution work in pyro or flip. flip_voxel_estimator.hiplc Edited August 16, 2017 by Atom Quote Link to comment Share on other sites More sharing options...
evanrudefx Posted August 16, 2017 Author Share Posted August 16, 2017 I am actually using my school's computer atm. It has 64 gigs of ram, gtx 980 ti, and a intel xeon (can't remember which model atm). While I am caching this sim around 35% of the ram is free. I can finish caching the sim, I just have to keep re-starting the cache when it stops. Also I should mention running out of ram while saving the compressed cache didn't happen to me for this particular sim, just in the past. To be safe, I usually save .sim first. Quote Link to comment Share on other sites More sharing options...
Atom Posted August 16, 2017 Share Posted August 16, 2017 (edited) Are you saving to a network drive? Some networks can't save a single disk file larger than 2GB. Try setting your particle separation really high to see if you can make it through the frame range you require. Then, using the voxel estimator, dial in a lower particle separation until you find the breaking point. You may have noticed in the GIF image I posted that the difference between 0.025 and 0.1 it 100,000,000. So the particle separation value is EXTREMELY sensitive. Edited August 16, 2017 by Atom Quote Link to comment Share on other sites More sharing options...
evanrudefx Posted August 16, 2017 Author Share Posted August 16, 2017 Yes I am. I wondered if that would be a problem. Could a connection problem cause it to stop? I am saving to the network because the local drive only has a 120 gig ssd. Quote Link to comment Share on other sites More sharing options...
Atom Posted August 16, 2017 Share Posted August 16, 2017 (edited) Are any of your files larger than 2GB? A company where I worked at we had the same exact problem. Old school networks may still have that 2GB limit. You may want to simply invest in a 128GB USB 3.0 local drive, or larger, and try writing your sim file to that. Report the network problem to your school's IT department. They may have a solution. Edited August 16, 2017 by Atom 1 Quote Link to comment Share on other sites More sharing options...
evanrudefx Posted August 16, 2017 Author Share Posted August 16, 2017 We don't have a 2 gig limit, but I believe saving to a hard drive is the next step. Thanks Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.