Measure Points / Subsequent Evaluation

[[Sh...]]

I'm having an issue with Measure Points when running Subsequent Evaluation.  It's taking about 5-6 minutes to load and run a single .zmp and I think it might be tied to a 2d Curve because I'm using Recall Feature Points in features generated from the curve.

Anyone familiar with this or have any solutions?

[[Ch...]]

Shawn,

 

 howdy, are meas points on local hard drive or network ?  I've had similar issues when they are on network.

Shouldnt take this long though unless you have a lot of curves/freeform with a lot of points and Ca evaluations.

[[Sh...]]

i've tried both network and local, unfortunately didn't matter 😞

[[Cr...]]

I found if you have a lot of files (or they are big files) in the idmeaspoints folder within the program folder it will slow down the loading of measured points. When this happens, I create a new folder within the measurement plan folder and move older files from idmeaspoints into that folder. If I ever need to load measured points from a part that I've moved, I'll just move it back into the idmeaspoints folder.

[[Pa...]]

In addition, a measurement plan with LOTS of points or with graphic displays absolutely take a much longer time to process.

[[Ra...]]

If it's taking a long time to just load the list of zmp files, making an archive folder worked for me. We had 1000s of runs, and it would take 15 minutes to load.

[[Cl...]]

What version of Calypso are you using?  I am on 2025 and I have noticed it being a lot slower too I think it is the custom little visual of the list it makes.  You might try using the "Subsequent Evaluation of Serval Measurement or Alternative Path" option I find it opens a lot faster.

[[Je...]]

Please sign in to view this username.

, I echo what the others are saying, especially

Please sign in to view this username.

 and

Please sign in to view this username.

.  Having a congested idmeaspoints folder creates lag.  I often have .zmp files moved to subfolders.

Additionally, if you don't have one, an NVMe solid state drive such as a Samsung 990 Pro will read/write quickly and noticeably improve many Calypso operations.  I like to run one Samsung 990 for the operating system and another for data storage.

[[Sh...]]

I believe I figured out the issue, solving it however might take more time than any of us have.  I believe Kyle Johnson helped me look into a similar issue I posted about and also created a ticket for a program used for automation.  The inspset file is somehow corrupt and believe it could be due to some u_Para userfields created but I'm just guessing at that point.

Kyle and I found that removing the inspset file completely and starting with a new one seemed to fix the issue but thats a tough one because all the import information needed in the program is gone and when I attempted to go back and make all those corrections to the new inspset, the issue of loading came right back.