Effet pervers

vignette|upright=1.2|Le ravinement en Australie causé par les lapins.La libération de lapins en Australie à des fins de chasse a eu de graves conséquences écologiques non voulues. On nomme effet pervers un résultat non désiré et fâcheux d'une action qui se retourne contre les intentions de ceux qui l'ont engagée, selon la formule . Définition Un effet pervers peut se traduire par :

de simples difficultés et obstacles pour atteindre le résultat ;
une action en retour partiellement opposée au système sur lequel on agit (par exemple : loi Le Chatelier) ;
des effets particulièrement malencontreux contre toute attente (« loi de Murphy ») ;
un résultat contreproductif ou désastreux, parce qu'annulant, voire aboutissant à l'inverse de celui recherché (effet boomerang).

Ces résultats « contreproductifs », ces « dommages collatéraux », « effets secondaires » et « conséquences non désirées », sont nombreux, tant dans la vie courante, que dans les domaines concernant l

Improving API Documentation for Java-like Languages

Gilles Dubochet, Donna Malayeri

The Javadoc paradigm for displaying API documentation to users is quite popular, with similar variants existing for many mainstream languages. However, two user interface design properties of Javadoc may reduce its utility when displaying documentation for APIs that make use of inheritance and parametric polymorphism. First, Javadoc does not show a flattened view of all members of a class or interface, but rather only those defined directly in the type. Second, and as a consequence, any methods whose types contain type parameters of a superclass will always be shown in the context of the superclass. That is, if the method C.m returns type T, subclasses of C will always see this parent signature, even if they instantiate T to a concrete type such as Integer. We show that this situation arises often in some libraries, and present the results of a study that measures the usability consequences of these two Javadoc design decisions. Our results show that a user interface that shows instantiated type parameters for members is preferred over one that presents type parameters in the Javadoc style.

2010

N-removal optimization by various aeration strategies

Simon Taillard

In order to improve the purification capacity of an aerobic granular sludge, two aeration strategies were designed and tested. The goal was to optimize the nitrogen removal performances via various oxygen patterns in the aeration phase of the reactor cycle. The main process driving theses patterns is that a difference between oxygen concentrations in the reactor will modify the size of the anoxic inner zone of a granule. The first aeration was based on a succession of oxygen peaks (50%DO) and semi anoxic valleys (5%DO). The second was based on a short pulse of oxygen followed by the hermetical isolation of the reactor and a continuous recirculation of the pulse. The objective was to get an n-removal superior to 82%, results of a previous article, and if possible better than 88%, results of a previous experiment in the lab. The succession of oxygenated peaks strategy worked well and gave good results, as the n-removal was increasing with the sludge bed height and time. However, due to laboratories problem and to the shortness of the time-slots available to experiment, the system could not have the time to stabilize and no constant removal value could be found. Therefore, the average n-removal was equal to 69% for 40 days of experimentation, with some peak over 80%. The highest value observed was 88% of n-removal. The recirculation strategy gave unsatisfactory results, actually unexplained. The first recirculation led to the disappearance of high nitrification capacity, giving an n-removal percentage of 48%. The second attempt was worse, as the oxygen concentration started to behave incoherently and over-oxygenated the system. This behavior still lacks a proper explanation and only hypotheses can actually be proposed. Besides these mains results, the surveillance of the sludge in the reactors allowed the discovery of a bias in the evaluation of the suspended biomass measurement. It was explained by the fact that heavier granules tend not to mix well, and therefore the system could not be considered homogenous. The bias was created because measurements were made at different height between the two reactors. In order to remove it, a linear transformation was developed and tested. The first results seem to be consistent, but due to the lack of experimenting time, the working hypothesis could not be deepened. Another bias that was spotted is the possible influence of the operator during the aeration cycle measurement. Three of four off-trend points in the first experiment originated from a cycle measurement. The data set was too small to draw strong conclusions upon the bias. An extended survey of the cycle measurement and their supposed off-trend consequences in previous and future experiments could clarify the situation.

2009

N-removal optimization by various aeration strategies

Simon Taillard

2009

Improving API Documentation for Java-like Languages

Evolution of a restored river course and alternative measures to correct unintended effects

N-removal optimization by various aeration strategies

N-removal optimization by various aeration strategies

Improving API Documentation for Java-like Languages

Evolution of a restored river course and alternative measures to correct unintended effects