You are not logged in.
Pages: 1
1) My system meets the posted requirements.
2) In a vercut session: AutoDif.
3) Problem: error message reads insuficent virtual memory.
What can I do to get AutoDif to work? Or who can I call?
Greatly Appreciated, Jim
Offline
Hi,
We used to get this a lot earlier (that time we were in5.3). We are in V5.4.1. Cgtech introduced COMPARE BY REGIONS in Autodiff since V5.4. With this, we are not getting the "Insufficient Memory". It could take longer, but it does the work.
Regards
Kanthavelan.
Offline
Look at your cut tolerance.
You may be able to loosen this and still get the desired results with a performance boost to boot. Of course you will have to experiment with your particular application but we base our cut tolerance by stock size and tweek it from there. I am usually able to make the cut tolerance a much larger number than the lowest that my RAM will allow and get good results.
Dan
Offline
Hi All,
Dan and Kantha are correct. You can typically make Cut Tolerance much larger that you think, and still detect small gouges. Use the Stock Size option so that the value is not modified by the geometry of the current tools. You can also use the new Compare By Region feature to divide AUTO-DIFF's work into smaller memory chunks. The penalty is time.
I've re-written the description of Cut Tolerance in the 5.4.4 docs to try to better describe how it works. There is a pdf file with this updated piece snipped from the docs, at ftp://ftp.cgtech.com/pub/cut_tolerance.pdf. If you're interested, please have a look at it, and let me know if the description helps.
The main concept is that "cut tolerance" is based on the size of a volume, not on a chordal deviation. Generally, a .001" gouge can be detected by a much larger cut tolerance value (like .007) as long as the span of the gouge is large enough. But it depends on the shape and volume of the gouge.
Regards,
Bill
Offline
Pages: 1