What does the word "characterize" mean in an EE context?
Starting at the beginning,
Simple Definition of characterize
: to describe the character or special qualities of (someone or something)
Source: Merriam-Webster's Learner's Dictionary
This is one of two basic definitions for characterize (which describes the action you are referring to).
I think this definition makes a lot of sense, in context, but coming at it from the other direction, an instrument or device or circuit that is NOT characterized has not been studied and described in a way that may be necessary to understand its fundamental characteristics.
In general, there are two categories of device that the EE can deal with.. one that is characterized sufficiently.. ie one that is understood well enough to utilize for some purpose -- but not necessarily totally understood.
...and one that is NOT characterized sufficiently. You may characterize a resistor as Red Black Black Gold by visual observation. You understand that to be a 20 Ohm 5% resistor, and have a reasonable belief that the marking is accurate. But if you need a 1/2 watt resistor, but are unsure of what you have, it is not sufficiently characterized.
You may characterize it by putting a certain amount of power through it and observing the temperature rise... eventually deciding that 1/2W through the resistor raises the case temperature 40C, and that this is sufficient in your application.
NOW the resistor is fully characterized to your need.
"Why would a EE invest time in characterizing a device or instrument?"
If the EE does not fully understand the specification of the device or instrument, or the needed information isn't published as a specification, the EE needs to do work to determine if that device or instrument will work in the needed application.
"What would be his or her primary objectives in doing so? What outcomes, once achieved, would cause them to stop characterizing, considering their objectives achieved?"
Generally this is a test for suitability. Once these questions have been answered (is this device suitable: yes or no?) it's probably time time to stop.
"In what ways am I already naturally occupied by characterizing devices, circuits, or whatever, just that I'm not using that word to describe what I'm doing?"
Any time you seek to understand a device or a circuit in a situation that isn't fully given by its documentation, a characterization step probably is taking place -- especially if that effort involves testing.
Because things never work in practice quite how they work in theory.
Say you're an IC designer. You design your transistors and gates and registers and design, based on the simulation, it all works perfectly. But once manufactured, you need to know whether it actually works correctly, and if it does how it performs. If you made an amplifier you might want to know what it's gain is - and is that what you expect. How does your buffer design perform for clock jitter and slew rates - that is important to know if you are to use it in a circuit.
Even moving away from VLSI, characterisation is important. Say you build a filter using an op-amp. In theory you know the bandwidth, however in practice due to component tolerances and the like you might find it performs differently. You need to characterise it to know for sure what its behaviour is and whether you need to make corrections to the design.
You might design a microcontroller software which has to interface with some device. You need to characterise the timing of your I/O signals to see if they are performing as expected.
TL;DR; Characterisation is basically determining how the circuit/system/whatever you designed behaves, what its characteristics are, and whether performs within the required parameters to do the job.
One place the term characterise shows up is in simulation. All simulation tools and models are compromises, and the actual simulation results you get will usually be accurate in a particular mode of operation for a circuit, but not all potential operating scenarios.
I will give a three scenarios where a simulation does not sufficiently characterise a circuit (there are obviously hundreds if not thousands of examples):
- Operational amplifier start-up, particularly for auto-zero (usually commutating) devices. Below is a picture of the start-up behaviour of the LTC2050 running on a single rail:
If you care about start-up behaviour (we did in this case), then the simulation has not sufficiently characterised the device. Try as you will with the model, you will not see this behaviour in simulation even if you set the power supplies to be pulse generators.
A TVS device model showed instant clamping for lightning simulation testing (see DO160), but in reality it took about 500ns to actually engage, subjecting downstream silicon devices to a few hundred volts with predictable results. Once more, the simulation did not sufficiently characterise the part (I ended up modifying the model to reflect reality) and changed the circuit to compensate.
A CMOS analogue switch driving a large complex load (A moving surface on a wing in this case). When we had inductive kickback (not huge, but it was there), the model was completely wrong. I ended up making my own model of a CMOS analogue switch (using 4 terminal MOSFETS) that reflected the reality of the operation of the switch.
In these cases, measurements were necessary to characterise the parts sufficiently for my needs.
I do not blame the manufacturers, as they have optimised their models for the majority of use cases for other reasons, and in some cases guidance is provided.