Two Novel Methods For The Determination Of The Number Of Components In Independent Components Analysis Models

Independent Components Analysis is a Blind Source Separation method that aims to find the pure source signals mixed together in unknown proportions in the observed signals under study. It does this by searching for factors which are mutually statistically independent. It can thus be classified among the latent-variable based methods. Like other methods based on latent variables, a careful investigation has to be carried out to find out which factors are significant and which are not. Therefore, it is important to dispose of a validation procedure to decide on the optimal number of independent components to include in the final model. This can be made complicated by the fact that two consecutive models may differ in the order and signs of similarly-indexed ICs. As well, the structure of the extracted sources can change as a function of the number of factors calculated. Two methods for determining the optimal number of ICs are proposed in this article and applied to simulated and real datasets to demonstrate their performance.

A proposal for a modular and application-aware autonomic manager of private cloud infrastructures

Recientemente, el paradigma de la computación en la nube ha recibido mucho interés por parte tanto de la industria como del mundo académico. Las infraestructuras cloud públicas están posibilitando nuevos modelos de negocio y ayudando a reducir costes. Sin embargo, una compañía podría desear ubicar sus datos y servicios en sus propias instalaciones, o tener que atenerse a leyes de protección de datos. Estas circunstancias hacen a las infraestructuras cloud privadas ciertamente deseables, ya sea para complementar a las públicas o para sustituirlas por completo. Por desgracia, las carencias en materia de estándares han impedido que las soluciones para la gestión de infraestructuras privadas se hayan desarrollado adecuadamente. Además, la multitud de opciones disponibles ha creado en los clientes el miedo a depender de una tecnología concreta (technology lock-in). Una de las causas de este problema es la falta de alineación entre la investigación académica y los productos comerciales, ya que aquella está centrada en el estudio de escenarios idealizados sin correspondencia con el mundo real, mientras que éstos consisten en soluciones desarrolladas sin tener en cuenta cómo van a encajar con los estándares más comunes o sin preocuparse de hacer públicos sus resultados. Con objeto de resolver este problema, propongo un sistema de gestión modular para infraestructuras cloud privadas enfocado en tratar con las aplicaciones en lugar de centrarse únicamente en los recursos hardware. Este sistema de gestión sigue el paradigma de la computación autónoma y está diseñado en torno a un modelo de información sencillo, desarrollado para ser compatible con los estándares más comunes. Este modelo divide el entorno en dos vistas, que sirven para separar aquello que debe preocupar a cada actor involucrado del resto de información, pero al mismo tiempo permitiendo relacionar el entorno físico con las máquinas virtuales que se despliegan encima de él. En dicho modelo, las aplicaciones cloud están divididas en tres tipos genéricos (Servicios, Trabajos de Big Data y Reservas de Instancias), para que así el sistema de gestión pueda sacar partido de las características propias de cada tipo. El modelo de información está complementado por un conjunto de acciones de gestión atómicas, reversibles e independientes, que determinan las operaciones que se pueden llevar a cabo sobre el entorno y que es usado para hacer posible la escalabilidad en el entorno. También describo un motor de gestión encargado de, a partir del estado del entorno y usando el ya mencionado conjunto de acciones, la colocación de recursos. Está dividido en dos niveles: la capa de Gestores de Aplicación, encargada de tratar sólo con las aplicaciones; y la capa del Gestor de Infraestructura, responsable de los recursos físicos. Dicho motor de gestión obedece un ciclo de vida con dos fases, para así modelar mejor el comportamiento de una infraestructura real. El problema de la colocación de recursos es atacado durante una de las fases (la de consolidación) por un resolutor de programación entera, y durante la otra (la online) por un heurístico hecho ex-profeso. Varias pruebas han demostrado que este acercamiento combinado es superior a otras estrategias. Para terminar, el sistema de gestión está acoplado a arquitecturas de monitorización y de actuadores. Aquella estando encargada de recolectar información del entorno, y ésta siendo modular en su diseño y capaz de conectarse con varias tecnologías y ofrecer varios modos de acceso. ABSTRACT The cloud computing paradigm has raised in popularity within the industry and the academia. Public cloud infrastructures are enabling new business models and helping to reduce costs. However, the desire to host company’s data and services on premises, and the need to abide to data protection laws, make private cloud infrastructures desirable, either to complement or even fully substitute public oferings. Unfortunately, a lack of standardization has precluded private infrastructure management solutions to be developed to a certain level, and a myriad of diferent options have induced the fear of lock-in in customers. One of the causes of this problem is the misalignment between academic research and industry ofering, with the former focusing in studying idealized scenarios dissimilar from real-world situations, and the latter developing solutions without taking care about how they f t with common standards, or even not disseminating their results. With the aim to solve this problem I propose a modular management system for private cloud infrastructures that is focused on the applications instead of just the hardware resources. This management system follows the autonomic system paradigm, and is designed around a simple information model developed to be compatible with common standards. This model splits the environment in two views that serve to separate the concerns of the stakeholders while at the same time enabling the traceability between the physical environment and the virtual machines deployed onto it. In it, cloud applications are classifed in three broad types (Services, Big Data Jobs and Instance Reservations), in order for the management system to take advantage of each type’s features. The information model is paired with a set of atomic, reversible and independent management actions which determine the operations that can be performed over the environment and is used to realize the cloud environment’s scalability. From the environment’s state and using the aforementioned set of actions, I also describe a management engine tasked with the resource placement. It is divided in two tiers: the Application Managers layer, concerned just with applications; and the Infrastructure Manager layer, responsible of the actual physical resources. This management engine follows a lifecycle with two phases, to better model the behavior of a real infrastructure. The placement problem is tackled during one phase (consolidation) by using an integer programming solver, and during the other (online) with a custom heuristic. Tests have demonstrated that this combined approach is superior to other strategies. Finally, the management system is paired with monitoring and actuators architectures. The former able to collect the necessary information from the environment, and the later modular in design and capable of interfacing with several technologies and ofering several access interfaces.

Combinatorial association and abundance of components of interferon-stimulated gene factor 3 dictate the selectivity of interferon responses.

Genes containing the interferon-stimulated response element (ISRE) enhancer have been characterized as transcriptionally responsive primarily to type I interferons (IFN alpha/beta). Induction is due to activation of a multimeric transcription factor, interferon-stimulated gene factor 3 (ISGF3), which is activated by IFN alpha/beta but not by IFN gamma. We found that ISRE-containing genes were induced by IFN gamma as well as by IFN alpha in Vero cells. The IFN gamma response was dependent on the ISRE and was accentuated by preexposure of cells to IFN alpha, a treatment that increases the abundance of ISGF3 components. Overexpression of ISGF3 polypeptides showed that the IFN gamma response depended on the DNA-binding protein ISGF3 gamma (p48) as well as on the 91-kDa protein STAT91 (Stat1 alpha). The transcriptional response to IFN alpha required the 113-kDa protein STAT113 (Stat2) in addition to STAT91 and p48. Mutant fibrosarcoma cells deficient in each component of ISGF3 were used to confirm that IFN gamma induction of an ISRE reporter required p48 and STAT91, but not STAT113. A complex containing p48 and phosphorylated STAT91 but lacking STAT113 bound the ISRE in vitro. IFN gamma-induced activation of this complex, preferentially formed at high concentrations of p48 and STAT91, may explain some of the overlapping responses to IFN alpha and IFN gamma.

Report of the general manager of railways.

1903 has appendix: Statement of revenue and expenditure and statistics of traffic of each station for the year ended 31st Decenber, 1903.

Hand receipt covering contents of components of end item (COEI), basic issue items (BII), and additional authorization list (AAL) for truck, utility, cargo/troop carrier, 1-1/4 ton, 4x4, M998 (2320-01-107-7155) ... truck, ambulance, 2-litter, soft top, 4x4, M1035 (2310-01-146-7194).

"May 1988."

Hand receipt covering contents of components of end item (COEI), basic issue items (BII), and additional authorization list (AAL) for armored combat earthmover (ACE), M9 (NSN 2350-00-808-7100).

"June 1992."

Hand receipt covering contents of components of end item (COEI), basic issue items (BII), and additional authorization list (AAL) for radio test set AN/PRM-34 (NSN 6625-01-094-5646).

"2 September 1983."

Hand receipt covering contents of components of end item (COEI), basic issue items (BII), and additional authorization list (AAL) for Multiple Integrated Laser Engagement System (MILES) simulator system, firing, laser, M80, NSN 1270-01-165-6240, for AH-1S helicopter.

"October 1988."

Hand receipt covering content of components of end item (COEI), basic issue items (BII), and additional authorization list (AAL) for tank, combat, full-tracked, 105-mm gun, M1 (2350-01-061-2445) General Abrams.

"March 1985."

Hand receipt covering contents of components of end item (COEI), basic issue items (BII), and additional authorization list (AAL) for tractor, full tracked, low speed, diesel engine-driven-medium-drawbar-pull : model, tractor with ripper ... NSN, 2410-01-223-0350 ....

"November 1992."

Hand receipt covering contents of components of end item (COEI), basic issue items (BII), and additional authorization list (AAL) for truck, container handler, rough terrain, 50,000 lb capacity, DED, PT (NSN 3930-01-082-3758) with tophandler(s).

"May 1981."

Hand receipt covering contents of components of end item (COEI), basic issue items (BII), and additional authorization list (AAL) for automatic message switching central AN/TYC-39(V)1 (NSN 5805-01-123-1851), AN/TYC-39(V)5 (NSN 5805-01-152-3068).

"20 April 1984."