mtucker
1. I don't know.
2. Using USD for your value clips is definitely faster to load than using BGEO for your clip files.
3. Automate which process? There is a File Cache LOP you could try?

protozoan

tamte
Why would it need to load any file to memory?

It used to be like that, but that was a long time ago and now should not be necessary anymore. The value clip generation should zing just through, even for large datasets.

robp: A lot of people seem to struggle with this. Maybe this warrants a case-study tutorial like "Solarifying production caches efficiently from start to finish" without skipping any checkboxes etc.

1. Soo is there an example file or a tutorial available currently?
   
2. I saw the example file using bgeo above, but I have concerns with using bgeo. It doesn't seem practical because, after any simulation, there's usually a step where additional elements are added, requiring another round of caching. Using USD makes more sense since it's a more LOP-friendly format?
   
3. Is there a way to automate this process similar to the Labs File Cache? The current method feels quite tedious :S
   

Hamilton Meathouse
I don't think that value is a multiplier, it's an explicit value. Looks like it's maybe using world units, so in this case if you set it to 0.8, you'd get pscale of 80 centimetres

1. Distinct Colors: I use different colors for input and output nodes (yellow for input, green for output) to quickly identify the flow of data. smth like: OUT_name_of_the_output
   
2. Framed Logic Blocks: I like to put a frame around each logical grouping of nodes and add a very short note (1-5 words max) that describes what that section does.
   
3. Numbered Notes: I find it helpful to leave notes with numbered steps (1, 2, 3...) that guide someone through the setup process.
   
4. Single Object Node (Usually): I generally prefer to keep everything within a single object node. Jumping between multiple object nodes can get messy quickly.
   
5. +1 for the above: Use a object merge to connect nodes that are far away.
   
6. All materials to start from "M_" when I'm not lazy
   
7. If you have 3+ similar blocks of code please make an OTL out of it