Scaleup of wet granulation processes: science not art

Significant advances have been made in the last decade to quantify the process of wet granulation. The attributes of product granules from the granulation process are controlled by a combination of three groups of processes occurring in the granulator: (1) wetting and nucleation, (2) growth and consolidation and (3) breakage and attrition. For the first two of these processes, the key controlling dimensionless groups are defined and regime maps are presented and validated with data from tumbling and mixer granulators. Granulation is an example of particle design. For quantitative analysis, both careful characterisation of the feed formulation and knowledge of operating parameters are required. A key thesis of this paper is that the design, scaleup and operation of granulation processes can now be considered as quantitative engineering rather than a black art. Résumé

Reasoning about timeouts

In real-time programming a timeout mechanism allows exceptional behaviour, such as a lack of response, to be handled effectively, while not overly affecting the programming for the normal case. For. example, in a pump controller if the water level has gone below the minimum level and the pump is on and hence pumping in more water, then the water level should rise above the minimum level within a specified time. If not, there is a fault in the system and it should be shut down and an alarm raised. Such a situation can be handled by normal case code that determines when the level has risen above the minimum, plus a timeout case handling the situation when the specified time to reach the minimum has passed. In this paper we introduce a timeout mechanism, give it a formal definition in terms of more basic real-time commands, develop a refinement law for introducing a timeout clause to implement a specification, and give an example of using the law to introduce a timeout. The framework used is a machine-independent real-time programming language, which makes use of a deadline command to represent timing constraints in a machine-independent fashion. This allows a more abstract approach to handling timeouts.