By hiding the implementation of different types of lights behind a carefully designed interface, the light transport routines can operate without knowing which particular types of lights are in the scene similar to how the acceleration structures can hold collections of primitives without needing to know their actual types.
We describe the basic architecture of the two packages and examine in detail the noise and RFI modeling in HIDE, as well as the implementation of gain calibration and RFI mitigation in SEEK.
All functionality can be accessed via a Python interface that hides the implementation details.
For example, even though classes hide the implementation details of their methods, except for abstract ones, they must have implementations.
Exposing functionalities through a web application programming interface allows to hide the implementation details of both data storage (different database types vs. memory vs. file system backend) and processing (descriptor calculation algorithms using CDK, OpenBabel, commercial or in-house implementations).
The implementation of data hiding is simpler than other synchronization techniques.
Because in ABC methods the evaluation of the likelihood is replaced by simulations, the implementation of these methods hides some numerical and technical problems.
We introduce an encapsulated type, Network, the implementation of which is hidden from the planner.
In this paper, we consider one fundamental aspect of DMC design: message passing communication, the implementation of which presents hidden tradeoffs often dismissed in DMC related literature.
The internal complexity of these components, however, is hidden from the user, so he/she can focus on the implementation of the desired protocol characteristics.
