A system design for space-based space surveillance

This paper presents the capabilities of a Space-Based Space Surveillance (SBSS) demonstration mission for Space Surveillance and Tracking (SST) based on a micro- satellite platform. The results have been produced in the frame of ESA’s "As sessment Study for Space Based Space Surveillance Demonstration Mission (Phase A) " performed by the Airbus DS consortium. Space Surveillance and Tracking is part of Space Situational Awareness (SSA) and covers the detection, tracking and cataloguing of spa ce debris and satellites. Derived SST services comprise a catalogue of these man-made objects, collision warning, detection and characterisation of in-orbit fragmentations, sub-catalogue debris characterisation, etc. The assessment of SBSS in an SST system architecture has shown that both an operational SBSS and also already a well - designed space-based demonstrator can provide substantial performance in terms of surveillance and tracking of beyond - LEO objects. Especially the early deployment of a demonstrator, possible by using standard equipment, could boost initial operating capability and create a self-maintained object catalogue. Unlike classical technology demonstration missions, the primary goal is the demonstration and optimisation of the functional elements in a complex end-to-end chain (mission planning, observation strategies, data acquisition, processing and fusion, etc.) until the final products can be offered to the users. The presented SBSS system concept takes the ESA SST System Requirements (derived within the ESA SSA Preparatory Program) into account and aims at fulfilling some of the SST core requirements in a stand-alone manner. The evaluation of the concept has shown that an according solution can be implemented with low technological effort and risk. The paper presents details of the system concept, candidate micro - satellite platforms, the observation strategy and the results of performance simulations for GEO coverage and cataloguing accuracy

Space-based space surveillance and tracking demonstrator: mission and system design

This paper presents the capabilities of a Space-Based Space Surveillance (SBSS) demonstration mission for Space Surveillance and Tracking (SST) based on a micro-satellite platform. The results have been produced in the frame of ESA’s "Assessment Study for Space Based Space Surveillance Demonstration Mission" performed by the Airbus Defence and Space consortium. The assessment of SBSS in an SST system architecture has shown that both an operational SBSS and also already a well- designed space-based demonstrator can provide substantial performance in terms of surveillance and tracking of beyond-LEO objects. Especially the early deployment of a demonstrator, possible by using standard equipment, could boost initial operating capability and create a self-maintained object catalogue. Furthermore, unique statistical information about small-size LEO debris (mm size) can be collected in-situ. Unlike classical technology demonstration missions, the primary goal is the demonstration and optimisation of the functional elements in a complex end-to-end chain (mission planning, observation strategies, data acquisition, processing, etc.) until the final products can be offered to the users and with low technological effort and risk. The SBSS system concept takes the ESA SST System Requirements into account and aims at fulfilling SST core requirements in a stand-alone manner. Additionally, requirements for detection and characterisation of small-sizedLEO debris are considered. The paper presents details of the system concept, candidate micro-satellite platforms, the instrument design and the operational modes. Note that the detailed results of performance simulations for space debris coverage and cataloguing accuracy are presented in a separate paper “Capability of a Space-based Space Surveillance System to Detect and Track Objects in GEO, MEO and LEO Orbits” by J. Silha (AIUB) et al., IAC-14, A6, 1.1x25640.

What is the frequency of nerve injuries associated with acetabular fractures?

BACKGROUND Acetabular fractures and surgical interventions used to treat them can result in nerve injuries. To date, only small case studies have tried to explore the frequency of nerve injuries and their association with patient and treatment characteristics. High-quality data on the risk of traumatic and iatrogenic nerve lesions and their epidemiology in relation to different fracture types and surgical approaches are lacking. QUESTIONS/PURPOSES The purpose of this study was to determine (1) the proportion of patients who develop nerve injuries after acetabular fracture; (2) which fracture type(s) are associated with increased nerve injury risk; and (3) which surgical approach was associated with the highest proportion of patients developing nerve injuries using data from the German Pelvic Trauma Registry. Two secondary aims were (4) to assess hospital volume-nerve-injury relationship; and (5) internal data validity. METHODS Between March 2001 and June 2012, 2236 patients with acetabular fractures were entered into a prospectively maintained registry from 29 hospitals; of those, 2073 (92.7%) had complete records on the endpoints of interest in this retrospective study and were analyzed. The neurological status in these patients was captured at their admission and at the discharge. A total of 1395 of 2073 (67%) patients underwent surgery, and the proportions of intervention-related and other hospital-acquired nerve injuries were obtained. Overall proportions of patients developing nerve injuries, risk based on fracture type, and risk of surgical approach type were analyzed. RESULTS The proportion of patients being diagnosed with nerve injuries at hospital admission was 4% (76 of 2073) and at discharge 7% (134 or 2073). Patients with fractures of the "posterior wall" (relative risk [RR], 2.0; 95% confidence interval [CI], 1.4-2.8; p=0.001), "posterior column and posterior wall" (RR, 2.9; CI, 1.6-5.0; p=0.002), and "transverse+posterior wall" fracture (RR, 2.1; CI, 1.3-3.5; p=0.010) were more likely to have nerve injuries at hospital discharge. The proportion of patients with intervention-related nerve injuries and that of patients with other hospital-acquired nerve injuries was 2% (24 of 1395 and 46 of 2073, respectively). They both were associated with the Kocher-Langenbeck approach (RR, 3.0; CI, 1.4-6.2; p=0.006; and RR, 2.4; CI, 1.4-4.3; p=0.004, respectively). CONCLUSIONS Acetabular fractures with the involvement of posterior wall were most commonly accompanied with nerve injuries. The data suggest also that Kocher-Langenbeck approach to the pelvic ring is associated with a higher risk of perioperative nerve injuries. Trauma surgeons should be aware of common nerve injuries, particularly in posterior wall fractures. The results of the study should help provide patients with more exact information on the risk of perioperative nerve injuries in acetabular fractures. LEVEL OF EVIDENCE Level III, therapeutic study. See Guidelines for Authors for a complete description of levels of evidence.

Towards Faster Method Search Through Static Ecosystem Analysis

Software developers are often unsure of the exact name of the method they need to use to invoke the desired behavior in a given context. This results in a process of searching for the correct method name in documentation, which can be lengthy and distracting to the developer. We can decrease the method search time by enhancing the documentation of a class with the most frequently used methods. Usage frequency data for methods is gathered by analyzing other projects from the same ecosystem - written in the same language and sharing dependencies. We implemented a proof of concept of the approach for Pharo Smalltalk and Java. In Pharo Smalltalk, methods are commonly searched for using a code browser tool called "Nautilus", and in Java using a web browser displaying HTML based documentation - Javadoc. We developed plugins for both browsers and gathered method usage data from open source projects, in order to increase developer productivity by reducing method search time. A small initial evaluation has been conducted showing promising results in improving developer productivity.