Some CoRoT highlights - A grip on stellar physics and beyond

About 2 years ago, back in 2009, the first CoRoT Symposium was the occasion to present and discuss unprecedented data revealing the behaviour of stars at the micromagnitude level. Since then, the observations have been going on, the target sample has enriched and the work of analysis of these data keeps producing first rank results. These analyses are providing the material to address open questions of stellar structure and evolution and to test the so many physical processes at work in stars. Based on this material, an increasing number of interpretation studies is being published, addressing various key aspects: the extension of mixed cores, the structure of near surface convective zones, magnetic activity, mass loss, ... Definitive conclusions will require cross-comparison of results on a larger ground (still being built), but it is already possible at the time of this Second CoRoT Symposium, to show how the various existing results take place in a general framework and contribute to complete our initial scientific objectives. A few results already reveal the potential interest in considering stars and planets globally, as it is stressed in several talks at this symposium. It is also appealing to consider the fast progress in the domain of Red Giants and see how they illustrate the promising potential of space photometry beyond the field of stellar physics, in connex fields like Galactic dynamics and evolution.Comment: 9 pages, 13 figures, to appear in Proceedings of the Second CoRoT Symposium, held in Marseille, June 14-17th 201

Convoluting device for forming convolutions and the like Patent

Punch and die device for forming convolution series in thin gage metal hemisphere

Advanced software development workstation. Comparison of two object-oriented development methodologies

This report is an attempt to clarify some of the concerns raised about the OMT method, specifically that OMT is weaker than the Booch method in a few key areas. This interim report specifically addresses the following issues: (1) is OMT object-oriented or only data-driven?; (2) can OMT be used as a front-end to implementation in C++?; (3) the inheritance concept in OMT is in contradiction with the 'pure and real' inheritance concept found in object-oriented (OO) design; (4) low support for software life-cycle issues, for project and risk management; (5) uselessness of functional modeling for the ROSE project; and (6) problems with event-driven and simulation systems. The conclusion of this report is that both Booch's method and Rumbaugh's method are good OO methods, each with strengths and weaknesses in different areas of the development process

Orbital Polarization in Strained LaNiO3_{3}: Structural Distortions and Correlation Effects

Transition-metal heterostructures offer the fascinating possibility of controlling orbital degrees of freedom via strain. Here, we investigate theoretically the degree of orbital polarization that can be induced by epitaxial strain in LaNiO$_3$ films. Using combined electronic structure and dynamical mean-field theory methods we take into account both structural distortions and electron correlations and discuss their relative influence. We confirm that Hund's rule coupling tends to decrease the polarization and point out that this applies to both the $d^8\underline{L}$ and $d^7$ local configurations of the Ni ions. Our calculations are in good agreement with recent experiments, which revealed sizable orbital polarization under tensile strain. We discuss why full orbital polarization is hard to achieve in this specific system and emphasize the general limitations that must be overcome to achieve this goal.Comment: 13 pages, 13 figure

Knowledge base methodology: Methodology for first Engineering Script Language (ESL) knowledge base

The primary goal of reusing software components is that software can be developed faster, cheaper and with higher quality. Though, reuse is not automatic and can not just happen. It has to be carefully engineered. For example a component needs to be easily understandable in order to be reused, and it has also to be malleable enough to fit into different applications. In fact the software development process is deeply affected when reuse is being applied. During component development, a serious effort has to be directed toward making these components as reusable. This implies defining reuse coding style guidelines and applying then to any new component to create as well as to any old component to modify. These guidelines should point out the favorable reuse features and may apply to naming conventions, module size and cohesion, internal documentation, etc. During application development, effort is shifted from writing new code toward finding and eventually modifying existing pieces of code, then assembling them together. We see here that reuse is not free, and therefore has to be carefully managed