which should you run programs from

[[Mi...]]

should you run from characteristics or feature list

[[Ma...]]

It depends on your goals.

You can sort features to minimize and optimize travels between them and then run feature list. With same setup but characteristic machine will go left right and prolonging measurement time.

Also if you have many probe changes then optimizing for features will save you time ( if you sort your features by probe systems and probe tip )

I also heard of some sort of optimizer function for characteristic list.

In the end, it is up to the taste of the program author.

[[DW...]]

Please sign in to view this quote.

Please sign in to view this username.

 Features

[[Je...]]

Hi 

Please sign in to view this username.

While either "run from features" or "run from characteristics" can be used, the overwhelming majority of users run from features.  There is clear reasoning for this choice, and the Calypso infrastructure seems to favor this as well.

Martin did a good job explaining the niche situations when someone may choose to run from characteristics, but I am comfortable calling run from features best practice.

 

[[Ri...]]

The only time I have used run from characteristics is when we setup a live feed from Calypso to a database.

Every time a characteristic was completed it would send the result to a database, and you could get real-time results at the machine making the part.

This was way back around 2005. I think it was called porting data.

[[Ba...]]

As a heads up - don't run from characteristics if you have a mini plan created and use sub clearance navigation.